URAC Dental Network Accreditation: Closing Critical Gaps After a Failed Desktop Review
Last updated: April 2026
A regional dental PPO network managing over 4,000 contracted dental providers came to IHS after URAC's desktop review identified deficiencies that prevented accreditation. The network had submitted its application without consulting support, believing its existing credentialing vendor relationships and compliance documentation were sufficient. They were not. IHS conducted a full gap remediation engagement and supported the organization through a successful resubmission. This is an account of what failed, why, and how each gap was closed.
Client identity is confidential. Operational details have been generalized to protect identifying information while preserving the accuracy of the accreditation challenges and remediation approach.
Client Background
The client was a regional dental PPO network operating across three states, managing a panel of approximately 4,200 dental and dental specialist providers. The network contracted its credentialing functions to a third-party credentialing vendor and had operated under that delegation arrangement for over seven years. The network also contracted network management and quality monitoring functions to a separate vendor.
The network's primary revenue came from contracts with self-insured employer groups and a regional health plan. When the health plan notified the network that future contract renewals would require URAC Dental Network Accreditation as a condition of continued participation, the network submitted an application without conducting a formal gap analysis. Six months into the desktop review, URAC issued a preliminary report identifying deficiencies across four of the five core standards domains. The network was unable to achieve accreditation on that submission.
The network engaged IHS three weeks after receiving URAC's preliminary deficiency report.
The Gap Analysis: What the Preliminary Report Revealed
IHS began with a full review of URAC's preliminary deficiency report alongside the network's submitted documentation, delegation agreements, credentialing policies, and operational practices. Four categories of deficiency required remediation before resubmission.
Gap 1: Delegation Agreement Deficiencies — Both Vendors
What URAC found: Neither delegation agreement — for the credentialing vendor nor the network management vendor — contained the specific oversight language URAC's standards require. The credentialing vendor agreement described the scope of delegated functions and payment terms but did not include: (a) defined performance reporting obligations with specified frequency and content; (b) the network's explicit right to audit the vendor's credentialing operations; (c) provisions specifying corrective action procedures when the vendor's performance falls below defined standards; or (d) provisions addressing what happens to the delegation arrangement in the event the vendor's own accreditation status changes.
The network management vendor agreement had similar gaps, with no audit access provision and no defined escalation process for network adequacy failures.
What this meant operationally: The network had been operating for seven years under delegation arrangements that provided no contractual mechanism for oversight. The credentialing vendor's operations were effectively unreviewed by the network — there were no required reports, no audit history, and no documented corrective action instances, because the agreement did not require any of these activities.
IHS remediation approach: IHS drafted amendment language for both agreements addressing all deficient provisions. The credentialing agreement was amended to require quarterly credentialing activity reports in a defined format, annual operational audits by the network, a corrective action initiation process with defined timelines, and provisions addressing vendor accreditation status changes. The network management agreement was amended to require quarterly network adequacy reports, defined escalation procedures for adequacy failures, and annual audit rights.
Negotiating these amendments with two external vendors — each with their own legal review processes — required eleven weeks. This is typical. Delegation agreement remediation is the longest-lead item in most URAC Dental Network Accreditation gap closure processes because it requires external cooperation from entities with no direct incentive to expedite the changes.
Gap 2: Credentialing Documentation — Primary Source Verification Records
What URAC found: URAC's desktop review selected a sample of provider credentialing files for review. In multiple files, primary source verification documentation was either absent or insufficient to demonstrate that verification had been completed. Several files showed only the credentialing vendor's summary notation ("verification complete") without the underlying verification records. URAC's standards require that the primary source verification be documented in a way that demonstrates the verification actually occurred — a vendor summary is not sufficient.
Recredentialing documentation showed a second problem: a subset of providers had recredentialing dates that had lapsed by 60-90 days, with no documentation of the network's response to the lapse. URAC's standards require defined recredentialing cycles and documentation that the organization has a process for identifying and acting on lapses.
What this meant operationally: The credentialing vendor was performing verifications, but the vendor's file structure did not retain the underlying verification records in a way that transferred to the network's documentation. The network's credentialing committee received summary reports, not file-level verification records. This created an accreditation-fatal documentation gap — the network could not demonstrate primary source verification for the sampled files, regardless of whether verification had actually occurred.
IHS remediation approach: IHS worked with the network and its credentialing vendor to restructure the vendor's file delivery format to include underlying verification documentation rather than summary notations. This required renegotiating a portion of the service agreement and establishing a new file transfer protocol. For the recredentialing lapse issue, IHS developed a lapse identification and escalation policy with defined response timelines and a tracking log format that generates audit evidence of how each lapse was identified and resolved. The network ran the new process for 90 days before resubmission to generate demonstrable operational history.
Gap 3: Consumer Protection Policy Infrastructure
What URAC found: The network lacked formal written policies for three required consumer protection areas: confidentiality of provider and member information, informed consent procedures at the network level, and a defined complaint and dispute resolution process with documented timelines and escalation procedures. The network had informal practices in each area — confidentiality was addressed in employment agreements and vendor contracts, and complaints were handled through a general inbox — but none of these informal practices existed as written network-level policies.
What this meant operationally: URAC's consumer protection standards require documented policies, not informal practices. The existence of a confidentiality clause in an employment agreement does not satisfy the requirement for a formal confidentiality policy. The handling of complaints through a general inbox does not satisfy the requirement for a defined complaint and dispute resolution process with documented timelines. The gap was structural, not operational — the network's practices were reasonable, but they were not documented in a form that satisfied URAC's evidentiary requirements.
IHS remediation approach: IHS developed three policy documents from template frameworks: a network-level confidentiality policy covering provider information, internal data handling, and breach notification procedures; an informed consent policy addressing the network's member-facing consent practices; and a complaint and dispute resolution policy with defined intake procedures, response timelines, escalation pathways, and documentation requirements. Each policy was reviewed against URAC's standards language before finalization. Implementation required eight weeks, including staff briefings and the establishment of a documented complaint log that began generating operational evidence before resubmission.
Gap 4: Performance Management Framework
What URAC found: The network did not have a formal performance management framework. Quality data was collected — provider complaints, utilization patterns, patient satisfaction data — but there was no documented process for: (a) defining the quality metrics the network monitors, (b) reviewing performance data on a defined schedule, (c) making improvement decisions based on that review, or (d) documenting the outcomes of improvement initiatives. URAC's standards require not just data collection but a documented cycle of monitoring, review, decision, implementation, and outcome tracking.
What this meant operationally: The network's quality data existed but could not demonstrate a performance management system to URAC surveyors. Data without a documented monitoring and improvement process does not satisfy URAC's performance management requirements. This is a common gap in organizations that collect quality data informally without formalizing the use of that data into a documented management cycle.
IHS remediation approach: IHS developed a performance management framework document defining the network's quality metrics, monitoring schedule (quarterly review with annual summary), review body and composition, decision documentation requirements, improvement initiative tracking format, and outcome reporting obligations. The framework was designed to be operationally manageable for a network of the client's size — not a compliance exercise requiring a large quality department, but a structured process that generates documented evidence of active performance management. The network ran one full quarterly review cycle under the new framework before resubmission to generate demonstrable operational history.
Resubmission and Outcome
The remediation engagement ran seventeen weeks from IHS engagement to resubmission — longer than IHS's initial estimate of twelve weeks, primarily because the delegation agreement negotiations with both vendors extended beyond the projected timeline. This is the most common source of schedule variance in URAC Dental Network Accreditation engagements: internal documentation can be developed and implemented on a controlled schedule, but delegation agreement remediation depends on external parties whose legal review and negotiation processes are outside the network's control.
IHS assembled the resubmission package, ensuring all amended documentation was properly organized, cross-referenced, and consistent with the network's updated policies and agreements. URAC conducted the resubmission desktop review, and the network received URAC Dental Network Accreditation within the subsequent review cycle.
The health plan partner extended the network's contract on the basis of the accreditation award. A second employer group contract, which had been contingent on accreditation, was executed within sixty days of the accreditation award.
What This Case Illustrates About URAC Dental Network Accreditation
Delegation agreements are the longest-lead item — review them first
Every organization delegating credentialing or network management functions has delegation agreements. Most of those agreements, if not recently reviewed against URAC's standards requirements, contain deficiencies. Identifying delegation agreement gaps in week one of preparation — rather than discovering them in URAC's desktop review — saves months. The eleven-week negotiation timeline in this case could not have been compressed; it could only have been started earlier.
Vendor documentation practices must produce accreditation-grade records
A credentialing vendor performing primary source verification does not automatically produce documentation that satisfies URAC's evidentiary requirements. The vendor's internal file format — optimized for the vendor's own workflow — may not generate the documentation that URAC surveyors need to see in your organization's files. Organizations delegating credentialing must review not just whether verification is being performed, but whether the documentation of that verification can survive an accreditation desktop review.
Informal practices do not substitute for written policies
The network in this case was not operating poorly. Its credentialing practices were functional, its complaint handling was responsive, its data collection was reasonable. What it lacked was documentation. URAC's standards require written policies — not because the standards are procedurally rigid, but because written policies are the only form of evidence that surveyors can review. Organizations that operate through institutional knowledge, informal practices, or undocumented conventions will consistently fail desktop reviews regardless of how well they actually operate.
Performance management is a cycle, not a dataset
Collecting quality data is not the same as operating a performance management system. URAC's standards require evidence of a documented monitoring and improvement cycle — not just data, but a demonstrated process for using that data to make decisions and track outcomes. Organizations with strong data collection practices often assume this requirement is satisfied. It is not, unless the data collection is embedded in a documented management process that generates a reviewable audit trail.
The cost of a failed submission is always higher than the cost of preparation
The network's failed first submission cost it: the original URAC application fees, seventeen weeks of remediation time during which the health plan contract was in jeopardy, a second application cycle, and the operational burden of running remediation while maintaining normal network operations. Every one of these costs would have been avoided — or dramatically reduced — by conducting a gap analysis before the first application submission.
How IHS Approaches URAC Dental Network Accreditation Engagements
IHS begins every URAC Dental Network Accreditation engagement with a standard-by-standard gap analysis that treats every delegation agreement, credentialing policy, consumer protection practice, and performance monitoring process as a potential deficiency until it is confirmed otherwise. We do not assume existing documentation is sufficient. We read it against the standards.
IHS is led by Thomas G. Goddard, JD, PhD, former COO and General Counsel of URAC. The institutional knowledge of how URAC standards are developed, how surveyors are trained to apply them, and where interpretive questions consistently arise is embedded in every gap analysis IHS conducts. That knowledge is the difference between identifying a delegation agreement deficiency in week one of preparation and discovering it in URAC's preliminary deficiency report six months later.
IHS handles the full engagement: gap analysis, delegation agreement review, policy development, application assembly, and desktop review RFI support. Engagement fees are scoped per client based on network size, delegation complexity, and current gap severity.
Start with a Gap Analysis — Before You Apply
The most expensive URAC Dental Network Accreditation mistake is submitting an application before your organization is ready. IHS conducts a standard-by-standard gap analysis that identifies every deficiency before URAC does — and gives your organization a remediation roadmap with realistic timelines before a single application document is submitted.