Scribd
Upload
104 views17 pages

HL7 V2 Standards Overview

The document provides an overview of HL7 Version 2 messages, including a brief history of HL7 and Version 2, the components and structure of Version 2 messages, and the role of profiles in improving interoperability. It describes how Version 2 messages are composed of segments and fields, and examples of common message types like ACK. It also discusses coded element data types, constraints imposed by profiles, and additional HL7 resources.

Uploaded by

mexbrain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
104 views17 pages

HL7 V2 Standards Overview

The document provides an overview of HL7 Version 2 messages, including a brief history of HL7 and Version 2, the components and structure of Version 2 messages, and the role of profiles in improving interoperability. It describes how Version 2 messages are composed of segments and fields, and examples of common message types like ACK. It also discusses coded element data types, constraints imposed by profiles, and additional HL7 resources.

Uploaded by

mexbrain
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 17

HL7 Version 2 Messages

An Introduction

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Presentation Outline
• Brief History of HL7 and Version 2 (V2)
• V2 message business process
• Message components and structure
• Vocabulary Constraints
• Role of Profiles in Improving Interoperability Success

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Brief History of HL7
• Founded as an international standards development
organization in 1987 to promote communication
between hospital data systems
• Stated a goal of creating a platform independent method
of moving data between different systems
• Developed grammar for messaging and standardized
vocabulary

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


HL7: The Primary Standard for Communicating Health Data
• ANSI Standard for clinical interoperability
• HL7 standards are widely adopted and continue to
evolve
• Meaningful Use has identified a number of HL7
standards to support sharing data between systems
• HL7 website: http://www.hl7.org/

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


HL7 Versions
• HL7 version 2.x messaging
• HL7 version 3 messaging
• HL7 Clinical Document Architecture (CDA)
• HL7 Fast Healthcare Interoperability Resources (FHIR)

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


HL7 Version 2 History
• HL7 Version 2 first published in 1989
• Each version of Version 2 builds on the previous
versions with a better data model and stronger
vocabulary standards
• The Normative Version specifications have evolved
• The current Normative Version is Version 2.7
• New versions are intended to allow backward
compatibility

v. 2.x v. 2.8
v. 2.7 Publish
Previous
Normative soon
versions

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


HL7 i
Messaging Business Process s criti
but n cal
enou ot
trigge

gh by
r

itself.

HL7
1) Prepare 2) Parse data HL7
data for received
transport

3) Process
Transport
HL7 Data
Layer
5) Parse
Sender Receiver
Response
HL7
4) Prepare
6) Process Response
Response

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Version 2.x: Messages
• Each message has a job and one or more
triggers
– Send vaccination history (VXU)
– Send demographic update or transfer patient (ADT)
– Send acknowledgement (ACK)
– Request immunization history (QBP)
– Return immunization history (RSP)
• The “job” and structure are identified by the
name and the trigger.
Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit
Version 2.x Messages Are Composed of Segments
and Segments Are Composed of Fields
• Segments are the “sentences” of the message
• Each has a job (PID is the personal identifier segment)
• Segment name (e.g., PID)
• Each segment is composed of fields
• PID|field1|field2|person identifiers|
• Fields are separated by delimiters (ASCII characters or XML tags)
• Fields may be optional, repeat, or both
• Empty fields have place holders
• Each field has a data type specification

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Delimiters Separate Components
Type Character
Segment Name 3 character code
Segment Terminator Carriage Return (ASCII 13)
Field Separator | (ASCII 124)
Component Separator ^ (ASCII 94)
Repeat Separator ~ (ASCII 126)
Escape Separator \ (ASCII 92)
Subcomponent Separator & (ASCII 38)

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


ACK Message Specification
HL7’s Definition:
“The simple general acknowledgment (ACK) can be used where the
application does not define a special application-level acknowledgment
message or where there has been an error that precludes application
processing.”
Segment Usage Cardinality Notes
MSH (Message Header Required (1..1)
Segment)
SFT (Software Segment) Optional (0..1)
MSA (Message Required (1..1)
Acknowledgement Segment)

ERR (Error Segment) Required (0..*)


but may be
empty

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Example ACK Message
MSH|^~\&||DCS|MYIIS|PHS||20090604||ACK^V04^ACK|
9299381|P|2.5.1|||NE|NE<CR>
 
MSA|AA|400586704<CR>

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


PID Segment (Partial)
Element Name Data Type Usage Cardinality

Set ID SI Required [1..1]


Patient ID CX Deprecated [0..0]
Patient ID List CX Required, but may [0..*]
be empty
Alternate Patient ID CX Deprecated [0..0]

Patient Name XPN Required [1..*]


Mother’s Maiden XPN Optional [0..1]
Name
Date of birth TS Required [1..1]
Many more fields

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Version 2.x: Data Types
• Atomic units of structured data
– Think of these as fields in a database
• NM: Numeric (primitive data type)
– For instance, 27.3
• CQ: Composite Quantity with units
– Quantity (NM)
– Units (CE)
– Example: 27.3^mL^milliliters^UCUM

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Coded Element (CE) Data Type
Position Requirements Description
1 Required Code
2 Required but may be Explanatory text
empty
3 Required Code system identifier
4 Optional Alternative code
5 Optional Alternative explanatory text
6 Required if position 4 is Alternative code system identifier
populated

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Profiles put Constraints one the Base Standard
• Base standard supports many needs
• Each need has different requirements
• Profiles are constraints that remove optionality and bind
to vocabulary
• The profile in use is identified in the MSH segment of the
message

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit


Additional Resources
• HL7 (hl7.org) has a variety of materials including
tutorials where you can get the specifics for each of its
standards.
• HL7’s website is at: http://www.hl7.org/
• CDC’s Vocabulary Access and Distribution Systems
(PHIN VADS) can be found at https://phinvads.cdc.gov/

Toolkit for Planning an EHR-based Surveillance Program | www.phii.org/EHRtoolkit

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy