HL7 Terminology
2.1.0 - Publication
This page is part of the HL7 Terminology (v2.1.0: Release) based on FHIR R4. The current version which supercedes this version is 5.2.0. For a full list of available versions, see the Directory of published versions
Summary
Defining URL: | http://terminology.hl7.org/ValueSet/endpoint-connection-type |
Version: | 0.2.0 |
Name: | EndpointConnectionType |
Title: | Endpoint Connection Type |
Status: | Draft as of 2020-02-24T12:41:39+11:00 (Standards Status: Trial Use) |
Definition: | 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 |
Copyright: | 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/ |
Maturity: | 2 |
OID: | 2.16.840.1.113883.4.642.3.498 (for OID based terminology systems) |
Source Resource: | XML / JSON / Turtle |
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 14 concepts
Expansion based on Endpoint Connection Type v0.1.0 (CodeSystem)
All codes from system http://terminology.hl7.org/CodeSystem/endpoint-connection-type
Code | Display | Definition |
ihe-xcpd | IHE XCPD | IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery |
ihe-xca | IHE XCA | IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access |
ihe-xdr | IHE XDR | IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange |
ihe-xds | IHE XDS | IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing |
ihe-iid | IHE IID | IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display |
dicom-wado-rs | DICOM WADO-RS | DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html |
dicom-qido-rs | DICOM QIDO-RS | DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html |
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 |
dicom-wado-uri | DICOM WADO-URI | DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html |
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. |
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. |
hl7v2-mllp | HL7 v2 MLLP | HL7v2 messages over an LLP TCP connection |
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 |
direct-project | Direct Project | Direct Project information - http://wiki.directproject.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 |
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) |
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 | Author | Custodian | Comment |
2020-10-14 | revise | Grahame Grieve | Vocabulary WG | Reset Version after migration to UTG |
2020-05-06 | revise | Ted Klein | Vocabulary WG | Migrated to the UTG maintenance environment and publishing tooling. |