×

HL7's new AMS is live!   We are working with Fonteva to resolve log in issues. My Account

Section 1e: Version 3 (V3)
Section 4: Rules and References

HL7 Version 3 Standard: Abstract Transport Specification, Release 1

DESCRIPTION

The Abstract Transport Specification provides models and mechanism for plug and play interoperability. Within that goal, the HL7 standard defines static and dynamic models for the information exchange that refer to the application layer (7th layer) in the OSI reference model. It also describes the functional characteristics of the messaging infrastructures that are of general interest to HL7 applications, such as reliable messaging, delivery assurances, addressing etc., and logical devices, such as gateways and bridges, which participate in the movement of composite messages between senders and receivers. It aims to define abstract messaging infrastructure concepts, rules and mechanisms for or in a HL7 compliant network.

This document describes a set of minimal requirements that a messaging infrastructure specification must meet to be considered for inclusion in the standard. It also lists features which are optional but of interest to the HL7 community. Functional characteristics include: mechanisms for reliable messaging; Destination delivery assurances, support for HL7 version 2 composite messages, message encryption and end-point authentication.

An updated errata package was posted in October 2019 and the details are in the download package.

ALTERNATIVE NAMES

HL7 Version 3 Standard: Abstract Transport Specification, Release 1 may also go by the following names or acronyms:

Reaffirmation of V3 Abstract Transport R1, "V3: Abstract Transport Specification, R1", Abstract Transport, ATS

TARGETS

  • Developers of Transport Standards

 

BENEFITS

  • Enables the development of interoperable transport standards
  • Supports :
    • Messaging infrastructure layer abstract services such as Addressing, Reliability, Attachments
    • Message exchange patterns.
    • Gateways, bridges, and other intermediary roles.
    • Differential transport of responses.
    • Message Fragmentation.

IMPLEMENTATIONS/CASE STUDIES

  • This specification is not directly implementable.

DEVELOPMENT BACKGROUND

The Abstract Transport Specification document has been published for the first time in MAY 2005 in the form of a Draft. Since then many of the concepts and statements have changed, mainly as the result of dispositions and findings at InM Working Group Meeting in San Antonio, MAY 2006.

The specifications introduced in this document are closely related to the HL7 MCCI domain, which mostly refers to the dynamics, constrains and definitions of commit/accept/application ack and naks that were ambiguously used in HL7 version 2 as well as in Release 1 of the MCCI domain.

RELATED DOCUMENTS

HL7 Version 3 Standard: Abstract Transport Specification, Release 1

(Download) (345 KB)

BALLOT TYPE

  • Normative

STATUS DATE

2018-05-31

RESPONSIBLE WORK GROUP

Infrastructure and Messaging

PRODUCT TYPE

  • Transport(ebxml, cd, mllp)

FAMILY

  • V3

CURRENT STATE

  • Stable

REALM

  • Universal