Release 5 Preview #1

This page is part of the FHIR Specification (v4.2.0: R5 Preview #1). 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.3.14.81 Code System http://terminology.hl7.org/CodeSystem/message-transport

FHIR Infrastructure Work Group Maturity Level: NNormative (from v4.0.0) Use Context: Any
This page has been approved as part of an ANSI standard. See the Conformance Package for further details.

This is a code system defined by the FHIR project.

Summary

Defining URL:http://terminology.hl7.org/CodeSystem/message-transport
Version:4.2.0
Name:MessageTransport
Title:MessageTransport
Definition:

The protocol used for message transport.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.1.1080 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

4.3.14.81.1 Content

4.3.14.81.2 MessageTransport

The protocol used for message transport.

This code system http://terminology.hl7.org/CodeSystem/message-transport defines the following codes:

CodeDisplayDefinition
http HTTPThe application sends or receives messages using HTTP POST (may be over http: or https:).
ftp FTPThe application sends or receives messages using File Transfer Protocol.
mllp MLLPThe application sends or receives messages using HL7's Minimal Lower Level Protocol.

 

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