Dual-Module URAC Health Contact Center Accreditation — Clinical and Non-Clinical in One Engagement
Last updated: April 2026
The following is a composite case study drawn from IHS engagements with regional managed care organizations pursuing URAC Health Contact Center Accreditation. Client-identifying details have been omitted. The operational challenges, gap patterns, and consulting approach described are representative of what IHS encounters in dual-module Health Contact Center engagements.
The Situation
A regional managed care organization operating Medicaid and commercial health plan products had built its member contact center in two phases over five years. The first phase established a nurse advice line — staffed by registered nurses around the clock, using a licensed clinical triage guideline system — to handle member clinical inquiries and health navigation calls. The second phase added a dedicated member services unit handling prior authorization intake, appointment referrals, claims inquiries, and enrollment support, staffed entirely by non-clinical administrative personnel.
Both functions operated under the same contact center director, shared telephony infrastructure, and were co-located. Operationally they were distinct — separate call queues, separate staff, separate supervisory structures — but the organization had never formally documented the boundary between clinical and non-clinical operations in its policies. The handoff protocol between member services staff and the nurse line existed in practice but not on paper.
The trigger for pursuing URAC Health Contact Center Accreditation was a contract renewal with a large self-insured employer group. The employer's vendor qualification requirements had been updated: clinical contact center vendors were now required to demonstrate URAC Health Contact Center Accreditation or provide an alternative quality attestation satisfactory to the employer's benefits committee. The benefits committee had rejected prior alternative attestations for two other vendors in the same procurement cycle. The organization needed URAC accreditation, and it needed it within the contract renewal timeline — approximately nine months.
What the Gap Analysis Revealed
IHS conducted a standard-by-standard gap analysis across both the Clinical Contact Center module and the Non-Clinical Contact Center module (NCP v6.0) in the first four weeks of the engagement. The findings fell into four categories.
1. Undocumented Operational Boundaries
The most significant structural gap: the organization's policy framework did not distinguish between clinical and non-clinical functions. A single set of operational policies covered the entire contact center without differentiating clinical staff protocols from non-clinical staff procedures. URAC reviewers examining the Clinical module would find policies that mixed clinical and administrative language without clear attribution. URAC reviewers examining the NCP module would find the same policies without the administrative-function-specific content NCP standards require.
Both modules would face deficiency findings if the application proceeded as-is. The solution was not to write two separate policy sets — it was to restructure the existing policy architecture into a tiered framework: shared CORE-applicable policies covering the full contact center, a clinical supplement governing nurse triage operations specifically, and an administrative supplement governing non-clinical member services functions.
2. Telephone Performance Reporting Infrastructure
The organization's telephony system captured the raw data URAC requires — average speed of answer, abandonment rate, callback completion times. But the data was not being pulled, formatted, or reported in a way that produced the documented performance record URAC reviewers expect. Reports existed as periodic snapshots for internal management but lacked the consistent format, frequency, and documentation trail needed to demonstrate ongoing compliance with URAC's defined thresholds.
The nurse line's 24/7/365 coverage was operationally real — RNs were on shift every hour of every day — but coverage was documented only through payroll records, not through a formal scheduling attestation structure that URAC reviewers could readily verify.
3. Clinical Guideline Integration Gap
The organization licensed a nationally recognized clinical triage guideline system and had integrated it into the nurse line's call handling software. But two gaps existed: the guidelines had not been reviewed and updated on a documented schedule in the prior 18 months (a requirement under the Clinical module's standards), and there was no formal policy governing how nurses were trained on guideline updates when the guideline vendor issued new protocols. Nurses were in practice receiving updates via email — but the training and competency documentation trail was absent.
4. Consumer Protection Documentation
Both modules require documented grievance and appeals pathways, privacy notices, and non-discrimination policies accessible to consumers. The organization had all of these in place as a health plan regulatory requirement — but they existed in the health plan's member handbook, not as operational policies of the contact center. URAC reviews the contact center as a standalone operational entity. The existence of these protections in the health plan's broader member materials did not satisfy the contact center-level documentation requirement.
Additionally, the organization had added web chat as a communication channel 18 months prior. Its information protection policies had not been updated to address HIPAA-aligned protections for health information transmitted through the chat platform.
What IHS Did
Month 1–2: Gap Analysis and Remediation Architecture
IHS delivered a prioritized remediation roadmap within the first four weeks — identifying every gap, the standard it implicated, the documentation evidence required to close it, and the deadline by which it needed to be closed to meet the nine-month accreditation timeline. The roadmap sequenced remediation to address the structural policy architecture first, because every other documentation deliverable depended on that foundation being correct.
IHS also made the module selection and simultaneous application recommendation in writing at this stage. The organization had considered applying for the Clinical module only and adding NCP in a subsequent cycle. IHS recommended against this: the shared CORE standards documentation would be developed once either way, the additional NCP-specific requirements were addressable within the existing timeline, and the employer contract that triggered the engagement would be better satisfied by full dual-module accreditation than a single-module credential. The organization proceeded with simultaneous application.
Month 2–4: Policy Architecture Rebuild and Protocol Development
IHS provided templates and drafting support for a restructured policy framework: shared operational policies covering the full contact center, a clinical supplement governing nurse triage functions, and an administrative supplement governing non-clinical member services. This architecture allowed each URAC module to be supported by documentation specifically addressing its standards, without requiring the organization to maintain two entirely separate policy sets.
Specific deliverables in this phase included:
- Clinical triage protocol policy referencing the licensed guideline system with a defined annual review cycle and update training procedure
- RN scheduling attestation framework documenting 24/7/365 coverage through shift scheduling records, not payroll data alone
- Telephone performance reporting template — standardized monthly format capturing average speed of answer, abandonment rate, and callback completion by call type (clinical and non-clinical queues separately)
- Clinical-to-non-clinical escalation protocol — the existing informal handoff documented as a formal written procedure with defined triggers, response time standards, and supervision accountability
- Non-clinical staff clinical escalation training — documented curriculum confirming non-clinical staff knew when to transfer a call to the nurse line and how
- Contact center-level consumer protection policies — grievance and appeals pathway, privacy notice, and non-discrimination statement as standalone contact center documents, not cross-references to the health plan member handbook
- Information protection policy update — HIPAA-aligned protections extended explicitly to web chat as a covered communication channel
- Quality improvement program framework — measurable goals tied to telephone performance thresholds, clinical triage outcome tracking, and consumer complaint trends, with a documented quarterly review cycle
Month 4–5: Live Documentation Generation and Performance Data Accumulation
Policies and protocols are necessary but not sufficient — URAC reviewers look for evidence that the organization has been operating under its documented procedures, not just that the procedures exist. IHS worked with the contact center director to ensure that the new reporting templates, scheduling attestation procedures, guideline review cycle, and QI program were operational and generating audit trail evidence from the day policies were finalized. The organization needed approximately two months of live operational documentation before the application could credibly represent ongoing compliance.
During this phase, IHS also prepared the formal URAC application — organizing all documentation, completing the application narrative, and cross-referencing each submitted document to the applicable standard it was intended to satisfy.
Month 5–6: Application Submission and Desktop Review
The formal application was submitted with complete documentation for both modules. URAC's desktop review issued three Requests for Information — all in the Non-Clinical module. Two RFIs requested additional specificity in the consumer protection policies; one requested clarification on how web chat interactions were captured in the organization's performance metrics. IHS drafted all three RFI responses within URAC's response window, providing supplementary documentation that satisfied each reviewer question.
No RFIs were issued against the Clinical module documentation.
Month 7–8: On-Site Review and Committee Preparation
URAC conducted a virtual on-site review — staff interviews, operational observation of call handling workflows, and review of the technology systems supporting both modules. IHS prepared the contact center director, nurse line supervisor, and member services manager for reviewer interactions, briefing each on the standards most likely to generate interview questions and on how to present operational evidence clearly and concisely.
The virtual review generated no post-review RFIs.
Month 8–9: Committee Decision
URAC's accreditation committee issued dual-module accreditation — Clinical Contact Center and Non-Clinical Contact Center (NCP v6.0) — on the first submission cycle. The organization received its accreditation determination within the nine-month contract renewal window. The accreditation credential was submitted to the employer's benefits committee as part of the vendor qualification package, and the contract was renewed.
What Made the Difference
Policy Architecture Before Application
The single most consequential decision in the engagement was restructuring the policy framework before submitting the application — not after. Organizations that submit undifferentiated policies covering clinical and non-clinical operations under a single document set routinely receive multiple RFIs requiring policy revision and resubmission, adding weeks to the review cycle. The tiered architecture IHS recommended resolved this before it became a reviewer finding.
Simultaneous Module Application
Pursuing both modules simultaneously was the right call for this organization. The shared CORE standards documentation was developed once. The clinical-specific and administrative-specific supplements were additive — not duplicative. Total preparation effort was materially less than two sequential applications would have required, and the dual credential was more valuable to the employer contract than a single-module credential would have been.
Performance Data Infrastructure Built Before Application
URAC does not accept a policy that says "we monitor telephone performance" as evidence of compliance. Reviewers look for the data — formatted, documented, and covering a period of demonstrated compliance. The two months of live performance reporting generated before application submission gave reviewers a documented record to verify, not a promise to evaluate.
IHS RFI Response Precision
The three NCP module RFIs were procedural — requesting specificity and clarification, not identifying substantive gaps. RFI response is where many organizations lose time: vague or over-broad responses generate follow-up questions; responses that miss the reviewer's precise concern restart the clock. IHS drafted each RFI response to answer exactly what was asked, with documentary evidence directly attached. All three were accepted without follow-up.
Key Lessons for Health Contact Center Organizations
- The operational boundary between clinical and non-clinical functions must be documented before you apply — not asserted in the narrative. If your policies do not explicitly define which staff perform which functions under which protocols, both modules will face deficiency findings.
- Performance data must exist as a documented record, not as a system capability. URAC does not review your telephony system's reporting features. Reviewers examine the reports your organization has actually generated and retained.
- 24/7/365 RN coverage must be documentable from scheduling records, not payroll records. Payroll shows that nurses were employed. Scheduling records show that nurses were on shift at every hour. These are different documents and reviewers examine both.
- Clinical guidelines must be operationally integrated, not just licensed. A licensed guideline system that has not been reviewed, updated, or formally incorporated into staff training documentation does not satisfy URAC's clinical guideline standards.
- Consumer protection policies must exist as contact center operational documents. Cross-references to a health plan's member handbook are not acceptable substitutes for contact center-level policies. URAC reviews the accredited entity — the contact center — not the parent organization's broader materials.
- All communication channels in use must be covered by your information protection policies. Adding a digital channel without updating HIPAA-aligned policies creates a gap that URAC reviewers will find.
Preparing Your Contact Center for URAC Accreditation
The gap analysis is where accreditation is won or lost — and it is where every IHS engagement starts. If your organization operates a nurse advice line, health plan contact center, or mixed clinical-administrative operation and is evaluating URAC Health Contact Center Accreditation, contact IHS to discuss your situation before committing to a timeline or module selection.