Вы находитесь на странице: 1из 167

Victorian Health Level 7 (HL7)

DWH and ODS Interface Specification


Issue 1.2

22 December 1998

1998 ASPECT Computing Pty Ltd 550 Glenferrie Rd Hawthorn VIC 3122 Australia

Every effort has been made to supply complete and accurate information, and advice about errors or general comments are greatly appreciated. ASPECT Computing Pty Ltd accepts no responsibility for any loss of data that may occur as a result of using this manual, other than any responsibility defined by the laws of the state.

Amendment History
Issue 1.2 (22 December 1998)
Filename: K:\Documentation\IN-TRAY\HL7 Interface Specification v1.2.doc Date Last Saved: 22 December 1998 History:
Date 3 Sept 1998 4 Sept 1998 30 Sept 1998 6 Oct 1998 7 Oct 1998 Issu e 0.1 0.2 0.3 0.4 0.5 Pages Changed All All All All All Replacement Details Initial Draft First Review Draft Second Review Draft Third Review Draft Working Draft

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

iii

Amendment History

Date 16 Oct 1998

Issu e 0.6

Pages Changed All

Replacement Details OR-1115, OR-1116, OR-1118, OR-1119, OR-1120, OR-1121, OR-1122, OR-1123, OR-1124, OR-1128, OR-1129, OR-1130, OR-1132, OR-1133, OR-1145, OR-1172, OR-1175, OR-1182, OR-1188, OR-1189 OR-1096, OR-1213, OR-1217, OR-1224, OR-1226, OR-1231, OR-1233, OR-1228, OR-1246, OR-1248, OR-1287, OR-1350, OR-1386, OR-1174, OR-1235, OR-1300, OR-1301, OR-1249 OR-1496, OR-1510, OR-1563 OR-1574

17 Nov 1998

0.7

All

4 December 1998

1.0

All

14 December 1998 21 December 1998

1.1 1.1

All All

iv

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Preface
This interface specification details the technical requirements for the transmission of data to the Department of Human Services (DHS), using the HL7 messaging protocol. For hospitals to implement this interface, additional information is required. This additional information includes The code list specification, which details valid values for each data item (if applicable), and The business rules specification, which specifies the rules for the submission to the Department for admitted episodes and emergency. The Client Management Interface (CMI) technical specifications, which specifies the rules for the submission to the Department for mental health (only required if Service Providers are not taking up the CMI). Development of the interface should not be attempted without these additional specifications. This interface specification is not a standard it is the interface definition for the reporting to the DHS systems, namely: Data Warehouse (DWH) for acute health and mental health reporting, and Operational Data Store (ODS) for mental health. This specification has been based on the HL7 Standard Version 2.3 and the Australian Standard AS4700.1. Some variation from these standards was necessary in order to meet the reporting requirements to the DHS. These variances are noted in bold throughout the specification where appropriate.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Table of Contents

Chapter 1. Introduction .................................................................................................................................. 1-1 1.1. 1.2. 1.3. 1.4. 1.5. Scope ............................................................................................................................... 1-1 Background ..................................................................................................................... 1-2 Application ...................................................................................................................... 1-3 Referenced Documents................................................................................................... 1-4 Definitions ....................................................................................................................... 1-4

Chapter 2. Trigger Events .............................................................................................................................. 2-1 2.1. General ............................................................................................................................ 2-1 2.2. Trigger Event Overview .................................................................................................. 2-2 2.3. Trigger Event Descriptions............................................................................................. 2-4 2.3.1. A01 Admit/Visit Notification ............................................................................ 2-4 2.3.2. A02 Transfer a Patient.................................................................................... 2-5 2.3.3. A03 Discharge/End Visit ................................................................................. 2-7 2.3.4. A04 Register a Patient.................................................................................... 2-8 2.3.5. A08 Update Patient Information.................................................................... 2-10 2.3.6. A11 Cancel Admit/Visit Notification............................................................... 2-11 2.3.7. A12 Cancel Transfer..................................................................................... 2-13 2.3.8. A13 Cancel Discharge/End Visit ................................................................... 2-14 2.3.9. A19 Patient Query ........................................................................................ 2-15 2.3.10. A21 Patient Goes on a Leave of Absence................................................... 2-18 2.3.11. A22 Patient Returns from a Leave of Absence ............................................ 2-19 2.3.12. A24 Link Patient Information......................................................................... 2-20 2.3.13. A31 Update Person Information.................................................................... 2-20 2.3.14. A37 Unlink Patient Information ..................................................................... 2-21

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

vii

Table of Contents

2.3.15. 2.3.16. 2.3.18. 2.3.19. 2.3.20. 2.3.21.

A45 R01 M02 M05 MFQ T12

Move Visit InformationVisit Number ..................................................... 2-21 Unsolicited Transmission of an Observation Message ........................... 2-22 Master Practitioner ................................................................................ 2-24 Master Location..................................................................................... 2-25 Master Files Query............................................................................... 2-25 Document Query.................................................................................... 2-26

Chapter 3. Message Segments....................................................................................................................... 3-1 3.1. General............................................................................................................................. 3-1 3.2. Message Segment Descriptions ..................................................................................... 3-2 3.2.1. Message Header Segment (MSH)..................................................................... 3-2 3.2.2. Message Acknowledgement (MSA) Segment.................................................... 3-4 3.2.3. Error (ERR) Segment........................................................................................ 3-5 3.2.4. Event Type (EVN) Segment.............................................................................. 3-6 3.2.5. Patient Identification (PID) Segment ................................................................. 3-7 3.2.6. Patient Visit (PV1) Segment............................................................................ 3-17 3.2.7. Patient Visit - Additional Information (PV2) Segment ...................................... 3-30 3.2.8. Patient Additional Demographic (PD1) Segment ............................................. 3-34 3.2.9. Diagnosis (DG1) Segment .............................................................................. 3-36 3.2.10. Diagnosis Related Group (DRG) Segment ...................................................... 3-39 3.2.11. Procedure (PR1) Segment .............................................................................. 3-40 3.2.12. Insurance (IN1) Segment ................................................................................ 3-46 3.2.13. Insurance Additional Information (IN2) Segment ............................................. 3-50 3.2.14. Observation Report (OBR) Segment............................................................... 3-55 3.2.15. Observation (OBX) Segment........................................................................... 3-58 3.2.16. Merge Patient Information (MRG) Segment .................................................... 3-63 3.2.17. Funding Arrangement Information (ZFA) Segment.......................................... 3-64 3.2.18. Emergency Information (ZEM) Segment ......................................................... 3-66 3.2.19. Mental Health Information (ZMH) Segment ..................................................... 3-68 3.2.20. Mental Health Legal Status Information (ZLE) Segment.................................. 3-76 3.2.21. Master File Identification Segment (MFI)......................................................... 3-85 3.2.22. Master File Entry Segment (MFE)................................................................... 3-87 3.2.23. Location Identification Segment (LOC)............................................................ 3-89

viii

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Table of Contents

3.2.24. 3.2.25. 3.2.26. 3.2.27. 3.2.28.

Location Characteristic Segment (LCH) .......................................................... 3-91 Location Department Segment (LDP) ............................................................. 3-93 Staff identification Segment (STF).................................................................. 3-95 Original-style Query Definition Segment (QRD) .............................................. 3-99 Original-style Query Filter Segment (QRF) ....................................................3-102

Chapter 4. Lower-Layer Protocols................................................................................................................. 4-1 4.1. Communications Environment Overview ...................................................................... 4-1 4.2. Lower Level Protocol Requirements.............................................................................. 4-2 4.3. Network Security ............................................................................................................. 4-4 Chapter 5. Reporting ...................................................................................................................................... 5-1

Chapter 6. Scenarios ...................................................................................................................................... 6-1 6.1. Emergency....................................................................................................................... 6-1 6.2. Admitted Episode............................................................................................................ 6-4 6.3. Mental Health................................................................................................................... 6-7

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

ix

Chapter 1 Introduction
This Interface Specification covers the Victorian (Australia) implementation of the Health Level Seven (HL7) Version 2.3 Standard, for patient administration for reporting to the Department of Human Services (Victoria). The Australian Standard AS 4700.1 - 1998 has been used as the basis for this specification and all relevant information from that Standard has been incorporated to enable consistent implementation of HL7 in Victoria, Australia. This specification is not a stand-alone document for review in isolation. A good understanding and, preferably, working knowledge of HL7 is essential, as this specification frequently refers to the HL7 Version 2.3 Standard. In particular, chapter 2 of the HL7 Version 2.3 Standard provides details of data types and data items specific to HL7 which are referred to in this document. Copies of the HL7 Standard are available from Standards Australia (Locked Bag 802 South Melbourne VIC 3205 or telephone 03 9693 3502). The purpose of this specification is to detail to health service providers, health information technology vendors, health information technology consultants and the health informatics community the use of the HL7 protocol to exchange key sets of data between different computer application systems and to the Department.

1.1. Scope
This Interface Specification defines a uniform implementation of the HL7 Version 2.3 protocol, for communications of on-line, real-time HL7 messages between computer application systems in Victorian health care providers (public and private) and the Victorian health Data Warehouse (DWH) and mental health Operational Data Store (ODS) systems. Both acute and mental health data is covered. Specifically, this document contains: reference information including reference documents and definitions trigger event descriptions e.g. A01 Admit/visit notification message segments e.g. Patient Identification (PID) Segment.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

11

Introduction

examples of triggers The specification provides interpretation and guidance on which HL7 trigger events, segments and data elements are mandatory (required), optional, or conditional (required, based on a condition), and gives relevant usage notes for interfacing to the DWH and ODS systems. The specification provides for consistent use of data definitions and references to the National Health Data Dictionary Version 7.0 (1998) and the International Organization for Standardization (ISO) where relevant. HL7 reporting to the Department of Human Services (Victoria) should comply with this specification as it allows for transmission of data sent to the Department for reporting to: Data Warehouse (DWH) for acute health and mental health Operational Data Store (ODS) for mental health which will be the systems accepting the collections of: Victorian Inpatient Minimum Database (VIMD/VAED) Victorian Emergency Minimum Dataset (VEMD) Psychiatric Records Information Systems Manager (PRISM). This specification will be further developed in the future to allow for HL7 reporting of other data sets to the Department including: Elective Surgery Information System (ESIS) Health services cost data Ambulance services data Aged Care Assessment Team (ACAT) data.

