HL7 Terminology (THO)
5.3.0 - Publication
This page is part of the HL7 Terminology (v5.3.0: Release) based on FHIR R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
Official URL: http://terminology.hl7.org/ValueSet/endpoint-connection-type | Version: 0.2.0 | |||
Draft as of 2020-02-24 | Maturity Level: 2 | Responsible: HL7 Patient Administration | Computable Name: EndpointConnectionType | |
Other Identifiers: id: urn:oid:2.16.840.1.113883.4.642.3.498 | ||||
Copyright/Legal: 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/ |
This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.
References
This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)
http://terminology.hl7.org/CodeSystem/endpoint-connection-type
This value set contains 10 concepts
Expansion based on codesystem Endpoint Connection Type v1.0.0 (CodeSystem)
Code | System | Display | Definition |
dicom-wado-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM WADO-RS | DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html |
dicom-qido-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM QIDO-RS | DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html |
dicom-stow-rs | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM STOW-RS | DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html |
dicom-wado-uri | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | DICOM WADO-URI | DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html |
hl7-fhir-rest | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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. |
hl7-fhir-msg | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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. |
hl7v2-mllp | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | HL7 v2 MLLP | HL7v2 messages over an LLP TCP connection |
secure-email | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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 |
direct-project | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | Direct Project | Direct Project information - http://wiki.directproject.org/ |
cds-hooks-service | http://terminology.hl7.org/CodeSystem/endpoint-connection-type | 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 |
Explanation of the columns that may appear on this page:
Level | A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies |
System | 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) |
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 |
History
Date | Action | Custodian | Author | Comment |
2020-10-14 | revise | Vocabulary WG | Grahame Grieve | Reset Version after migration to UTG |
2020-05-06 | revise | Vocabulary WG | Ted Klein | Migrated to the UTG maintenance environment and publishing tooling. |