This is the Continuous Integration Build of FHIR (will be incorrect/inconsistent at times).
See the Directory of published versions 
Responsible Owner: Patient Administration Work Group |
Informative | Use Context: Country: World |
Official URL: http://hl7.org/fhir/ValueSet/endpoint-connection-type
|
Version: 6.0.0-snapshot1 | |||
| active as of 2026-11-17 | Computable Name: EndpointConnectionType | |||
| Flags: | OID: 2.16.840.1.113883.4.642.3.498 | |||
This value set is used in the following places:
This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.
Generated Narrative: ValueSet endpoint-connection-type
Last updated: 2026-11-17T03:14:18.602Z
This value set includes codes based on the following rules:
http://terminology.hl7.org/CodeSystem/endpoint-connection-type
version 📦2.1.1http://terminology.hl7.org/CodeSystem/v3-NullFlavor
version 📦4.0.0
| Code | Display | Definition |
UNK ![]() |
unknown | **Description:**A proper value is applicable, but not known. **Usage Notes**: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless: 1. Those properties themselves directly translate to a semantic of "unknown". (E.g. a local code sent as a translation that conveys 'unknown') 2. Those properties further qualify the nature of what is unknown. (E.g. specifying a use code of "H" and a URL prefix of "tel:" to convey that it is the home phone number that is unknown.) |
This expansion generated 17 Nov 2026
ValueSet
Expansion performed internally based on:
This value set contains 16 concepts
| System | Code | Display | Definition | status ![]() |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
dicom-wado-rs ![]() |
DICOM WADO-RS | DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
dicom-qido-rs ![]() |
DICOM QIDO-RS | DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
dicom-stow-rs ![]() |
DICOM STOW-RS | DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
dicom-wado-uri ![]() |
DICOM WADO-URI | DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
hl7-fhir-rest ![]() |
HL7 FHIR | Interact with the server interface using FHIR's RESTful interface. For details on its version/capabilities you should connect the value in Endpoint.address and retrieve the FHIR CapabilityStatement. | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
hl7-fhir-msg ![]() |
HL7 FHIR Messaging | Use the servers FHIR Messaging interface. Details can be found on the messaging.html page in the FHIR Specification. The FHIR server's base address is specified in the Endpoint.address property. | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
hl7v2-mllp ![]() |
HL7 v2 MLLP | HL7v2 messages over an LLP TCP connection | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
secure-email ![]() |
Secure email | Email delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
direct-project ![]() |
Direct Project | Direct Project information - http://wiki.directproject.org/ | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
cds-hooks-service ![]() |
CDS Hooks Service | A CDS Hooks Service connection. The address will be the base URL of the service as described in the CDS specification https://cds-hooks.hl7.org | |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
ihe-xcpd ![]() |
IHE XCPD | IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery | deprecated |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
ihe-xca ![]() |
IHE XCA | IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access | deprecated |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
ihe-xdr ![]() |
IHE XDR | IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange | deprecated |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
ihe-xds ![]() |
IHE XDS | IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing | deprecated |
http://terminology.hl7.org/CodeSystem/endpoint-connection-type |
ihe-iid ![]() |
IHE IID | IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display | deprecated |
http://terminology.hl7.org/CodeSystem/v3-NullFlavor |
UNK ![]() |
unknown | **Description:**A proper value is applicable, but not known. Usage Notes: This means the actual value is not known. If the only thing that is unknown is how to properly express the value in the necessary constraints (value set, datatype, etc.), then the OTH or UNC flavor should be used. No properties should be included for a datatype with this property unless:
|
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
| Lvl | A few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information |
| Source | The source of the definition of the code (when the value set draws in codes defined elsewhere) |
| Code | The code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract') |
| Display | The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application |
| Definition | An explanation of the meaning of the concept |
| Comments | Additional notes about how to use the code |