Australian Diagnostic Testing eMessage Validator v1.24
About us Help Contacts Home

Healthbase HL7 Testing:


This version is no longer supported. A newer version is available here.

This service tests user-chosen HL7 messages for compliance against Australian Standard AS4700.2(2007) - Implementation of Health Level Seven (HL7) Version 2.4 Part 2: Pathology and medical imaging (diagnostics) You can upload an HL7 message file for parsing, and view the resultant report. Alternatively, a number of sample messages can be validated. The sample files include the samples in Appendix B of AS4700.2. Please refer to the Compliance Checklist for the details of checks currently performed. The functionality of this service may be subject to frequent change, hopefully for the better.

Select your local HL7 message file for upload:

File:






  OR  

Choose Sample File:


HTML_escaped.oru
cancer_registry_report_IHE.oru
cancer_report_staging_NZ.oru
errors.orm
jpg_test.oru
jpg_time_series.oru
medical_imaging_order+errors.orm
medical_imaging_order.ack
medical_imaging_order.orm
medical_imaging_order_response.orr
medical_imaging_unsolicited_observation.oru
micro+pdf.oru
outpatient_PBS_prescription.rde
pathology_blood.oru
pathology_micro.oru
pathology_order.ack
pathology_order.oml
pathology_order_response.orl
pathology_unsolicited_observation+RTF.oul
pathology_unsolicited_observation+RTF2.oul
pathology_unsolicited_observation.oul
rtf+HL7FT+PIT.oru
x_archetype_urine_culture.oru


Acknowledgements: Eric Browne - for web site production, HL7 parser/validator development and LOINC/SNOMED integration; Russell McDonell - for bar2xml and other python utilities; Andrew McIntyre & Medical Objects - for sample messages and useful HL7 and pathology messaging documentation; members of Standards Australia IT-014-06-05 subcommittee- for AS4700.2 and HB262; The US Public Health Information Network (PHIN) & Vocabulary Access and Distribution Service (VADS) - for inspiration; Brendon Hogger for the pyth RTF to HTML parser.

L E G E N D

[ hint: mouse over labels below images for more information ]

OML Message icon ORL Message icon OUL Message icon ORM Message icon ORR Message icon ORU Message icon MSH Segment icon PID Segment icon PV1 Segment icon OBR Segment icon OBX Segment icon
Lab order An OML message is an order for a laboratory test. Lab order response An ORL message is a pathology order response message. Lab report An OUL message is an unsolicited pathology observation message. Imaging order An ORM message is an order for a medical imaging test. Imaging order response An ORR message is a medical imaging order response message. imaging report An ORU message is an unsolicited medical imaging observation message. MSH SEGMENT A Message Header segment describes the type of message and other associated metadata. All HL7 messages must contain a MSH Segment. PID SEGMENT A Patient Identifier segment carries information about the patient, including name, date of birth, sex and contact details. PV1 SEGMENT A PV1 segment carries information about the patient visit. to communicate information on a visit specific basis. This segment can be used to send multiple visit statistical records to the same patient account, or single visit records to more than one account. OBR SEGMENT An OBR segment carries information about the observation request. It can appear in both an order message to identify the nature of an order being requested. Multiple OBR segments can appear in the one order message - one for each test ordered. OBX SEGMENT An OBX segment normally carries information about the observation result, although it may also appear in an order, to carry clinical information pertinent to the test, such as patient height or weight. Multiple OBX segments can appear in the one result message.
Datatypes: AD:Address, CE:Coded Entry, CF:Coded Element With Formatted Values, CK:Composite ID With Check Digit, CN:Composite ID And Name, CP:Composite Price, CWE:Coded with Extensions, CX:Extended Composite ID With Check Digit, DT:Date, ED:Encapsulated Data, FT:Formatted Text (Display), MO:Money, NM:Numeric, PN:Person Name, RP:Reference Pointer, SN:Structured Numeric, ST:String Data, TM:Time, TN:Telephone Number, TS:Time Stamp (Date & Time), TX:Text Data (Display), XAD:Extended Address, XCN:Extended Composite Name And Number For Persons, XON:Extended Composite Name And Number For Organizations, XPN:Extended Person Name, XTN:Extended Telecommunications Number
[about] [disclaimer] [help] [contacts] [home]
Copyright © 1999-2011 Healthbase Australia.