CREDENTIALINGCURRENT

Follow the record. Separate the decisions. Keep the workforce ready.

Coverage desk

Primary-Source Verification

Source-backed reporting and analysis connected to the companies, capabilities, authorities, and operating domains it affects.

Nursys results need board-participation and update context

Nursys describes itself as a repository of licensure and disciplinary data submitted by participating boards of nursing, and it displays when a board updated its information. A returned result can support verification, but an absent or stale result cannot be treated as proof that no license or discipline record exists.

MedTrainer license checks need credential-age rules

MedTrainer presents automated license verification alongside provider data, credentialing, enrollment, reports, and managed services. Automation can refresh evidence, but each credential type still needs a source, matching method, verification timestamp, acceptable age, change trigger, exception path, reviewer, and separate downstream appointment or enrollment decision.

MD-Staff automation needs verification and reviewer lineage

MD-Staff presents automation for primary-source verification requests and responses alongside credentialing, privileging, enrollment, application, and committee workflows. Automation can organize evidence, but it cannot turn a returned source record into an appointment, privilege, enrollment, or other accountable decision without identity, scope, exception, and reviewer lineage.

CMS Preclusion List is a program payment control—not a credentialing verdict

CMS ties the Preclusion List to payment for specified Medicare Advantage items and services and Part D prescriptions. A match can have serious program consequences, but it does not replace licensure, enrollment, credentialing, appointment, or privileging decisions.

EPIC verifies credential authenticity—not a physician qualification decision

Intealth's ECFMG division verifies specified medical education, training, and registration or licensure credentials directly with issuing institutions. The resulting report supports an evaluating organization; it does not appoint, privilege, license, enroll, or hire the physician.

OIG profile-correction files are not exclusion-verification evidence

HHS-OIG publishes profile corrections beside the monthly exclusion data, but the agency expressly says not to use that file to verify exclusions. The full database, monthly additions and reinstatements, identity matching, and online verification serve different operating purposes.

Certification Matters is a patient lookup—not professional PSV

ABMS separates its free patient-facing board-certification search from products used by professional organizations for primary-source verification. Credentialing teams need the authorized professional record, certification dates, identity match, and current evidence.

PECOS enrollment is not a credentialing or privileging decision

CMS uses PECOS for Medicare enrollment and related maintenance; provider organizations still need separate evidence and authority for credentialing, privileging, and payer participation decisions.

Medicaid federal database checks need entity scope

42 CFR 455.436 requires Medicaid agencies to check defined providers and associated people against federal databases at specified points. Systems must preserve who, which source, when, and what followed.

CMS makes telemedicine credentialing reliance conditional

42 CFR 482.22 permits a hospital to rely on certain distant-site credentialing and privileging decisions for telemedicine only through a defined written-agreement path. Reliance is governed, not automatic.

NPDB separates delegated credentialing from query agency

The NPDB guidebook treats delegated credentialing and query agency as different roles. Systems must bind each query, result, user, and decision to the right entity.