URAC IRO Accreditation: From Regulatory Pressure to Full Award

Last updated: April 2026

Client details have been anonymized to protect confidentiality. This case study is a composite template representing the types of challenges and outcomes IHS routinely addresses in URAC IRO accreditation engagements.

Background

The organization — a physician-founded independent review company operating across 14 states — had been providing external adverse benefit determination reviews for health plans and self-insured employers for seven years. It had built a solid clinical reputation but had never pursued formal accreditation. Two events changed that calculus simultaneously: a major health plan contract required URAC IRO accreditation as a qualification condition effective at the next renewal cycle, and two of the organization's key operating states announced updated IRO registration requirements that explicitly referenced URAC accreditation.

The organization faced a hard deadline. Without accreditation, it stood to lose a contract representing a significant portion of its revenue — and lose regulatory standing in two states. Leadership engaged IHS approximately 13 months before the contract renewal date.

Initial Assessment: What the Gap Analysis Found

IHS conducted a structured readiness assessment against URAC's IRO standards (version 6.0 Comprehensive Review) in the first three weeks of engagement. The assessment revealed four categories of deficiency:

1. Specialty Coverage Documentation

The organization had access to a broad physician reviewer panel but had never systematically documented specialty coverage against URAC's requirements. Several subspecialties — including pediatric subspecialties and certain surgical specialties — lacked documented primary reviewers. The physician panel existed in a spreadsheet that had not been maintained with consistent credentialing documentation. URAC requires not just access to specialties but documented, verified, and current credentials for reviewers in each category.

2. Conflict-of-Interest Protocol Gaps

The organization conducted internal review for two health plans while also conducting external review — placing it squarely in URAC's comprehensive review category with its associated disclosure requirements. Its conflict-of-interest screening was informal and reviewer-attestation-based, with no systematic organizational-level screening protocol. URAC's standards require a documented, repeatable process applied at both the organizational and individual reviewer level. The disclosure obligations for internal review client relationships were entirely unaddressed in existing documentation.

3. Timeframe Compliance Data

The organization met its review deadlines operationally but had no systematic tracking mechanism that could produce the kind of aggregate compliance data URAC reviewers expect to see. Individual case files contained dates but no reporting infrastructure existed to demonstrate population-level timeframe adherence. The desktop review phase would require this data, and the on-site review would probe how the organization monitors and responds to timeframe performance.

4. Policy-to-Practice Alignment

Several existing policies were written at a high level of generality and did not map cleanly to URAC's specific standard language. The medical necessity criteria policy referenced "nationally recognized guidelines" without specifying which guidelines applied to which clinical categories. The appeals process policy lacked required elements on communication timeframes and the documentation of determination rationale. Quality management program documentation existed but had not been updated in two years and did not reflect current operational practices.

The IHS Engagement: What We Did

Phase 1: Remediation Planning (Months 1–2)

IHS developed a detailed remediation plan mapping each deficiency to a specific standard element, an owner within the client organization, and a completion target. The plan was organized to front-load the items with the longest lead times — particularly the reviewer panel documentation and credentialing, which required outreach to and re-credentialing of dozens of physicians.

Phase 2: Reviewer Qualification Program Build (Months 2–5)

IHS designed a formal physician reviewer qualification program, including standardized credentialing application forms, specialty coverage mapping against URAC's required categories, primary source verification procedures, and a re-credentialing cycle. The organization's administrative team was trained on the new process. A tracking database replaced the legacy spreadsheet. By month five, the organization had documented primary reviewer coverage across all required specialties and subspecialties with current credentials on file.

Phase 3: Conflict-of-Interest Protocol Design (Months 2–4)

IHS drafted a comprehensive conflict-of-interest policy covering organizational-level screening (clients for whom the organization provides internal review services are disclosed and managed), reviewer-level screening (attestation plus objective review of referral relationships), and the disclosure obligations URAC requires for comprehensive review organizations. The policy was reviewed against URAC's specific standard language and revised through two drafts before finalization.

Phase 4: Policy Suite Revision (Months 3–6)

IHS systematically reviewed and revised the organization's full policy suite against URAC IRO standards. Key revisions included: medical necessity criteria policy updated to specify named clinical guidelines by review category; appeals policy updated with required communication timeframes and determination rationale documentation requirements; quality management program policy updated to reflect current structure and include active performance metric tracking. New policies were drafted where URAC standards required elements the organization had not previously addressed.

Phase 5: Timeframe Compliance Infrastructure (Months 3–5)

Working with the organization's operations team, IHS designed a simple but URAC-ready timeframe tracking system — a structured case log with automated flagging for reviews approaching deadline thresholds. The system produced monthly compliance reports that could be reviewed by leadership and retained as evidence of ongoing timeframe monitoring. Historical case data was retroactively structured to produce a baseline compliance report for the desktop review submission.

Phase 6: Application and Desktop Review Preparation (Months 6–9)

IHS led the application build, organizing the document submission package for maximum clarity. URAC reviewers evaluate hundreds of accreditation submissions; clear organization and direct standard-to-document cross-referencing reduces review friction and demonstrates program maturity. IHS prepared the desktop review submission document index, ensured every required standard element had a clearly referenced policy or procedure document, and drafted the organizational overview narrative.

Phase 7: On-Site Review Preparation (Month 9)

With the desktop review submitted, IHS shifted to on-site preparation. This included: a mock on-site review with leadership and key staff; preparation of standard question-and-answer frameworks for areas the gap analysis had identified as potential scrutiny points (particularly conflict-of-interest controls and the dual internal/external review function); organization of personnel and reviewer credentialing files for audit access; and a pre-review walk-through of the quality management program documentation.

Results

Key Lessons From This Engagement

Start Earlier Than You Think You Need To

The organization came to IHS with 13 months before its deadline — which proved sufficient, but only because the remediation work moved efficiently. Organizations that engage with 6 months or less before a hard deadline frequently cannot complete the reviewer qualification rebuild and policy revision cycle in time. The URAC process itself takes 10 to 12 months; preparation should begin well before the application is filed.

The Dual Internal/External Function Adds Complexity

Organizations conducting both internal review (for plans) and external review face additional disclosure and conflict-of-interest documentation requirements that organizations providing only one function do not encounter. This complexity is manageable — but it must be addressed explicitly, not assumed to be covered by general conflict-of-interest policies.

Timeframe Data Is Operational, Not Just Compliance

The timeframe tracking system IHS helped build was not just a URAC requirement — it became an operational tool the organization used to manage reviewer workloads and identify bottlenecks before they became compliance problems. The discipline URAC's standards impose on timeframe management made the organization operationally stronger.

On-Site Preparation Is Non-Negotiable

The gap between a well-documented program and a well-performed on-site review is preparation. Organizations that treat the on-site review as an evaluation of their documentation — rather than a demonstration of operational reality — underperform relative to their actual program quality. Mock reviews and staff briefings are not optional extras; they are standard components of effective accreditation preparation.

Is Your Organization Ready for URAC IRO Accreditation?

Whether you are facing a contract requirement, a state registration mandate, or a strategic decision to pursue accreditation as a market differentiator, the starting point is the same: an honest assessment of where your program stands against URAC's current standards. IHS provides that assessment as the first step of every engagement.

Thomas G. Goddard, JD, PhD, former Chief Operating Officer and General Counsel of URAC, leads IHS's IRO accreditation consulting practice. That institutional perspective — built from inside URAC — is what separates IHS from generalist healthcare consultants who work from the outside in.