Fragmentation
Plan directories, hospital privilege files, CMS-facing attestations, and partner APIs often describe the same practitioner with different shapes and clocks—without a single reconciliation story.
The problem we are solving
Health care still runs on stale rosters, unscanned PDFs, and disconnected systems that cannot answer—at scale—who said this was true, when, and is it still true? Past national provider directory attempts never fixed that; they left the same operating model in place. The gap shows up as wrong network directories, slow credentialing, and privacy failures when sensitive columns move through unmanaged extracts nobody can defend. When the roster is wrong, the patient hits the wrong network—and the org owns the harm. This is not a phone-book problem; it is a lineage and control problem—and it still drives denials, stalled onboarding, and PHI risk.
Weak lineage
Issuance and operational signals (verification status, integrity alerts, attestations) rarely travel together—reviewers cannot tie cryptographic proof to day-to-day stewardship queues.
Interchange drag
Without an honest FHIR-shaped path to refresh directories, every buyer reinvents CSV dialects—while compliance still expects traceable, policy-bound payloads.
Our approach
NVPDR centers a golden registry record with explicit verification events, optional verifiable credential issuance metadata for high-risk attestations, and Integrity-style analytics layered on the same NPI keys your stewards already work in UI. Downstream, we surface Plan–Net style FHIR bundles as the interchange metaphor—not a certified endpoint claim in the demo, but a credible sketch buyers recognize.
Registry-first
VC-ready lineage
Integrity & attest paths
FHIR roster interchange
Persona-scoped UX
Interactive demo — guided flow
The live demonstration walks stakeholders through realistic personas in order—eight lenses on the same synthetic roster—so you can show interchange and governance in one sitting.
1 Provider
Submit NPI request scenarios, update your practice record, work Attestations, then file hospital privilege requests.
2 CMS Administrator
Work the verification queue, NPI issuance queue (legacy vs VC paths), Integrity alerts, and full registry table.
3 Hospital / Medical Staff
Review incoming privilege packets and approve or deny.
4 Health Plan Administrator
FHIR carries submit/download interchange; Integrity-style analytics carry verification posture & composite scores—use either or both in the same demo path.
5 Partner (API consumer)
Preview the same roster payload shape an exchange or partner system would pull.
6 Patient
Each patient persona opens a plan-scoped health-plan provider directory (in-network slice). Use keywords or specialty filters, then open a profile for verification and enrollment context.
7 Platform operations
Inspect where the DDL lives and review the demo audit log.
8 VA Community Care
Submit Community Care information to CMS, then download—via FHIR—the providers you want to add to your Community Care provider directory.
Try the full UI — synthetic data, in-browser only; not affiliated with CMS.
Open interactive demo →