1.2. Background
HL7 is a health care application protocol accredited as a Standard by the American National Standards Institute (ANSI). `Level Seven' refers to the highest level of the International Organization for Standardization (ISO) communications model for Open Systems Interconnection (OSI) at the application level. Issues within the application level include definition of the data to be exchanged, the timing of the exchange

12

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Introduction

and communication of certain errors to the application. This level supports such functions as security checks, identification of the participants, availability checks, negotiating exchange mechanisms and, importantly, structuring the data exchanges themselves. HL7 focuses on the interface requirements of the entire health care organization. It allows development along the fastest possible track to the unique requirements of already installed hospital and departmental systems, some of which use mature technologies. The HL7 protocol is a collection of standard formats that specify the implementation of interfaces between computer applications. It is not rigid. Flexibility is built into the protocol to allow compatibility for specialized data sets that have facility-specific needs. One of HL7's strengths is its inbuilt flexibility. However, it is also one of its weaknesses. It is open to misinterpretation in its structure and format. HL7 is based on the health environment in the USA. While HL7 is concerned with addressing immediate needs, there is a very strong focus on convergence with other Standards development activities in the USA and internationally. There are international HL7 initiatives in countries such as Australia, Canada, the United Kingdom, Germany, Japan, the Netherlands and New Zealand. The Australian Standard for the implementation of HL7, AS 4700.1, was prepared by the Standards Australia HL7 Working Group IT/14/6/3, under direction from the IT/14 Health Informatics Committee, in response to requests from the health informatics community. This working group aims to develop Australian Standards for patient electronic data communication between health care information systems based on the current release of the Health Level Seven (HL7) protocol. The HL7 protocol covers a wide range of data interchange functions. However, the Australian Standard focuses on the patient administration functions as these form the common basis for all HL7 messages. Generally, information entered into a patient administration system is passed to the nursing, ancillary and financial systems, either in the form of an unsolicited update or in response to a record-oriented query. Other functions of HL7 being addressed include pathology, prescriptions, radiology, referral and health service messaging, dietary and stock orders and results, together with finance and billing. This document is based upon the Australian standard and HL7 2.3, and covers the Victorian application of these standards. The interface described within this document must be adhered to in order to interface with the DWH and ODS.

1.3. Application
All efforts have been made in this document to minimize divergence from the Australian Standard which respectively has aimed to minimize divergence with the HL7 USA protocol to ensure maximum compatibility with future versions. Deviations from the AS 4700.1 (Australian HL7 Standard) and HL7 2.3 have been indicated by the use of bolding.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

13

Introduction

1.4. Referenced Documents


The following documents are referred to in this Specification: AS 4700 4700.1 ISO 639 3106 HL7 NHDD Codes for the representation of names of languages Codes for the representation of names of countries Health Level Seven Version 2.3, Ann Arbor: Health Level Seven, 1997 National Health Data Dictionary Version 7.0. National Health Data Committee, Canberra: Australian Institute of Health and Welfare, 1998 Implementation of Health Level Seven (HL7) Version 2.2 Part 1: Admission, discharge and transfer, 1998

1.5. Definitions
For the purpose of this document, the definitions below apply. Admitted patient A patient who undergoes a hospital's formal admission process (NHDD). Non-admitted patient A patient who does not undergo a hospital's formal admission process. This includes emergency department patient, outpatient and other non-admitted patient (NHDD). Community mental health clients also belong to this category. Trigger event An action that takes place in an application, based on some predefined condition such as an admission, ward transfer, or placement of an order and the like. The action usually results in the compilation and transmission of a data message.

14

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Introduction

Visit An admitted patient visit is the hospital stay from date of admission to the date of discharge. A non-admitted patient visit is the attendance for which one or more services are provided to that patient. Establishment Identifier A three character code used by the Victorian health Data Warehouse to identify a Hospital or equivalent health service provider. Campus A location within a network component hospital or itself a hospital. Campus Code A four character code used by the Victorian health Data Warehouse to identify a Campus or equivalent health service provider. The code includes the three character Hospital code plus a fourth character Site Identifier to indicate the exact physical site where the health service was provided or data was transmitted. Subcentre Independent unit within a campus (e.g. a specific ward or team). Emergency An non-admitted patient visit at an Emergency Department. Admitted Episode An acute or mental health visit performed within a hospital setting (includes hospital in the home, but not mental health residential placement). Case A period of mental health care of a client at a campus. Episode A period of mental health care of a client at a subcentre, within the bounds of a case.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

15

Chapter 2 Trigger Events


2.1. General
It is assumed that the sending systems will produce transactions only after performing the relevant validation checks to confirm that data integrity has been maintained. The trigger events are described below. Most trigger events are served by the ADT unsolicited update and the ACK response. The mental health Operational Data Store also uses A19 trigger events, which are served by a QRY and an ADR reply; also M02 and M05 trigger events are served by an MFN notification and the MFK response. The T12 trigger is used to request reports, and will receive a DOC response. As different hospital systems often differ in the way they define and handle different patient types (Care Types), the trigger events defined in the specification are each specific to a patient type. The patient type for any visit-related information must be specified in the patient class (eg same day patient, emergency patient, mental health community client) data element (see PV1-2) to enable each system to properly handle the transaction. This means that both the trigger event code and the patient class should be checked in order to determine how to handle the transaction. Both admitted and non-admitted patient trigger events are generated using most of the same trigger event codes. The meaning or interpretation of the trigger event depends on the type of patient. For Admitted Episode and Emergency submissions, the information that is included in any of these trigger event transactions can be more than the minimum necessary to accommodate the trigger event. Only data items which are changed are required for submission (provided the submission conforms to business rules). It is recommended that the A08 trigger event be used to update data elements that are not necessarily related to any of the other trigger events. Additional data elements that are supplied which are not specifically related to the trigger event will be ignored. Mental health submissions require all data to be sent for both new and updated data. The CMI/ODS Technical Specifications contain message definitions.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

21

Trigger Events

2.2. Trigger Event Overview


This section addresses the uses of triggers for the exchange of data between health care provider systems and the DWH and ODS applications. Each trigger event has been described in the following fashion: (a) Status The status can be 'mandatory', optionalor 'not available' for each of the specified interfaces as follows: (i) Mandatory must be supported by all health care facilities and vendors of health software for the indicated interface (ii) Optional support by health care facilities and vendors of health software for the indicated interface is available, but is not currently required. (iii) Not Available the trigger is not currently used in the indicated interface. (b) Description The description typically refers to the HL7 Standard Version 2.3 description and is the generic description of the trigger. The description outlines the context in which the trigger will be used. (c) Usage Notes Usage notes gives information that is pertinent to the use of the trigger event. It particularly addresses issues in relation to the population of individual data elements. (d) Trigger Structure The trigger structure outlines the Victorian implementation of the trigger event where it varies from the HL7 Standard Version 2.3. Otherwise, the trigger structure refers to the standard. Note: Square brackets ( [ ] ) in the trigger structure refer to optional items and curly brackets ( { } ) refer to repeating items. (e) Trigger Uses The trigger uses describe the events that will be transmitted using the trigger and to which application (DWH or ODS) the trigger is to be sent.

22

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

The trigger events that can be sent and received by the different systems interfacing to the DWH and ODS are described below: Table 21. Trigger Events for DWH and ODS
Trigger Mental Health (admitted and community) Send A01 A02 A03 A04 A08 A11 A12 A13 A19 A21 A22 Receive Emergency Send Receive Acute Admitted Episode Send (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) (DWH) Receive

(DWH, ODS) (DWH, ODS) (DWH, ODS) (DWH, ODS) (DWH, ODS) (DWH, ODS) (DWH, ODS) (DWH, ODS) (ODS) (DWH, ODS) (DWH, ODS)

(DWH) (DWH)

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

23

Trigger Events

Trigger

Mental Health (admitted and community) Send Receive (from ODS) (DWH, ODS) (from ODS) (DWH, ODS) (DWH, ODS) (ODS) (ODS)

Emergency Send Receive

Acute Admitted Episode Send Receive

A24 A31 A37 A45 R01 M02 M05 T12

(DWH)

(DWH)

2.3. Trigger Event Descriptions


2.3.1. A01 Admit/Visit Notification
The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH

24

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A01 trigger event is to be used for admitted patients only. It is generated as a result of the patient undergoing the admission process of a health care facility which assigns the patient to a bed. It signals the beginning of a patient's stay in a health care facility. (c) Usage Notes It is important that the patient id(see PID-3), visit number(see PV1-19) and the servicing facility(see PV1-39) are populated as these form the basis of uniquely identifying each visit within a health care facility. Trigger A11 cancels an A01. (d) Trigger Structure
ADT MSH EVN PID [ PD1 ] [ { NK1 } ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] [ { AL1 } ] [ { DG1 } ] [ DRG ] [ { PR1 [ { ROL } ] } ] [ { GT1 } ] [ { IN1 [ IN2 ] [ IN3 ] } ] [ ACC ] [ UB1 ] [ UB2 ] [ { ZMH } ] [ { ZLE } ] [ { ZFA } ] ADT Message Message Header Event Type Patient Identification Additional Demographics Next of Kin / Associated Parties Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Allergy Information Diagnosis Information Diagnosis Related Group Procedures Role

Guarantor Insurance Insurance Additional Info. Insurance Add'l Info Cert.

Accident Information Universal Bill Information Universal Bill 92 Information Mental Health Information Mental Health Legal Status Information Funding Arrangement Information

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

25

Trigger Events

ACK MSH MSA [ ERR ]

General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Acute health patient admission into a ward within a hospital; sent to DWH Mental health client admission into a ward within a hospital; sent to ODS and DWH Mental health client residential placement; sent to ODS and DWH

2.3.2. A02 Transfer a Patient


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A02 trigger event is generated as a result of the patient changing his or her assigned physical location. This is only used for admitted patients. (c) Usage Notes The new patient location appears in data element 'assigned patient location' (see PV1-3), while the old patient location appears in data element 'prior patient location' (see PV1-6). The date and time of the change of location is recorded in event occurred (see EVN-6). Trigger A12 cancels an A02. (d) Trigger Structure
ADT MSH EVN PID [ PD1 ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] ADT Message Message Header Event Type Patient Identification Additional Demographics Patient Visit Patient Visit Additional Info. Disability Information Observation / Result

26

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

[ { ZMH } ] [ { ZLE } ] [ { ZFA } ] ACK MSH MSA [ ERR ]

Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Acute health patient transfer between wards; sent to DWH Mental health client transfer between wards; sent to ODS and DWH Mental health client transfer between residential units; sent to ODS and DWH

2.3.3. A03 Discharge/End Visit


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Mandatory for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A03 trigger event signals the end of the patient's stay in the health care facility. For an admitted patient, the A03 trigger event is generated as a result of recording the discharge date indicating that the patient is no longer in the facility. For a nonadmitted patient, the A03 trigger event is sent as a result of recording the completion of the non-admitted visit to the health care facility. (c) Usage Notes For an admitted patient, the patient's location prior to discharge should be entered in data element 'assigned patient location' (see PV1-3). For a non-admitted patient, the visit and date/time can be entered in data element 'discharge date/time' (see PV145). This trigger is also sent on statistical separation (change of Care Type). A statistical admission should follow. Trigger A13 cancels an A03. (d) Trigger Structure
ADT MSH EVN ADT Message Message Header Event Type

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

27

Trigger Events

PID [ PD1 ] PV1 [ PV2 ] [ { DB1 } ] [ { DG1 } ] [ DRG ] [ { PR1 [ { ROL } ] } ] [ { OBX } ] [ ZEM ] [ { ZMH } ] [ { ZLE } ] [ { ZFA } ] ACK MSH MSA [ ERR ]

Patient Identification Additional Demographics Patient Visit Patient Visit Additional Info. Disability Information Diagnosis Information Diagnosis Related Group Procedures Role

Observation / Result Emergency Information Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Acute health patient discharge from hospital; sent to DWH Acute health patient statistical separation (change of care type); sent to DWH Emergency department departure of patient; sent to DWH Mental health client separation from hospital; sent to ODS and DWH Mental health client separation from residential placement; sent to ODS and DWH Mental health client statistical separation (change of program classification, leave > 3 days); sent to DWH Mental health client completion of R/CTO; sent to ODS and DWH Mental health client closure of a case; sent to ODS and DWH Mental health client closure of an episode; sent to ODS and DWH

2.3.4. A04 Register a Patient


The following applies:

28

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

(a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Mandatory for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A04 trigger event is generated when a patient has been registered as a non-admitted patient. That is, the patient is not yet admitted to a health care facility. (c) Usage Notes The visit start date/time is entered in data element 'admit date/time' (see PV1-44). (d) Trigger Structure
ADT MSH EVN PID [ PD1 ] [ { NK1 } ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] [ { AL1 } ] [ { DG1 } ] [ DRG ] [ { PR1 [ { ROL } ] } ] [ { GT1 } ] [ { IN1 [ IN2 ] [ IN3 ] } ] [ ACC ] [ UB1 ] [ UB2 ] [ ZEM ] [ { ZMH } ] ADT Message Message Header Event Type Patient Identification Additional Demographics Next of Kin / Associated Parties Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Allergy Information Diagnosis Information Diagnosis Related Group Procedures Role

Guarantor Insurance Insurance Additional Info. Insurance Add'l Info Cert.

Accident Information Universal Bill Information Universal Bill 92 Information Emergency Information Mental Health Information

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

29

Trigger Events

[ { ZLE } [ { ZFA } ACK MSH MSA [ ERR ]

] ]

Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Emergency department arrival of a patient; sent to DWH Mental health client statewide registration; sent to ODS and DWH Mental health client start case; sent to ODS and DWH Mental health client start episode; sent to ODS and DWH Mental health client start R/CTO; sent to ODS and DWH Mental health client recording of contact; sent to ODS and DWH

2.3.5. A08 Update Patient Information


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Mandatory for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A08 trigger event is generated as a result of patient information being changed. This will include all events that are not specifically identified by some other trigger, e.g. A02 trigger event for change to location. A08 is used when visit information is being updated. (Note: A31 is used when only demographic details are to be updated.) (c) Usage Notes It is anticipated that separate triggers will be generated for separate events. For example, changes to clinical or financial status require date and time of change. However, this does not preclude an A08 trigger event being sent with multiple changed fields, including both demographics and visit details. (d) Trigger Structure

210

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

ADT MSH EVN PID [ PD1 ] [ { NK1 } ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] [ { AL1 } ] [ { DG1 } ] [ DRG ] [ { PR1 [ { ROL } ] } ] [ { GT1 } ] [ { IN1 [ IN2 ] [ IN3 ] } ] [ ACC ] [ UB1 ] [ UB2 ] [ ZEM ] [ { ZMH } ] [ { ZLE } ] [ { ZFA } ] ACK MSH MSA [ ERR ]

ADT Message Message Header Event Type Patient Identification Additional Demographics Next of Kin / Associated Parties Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Allergy Information Diagnosis Information Diagnosis Related Group Procedures Role

Guarantor Insurance Insurance Additional Info. Insurance Add'l Info Cert.

Accident Information Universal Bill Information Universal Bill 92 Information Emergency Information Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Acute health patient update of details; sent to DWH Emergency department patient update of details; sent to DWH Mental health update of client details; sent to ODS and DWH Mental health client start case management; sent to ODS and DWH

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

211

Trigger Events

Mental health client legal status assignment; sent to ODS and DWH Mental health client recording of ECT, mechanical restraint and seclusion procedures; sent to DWH Mental Health update of CTO details; sent to ODS and DWH Mental Health ISP details; sent to DWH Mental Health Diagnosis details; sent to ODS and DWH

2.3.6. A11 Cancel Admit/Visit Notification


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Mandatory for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A11 trigger event is generated as a result of the patient's admission or visit being cancelled. For admitted patients, it is sent to either cancel an erroneous A01 (admit a patient) trigger event or for non-admitted patients, it is sent to either cancel an erroneous A04 (register a patient) trigger event. (c) Usage Notes The A11 trigger is generated to delete a previously sent admission (A01) or registration (A04). (Note: The ODS will not accept cancellation of an admission which has events associated. Appropriate triggers must be sent to cancel each admitted event before transmitting the A11.) (d) Trigger Structure
ADT MSH EVN PID [ PD1 ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] ADT Message Message Header Event Type Patient Identification Additional Demographics Patient Visit Patient Visit Additional Info. Disability Information Observation / Result

212

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

[ [ [ [ [

{ DG1 } ZEM ] { ZMH } { ZLE } { ZFA }

] ] ] ]

Diagnosis Information Emergency Information Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

ACK MSH MSA [ ERR ]

(d) Trigger Uses

Cancellation of an acute health patient admission into a ward within a hospital; sent to DWH Cancellation of an emergency department arrival of a patient; sent to DWH Cancellation of a mental health client admission into a ward within a hospital; sent to ODS and DWH Cancellation of a mental health client residential placement; sent to ODS and DWH

2.3.7. A12 Cancel Transfer


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A12 trigger event is generated following cancellation of an admitted patient location transfer. It is sent to either cancel an erroneous A02 (transfer a patient) trigger event or because of a decision not to transfer a patient. (c) Usage Notes The location of the patient before the original transfer should be recorded in data element 'assigned patient location' (see PV1-3). (d) Trigger Structure
ADT MSH EVN ADT Message Message Header Event Type

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

213

Trigger Events

PID [ PD1 ] PV1 [ PV2 ] [ { DB1 } [ { OBX } [ DG1 ] [ { ZMH } [ { ZLE } [ { ZFA } ACK MSH MSA [ ERR ]

] ] ] ] ]

Patient Identification Additional Demographics Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Diagnosis Information Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Cancellation of an acute health patient transfer between wards; sent to DWH Cancellation of a mental health client transfer between wards; sent to ODS and DWH Cancellation of a mental health client transfer between residential units; sent to ODS and DWH

2.3.8. A13 Cancel Discharge/End Visit


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Mandatory for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A13 trigger event is generated as the result of a discharge/separation needing to be cancelled, for an admitted or nonadmitted visit. It is sent to either cancel an erroneous A03 (discharge/end visit) trigger event or because of a decision not to discharge the patient or end the patient visit. (c) Usage Notes After the cancellation has been processed, the location of the patient should be in data element 'assigned patient location' (see PV1-3). Before the erroneous A03 trigger event, the patient's previous location should be in data element 'prior patient location' (see PV1-6).

214

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

(d) Trigger Structure


ADT MSH EVN PID [ PD1 ] [ { NK1 } ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] [ { AL1 } ] [ { DG1 } ] [ DRG ] [ { PR1 [ { ROL } ] } ] [ { GT1 } ] [ { IN1 [ IN2 ] [ IN3 ] } ] [ ACC ] [ UB1 ] [ UB2 ] [ ZEM ] [ { ZMH } ] [ { ZLE } ] [ { ZFA } ] ACK MSH MSA [ ERR ] ADT Message Message Header Event Type Patient Identification Additional Demographics Next of Kin / Associated Parties Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Allergy Information Diagnosis Information Diagnosis Related Group Procedures Role

Guarantor Insurance Insurance Additional Info. Insurance Add'l Info Cert.

Accident Information Universal Bill Information Universal Bill 92 Information Emergency Information Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Cancellation of an acute health patient discharge from hospital; sent to DWH Cancellation of an acute health patient statistical separation (change of care type); sent to DWH Cancellation of an emergency department departure of patient; sent to DWH

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

215

Trigger Events

Cancellation of a mental health client separation from hospital; sent to ODS and DWH Cancellation of a mental health client separation from residential placement; sent to ODS and DWH Cancellation of a mental health client statistical separation; sent to DWH

2.3.9. A19 Patient Query


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Optional for Mental Health interface to acquire details from ODS Not Available for Mental Health interface to DWH (b) Description The A19 trigger event is generated because a health care facility requires patient details from the Operational Data Store. ODS will not query other applications. For further details on QRY refer to Clause 2.24.4 of the HL7 Version 2.3 protocol. (c) Usage Notes The implications of this trigger event are that the sending and receiving systems can at least understand and support query accept/response messages and syntax. This trigger is used for queries related to a specific client. (c) Trigger Structure
QRY MSH QRD [ QRF ] ADR MSH MSA [ ERR ] QRD [ QRF ] { [ EVN ] PID [ PD1 ] [ { NK1 } Patient Query Message Header Query Definition Query Filter ADR Message Message Header Message Acknowledgment Error Query Definition Query Filter Event Type Patient Identification Additional Demographics Next of Kin / Associated Parties

216

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] [ { AL1 } ] [ { DG1 } ] [ DRG ] [ { PR1 [ { ROL } ] } ] [ { GT1 } ] [ { IN1 [ IN2 ] [ IN3 ] } ] [ ACC ] [ UB1 ] [ UB2 ] [ { ZMH } ] [ { ZLE } ] } [ DSC ]

Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Allergy Information Diagnosis Information Diagnosis Related Group Procedures Role

Guarantor Insurance Insurance Additional Info. Insurance Add'l Info Cert.

Accident Information Universal Bill Information Universal Bill 92 Information Mental Health Information Mental Health Legal Status Information Continuation Pointer

(e) Trigger Uses

Mental Health query on Admission history for a client; sent to ODS Mental Health query on Residential Placement history for a client; sent to ODS Mental Health query on R/CTO history for a client; sent to ODS Mental Health query on legal status history for a client; sent to ODS Mental Health query on demographic details for a client; sent to ODS Mental Health query on most recent legal status for a client; sent to ODS Mental Health query on most recent admission for a client; sent to ODS Mental Health query on status of CTO Transfer Out; sent to ODS Mental Health query on Contacts history for a client; sent to ODS Mental Health query on Cases for a client; sent to ODS

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

217

Trigger Events

Mental Health query on Episode for a client; sent to ODS Mental Health query on diagnosis history for a client; sent to ODS Mental Health query on MHRB Hearing history for a client; sent to ODS Mental health final registration check; sent to ODS Mental Health client search; sent to ODS

2.3.10.

A21 Patient Goes on a Leave of Absence


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A21 trigger event is generated to notify that an admitted patient has gone on a leave of absence. It is used for systems where a patient is still recorded as being admitted in the ward (ie they are expected to return), and puts that patient's current admission on suspension. (c) Usage Notes The HL7 Version 2.3 protocol does not provide a trigger event to cancel the A21 trigger event. To cancel 'patient goes on leave of absence', use the A22 trigger event (patient returns from 'leave of absence') with event date and time the same as the A21 trigger event to be cancelled. (d) Trigger Structure
ADT MSH EVN PID [ PD1 ] PV1 [ PV2 ] [ { DB1 } ] [ { OBX } ] ADT Message Message Header Event Type Patient Identification Additional Demographics Patient Visit Patient Visit Additional Info. Disability Information Observation / Result

218

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

[ { ZMH } ] [ { ZLE } ] [ { ZFA } ] ACK MSH MSA [ ERR ]

Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Acute health patient recording of leave from ward sent to DWH Mental health client recording of leave from ward; sent to ODS and DWH Mental health client recording of leave from residential unit; sent to ODS and DWH

2.3.11. A22 Patient Returns from a Leave of Absence


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A22 trigger event is generated to notify that a patient has returned from a leave of absence. It is used for systems where a bed is still assigned to the patient who has his or her current admission on suspend/hold and is returning to the hospital. It removes the state of suspension from the patient's admission. (c) Usage Notes The HL7 Version 2.3 protocol does not provide a trigger event to cancel the A22 trigger event. To cancel 'patient returns from leave of absence', use the A21 trigger event (patient goes on 'leave of absence') with event date and time the same as the A22 trigger event to be cancelled. (d) Trigger Structure
ADT MSH EVN PID ADT Message Message Header Event Type Patient Identification

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

219

Trigger Events

[ PD1 PV1 [ PV2 ] [ { DB1 [ { OBX [ { ZMH [ { ZLE [ { ZFA ACK MSH MSA [ ERR ]

} } } } }

] ] ] ] ]

Additional Demographics Patient Visit Patient Visit Additional Info. Disability Information Observation / Result Mental Health Information Mental Health Legal Status Information Funding Arrangement Information General Acknowledgment Message Header Message Acknowledgment Error

(e) Trigger Uses

Acute health patient recording of return from leave to ward sent to DWH Mental health client recording of return from leave to ward; sent to ODS and DWH Mental health client recording of return from leave to residential unit; sent to ODS and DWH

2.3.12. A24 Link Patient Information


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface from ODS Not Available for Mental Health interface to DWH (b) Description This trigger is used to link two or more patients, and does not involve the actual merging of patient information. Person records recorded in an A24 trigger event will remain distinct after processing. (c) Usage Notes This trigger event is used by ODS to transmit statewide UR numbers that have been linked. The receiving system must then process this. ODS will not receive A24 triggers, only send them. Refer to Clause 3.5.3 of the HL7 Version 2.3 protocol. Trigger A37 is used to unlink linked identifiers. This trigger requires two PID segments. (d) Trigger Structure (e) Trigger Uses Refer to HL7 Standard Version 2.3

Mental health client notification of statewide unit record numbers to be linked; sent to CMI

220

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

2.3.13. A31 Update Person Information


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The A31 trigger event relates only to the updating of person information on a Patient Master Index. It is similar to an A08 trigger event in that it can update a lot of fields, e.g. name, address, date of birth, financial class and the like. The difference is that an A08 trigger event relates to visit-specific data, not patient-specific data. (c) Usage Notes This trigger is used rather than A08 for updates to the demographic details of a client captured at Registration. (d) Trigger Structure (e) Trigger Uses Refer to HL7 Standard Version 2.3

Mental Health Client Update of Registration Details (demographics, alias and alerts); sent to ODS and DWH.

2.3.14. A37 Unlink Patient Information


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface from ODS Not Available for Mental Health interface to DWH (b) Description The A37 trigger event is generated to unlink two patient identifier segments previously transmitted via an A24 (link patient information) trigger event (see Clause 5.26). (c) Usage Notes This trigger is used by ODS to notify of a previous link (via A24) that has been reversed. The receiving system must then process this. This trigger requires two PID segments. (d) Trigger Structure Refer to HL7 Standard Version 2.3

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

221

Trigger Events

(e) Trigger Uses

Mental health client notification of statewide unit record numbers to be unlinked; sent to CMI

2.3.15. A45 Move Visit InformationVisit Number


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description Signals that an episode has been created for the wrong person, and notifies what the correct UR number for that episode is. (c) Usage Notes Signals a move of records identified by the data element 'prior visit number' (see MRG-5) and prior patient ID internal (see MRG-1) to the correct patient identifier identified in data element 'patient ID - internal' (see PID-3). Clause 3.5.2 of the HL7 Version 2.3 protocol further discusses issues related to implementing merge messages. This message is sent to ODS to assign an episode to a different client. (d) Trigger Structure
ADT MSH EVN PID [PD1] { MRG PV1 [ ZMH ] } ACK MSH MSA [ ERR ] ADT Message Message Header Event Type Patient Identification Additional Demographics Merge Information Patient Visit

General Acknowledgment Message Header Message Acknowledgment Error

222

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

(e) Trigger Uses

Mental health client change client for an episode; sent to ODS and DWH

2.3.16. R01 Unsolicited Transmission of an Observation Message


The following applies: (a) Status Mandatory for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Mandatory for Mental Health interface to DWH (b) Description The R01 trigger event is used to signal a create or update of an observation to a patient. (c) Usage Notes Different uses for this trigger are outlined in the OBX segment. (d) Trigger Structure
ORU MSH { [ PID [PD1] [{NTE}] [PV1 [PV2]] ] { [ORC] OBR {[NTE]} { [OBX] {[NTE]} } {[CTI]} } Observational Results (Unsolicited) Message Header

Patient Identification Additional Demographics Notes and Comments Patient Visit Patient Visit - Additional Info

Order common Observations Report ID Notes and comments Observation/Result Notes and comments Clinical Trial Identification

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

223

Trigger Events

} [ ZMH [DSC]

Mental Health Information Continuation Pointer

ACK MSH MSA

Acknowledgment Message header Message acknowledgment

(e) Trigger uses

Acute health patient recording of barthel index scores; sent to DWH Acute health patient recording of RUG ADL scores; sent to DWH Acute health patient recording of mechanical ventilation; sent to DWH Acute health patient recording of newborn details; sent to DWH Mental health client recording of wellbeing scores; sent to DWH Mental health client recording of death; sent to ODS and DWH

2.3.17. M02 Master Practitioner


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Not Available for Mental Health interface to DWH (b) Description The M02 trigger event is used by Mental Health service facilities to advise details of Mental Health workers. (c) Usage Notes Refer to the STF segment for further detail. (d) Trigger Structure Refer to HL7 Standard Version 2.3

224

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

(e) Trigger Uses

Mental health notification of health care professional; sent to ODS Mental Health notification of campuses for a HCP; sent to ODS Mental health notification of authorised psychiatrist for a campus; sent to ODS

2.3.18. M05 Master Location


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Mandatory for Mental Health interface to ODS Not Available for Mental Health interface to DWH (b) Description The M05 trigger event is used by Mental Health service facilities to advise of daily bed status, campus details, gazetted service details, subcentre details and program details. (c) Usage Notes Refer to the LCH segment for further detail. (d) Trigger Structure (e) Trigger Uses Refer to HL7 Standard Version 2.3

Mental health notification of establishment/campus daily bed status; sent to ODS Mental health update of campus details; sent to ODS Mental health update of gazetted service details; sent to ODS Mental health update of subcentre details; sent to ODS Mental health update of program details; sent to ODS Mental Health update of subcentre/program details; sent to ODS Mental Health update of held bed details; sent to ODS Mental Health update of bed details; sent to ODS

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

225

Trigger Events

2.3.19. MFQ Master Files Query


The following applies: (a) Status Not Available for Admitted Episode interface (Acute Health patients) to DWH Not Available for Emergency interface to DWH Optional for Mental Health interface to ODS Not Available for Mental Health interface to DWH (b) Description The MFQ trigger event is used by Mental Health service facilities to query on master file details. (c) Usage Notes Refer to the QRD/QRF segments for further detail. Responses are formatted the same as the master file update messages, with the query definition segments returned also. This trigger is used for queries on master file details. (d) Trigger Structure (e) Trigger Uses Refer to HL7 Standard Version 2.3

Mental health request for campus details; sent to ODS Mental health request for bed status details; sent to ODS

2.3.20. T12 Document Query


The following applies: (a) Status Optional for Admitted Episode interface (Acute Health patients) to DWH Optional for Emergency interface to DWH Not available for Mental Health Interface to ODS Optional for Mental Health interface to DWH (b) Description The T12 trigger event is used by Service Providers to request submission reports. (c) Usage Notes Refer to the QRD/QRF segments for further detail. Acknowledgements will be received on-line but the reports will not. Hard copies will be produced and couriered to the requesting service. (d) Trigger Structure

226

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Trigger Events

QRY MSH QRD [ QRF ] DOC

Document Query Message Header Query Definition Query Filter Document Response

MSH MSA [ERR] QRD [{ [EVN] PID PV1 TXA [{OBX}] }] [DSC]

Message Header Message Acknowledgement Error Query Definition Event Type Patient Identification Patient Visit Document Notification Observation Continuation Pointer

(e) Trigger Uses

Mental Health Request Submission Report Admitted Episode Request Submission Report

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

227

Chapter 3 Message Segments


3.1. General
All HL7 Version 2.3 protocol message segment definitions, types and descriptions will be followed. The associated data element definition, formats and usage will also be followed unless otherwise indicated. The following is noted for each field: (a) Sequence (Seq) The sequence number of the data element within the segment. (b) Length (Len) The maximum number of characters that one occurrence of the data element may occupy. (c) Data type (DT) Restrictions on the contents of the data element. (See HL7 Version 2.3 Clause 2.8.) Additional RAPID data types have been defined as follows: RS1 = <alias family name (ST)> ^ <alias given name (ST)> ^ <alias middle initial or name (ST)> ^ <alias suffix (ST)> ^ <alias prefix (ST)> ^ <alias degree (ST)> ^ <alias sex (IS)> ^ <alias date of birth (TS)> ^ <alias sequence (NM) > ^ <alias effective date (TS) > ^ <recorded by campus (ST) > RS2 = <quantity 1 (NM) > ^ <identifier 1 (ST) > ^ <identifier 2 (ST)> ^ <identifier 3 (ST) > ^ <identifier 4 (ST) > ^ <flag 1 (IS) > ^ <flag 2 (IS) > ^ <quantity 2 (NM) > ^ <quantity 3 (NM) > ^ <quantity 4 (NM) > ^ <quantity 5 (NM) > ^ <date 1 (TS)> ^ <flag 3 (IS)> (d) Optionality One of the following applies for each data element: (i) Required (R) Data element must be present for every transmission. (ii) Conditional (C) Data element must be present for specified trigger events. (iii) Optional (O) Data element need not be present for any transmission. (iv) Backward compatibility (B/X) Data element superseded. Appears for backward compatibility only.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

31

Message Segments

(e) Repetition (Rp/#) Whether the data element may repeat. A 'Y' indicates that repetition is indefinite or site-determined. An integer indicates repetition to the number of times specified in the integer. (f) Table (Tbl#) The number of the HL7 Version 2.3 table that defines the values for the data element. These values should be followed unless otherwise indicated. Additional RAPID variations have been included. (g) ID number (Item#) The small integer that uniquely identifies the data element in the HL7 Version 2.3 protocol. (h) Element name The descriptive name for the data element. (i) Usage Notes Usage notes are provided for data elements to assist health institutions and health information technology vendors with data element interpretation, use and implementation in the Victorian health information technology environment. (j) Victorian definition reference (Ref) Where an appropriate National Health Data Dictionary or Australian Bureau of Statistics item exists, its definition and format applies unless otherwise indicated in the usage notes. (k) Format Required format for the data element. (l) Example Sample of values that may be populated within this data element.

(m) AE Refers to Admitted Episode data element, previously known as a VAED data element. (n) EM Refers to Emergency data element, previously known as VEMD data element. (o) MH Refers to Mental Health data element, some of which were previously known as PRISM data elements.

3.2. Message Segment Descriptions


3.2.1. Message Header Segment (MSH)
The following applies: (a) Function The MSH segment contains the intent, source, destination, and some specifics of the syntax of a message. (b) Data elements and usage notes For relevant data elements and usage notes, see table below. Table 31. Message Header (MSH) Segment

32

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1 2 3

Len 1 4

DT ST ST

Opt R R O

Rp/#

Tbl#

Item# 00001 00002 00003

Element name Field separator Encoding characters Sending application

Usage Notes Value = | Values = ^~\& Allows institutions and software vendors to populate this field with software version generating this transaction.

Ref

Format

Example

180 HD

180 HD

00004

Sending facility

This is used to transmit the NHDD 50 Establishment Identifier/Campus Code of the sending system (includes CMI Server Code). Refer to Code List Book "Service Provider Code". Note: Variant to HL7 & NHDD

DHSODS or DHSDWH or DHSMSW BBBB

5 6

180 HD 180 HD

O R

00005 00006

Receiving application Receiving facility This is used to transmit the Establishment Identifier /Campus Code of the receiving system (includes CMI Server Code). Refer to Code List Book "Service Provider Code ". Note: Variant to HL7 & NHDD NHDD 50 DHSODS or DHSDWH or BBBB

7 8

26 40

TS ST

O O

00007 00008

Date/time of message Generated by transmitting system Security

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

33

Message Segments

Seq 9 10 11

Len 7 20 3

DT CM ST PT

Opt R R R

Rp/#

Tbl#

Item# 00009 00010 00011

Element name Message type Message control ID Processing ID

Usage Notes The message type and trigger event A number that uniquely identifies the message Values: Production = P Testing = D

Ref

Format

Example ADT^A01 or QRY^A19

12 13 14 15

8 15

ID NM

R O O O

0104

00012 00013 00014

Version ID Sequence number Continuation pointer

Value = 2.3

180 ST 2 ID

0155

00015

Accept Default value = AL acknowledgment type For immediate query, set to NE Application Default value = AL acknowledgment type Country code Values: AU for Australia NZ for New Zealand ISO 3166

16 17

2 2

ID ID

O O

0155

00016 00017

18 19

6 60

ID CE

O O

Y/3

0211

00692 00693

Character set Principal language of message Value = EN (for English) ISO 639

3.2.2. Message Acknowledgement (MSA) Segment


The following applies: (a) Function The MSA segment contains information sent while acknowledging another message.

34

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

(b) Data elements and usage notes DWH and ODS will be sending both positive and negative receipt (commit) and process (application) acknowledgements.
Acknowledgement Type Positive Receipt Acknowledgement Negative Receipt Acknowledgement Positive Process Acknowledgement Negative Process Acknowledgement Acknowledgement Code CA CE AA AE

Table 32. Message Acknowledgment (MSA) Segment

Seq 1 2 3 4 5 6

Len 2 20 80 15 1

DT ID ST ST NM ID

Opt R R O O B/X O

Rp/#

Tbl# 0008

Item# 00018 00010 00020 00021

Element name Acknowledgment code Message control ID Text message Expected sequence number

Usage Notes

Ref

Format AA

Example

AE/EM/MH: Unique trigger identifier

0102

00022 00023

Delayed Superseded acknowledgment type Error condition

100 CE

3.2.3. Error (ERR) Segment


The following applies:

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

35

Message Segments

(a) Function The ERR segment is used to add error comments to acknowledgment messages. (b) Data elements and usage notes DWH and ODS will be sending back error messages in the ERR-1 Error code and Location field. Warnings will also be notified in this field. If only warnings are generated for a trigger message, then the MSA-1 Acknowledgement Code will have a AA (Positive Process Acknowledgement) and warning numbers will be generated in ERR-1. When an error refers to a diagnosis, the error message will contain the error number, a dash, and then the ICD code it applies to. (In the error messages listed in the Business Rules book, the ICD code is denoted by a #.) Table 33. Error (ERR) Segment

Seq 1

Len 80

DT CM

Opt R

Rp/# Y

Tbl#

Item# 00024

Element name Error code and location

Usage Notes

Ref

Format A126

Example

A560 B049

3.2.4. Event Type (EVN) Segment


The following applies: (a) Function The EVN segment is used to communicate necessary trigger event information to receiving applications. (b) Data elements and usage notes For relevant data elements and usage notes, see table EVN segment. The following table defines the coding requirements for data elements in the EVN segment where indicated.

36

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name Operator ID

Rules To transmit Last Updated By User, populate <ID Number>; To transmit Last Updated By Campus, populate <Assigning authority> : <ID Number>^^^^^^^^<assigning authority>

Event Reason Code

Set this field to the appropriate code. To transmit details of an ISP, set this field to . ISP

Table 34. Event Type (EVN) Segment

Seq 1 2

Len 3 26

DT ID TS

Opt B/X R

Rp/#

Tbl# 0003

Item# 00099 00100

Element name Event type code Recorded Date/Time of event

Usage Notes Refer to HL7 2.3 Most systems will default to the system date/time when the transaction was entered, but they should also permit an override.

Ref

Format

Example

3 4

26 3

TS IS

O O 0062

00101 00102

Date/Time planned event Event reason code See above table. Refer to Code List Book Admission Event Type , Placement Event Type SA

60

XCN

0188

00103

Operator ID

MH: This is used to transmit Last Updated By User / Last Updated by Campus Refer to Code List Book Service Provider Code

123456789^^^^^^^^BB BB

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

37

Message Segments

Seq 6

Len 26

DT TS

Opt R

Rp/#

Tbl#

Item# 01278

Element name Event occurred

Usage Notes This field contains the date/time that the event actually occurred. For cancellations, this field should contain the date/time that the event being cancelled occurred. Note: Variant to HL7 & AS4700.1

Ref

Format

Example

3.2.5. Patient Identification (PID) Segment


The following applies: (a) Function The PID segment is used by all applications as the primary means of communicating patient identification information. This segment contains permanent patient identifying and demographic information that, for the most part, is not likely to change frequently. (b) Data elements and usage notes For relevant data elements and usage notes, see table PID Segment. RS1 Data Type structure is as follows : <alias family name>^<alias given name>^<alias middle initial or name>^<alias suffix>^<alias prefix>^<alias degree>^<alias sex>^<aliasdate of birth>^<alias sequence>^<alias effective date>^<recorded by campus> The following table defines the coding requirements for data elements in the PID segment where indicated.

38

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name Patient ID (internal ID)

Rules To transmit Local Unit Record Number use as <identifier type code>; PI Populate <assigning authority> with Campus Identifier : <ID>^^^<assigning authority>^PI

Patient ID (internal ID)

To transmit Statewide Unit Record Number use SWUR as <identifier type code>; Populate <assigning authority> with DHSODS : <ID>^^^DHSODS^SWUR

Patient ID (internal ID)

To transmit a message for a mental health client who is not registered statewide, set <ID> to UNREGISTERED and set <identifier type code> , to SWUR ; Populate <assigning authority> with DHSODS : UNREGISTERED^^^DHSODS^SWUR

Patient ID (internal ID)

To transmit CMI Client Number use as <identifier type code>; CI Populate <assigning authority> with CMI Identifier : <ID>^^^<assigning authority>^CI

Patient ID (internal ID)

To transmit Pension Number use PN as <identifier type code>; To transmit Pension Type populate <assigning authority> : <ID>^^^<assigning authority>^PN

Patient Name

To transmit Surname, populate <family name> ; To transmit First name, populate <given name> ; To transmit Middle Name, populate <middle initial or name> ; To transmit Title, populate <prefix> : <family name>^<given name>^<middle initial or name>^^<prefix>

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

39

Message Segments

Element Name Patient Alias

Rules To transmit Alias Surname, populate <alias family name> ; To transmit Alias First name, populate <alias given name> ; To transmit Alias Middle name, populate <alias middle initial or name> ; To transmit Alias Title, populate <alias prefix> ; To transmit Alias Identifier, populate <alias id> ; To transmit Alias Sex, populate <alias sex> ; To transmit Alias Date of Birth, populate <alias date of birth> ; To transmit Alias sequence, populate <alias sequence> ; To transmit Alias Effective Date, populate <alias effective date> ; To transmit Recorded By Campus, populate <recorded by campus> : <alias family name>^<alias given name>^<alias middle initial or name>^^<alias prefix>^<alias degree>^<alias sex>^< alias date of birth>^<alias sequence>^<alias effective date>^<recorded by campus>

Patient Address

To transmit Address, populate <street address> ; To transmit Locality (suburb), populate <other designation> ; To transmit State, populate <state or province> ; To transmit Postcode, populate <zip or postal code> : <street address>^<other designation>^^<state or province>^<zip or postal code>

SSN Number- Patient

Separate medicare number and code and suffix with a preceded by a space: 30993303651 ALB

Table 35. Patient Identification (PID) Segment

Seq 1 2

Len 4 20

DT SI CX

Opt O O

Rp/#

Tbl#

Item# 00104 00105

Element name Set ID-Patient ID Patient ID (external ID)

Usage Notes

Ref

Format

Example

Note: Variant to AS4700.1

310

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 3

Len 20

DT CX

Opt R

Rp/# Y

Tbl#

Item# 00106

Element name Patient ID (internal ID)

Usage Notes

Ref

Format

Example AE: 987659^^^BBBB^PI MH: 749987611^^^DHSOD S^SWUR~564432^^^B BBB^PI~656733^^^20 ^PN

NHDD The institution's unique patient identifier (e.g. medical 127 record number) Populate with as many identifiers as is necessary. Include Assigning Authority for each. Refer to NHDD data element 'Person identifier' AE: Previously known as Unit Record Number EM: Previously known as Patient Identifier MH: This is used to transmit Local Unit Record Number ~ Statewide Unit Record Number ~ CMI Client Identifier (system nbr)~ Pension Number & Benefit Type Refer to Code List Book Pension Benefit Type Note: Variant to AS4700.1 NHDD 121

20

CX

00107

Alternate patient ID

MH: This is used to transmit Statewide UR Linked To

MH: 1234567

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

311

Message Segments

Seq 5

Len 48

DT XPN

Opt C

Rp/# Y

Tbl#

Item# 00108

Element name Patient name

Usage Notes Conditional for trigger A01 AE: This is used to transmit Surname & First Name for DVA patients only MH: This is used to transmit Client Surname, First Name, Middle name and Title. Refer to Code List Book Title Note: Variant to HL7 & AS4700.1

Ref

Format

Example AE: Doe^John MH : Doe^John^Aaron^^01

6 7

48 26

XPN TS

O C

00109 00110

Mother's Maiden Name Date of birth Conditional for triggers A01 and A04 HL7 data element format to be used. Time optional Refer to NHDD data element 'Date of birth' AE & EM: This is used to transmit Birth Date MH: This is used to transmit Date of Birth Note: Variant to HL7 NHDD 36 19720612

312

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 8

Len 1

DT IS

Opt C

Rp/#

Tbl# 0001

Item# 00111

Element name Sex

Usage Notes Conditional for triggers A01 and A04 Refer to Code List Book "Sex" Note: Variant to HL7, AS4700.1 & NHDD

Ref NHDD 149

Format 2

Example

120 RS1

00112

Patient alias

Repeating data element for recording of Mental Health Name alias. Populate with as many occurrences as is necessary. MH: This is used to transmit Alias surname, firstname, middle name, title, sex, date of birth, alias sequence, effective date and campus the alias assigned by. Refer to Code List Book Title , Sex , Service Provider Code Note: Variant to HL7 & AS4700.1

MH: Jackson^Jane^Sarah^ ^05^^2^19601201^1^1 9980605^AAAA~Jacks on^Simone^^^04^^2^1 9701201^2^19980605 ^BBBB

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

313

Message Segments

Seq 10

Len 1

DT IS

Opt C

Rp/#

Tbl# 0005

Item# 00113

Element name Race

Usage Notes This element is used for indigenous status (aboriginality) Refer to NHDD data element 'Indigenous status' Conditional for triggers A01 and A04 AE & EM: Previously known as Aboriginality MH: This is used to transmit Indigenous Status Refer to Code List Book "Indigenous Status" Note: Variant to HL7 & AS4700.1

Ref NHDD 1

Format

Example

11

106 XAD

00114

Patient address

Full street address of patient. NHDD 16 Populate only one occurrence. See also NHDD data element 'Area of usual residence' AE & EM: Populate only locality and postcode MH: Populate with address, locality (suburb), postcode & state. Refer to Code List Book State

AE & EM: ^^Carnegie^^3163 MH: 123 Smith St ^^Collingwood^VIC^31 00

314

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 12

Len 4

DT IS

Opt O

Rp/#

Tbl#

Item# 00115

Element name County code

Usage Notes Superseded Refer to PID-11-Patient address component 9 Note: Variant to HL7

Ref

Format

Example

13

40

XTN

00116

Phone number- Home MH: This is used to transmit Home Phone Number. Populate only one occurrence. Phone numberBusiness Language-Patient Refer to NHDD data element 'Preferred language' MH & EM: Previously known as Preferred Language Refer to Code List Book "Preferred Language" NHDD 132

MH: 0399999999

14 15

40 60

XTN CE

O O

Y 0296

00117 00118

01

16

IS

0002

00119

Marital status

Data element 'Marital status' Conditional for triggers A01 and A04 AE & MH: This is used to transmit Marital Status Refer to Code List Book "Marital Status" Note: Variant to HL7 & AS4700.1

NHDD 89 AE & MH: 2

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

315

Message Segments

Seq 17

Len 3

DT IS

Opt O

Rp/#

Tbl# 0006

Item# 00120

Element name Religion

Usage Notes MH: This is used to transmit Religion. Refer to Code List Book Religion

Ref

Format 2233

Example

18 19

20 16

CX ST

O C

00121 00122

Patient account number SSN Number- Patient Use the Medicare number, plus the line number (medicare code) Refer to NHDD data element 'Medicare number' Conditional for trigger A01 and A04 AE & MH & EM: This is used to transmit medicare number (including medicare code) and suffix Separate medicare number (including medicare code) and suffix with a space. Note: Variant to HL7 & AS4700.1 NHDD 91 30993303651 ALB

20 21

25 20

DLN CX

O O Y

00123 00124

Driver's licence number-Patient Mother's identifier This is the mother's unique identifier where this patient is the child of the mother

316

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 22

Len 3

DT IS

Opt O

Rp/#

Tbl# 0189

Item# 00125

Element name Ethnic group

Usage Notes Not to be used for aboriginality or country of birth Patient's country of birth Refer to NHDD data element 'Country of birth' Conditional for triggers A01 and A04 AE & EM: Previously known as Birth Place MH: This is used to transmit Country of Birth Refer to Code List Book "Country of Birth" Note: Variant to HL7 & AS4700.1

Ref

Format

Example

23

60

ST

00126

Birthplace

NHDD 35 8206

24 25 26 27

2 2 4 60

ID NM IS CE

O O O O Y

0136

00127 00128

Multiple birth indicator Refer to NHDD data element 'Birth plurality' Birth order Citizenship Veteran's military status Use the Australian Veterans Affairs File Number AE: This is used to transmit DVA Number Refer to NHDD data element 'Birth order'

NHDD 20 NHDD 19

0171 0172

00129 00130

NHDD 204

AE: VX123456

28

80

CE

00739

Nationality

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

317

Message Segments

Seq 29

Len 26

DT TS

Opt O

Rp/#

Tbl#

Item# 00740

Element name Patient Death Date and Time

Usage Notes MH: This is used to transmit Date of Death Time optional

Ref

Format

Example MH: 199805250100

30

ID

0136

00741

Patient Death Indicator

MH: Set to Y if date of death is not null.

MH: Y

3.2.6. Patient Visit (PV1) Segment


The following applies: (a) Function The PV1 segment is used by Registration/ADT applications to communicate information on a visit specific basis. (b) Data elements and usage notes For relevant data elements and usage notes, see table below. The following table defines the coding requirements for data elements in the PV1 segment where indicated.
Element Name Assigned Patient Location Rules To transmit Accommodation Type, populate <person location type> ; To transmit Subcentre, populate <point of care> ; To transmit Inpatient/Community indicator, populate <location status> : <point of care>^^^^<location status>^<person location type> Attending Doctor To transmit Contact Clinician Code, populate <ID> ; To transmit Discipline, populate <Degree> ; Set <Assigning authority> to campus code the user is logged in to : <ID>^^^^^^<degree>^^<assigning authority> Visit Number Discharged to Location For MH Registration, set to REGISTRATION. Note: This field repeats up to 5 times only.

318

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name Discharged to Location Discharged to Location Discharged to Location

Rules If Discharge disposition = transfer, Discharged to location is mandatory, containing only one transfer code If Discharge disposition = home, Discharged to location is mandatory, containing up to 5 repeating Separation Referral codes. To transmit Separation Transfer Code, populate <identifier> and set <name of coding system> to TRF ; To transmit Separation Referral Code, populate <identifier> and set <name of coding system> to REF ; To transmit Source of referral to Palliative Care, populate <identifier> and set <name of coding system> to PAL : <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)>

Discharged to Location (EM)

To transmit Transfer destination, populate <identifier> : <identifier>

Discharged to Location (MH)

To transmit Referral Type Code, populate <identifier> and set <name of coding system> to RTYP ; To transmit Referred to Campus, populate <identifier> and set <name of coding system> to RCMP ; To transmit Referred to Subcentre, populate <identifier> and set <name of coding system> to RSBC : <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)>

Table 36. Patient Visit (PV1) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

319

Message Segments

Seq 1 2

Len 4 1

DT SI IS

Opt O R

Rp/#

Tbl#

Item# 00131

Element name Set ID-Patient visit Patient class

Usage Notes

Ref

Format

Example

0004

00132

Intended mode of treatment Admitted patient: S = Same day patient I = Overnight patient Refer to NHDD data element concept 'Admitted patient' Non-admitted patient: P = Pre-admit patient E = Emergency patient C = Mental Health community client Refer to NHDD data element concept 'Non-admitted patient' Note: Variant to HL7 & AS4700.1

NHDD 11 & 104

EM: E AE: I MH: S

320

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 3

Len 80

DT PL

Opt C

Rp/#

Tbl#

Item# 00133

Element name Assigned patient location

Usage Notes Conditional for triggers A01 and A02 AE: Previously known as Accommodation Type MH: This is used to transmit Subcentre Code, Subcentre Type and Accommodation Type Refer to Code List Book "Accommodation Type", Subcentre Type Note: Variant to HL7

Ref

Format

Example

AE: ^^^^^8 MH: 1234^^^^I^2

IS

0007

00134

Admission type

Conditional for trigger A01 The circumstance under which the patient will be admitted: AE: This is used to transmit Admission Type EM: Previously known as Type of Visit MH: This is used to transmit Admission Type Refer to Code List Book "Admission Type", Type of Visit Note: Variant to HL7 AE: M EM: 1 MH: O

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

321

Message Segments

Seq 5

Len 20

DT CX

Opt O

Rp/#

Tbl#

Item# 00135

Element name Pre-admit number

Usage Notes Planning number for identification Primarily used as source of identification, before the admission number Identify for use by other systems to attach details MH: This is used to transmit Linked Admission Id

Ref

Format

Example

80

PL

00136

Prior patient location

Conditional for trigger A02 Refer to PV1-3 AE & MH: Populate with previous location when changing location. Refer to Code List Book "Accommodation Type" Note: Variant to HL7 & AS4700.1 AE & MH: E

60

XCN

0010

00137

Attending doctor

The attending doctor providing services to the patient MH: This is used to transmit Contact clinician code, discipline and campus Refer to Code List Book Discipline , Service Provider Code

MH: 123456^^^^^^03^^BBB B

322

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 8

Len 60

DT XCN

Opt C

Rp/# Y

Tbl# 0010

Item# 00138

Element name Referring doctor

Usage Notes Clinician who referred patient to the consulting doctor Conditional for trigger A04 EM: Previously known as Referred By Refer to Code List Book "Referred By" Note: Variant to HL7 & AS4700.1

Ref

Format

Example

EM: 1

60

XCN

0010

00139

Consulting doctor

Consultant responsible for the care of the patient, including salaried specialist, visiting medical officer AE: Previously known as Clinical Sub-program Refer to Code List Book "Clinical Sub-program" Note: Variant to AS4700.1

10

IS

0069

00140

Hospital service

AE: 010

11 12 13

80 2 2

PL IS IS

O O O 0087 0092

00141 00142 00143

Temporary location Pre-admit test indicator Readmission indicator

Refer to PV1-3 and PV1-6 Indicate whether preadmission test is required AE: This is used to transmit Admission/Readmission to Rehabilitation Refer to Code List Book "Admission/Readmission to Rehabiliation"

AE: 0

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

323

Message Segments

Seq 14

Len 3

DT IS

Opt C

Rp/#

Tbl# 0023

Item# 00144

Element name Admit source

Usage Notes Conditional for trigger A01 Refer to NHDD data elements 'Source of referral to acute hospital or private psychiatric hospital' and 'Source of referral to public psychiatric hospital' AE & MH: This is used to transmit Admission Source Refer to Code List Book "Admission Source" Note: Variant to HL7, AS4700.1 & NHDD

Ref NHDD 385 & 150

Format

Example

AE: C MH: 13

15 16 17

2 2 60

IS IS XCN

O O O

0009 0099

00145 00146 00147

Ambulatory status VIP indicator Admitting doctor Note: Variant to AS4700.1

0010

324

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 18

Len 2

DT IS

Opt C

Rp/#

Tbl# 0018

Item# 00148

Element name Patient type

Usage Notes Patient's accommodation status Conditional on AE and MH submissions. Not required for EM. AE & MH: Previously known as Care Type MH: Value = 5 Refer to Code List Book "Care Type" Note: Variant to HL7 & AS4700.1

Ref

Format

Example

AE: U MH: 5

19

20

CX

00149

Visit number

This field contains the unique number assigned to each patient visit (formal admission) AE: Previously known as Unique Key EM: This is used to transmit Visit Number MH: This is used to transmit Admitted Episode Id Note: Variant to HL7 & AS4700.1

0087654321

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

325

Message Segments

Seq 20

Len 50

DT FC

Opt C

Rp/# Y

Tbl# 0064

Item# 00150

Element name Financial class

Usage Notes

Ref

Format

Example

Primary class for identifying NHDD source of reimbursement, for 118 & 397 example: Conditional for triggers A01 and A04 AE & MH: Previously known as Account Class EM: Previously known as Compensable Status Refer to Code List Book "Account Class" and "Compensable Status" Note: Variant to HL7

AE: M EM: 5 MH: M

21 22 23 24 25 26 27 28 29 30

2 2 2 2 8 12 3 2 1 8

IS IS IS IS DT NM NM IS IS DT

O O O O O O O O O O Y Y Y Y

0032 0045 0046 0044

00151 00152 00153 00154 00155 00156 00157

Charge price indicator Courtesy code Credit rating Contract code Contract effective date Contract amount Contract period Interest code Transfer to bad debt code Transfer to bad debt date

0073 0110

00158 00159 00160

326

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 31 32 33 34 35 36

Len 10 12 12 1 8 3

DT IS NM NM IS DT IS

Opt O O O O O C

Rp/#

Tbl# 0021

Item# 00161 00162 00163

Element name Bad debt agency code Bad debt transfer amount Bad debt recovery amount Delete account indicator Delete account date

Usage Notes

Ref

Format

Example

0111

00164 00165

0112

00166

Discharge disposition Conditional for trigger A03 AE: Previously known as Separation Type EM: Previously known as Departure Status MH: This is used to transmit Separation Type (A03) and Leave Type (A21) Refer to Code List Book Separation Type , Ward Leave Type , Placement Leave Type Note: Variant to HL7, AS4700.1 & NHDD

NHDD 96 & 359

AE: D EM: 7 MH: A

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

327

Message Segments

Seq 37

Len 25

DT CE

Opt O

Rp/# Y/5

Tbl# 0113

Item# 00167

Element name Discharged to location

Usage Notes AE: Previously known as Separation Transfer Code, Separation Referral Code and Source of Referral to Palliative Care EM: Previously known as Transfer Destination MH: This is used to transmit Separation Referral Code, Referral Type, Referred to Campus, Referred to Subcentre Refer to Code List Book "Service Provider Code" and "Separation Referral" and "Referral Type" Note: Variant to HL7 & AS4700.1

Ref

Format BBBB

Example

M^^REF~S^^REF MH: 01^^RTYP~BBBB^^R CMP

38

IS

0114

00168

Diet type

39

IS

0115

00169

Servicing facility

AE & EM & MH: This is used to transmit Establishment Id (Campus Code) Refer to Code List Book "Service Provider Code"

NHDD 50

BBBB

40 41 42

1 2 80

IS IS PL

O O O

0116 0117

00170 00171 00172

Bed status Account status Pending location

Note:

Variant to HL7

328

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 43 44

Len 80 26

DT PL TS

Opt O C

Rp/#

Tbl#

Item# 00173 00174

Element name Prior temporary location Admit date/time

Usage Notes

Ref

Format

Example

Conditional for triggers A01 and A04 HL7 data element format to be used. Refer to NHDD data element 'Admission date' AE: Previously known as Admission Date/Time EM: Previously known as Arrival Date/Time MH: This is used to transmit Admission Date/Time (A01) Note: Variant to HL7 & AS4700.1

NHDD 8 & 358

199808271537

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

329

Message Segments

Seq 45

Len 26

DT TS

Opt C

Rp/#

Tbl#

Item# 00175

Element name Discharge date/time

Usage Notes Conditional for trigger A03 HL7 data element format to be used Refer to NHDD data element 'Discharge date' AE: Previously known as Separation Date/Time EM: Previously known as Departure Date/Time MH: This is used to transmit Separation Date/Time Note: Variant to HL7 & AS4700.1

Ref NHDD 43

Format

Example

199808271833

46 47 48 49 50 51 52

12 12 12 12 20 1 60

NM NM NM NM CX IS XCN

O O O O O O O Y 0192 0326 0010

00176 00177 00178 00179 00180 01226 01224

Current patient balance Total charge Total adjustments Total payments Alternate visit ID Visit indicator Other healthcare provider MH: This is used to transmit Shared Care Refer to Code List Book Shared Care Flag MH: Y

330

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

3.2.7. Patient Visit - Additional Information (PV2) Segment


The following applies: (a) Function The PV2 segment is a continuation of visit-specific information contained in the PV1 segment. (b) Data elements and usage notes For relevant data elements and usage notes, see PV2 table below. Table 37. Patient Visit - Additional Information (PV2) Segment

Seq 1 2 3

Len 80 60 60

DT PL CE CE

Opt O O C

Rp/#

Tbl# 0129

Item# 00181 00182 00183

Element name Prior pending location Accommodation code Admit reason

Usage Notes

Ref

Format

Example

Conditional for trigger A01 AE/MH: Previously known as Criterion for Admission Refer to Code List Book "Criterion for Admission" Note: Variant to HL7 & AS4700.1

AE/MH: B

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

331

Message Segments

Seq 4

Len 60

DT CE

Opt C

Rp/#

Tbl#

Item# 00184

Element name Transfer reason

Usage Notes Conditional for trigger A01 AE: Previously known as Reason for Critical Care Transfer MH: This is used to transmit Transfer Reason. Refer to Code List Book "Reason for Critical Care Transfer" and "Transfer Reason" Note: Variant to HL7 & AS4700.1

Ref

Format AE: W MH: 5

Example

5 6 7 8

25 25 2 26

ST ST IS TS

O O O O

00185 00186 0130 00187 00188

Patient valuables Patient valuables location Visit user code Expected admit date Time optional MH: This is used to transmit Expected return (from leave) date Note: Variant to AS4700.1 Variant to AS4700.1 MH: 19980811

26

TS

00189

Expected discharge date

Note:

332

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 10

Len 3

DT NM

Opt C

Rp/#

Tbl#

Item# 00711

Element name Estimated length of inpatient stay

Usage Notes Conditional for trigger A01 AE: Previously known as Intended Duration of Stay MH: This is used to transmit Intended Duration of Stay Refer to Code List Book Intended Duration of Stay Note: Variant to HL7

Ref NHDD 76

Format AE: 2 MH: 2

Example

11

NM

00712

Actual length of inpatient stay Visit description Referral source code

See also NHDD data element NHDD 'Length of stay' 119

12 13

50 90

ST XCN

O O

00713 00714

See also NHDD data element EM/AE: 'Source of referral' NHDD 50 EM & AE: Previously known as Transfer Source MH: This is used to transmit Source of Referral Refer to Code List Book Source of Referral MH: NHDD 385 & 150

AE & EM: BBBB MH: 31

14 15 16 17

8 1 1 8

DT ID IS DT

O O O O 0136 0213

00715 00716 00717 00718

Previous service date Employment illness related indicator Purge status code Purge status date

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

333

Message Segments

Seq 18

Len 6

DT IS

Opt C

Rp/#

Tbl# 0214

Item# 00719

Element name

Usage Notes

Ref

Format AE: 6 MH: 7

Example

Special program code Conditional for trigger A01, Optional for other triggers. AE & MH: Previously known as Program Funding Source Refer to Code List Book "Program Funding Source" Note: Variant to HL7

19 20 21 22 23 24

1 1 1 1 90 2

ID NM IS ID XON IS

O O O O O O Y

0136

00720 00721

Retention indicator Expected number of insurance plans Visit publicity code Visit protection indicator Clinic organization name Patient status code See also NHDD data element NHDD 'Patient accommodation 118 eligibility status'

0215 0136

00722 00723 00724

0216

00725

25 26 27 28 29

1 8 2 8 8

IS DT IS DT DT

O O O O O

0217

00726 00727

Visit priority code Previous treatment date Expected discharge disposition Signature on file date First similar illness date AE: Previously known as Onset Date AE: 19980304

0112

00728 00729 00730

334

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 30 31

Len 3 2

DT IS IS

Opt O O

Rp/#

Tbl# 0218 0219

Item# 00731 00732

Element name Patient charge adjustment code Recurring service code

Usage Notes

Ref

Format

Example

AE & MH: Previously known as Intention to readmit within 28 days Refer to Code List Book "Intention to Readmit within 28 Days

32 33 34 35 36 37

1 26 2 2 1 1

ID TS ID ID ID ID

O O O O O O

0136

00733 00734

Billing media code Expected surgery date & time Military partnership code Military nonavailability code Newborn baby indicator Baby detained indicator See also NHDD references to 'Newborns'

0136 0136 0136 0136

00735 00736 00737 00738

3.2.8. Patient Additional Demographic (PD1) Segment


The following applies: (a) Function detail. The PD1 segment is an optional segment used by the Registration/ADT application to communicate additional demographic

(b) Data elements and usage notes For relevant data elements and usage notes, see PD1 table below. Table 38. Patient Additional Demographic (PD1) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

335

Message Segments

Seq 1

Len 2

DT IS

Opt C

Rp/# Y

Tbl# 0223

Item# 00755

Element name Living Dependency

Usage Notes MH: This is used to transmit Living Status Conditional for trigger A01 Refer to Code List Book "Living Status" Note: Variant to HL7

Ref

Format MH: 3

Example

IS

0220

00742

Living Arrangement

AE & MH: This is used to transmit Carer Availability Refer to Code List Book "Carer Availability Note: Variant to HL7

NHDD 22 (v 6.0)

AE & MH: 1

3 4

90 90

XON XCN

O O

Y Y

00756 00757

Patient Primary Facility Patient Primary Care Provider Name & ID No. Student Indicator Handicap Living Will Organ Donor Separate Bill Duplicate Patient Publicity Indicator Protection Indicator

5 6 7 8 9 10 11 12

2 2 2 2 2 2 1 1

IS IS IS IS ID CX CE ID

O O O O O O O O Y

0231 0295 0315 0316 0136

00745 00753 00759 00760 00761 00762

0125 0129

00743 01283

336

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

3.2.9. Diagnosis (DG1) Segment


The following applies: (a) Function The DG1 segment contains patient diagnosis information of various types. This segment is used to send multiple diagnoses. (b) Data elements and usage notes For relevant data elements and usage notes, see DG1 table below. The following table defines the coding requirements for data elements in the DG1 segment where indicated.
Element Name Diagnosis Code Rules See table below. <Identifier> is a code ; <text> is associated description ; <name of coding system> specifies what codeset is being transmitted ; <alternate identifier> is used to transmit ICD prefix : <identifier>^<text>^<name of coding system>^<alternate identifier> Diagnosis Clinician To transmit Clinician Code, populate <ID> ; To transmit Clinican Discipline, populate <degree> ; To transmit Clinician Campus, populate <assigning authority> : <ID>^^^^^^<degree>^^<assigning authority>

The first four components of diagnosis code are used in differing ways according to the type of diagnosis. Table 39. Use of Diagnosis Code (DG1-3) Field

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

337

Message Segments

Type of diagnosis ICD Code

<Identifier> H571 (ICD diagnosis code)

<Text>

<Name of Coding System> ICD10AM P

<Alternate Identifier>

(Diagnosis type)

Nature of Main Injury Ref: NHDD 87

13 (Nature of main injury code) 22 (Body region code)

NATINJ

N/A

Body Region

BODREG

N/A

Description of Injury Ref: NHDD 99 Injury Cause

N/A

Cricket ball (Description of injury)

DESCINJ

N/A

24 (Injury cause code)

INJCAU

N/A

Human Intent Ref: NHDD 382 Type of Place Where Injury Occurred Ref: NHDD 384 Activity When Injured

1 (Human intent code) A (Place code) S (Activity code)

HUMINT

N/A

TYPLC

N/A

ACTINJ

N/A

Table 310. Diagnosis (DG1) Segment

338

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1 2 3

Len 4 2 60

DT SI ID CE

Opt R (B) R R

Rp/#

Tbl#

Item# 00375

Element name Set ID DG1 Diagnosis Coding Method Diagnosis Code

Usage Notes AE: Diagnosis Code Sequence Number.

Ref

Forma t

Example

0053 0051

00376 00377

Refer to table above for coding of this data element Refer to Code List Book Diagnosis Type Note: Variant to HL7

NHDD 387 & 232

AE/MH: H571^^ICD10AM^P EM: H571^^ICD10AM^P 13^^NATINJ 22^^BODREG ^Cricket ball^DESCINJ 24^^INJCAU 1^^HUMINT A^^TYPLC S^^ACTINJ

4 5

40 26

ST TS

B C

00378 00379

Diagnosis Description Diagnosis Date/Time MH: This is used to transmit Diagnosis Date Time optional Note: Variant to HL7 Variant to HL7, not required MH: 19981111

6 7

2 60

IS CE

O B

0052 0118

00380 00381

Diagnosis Type Major Diagnosis Category

Note:

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

339

Message Segments

Seq 8 9 10 11 12 13 14 15

Len 60 2 2 60 3 12 4 10

DT CE ID IS CE NM CP ST NM

Opt B B B B B B B B

Rp/#

Tbl# 0055 0136 0056 0083

Item# 00382 00383 00384 00385 00386 00387 00388 00389

Element name Diagnostic Related Group DRG Approval Indicator DRG Grouper Review Code Outlier Type Outlier Days Outlier Cost Grouper Version and Type Diagnosis Priority

Usage Notes

Ref

Forma t

Example

MH: This is used to transmit Diagnosis Event Sequence Number. Note: Variant to HL7

MH: 1

16

60

XCN

00390

Diagnosis Clinician

MH: This is used to transmit Clinician Code, Discipline and Campus. Refer to Code List Book "Discipline , Service Provider Code

MH: 123456^^^^^^02^^BBB B

17 18 19

3 1 26

IS ID TS

O O O

0228 0136

00766 00767 00768

Diagnosis Classification Confidential Indicator Attestation Date/Time

340

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

3.2.10. Diagnosis Related Group (DRG) Segment


The following applies: (a) Function The DRG segment contains diagnoses-related grouping information of various types. This segment is used to send the DRG information. (b) Data elements and usage notes For relevant data elements and usage notes, see DRG table below. Table 311. Diagnosis Related Group (DRG) Segment

Seq 1

Len 60

DT CE

Opt R

Rp/#

Tbl# 0055

Item# 00382

Element name Diagnosis Related Group

Usage Notes AE: Previously known as DRG Hosp. Gen. Note: Variant to HL7 & NHDD

Ref NHDD 42

Format

Example AE: 415

2 3 4 5 6 7 8 9 10

26 2 2 60 3 12 1 9 1

TS ID IS CE NM CP IS CP ID

O O O O O O O O O 0136 0229 0136 0056 0083

00769 00383 00384 00385 00386 00387 00770 00771 00767

DRG Assigned Date/Time DRG Approval Indicator DRG Grouper Review Code Outlier Type Outlier Days Outlier Cost DRG Payor Outlier Reimbursement Confidential Indicator

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

341

Message Segments

3.2.11. Procedure (PR1) Segment


The following applies: (a) Function The PR1 segment contains information relative to various types of procedures that can be performed on a patient. This segment is used to send multiple procedures. (b) Data elements and usage notes For relevant data elements and usage notes, see table PR1 segment below. The following table defines the coding requirements for data elements in the PR1 segment where indicated.

342

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name Procedure Code

Rules See table below. <Identifier> is a code for what is contained in the segment; <text> is used for descriptions associated with the <identifier>; ECT course number, reason, or variation reason ; <name of coding system> specifies what codeset is being transmitted ; <alternate identifier> is used to transmit maximum number of treatments in an ECT course : <identifier>^<text>^<name of coding system>^<alternate identifier>

Procedure Date/Time

If Type of Procedure is an ICD code, populate this field with Procedure Date/Time (where procedure code is an ICD code). If Type of Procedure is ECT Course, populate this field with Consent Date/Time (Proc Code = ECTCOURSE) ; If Type of Procedure is ECT Treatment, populate this field with ECT Date/Time (Proc. Code = ECTTREAT) ; If Type of Procedure is Start Mechanical Restraint, populate this field with MR Start Date/Time (Proc. Code = STARTMR) ; If Type of Procedure is End Mechanical Restraint, populate this field with MR End Date/Time (Proc. Code = ENDMR) ; If Type of Procedure is Start Seclusion, populate this field with Seclusion Start Date/Time (Proc. Code = STARTSEC) ; If Type of Procedure is End Seclusion, populate this field with Seclusion End Date/Time (Proc. Code = ENDSEC) ;

Procedure Functional Type

If Type of Procedure is Start Mechanical Restraint, populate this field with Form of restraint (Proc. Code = STARTMR) ; If Type of Procedure is ECT Treatment, populate this field with ECT Type (Proc. Code = ECTTREAT).

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

343

Message Segments

Element Name Procedure Practitioner

Rules To transmit Clinician Code, populate <ID> ; To transmit Clinican Discipline, populate <degree> ; To transmit Clinician Campus, populate <assigning authority> ; Set <identifier type code> to AUTH (authorised by), APPR (approved by), SUP (supervised by), or ADMIN (administered by) as appropriate : <ID>^^^^^^<degree>^^<assigning authority>^^^^<identifier type code>

Anesthesiologist

To transmit Anaesthetist Name, populate <family name> : ^<family name>

The first four components of procedure code are used in differing ways according to the type of procedure. Table 312. Use of Procedure Code (PR1-3) Field

Type of procedure ICD Code

<Identifier> 5600100 (ICD procedure code) CAT scan

<Text>

<Name of Coding System> ICD10AM

<Alternate Identifier> N/A

(Associated description) Eye examination (Associated description) 1 (Holds course number) N/A 6 (Maximum number of treatments in the course) 2 (Treatment number) 6 (Maximum number of treatments in the course) VEMD N/A

Emergency Procedure Code

83 (Emergency procedure code)

ECT Course

ECTCOURSE

ECT Treatment

ECTTREAT

1 (Holds course number)

344

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Type of procedure Start Mechanical Restraint

<Identifier> STARTMR 1

<Text>

<Name of Coding System> N/A

<Alternate Identifier> N/A

(Holds reason code) End Mechanical Restraint ENDMR 2 (Holds Variation reason code) Start Seclusion STARTSEC 1 (Holds reason code) End Seclusion ENDSEC 2 (Holds Variation reason code) N/A N/A N/A N/A N/A N/A

Table 313. Procedure (PR1) Segment

Seq 1 2

Len 4 2

DT SI IS

Opt R (B) R

Rp/#

Tbl#

Item# 00391

Element name Set ID PR1 Procedure Coding Method

Usage Notes AE: Procedure Code Sequence Number

Ref

Format

Example

0089

00392

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

345

Message Segments

Seq 3

Len 80

DT CE

Opt R

Rp/#

Tbl# 0088

Item# 00393

Element name Procedure Code

Usage Notes Refer to table above for coding of this data element Refer to Code List Book Reason for Restraint , Reason for Seclusion , Restraint Variation Reason , Seclusion Variation Reason

Ref NHDD 387 & 232

Format

Example AE: 5600100^CAT Scan^ICD10AM EM: 83^Eye examination^VEMD MH (ECT course): ECTCOURSE ^1^^5 MH (ECT Treatment): ECTTREAT^1^2^6 MH (Start MR): STARTMR ^1 MH (End MR): ENDMR ^2 MH (Start Seclusion): STARTSEC^1 MH (End Seclusion): ENDSEC^2

4 5

40 26

ST TS

B C

00394 00395

Procedure Description Procedure Date/Time Refer to table above for coding of this data element Note: Variant to HL7 MH: 19980101

346

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 6

Len 2

DT IS

Opt C

Rp/#

Tbl# 0230

Item# 00396

Element name Procedure Functional Type

Usage Notes Refer to table above for coding of this data element Refer to Code List Book Form of Restraint , ECT Type Note: Variant to HL7

Ref

Format MH: 1

Example

7 8 9 10 11 12

NM

O B O O B C Y Y 0010 0010 Y 0010 0019

00397 00398 00399 00400 00401 00402

Procedure Minutes Anesthesiologist Anesthesia Code Anesthesia Minutes Surgeon Procedure Practitioner MH: This is used to transmit Authorised By (Proc. Code = ECTCOURSE or STARTMR or STARTSEC) / Approved By (Proc. Code = STARTMR or STARTSEC) / Supervised By (Proc Code = STARTMR or STARTSEC) / Administered By (Proc Code = ECTTREAT) / Discipline (Proc Code = ECTCOURSE, ECTTREAT, STARTMR or STARTSEC) Refer to Code List Book Service Provider Code , Discipline Note: Variant to HL7 MH:123456^^^^^^04^^ AAAA^^^^ADMIN MH: This is used to transmit ECT Anaesthetist MH: ^Joe Blogges

120 XCN 2 4 IS NM

120 XCN 230 XCN

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

347

Message Segments

Seq 13

Len 60

DT CE

Opt C

Rp/#

Tbl# 0059

Item# 00403

Element name Consent Code

Usage Notes MH: This is used to transmit Consent Type Refer to Code List Book Consent Type Note: Variant to HL7

Ref

Format MH: 1

Example

14

NM

00404

Procedure Priority

MH: This is used to transmit MR Seq (Proc. Code = STARTMR or ENDMR) / Seclusion Seq (Proc. Code = STARTSEC or ENDSEC) Note: Variant to HL7

MH: 1

15

80

CE

00772

Associated Diagnosis Code

3.2.12. Insurance (IN1) Segment


The following applies: (a) Function The IN1 segment contains insurance policy coverage information.

(b) Data elements and usage notes For relevant data elements and usage notes, see IN1 table below. Table 314. Insurance (IN1) Segment

348

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1

Len 4

DT SI

Opt C

Rp/#

Tbl#

Item# 00426

Element name Set ID IN1

Usage Notes Required for the sending of Insurance Details. Value = 1 Note: Variant to HL7 Variant to HL7

Ref

Format 1

Example

2 3

60 59

CE CX

O C Y

0072

00368 00428

Insurance Plan ID Insurance Company ID

Note:

Required for the sending of Insurance Details. Conditional for trigger A01 AE & MH: This is used to transmit Health Insurance Fund Refer to Code List Book "Health Insurance Fund" Note: Variant to HL7

AE & MH: HBA

4 5 6 7 8 9 10

130 XON 106 XAD 48 40 12 XPN XTN ST

O O O O O O O

Y Y Y Y

00429 00430 00431 00432 00433

Insurance Company Name Insurance Company Address Insurance Co. Contact Person Insurance Co. Phone Number Group Number Group Name Insured Group Emp s ID

130 XON 12 CX

Y Y

00434 00435

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

349

Message Segments

Seq 11 12 13 14 15

Len

DT

Opt O O O O C

Rp/# Y

Tbl#

Item# 00436 00437 00438 00439 00440

Element name Insured Group Emp s Name Plan Effective Date Plan Expiration Date Authorization Information Plan Type

Usage Notes

Ref

Format

Example

130 XON 8 8 55 3 DT DT CM IS

Required for the sending of Insurance Details. Conditional for trigger A01 AE & MH: This is used to transmit Level of Insurance Refer to Code List Book "Level of Insurance" Note: Variant to HL7 & NHDD

NHDD 75

AE & MH: 3

16 17 18 19 20 21 22

48 2 26

XPN IS TS

O O O O O O O

00441 00442 00443

Name of Insured Insured Relationship s to Patient Insured Date of s Birth Insured Address s Assignment of Benefits Coordination of Benefits Coord of Ben. Priority

106 XAD 2 2 2 IS IS ST

00444 00445 00446 00447

350

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39

Len 2 8 2 8 2 15 26 60 2 2 4 4 8 15 12 12 4

DT ID DT ID DT IS ST TS XCN IS IS NM NM IS ST CP CP NM

Opt O O O O O O O O O O O O O O O O O

Rp/#

Tbl#

Item# 00448 00449 00450 00451 00452 00453 00454 00455 00456 00457 00458 00459 00460 00461 00462 00463 00464

Element name Notice of Admission Flag Notice of Admission Date Report of Eligibility Flag Report of Eligibility Date Release Information Code Pre-Admit Cert (PAC) Verification Date/Time Verification By Type of Agreement Code Billing Status Lifetime Reserve Days Delay Before L.R. Day Company Plan Code Policy Number Policy Deductible Policy Limit Amount Note: Policy Limit Days

Usage Notes

Ref

Format

Example

Variant to HL7

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

351

Message Segments

Seq 40 41 42 43 44 45 46 47 48 49

Len 12 12 60 1

DT CP CP CE IS

Opt O O O O O O O O O O

Rp/#

Tbl#

Item# 00465 00466 00467 00468

Element name Room Rate SemiPrivate Room Rate Private Insured s Employment Status Insured Sex s Insured Employer s Address Verification Status Prior Insurance Plan ID Coverage Type Handicap Insured ID Number s Note: Note:

Usage Notes Variant to HL7 Variant to HL7

Ref

Format

Example

106 XAD 2 8 3 2 12 ST IS IS IS CX

00469 00470 00471 01227 00753

01230

3.2.13. Insurance Additional Information (IN2) Segment


The following applies: (a) Function The IN2 segment contains additional insurance policy coverage and benefit information.

(b) Data elements and usage notes For relevant data elements and usage notes, see table below. Table 315. Insurance Additional Information (IN2) Segment

352

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Len 59 11

DT CX ST

Opt O O O O O O O O O O O O O O O O

Rp/# Y

Tbl#

Item# 00472 00473

Element name Insured's Employee ID Insured's Social Security Number Insured's Employer Name Employer Information Date Mail Claim Party Medicare Health Ins Card Number Medicaid Case Name Medicaid Case Number Champus Sponsor Name Champus ID Number Dependent of Champus Recipient Champus Organisation Champus Status Champus Service Champus Rank/Grade Champus Status

Usage Notes

Ref

Format

Example

130 XCN 1 1 15 48 15 48 20 80 25 25 14 2 3 IS IS ST XPN ST XPN ST CE ST ST IS IS IS

Y 0139 Y 0137

00474 00475 00476 00477

00478 00479

00480 00481 00482 00483 00484 0140 0141 0142 00485 00486 00487

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

353

Message Segments

Seq 17 18 19 20 21 22 23 24 25 26 27 28

Len 8 1 1 1 1 48 30 8 59 59 1 25

DT DT ID ID ID ST XPN ST IS CX CX IS CM

Opt O O O O O O O O O O O O

Rp/#

Tbl#

Item# 00488

Element name Champus Retire Date Champus Non-Avail Cert On File Baby Coverage Combine Baby Bill Blood Deductible Special Coverage Approval Name Special Coverage Approval Title Non-Covered Insurance Code Payor ID Payor Subscriber ID Eligibility Source Room Coverage Type/Amount Policy Type/Amount

Usage Notes

Ref

Format

Example

0136 0136 0136

00489 00490 00491 00492

00493 00494

Y Y Y

0143

00495 00496 00497

0144 Y

00498

0145/ 00499 0146

29

25

CM

0147/ 00500 0193

30 31 32 33

25 2 2 4

CM IS IS IS

O O O O

Y 0223 0009 0171

00501 00755 00145 00129

Daily Deductible Living Dependency Ambulatory Status Citizenship

354

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 34 35 36 37 38 39 40 41 42 43 44

Len 60 2 80 1 2 3 48 80 3 1 8

DT CE IS CE ID IS IS XPN CE IS IS DT

Opt O O O O O O O O O O O

Rp/#

Tbl# 0296 0220 0215 0136 0231 0006

Item# 00118 00742 00743 00744 00745 00120 00746

Element name Primary Language Living Arrangement Publicity Indicator Protection Indicator Student Indicator Religion Mother's Maiden Name Nationality Ethnic Group Marital Status Insured's Employment Start Date Insured's Employment Stop Date Job Title

Usage Notes

Ref

Format

Example

0212 0189 Y 0002

00739 00125 00119 00787

45

DT

00783

46

20

ST

00785

MH: This is used to transmit Occupation Refer to Code List Book "Occupation" Note: Variant to NHDD

NHDD 230

83

47

20

JCC

0327/ 00786 0328

Job Code/Class

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

355

Message Segments

Seq 48

Len 2

DT IS

Opt O

Rp/#

Tbl# 0311

Item# 00752

Element name Job Status

Usage Notes MH: This is used to transmit Employment Status Refer to Code List Book "Employment Status"

Ref NHDD 317

Format 70

Example

49 50

48 40

XPN XTN

O O

Y Y

00789 00790

Employer Contact Person Name Employer Contact Person Contact Phone Number Employer Contact Reason Insured's Contact Person's Name Insured's Contact Person Telephone Number Insured's Contact Person Reason Relationship To The Patient Start Date Relationship To The Patient Stop Date Insurance Co. Contact Reason Insurance Co. Contact Phone Number Policy Scope

51 52 53

2 48 40

IS XPN XTN

O O O Y Y

0222

00791 00792 00793

54 55 56 57 58

2 8 8 2 40

IS DT DT IS XTN

O O O O O

0222

00794 00795

Y 0232

00796 00797 00798

59

IS

0312

00799

356

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 60 61 62

Len 2 60 2

DT IS CX IS

Opt O O O

Rp/#

Tbl# 0313

Item# 00800 00801

Element name Policy Source Patient Member Number Guarantor's Relationship To Insured Insured's Telephone Number Home Insured's Employer Telephone Number Military Handicapped Program Suspend Flag Copay Limit Flag Stoploss Limit Flag Insured Organisation Name and ID Insured Employer Organisation Name and Id Race HCFA Patient Relationship To Insured

Usage Notes

Ref

Format

Example

0063

00802

63 64 65 66 67 68 69 70

40 40 60 2 2 2

XTN XTN CE ID ID ID

O O O O O O O O

Y Y

00803 00804 00805 0136 0136 0136 00806 00807 00808 00809 00810

130 XON 130 XON

Y Y

71 72

1 60

IS CE

O O

0005

00113 00811

3.2.14. Observation Report (OBR) Segment


The following applies:

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

357

Message Segments

(a) Function

The OBR segment identifies the observation set represented by the following observations.

(b) Data elements and usage notes For relevant data elements and usage notes, see table below. Table 316. Observation Report (OBR) Segment

Seq 1 2 3 4

Len 4 22 22

DT SI EI EI

Opt C C C R

Rp/#

Tbl#

Item# 00237 00216 00217 00238

Element name Set ID OBR Placer Order Number Filler Order Number + Universal Service ID

Usage Notes

Ref

Format

Example

200 CE

Identifies the category for the OBX segment Values: RUGADL, BARTHEL, MECHVENT, ALERTSTART, ALERTHALT, WELLBEING, DEATH, ADMISSION, NEWBORN

AE: RUGADL MH: ALERT

5 6 7 8 9 10 11 12

2 26 26 26 20 60 1 60

ID TS TS TS CQ XCN ID CE

X X C O O O O O Y 0065

00239 00240 00241 00242 00243 00244 00245 00246

Priority Requested Date/Time Observation Date/Time # Observation End Date/Time # Collection Volume * Collector Identifier * Specimen Action Code Danger Code

358

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31

Len

DT

Opt O C O O O O O O O C O O C O O O O O O

Rp/#

Tbl#

Item# 00247 00248

Element name Relevant Clinical Info. Specimen Received Date/Time * Specimen Source * Ordering Provider Order Callback Phone Number Placer Field 1 Placer Field 2 Filler Field 1 + Filler Field 2 + Results Rpt/Status Chng Date/Time Charge to Practice + Diagnostic Serv Sect ID Result Status + Parent Result + Quantity/Timing Result Copies To Parent * Transportation Mode Reason for Study

Usage Notes

Ref

Format

Example

300 ST 26 TS

300 CM 80 40 60 60 60 60 26 40 10 1 XCN XTN ST ST ST ST TS CM ID ID

0070 Y Y/2

00249 00226 00250 00251 00252 00253 00254 00255 00256

0074 0123

00257 00258 00259

400 CM 200 TQ 150 XCN 150 CM 20 ID

Y Y/5

00221 00260 00261 0124 00262 00263

300 CE

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

359

Message Segments

Seq 32 33 34 35 36 37 38 39 40

Len

DT

Opt O O O O O O O O O

Rp/#

Tbl#

Item# 00264

Element name Principal Result Interpreter + Assistant Result Interpreter + Technician + Transcriptionist + Scheduled Date/Time + Number of Sample Containers * Transport Logistics of Collected Sample * Collector Comment s * Transport Arrangement Responsibility Transport Arranged Escort Required Planned Patient Transport Comment

Usage Notes

Ref

Format

Example

200 CM 200 CM 200 CM 200 CM 26 4 60 TS NM CE

Y Y Y

00265 00266 00267 00268 01028

Y Y

01029 01030 01031

200 CE 60 CE

41 42 43

30 1

ID ID

O O O Y

0224 0225

01032 01033 01034

200 CE

3.2.15. Observation (OBX) Segment


The following applies: (a) Function The OBX segment is used to transmit a single observation or observation fragment.

360

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

(b) Data elements and usage notes For relevant data elements and usage notes, see table OBX below. RS2 Data Type structure is as follows : <quantity 1 (NM)> ^ <identifier 1 (ST)> ^ <identifier 2 (ST)> ^ <identifier 3 (ST)> ^ <identifier 4 (ST)> ^ <flag 1 (IS)> ^ <flag 2 (IS)> ^ <quantity 2 (NM)> ^ <quantity 3 (NM)> ^ <quantity 4 (NM)> ^ <quantity 5 (NM)> ^ <date 1 (TS)> ^ <flag 3 (IS)> The following table defines the coding requirements for data elements in the OBX segment where indicated.
Element Name Responsible Observer Rules To transmit clinician code, populate <ID Number>; To transmit Discipline, populate <Degree> ; To transmit campus code, populate <Assigning authority> : <ID Number>^^^^^^<degree>^^<assigning authority>

Note:

The components of observation value are used in differing ways according to the type of observation. Table 317. Use of Observation Value (OBX-5) Field

Observation Identifier = ALERTSTART^Appropriate Alert Description = ALERTHALT^Appropriate Alert Description = BARTHEL Ref: NHDD 309 = RUGADL Ref: NHDD 309 N/A N/A

Observation Value

^= A (Admission) or S (Separation) ^Barthel Index Score Eg: A^80 ^= A (Admission) or S (Separation) ^RUG ADL State Eg: A^16

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

361

Message Segments

Observation Identifier = MECHVENT

Observation Value Duration of Mechanical Ventilation Eg: 45

= NEWBORN Ref: NHDD 21 (Birth weight) Ref: NHDD 375 (Qual. Status) = WELLBEING^Wellbeing ID

Admission Weight^= Q (Qualified) or U (Unqualified) Eg: 5^U If Seq No is 1 then Total Score If Seq No is > 1 then Wellbeing Component ^ Wellbeing Component Value (in calculations) ^ Wellbeing Component Score Eg: 1^0^9

= DEATH

^Nature of death^Suicide method^Date of death accuracy^^Deliberate self harm Flag^History of Suicide Attempts^Days since last inpatient^Days since last contact^Days since last MHA status^Days since last seen^Date of deliberate self-harm^client admitted flag Eg: ^2^06^1^^N^Y^10^5^20^5^^Y

= ADMISSION

^= PR (Prior Restraint) ^=PS (Prior Sedation) Eg: PR^PS

Table 318. Observation (OBX) Segment

362

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1 2

Len 10 2

DT SI CE

Opt O C

Rp/#

Tbl#

Item# 00569 00570

Element name Set ID OBX Value Type

Usage Notes

Ref

Format

Example

Variation of the HL7 structure Value = RS2 (RAPID structure) See usage notes above for RS2 structure. RS2

590 CE

00571

Observation Identifier Refer to table above. Note: Variant to HL7

NEWBORN

20

ST

00572

Observation Sub-ID

MH: This is used to transmit Wellbeing Scale Refer to Code List Book Wellbeing Scale

MH: HNSADL

600 RS2

00573

Observation Value

See table above. Refer to Code List Book "Nature of Death", "Suicide Method", Date of Death Accuracy , Deliberate Self harm Flag , History of Suicide Attempts , "Qualification Status , Wellbeing Component , Wellbeing Component Score , Prior Restraint/ Sedation , Client Admitted Flag , Barthel Index Scores , RUG ADL Score Note: Variant to HL7

400^Q

60

CE

00574

Units

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

363

Message Segments

Seq 7

Len 10

DT ST

Opt O

Rp/#

Tbl#

Item# 00575

Element name References Range

Usage Notes MH: This is used to transmit Alert Sequence (when Obs. ID = ALERTSTART/ALERTHALT), Wellbeing Sequence (when Obs. ID = WELLBEING)

Ref

Format MH: 1

Example

8 9 10 11

5 5 2 1

ID NM ID ID

O O O R

Y/5

0078

00576 00577

Abnormal Flags Probability Nature of Abnormal Test Observ Result Status Value = F (final result) or = C (correction to observation previously sent ) or = D (delete the observation) F

0080 0085

00578 00579

12 13 14

26 20 26

TS ST TS

O O O

00580 00581 00582

Date Last Obs Normal Values User Defined Access Checks Date/Time of the Observation MH: This is used to transmit Alert Start Date (Obs. ID = ALERTSTART) / Alert Halt Date (Obs. ID = ALERTHALT / Wellbeing Date (Obs. ID = WELLBEING) / Qualification Change Date (Obs. ID = NEWBORN) NHDD 342 MH: 19980505

15

60

CE

00583

Producer ID s

364

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 16

Len 80

DT XCN

Opt O

Rp/#

Tbl#

Item# 00584

Element name

Usage Notes

Ref

Format MH : 111

Example

Responsible Observer MH: This is used to transmit Wellbeing Clinician, Discipline and Campus (Obs. ID = WELLBEING), Alert entered by User and Campus(Obs. ID = ALERTSTART) Refer to Code List Book "Service Provider Code , Discipline

17

60

CE

00936

Observation Method

3.2.16. Merge Patient Information (MRG) Segment


The following applies: (a) Function The MRG segment is used to transmit details of links or merges.

(b) Data elements and usage notes For relevant data elements and usage notes, see MRG table below. The following table defines the coding requirements for data elements in the MRG segment where indicated.
Element Name Prior Patient ID Internal Prior Visit Number Rules If changing client for a service episode (A45), populate this field with the original Client ID for the episode. To transmit Prior Episode Id, populate <ID> ; Set <identifier type code> to EPISODE : <ID>^^^^EPISODE

Table 319. Merge Patient Information (MRG) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

365

Message Segments

Seq 1 2 3 4 5 6 7

Len 20 20 20 20 20 20 48

DT CX CX CX CX CX CX XPN

Opt R O O O O O O

Rp/# Y Y

Tbl#

Item# 00211 00212 00213 00214 01279 01280 01281

Element name Prior Patient ID Internal Prior Alternate Patient ID Prior Patient Account Number Prior Patient ID External Prior Visit Number Prior Alternate Visit ID Prior Patient Name

Usage Notes MH: This is used to transmit Client Id

Ref

Format

Example 123456789

Prior Episode Id

12345^^^^EPISODE

3.2.17. Funding Arrangement Information (ZFA) Segment


The following applies: (a) Function The ZFA segment contains the specific funding arrangement and participating healthcare facilities in contracts, hub & spoke and healthstreams arrangements. (b) Data elements and usage notes For relevant data elements and usage notes, see table below. Table 320. Funding Arrangement Information (ZFA) Segment

366

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1

Len 4

DT SI

Opt R

Rp/#

Tbl#

Item# 00391

Element name Set ID PR1

Usage Notes Identifies which procedures were performed under this contract.

Ref

Format

Example

CE

90001

Funding Arrangement Indicates if the funding arrangement is a contract or hub and spoke arrangement. Values: 1 Contract 2 Hub/Spoke 3 Healthstreams Refer to Code List Book "Funding Arrangement"

AE: 1

CE

90002

Contract Type

Type of contract arrangement NHDD 79 Refer to Code List Book "Contract Type"

AE: 3

CE

90003

Contract Role

Role of health care facility in this funding arrangement Values: A Contractor B Service Provider Refer to Code List Book "Contract Role"

NHDD 79

AE: B

26

TS

90004

Contract Start Date/Time Contract End Date/Time

Date and Time of beginning of special funding arrangement Date and Time of end of special funding arrangement

26

TS

90005

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

367

Message Segments

Seq 7

Len 4

DT ST

Opt R

Rp/#

Tbl#

Item# 90006

Element name Contract / Spoke Identifier

Usage Notes

Ref

Format

Example AE: BBBB

Identifier of the other hospital NHDD 50 party to the special funding arrangement AE: This is used to transmit Campus Code Refer to Code List Book "Service Provider Code"

3.2.18. Emergency Information (ZEM) Segment


The following applies: (a) Function The ZEM segment contains Emergency data elements not covered elsewhere in other segments.

(b) Data elements and usage notes For relevant data elements and usage notes, see table below. Table 321. Emergency Information (ZEM) Segment

368

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1

Len 60

DT CE

Opt O

Rp/#

Tbl#

Item# 90007

Element name Arrival Transport Mode

Usage Notes Transport used to present to Emergency Dept. Conditional for trigger A04. Refer to Code List Book Transport Mode

Ref

Format EM: 1

Example

60

CE

90008

Departure Transport Mode

Transport used to depart from Emergency Dept. Conditional for trigger A03. Refer to Code List Book Transport Mode

EM: 3

10

ST

90009

Ambulance Case Number Triage Category

Unique identifier to each ambulance transport occasion. Classification for urgency of NHDD need for medical and nursing 355 care Refer to Code List Book Triage Category Note: Variant to NHDD NHDD 353 & 354 NHDD 356 & 357 NHDD 356 & 357

10 digit, leading zeros

EM: 0000746532

60

CE

90010

EM: 2

5 6

26 26

TS TS

O O

90011 90012

Triage date/time First Seen Nurse date/time First Seen Doctor date/time

Date and time patient first seen by triage nurse Date and time baseline observations taken after triage Date and time first medical officer assess patient

EM: 199808270334

26

TS

90013

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

369

Message Segments

Seq 8

Len 60

DT CE

Opt O

Rp/#

Tbl#

Item# 90014

Element name Referred to on Discharge

Usage Notes Referral to further care if necessary for continuation of treatment. Refer to Code List Book Referred To

Ref

Format EM: 2

Example

60

CE

90015

Reason for Transfer on Discharge

Reason patient referred to another health care facility Refer to Code List Book Reason for Transfer

EM: 5

10

60

CE

90016

Escort Source

Work location or other source of the medical or nursing assistant(s) accompanying a patient whilst being transferred to another hospital. Refer to Code List Book Escort Source

EM: 2

3.2.19. Mental Health Information (ZMH) Segment


The following applies: (a) Function The ZMH segment contains Mental Health data elements not covered elsewhere in other segments.

(b) Data elements and usage notes For relevant data elements and usage notes, see ZMH table below. The following table defines the coding requirements for data elements in the ZMH segment where indicated.

370

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name Case Manager

Rules To transmit Clinician Code, populate <ID> ; To transmit Clinican Discipline, populate <degree> ; To transmit Clinician Campus, populate <assigning authority> : <ID>^^^^^^<degree>^^<assigning authority>

Table 322. Mental Health Information (ZMH) Segment

Seq 1 2

Len 10 5

DT SI NM

Opt O O

Rp/#

Tbl#

Item# 90020 90100

Element name Set ID - ZMH Contact Duration

Usage Notes

Ref

Format

Example

Duration of the contact in minutes MH: This is used to transmit Contact Duration.

10

CE

90101

Contact Type

Type of contact. MH: This is used to transmit Contact Type. Refer to Code List Book Contact Type

10

CE

90102

Community Contact Type

Type of community contact. MH: This is used to transmit Community Type. Refer to Code List Book Community Contact Type

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

371

Message Segments

Seq 5

Len 10

DT CE

Opt O

Rp/#

Tbl#

Item# 90103

Element name Service Medium

Usage Notes Medium of the contact. MH: This is used to transmit. Service Medium. Refer to Code List Book Service Medium

Ref

Format 1

Example

10

CE

90104

Service Location

Location of the contact. MH: This is used to transmit. Service Location. Refer to Code List Book Service Location

10

CE

90105

Service Recipient

Identifies the recipient or recipient group of the contact. MH: This is used to transmit. Service Recipient. Refer to Code List Book Service Recipient

10

CE

90106

Number Providing Service

Number of clinicians involved in the contact. MH: This is used to transmit. Number Providing Service.

10

CE

90107

Number Receiving Service

Number of clients/client related persons involved in the contact. MH: This is used to transmit Number Receiving Service.

372

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 10

Len 10

DT CE

Opt O

Rp/#

Tbl#

Item# 90108

Element name Focus of Care

Usage Notes Focus of care of the contact. MH: This is used to transmit. Focus of Care. Refer to Code List Book Focus of Care

Ref

Format 4

Example

11

30

ST

90109

Contact Name

Name of the contact recipient, not necessarily the client. MH: This is used to transmit. Contact Name.

12

10

CE

90110

Program

Funding program for the visit. MH: This is used to transmit Program.

13

10

CE

90111

Program Classification

Program Classification of the client. MH: This is used to transmit Program Classification. Refer Code List Book Program Class

14

10

CE

90021

Case Id

The unique identifier for a case. MH: This is used to transmit: Case Id

1234567890

15

26

TS

90022

Case Start Date

The start date of a case. MH: This is used to transmit: Case Start Date

19980404

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

373

Message Segments

Seq 16

Len 26

DT TS

Opt O

Rp/#

Tbl#

Item# 90023

Element name Case End Date

Usage Notes The end date of a case. MH: This is used to transmit: Case End Date

Ref

Format

Example 19980707

17

10

CE

90024

MH Episode Id

The unique identifier of an episode. MH: This is used to transmit: Episode Id

1234567890

18

26

TS

90025

Episode Start Date

The start date of an episode. MH: This is used to transmit: Episode Start Date

19980404

19

26

TS

90026

Episode End Date

The end date of an episode. MH: This is used to transmit: Episode End Date

19980707

20

10

CE

90110

Case Management Id

Case Management sequence. MH: This is use to transmit Case Management Sequence Number.

21

48

XPN

90027

Case Manager

Details of the case manager for the case. MH: This is used to transmit: Case Manager Code/ Case Manager Discipline and Campus Refer to Code List Book Discipline , Service Provider Code

123456^^^^^^31^^BBB B

374

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 22

Len 26

DT TS

Opt O

Rp/#

Tbl#

Item# 90028

Element name Case Management Start Date

Usage Notes Start of case management period for the case manager listed in Case Manager field. MH: This is used to transmit: Case Management Start Date

Ref

Format

Example 19980404

23

TS

90029

Case Management End Date

End of case management period for the case manager listed in Case Manager field. MH: This is used to transmit: Case Management End Date

19980707

24

10

CE

90030

Previous Case Id

Reference to the previous case for the client, at the service. MH: This is used to transmit: Previous Case Id

87876776

25

IS

90031

Admission Details

Admission Details for the client. MH: This is used to transmit: Admission Details Refer to Code List Book Admission Details

26

IS

90032

Crisis Assessment Indicator

Whether a crisis assessment has led to the admission. MH: This is used to transmit: Crisis Assessment Indicator Refer to Code List Book Crisis Assessment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

375

Message Segments

Seq 27

Len 6

DT IS

Opt O

Rp/#

Tbl#

Item# 90033

Element name MH Escort Source

Usage Notes What the Mental Health escort source was (if any), leading up to the admission. MH: This is used to transmit: Escort Source Refer to Code List Book Mental Health Escort Source

Ref

Format 5

Example

28

IS

90034

MH Transport Mode

What the transport mode to the hospital was, leading up to the admission. MH: This is used to transmit: Transport Mode Refer to Code List Book Transport Mode

29

10

CE

90035

Transfer from campus Campus code that the client was transferred from. MH: This is used to transmit: Transfer from campus Refer to Code List Book Establishment Id

BBBB

30

26

TS

90036

Involuntary Start Date Date the client was first assigned an involuntary legal status for the current involuntary period. MH: This is used to transmit: Involuntary Start Date

19980304

376

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 31

Len 1

DT IS

Opt O

Rp/#

Tbl#

Item# 90037

Element name Interpreter required

Usage Notes Whether the client requires an interpreter. MH: This is used to transmit: Interpreter Required Refer to Code List Book Interpreter Required

Ref NHDD 100

Format 2

Example

32

PL

90038

Client Mental Health Area Code at event date

The Mental Health Area code the client belongs to, according to home address, at time of event. MH: This is used to transmit: MHA Code Refer to Code List Book Mental Health Area

81

33

PL

90039

Client Postcode at event date

The Mental Health Postcode for the client according to home address, at time of event. MH: This is used to transmit: Client Postcode at time of event.

3123

34

IS

90040

Education

Level of education of the client. MH: This is used to transmit: Education Refer to Code List Book Education

40

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

377

Message Segments

Seq 35

Len 6

DT IS

Opt O

Rp/#

Tbl#

Item# 90041

Element name Housing

Usage Notes

Ref

Format 10

Example

Type of housing of the client. NHDD 173 MH: This is used to transmit: Housing Refer to Code List Book Housing

36

26

TS

90042

Statewide Registration Date

Date of Mental Health statewide registration. MH: This is used to transmit Registration Date

19981002

37

PL

90039

Client Region

The Mental Health Region for the client according to home address. MH: This is used to transmit: Mental Health Region. Refer to Code List Book Region

20

3.2.20. Mental Health Legal Status Information (ZLE) Segment


The following applies: (a) Function The ZLE segment contains Mental Health Legal Status data elements not covered elsewhere in other segments.

(b) Data elements and usage notes For relevant data elements and usage notes, see ZLE table below. The following table defines the coding requirements for data elements in the ZLE segment where indicated.

378

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name ID Number

Rules To transmit R/CTO Id, populate <identifier> and set <name of coding system to CTO : <identifier>^^CTO

ID Number

To transmit Progress Report Id, populate <identifier> and set <name of coding system to CTOPROGRESS : <identifier>^^CTOPROGRESS

ID Number

To transmit Legal Status ID, populate <identifier> and set <name of coding system to LEGAL : <identifier>^^LEGAL

ID Number

To transmit MHRB Hearing Id, populate <identifier> and set <name of coding system to MHRB : <identifier>^^MHRB

ID Number

To transmit Annual Exam Id, populate <identifier> and set <name of coding system> to ANEXAM : <identifier>^^ANEXAM

Legal Status Code Legal Status Code

To transmit Mental Health Legal Status (voluntary/involuntary indicator), populate <identifier> and set <name of coding system> to MHLS. To transmit Legal Status (specific act/section), populate <identifier> and set <name of coding system> to LSC.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

379

Message Segments

Element Name Practitioner Name

Rules To transmit Clinician Code, populate <ID number> ; To transmit Clinican Discipline, populate <degree> ; To transmit Clinician Campus, populate <assigning authority> ; Populate <identifier type code> with AUTHPSYCH (authorised psychiatrist), CONFBY (legal status confirmed by), ANEXAM (annual exam clinician), CTOAUTH (CTO Authorising psychiatrist), MONPSYCH (monitoring psychiatrist), SUPDOCTOR (supervising doctor) ,SUPPSYCH (supervising psychiatrist : <ID number>^^^^^^<degree>^^<assigning authority>^^^^<identifier type code>

Reason

To transmit Legal Status Discharge reason, populate <Identifier> and set <text> to DISCHARGE : <identifier>^DISCHARGE

Reason

To transmit CTO revoke reason, populate <Identifier> and set <text> to CTOREVOKE : <identifier>^CTOREVOKE

Reason

To transmit RCTO revoke reason, populate <Identifier> and set <text> to DISCHARGE : <identifier>^RCTOREVOKE

Table 323. Mental Health Legal Status Information (ZLE) Segment

380

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 1 2

Len 10 22

DT SI CE

Opt O O

Rp/#

Tbl#

Item# 90050 90051

Element name Set ID ZLE ID Number

Usage Notes

Ref

Format

Example

General Identifier. MH: This is used to transmit: R/CTO ID / Legal ID / MHRB Hearing ID / Annual Exam ID / Type of ID

123456^^LEGAL

60

CE

90052

Legal Status Code

Legal Status Code of the client. AE: This is used to transmit Mental Health Legal Status MH: This is used to transmit Legal Status Refer to Code List Book Mental Health Legal Status Legal Status Code

AE: 1^^MHLS MH: 10^^^LSC

48

XCN

90053

Practitioner Name

Name of practitioner. MH: This is used to transmit: Legal Status Authorising Psychiatrist Code / Confirmed By / Annual Exam Clinician / CTO Authorising Psychiatrist / Monitoring Psychiatrist / Supervising Doctor / Supervising Psychiatrist / Discipline and Campus Code Refer to Code List Book Discipline , Service Provider Code

123456^^^^^^02^^BBB B^^^^ANEXAM

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

381

Message Segments

Seq 5

Len 60

DT CE

Opt O

Rp/#

Tbl#

Item# 90054

Element name Reason

Usage Notes Reason for event. MH: This is used to transmit: Legal Status Discharge Reason / CTO Revoked Reason / RCTO Revoked Reason Refer to Code List Book Discharge Reason , CTO Revoked Reason , RCTO Revoked Reason

Ref

Format

Example 2^DISCHARGE

26

TS

90055

Applicable date

Date the CTIP order became applicable for the client. MH: This is used to transmit CTIP Applicable Date

19980505

26

TS

90056

Legal Status Date/Time

Date the client first approved with this legal status. MH: This is used to transmit Legal Status Date/time

19980330

26

TS

90057

CTIP Review Date

Date the next CTIP Review is expected for the client. MH: This is used to transmit CTIP Review Date

19981217

26

TS

90058

CTIP Finish Date

Date the CTIP order expires for the client. MH: This is used to transmit CTIP Finish Date

19981215

382

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 10

Len 26

DT TS

Opt O

Rp/#

Tbl#

Item# 90059

Element name Sentence Expiry Completion Date

Usage Notes Date the sentence expires for the client. MH: This is used to transmit Sentence Expiry Completion Date

Ref

Format

Example 19981103

11

26

TS

90060

Due Date

Due Date for the event. MH: This is used to transmit: Annual Exam Due Date (if ID number type = ANEXAM/ CTO Report Due Date (if ID number type = CTO) (may be repeating for CTO reporting requirements)

19980504~19980604

12

26

TS

90061

Completed date

Date the event actually occurred. MH: This is used to transmit: Annual Exam Competed Date (if ID number type = ANEXAM) / CTO Report Completed Date (if ID Number type = CTO)

19981207

13

26

TS

90062

MHRB Hearing Date/time

Date of the MHRB Hearing for the client. MH: This is used to transmit: MHRB Hearing Date

19980706

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

383

Message Segments

Seq 14

Len 6

DT IS

Opt O

Rp/#

Tbl#

Item# 90063

Element name MHRB Hearing Type

Usage Notes Type of the MHRB Hearing for the client. MH: This is used to transmit: MHRB Hearing Type Refer to Code List Book Hearing Type

Ref

Format 49

Example

15

26

TS

90064

New Scheduled Date/time

New scheduled date/time of the MHRB hearing for the client. MH: This is used to transmit: New Scheduled Date/time

19981203

16

IS

90065

Campus

New campus of the MHRB hearing for the client. MH: This is used to transmit: New Campus for Hearing

BBBB

17

10

IS

90066

Subcentre

New subcentre of the MHRB hearing for the client. MH: This is used to transmit: New Subcentre for Hearing

CCCC

18

IS

90067

MHRB Outcome

Outcome of the MHRB hearing for the client. MH: This is used to transmit: MHRB Outcome Refer to Code List Book MHRB Outcome

19

26

TS

90068

R/CTO Start Date

Start Date of the R/CTO. MH: This is used to transmit: R/CTO Start Date

19980816

384

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 20

Len 26

DT TS

Opt O

Rp/#

Tbl#

Item# 90069

Element name R/CTO Completed Date

Usage Notes Completed date of the R/CTO. MH: This is used to transmit: R/CTO Completed Date

Ref

Format

Example 19980530

21

26

TS

90070

R/CTO Expiry Date

Expiry Date of the R/CTO. MH: This is used to transmit: R/CTO Expiry Date

19980731

22

30

ST

90071

R/CTO Completed By Who completed the R/CTO form. MH: This is used to transmit: R/CTO Completed By

19980404

23

26

TS

90072

Revoke Authorised Date

Date the R/CTO revocation was authorised. MH: This is used to transmit: Revoke Authorised Date

19980505

24

IS

90073

Restricted Flag

Whether the CTO is restricted. MH: This is used to transmit: Restricted flag Refer to Code List Book Restricted Flag

25

26

TS

90074

CTO Event Date

Date the R/CTO event occurred. MH: This is used to transmit: R/CTO Event Date

19980606

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

385

Message Segments

Seq 26

Len 60

DT CE

Opt O

Rp/#

Tbl#

Item# 90075

Element name CTO Event Type

Usage Notes Type of the R/CTO event. MH: This is used to transmit: R/CTO Event Type Refer to Code List Book CTO Event Type

Ref

Format 2

Example

27

IS

90076

Residency Clause

Whether a residency clause is included in the R/CTO. MH: This is used to transmit: Residency Clause Refer to Code List Book Residency Clause Flag

28

1000

TX

90077

RCTO Further Conditions

Further conditions placed on an RCTO. MH: This is used to transmit: RCTO Further Conditions

29

IS

90078

Report Required

Reporting Requirements of the R/CTO. MH: This is used to transmit: Reporting Requirements Refer to Code List Book R/CTO Reporting Requirements

03

30

IS

90079

Report Outcome

Outcome of R/CTO report. MH: This is used to transmit: Report Outcome. Refer to Code List Book R/CTO Report Outcome

386

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 31

Len 30

DT ST

Opt O

Rp/#

Tbl#

Item# 90080

Element name

Usage Notes

Ref

Format

Example Meg Hondy

Report Completed By Who completed the R/CTO report. MH: This is used to transmit: Report Completed By

32

10

CE

90081

R/CTO Status

Status of the R/CTO. MH: This is used to transmit the status of an R/CTO for a client. Refer to Code List Book R/CTO Status

3.2.21. Master File Identification Segment (MFI)


The following applies: (a) Function The MFI segment is used to report the healthcare facilities bed status.

(b) Data elements and usage notes For relevant data elements and usage notes, see MFI table below. The following table defines the coding requirements for data elements in the MFI segment where indicated.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

387

Message Segments

Element Name Master File Application Identifier When Master File Identifier = PRA

Rules

Set to HCP for HCP Details Set to HCPCAMPUS for campuses a HCP works at Set to AUTHPSYCH for Authorised Psychiatrist Details When Master File Identifier = LOC Set to CAMPUS for Campus Details Set to SUBCENTRE for Subcentre Details Set to PROGRAM for Program Details Set to GAZSERV for Gazetted Service Details Set to DAILYBED for Daily Bed Status Details Set to BED for Bed Details Set to SUBCENTPROG for Subcentre Program Details Set to HELDBED for Held Bed Details

Table 324. Master File Identification (MFI) Segment

Seq 1

Len 60

DT CE

Opt R

Rp/#

Tbl# 0175

Item# 00658

Element name Master File Identifier

Usage Notes This field containsLOCfor Location Master File (M05), This field contains PRAfor Practitioner Master File (M02)

Ref

Format LOC

Example

2 3 4 5

180 HD 3 26 26 ID TS TS

O R O O 0178

00659 00660 00661 00662

Master File Application Identifier

See table above.

HCP REP

File-Level Event Code Value: REP Entered Date/Time Effective Date/Time

388

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 6

Len 2

DT ID

Opt R

Rp/#

Tbl# 0179

Item# 00663

Element name

Usage Notes

Ref

Format NE

Example

Response Level Code Value: NE No application level responses will be sent back to sending application for master file notifications.

3.2.22. Master File Entry Segment (MFE)


The following applies: (a) Function The MFE segment is used to report the healthcare facilities bed status, subcentre and program details.

(b) Data elements and usage notes For relevant data elements and usage notes, see MFE table below. Table 325. Master File Entry (MFE) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

389

Message Segments

Seq 1

Len 3

DT ID

Opt R

Rp/#

Tbl# 0180

Item# 00664

Element name Record-Level Event Code Values:

Usage Notes

Ref

Format MAD

Example

MAD Add record MUP Update record MDL Delete record

Use MAD to send bed status for the first time for that Activity Date, or to add a reference table record. Use MUP to resend a bed status for a previously sent Activity Date, or to update a reference table record. Use MDL to remove a reference table record. Note: ODS is the only system that can ADD campus details. CMI and equivalents can UPDATE campus details and ADD subcentre and gazetted service details. Variant to HL7 MH: 19980902

2 3

20 26

ST TS

O R

00665 00662

MFN Control ID Effective Date/Time

Note:

MH: This is used to transmit Activity Date Note: Variant to HL7

390

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 4

Len

DT

Opt O

Rp/# Y

Tbl#

Item# 00667

Element name Primary Key Value MFE Note:

Usage Notes Variant to HL7, not required

Ref

Format

Example

200 Varies

3.2.23. Location Identification Segment (LOC)


The following applies: (a) Function The LOC segment is used to report the healthcare facilities bed status, subcentre and program details.

(b) Data elements and usage notes For relevant data elements and usage notes, see LOC table below. The following table defines the coding requirements for data elements in the LOC segment where indicated.
Element Name Location Address Rules To transmit Address, populate <street address> ; To transmit Suburb, populate <other designation> ; To transmit State, populate <state or province> ; To transmit Postcode, populate <zip or postal code> ; To transmit MHA code, populate <other geographic designation> : <street address>^<other designation>^^<state or province>^<zip or postal code>^^^<other geographic designation>

Table 326. Location Identification (LOC) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

391

Message Segments

Seq 1

Len

DT

Opt R

Rp/#

Tbl#

Item# 01307

Element name Primary Key Value LOC

Usage Notes MH: This is used to transmit Campus Code Refer to Code List Book Service Provider Code

Ref

Format BBBB

Example

200 PL

2 3 4

48 2 90

ST IS XON

O R O Y 0260

00944 00945 00947

Location Description Location Type Organisation Name Value: L MH: This is used to transmit Subcentre Name (if MFI-2 = SUBCENTRE), Campus Name (if MFI-2 = CAMPUS) MH: This is used to transmit Subcentre Address, Suburb, State and Postcode (if MFI-2 = SUBCENTRE), Campus Address, Suburb, State, Postcode and MHA code (if MFI-2 = CAMPUS) Refer to Code List Book State Mental Health Area , L Monash CAT

106 XAD

00948

Location Address

123 Smith St^^Collingwood^VIC^ 3001^^^72

40

XTN

00949

Location Phone

MH: This is used to transmit Subcentre Phone Number (if MFI-2 = SUBCENTRE), Campus Phone Number (if MFI-2 = CAMPUS)

94897766

7 8

60 3

CE IS

O O

Y Y 0261

00951 00953

License Number Location Equipment

392

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

3.2.24. Location Characteristic Segment (LCH)


The following applies: (a) Function The LCH segment is used to report the healthcare facilities bed status, subcentre and program details.

(b) Data elements and usage notes For relevant data elements and usage notes, see LCH table below. The following table defines the coding requirements for data elements in the LCH segment where indicated.
Element Name Primary Key Value LCH Rules To transmit Subcentre Code, populate <point of care> ; To transmit Subcentre Type, populate <location status> ; To transmit Program Classification, populate <person location type> <point of care>^^^^<location status>^<person location type> Location Characteristic ID If MFI-2 = DAILYBED Location Characteristic will contain HELD, OCCUPIED, ONLEAVE, APPROVED, OPERATIONAL, PURCHASED (in repeating segments). If MFI-2 = PROGRAM Location Characteristic will contain TARGETPOP, AMHS, FUNDSOURCE (in repeating segments). If MFI-2 = SUBCENTRE Location Characteristic will contain OPENREASON If MFI-2 = HELDBED Location Characteristic will contain HELDBED If MFI-2 = BED Location Characteristic will contain APPROVED, OPERATIONAL, PURCHASED Location Characteristic Value This will contain the value for the characteristic specified in Location Characteristic ID for the current segment.

Table 327. Location Characteristic (LCH) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

393

Message Segments

Seq 1

Len

DT

Opt R

Rp/#

Tbl#

Item# 01305

Element name Primary Key Value LCH

Usage Notes MH: This is used to transmit Subcentre Code, Program Classification and Subcentre Type Refer to Code List Book "Program Class", Subcentre Type

Ref

Format

Example CCCC^^^^C^A

200 PL

2 3 4

1 80 80

ID EI CE

O O O

0206

00763 00764

Segment Action Code Segment Unique Key Location Characteristic ID MH: This is used to transmit Bed Category (Held Beds, Occupied Beds, On Leave, Approved Beds, Operational Beds, Purchased Beds) Program Characteristic (Target population, AMHS and Funding source) Subcentre Open reason Held Bed (Held Bed) Bed (Approved, Operational, Purchased Beds) Note: Variant to HL7 HELD

0324

01295

394

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 5

Len 80

DT CE

Opt O

Rp/#

Tbl#

Item# 01237

Element name Location Characteristic Value

Usage Notes MH: This is used to transmit Number of Beds in this Bed Category, Value for Program Characteristic, Subcentre Open Reason Refer to Code List Book "Target Population Area , Mental Health Service , Funding Source , Open Reason Note: Variant to HL7

Ref

Format 2

Example

3.2.25. Location Department Segment (LDP)


The following applies: (a) Function The LDP segment is used to report the healthcare facilities bed status, subcentre and program details..

(b) Data elements and usage notes For relevant data elements and usage notes, see LDP table below. The following table defines the coding requirements for data elements in the LDP segment where indicated.
Element Name Specialty Type Rules To transmit Program Code, populate <identifier> ; To transmit Program Description, populate <text> : <identifier>^<text>

Table 328. Location Department (LDP) Segment

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

395

Message Segments

Seq 1 2 3

Len

DT

Opt O O O

Rp/#

Tbl#

Item# 00963

Element name Primary Key Value LDP Location Department Location Service Note: Note:

Usage Notes Variant to HL7 Variant to HL7

Ref

Format

Example

200 PL 10 3 IS IS

0264 Y 0069

00964 00965

MH: This is used to transmit Ward/Residential Type Refer to Code List Book Ward/Residential Type

60

CE

0265

00966

Specialty Type

MH: This is used to transmit Program Code, Program Description MH: This is used to transmit Locked Type (for Beds) Refer to Code List Book Locked Type

1234^Eating Disorder Program 1

IS

0004

00967

Valid Patient Classes

6 7

1 26

ID TS

O O

0183

00675 00969

Active/Inactive Flag Activation Date MH: This is used to transmit Subcentre Open Date (if MFI2 = SUBCENTRE), Subcentre Program Start Date (if MFI-2 = SUBCENTPROG), Campus Open Date (if MFI-2 = CAMPUS), Gazetted Service Proclaimed Date (if MFI-2 = GAZSERV), Bed Effective Date (if MFI-2 = BED), Program Start Date (if MFI-2 = PROGRAM) 19980101

396

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 8

Len 26

DT TS

Opt O

Rp/#

Tbl#

Item# 00970

Element name Inactivation Date LDP

Usage Notes MH: This is used to transmit Subcentre Close Date (if MFI-2 = SUBCENTRE), Subcentre Program End Date (if MFI-2 = SUBCENTPROG), Campus Close Date (if MFI-2 = CAMPUS, Gazetted Service End Date (if MFI-2 = GAZSERV), Program End date (if MFI-2 = PROGRAM) MH: This is used to transmit Subcentre Termination Reason (if MFI-2 = SUBCENTRE), Reason for change to Bed Numbers (if MFI-2 = BED). Refer to Code List Book Termination Reason , Reason for Change to Bed Numbers

Ref

Format

Example 19980202

80

ST

00971

Inactivated Reason

06

10 11

80 40

VH

0267

00976 00978

Visiting Hours Contact Phone

XTN O

3.2.26. Staff identification Segment (STF)


The following applies: (a) Function The STF segment is used to report details of workers within the service.

(b) Data elements and usage notes For relevant data elements and usage notes, see STF table below.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

397

Message Segments

The following table defines the coding requirements for data elements in the STF segment where indicated.
Element Name Staff Name Rules To transmit Surname, populate <family name> ; To transmit Given Name, populate <given name> ; To transmit Title, populate <prefix> : <family name>^<given name>^^^<prefix> Staff Type If MFI-2 = HCP Possible values are CASEMANAGER, CLINICIAN, DELEGATE, DOCTOR, GP,PRIVATEPSYCH. All codes appropriate to the HCP will be transmitted in this repeating field. If MFI-2 = AUTHPSYCH Set only one value in this field, to AUTHPSYCH. Office/Home Address To transmit Address, populate <street address> ; To transmit Suburb, populate <other designation> ; To transmit State, populate <state or province> ; To transmit Postcode, populate <zip or postal code> : <street address>^<other designation>^^<state or province>^<zip or postal code>

Table 329. Staff Identification (STF) Segment

Seq 1 2

Len 60 60

DT CE CX

Opt O O

Rp/#

Tbl#

Item# 00671

Element name Primary Key Value STF Staff ID Code Note:

Usage Notes Variant to HL7

Ref

Format

Example

00672

MH: This is used to transmit HCP Code

398

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 3

Len 48

DT XPN

Opt O

Rp/#

Tbl#

Item# 00673

Element name Staff Name

Usage Notes MH: This is used to transmit Title, Surname and Given Name Refer to Code List Book Title

Ref

Format

Example

IS

0182

00674

Staff Type

MH: This is used to transmit what roles the HCP will carry out. (All codes appropriate for the HCP will be transmitted.) Refer to Code List Book HCP Type

CASEMANAGER~DO CTOR

5 6 7 8 9

1 26 1

IS TS ID

O O O O O Y Y

0001

00111 00110

Sex Date/Time of Birth Active/Inactive Department Service MH: This is used to transmit Campus Code for the HCP/Authorised Psychiatrist. Populate only one occurrence. Refer to Code List Book Service Provider Code AAAA

0183 0184 0069

00675 00676 00677

200 CE 200 CE

10

40

XTN

00678

Phone

MH: This is used to transmit Contact Phone Number

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

399

Message Segments

Seq 11

Len

DT

Opt O

Rp/# Y

Tbl#

Item# 00679

Element name Office/Home Address

Usage Notes MH: This is used to transmit Address, Suburb, State and Postcode. Refer to Code List Book State

Ref

Format

Example

106 XAD

12

26

CM

00680

Activation Date

MH: This is used to transmit one occurrence of either HCP Start Date, Authorised Psychiatrist Start Date, HCP Start Date at Campus MH: This is used to transmit HCP End Date, HCP End Date at Campus

13

26

CM

00681

Inactivation Date STF Backup Person ID E-mail address Preferred Method of Contact Marital Status Job Title Job Code/Class

14 15 16 17 18 19

60 40 1 1 20 20

CE ST ID IS ST JCC

O O O O O O

Y Y 0185 0002

00682 00683 00684 00119 00785 00786

MH: This is used to transmit Discipline Refer to Code List Book Discipline

31

20 21

2 1

IS ID

O O

0066 0136

01276 01275

Employment Status Additional Insured on Auto

3100

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Seq 22 23 24 25 26

Len 25 1 8 8 8

DT DLN ID DT DT DT

Opt O O O O O

Rp/#

Tbl#

Item# 01302

Element name Driver License s Number Staff Copy Auto Ins Auto Ins. Expires Date Last DMV Review Date Next DMV Review

Usage Notes

Ref

Format

Example

0136

01229 01232 01298 01234

3.2.27. Original-style Query Definition Segment (QRD)


The following applies: (a) Function The QRD segment is used to define a query.

(b) Data elements and usage notes For relevant data elements and usage notes, see QRD table below. The following table defines the coding requirements for data elements in the QRD segment where indicated.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

3101

Message Segments

Element Name Who Subject Filter

Rules To transmit Statewide UR Number, populate <ID> and set <identifier type code> to SWUR ; To transmit CMI Client Number, populate <ID> and set <identifier type code> to CI ; To transmit Client Surname, populate <family name> ; To transmit Client First Name, populate <given name> : <ID>^<family name>^<given name>^^^^^^^^^^<identifier type code>

What Subject Filter

For Admission History query, set to WRDADM For Placement History query, set to RESPLC For R/CTO history query, set to CTO For Legal status history query, set to LEGHISTORY For demographics query, set to CLIENT For most recent legal status query, set to LEGCURRENT For most recent admission query, set to ADMCURRENT For Status of CTO Transfer Out query, set to CTOSTATUS For Contacts history query, set to CONTACT For all cases for a client query, set to CASE For all episodes for a client query, set to EPISODE For diagnosis history query, set to DIAGNOSIS For MHRB Hearing history, set to MHRBHEAR For Client Search, set to CLSEARCH For Final Registration Check, set to REGCHECK For Request Campus Download, set to CMPDWNLD For Request Bed Status Details, set to BEDSTATUS For Request UR Number, set to REQUESTUR. For Request Submission Reports, set to SUBMRPT

3102

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name What Department Data Code

Rules To transmit CTO Id, populate <identifier> and set <text> to CTO ; To transmit Campus Code, populate <identifier> and set <text> to CAMPUS ; To transmit Program Class, populate <identifier> and set <text> to PROGCLASS : <identifier>^<text>

Table 330. Original-style Query Definition (QRD) Segment

Seq 1 2

Len 26 1

DT TS ID

Opt R R

Rp/#

Tbl#

Item# 00025

Element name Query Date/Time Query Format Code

Usage Notes MH: Date & time of query Value = T (tabular) if multiple records are expected to be returned. Value = R (record) if a single record is expected to be returned.

Ref

Format

Example 199802021400 T

0106

00026

3 4 5 6 7

1 10 1 26 10

ID ST ID TS CQ

R R O O O

0091

00027 00028

Query Priority Query ID Deferred Response Type Deferred Response Date/Time Quantity Limited Request

Value: I (immediate) MH: Unique identifier for the query

0107

00029 00030

0126

00031

MH: Value = 100 Note: Variant to HL7

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

3103

Message Segments

Seq 8

Len 60

DT XCN

Opt O

Rp/# Y

Tbl#

Item# 00032

Element name Who Subject Filter

Usage Notes MH: This is used to transmit Statewide UR Number, CMI Client ID, Client Surname, given name, Note: Variant to HL7

Ref

Format

Example

60

CE

0048

00033

What Subject Filter

MH: This field is used to transmit the type of query requested MH: This is used to transmit CTO Id, Campus and Program Class. Refer to Code List Book Service Provider Code , Program Class Note: Variant to HL7

REQUESTUR

10

60

CE

00034

What Department Data Code

1234567^CAMPUS~9 876^PROGCLASS

11

20

ST

00035

What Data Code Value Qual.

MH: This is used to transmit Soundex Indicator Refer to Code List Book Soundex Flag

12

ID

0108

00036

Query Results Level

3.2.28. Original-style Query Filter Segment (QRF)


The following applies: (a) Function The QRF segment is used to further refine the content of an original style query.

(b) Data elements and usage notes For relevant data elements and usage notes, see QRF table below. The following table defines the coding requirements for data elements in the QRF segment where indicated.

3104

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Message Segments

Element Name Other QRY Subject Filter

Rules To transmit Date of Birth, populate <identifier>, and set <text> to DOB ; To transmit Date of Birth Range, populate <identifier>, and set <text> to DOBRANGE ; To transmit Sex, populate <identifier>, and set <text> to SEX ; To transmit Medicare Number, populate <identifier>, and set <text> to MEDICARE : <identifier>^<text>

Table 331. Original-style Query Filter (QRF) Segment

Seq 1

Len 20

DT ST

Opt R

Rp/# Y

Tbl#

Item# 00037

Element name Where Subject Filter

Usage Notes MH: This field is used to transmit Campus Code. Refer to Code List Book Service Provider Code

Ref

Format BBBB

Example

26

TS

00038

When Data Start Date/Time

MH: This field is used to transmit Schedule start date, Bed Status Date, Submission Report Start Date. MH: This field is used to transmit Schedule end date, Submission Report End Date.

19980104

26

TS

00039

When Data End Date/Time

19980430

60

ST

00040

What User Qualifier

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

3105

Message Segments

Seq 5

Len 60

DT CE

Opt O

Rp/# Y

Tbl#

Item# 00041

Element name Other QRY Subject Filter

Usage Notes MH: This is used to transmit DOB, DOB range, Sex and Medicare Number. See table above. Refer to Code List Book Sex Note: Variant to HL7

Ref

Format

Example DOB^19710101~DOB RANGE^4

6 7 8 9

12 12 12 60

ID ID ID TQ

O O O O

Y Y Y

0156 0157 0158

00042 00043 00044 00694

Which Date/Time Qualifier Which Date/Time Status Qualifier Date/Time Selection Qualifier When Quantity/Timing Qualifier

3106

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Chapter 4 Lower-Layer Protocols


4.1. Communications Environment Overview
The HL7 Standard defines the messages as they are exchanged among applications entities and the procedures used to exchange them. As such, it conceptually operates at the seventh level of the ISO model for Open System Interconnection (OSI). It is primarily concerned with the data content and interrelationship of messages and with communicating certain application-level error conditions. Since the OSI protocols are not universally implemented, HL7 must be able to use protocols other than ISO OSI. The environments that HL7 can be implemented in include, but is not restricted to: a) Ad hoc environments that do not provide even basic transport reliability. Such environments consist of point-to-point RS-232 links, modems, and even LANs, if their connection to host computers is made via RS-232 communications links. In such an environment, the HL7 Lower Level Protocols (LLP) may be used between systems to enhance the capabilities of the communications environment. The HL7 Lower Level Protocols are defined in the HL7 Implementation Guide, which is not an official part of the Standard. b) Environments that support a robust transport level, but do not meet the high level requirements. This includes environments such as TCP/IP, DECNET, and SNA. c) ISO and proprietary networks that implement up to presentation and other high level services. IBM SNA LU6.2 and SUN s Microsystems NFS are examples of complete proprietary networks. s d) Two or more applications running on the same physical and/or logical machine that are not tightly integrated. In these environments, the messaging capabilities may be provided by inter-process communications services (e.g., Pipes in a UNIX System). The HL7 Standard assumes the communications environment will provide the following capabilities:

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

41

Lower-Layer Protocols

a) Error free transmission. Applications can assume that they correctly received all of the transmitted bytes in the correct order that they were sent. This implies that error checking is done at a lower level. However, sending applications may not assume that the message was actually received without receiving an acknowledgement message. b) Character conversion. If the two machines exchanging data use different representations of the same character set, the communications environment will convert the data from one representation to the other. c) Message length. HL7 sets no limits on the maximum size of HL7 messages. The Standard assumes that the communications environment can transport messages of any length that might be necessary. Note: Just as HL7 makes no assumptions about the design or architecture of the application systems sending and receiving HL7 messages, it makes no assumptions about the communications environment beyond those listed above. In particular, aside from the above assumptions, the communications environment, including its architecture, design and implementation, is outside the scope of HL7.

4.2. Lower Level Protocol Requirements


In the HL7 LLP environment a Start and an End character mark the beginning and end of a message. This allows other transport protocols to break a message into packets for transmission and then allow the re-assembly of the message again from the packets. For example with TCP/IP as the transport protocol and using Minimal LLP a process may read from a socket the incoming packets looking for a <start of message character> and then collect bytes from the socket until the <end of message character> is seen. At this point it knows that a complete HL7 message has been received and it then presents the collected bytes (without the start/end characters) to the HL7 parser. For example: Minimal LLP: Used in reliable transports, i.e., TCP/IP <SB>data<CR> more segments<CR> <EB><CR> eg <013>MSH||||||<CR>EVN||||||<CR><014>

42

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Lower-Layer Protocols

Where an unreliable transport mechanism is used, a checksum is used to mathematically determine that the data has arrived uncorrupted. For example: Hybrid LLP: used only for unreliable transports, i.e., serial. <SB>D21<CR> segment<CR> segment<CR> more segments<CR> cccccxxx <EB><CR> where c=length ( 5 bytes ) x=checksum ( 3 bytes ) and <CR> =0x0D, <SB>=0x0B, <EB>=0x1C eg <013>MSH|||||<CR>EVN|||||<CR>PID|||||<CR>cccccxxx<014>

The Lower Level Protocol (LLP) requirements for the RAPID project are based on the use of TCP/IP as the base communications protocol. It is a mandatory requirement that any external system wishing to communicate with the RAPID subsystems implements TCP/IP as the transport protocol. Any external system will also need to register with the RAPID management, the IP Address of the server which they will be using to send information to RAPID. RAPID will only accept information from the IP Address which is registered for that facility. RAPID will also only send HL7 information to registered facilities, and the information will always be sent to the IP Address that has been registerd for that facility. This means that machines for which IP Addresses are dymanically allocated will not be able to send information to any of the RAPID subsystems. RAPID will use the Minimal LLP, which is intended for use over error-free links and reliable transport protocols such as TCP/IP. The use of the Hybrid LLP is unnecessary in an IP environment. The checksums introduced by the use of the Hybrid LLP are for integrity checking across network links. With IP, checksums over data and header are inherent to the protocol. In particular with TCP the protocol will request retransmission if checksum errors are detected. So another checksum doesn add further protection but does add to transmission t overheads.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

43

Lower-Layer Protocols

4.3. Network Security


The security and protection of the data transmitted over Wide Area Network (WAN) links between entities in the RAPID project is the responsibility of the network service provider. Where the data is transmitted over the VicOne network, the service provider (AAPT) will provide data encryption at a network hardware layer. The specification of the encryption services is subject to negotiation between service providers, Allegiance and AAPT.

44

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Chapter 5 Reporting
Report requests will be transmitted to DWH using the T12 trigger. Report period can be specified using segments QRD and QRF. Hard copy reports will be produced and provided to the service provider the next day at latest. Report Definitions will be provided at a later date.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

51

Chapter 6 Scenarios
The following scenarios do not attempt to give a complete picture of a patient episode of care. They are intended to provide examples of s how the triggers and segments may be transmitted.

6.1. Emergency
Note: Nature of main injury, Body region, Description of injury event, Injury Cause, Human Intent, Type of place where injury occurred and Activity when injured are transmitted in the diagnosis code field of the DG1 segment. These data items are identified separate to the ICD diagnosis code by the name of coding system sub component of the diagnosis code.

Example 1 Joe is transported via an ambulance (case # 048851) to the emergency department at hospital AAAA. He is registered at 3:45pm on 27/8/99 and presents to triage 3 minutes later. A nurse first attends him at 3:57 pm and the doctor follows at 4:03pm. He is diagnosed with an eye injury and has an eye examination performed. He is subsequently discharged to go home at 4:32pm. A04 Register a patient
MSH|^~\&||AAAA||DWH|199808271545||ADT^A04|000008|P|2.3<cr> EVN|A04|199808271545<cr> PID|||0012345678^^^^PI||||19710105|1||1|^^CARNEGIE^^3163||||||||1234567890 1 JOS||||1102<cr> PV1||E||1||||1|||||||||||8888888|6|||||||||||||||||||AAAA|||||199808271545<cr> IN1|||HBA||||||||||||01<cr> ZEM|4||0000048851<cr>

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

61

Scenarios

A08 Update patient information


MSH|^~\&||AAAA||DWH|199808271550||ADT^A08|000008|P|2.3<cr> EVN|A08|199808271550<cr> PID|||0012345678^^^^PI<cr> PV1||E|||||||||||||||||8888888||||||||||||||||||||AAAA<cr> ZEM||||4|199808271548<cr>

A08 Update patient information


MSH|^~\&||AAAA||DWH|199808271605||ADT^A08|000008|P|2.3<cr> EVN|A08|199808271605<cr> PID|||0012345678^^^^PI<cr> PV1||E|||||||||||||||||8888888||||||||||||||||||||AAAA<cr> ZEM||||||199808271557|199808271603<cr>

A03 Discharge/end visit


MSH|^~\&||AAAA||DWH|199808271632||ADT^A03|000008|P|2.3<cr> EVN|A03|199808271632<cr> PID|||0012345678^^^^PI<cr> PV1||E|||||||||||||||||8888888||||||||||||||||||||AAAA||||||199808271632<cr> DG1|1||H571^Eye, painful/Ocular pain^ICD10AM <cr> DG1|2||H578^Eye,inflammation^ICD10AM <cr> DG1|3||13^Eye injury^NATINJ<cr> DG1|4||22^^BODREG<cr> DG1|5||^Cricket ball^DESCINJ<cr>

62

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Scenarios

DG1|6||24^Struck by or collision with object^INJCAU<cr> DG1|7||1^Accident^HUMINT<cr> DG1|8||A^Athletics and sports area^TYPLC<cr> DG1|9||S^Sports^ACTINJ<cr> PR1|1||83^Eye Examination^VEMD<cr>

Example 2 Joe is walks into the emergency department at hospital AAAA. He is registered at 3:45pm on 27/8/99 and presents to triage 3 minutes later. A doctor first attends him at 4:03pm. He is diagnosed with a migraine and has a CT scan performed. He is subsequently admitted to a ward for further observation at 4:32pm. A04 Register a patient
MSH|^~\&||AAAA||DWH|199808271545||ADT^A04|000008|P|2.3<cr> EVN|A04|199808271545<cr> PID|||0012345678^^^^PI||||19710105|1||1|^^CARNEGIE^^3163||||01||||1234567890 1 JOS||||1102<cr> PV1||E||1|||||||||||||||8888888|6|||||||||||||||||||AAAA|||||199808271543<cr> IN1|||HBA||||||||||||01<cr> ZEM|7<cr>

A08 Update patient information


MSH|^~\&||AAAA||DWH|199808271548||ADT^A08|000009|P|2.3<cr> EVN|A08|199808271548<cr> PID|||0012345678^^^^PI<cr> PV1||E||||||||||||||||||8888888|||||||||||||||||||AAAA<cr> ZEM||||1|199808271548<cr>

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

63

Scenarios

A08 Update patient information


MSH|^~\&||AAAA||DWH|199808271603||ADT^A08|000010|P|2.3<cr> EVN|A08|199808271603<cr> PID|||0012345678^^^^PI<cr> PV1||E|||||||||||||||||8888888||||||||||||||||||||AAAA<cr> ZEM||||||||199808271603<cr>

A03 Discharge/end visit


MSH|^~\&||AAAA||DWH|199808271632||ADT^A03|000011|P|2.3<cr> EVN|A03|199808271632<cr> PID|||0012345678^^^^PI<cr> PV1||E|||||||||||||||||8888888|||||||||||||||||2|||AAAA||||||199808271632<cr> DG1|1||R51^Headache^ICD10AM<cr> DG1|2||R42^Dizziness^ICD10AM<cr> PR1|1||43^CT Scan^VEMD<cr>

6.2. Admitted Episode


Note: Newborn details, Barthel and RUG ADL scores and Mechanical Ventilation hours are transmitted in the observation code field of the OBX segment. These data items are identified separate to other observations by the observation identifier field.

Example 1 Joe is admitted to a ward from the emergency department. He suffered a blow to the head. He was released from hospital the next day. A01 Admit/visit notification
MSH|^~\&||AAAA||DWH|199808271640||ADT^A01|12345678|P|2.3<cr>

64

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Scenarios

EVN|A01|199808271640<cr> PID|||0012345678^^^^PI||||19710105|1||1|^^CARNEGIE^^3163||||||||1234567890 1 JOS||||1102<cr> PV1||I|^^^^^2|E||||||||||C|||||8888888|PM1|||||||||||||||||||BBBB|||||199808271640<cr> PV2|||0|||||||2||||||||6<cr> PD1||1<cr> IN1|||HBA||||||||||||01<cr>

A03 Discharge/end visit


MSH|^~\&||AAAA||DWH|199808280932||ADT^A03|12345679|P|2.3<cr> EVN|A03|199808280932<cr> PID|||0012345678^^^^PI<cr> PV1||I|||||||||||||||||8888888|||||||||||||||||1|||BBBB||||||199808280932<cr> DG1|1||R220^Localised swelling mass and lump head^ICD10AM<cr> PR1|1||9090101^Magnetic resonance imaging of brain^ICD10AM<cr>

Example 2 Sarah is admitted for knee surgery from the booking list. A01 Admit/visit notification
MSH|^~\&||AAAA||DWH|199808271545||ADT^A01|12345680|P|2.3<cr> EVN|A01|199808271545<cr> PID|||0012345678^^^^PI||||19710105|2||1|^^CARNEGIE^^3163|||||1|||1234567891 1 SAR||||01<cr> PV1||I|^^^^^2|X||||||||||L||||4|8888888|PJ1|||||||||||||||||||BBBB|||||199808271545<cr> PV2|||0|||||||2||||||||1<cr> PD1||1<cr>

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

65

Scenarios

IN1|||HBA||||||||||||01<cr>

A03 Discharge/end visit


MSH|^~\&||AAAA||DWH|199809061000||ADT^A03|12345681|P|2.3<cr> EVN|A03|199809061000<cr> PID|||0012345678^^^^PI<cr> PV1||I|||||||||||||||||8888888|||||||||||||||||H|M^^REF||BBBB||||||199809061000<cr> DG1|1||M2361^Oth spont disrupt ant cruciate ligament^ICD10AM<cr> PR1|1||9058901^Repair of ligament,nec^ICD10AM<cr>

Example 3 John has stones that require attention. The procedure to be performed has been contracted out to hospital CCCC from hospital AAAA. John was not admitted to hospital AAAA. This represents hospital AAAA transmissions. A01 Admit/visit notification
MSH|^~\&||AAAA||DWH|199808271545||ADT^A01|12345682|P|2.3<cr> EVN|A01|199808271545<cr> PID|||0012345678^^^^PI||||19710105|2||1|^^CARNEGIE^^3163|||||1|||1234567891 1 JOH||||01<cr> PV1||I|^^^^^2|X||||||||||L||||4|8888888|PJ1|||||||||||||||||||AAAA|||||199808271545<cr> PV2|||0|||||||2||||||||1<cr> PD1||1<cr> IN1|||HBA|||||||||||3<cr>

A03 Discharge/end visit


MSH|^~\&||AAAA||DWH|199809061400||ADT^A03|12345683|P|2.3<cr> EVN|A03|199809061400<cr>

66

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Scenarios

PID|||0012345678^^^^PI<cr> PV1||I|||||||||||||||||8888888|||||||||||||||||H|G||AAAA||||||199809061300<cr> DG1|1||N200^Calculus of kidney^ICD10AM<cr> PR1|1||3654600^ESWL of urinary tract^ICD10AM<cr> ZFA|1|1|4|A|199809060900|199809061300|CCCC<cr>

6.3. Mental Health


Example 1 Kim is 28 years old, and has been registered by campus ZZZZ as a mental health client (Statewide number 1111111111). An incident occurs on 10/11/1998, and a CAT team (subcentre QQQQ) from campus BBBB attends. An unregistered contact is recorded for Kim. Contact A04 Register a Patient
MSH|^~\&||BBBB||DWH|199811102305||ADT^A04|0000012345|P|2.3<cr> EVN|A04|199811102305|||98675^^^^^^^^BBBB|199811102305<cr> PID|||UNREGISTERED^^^^SWUR<cr> PV1||C|QQQQ||||123456^^^^^^31^^BBBB|||||||||||5|||||||||||||||||||||BBBB<cr> ZMH||20|2||1|1|2|1|2|1||1234|A<cr>

Subsequently, the team take Kim to triage at a hospital (campus BBBB). Triage decide to register Kim, and record this on the system at approximately 1am, 11/11/1998. The Registration details are updated. A Client Search is performed on ODS, ODS returns a match for Kim as Statewide number 1111111111. Details are updated & Kim is registered at campus BBBB. Registration - A04 Register a Patient
MSH|^~\&||BBBB||ODS|199811110105||ADT^A04|0000012346|P|2.3<cr>

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

67

Scenarios

EVN|A04|199811110105|||98675^^^^^^^^BBBB|199811110105<cr> PID|||1111111111^^^^SWUR||Kimball^Kim^Nadia^^Ms||19700302|2|Kimball^Kimberley^Nadia^^Miss^^2^19700302^1^19981111^ZZZZ|4|123 Smith St^Collingwood^^VIC^3100||0395884621||01|1|0001||3900198883 1 ALB||||1102<cr> PV1||C||||||||||||||||5|REGISTRATION||||||||||||||||||||BBBB|||||199811110105<cr> PD1|3|1<cr> IN1|1<cr> IN2||||||||||||||||||||||||||||||||||||||||||||||99||S<cr> ZMH|||||||||||||||||||||||||||||||||0|81|08|D|1<cr>

On 12/11/98 an assessment is performed (at Campus BBBB) & the assessing clinician decides a community team (subcentre JJJJ) should treat Kim. Start case & start episode - A04 Register a Patient
MSH|^~\&||BBBB||ODS|199811121400||ADT^A04|0000012347|P|2.3<cr> EVN|A04|199811121400|||98675^^^^^^^^BBBB|199811112400<cr> PID|||1111111111^^^^SWUR<cr> PV1||C|JJJJ||||||||||||||||||||||||||||||||||||BBBB<cr> ZMH||||||||||||||9999999999|19981112||8888888888|19981112<cr>

The campus appoints a Case Manager for Kim on 20/11/1998. Start Case Management - A08 Update Patient Details
MSH|^~\&||BBBB||ODS|19981120||ADT^A08|0000012348|P|2.3<cr> EVN|A08|199811201600<cr> PID|||1111111111^^^^SWUR<cr> PV1||C|JJJJ||||||||||||||||||||||||||||||||||||BBBB<cr>

68

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Scenarios

ZMH||||||||||||||9999999999||||||1111|12385^^^^^^31^^BBBB|19981120<cr>

Wellbeing performed for Kim on 21/11/1998. Wellbeing - R01 Unsolicited Transmission of an observation message
MSH|^~\&||BBBB||DWH|19981121||ORU^R01|0000012349|P|2.3<cr> EVN|R01|19981121<cr> PID|||1111111111^^^^SWUR<cr> PV1||C|JJJJ||||||||||||||||||||||||||||||||||||BBBB<cr> OBR||||WELLBEING^1111<cr> OBX|1|RS2|WELLBEING|HNSADL|12||||||F|||19981121|| 67856788^^^^^^31^^BBBB<cr> OBX|2|RS2|WELLBEING|HNSADL|2^1~0^2~2^3~1^4~1^5~9^6~1^7~1^8~1^9~2^10~1^11~0^12<cr>

Time passes & Kim has been recommended, admitted and made involuntary. Throughout this time the community episode continues. A diagnosis is performed for Kim on 1/1/1999, the diagnosis is ???. Diagnosis A08 Update Patient Information
MSH|^~\&||BBBB||ODS|19990101||ADT^A08|1000222222|P|2.3<cr> EVN|A08|19990101<cr> PID|||1111111111^^^^SWUR<cr> PV1||I|||||||||||||||||987652||||||||||||||||||||BBBB|||||199811110105<cr> DG1|||F311^Bipolar affective disorder^ICD10AM^P~F101^Alcohol abuse^ICD10AM^A~G409^Suspected Epilepsy^ICD10AM^A~J459^Asthma^ICD10AM^A||19990101|||||||||||12345656^^^^^^31^^BBBB<cr> PR1|||5600100^CAT Scan^ICD10AM||1990101<cr>

Kim is separated from the inpatient unit on a CTO on 2/1/1999. (The legal status has previously been changed to s14.) The CTO requires 3monthly reporting.

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

69

Scenarios

Separation - A03 Discharge/End Visit


MSH|^~\&||BBBB||ODS|199901021100||ADT^A03|1000222223|P|2.3<cr> EVN|A03|199901021100<cr> PID|||1111111111^^^^SWUR<cr> PV1||I||||||||||||||||987652||||||||||||||||||A|||BBBB||||||1999010221100<cr> PV2||||||||||||||||||||||||||||||9<cr>

CTO - A04 Register a patient


MSH|^~\&||BBBB||ODS|199901021115||ADT^A04|1000222224|P|2.3<cr> EVN|A04|199901021115||||199901021115<cr> PID|||1111111111^^^^SWUR<cr> PV1||C|||||||||||||||||||||||||||||||||||||BBBB<cr> ZLE||123456^^CTO|09|987565^^^^^^01^^BBBB^^^^AUTHPSYCH~789678^^^^^^03^^BBBB^^^^SUPDOCTOR|||||||19990402~19990702~19991002~20000102| |||||||19990102|19990102|20000102|123456||0|||0||03<cr>

Kim is discharged from the CTO on 6/8/1999. Discharge CTO A03 Discharge/End Visit
MSH|^~\&||BBBB||ODS|19990806||ADT^A03|1000222225|P|2.3<cr> EVN|A03|19990806||||19990806<cr> PID|||1111111111^^^^SWUR<cr> PV1||C|||||||||||||||||||||||||||||||||||||BBBB<cr> ZLE||123456^^CTO|||02||||||||||||||||||1990806<cr>

Kim legal status is set to voluntary on 6/8/1999. The community episode continues. s

610

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

Scenarios

Legal Status - R01 Unsolicited Transmission of an observation message


MSH|^~\&||BBBB||ODS|19990806||ORU^R01|1000222226|P|2.3<cr> EVN|R01|19990806||||19990806<cr> PID|||1111111111^^^ODS^SWUR<cr> PV1||C|||||||||||||||||||||||||||||||||||||BBBB<cr> ZLE|||98|556667788^^^^^^01^^BBBB^^^^AUTHPSYCH|1||19990806<cr>

Victorian Health Level 7 (HL7) DWH and ODS Interface Specification, Issue 1.2

611

Вам также может понравиться