| # | | Name | Source | Ver | Description |
| 1 | | Argonaut Provider Directory Endpoint | fhir.argonaut.pd#1.0.0 | R3 | |
| 2 | | AU PD Secure Messaging Endpoint | hl7.fhir.au.pd#current | R4 | |
| 3 | | BeCapabilitiesEndpoint | hl7.fhir.be.capabilities#current | R4 | |
| 4 | | Endpoint | hl7.fhir.nl.zorgviewer#current | R3 | The minimal Endpoint for the Zorgviewer |
| 5 | | FHIR REST API Endpunkt | fhir.qpath4ms#current | R4 | Profil eines Endpunkts zu einer FHIR REST API, z.B. Repository für Patientenpfade |
| 6 | | Imaging Study Endpoint | ihe.rad.imr#current | R4 | IHE Radiology profile on Endpoint for Study |
| 7 | | Location to the PACS server | arkhn.fhir.uv.osiris#current | R4 | System communication to the PACS server |
| 8 | | mCSD Endpoint | medcom.sor.mcsd#current | R4 | A profile on the mCSD Endpoint.
An Organization may be reachable through electronic Endpoint(s).
An Endpoint may be a FHIR server, an IHE web services actor, or some other
mechanism. If an Organization does not have an Endpoint, it may still be
reachable via an Endpoint at its parent Organization or an affiliated Organization.
Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource. |
| 9 | | mCSD Endpoint for Document Sharing | medcom.sor.mcsd#current | R4 | A profile on the mCSD Endpoint for Document Sharing environments.
Given that in FHIR R4 the .connnectionType is 1..1, each type of endpoint will be indicated with an independent Endpoint resource. Thus a XCA Responding Gateway will need two Endpoint instances to express Query vs Retrieve.
Open-Issues:
1. That payloadType and payloadMimeType are either empty to indicate that the endpoint is not constrained; or fully populated.
2. That payloadType and PayloadMimeType for XCA/XDS/MHD Query and XCA/XDS/MHD Retrieve would be the same thus replicating the capability at both endpoints.
3. It did not seem right that Query be indicated with a mimeType of ebRegistry as that is not helpful to the use-case.
4. should the homeCommunityId be mandated here, should those behind it be here, should this be empty?
5. would a Proxy service that is supporting OrgAff be a good example of NOT putting a homeCommunityId in the endpoint.identifier? |
| 10 | | MIPHREndpoint | hl7.fhir.mi.phr#current | R4 | |
| 11 | | mTLS Endpoint | hl7.fhir.us.davinci-pdex#current | R4 | The mTLS Endpoint is used to assist payers in defining their mTLS endpoints and discovering other Payer's mTLS endpoints |
| 12 | | NatDir Endpoint | hl7.fhir.us.directory-attestation#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 13 | | National Directory Endpoint | hl7.fhir.us.directory-exchange#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 14 | | National Directory Endpoint Qry Exchange Endpoint | hl7.fhir.us.directory-query#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 15 | | NDH Base Endpoint Profile | hl7.fhir.us.ndh#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 16 | | NDH Exchange Endpoint Profile | hl7.fhir.us.ndh#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 17 | | no-basis-Endpoint | hl7.fhir.no.basis#2.1.2 | R4 | Basisprofil for Norwegian Endpoint information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. The profile adds Norwegian specific identification of Endpoing. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case.
Resource profile for definition of electronic endpoints used by healthcare organizations to communicate using different protocols. The norwegian profile use-case is to represent endpoints for electronic communication. Fallback solutions using mail or fax has to be indexed in the norwegian master index for healthcare organizations and are not described using this profile. |
| 18 | | Payer Provider Network Query Endpoint Profile | hl7.fhir.us.ndh#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 19 | | Plan-Net Endpoint | hl7.fhir.us.davinci-pdex-plan-net#current | R4 | The technical details of an endpoint that can be used for electronic services, such as a portal or FHIR REST services, messaging or operations, or DIRECT messaging. |
| 20 | | US Public Health Endpoint | hl7.fhir.us.ph-library#current | R4 | This is the Endpoint Resource profile for the IG used to specify receivers addresses |
| 21 | | US Public Health Endpoint | hl7.fhir.us.ecr#current | R4 | This is the Endpoint Resource profile for the IG used to specify receivers addresses |
| 22 | | US Public Health Endpoint | hl7.fhir.us.ph-library#current | R4 | This Endpoint profile indicates where the report is to be sent. |
| 23 | | USPH Endpoint | hl7.fhir.us.medmorph#current | R4 | This is the Endpoint Resource profile for the IG used to specify receivers addresses |
| 24 | | VhDir Endpoint | hl7.fhir.uv.vhdir#current | R4 | Defines the basic constraints and extensions on the Endpoint resource for use in a Validated Healthcare Directory |
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 |
| Endpoint |
D |
D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
D |
|
|
D |
D |
|
D |
|
| Endpoint.payloadMimeType |
|
|
|
|
F |
|
|
|
|
|
B M |
|
|
|
B M |
|
D B M |
|
|
|
|
|
|
|
| Endpoint.payloadType |
C B M |
D B M |
B M |
|
B M |
C |
|
|
D |
C |
C B M |
|
|
C B M |
C B M |
|
S D B M (3) |
|
C B M |
|
|
|
|
|
| Endpoint.payloadType.text |
|
|
|
|
|
|
|
|
|
C F |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payloadType.coding |
|
|
|
|
|
B M |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payloadType.extension |
|
|
S C (2) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.meta |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.meta.profile |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
| Endpoint.meta.lastUpdated |
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
C |
|
|
|
C |
|
|
|
|
|
| Endpoint.meta.source |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.implicitRules |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.language |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.text |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.contained |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.extension |
|
S C (4) |
S C (2) |
|
|
|
|
S C (2) |
S C |
|
S C (12) |
|
S (2) |
S C (9) |
S C (15) |
S C (11) |
|
S |
S C (2) |
|
|
|
|
S C D (5) |
| Endpoint.modifierExtension |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.identifier |
|
S D (2) |
|
|
|
|
|
|
D |
C |
|
|
|
|
|
|
D |
|
|
|
|
|
|
|
| Endpoint.identifier.period |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.identifier.type |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.identifier.use |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.identifier.assigner |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.identifier.extension |
|
|
|
|
|
|
|
|
|
|
S C |
|
|
|
S C |
S C (2) |
|
|
|
|
|
|
|
S C (2) |
| Endpoint.identifier.value |
|
C |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.identifier.system |
|
C F D |
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.status |
C B M |
D |
|
|
|
|
|
D |
|
F |
F |
|
|
F |
F |
|
|
|
F |
C |
C |
|
C |
|
| Endpoint.connectionType |
C B M |
D B M |
B M |
|
F |
B M |
|
|
B M |
|
B M |
|
|
B M |
B M |
|
D B M |
|
B M |
C |
C |
|
C |
|
| Endpoint.connectionType.code |
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.connectionType.system |
|
|
|
|
|
|
|
|
|
C F |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.name |
C |
|
|
|
C |
|
C D |
|
C |
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.description |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.environmentType |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.managingOrganization |
C |
C D |
|
|
C |
|
|
C D |
|
C |
|
|
|
|
|
|
D |
|
|
|
|
|
|
|
| Endpoint.managingOrganization.reference |
|
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.managingOrganization.display |
|
C D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.contact |
|
D |
|
|
C |
|
|
D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
| Endpoint.contact.period |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.contact.rank |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.contact.use |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.contact.value |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
| Endpoint.contact.system |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
C |
| Endpoint.contact.extension |
|
|
|
|
|
|
|
|
|
|
S C |
|
|
|
S C (2) |
S (2) |
|
|
|
|
|
|
|
S C (3) |
| Endpoint.period |
|
|
|
|
|
|
|
D |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payload |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payload.extension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payload.modifierExtension |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payload.type |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.payload.mimeType |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Endpoint.address |
C |
D |
|
|
|
|
|
|
D |
|
|
|
|
|
|
|
D |
|
|
C |
C |
|
C |
|
| Endpoint.header |
|
|
|
|
|
|
|
|
C |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|