NCQA's 2026 credentialing standards cycle raises a familiar buyer question: which program, scope, and survey period are you actually evaluating?

Start with the program identity

A buyer should identify the exact NCQA program, product year, survey cycle, option, organization, legal entity, and delegated scope before translating requirements into software criteria. A health plan, CVO, delegated credentialing entity, and technology vendor may all appear in one workflow while holding different responsibilities and evidence states.

Public NCQA program pages help establish the available pathway and terminology, but the licensed standards control the detailed criteria. Editorial summaries and vendor checklists should never substitute for authorized access and qualified interpretation. Procurement documents should cite the buyer's selected program and version rather than a generic NCQA compliant phrase.

Accreditation is not a transferable product attribute

An accredited or certified organization may use several products, services, and manual controls. Its status does not automatically transfer to those products, and a provider serving accredited customers does not inherit their status. Conversely, a product can support a conforming workflow without itself being an accreditation subject.

Profiles therefore need exact language: issuing body, organization, program, scope, effective period, and official source. If any element is missing, the status should remain unverified rather than being rounded up to a stronger marketing conclusion.

What to test in delegation and CVO workflows

Ask for a representative file from intake through primary-source verification, discrepancy handling, decision or recommendation, reporting, monitoring, and audit. Show which work the CVO performs, which decisions the plan retains, how subdelegation is controlled, and what evidence the plan receives. Then inspect a failed source response, potential sanction match, and late recredentialing case.

The technology should preserve standards version, customer policy, source method, reviewer, exception, service level, corrective action, and historical evidence. A completed task list is insufficient if the buyer cannot reconstruct how the organization met its own program responsibilities.

How the publication reports status

Credentialing Current will link to NCQA's official program materials and distinguish current official status from an organization's marketing statement. We will not reproduce licensed criteria, infer status from a logo, or describe a product as accredited.

Comparisons will ask whether a provider supports the buyer's program-specific evidence and delegation model. They will not score organizations on an invented universal compliance scale.

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.