National Directory of Healthcare Providers & Services (NDH) Implementation Guide, published by HL7 International / Patient Administration. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-us-ndh/ and changes regularly. See the Directory of published versions
Page standards status: Informative |
Inspired by the Validated Healthcare Directory (VhDir) Technical Guidance, the objective of this document is to provide implementers with key attestation, validation, and verification guidance for developing robust and interoperable solutions without being prescriptive.
The recommendations aim to guide implementers of the National Directory of Healthcare Providers & Services (NDH) in creating solutions that meet business needs, operational constraints, and regulatory requirements, while still allowing flexibility.
Attestation involves authorized entities submitting information for inclusion in a healthcare directory. The guide focuses on using a FHIR API for managing attestation, but implementers can choose accordingly based on their context (laws, regulations, policies). Traditional methods like paper-based forms are outside this guide's scope.
Attestation Scenarios include:
Authorized entities have specific rights for resource attestation:
FHIR Resource | Practitioner | Organization | Payer | HIE/HIO |
---|---|---|---|---|
CareTeam | Attest | Create by one or more Organizations | ||
Endpoint | Attest | Attest/Create | Attest/Create | Create |
HealthcareService | Create | Attest/Create | ||
InsurancePlan | Create | |||
Location | Attest | Create | ||
Network | Attest | Attest/Create | Create | |
Organization | Create | |||
OrganizationAffiliation | Create by one or more Organizations | |||
Practitioner | Create | |||
PractitionerRole | Attest/Create | Attest/Create | Attest/Create |
Policies before Accepting Attested Data:
A typical attestation workflow includes accessing the NDH client, reviewing and submitting information, data conversion, transmission, and server validation.
Validation ensures data integrity and compliance with FHIR specifications. Verification confirms data truthfulness against primary sources, which may offer APIs or manual methods.
Verification types might include:
VerificationResult Resource documents the verification process, primary sources, data sources, and outcomes.
Handling Verification Failures involves flagging incomplete resources and maintaining logs of verification attempts.
Provenance tracks attestation and verification details, while security and privacy policies ensure adherence to standards like NIST guidelines.
By streamlining these processes, the document aids implementers in efficiently building and maintaining a comprehensive directory.