|
LINKTools® IDK Tutorial: HL7 Order/Result Interface Overview |
LINKTools® HL7 Order/Result Interface
The interface is triggered by the availability of HL7 Order messages
from HIS Ordering System. HL7 Order messages are transmitted via TCP/IP
Minimal Lower Protocols (MLLP) to LINKTools® Interface server. LINKTools®
Interface receives processes or filters this data to its internal intermediate
database and then inserts patient demographics to vendor system. Alternatively
vendors system can import patient demographics using WebSelect client
application or from file output to a shared folder directory.
Upon completion of study or review by the reading physician, the test
results then output to LINKTools® interface for processing to HL7
result messages (ORU) and send back to the HIS or EMR systems.
Note: LINKTools® Order/Result Interface by default also accepts ADT update patient information (ADT^A08) and ADT merge patient information (see table below). ORU message can be customized
What you need: LINKTools® IDK toolkit
Ideal Interface: Uni-directional (HIS to your system) or Bi-directional
(HIS to your system and report from your system to HIS)
LINK Medical Interface Services: LINK Medical provides all
the resource needed to build your Uni or bi-directional HL7 interface
from start to go live. A cost-effective way to get more of your interfaces
done and your company revenue up
-
Inbound interface
HIS (OE) sends HL7 messages----------> LINKTools® TCP/IP Receiver-----------> Parsed HL7 to Vendor's System
-
Outbound Interface
Vendor's System creates study result----------> LINKTools® Interface creates HL7 result message----------> LINKTools® HL7 TCP/IP Transmitter sends HL7 result message-------->HIS or EMR systems
|
HL7 Trigger Event
|
Event Code
|
Minimum HL7 segment
|
| Order Message |
ORM^O01
|
MSH, PID, PV1, ORC, OBR
|
| Update Information |
ADT^A08
|
MSH, PID, PV1
|
| Merge patient Information |
ADT^A18, A30, A34, A35, A36
|
MSH, {PID}, [PD1], MRG
|
