Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32). 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.572 ValueSet http://hl7.org/fhir/ValueSet/endpoint-connection-type

Patient Administration icon Work Group Maturity Level: 1Draft Use Context: Country: World, Not Intended for Production use, Not Intended for Production use
Official URL: http://hl7.org/fhir/ValueSet/endpoint-connection-type Version: 5.0.0-snapshot3
draft as of 2022-12-14 Computable Name: EndpointConnectionType
Flags: Experimental OID: 2.16.840.1.113883.4.642.3.498

This value set is used in the following places:

4.4.1.572.1 Definition

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

4.4.1.572.2 Content Logical Definition

 

4.4.1.572.3 Expansion

This expansion generated 14 Dec 2022

This value set contains 10 concepts

Expansion based on Endpoint Connection Type v1.0.0 (CodeSystem) icon

CodeSystemDisplayDefinition
  dicom-wado-rs iconhttp://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-rs iconhttp://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-rs iconhttp://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-uri iconhttp://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-rest iconhttp://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-msg iconhttp://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-mllp iconhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeHL7 v2 MLLP

HL7v2 messages over an LLP TCP connection

  secure-email iconhttp://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-project iconhttp://terminology.hl7.org/CodeSystem/endpoint-connection-typeDirect Project

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

  cds-hooks-service iconhttp://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

 

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