URAC CVO standards do not require mental-health history questions

Find the real requirement before collecting sensitive history

The direct answer is to place every credentialing-application question in a requirement register with the current source, effective date, purpose, owner and disposition. URAC's official CVO page explicitly says its accreditation standards have never required mental-health or substance-use-disorder history questions. That narrow statement rules out treating URAC CVO accreditation as the assumed reason for such an intake item; it does not interpret state license rules, hospital bylaws, payer contracts, professional duties, disability protections, or any separate process. A local requirement must be researched and read in its actual current text before a form is kept or changed.

For each question record which individual and organization it applies to, exact wording, material purpose, source citation and version, mandatory versus optional status, permitted response, who can see it, whether the information is actually necessary for the credentialing decision, confidentiality, retention and change approval. Separate verification of qualifications and current professional standing from personal health history. Avoid turning an unsupported legacy question into a universal gate, and avoid treating removal from one form as a waiver of an independently required process.

Review copied forms and delegated handoffs

CVOs may collect or transmit application data for a health plan, hospital or other client. An old client template, third-party portal or imported PDF can retain a sensitive field without naming who required it. Map the request from applicant through CVO, primary-source verification, reviewer, credentialing committee, client and archive; distinguish data the CVO verifies from a field supplied by a client, inferred from past templates, or demanded by another authority. A 'required' flag in software is a configuration, not a citation to an accreditation standard.

When a question is revised, retain form version, accountable client and legal review, affected applicant groups, communication, privacy notice, access and retention change, effective date, migrating incomplete applications, and whether historic responses are removed or lawfully retained. Do not quietly expose historic sensitive answers to downstream recipients just because a form no longer asks for new answers. Keep clinical or occupational-health assessments, if legitimately required, in the designated protected process instead of importing raw history into a broadly accessible credentialing profile.

Pilot a requirement-by-question review

Test one CVO serving two clients, one state-specific licensing application, a hospital form from an older edition, and a portal template labelled 'accreditation-required'. Ask each authority for the precise current source and the question's purpose. If a field has no applicable requirement, decide through the proper governance process whether to retire it, narrow it or route it elsewhere; do not claim legal prohibition from the URAC page alone. If a separate current source requires a question, define exact scope, privacy protection and date rather than projecting it onto all providers.

Check whether a clinician can submit the correct current application, whether old response fields leak into data exports or case views, how delegated CVO staff are trained, how exceptions are explained, and what evidence is available at survey or audit. URAC's page says accreditation is for three years but it does not establish that any particular organization is accredited or that every questionnaire reflects current standards. A buyer should request the exact program, organization, dates and licensed standards relevant to its own process.

Evidence boundary and distinct decision

The URAC CVO page is direct evidence for its own program statement about the absence of a mental-health-history requirement, the program's described scope and eligibility wording. It is not a source of a customer's state-law obligations, all accreditation bodies' standards, an individual's health status, fitness to practice, or a credentialing outcome. No provider health information was viewed, and the article makes no suggestion that seeking care is evidence of unfitness.

This question differs from the prior NCQA program/survey-cycle article, NPDB delegated query authority, MedTrainer license-age review, and Quest directory-data-versus-credentialing-status story. The unit here is one potentially sensitive form question: whether its claimed accreditation requirement actually exists and whether its collection, access and downstream uses are authorized. That is a privacy and application-design decision, not a provider approval or a general accreditation-status comparison.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Credentialing Current will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.