HL7 Terminology (THO)
6.1.0 - Continuous Process Integration (ci build) International flag

HL7 Terminology (THO), published by HL7 International - Vocabulary Work Group. This guide is not an authorized publication; it is the continuous build for version 6.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/UTG/ and changes regularly. See the Directory of published versions

ValueSet: Endpoint Connection Type

Official URL: http://terminology.hl7.org/ValueSet/endpoint-connection-type Version: 1.0.1
Active as of 2024-04-24 Maturity Level: 2 Responsible: Health Level Seven International Computable Name: EndpointConnectionType
Other Identifiers: OID:2.16.840.1.113883.4.642.3.498

Copyright/Legal: This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

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)

Logical Definition (CLD)

Generated Narrative: ValueSet endpoint-connection-type

Last updated: 2024-04-24 00:00:00+0000

Profile: Shareable ValueSet

 

Expansion

Generated Narrative: ValueSet

Last updated: 2024-04-24 00:00:00+0000

Profile: Shareable ValueSet

Expansion based on codesystem Endpoint Connection Type v2.1.1 (CodeSystem)

This value set contains 15 concepts

CodeSystemDisplayInactiveDefinitionstatus
  dicom-wado-rshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM WADO-RS

DICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html

  dicom-qido-rshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM QIDO-RS

DICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html

  dicom-stow-rshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM STOW-RS

DICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html

  dicom-wado-urihttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDICOM WADO-URI

DICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html

  hl7-fhir-resthttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 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-msghttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 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-mllphttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 v2 MLLP

HL7v2 messages over an LLP TCP connection

  secure-emailhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeSecure 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-projecthttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDirect Project

Direct Project information - http://wiki.directproject.org/

  cds-hooks-servicehttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeCDS 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

  ihe-xcpdhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XCPDinactive

IHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery

deprecated
  ihe-xcahttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XCAinactive

IHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access

deprecated
  ihe-xdrhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XDRinactive

IHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange

deprecated
  ihe-xdshttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE XDSinactive

IHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing

deprecated
  ihe-iidhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeIHE IIDinactive

IHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display

deprecated

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

DateActionCustodianAuthorComment
2023-11-14reviseTSMGMarc DuteauAdd standard copyright and contact to internal content; up-476
2020-10-14reviseVocabulary WGGrahame GrieveReset Version after migration to UTG
2020-05-06reviseVocabulary WGTed KleinMigrated to the UTG maintenance environment and publishing tooling.