Release 4B Snapshot #1

This page is part of the FHIR Specification v4.3.0-snapshot1: R4B Snapshot to support the Jan 2022 Connectathon. About the R4B version of FHIR. The current officially released version is 4.3.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3

4.3.14.235 Code System http://terminology.hl7.org/CodeSystem/endpoint-connection-type

Patient Administration Work Group Maturity Level: 0Informative Use Context: Any

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/endpoint-connection-type
Version:4.3.0-snapshot1
Name:EndpointConnectionType
Title:
Definition:

This is an example codesystem 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.1.1140 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

  • ValueSet: Endpoint Connection Type (This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.)
  • ValueSet: Endpoint Connection Type (This is an example value set defined by the FHIR project, that could be used to represent possible connection type profile values.)

4.3.14.235.1 Content

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

CodeDisplayDefinition
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/

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. 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