# NDH Endpoint Access Control Mechanism - National Directory of Healthcare Providers & Services (NDH) Implementation Guide v2.0.0-current

* [**Table of Contents**](toc.md)
* [**Artifacts Summary**](artifacts.md)
* **NDH Endpoint Access Control Mechanism**

## Extension: NDH Endpoint Access Control Mechanism 

| | | |
| :--- | :--- | :--- |
| *Official URL*:http://hl7.org/fhir/us/ndh/StructureDefinition/base-ext-endpointAccessControlMechanism | *Version*:2.0.0-current | |
| * Standards status: *[Trial-use](http://hl7.org/fhir/R4/versions.html#std-process) | [Maturity Level](http://hl7.org/fhir/versions.html#maturity): 4 | *Computable Name*:EndpointAccessControlMechanism |

Endpoint access control mechanisms protect and manage access to healthcare endpoints, ensuring secure data exchange between systems. They standardize methods to secure endpoints, ensuring interoperability and security.
 In certain use cases requiring system scalability and flexibility, different profiles may be utilized based on the chosen access control mechanism. For example, the Unified Data Access Profile (UDAP) uses JWT access tokens.

**Context of Use**

**Usage info**

**Usages:**

* Use this Extension: [NDH Endpoint Profile](StructureDefinition-ndh-Endpoint.md)
* Examples for this Extension: [Endpoint for Acme of CT Portal](Endpoint-AcmeOfCTPortalEndpoint.md) and [Endpoint for Coordination of Care](Endpoint-CoordinationOfCareEndpoint.md)

You can also check for [usages in the FHIR IG Statistics](https://packages2.fhir.org/xig/hl7.fhir.us.ndh|current/StructureDefinition/base-ext-endpointAccessControlMechanism)

### Formal Views of Extension Content

 [Description of Profiles, Differentials, Snapshots, and how the XML and JSON presentations work](http://build.fhir.org/ig/FHIR/ig-guidance/readingIgs.html#structure-definitions). 

 

Other representations of profile: [CSV](StructureDefinition-base-ext-endpointAccessControlMechanism.csv), [Excel](StructureDefinition-base-ext-endpointAccessControlMechanism.xlsx), [Schematron](StructureDefinition-base-ext-endpointAccessControlMechanism.sch) 

#### Terminology Bindings

#### Constraints



## Resource Content

```json
{
  "resourceType" : "StructureDefinition",
  "id" : "base-ext-endpointAccessControlMechanism",
  "extension" : [{
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
    "valueCode" : "pa"
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
    "valueInteger" : 4,
    "_valueInteger" : {
      "extension" : [{
        "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
        "valueCanonical" : "http://hl7.org/fhir/us/ndh/ImplementationGuide/hl7.fhir.us.ndh"
      }]
    }
  },
  {
    "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
    "valueCode" : "trial-use",
    "_valueCode" : {
      "extension" : [{
        "url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
        "valueCanonical" : "http://hl7.org/fhir/us/ndh/ImplementationGuide/hl7.fhir.us.ndh"
      }]
    }
  }],
  "url" : "http://hl7.org/fhir/us/ndh/StructureDefinition/base-ext-endpointAccessControlMechanism",
  "version" : "2.0.0-current",
  "name" : "EndpointAccessControlMechanism",
  "title" : "NDH Endpoint Access Control Mechanism",
  "status" : "active",
  "date" : "2026-03-23T21:58:05+00:00",
  "publisher" : "HL7 International / Patient Administration",
  "contact" : [{
    "name" : "HL7 International / Patient Administration",
    "telecom" : [{
      "system" : "url",
      "value" : "http://www.hl7.org/Special/committees/pafm"
    },
    {
      "system" : "email",
      "value" : "pafm@lists.hl7.org"
    }]
  }],
  "description" : "Endpoint access control mechanisms protect and manage access to healthcare endpoints, ensuring secure data exchange between systems. \nThey standardize methods to secure endpoints, ensuring interoperability and security.  \nIn certain use cases requiring system scalability and flexibility, different profiles may be utilized based on the chosen access control mechanism. For example, \nthe Unified Data Access Profile (UDAP) uses JWT access tokens.",
  "jurisdiction" : [{
    "coding" : [{
      "system" : "urn:iso:std:iso:3166",
      "code" : "US",
      "display" : "United States of America"
    }]
  }],
  "fhirVersion" : "4.0.1",
  "mapping" : [{
    "identity" : "rim",
    "uri" : "http://hl7.org/v3",
    "name" : "RIM Mapping"
  }],
  "kind" : "complex-type",
  "abstract" : false,
  "context" : [{
    "type" : "element",
    "expression" : "Endpoint"
  }],
  "type" : "Extension",
  "baseDefinition" : "http://hl7.org/fhir/StructureDefinition/Extension",
  "derivation" : "constraint",
  "differential" : {
    "element" : [{
      "id" : "Extension",
      "path" : "Extension",
      "short" : "NDH Endpoint Access Control Mechanism",
      "definition" : "Endpoint access control mechanisms protect and manage access to healthcare endpoints, ensuring secure data exchange between systems. \nThey standardize methods to secure endpoints, ensuring interoperability and security.  \nIn certain use cases requiring system scalability and flexibility, different profiles may be utilized based on the chosen access control mechanism. For example, \nthe Unified Data Access Profile (UDAP) uses JWT access tokens."
    },
    {
      "id" : "Extension.extension",
      "path" : "Extension.extension",
      "max" : "0"
    },
    {
      "id" : "Extension.url",
      "path" : "Extension.url",
      "fixedUri" : "http://hl7.org/fhir/us/ndh/StructureDefinition/base-ext-endpointAccessControlMechanism"
    },
    {
      "id" : "Extension.value[x]",
      "path" : "Extension.value[x]",
      "min" : 1,
      "type" : [{
        "code" : "CodeableConcept"
      }],
      "binding" : {
        "strength" : "extensible",
        "valueSet" : "http://hl7.org/fhir/us/ndh/ValueSet/EndpointAccessControlMechanismVS"
      }
    }]
  }
}

```
