Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions icon . Page versions: R5 R4B R4 R3

4.4.1.527 4.4.1.278 ValueSet http://hl7.org/fhir/ValueSet/endpoint-connection-type

  Maturity Level : 1
Responsible Owner: Patient Administration icon Work Group Draft Informative Use Context : Country: World, Not Intended for Production use World
Official URL : http://hl7.org/fhir/ValueSet/endpoint-connection-type Version : 5.0.0 6.0.0-ballot3
draft active as of 2023-03-26 2025-12-17 Computable Name : EndpointConnectionType
Flags : Experimental OID : 2.16.840.1.113883.4.642.3.498

This value set is used in the following places:

4.4.1.527.1 4.4.1.278.1 Definition

This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.

4.4.1.527.2 4.4.1.278.2 Content Logical Definition

Generated Narrative: ValueSet endpoint-connection-type

Last updated: 2025-12-17T09:50:17.012Z

 

4.4.1.527.3 4.4.1.278.3 Expansion

This expansion generated 26 Mar 2023 17 Dec 2025

This value set contains 10 concepts

ValueSet

Expansion performed internally based on codesystem Endpoint Connection Type v1.0.0 v2.1.1 (CodeSystem) icon

This value set contains 15 concepts

http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type http://terminology.hl7.org/CodeSystem/endpoint-connection-type
System Code System Display Display Definition Definition status icon
http://terminology.hl7.org/CodeSystem/endpoint-connection-type    dicom-wado-rs icon 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 icon 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 icon 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 icon 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 icon 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 icon 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 icon HL7 v2 MLLP HL7v2 messages over an LLP TCP connection
http://terminology.hl7.org/CodeSystem/endpoint-connection-type    secure-email icon 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 icon Direct Project Direct Project information - http://wiki.directproject.org/
http://terminology.hl7.org/CodeSystem/endpoint-connection-type    cds-hooks-service icon 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 icon 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 icon 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 icon 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 icon 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 icon IHE IID IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display deprecated

 

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