Certification Matters is a patient lookup—not professional PSV

The same credential can have different authorized channels

The direct answer in ABMS's Certification Matters guidance is a use boundary. The public service lets patients and families check a known doctor's ABMS board-certification status. The site separately says its displayed patient-search information is not valid or authorized for use by professional organizations. A credentialing workflow therefore cannot treat any visible result as purpose-neutral evidence.

A defensible record should identify the subject, Member Board, specialty or subspecialty, certification and maintenance status, relevant dates, source product or channel, retrieval time, organization and authorized user, permitted purpose, official report identifier, and retained evidence. A screenshot from a patient lookup and a professional primary-source-verification response may refer to the same doctor but are not operationally equivalent.

Professional PSV needs the professional record

ABMS directs professional organizations that need primary-source verification and official certification reports to ABMS Solutions. Its guidance notes that professional use commonly requires certification status and dates, and that ABMS makes primary-source data available for credentialing uses. The professional workflow should preserve exactly which product and report supplied the evidence rather than labelling the profile only 'ABMS checked.'

A representative demonstration should start with a practitioner identity, request the authorized professional record, reconcile name and other identifiers, capture specialty and certification dates and status, route discrepancies, record reviewer action, and retain the source evidence. The system should distinguish no result, ambiguous match, delayed update, certified, no longer certified, and other reported states without converting any one state into appointment or privileging.

Freshness and identity limits stay visible

Certification Matters says Member Board data are updated periodically and may not reflect very recent changes. Its guidance also notes that reported location can be out of date and gives reasons a doctor may not appear in a patient search, including recent certification, privacy choices, scope outside ABMS Member Boards, or search inputs. An absent or stale-looking public result is therefore an investigation trigger, not a final adverse conclusion.

Credentialing systems should preserve search criteria, candidate matches, source timestamps, reporting delays, discrepancy communications, and later corrected evidence. Matching needs governed identity review, especially when names, locations, or specialty descriptions differ. The accountable reviewer should be able to see what the source established at the time and why a later record changed the disposition.

Board certification remains one credential

ABMS board certification concerns knowledge and skills in a medical specialty or subspecialty under a Member Board's requirements. It is distinct from state licensure and does not itself grant a hospital appointment, clinical privilege, payer enrollment, network participation, employment, or authority to perform a procedure at a facility. Those decisions rely on other sources, criteria, committees, and current facts.

This article does not verify a physician, interpret a certification status, establish PSV sufficiency, or determine credentialing, appointment, privileging, enrollment, participation, licensing, employment, competence, or patient-care decisions. Organizations need current ABMS professional evidence where appropriate plus other required primary sources and qualified credentialing, medical-staff, payer, clinical, compliance, privacy, and legal judgment.

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.