AUSTPATH (Australian Pathology Code Set) - Sets of Pathology request and result codes recommended for use within Australia.
Conversion Utility - A useful utility
for removing those pesky linefeed characters from your HL7 messages.
HL7 v2.3.1 - AS4700.2 2004, Pathology Orders and Results - Amdt 1-2006 - Messages - The Standards Australia working committee, IT-14-6-5, who produce the Australian Standard for Pathology and Diagnostic Imaging, AS4700.2 have provided a set of trusted messages which conform to the standard.
SMD Service Categories - Service Categories for Secure Message Delivery.
Question. My HL7 messages are generating one of the following errors:
INVALID LINEFEED CHARACTERS HAVE BEEN FOUND IN THE MESSAGE or
MESSAGE HAS TRAILING CHARACTERS AFTER THE LAST SEGMENT
What is going on?
Answer. HL7 2.3.1 messages are
broken into segments by the use of a carriage return (hex 0D) character.
The next three characters after a carriage return specify the identity
of the next segment. DOS and Windows based editors signify a newline
by using a combination carriage return AND linefeed character (hex
0A). If you have used a DOS or Windows based editor to generate
or modify your message (or used ASCII based FTP) then it is probable
that your message includes the linefeed character before each segment,
which is unrecognisable for the purposes of segment delineation
in HL7. We suggest that you make sure your message has no linefeed
characters by using a conversion utility
to convert from DOS based text to the correct HL7 message format, which will remove
Question. If I submit an OBX in the following
I get the following error:
Element no: 6 Component no: 3 Description:
name of coding system Data type: ST Value: Component is empty!
ERROR: MANDATORY COMPONENT IS MISSING -> (CONDITION: OPTIONALITY
is 'R' IF (SUB)COMPONENT 1 IS VALUED) See HL7 v2.3.1 Chapter 2.8.3
Answer. The Element OBX-6 is
a CE data type, which must have first and third field populated
or fourth and sixth field populated. When you look at all of the
examples of ORU messages in HL7 v2.3.1 NONE of the examples have
the third sub-component of OBX-6 populated. We are waiting clarification
from HL7 inc on this matter.