Scribd
Upload
245 views7 pages

HL7 Communication Protocol For Quintus

Quintus can send measurement results to and receive work lists from a remote HL7-capable server by connecting directly or over a network. To enable this, the user must configure the IP address and port of the HL7 server in the Send settings menu. Measurement results are sent automatically after each test or manually by clicking Print/Send. To receive work lists, the user turns on Receiving LIS command in Send settings. Work lists are displayed on screen and the user loads samples in the order listed. Bidirectional HL7 messaging examples show the structure of messages sent from the server with a work list to Quintus and the acknowledgment message sent back.

Uploaded by

Diego Andres Beltran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
245 views7 pages

HL7 Communication Protocol For Quintus

Quintus can send measurement results to and receive work lists from a remote HL7-capable server by connecting directly or over a network. To enable this, the user must configure the IP address and port of the HL7 server in the Send settings menu. Measurement results are sent automatically after each test or manually by clicking Print/Send. To receive work lists, the user turns on Receiving LIS command in Send settings. Work lists are displayed on screen and the user loads samples in the order listed. Bidirectional HL7 messaging examples show the structure of messages sent from the server with a work list to Quintus and the acknowledgment message sent back.

Uploaded by

Diego Andres Beltran
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

HL7 functionality

Quintus is able to send measurement results to and receive so-called work lists from a
remote computer. To activate and use this feature, Quintus needs to be connected to a HL7
capable server directly or through a computer network.
Quintus sending measurement data to the server
Setup
Go to Main / Settings / Send settings

The following data have to be provided:


- Export type: Send to LIS
- Communication port: Ethernet
- IP address of the HL7 server
- Communication port of the HL7 server
Upon setting and saving the above settings, Quintus is ready to send measurement results to
the server.
Usage
Sending data takes place at the end of each measurement automatically and can also be
initiated by the user through the menu system by clicking on the Print/Send button.
Quintus sends a specified data package adhering to HL7 standards. The message and its
setup are described at the end of this document.

Quintus receiving work list from the server


Setup
Go to Main / Settings / Send settings

The following data need to be provided:


-

Receiving LIS command: ON / OFF

Upon setting and saving the above setting Quintus is ready to receive work lists from the HL7
server.
Usage
Work list information is only relevant in Free List mode only the sequence of the samples
in the auto sampler need to match the sequence of the work list.
When entering auto sampler menu, you need to select Free list mode.

A screen is displayed with sample information received as the work list.


Status of messages and the communication can be seen in the lower left corner.
<screenshot: Remote WL (Free list): table, and received WL items..>
Make sure you follow the sequence set in the work list when loading samples into the racks
of the auto sampler.
After loading the samples, autoloader can be started with the Start button.

Bidirectional example of HL7 Messages

Figure 1 shows an example of a HL7 message v. 2.5 to be sent to Quintus as a Work List Item.
MSH|$~\&|7EDIT$XYZ_ID||||20100427163520||ORM$O01|4534|P|2.5||||||WINDOWS-1250
PID|||344||Doe$John||19970527163718|F|||||||||||123465798
ORC|NW|5465
OBR||5465||XYZ_Sample_ID||20100527164606

Figure 1
The descriptions of the Message Header (MSH), the Patient ID (PID), the Common Order (ORC) and
the Order Observation Request (OBR) can be seen on the following images:

i.e.: MSH|$~\&|7EDIT$XYZ_ID||||20100427163520||ORM$O01|4534|P|2.5||||||WINDOWS-1250
1. | is the Field Separator
2. $~\& is the Encoding Characters
3. 7EDIT$XYZ_ID is the Sending Application. which contains the Namespace ID and the
Universal ID
4. etc.

i.e.: PID|||344||Doe$John||19970527163718|F|||||||||||123465798
3. 334 is the first element (ID Number) of Patient Identifier List
5. Doe$John is the Family and the Given Name of Patient Name
7. 19970527163718 is the Date/Time of Birth

8. F Administrative Sex (The value can be: A - Ambiguous, F - Female, M Male, N


Not applicable, O - Other, U - Unknown)
19.
SSN Number - Patient

i.e.: ORC|NW|5465
This segment provides information for Work List. The Entity Identifier (5465) is used to identify the
Work List.

i.e.: OBR||5465||XYZ_Sample_ID||20100527164606
2.

5465 The Entity Identifier has to be the same as the Entity Identifier of ORC segment.

4.

XYZ_Sample_ID The Identifier of Universal Service Identifier is used for Sample ID.

After Analyzer processed the request a general acknowledge is sent back, which can be seen on
Figure 2.

MSH|$~\&|||7EDIT$XYZ_ID ||20100427163520||ACK|4534|P|2.5
MSA|AA|4534

Figure 2
Figure 2 is a requested and acknowledged Work List Item. The whole list is built up on the Analyzer
by receiving the sequence of the Work List Items. The Work List Items with the same Common Order
(ORC) segment belong to the same Work List.
The analyzer will refuse the request (and will an AR (Application Reject) message), if the number of
samples in the Work List exceeds 100.
The first field of MSA segment in the acknowledged message is used to define whether Analyzer
accepted the Work List Item or not.
AA Application Acknowledgment,
AR Application Reject

You might also like