Table of Contents

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