LINKMED® Interface Tutorial:
LINKMED® HL7 Result Interface Overview

LINKMED® HL7 Result (ORU) Interface Uni-directional

LINKMED® HL7 ORU interface supports all version of HL7 unsolicited ORU messages (2.1, 2.2, 2.3, 2.3.1, 2.4, 2.4.1, 2.5, 2.6), XML, DICOM, Text Reports, CSV, SQL and others format…
LINKMED® HL7 result Interface can be configured to parse HL7 ORU to "What you want" format or to convert non-HL7 to HL7 ORU format.
Example of result message: Lab results, Transcription reports, vital-signs, Resting ECG report, Stress Test reports, Holter Monitor Reports etc... can be converted from HL7 to non-HL7 or from non-HL7 to HL7 (any version)

What you need: LINKMED® IE software
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

Save your company development time and resource by puchasing LINKMED® Interface Services with LINKMED® IE. LINK Medical provides all resources needed to build Uni-directional or Bi-directional HL7 interface from start to go live. LINK cost-effective full interface services includes: Interface tele-Con with your client, LINKMED® system integration engineer assigned to your account, your interface documentation after "Go Live", interface support training and seamless transitioning from our integration team to yours.


  • Inbound interface


    HL7 ORU messages---------->LINKMED® IE ---------> Parsed HL7 Result to Vendor's System

    or


    Non-HL7 Result reporting messages----------> LINKMED® IE -----------> creates HL7 ORU Messages
    ----->LINKMED® HL7 TCP/IP Transmitter sends HL7 result message-------->HIS or EMR systems


HL7 Trigger Event
Event Code
Minimum HL7 segment
Unsolicited HL7 Result Message
ORU^R01
MSH, PID,[{ORC}], {OBR}, {OBX}
Non-HL7 (XML, SQL, CSV, Text Report)
Creates
ORU^R01
MSH, PID, [{ORC}], {OBR}, {OBX}
 

 


| 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9|10|