Table of Contents
-
1
Introduction
- PURPOSE
- BACKGROUND
- NEED FOR A STANDARD
- GOALS OF THE STANDARD
- HISTORY OF HL7 DEVELOPMENT
- OVERVIEW
-
HL7 encoding rules
-
Local variations
-
Evolutionary changes to the standards
-
Applicability to file transfers (batch processing)
-
Relationship to other protocols
- REFERENCE DOCUMENTS
-
ANSI standards
-
ISO standards
-
Codes and terminology sources
-
Other applicable documents
- TECHNICAL EDITORS
- SUGGESTIONS AND COMMENTS
-
2. Control/Query
- INTRODUCTION
- CONCEPTUAL APPROACH
-
Trigger events
-
Acknowledgements: original mode
-
Acknowledgements: enhanced mode
-
Queries
- COMMUNICATIONS ENVIRONMENT
- HL7 MESSAGES
- SEGMENTS
- FIELDS
-
Position (sequence within the segment)
-
Maximum length
-
Data type
-
Optionality
-
Repetition
-
Table
-
ID number
-
Name
- MESSAGE DELIMITERS
- Data types
-
AD - address
-
CD - channel definition
-
CE - coded element
-
CF - coded element with formatted values
-
CK - composite ID with check digit
-
CM - composite
-
CN - composite ID number and name
-
CP - composite price
-
CQ - composite quantity with units
-
CX - extended composite ID with check digit
-
DLN - driver's license number
-
DR - date/time range
-
DT - date
-
ED - encapsulated data
-
EI - entity identifier
-
FC - financial class
-
FT - formatted text data
-
HD - hierarchic designator
-
ID - coded value for HL7 defined tables
-
IS - coded value for user-defined tables
-
JCC - job code/class
-
MA - multiplexed array
-
MO - money
-
NA - numeric array
-
NM - numeric
-
PL - person location
-
PPN - performing person time stamp
-
PN - person name
-
PT - processing type
-
QIP - query input parameter list
-
QSC - query selection criteria
-
RCD - row column definition
-
RI - repeat interval
-
RP - reference pointer
-
SCV - scheduling class value pair
-
SI - sequence ID
-
SN - structured numeric
-
ST - string data
-
TM - time
-
TN - telephone number
-
TQ - timing quantity
-
TS - time stamp
-
TX - text data
-
VH - visiting hours
-
XAD - extended address
-
XCN - extended composite ID number and name for persons
-
XON - extended composite name and identification number for organizations
-
XPN - extended person name
-
XTN - extended telecommunication number
- Use of escape sequences in text fields
-
Formatting codes
-
Escape sequences supporting multiple character sets for PN and XPN data types
-
Highlighting
-
Special character
-
Hexadecimal
-
Formatted text
-
Local
- Message construction rules
-
Encoding rules notes
-
Version compatibility definition
- CHAPTER FORMATS FOR DEFINING HL7 MESSAGES
-
HL7 abstract message syntax example
- APPLICATION (LEVEL 7) PROCESSING RULES
-
Original and enhanced processing rules
-
Application (level 7) processing rules, deferred processing two phase reply (original acknowledgment mode only)
- ACKNOWLEDGEMENT MESSAGES
-
ACK - general acknowledgment
-
MCF - delayed acknowledgment
- DISPLAY MESSAGES
-
Display vs. record-oriented messages
-
UDM/ACK - unsolicited display update message (event Q05)
-
Continuation of unsolicited display update message
- QUERIES
-
Display vs. record oriented queries (original mode, embedded query language, virtual table, and stored procedure queries); and event replay requests
-
Message definition
-
Immediate vs. deferred response
-
Interactive continuation or cancellation of response messages: original mode (display and record oriented) and enhanced mode (display, tabular, and event replay)
-
Logical display break points
- Query trigger events and message definitions
- ORIGINAL MODE QUERIES
-
QRY/DSR - original mode display query - immediate response (event Q01)
- ORIGINAL MODE DEFERRED ACCESS
-
QRY/QCK - deferred query (event Q02)
-
DSR/ACK - deferred response to a query (event Q03)
- ENHANCED MODE QUERY MESSAGES
-
EQQ - embedded query language query (event Q01)
-
VQQ - virtual table query (event Q01)
-
SPQ - stored procedure request (event Q01)
-
RQQ - event replay query (event Q01)
- ENHANCED QUERY MODE RESPONSE MESSAGES
-
EDR - enhanced display response
-
TBR - tabular data response
-
ERP - event replay response
- QUERY MESSAGE IMPLEMENTATION CONSIDERATIONS
-
Original mode implementation considerations
-
Enhanced mode implementation considerations: definition of tables and "virtual tables"
- QUERY ERROR RESPONSE
- SPECIAL HL7 PROTOCOLS
-
Sequence number protocol
-
Continuation messages and segments
-
HL7 batch protocol
-
Modes for updating via repeating segments
- MESSAGE CONTROL SEGMENTS
-
MSH - message header segment
-
MSA - message acknowledgment segment
-
ERR - error segment
-
QRD - original-style query definition segment
-
QRF - original style query filter segment
-
URD - results/update definition segment
-
URS - unsolicited selection segment
-
DSC - Continuation pointer segment
-
DSP - display data segment
-
ADD - addendum segment
-
FHS - file header segment
-
FTS - file trailer segment
-
BHS - batch header segment
-
BTS - batch trailer segment
-
NTE - notes and comments segment
-
EQL - embedded query language segment
-
VTQ - virtual table query request segment
-
RDF - table row definition segment
-
RDT - table row data segment
-
SPR - stored procedure request definition segment
-
ERQ - event replay query segment
-
QAK- query acknowledgment segment
-
Miscellaneous HL7 tables used across all chapters
- SAMPLE CONTROL AND QUERY MESSAGES
-
General acknowledgment
-
Error return
-
Sequence number: initial message
-
Query examples
-
Master file update examples: with original and enhanced acknowledgment protocol
- OUTSTANDING ISSUES
-
3. Admission, Discharge, and Transfer
- PURPOSE
- TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
ADT/ACK - admit / visit notification (event A01)
-
ADT/ACK - transfer a patient (event A02)
-
ADT/ACK - discharge/end visit (event A03)
-
ADT/ACK - register a patient (event A04)
-
ADT/ACK - pre-admit a patient (event A05)
-
ADT/ACK - change an outpatient to an inpatient (event A06)
-
ADT/ACK - change an inpatient to an outpatient (event A07)
-
ADT/ACK - update patient information (event A08)
-
ADT/ACK - patient departing - tracking (event A09)
-
ADT/ACK - patient arriving - tracking (event A10)
-
ADT/ACK - cancel admit / visit notification (event A11)
-
ADT/ACK - cancel transfer (event A12)
-
ADT/ACK - cancel discharge / end visit (event A13)
-
ADT/ACK - pending admit (event A14)
-
ADT/ACK - pending transfer (event A15)
-
ADT/ACK - pending discharge (event A16)
-
ADT/ACK - swap patients (event A17)
-
ADT/ACK - merge patient information (event A18)
-
QRY/ADR - patient query (event A19)
-
ADT/ACK - bed status update (event A20)
-
ADT/ACK - patient goes on a "leave of absence" (event A21)
-
ADT/ACK - patient returns from a "leave of absence" (event A22)
-
ADT/ACK - delete a patient record (event A23)
-
ADT/ACK - link patient information (event A24)
-
ADT/ACK - cancel pending discharge (event A25)
-
ADT/ACK - cancel pending transfer (event A26)
-
ADT/ACK - cancel pending admit (event A27)
-
ADT/ACK - add person information (event A28)
-
ADT/ACK - delete person information (event A29)
-
ADT/ACK - merge person information (event A30)
-
ADT/ACK - update person information (event A31)
-
ADT/ACK - cancel patient arriving - tracking (event A32)
-
ADT/ACK - cancel patient departing - tracking (event A33)
-
ACK/ADT - merge patient information - patient ID only (event A34)
-
ADT/ACK - merge patient information - account number only (event A35)
-
ADT/ACK - merge patient information - patient ID & account number (event A36)
-
ADT/ACK - unlink patient information (event A37)
-
ADT/ACK - cancel pre-admit (event A38)
-
ADT/ACK - merge person - external ID (event A39)
-
ADT/ACK - merge patient - internal ID (event A40)
-
ADT/ACK - merge account - patient account number (event A41)
-
ADT/ACK - merge visit - visit number (event A42)
-
ADT/ACK - move patient information - internal ID (event A43)
-
ADT/ACK - move account information - patient account number (event A44)
-
ADT/ACK - move visit information - visit number (event A45)
-
ADT/ACK - change external ID (event A46)
-
ADT/ACK - change internal ID (event A47)
-
ADT/ACK - change alternate patient ID (event A48)
-
ADT/ACK - change patient account number (event A49)
-
ADT/ACK - change visit number (event A50)
-
ADT/ACK - change alternate visit ID (event A51)
- MESSAGE SEGMENTS
-
EVN - event type segment
-
PID - patient identification segment
-
PV1 - patient visit segment
-
PV2 - patient visit - additional information segment
-
NK1 - next of kin / associated parties segment
-
AL1 - patient allergy information segment
-
NPU - bed status update segment
-
MRG - merge patient information segment
-
PD1 - patient additional demographic segment
-
DB1 - Disability segment
- EXAMPLE TRANSACTIONS
-
Admit/visit notification - event A01 (admitted patient)
-
Pre-admit notification - event A05 (nonadmitted patient)
-
Admit/visit notification - event A04 (nonadmitted patient)
-
Change outpatient to inpatient - event A06
-
Transfer patient - event A02 (first example)
-
Cancel transfer - event A12
-
Transfer patient - event A02 (second example)
-
Discharge patient - event A03
- IMPLEMENTATION CONSIDERATIONS
-
Swapping a patient
-
Merging patient/person information
-
Patient record links
- OUTSTANDING ISSUES
-
4.
Order Entry
- OVERVIEW
-
Preface (organization of this chapter)
-
Glossary
- ORDER MESSAGE DEFINTIONS
-
ORM - general order message
-
ORR - general order response message (response to any ORM)
-
OSQ - query response for order status
- SEGMENTS COMMON TO ALL ORDERS
-
ORC - common order segment
-
BLG - billing segment
- QUANTITY/TIMING (TQ) DEFINITION
-
Quantity component (CQ)
-
Interval component (CM)
-
Duration component (ST)
-
Start date/time component (TS)
-
End date/time component (TS)
-
Priority component (ST)
-
Condition component (ST)
-
Text component (TX)
-
Conjunction component (ST)
-
Order sequencing component (CM)
-
Examples of quantity/timing usage
- OBSERVATION AND DIAGNOSTIC STUDY ORDERS
-
OBR - observation request segment
-
Examples of use
- DIET ORDERS
-
ODS - dietary orders, supplements, and preferences segment
-
ODT - diet tray instructions segment
-
Example diet messages
- SUPPLY ORDERS
-
RQD - requisition detail segment
-
RQ1 - requisition detail-1 segment
-
Examples of the use of RQD and RQ1 segments
- PHARMACY/TREATMENT ORDERS
-
ORM - pharmacy/treatment order message
-
RXO - pharmacy/treatment order segment
-
RXR - pharmacy/treatment route segment
-
RXC - pharmacy/treatment component order segment
-
IV solution groups
-
RDE/RRE - pharmacy/treatment encoded order message
-
RXE - pharmacy/treatment encoded order segment
-
Usage notes for pharmacy/treatment messages
-
RDS/RRD - pharmacy/treatment dispense message
-
RXD - pharmacy/treatment dispense segment
-
RGV/RRG - pharmacy/treatment give message
-
RXG - pharmacy/treatment give segment
-
RAS/RRA - pharmacy/treatment administration message
-
RXA - pharmacy/treatment administration segment
-
Pharmacy/treatment queries
-
Examples of use
- PHARMACY/TREATMENT ORDERS AND RESULTS TRANSACTION FLOW DIAGRAM
- VACCINE ADMINISTRATION DATA
- QUERIES FOR IMMUNIZATION RECORDS (QRF SEGMENTS)
- VACCINE TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
VXQ -query for vaccination record (event V01)
-
VXX - response to vaccination query returning multiple PID matches (event V02)
-
VXR - vaccination record response (event V03)
-
VXU - unsolicited vaccination record update (event V04)
- RXA SEGMENT USAGE IN VACCINE MESSAGES
-
Vaccines administered
-
Vaccine manufacturer
- VACCINATION - EXAMPLE TRANSACTIONS
-
VXQ - query for vaccination record
-
VXX - response to vaccination query with multiple PID matches
-
VXR - vaccination record response
-
VXU - unsolicited vaccination record update
-
Query acknowledgement with no records found
- OUTSTANDING ISSUES
-
5.
Query
-
6.
Finance
- PURPOSE
- PATIENT ACCOUNTING MESSAGE SET
- TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
BAR/ACK - add patient account (event P01)
-
BAR/ACK - purge patient accounts (event P02)
-
DFT/ACK - post detail financial transactions (event P03)
-
QRY/DSP - generate bills and accounts receivable statements (event P04)
-
BAR/ACK - update account (event P05)
-
BAR/ACK - end account (event P06)
- MESSAGE SEGMENTS
-
FT1 - financial transaction segment
-
DG1 - diagnosis segment
-
DRG - diagnosis related group segment
-
PR1 - procedures segment
-
GT1 - guarantor segment
-
IN1 - insurance segment
-
IN2 - insurance additional information segment
-
IN3 - insurance additional information, certification segment
-
ACC - accident segment
-
UB1 - UB82 data segment
-
UB2 - UB92 data segment
- EXAMPLE TRANSACTIONS
-
Create a patient billing/accounts receivable record
-
Post a charge to a patients account
-
Update patient accounts - update UB82 information
-
Update patient accounts - update diagnosis and DRG information
- IMPLEMENTATION CONSIDERATIONS
- OUTSTANDING ISSUES
-
7.
Observation Reporting
- INTRODUCTION AND OVERVIEW
-
Glossary
-
Narrative reports as batteries with many OBX
-
Suffixes for defining observation IDs for common components of narrative reports
-
Coding schemes
- MESSAGE DEFINITIONS
-
ORU/ACK - unsolicited transmission of an observation message (event R01)
-
QRY/ORF - query for results of observation (events R02, R04)
- SEGMENTS
-
OBR - observation request segment
-
OBX - observation/result segment
- EXAMPLE TRANSACTIONS
-
Query/response
-
Unsolicited
-
Example message
-
Example of narrative report messages
-
Reporting cultures and susceptibilities
-
Results reporting
-
Patient-specific clinical data with an order
- CLINICAL TRIALS
-
Terminology and concepts
- CLINICAL TRIALS - TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
CRM- clinical study registration message (events C01-C08)
-
CSU - unsolicited study data message (events C09-C12)
-
CM0, CM1, CM2 - clinical trials master file messages
- CLINICAL TRIALS - SEGMENT DEFINITIONS
-
CSR - clinical study registration segment
-
CSP - clinical study phase segment
-
CSS - clinical study data schedule segment
-
CTI - clinical trial identification segment
-
CM0 clinical study master segment
-
CM1 clinical study phase master segment
-
CM2 clinical study schedule master segment
- CLINICAL TRIALS - EXAMPLES
-
CRM - message when patient registered on a clinical trial
-
CRM - message when patient begins a phase of a clinical trial
-
CSU - message reporting monthly patient data updates to the sponsor
- PRODUCT EXPERIENCE
-
Terminology and concepts
- PRODUCT EXPERIENCE - TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
PEX - product experience message (events P07,P08)
-
SUR - summary product experience report (event P09)
- PRODUCT EXPERIENCE - SEGMENTS DEFINITIONS
-
PES - product experience sender segment
-
PEO - product experience observation segment
-
PCR - possible causal relationship segment
-
PSH - product summary header segment
-
PDC - product detail country segment
-
FAC - facility segment
- PRODUCT EXPERIENCE - EXAMPLE MESSAGES
- PRODUCT EXPERIENCE - REFERENCES
- WAVEFORM SUMMARY
- WAVEFORM RESULT DATA TYPES
-
NA - numeric array
-
MA - multiplexed array
-
CD - channel definition
- WAVEFORM SPECIFIC OBSERVATION ID SUFFIXES
-
Timing information (TIM)
-
Channel definition data (CHN)
-
Waveform digital data (WAV)
-
Waveform annotation (ANO)
- COMBINING RULES FOR WAVEFORM OBX SEGMENTS
- RESTRICTIONS ON VALUATION OF OBX SEGMENT FIELDS
-
OBX segment - TIM category
-
OBX segment - CHN category
-
OBX segment - WAV category
-
ANO category OBX segment
- WAVEFORM RESPONSE TRIGGER EVENTS
-
W01 - waveform result, unsolicited transmission of requested information
-
W02 - waveform result, response to query
- EXAMPLE MESSAGES FOR GENERIC WAVEFORM DATA
-
Example 1: "channel-block" format, using three separate sets of TIM, CHN, WAV and category OBX segments:
-
Example 2: "channel-block" format, using a single set of TIM, CHN, WAV and category OBX segments, with multiple channels within the one WAV category result segment:
-
Example 3: "channel-multiplexed" format, with multiple channels within the one WAV category result segment:
-
Example 4: "channel-block" format, using three separate sets of TIM, CHN, WAV and category OBX segments with a break in waveform data used to pinpoint waveform annotations for channels one and three:
- OUTSTANDING ISSUES
-
8.
Master Files
- PURPOSE
- TRIGGER EVENTS
- MESSAGES
-
MFN/MFK - master files notification
-
MFD/ACK - master files delayed application acknowledgment
-
MFQ/MFR - master files query
- GENERAL MASTER FILE SEGMENTS
-
MFI - master file identification segment
-
MFE - master file entry segment
-
MFA - master file acknowledgment segment
- GENERIC MASTER FILE EXAMPLES
-
ZL7 segment (proposed example only)
-
MFN message with original acknowledgment mode
-
Enhanced mode application-level acknowledgment to the MFN message
-
Delayed application-level acknowledgment
- STAFF AND PRACTITIONER MASTER FILES
-
MFN/MFK - staff/practitioner master file message
-
STF - staff identification segment
-
PRA - practitioner detail segment
-
Example: doctor master file MFN message
- TEST/OBSERVATIONS MASTER FILES
-
General approach of test/observation master files
-
MFN/MFR - test/observation master file
-
OM1 - general segment (fields that apply to most observations)
-
OM2 - numeric observation segment
-
OM3 - categorical test/observation segment
-
OM4 - observations that require specimens segment
-
OM5 - observation batteries (sets) segment
-
OM6 - Observations that are calculated from other observations segment
- LOCATION MASTER FILES
-
Patient location master file message (MFN/MFK)
-
LOC - location identification segment
-
LCH - location characteristic segment
-
LRL - location relationship segment
-
LDP - location department segment
-
LCC - location charge code segment
-
Example: MFN location master file message
- CHARGE DESCRIPTION MASTER FILES
-
Charge description master file message (MFN/MFK)
-
CDM - charge description master segment
-
PRC - pricing segment
-
Example: MRN message charge description master file
- CLINICAL TRIALS MASTER FILES
-
Clinical trials master file message (MFN/MFK)
-
CM0 - clinical study master segment
-
CM1 - clinical study phase master segment
-
CM2 - clinical study schedule master segment
- OUTSTANDING ISSUES
-
We invite proposals for the specification of other HL7-wide master files segments.
-
9.
Medical Records/Information Management
(Document Management)
- PURPOSE
-
Definition of terms and concepts
- DOCUMENT MANAGEMENT SECTION
- ASSUMPTIONS
- TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
Original document notification (event T01)
-
Original document notification and content (event T02)
-
Document status change notification (event T03)
-
Document status change notification and content (event T04)
-
Document addendum notification (event T05)
-
Document addendum notification and content (event T06)
-
Document edit notification (event T07)
-
Document edit notification and content (event T08)
-
Document replacement notification (event T09)
-
Document replacement notification and content (event T10)
-
Document cancel notification (event T11)
- MESSAGE SEGMENTS
-
TXA - transcription document header segment
-
OBX - observation segment usage
- EXAMPLE MESSAGE
- QUERY
-
QRY/DOC - document query (event T12)
-
10.
Scheduling
- PURPOSE
-
Schedules, appointments, and services and resources
-
Application roles
-
Trigger events, statuses, reasons, and types
-
Appointments, orders, and referrals
-
Glossary
-
Organization of this chapter: trigger events and message definitions
- PLACER APPLICATION REQUESTS AND TRIGGER EVENTS
-
Request new appointment booking (event S01)
-
Request appointment rescheduling (event S02)
-
Request appointment modification (event S03)
-
Request appointment cancellation (event S04)
-
Request appointment discontinuation (event S05)
-
Request appointment deletion (event S06)
-
Request addition of service/resource on appointment (event S07)
-
Request modification of service/resource on appointment (event S08)
-
Request cancellation of service/resource on appointment (event S09)
-
Request discontinuation of service/resource on appointment (event S10)
-
Request deletion of service/resource on appointment (event S11)
- FILLER APPLICATION MESSAGES AND TRIGGER EVENTS UNSOLICITED
-
Notification of new appointment booking (event S12)
-
Notification of appointment rescheduling (event S13)
-
Notification of appointment modification (event S14)
-
Notification of appointment cancellation (event S15)
-
Notification of appointment discontinuation (event S16)
-
Notification of appointment deletion (event S17)
-
Notification of addition of service/resource on appointment (event S18)
-
Notification of modification of service/resource on appointment (event S19)
-
Notification of cancellation of service/resource on appointment (event S20)
-
Notification of discontinuation of service/resource on appointment (event S21)
-
Notification of deletion of service/resource on appointment (event S22)
-
Notification of blocked schedule time slot(s) (event S23)
-
Notification of opened ("un-blocked") schedule time slot(s) (event S24)
-
Notification that patient did not show up for scheduled appointment (event S26)
- QUERY TRANSACTIONS AND TRIGGER EVENTS
-
Original mode queries - display oriented
-
Original mode queries - record oriented
-
SQM/SQR - schedule query message and response (event S25)
-
Enhanced mode queries
- MESSAGE SEGMENTS
-
ARQ - appointment request segment
-
SCH - schedule activity information segment
-
RGS - resource group segment
-
AIS - appointment information - service segment
-
AIG - appointment information - general resource segment
-
AIL - appointment information - location resource segment
-
AIP - appointment information - personnel resource segment
-
APR - appointment preferences segment
- EXAMPLE TRANSACTIONS
-
Request and receive new appointment - event S01
-
Unsolicited notification of rescheduled appointment - event S13
-
Request and receive new appointment with repeating interval - event S01
- IMPLEMENTATION CONSIDERATIONS
-
Logical relationship of resource and service segments
-
Multiple placer applications
- ISSUES
-
Logical relationship of resource and service segments
-
11.
Patient Referral
- PURPOSE
-
Patient referral and responses
-
Application roles and data process
-
Glossary
- PATIENT INFORMATION REQUEST MESSAGES AND TRIGGER EVENTS
-
RQI/RPI - request for insurance information (event I01)
-
RQI/RPL - request/receipt of patient selection display list (event I02)
-
RQI/RPR - request/receipt of patient selection list (event I03)
-
RQP/RPI - request for patient demographic data (event I04)
-
RQC/RCI - request for patient clinical information (event I05)
-
RQC/RCL - request/receipt of clinical data listing (event I06)
-
PIN/ACK - unsolicited insurance information (event I07)
- PATIENT TREATMENT AUTHORIZATION REQUESTS
-
RQA/RPA - request patient authorization message
-
RQA/RPA - request for treatment authorization information (event I08)
-
RQA/RPA - request for modification to an authorization (event I09)
-
RQA/RPA - request for resubmission of an authorization (event I10)
-
RQA/RPA - request for cancellation of an authorization (event I11)
- PATIENT REFERRAL MESSAGES AND TRIGGER EVENTS
-
REF/RRI - patient referral message
-
REF/RRI - patient referral (event I12)
-
REF/RRI - modify patient referral (event I13)
-
REF/RRI - cancel patient referral (event I14)
-
REF/RRI - request patient referral status (event I15)
- SEGMENTS
-
RF1 - referral information segment
-
AUT - authorization information segment
-
PRD - provider data segment
-
CTD - contact data segment
- EXAMPLES
-
RQI message using an I01 event with an immediate response
-
RQA message using an I08 event with an immediate response
-
RQA message using an I08 event with a deferred response
-
REF message using an I11 event with an immediate response
-
REF message using an I11 event with a deferred response
-
RQC inquiry message using an I05 event with an immediate response
- ISSUES
-
HL7 overlapping with ASC X12n
-
12.
Patient Care
- INTRODUCTION AND OVERVIEW
-
Glossary
-
Scenario descriptions
-
Trigger events
-
Use of action codes
-
Message construction rules
- MESSAGE DEFINITIONS
-
PGL/ACK - patient goal message (events PC6, PC7, PC8)
-
PPR/ACK - patient problem message (events PC1, PC2, PC3)
-
PPP/ACK - patient pathway message (problem-oriented) (events PCB, PCC, PCD)
-
PPG/ACK - patient pathway message (goal-oriented) (events PCG, PCH, PCJ)
-
QRYPRQ - patient care problem query (event PC4)
-
PRR - patient problem response (event PC5)
-
QRYPGQ - patient goal query (event PC9)
-
PPVPGR - patient goal response (event PCA)
-
QRYPTQ - patient pathway (problem-oriented) query (event PCE)
-
PTR - patient pathway (problem-oriented) response (event PCF)
-
QRYPTU - patient pathway (goal-oriented) query (event PCK)
-
PPTPTV - patient pathway (goal-oriented) response (event PCL)
- MESSAGE SEGMENTS
-
GOL - goal detail segment
-
PRB - problem detail segment
-
ROL - role segment
-
PTH - pathway segment
-
VAR - variance segment
- EXAMPLE TRANSACTIONS
- IMPLEMENTATION CONSIDERATIONS
- ONGOING ISSUES
-
A.
Data Definition Tables
- INTRODUCTION
- MESSAGE TYPES
- SEGMENTS
- HL7 AND USER-DEFINED TABLES - ALPHABETIC SORT
- HL7 AND USER-DEFINED TABLES - NUMERIC SORT
- DATA ELEMENT NAMES
-
B.
Lower Layer Protocols
-
C.
Network Management
- TRIGGER EVENTS AND MESSAGE DEFINITIONS
-
NMQ - Network management query message
-
NMD - Network management data message
- NETWORK MANAGEMENT SEGMENTS
-
NCK - system clock segment
-
NST - statistics segment
-
NSC - status change segment
-
QRD - query definition segment usage
-
D.
Version 2.2 BNF Message Descriptions
- BNF DESCRIPTIONS OF HL7 VERSION 2.2 ABSTRACT MESSAGES
-
Overview
-
Tokens
-
BNF Message Definitions
-
E. Glossary