We are using DG REGISTER PATIENT. We confirmed that 1. HL7 PING works from WorldVistA to Mirth using the setup below; 2. that CALL^%ZISTCP successfully communicates with Mirth. So we know it's not a Mirth issue.
Here's the Logical Link:
Select HL LOGICAL LINK NODE: MIRTH TCP
ANOTHER ONE:
STANDARD CAPTIONED OUTPUT? Yes// (Yes)
Include COMPUTED fields: (N/Y/R/B): NO// - No record number (IEN), no Computed
Fields
NODE: MIRTH TCP LLP TYPE: TCP
STATE: Enabled TIME STARTED: FEB 17, 2010@12:59:43
SHUTDOWN LLP ?: NO QUEUE SIZE: 10
TCP/IP ADDRESS: 127.0.0.1 TCP/IP PORT: 12346
TCP/IP SERVICE TYPE: CLIENT (SENDER)
Here are the protocols that DG REGISTER PATIENT fires:
NAME: VAFC ADT-A04 SERVER
ITEM TEXT: This protocol fires off of the PIMS Registration option
TYPE: event driver CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: REGISTRATION
DESCRIPTION: This server protocol fires when a patient is registered. It
generates a Health Level Seven (HL7) register a patient (event code A04)
message.
TIMESTAMP: 60991,21593 SENDING APPLICATION: VAFC PIMS
TRANSACTION MESSAGE TYPE: ADT EVENT TYPE: A04
PROCESSING ID: P ACCEPT ACK CODE: NE
APPLICATION ACK TYPE: NE VERSION ID: 2.3
SUBSCRIBERS: RG ADT-A04 TRIGGER
NAME: RG ADT-A04 TRIGGER
ITEM TEXT: MPI/PD ADT-A04 Trigger Protocol
TYPE: subscriber CREATOR: WVEHR,PATCH INSTALLER
PACKAGE: CLINICAL INFO RESOURCE NETWORK
DESCRIPTION: This protocol is used as an internal process of the A04
messages. The protocol will read in the message and reformat to the HL7 v2.4
standard with Application and Commit acknowledgements turned on.
TIMESTAMP: 59147,62050 RECEIVING APPLICATION: RG ADT
EVENT TYPE: A04 LOGICAL LINK: MIRTH TCP
RESPONSE MESSAGE TYPE: ACK PROCESSING ROUTINE: Q
SENDING FACILITY REQUIRED?: YES RECEIVING FACILITY REQUIRED?: YES
ROUTING LOGIC: D PROC^RGADTP
--
Sam Habiel
