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-current 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

Plan-Net Mappings

Da Vinci PDex Plan-Net is a FHIR Implementation Guide that defines a set of FHIR profiles and mappings to support the exchange of health insurance plan information between payers and providers. The PlanNet IG is designed to facilitate the sharing of insurance plan details, including coverage information, provider networks, and other relevant data.

FHIR Mapping Language (StructureMap)

FHIR StructureMaps, encoded using FHIR Mapping Language (FML), are very detailed and include mappings at the element level, including mappings for extensions, CodeSystems, and ValueSets. The FML mappings are designed to be used for automated translation of data between Plan-Net and NDH.

Plan-Net does not derive from NDH, but rather creates similar Profiles, extensions, CodeSystems, and ValueSets. These look similar (semantically), but are not technically the same (syntactically). This means that the concepts recorded in Plan-Net are not the same concepts as those in NDH, although for example a code string is the same. The data recorded in a Plan-Net extension is not understood by an NDH Actor as the NDH Actor would not know about the extension defined in Plan-Net. Thus the FML mappings include mappings at the element and concept level (ConceptMap).

• Endpoint: Plan-Net to NDH
• HealthcareService: Plan-Net to NDH
• InsurancePlan: Plan-Net to NDH
• Location: Plan-Net to NDH
• Network: Plan-Net to NDH
• Organization: Plan-Net to NDH
• OrganizationAffiliation: Plan-Net to NDH
• Practitioner: Plan-Net to NDH
• PractitionerRole: Plan-Net to NDH

Profile mapping

Profile mappings do not have the fidelity to support translating CodeSystems, ValueSets, or extensions, so the Profile mappings are at the semantic level only. The same syntactic detail problem exists, but is not addressed by a Profile mapping.

• Endpoint: NDH to Plan-Net
• Group: NDH to Plan-Net – none
• HealthcareService: NDH to Plan-Net
• InsurancePlan: NDH to Plan-Net
• Location: NDH to Plan-Net
• Network: NDH to Plan-Net
• Organization: NDH to Plan-Net
• OrganizationAffiliation: NDH to Plan-Net
• Practitioner: NDH to Plan-Net
• PractitionerRole: NDH to Plan-Net
• Verification: NDH to Plan-Net – none