What this domain asks
Risk that one practitioner, group, supplier, location, owner, or affiliation is split across records or incorrectly merged, causing credentialing, enrollment, roster, directory, monitoring, and payment systems to act on the wrong identity.
The domain should retain its own evidence, decision owner, materiality criteria, exception path, and consequence even when it shares organization identity, workflow, or technology with adjacent domains. Aggregation can support oversight; it should not erase the evidence behind different risks or operating outcomes.
Buyer questions
- Which identifier is authoritative for each provider, organization, location, program, and date?
- How are Type 1 and Type 2 NPIs, TINs, reassignment relationships, taxonomies, and service locations represented?
- What confidence and review path applies when names, addresses, dates, or ownership records disagree?
- Can merges and splits be reversed without losing history or propagating a false identity downstream?
- How quickly do NPPES, PECOS, payer, licensing, and internal changes reach each consuming system?
- Does the platform clearly state that NPI enumeration is not credentialing or enrollment?
Mapped workflows
Provider Onboarding And Profile Management
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for provider onboarding and profile management within this domain.
Provider Roster Reconciliation
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for provider roster reconciliation within this domain.
Provider Directory Data Management
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for provider directory data management within this domain.
NPI, Taxonomy, And Identity Resolution
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for NPI, taxonomy, and identity resolution within this domain.
Provider Affiliations And Locations
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for provider affiliations and locations within this domain.
APIs, Integration, And Downstream Data Distribution
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for APIs, integration, and downstream data distribution within this domain.
Audit Trail, Source Provenance, And Committee Evidence
A demonstration should show the trigger, source, accountable role, decision, exception, evidence, and downstream handoff for audit trail, source provenance, and committee evidence within this domain.
Authority context
CMS PECOS
PECOS is CMS's online system for Medicare provider and supplier enrollment, revalidation, changes of information, reassignment, ownership and managing-control records, and related enrollment administration. It is not a credentialing or privileging system.
NPPES and NPI
NPPES enumerates healthcare providers and maintains NPI-associated public data. CMS explicitly states that NPI issuance does not ensure or validate licensure or credentialing and does not ensure Medicare enrollment.
CMS Medicare FFS Public Provider Enrollment data
The dataset publishes selected Medicare fee-for-service provider and supplier enrollment characteristics for public analysis, subject to its data dictionary, suppression, update cadence, and program scope.
Relevant operating models
- Payer Provider-Data And Network Lifecycle Platform
- Provider Roster And Directory Data Platform
- Provider Reference Data And Identity Intelligence
- API-First Verification And Provider Operations Infrastructure
Evidence boundary
Credentialing Current provides organizational research, not legal, accreditation, billing, enrollment, privileging, credentialing, sanctions, or exclusion determinations. Accountable organizations must review controlling sources and the facts of each provider, program, and jurisdiction. A provider's documented capability can identify a research candidate but cannot establish buyer-specific adequacy for this domain.