Skip to content

Glossary

Definitions of the terms used in the HL7v2 learning pages.

Terms are grouped by first letter. Each entry links to the page that covers it.

A

Abstract message syntax

The notation that the HL7v2 standard uses to define the segments of each message, in order. A segment code on its own is required, [ ] marks an optional segment or group, { } marks one that can repeat, and uppercase names identify groups: [{ NK1 }] is an optional, repeating next-of-kin segment. See Optionality and Group.

Acknowledgment (ACK)

The HL7v2 message that a destination returns to confirm receipt of a message and report the results of validating and processing it. The outcome is carried in the MSA segment. See Acknowledgments.

Acknowledgment code

The value in MSA-1: AA accept, AE error, AR reject, and the commit-level CA, CE, CR. See Acknowledgment codes.

ADT

Admit, Discharge, Transfer. The message type that carries patient demographics and encounter changes. See Message types.

Application acknowledgment

In enhanced mode, the acknowledgment that reports the outcome of processing, with the code AA, AE, or AR. See Enhanced mode.

Assigning authority

The organization or system that issued an identifier, carried as an HD inside a CX or EI. See Data types.

At-least-once delivery

Message delivery in which the source resends a message until the destination acknowledges it, so the message is not lost but can arrive more than once. A destination detects duplicates by control ID. See Delivery confirmation.

At-most-once delivery

Message delivery in which the source sends each message once and never retries, so the message is never duplicated but can be lost. See Delivery confirmation.

B

Batch

A set of messages wrapped in BHS and BTS segments for transfer as a unit, typically as a file. See Batch.

C

Coding system

A code list from which a coded value is taken, such as LOINC, SNOMED CT, or an HL7 table, identified in coded fields by its identifier from table 0396. See Coding systems.

Commit acknowledgment

In enhanced mode, the acknowledgment that confirms the destination has stored a message, with the code CA, CE, or CR. See Enhanced mode.

Component

A part of a field, separated from its neighbors by ^. Which components a field has is determined by its data type. See Component.

Conformance

The property of a system whose messages satisfy a message profile: it sends only messages that the profile permits and accepts every message that it permits. See Conformance.

Constrainable profile

A message profile that resolves some of the standard's options and leaves others open, to be resolved by the profiles derived from it. National implementation guides usually contain constrainable profiles. See Profile levels.

Control ID

The unique identifier of a message, in MSH-10. Echoed in MSA-2 of the acknowledgment so the two can be matched, which makes it the message's correlation identifier. A retransmitted message keeps its original control ID. See Acknowledgments.

CWE, CNE

The composite coded data types. CWE (coded with exceptions) allows values outside the bound table; CNE (coded, no exceptions) does not. See Data types.

D

Data type

The definition of what a field or component holds: a primitive such as ST or DTM, or a composite such as XPN or CX. See Data types.

Delimiter

One of the characters that separate the levels of a message: \r between segments, | between fields, ^ between components, ~ between repetitions, & between sub-components, and \ to escape them. See Delimiters.

Destination

The system that receives and processes a message. The message header identifies it in MSH-5 (receiving application). See Message flow.

E

Encoding characters

The four (or five) characters in MSH-2 that declare the component, repetition, escape, sub-component, and optionally truncation delimiters. See Delimiters.

Enhanced mode

The acknowledgment mode in which a destination sends a commit acknowledgment on receipt and an application acknowledgment after processing. Selected by MSH-15 and MSH-16. See Enhanced mode.

ERR segment

The segment that reports one error in an acknowledgment: location, standard error code, and severity. See ERR segment.

Escape sequence

A short code between escape characters, such as \T\, that stands in for a delimiter inside a value. See Escape sequences.

F

Field

A data element within a segment, identified by its position: PID-5 is the fifth field of PID. See Field.

I

Implementable profile

A message profile that leaves no option open and describes one interface completely. Chapter 2B of the standard calls it an implementation profile. See Profile levels.

Implementation guide

A published document that collects the message profiles for a use case, such as laboratory reporting or immunization registries. See Implementation guides.

Interface

The connection over which two specific systems exchange HL7v2 messages. Its profile specifies the messages it carries. See Conformance.

