Endpoint (20)

#NameSourceVerDescription
1Argonaut Provider Directory Endpointfhir.argonaut.pd#1.0.0R3
2AU PD Secure Messaging Endpointhl7.fhir.au.pd#currentR4
3BeCapabilitiesEndpointhl7.fhir.be.capabilities#currentR4
4Endpointhl7.fhir.nl.zorgviewer#currentR3The minimal Endpoint for the Zorgviewer
5FHIR REST API Endpunktfhir.qpath4ms#currentR4Profil eines Endpunkts zu einer FHIR REST API, z.B. Repository für Patientenpfade
6MIPHREndpointhl7.fhir.mi.phr#currentR4
7mTLS Endpointhl7.fhir.us.davinci-pdex#currentR4The mTLS Endpoint is used to assist payers in defining their mTLS endpoints and discovering other Payer's mTLS endpoints
8NatDir Endpointhl7.fhir.us.directory-attestation#currentR4The 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.
9National Directory Endpointhl7.fhir.us.directory-exchange#currentR4The 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.
10National Directory Endpoint Qry Exchange Endpointhl7.fhir.us.directory-query#currentR4The 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.
11NDH Base Endpoint Profilehl7.fhir.us.ndh#currentR4The 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.
12NDH Exchange Endpoint Profilehl7.fhir.us.ndh#currentR4The 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.
13no-basis-Endpointhl7.fhir.no.basis#2.1.2R4Basisprofil 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.
14Payer Provider Network Query Endpoint Profilehl7.fhir.us.ndh#currentR4The 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.
15Plan-Net Endpointhl7.fhir.us.davinci-pdex-plan-net#currentR4The 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.
16US Public Health Endpointhl7.fhir.us.ph-library#currentR4This is the Endpoint Resource profile for the IG used to specify receivers addresses
17US Public Health Endpointhl7.fhir.us.ecr#currentR4This is the Endpoint Resource profile for the IG used to specify receivers addresses
18US Public Health Endpointhl7.fhir.us.ph-library#currentR4This Endpoint profile indicates where the report is to be sent.
19USPH Endpointhl7.fhir.us.medmorph#currentR4This is the Endpoint Resource profile for the IG used to specify receivers addresses
20VhDir Endpointhl7.fhir.uv.vhdir#currentR4Defines 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
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 C B M C B M C B M S D B M (3) C B M
Endpoint.payloadType.text C F
Endpoint.payloadType.extension S C (2)
Endpoint.meta
Endpoint.meta.profile C
Endpoint.meta.lastUpdated C C C
Endpoint.meta.source
Endpoint.implicitRules
Endpoint.language
Endpoint.text
Endpoint.contained
Endpoint.extension S C (4) S C (2) S C (12) S (2) S C (9) S C (15) S C (11) S S C (2) S C D (5)
Endpoint.modifierExtension
Endpoint.identifier S D (2) 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 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 D B M B M C C C
Endpoint.connectionType.code C
Endpoint.connectionType.system C F
Endpoint.name C C C
Endpoint.description
Endpoint.environmentType
Endpoint.managingOrganization C C D C C D
Endpoint.managingOrganization.reference C
Endpoint.managingOrganization.display C D
Endpoint.contact D C 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
Endpoint.payload
Endpoint.payload.extension
Endpoint.payload.modifierExtension
Endpoint.payload.type
Endpoint.payload.mimeType
Endpoint.address C D D C C C
Endpoint.header
S: There is slicing defined in the element(s)
C: There is cardinality erstrictions defined in the element(s)
I: There is invariants defined in the element(s)
F: There is a fixed or pattern value defined in the element(s)
D: There is document provided in the element(s)
B: There is terminology bindings defined in the element(s)
M: At least one of the element(s) has must-support = true
(N): The number of elements if > 1

Produced 08 Sep 2023