Page tree
Skip to end of metadata
Go to start of metadata

The HL7 Messaging Implementation Guide describes how Orion Health solutions process the segments and fields in an HL7 message. This guide applies to solutions that are deployed with the following data processors:

  • Clinical Data Repository (CDR)
  • Data Engine with Clinical Data Spaces (CDS)
  • Both Clinical Data Repository (CDR) and Data Engine with Clinical Data Spaces

This guide is aimed at healthcare providers, participant technical staff, and EMR/EHR vendors connecting to Orion Health solutions. It is also aimed at internal implementation and onboarding teams. Readers are expected to have a thorough understanding of the Health Level Seven (HL7) version 2 standard.

Purpose of this Guide

This guide enumerates the supported message types in an HL7 message. It assumes that the structure and content of the inbound and outbound messages conform to version 2.5.1 of the HL7 Messaging Standard. It does not attempt to repeat the HL7 standard but identifies any differing or additional requirements for Orion Health implementations.

Some implementations may vary from this specification in their use of code sets and message structure requirements. Participants must consult the Orion Health project team to confirm any deviations from this specification.

Any references to Enterprise Master Patient Index (EMPI) in this guide are for the standard Orion Health solution implementation, which uses NextGate as the source of truth for patient information and patient demographic code sets.

Conventions used in this Guide

?   Tooltip
Point to the column heading to view the tooltip.


——>  Description
Some examples are accompanied by a description.
Segment IDSegment Name
Ignored segment
Segments in gray are ignored by downstream systems such as EMPI and Clinical Data Repository (CDR).
Field Number
Field Name
Ignored field
Fields in gray are ignored by downstream systems.


  • No labels