Release 4B

This page is part of the FHIR Specification (v4.3.0: R4B - STU). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3

4.4.1.275 Value Set http://hl7.org/fhir/ValueSet/endpoint-connection-type

Patient Administration Work Group Maturity Level: 2Trial Use Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/endpoint-connection-type
Version:4.3.0
Name:EndpointConnectionType
Title:Endpoint Connection Type
Definition:

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

Committee:Patient Administration Work Group
OID:2.16.840.1.113883.4.642.3.498 (for OID based terminology systems)
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/

Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.275.1 Content Logical Definition

 

4.4.1.275.2 Expansion

This expansion generated 28 May 2022

This value set contains 14 concepts

Expansion based on EndpointConnectionType v4.3.0 (CodeSystem)

All codes in this table are from the system http://terminology.hl7.org/CodeSystem/endpoint-connection-type

CodeDisplayDefinition
  ihe-xcpdIHE XCPDIHE Cross Community Patient Discovery Profile (XCPD) - http://wiki.ihe.net/index.php/Cross-Community_Patient_Discovery
  ihe-xcaIHE XCAIHE Cross Community Access Profile (XCA) - http://wiki.ihe.net/index.php/Cross-Community_Access
  ihe-xdrIHE XDRIHE Cross-Enterprise Document Reliable Exchange (XDR) - http://wiki.ihe.net/index.php/Cross-enterprise_Document_Reliable_Interchange
  ihe-xdsIHE XDSIHE Cross-Enterprise Document Sharing (XDS) - http://wiki.ihe.net/index.php/Cross-Enterprise_Document_Sharing
  ihe-iidIHE IIDIHE Invoke Image Display (IID) - http://wiki.ihe.net/index.php/Invoke_Image_Display
  dicom-wado-rsDICOM WADO-RSDICOMweb RESTful Image Retrieve - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.5.html
  dicom-qido-rsDICOM QIDO-RSDICOMweb RESTful Image query - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.7.html
  dicom-stow-rsDICOM STOW-RSDICOMweb RESTful image sending and storage - http://dicom.nema.org/medical/dicom/current/output/chtml/part18/sect_6.6.html
  dicom-wado-uriDICOM WADO-URIDICOMweb Image Retrieve - http://dicom.nema.org/dicom/2013/output/chtml/part18/sect_6.3.html
  hl7-fhir-restHL7 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-msgHL7 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-mllpHL7 v2 MLLPHL7v2 messages over an LLP TCP connection
  secure-emailSecure 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-projectDirect ProjectDirect Project information - http://wiki.directproject.org/

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA 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
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code