# NDH Profiles - National Directory of Healthcare Providers & Services (NDH) Implementation Guide v2.0.0-current

## NDH Profiles

The following presents the list of Directory NDH profiles. Each profile defines the minimum mandatory elements, extensions, and terminology requirements that are required to be present [Must Support](conformance.md#must-support)). Within the profile, there is a simple summary of requirements and guidance, the usage and scope of the profile, and the boundaries and relationship with other profiles.

[NDH Endpoint Profile](StructureDefinition-ndh-Endpoint.md)

This profile enables NDH to publish trusted, implementation-ready technical endpoints so directory consumers can reliably discover, evaluate, and connect to electronic exchange services including APIs and messaging; it adds endpoint-focused extensions for trust, registration, access control, testing, and environment context, and applies ValueSet bindings that standardize connection type, payload type, and MIME-type semantics.

[NDH Group](StructureDefinition-ndh-Group.md)

This profile enables NDH to represent multidisciplinary provider groups as directory entities so consumers can discover team-based programs and services and understand the practitioner and practitioner-role membership that supports coordinated care delivery; it adds extensions for location and endpoint references, verification, artifact description, and effective period, and uses ValueSet-constrained group coding to standardize program/service classification.

[NDH HealthcareService Profile](StructureDefinition-ndh-HealthcareService.md)

This profile enables NDH to represent healthcare and community services in a consistent, searchable way so consumers can identify what is offered, where and how it is delivered, and who can access it; it adds extensions for ratings, new-patient intake, delivery method, funding, required documents, network linkage, and verification, and strengthens interoperability with ValueSet-constrained categories, types, specialties, provision conditions, eligibility codes, and programs.

[NDH InsurancePlan Profile](StructureDefinition-ndh-InsurancePlan.md)

This profile enables NDH to publish normalized insurance product and plan details, including coverage, network relationships, and administration, so users can compare options and accurately match plans to participating providers and service areas; it adds verification and identifier-status extensions and uses ValueSet bindings to normalize product type, coverage type, benefit type, and plan type classifications.

[NDH Location Profile](StructureDefinition-ndh-Location.md)

This profile enables NDH to define service locations with consistent operational and geographic details so consumers can accurately discover where care is delivered, understand access characteristics, and link locations to organizations, services, and endpoints; it adds extensions for geospatial boundaries, accessibility, new-patient status, and verification, and applies ValueSet constraints for status, mode, location type, address use and type, state, and days-of-week availability.

[NDH Network Profile](StructureDefinition-ndh-Network.md)

This profile enables NDH to represent payer and provider network structures as computable directory data so users can determine network participation, geographic coverage, and organizational relationships that affect access and coverage decisions; it adds extensions for coverage-area references, organization period, and verification, and uses ValueSet bindings to standardize network type and key identifier semantics.

[NDH Organization Profile](StructureDefinition-ndh-Organization.md)

This profile enables NDH to publish authoritative organizational identities, attributes, and contact channels so directory consumers can verify entities, understand what they offer, and connect organizations to plans, networks, services, and exchange endpoints; it adds extensions for ratings, funding, accepted payments, organization description, insurance-plan linkage, CMS-alignment indicators, verification, logos, and alias metadata, and applies ValueSet constraints for organization type and state/address semantics.

[NDH OrganizationAffiliation Profile](StructureDefinition-ndh-OrganizationAffiliation.md)

This profile enables NDH to describe formal affiliations between organizations in a computable way so consumers can understand delegated services, shared networks, service locations, and endpoint relationships that drive referral and access pathways; it adds extensions for verification, and branding, and uses ValueSet bindings for affiliation role and specialty coding to improve consistent role interpretation across implementations.

[NDH Practitioner Profile](StructureDefinition-ndh-Practitioner.md)

This profile enables NDH to represent healthcare practitioners with verifiable identity and qualification details so consumers can discover, trust, and select individual professionals participating in care delivery and directory exchange; it adds extensions for endpoint references, accessibility, ratings, CMS-alignment indicators, verification, and communication proficiency, and applies ValueSet constraints and additional bindings for qualification, taxonomy, credential, and address-state semantics.

[NDH PractitionerRole](StructureDefinition-ndh-PractitionerRole.md)

This profile enables NDH to express how practitioners function within organizations, locations, services, and networks so users can understand role-specific participation and route patients to the right provider context for care and coverage; it adds extensions for ratings, new-patient intake, network references, and verification, and uses ValueSet bindings for practitioner-role and specialty coding to support consistent downstream matching and routing.

[NDH Verification](StructureDefinition-ndh-Verification.md)

This profile enables NDH to capture verification provenance, status, and timing for directory data so consumers can assess trust, recency, and validation method when making decisions based on published provider, organization, and role information; it adds CMS-focused verification extensions and applies ValueSet bindings for validation type, process, primary-source type, and communication method to normalize attestation workflows.