.
   

LINKMED® HL7 TCP/IP Communication Drivers_Basic
LINKMED® HL7 TCP/IP Communication Drivers communicate with remote systems through TCP/IP socket connections. HL7 messages can be wrapped using HL7 MLLP protocols or user-defined protocols (headers and trailers). The LINKMED® TCP/IP Drivers communication protocols are configured in the Drivers Options Configuration window.
LINKMED® HL7 TCP/IP Communication Drivers can send and receive information in virtually any formats over any protocols, effectively bridging other systems with the LINKMED® Interface environment.
Currently there are two types of LINKMED® HL7 TCP/IP Receiver (File-based Receiver and Mapper-based Receiver)
File-based Receiver: Coverts inbound HL7 stream to HL7 message
Mapper-based Receiver: Parses inbound HL7 stream directly to LINKMED® interface intermediate database and client's SQL database or to output directory. The following are basic functionalities of the LINKMED® HL7 TCP/IP Receiver and Transmitter.

LINKMED® HL7 TCP/IP Drivers communicate over two TCP/IP sockets (ports):
  • ADT/Order port: LINKMED® HL7 TCP/IP Receiver is the "server", accepting connections from client(s). HL7 ADT/Order messages are sent over this socket, and acknowledgements for those messages are sent back over the same socket. LINKMED® HL7 TCP/IP Receiver accepts connection from the HIS on ADT/Order port immediately upon system start
  • Report port: LINKMED® HL7 TCP/IP Transmitter is the "client", connecting to the HIS. Reports are sent over this socket, and acknowledgements for those reports are expected over the same socket.
    LINKMED® HL7 TCP/IP Transmitter attempts to connect to the HIS server upon system start up
Sending HL7 Message Acknowledgements:
LINKMED® HL7 TCP/IP Receiver automatically sends standard HL7 ACK to the sender system (client) following sucessful receiving HL7 ADT message and sends "Order Response" ACK (ORR^O02) following sucessful receiving ORM message.
  • The ACK message is formatted as follow:
    ADT message ACK:
    MSH|^~\&|SA|SF|RA|RFI|200409121433||ACK|4000156|P|2.3|
    MSA|AA|CHPFORDR|| -9999
    Order Response (ORR) message ACK:
    MSH|^~\&|SA|SF|RA|RFI|200409121433||ORR^O02|4000156|P|2.3|
    MSA|AA|CHPFORDR|| -9999
    AA=Application Accept- LINKMED® accepted the message
  • The NAK message is formatted as follow:
    ADT message NAK:
    MSH|^~\&||LINKMED|||200409121433||ACK|24595796|P|2.4|
    MSA|AR|L1085514220875|Invalid Version (2.4)|-9999
    Order (ORM) message NAK:
    MSH|^~\&||LINKMED|||200409121433||ORR^O02|24595796|P|2.4|
    MSA|AR|L1085514220875|Invalid Version (2.4)|-9999
    AR=Application Reject- LINKMED® rejected the message. The text message in MSA sequence 3 contains reason(s) for the rejection
  • Receiving HL7 Message Acknowledgments:
    LINKMED® HL7 TCP/IP Transmitter expects HIS or EMR system to send HL7 ACK message back on every successful result message received. The ACK message should be formatted as follows:
    MSH|^~\&|SA|SF|RA|RFI|200409121433||ACK|4000156|P|2.3|
    MSA|AA|CHPFORDR|| -9999
    MSA= Position 1
    AA=Application Accept- HIS or clinical system accepts LINKMED® result message
    AR=Application Reject- HIS rejects LINKMED® result message

Next>>>



HL7 TCP/IP Receiver (File-based)



HL7 TCP/IP Receiver (Mapper-based)


HL7 TCP/IP Transmitter

Next>>>

..........................................................................................................................................................

| Home | Products | Partners | Contact | News | Contact Us |

 

 

© Copyright LINK Medical Computing, Inc. All rights reserved Terms of Use.