HL7 Terminology
2.0.19 - UTG Continuous Process Integration (ci build)

HL7 Terminology, published by HL7 International - Vocabulary Work Group. This is not an authorized publication; it is the continuous build for version 2.0.19). This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

CodeSystem: Endpoint Connection Type


Defining URL:http://terminology.hl7.org/CodeSystem/endpoint-connection-type
Title:Endpoint Connection Type
Status:Draft as of 2021-02-24T19:08:34+00:00 (Standards Status: Trial Use)

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

Publisher:HL7 Patient Administration
Committee:Patient Administration

Some content from IHE® Copyright © 2015 IHE International, Inc. This content is from the IHE Technical Frameworks and Supplements, available for free download and use at http://www.ihe.net/Technical_Frameworks/

Content:Complete: All the concepts defined by the code system are included in the code system resource
OID:2.16.840.1.113883.4.642.1.1140 (for OID based terminology systems)
Value Set:http://terminology.hl7.org/ValueSet/endpoint-connection-type ( is the value set for all codes in this code system)
Source Resource:XML / JSON / Turtle

This Code system is referenced in the content logical definition of the following value sets:

This code system http://terminology.hl7.org/CodeSystem/endpoint-connection-type defines the following codes:

ihe-xcpd IHE XCPDIHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery
ihe-xca IHE XCAIHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access
ihe-xdr IHE XDRIHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange
ihe-xds IHE XDSIHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing
ihe-iid IHE IIDIHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display
dicom-wado-rs DICOM WADO-RSDICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html
dicom-qido-rs DICOM QIDO-RSDICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html
dicom-stow-rs DICOM STOW-RSDICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html
dicom-wado-uri DICOM WADO-URIDICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html
hl7-fhir-rest HL7 FHIRInteract 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.
hl7-fhir-msg HL7 FHIR MessagingUse 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.
hl7v2-mllp HL7 v2 MLLPHL7v2 messages over an LLP TCP connection
secure-email Secure emailEmail delivery using a digital certificate to encrypt the content using the public key, receiver must have the private key to decrypt the content
direct-project Direct ProjectDirect Project information - http://wiki.directproject.org/


2020-10-14reviseGrahame GrieveVocabulary WGReset Version after migration to UTG
2020-05-06reviseTed KleinVocabulary WGMigrated to the UTG maintenance environment and publishing tooling.