URAC Pharmacy Services Accreditation: Regional PBM Case Study
Last updated: April 2026
This case study describes a representative IHS engagement with a regional pharmacy benefit manager pursuing URAC Pharmacy Services Accreditation for the first time. Identifying details have been changed to protect client confidentiality. The compliance challenges, deficiency patterns, timeline, and outcomes described reflect the actual characteristics of first-time PBM accreditation engagements.
The Situation
Organization Profile
A regional pharmacy benefit manager serving approximately 180,000 covered lives across employer group and small commercial health plan clients in the mid-Atlantic region. The organization had operated for nine years without external accreditation, competing on price and regional relationships. When its two largest employer group clients — accounting for a combined 40% of covered lives — notified the PBM that their next contract renewal would require demonstrated URAC Pharmacy Services Accreditation, the organization engaged IHS.
The contracts were up for renewal in 14 months. URAC accreditation had to be achieved in time to satisfy the renewal requirements.
Starting Baseline
The IHS gap analysis identified the organization's starting position as low-compliance across several critical standards domains. The PBM had solid operational history and genuinely good dispensing practices — but had never built its documentation infrastructure against external accreditation standards. The gap was not primarily operational; it was documentary and systemic. The organization did not have policies aligned with URAC's specific criteria, did not have a functioning performance measure data collection system for all five URAC core measures, and had never evaluated its consumer grievance procedures against URAC's CPE standards.
Three domains required structural intervention before the accreditation application could be submitted:
- Performance monitoring infrastructure — no systematic collection of call center performance data, and inconsistent collection of prescription turnaround time data. Dispensing accuracy and distribution accuracy were tracked internally but not in a format suitable for URAC reporting.
- Patient management documentation — clinical assessments were being conducted by pharmacists during patient interactions but were not documented in pharmacy management software in the format and at the frequency URAC requires. The compliance gap existed not in clinical quality but in documentation.
- Consumer grievance procedures — the organization's grievance process omitted state-specific regulatory information from grievance communications, a recurring deficiency category in URAC pharmacy surveys.
The IHS Approach
Phase 1: Gap Analysis and Remediation Roadmap (Months 1-2)
IHS conducted a standard-by-standard gap analysis across all applicable URAC Pharmacy Services modules. The analysis produced a prioritized remediation roadmap — not a generic checklist, but a gap-by-gap action plan sequenced by remediation complexity and lead time. Gaps requiring structural changes (performance monitoring infrastructure) were addressed first. Gaps resolvable through policy development were sequenced to follow the structural fixes, ensuring policies reflected actual operations rather than aspirational ones.
The analysis identified 31 discrete gaps across six standards modules. Eleven were classified as high-priority (likely to generate RFIs or survey failure without remediation). Eight required structural or technical changes. Twelve were addressable through policy development and staff training alone.
Phase 2: Performance Monitoring Infrastructure (Months 2-4)
The most significant pre-application task was building functional performance monitoring infrastructure for all five URAC core pharmacy performance measures. The organization's IT team, working with IHS guidance on URAC's specific data collection and reporting requirements, implemented tracking for call center response times and abandonment rates, standardized prescription turnaround time measurement from receipt to dispensing confirmation, and reformatted existing dispensing and distribution accuracy tracking into URAC-reportable formats.
IHS provided the data collection specifications and reporting format requirements derived from direct knowledge of what URAC surveyors evaluate during the desktop review. The IT implementation took approximately 6 weeks. The organization then ran two full months of performance data collection before application submission — the minimum data history IHS recommended for demonstrating ongoing monitoring to surveyors.
Phase 3: Policy Development and Patient Management Documentation (Months 3-5)
IHS provided policy templates across all six standards modules. The organization's compliance team adapted each template to reflect actual operations, with IHS review of each adapted policy for URAC alignment before finalization. The policy development process took longer than typical because several policies required coordination across pharmacy operations, IT, and legal — particularly the consumer grievance and appeals procedures requiring state-specific regulatory content for each of the seven states in the PBM's operating footprint.
The patient management documentation gap required a workflow change rather than a policy change. IHS worked with the organization's pharmacy management software vendor to configure documentation fields and prompts aligned with URAC's clinical assessment requirements. Pharmacists received training on the new documentation protocol, with a four-week compliance period generating documented evidence before the mock desktop review.
Phase 4: Mock Desktop Review (Month 6)
IHS conducted a mock desktop review simulating URAC's survey process. The review evaluated all six standards modules against submitted policies and supporting documentation. IHS identified 14 deficiencies during the mock review — all were corrected before application submission. The most consequential finding was that three state-specific grievance packet templates still omitted required regulatory information for two states, despite the policy revision. The error was in the grievance packet templates themselves, not the governing policy — a distinction that would have generated RFIs during the actual desktop review.
The mock review also identified that dispensing accuracy data was being reported at the dispensing event level rather than at the prescription level, as URAC requires. The reporting format was corrected before submission.
Phase 5: Application Submission and Desktop Review (Months 7-9)
The formal URAC application was submitted in month seven. URAC's desktop review phase took 38 days. At the conclusion of the desktop review, URAC issued seven Requests for Information across four standards modules. All seven RFIs were within domains IHS had flagged as residual risk during the mock review — none were surprises.
The seven RFIs covered:
- CSCD module (2 RFIs) — documentation of call center supervisor training on the grievance escalation protocol, and evidence of patient notification timing for a specific disclosure category
- Drug Management module (1 RFI) — clarification of the drug-drug interaction review process for mail-order refills, where the policy described a process that differed slightly from the pharmacy management software workflow
- Pharm-Op module (2 RFIs) — primary source verification documentation for two pharmacist staff members whose credential files had incomplete primary source evidence, and temperature log documentation for a two-week period three months prior
- PMI module (1 RFI) — additional evidence that prescription turnaround time reporting covered the full patient population rather than a sample
- CPE module (1 RFI) — documentation of the grievance resolution outcome communication for a specific grievance category
IHS drafted all seven RFI responses and assembled supporting documentation packages within URAC's response windows. The response to the Drug Management RFI included a policy revision clarifying the mail-order refill review workflow, along with a brief implementation attestation. All seven RFIs were accepted by URAC surveyors without follow-up requests.
Phase 6: Validation Review and Committee Decision (Months 9-11)
The validation review followed the desktop review closure. URAC surveyors evaluated operational evidence against submitted documentation. No additional findings were issued during the validation review — the mock desktop review and RFI remediation had resolved the documentation gaps that typically surface during validation.
The URAC accreditation committee convened in month eleven. The organization received URAC Pharmacy Services Accreditation — its first external quality credential in nine years of operation — with three years before the renewal survey.
Outcomes
Accreditation Timeline
Eleven months from consulting engagement kickoff to committee decision. URAC's published six-month timeline assumes a compliance baseline the organization did not have at engagement start. The 11-month timeline reflects the additional time required to build performance monitoring infrastructure and remediate the patient management documentation workflow — both of which were prerequisites to application submission.
Contract Retention
The two employer group clients that had made accreditation a contract renewal condition received confirmation of URAC accreditation two months before the renewal deadline. Both contracts were renewed. The accreditation satisfied their pharmacy network quality requirements without requiring a competitive re-bid process.
Preferred Network Tier Access
Following accreditation, the organization applied for preferred-tier status with three commercial health plans in its service region that had previously categorized it as a standard-tier pharmacy network partner. Two of the three health plans moved the organization to preferred-tier status within 90 days of accreditation confirmation, citing URAC Pharmacy Services Accreditation as the qualifying credential for preferred status. Preferred-tier status carries higher reimbursement rates than standard-tier for equivalent services in those plan contracts.
RFI Resolution Rate
Seven RFIs issued. Seven resolved within URAC's response windows. Zero follow-up requests from surveyors after RFI responses were submitted. The mock desktop review conducted before application submission identified and remediated more than a dozen additional deficiencies that would have generated additional RFIs — and potentially extended the timeline by weeks.
Internal Infrastructure Built
Beyond the accreditation credential itself, the organization emerged from the engagement with durable internal infrastructure: a functioning five-measure performance monitoring system, a complete policy library aligned with URAC standards, a grievance and appeals procedure updated for all seven states, and documented staff competency assessment protocols. This infrastructure positions the organization for renewal without a significant re-build — and provides the documentation foundation required if it pursues ACHC accreditation in the future.
What This Engagement Illustrates
URAC's Six-Month Timeline Requires a Compliance Baseline Most Organizations Don't Have
URAC's published six-month accreditation timeline is achievable — for organizations that already have compliant policies, functioning performance monitoring, and audit-ready documentation. In practice, first-time applicants rarely have all three. The gap analysis in this engagement identified 31 discrete compliance gaps. Building the performance monitoring infrastructure alone took six weeks of IT development before the first line of policy could be drafted against the actual operational data. Organizations that plan for six months and discover they need eleven lose the additional five months when they can least afford to.
Performance Monitoring Infrastructure Is a Prerequisite, Not a Deliverable
The single most time-consuming pre-application task in this engagement — and in most first-time pharmacy accreditation engagements — was building functional performance monitoring infrastructure. URAC requires demonstrable performance data, not just policies describing what data will be collected. Organizations that apply without operational data collection for all five core performance measures fail the performance monitoring standards. This is not a documentation problem; it is a systems problem that requires IT involvement and a minimum data collection period before the application can be submitted.
Mock Desktop Review Is Not Optional for First-Time Applicants
The mock desktop review identified 14 deficiencies that the policy development process had not caught — including the state-specific grievance packet error and the prescription-level vs. dispensing-event-level reporting format issue. Both would have generated RFIs. The grievance packet error, in particular, involved a nuance in how state regulatory information must appear in the grievance communication itself (not just in a separate policy) — a distinction that becomes clear only when you evaluate the actual patient-facing document against URAC's CPE standards, as a surveyor would.
RFI Response Quality Matters as Much as Policy Quality
Seven RFIs were issued. All seven were resolved on first response. The resolution rate reflects the quality of the RFI responses — specific, documented, with supporting evidence attached and no ambiguity for surveyors to follow up on. Vague RFI responses that require surveyor follow-up extend the desktop review phase and create additional scrutiny that compounds the original deficiency. IHS's RFI response drafting experience — built on direct institutional knowledge of how URAC surveyors interpret standards — is a material factor in first-response resolution rates.
Schedule a Free Discovery Session
If your organization is facing a contract renewal deadline, a new payer requirement, or a competitive need to establish URAC Pharmacy Services Accreditation, talk directly with Thomas G. Goddard, JD, PhD — former Chief Operating Officer and General Counsel of URAC. He will tell you what the process actually requires for your specific situation, what timeline is realistic given your current compliance baseline, and where IHS can provide the most leverage.