Primary source verification

Editorial approval scope: The team checked current source fidelity, scope boundaries, dates, arithmetic, reader usefulness, practical workflow, and general-information limitations.

Verification starts with the origin

The CMS Medicare Managed Care Manual, Chapter 6 defines a primary source as an organization or entity with legal responsibility for originating a document and ensuring the accuracy of its information. It also recognizes certain industry verification sources identified by nationally recognized accrediting organizations.

That makes primary source verification, or PSV, an evidence process. The verifier confirms a defined fact with an accepted originator or route and preserves the result. A credentialing committee, payer, program, or other authorized decision-maker then evaluates the complete file under its rules.

A copied license, provider attestation, résumé, directory entry, NPI record, or prior payer approval may help identify what to verify. Each becomes PSV only when the governing source accepts that route for the credential in question.

Build a source map by credential

Start with the requirement, then identify its accepted source. A practical source map can include:

The Joint Commission FAQ defines PSV for its cited Disease Specific Care standard more narrowly. It addresses licensure, certification, or registration required to practice and accepts secure electronic communication or documented telephone verification from the licensing board or officially designated agency. Use that guidance only within its stated accreditation scope.

Payer and accreditation rules control the method

The CMS Medicare Managed Care Manual requires primary-source verification of specified credentials for Medicare Advantage credentialing, including current licensure, the highest applicable education or training, and claimed board certification. The manual also explains when recognized or secondary sources may be accepted. Those are Medicare Advantage requirements, not a universal ABA credentialing checklist.

NCQA's CVO FAQ says credentials verification can occur through the primary source, a recognized source, or a contracted agent of the primary source. CVO certification evaluates a verification organization's operations. It does not make every output acceptable to every payer or transfer the final credentialing decision.

Current DataSpring credentialing materials describe a Primary Source Verification product using data from licensing boards, schools, government registries, and other authoritative sources. That is a vendor description. A practice or payer should verify the product's supported credentials, source provenance, freshness, contracts, validation, exceptions, evidence access, and acceptance under its controlling standard.

Preserve a usable verification record

For every PSV event, record:

• person or organization and the exact credential or fact checked
• requirement, payer, product, standard, contract, and version
• primary, recognized, or contracted-agent source and why it is accepted
• query method, date, time, credential identifier, and relevant validity dates
• result, limitations, restrictions, sanctions, or unresolved mismatch
• verifier, reviewer, artifact or reference number, and next recheck
• escalation, correction, adverse-information, and decision status

Use role-limited access for sensitive credentialing evidence. Preserve the source response and provenance needed for audit without copying more personal information than the workflow requires.

Currentness belongs in the design. A verification can accurately describe a credential on the query date and still be stale for a later decision. Set freshness and recheck triggers from the current payer, accreditation, licensing, contract, and policy sources.

Resolve discrepancies before the decision

Names, credential numbers, status dates, taxonomy, locations, and discipline information can disagree across sources. Keep both values, identify their origins, and route the conflict to the credential owner or authorized decision-maker. Software may flag the mismatch and hold the file. It should not select the favorable value or clear adverse information without review.

The CMS NPI fact sheet provides a useful boundary: an NPI identifies a health care provider, while NPI issuance does not ensure licensure or credentialing. A clean NPPES match cannot repair an expired license or missing certification verification.

A fictional PSV cohort

A fictional ABA practice locks 20 practitioner files due for credentialing review. Seventeen contain accepted, current PSV for every credential required at that stage. PSV completeness is 17 of 20, or 85%. The three incomplete files stay open with the missing credential, source, owner, age, and next action.

Among the 17 complete files, 13 have resolved every discrepancy and contain the other application, screening, and review evidence required for a decision. Decision readiness is 13 of 17, or 76.5%. Across the original cohort, it is 13 of 20, or 65%.

The remaining seven files include three with missing PSV and four with conflicts or other open requirements. The practice reports those reasons separately. It does not call 17 verified files credentialed or treat the 13 decision-ready files as approved.

Measure verification and decisions separately

Useful measures include:

• files with all required PSV complete divided by all files due for review
• individual credential checks completed within the accepted freshness window divided by checks due
• discrepancies resolved by target divided by discrepancies due for resolution
• decision-ready files divided by all files in the locked cohort

Define the file cohort, required credentials, accepted sources, freshness rule, cutoff, exclusion reasons, and decision state before reporting. Segment recurring gaps by credential, source, payer, workflow version, and responsible role. Verification completeness, decision approval, payer enrollment, roster acceptance, claim results, and payment remain separate outcomes.