Interface engine

Middleware that receives messages from the systems in an organization and routes, transforms, validates, and forwards them. See Interface engines.

Interoperability

The ability of systems built by different vendors to exchange data and interpret it in the same way. HL7v2 provides a shared message format for this purpose, and a profile fixes the options that the standard leaves open for each interface. See Introduction to HL7v2.

L

LOINC

Logical Observation Identifiers Names and Codes. The external coding system for laboratory tests and clinical observations, identified as LN in table 0396. See Tables.

M

Message structure

The third component of MSH-9, naming the segment layout a message follows: ADT_A01, ORU_R01. Several trigger events can share one structure. See Message structure.

Message profile

A specification that narrows the standard's definition of one message for one context of use: usage, cardinality, length, and vocabulary for every element. Identified in MSH-21. See Conformance.

Message type

The category of information that a message carries, which groups related trigger events: ADT, ORU, SIU. Identified in MSH-9.1. See Message types.

MLLP

Minimal Lower Layer Protocol. The framing protocol that carries HL7v2 messages over TCP, consisting of a start byte, the message, and a two-byte end sequence. See MLLP.

MSA segment

The Message Acknowledgment segment: acknowledgment code, the original message's control ID, and optional text. See MSA segment.

MSH segment

The Message Header: the first segment of every message, carrying delimiters, sending and receiving applications, timestamp, message type, control ID, processing ID, and version. See MSH numbering.

N

Null value

The literal "" in a field, which instructs the destination to delete the stored value, as distinct from an empty field, which provides no information. See Null value.

O

OBX segment

The Observation/Result segment: one observation, with its identifier, value, units, reference range, and status. The value's data type is declared by OBX-2. See Variable types.

Original mode

The default acknowledgment mode: one acknowledgment, sent after processing. See Original mode.

P

Profile

Short for message profile.

R

Repetition

One of several values in a field that allows more than one, separated by ~. See Repetition.

S

Segment

A sequence of related fields, identified by a three-character code and terminated by a carriage return: MSH, PID, OBX. See Segment.

Segment group

A set of segments that belong together and may repeat as a unit, such as an OBR and its OBX segments. Groups exist only in the standard's definition of the message, written in abstract message syntax, and not in the transmitted message. See Group.

Self-describing format

A format whose messages name their values, as JSON and XML documents do, so that a reader can see what each value is from the message itself. HL7v2 is not self-describing: a message contains only values and delimiters, and the meaning of each value comes from the standard's definitions and the interface's profile. See Data types.

Source

The system that generates and sends a message. The message header identifies it in MSH-3 (sending application). See Message flow.

Store and forward

The method by which an interface engine stores each message it receives and keeps it until every destination has acknowledged it, so that a message for an unavailable destination waits in a queue instead of being lost. See Persistence.

Sub-component

A part of a component, separated by &. The deepest level of the hierarchy. See Sub-components.

T

Table

A list of the codes that a coded field can contain, with the meaning of each. A table is defined by HL7, by each site (a user-defined table), or by another organization. See Table types.

Table 0396

The HL7 table that identifies coding systems, so that a composite coded value can identify the coding system of its code. See Coding systems.

Trigger event

The real-world event that causes a message to be sent, identified by its code in MSH-9.2: A01 admit, R01 result, S12 new appointment. See Trigger events.

Truncation character

The optional fifth encoding character, #, introduced in version 2.7 to mark a value that the source truncated. See Versioning.

U

Usage

The profile constraint that specifies whether an element must be present: R, RE, O, C, or X. See Usage.

User-defined table

A table whose codes each site defines, usually starting from values that HL7 suggests, such as table 0001 for administrative sex. See User-defined tables.

V

Version

The release of the standard that a message declares, in MSH-12. See Versioning.

X

X12

An electronic data interchange standard that businesses use to exchange documents such as orders and invoices, and that US healthcare uses for claims and payments. HL7v2 belongs to the same lineage of segment-and-delimiter formats. See HL7v2.

Z

Z-segment

A segment whose identifier begins with Z, a letter that the standard reserves for local definitions. Its fields are defined by a site or vendor and documented in the interface's message profile. See Z-segments.