Configuration - Open Vista/Mirth on AWS
MY STEPS TO SET UP HL7 TO TALK TO A MIRTH CHANNEL
MY Config:
1. Two applications: A) MEDSPHERE (Predefined)
1. Two applications: A) MEDSPHERE (Predefined)
Name: MEDSPHERE
ACTIVE/ INACTIVE: ACTIVE
Facility Name: MEDSPHERE@MIDLAND
Country Code: USA
HL7 Field sepoarator : |
HL7 Encoding characters: ^~\&
B) TESTAWS (new application)
Name: TESTAWS
ACTIVE/ INACTIVE: ACTIVE
Facility Name: AWS VISTAVIS
Country Code: USA
HL7 Field sepoarator : |
HL7 Encoding characters: ~^\&
2. Logical Link - Used MSCS HL7 (already defined by Medspehere) - TCP entries
Service type: Client (sender)
TCP/ IP Address: Address of my cloud server where mirth is running
TCP/IP Port: 5002
TCP/IP Port (Optimized) - 5002 (Although I think I do not need to define it)
ACK TIMEOUT:5
RE-TRANSMISSION ATTEMPT: 5
READ TIMEOUT:10
EXCEE RETRANSMIT ACTION : shutdown
BLOCK SIZE: 512
SAY HELO:
PERSISTENT: YES
3. Two Protocols: A )MSC A08 SERVER (Predefined by Medsphere)
Type: event driver
sending appl: MEDSPHERE
Transaction Message Type: ADT
Event type: A08
Processing ID: debug
Version : 2.3
Su8bscribers: MSC A08 CLIENT
B) MSC A08 CLIENT:
Receiving app: TESTAWS
Event type: A08
Sending Facility reqd: No
Receiving facility reqd: No
Security reqd: No
Logical Link: MSCS HL7
Processing RTN: Q
MIRTH: SOurce is set to :
connector type : LLP listener
LLP Mode: Server
Listener address: 127.0.0.1 (as mirth is on the same physical server)
Listener Port: 5002
MY STEPS TO SET UP HL7 TO TALK TO A MIRTH CHANNEL
- Set up Application: HL7 Main Menu Option -> Interface Developer Options -> EA Application Edit ->Iput the new app name (should be your application like PIMS etc
- Set up Protocol - (do we need this? ) HL7 Main Menu Option -> Interface Developer Options -> EP Protocol Edit
- Site Parameter Edit - HL7 Main Menu -> SIte Parameter Edit (set up current domain, current institution, whether prod or test account)
- Define Logical Link (maybe even create new one) : HL7 Main Menu Option -> Filer and Link Management Options-> ED Link Edit
- SL (STart Stop Links) -??
- LM (TCP Link Manager start/ Stop) -??
- FM (monotor start stop filers) -??
- Finally Ping (and input the link name) - ping seemed to work; not any more
My Log
6-feb-10: stopped incoming filer. Kept outgoing filer on. added an allergy and pinged 'iktest' . data was transmitted fine
7-feb-10: Stopped all filers. added an allergy data, pinged iktest. No data transmitted., However, message queue did have MSCS HL7 data in error for the added record. How?? iktest and MSCS HL7 have same link definition.
6-feb-10: stopped incoming filer. Kept outgoing filer on. added an allergy and pinged 'iktest' . data was transmitted fine
7-feb-10: Stopped all filers. added an allergy data, pinged iktest. No data transmitted., However, message queue did have MSCS HL7 data in error for the added record. How?? iktest and MSCS HL7 have same link definition.
8-feb-10: defined 2 new protocols, 2 apps and used the logical link created earlier. Stopped all links. Just started new one. Still looks like MSCS HL7 became active inspite of my stopping it. So I see the message in the message queue. But does not go through interface to the destination.
14-Feb-10: Now I can see messages in my queue with "TRANSMISSION PENDING" status, but do not see them on Mirth.
From VDL Doc (SIte manager's manual) -
http://www4.va.gov/vdl/documents/Infrastructure/Health_Level_7_%28HL7%29/hl71_6p56_p66.pdf
3.5 HL7 Startup
3.5.1 Manual Startup To manually start up VISTA HL7, execute the following steps in the listed order:
1.Use the "Restart/Start All Links and Filers" option to start the default number of filers, and all links whose "Autostart" field is enabled (including non-UCX TCP/IP listeners).
2.Use the "TCP Link Manager Start/Stop" option to start the TCP Link Manager.
3.For OpenVMS sites only, start up any UCX-based TCP/IP Listener processes according to the guidelines provided in the "Managing TCP/IP Listeners" chapter.
3.5.2 Automatic Startup You can set up the VISTA HL7 background processes to start automatically on system boot:
Process How to Automatically Start on System Boot
Filers & Links
1.Go to TaskMan Management | Schedule/Unschedule Options. Add [HL TASK RESTART] ("Restart/Start All Links and Filers") as an option to schedule. Set SPECIAL QUEUEING to "Startup Persistent". Doing this will run this option at system startup.
2.For each link that you want to start automatically on system boot, set the link's AUTOSTART field to ENABLED. Each link set this way will be started by the "Restart/Start All Links and Filers" option.
3.Use VISTA HL7's site parameters to set the default number of incoming filers and outgoing filers. This number of filers will be started by the "Restart/Start All Links and Filers" option.
2.For each link that you want to start automatically on system boot, set the link's AUTOSTART field to ENABLED. Each link set this way will be started by the "Restart/Start All Links and Filers" option.
3.Use VISTA HL7's site parameters to set the default number of incoming filers and outgoing filers. This number of filers will be started by the "Restart/Start All Links and Filers" option.
TCP Link Manager
1. Go to TaskMan Management | Schedule/Unschedule Options. Add [HL AUTOSTART LINK MANAGER] ("Autostart Link Manager") as an option to schedule. Set SPECIAL QUEUEING to "Startup Persistent". Doing this will run this option at system startup.
TCP Listeners
Varies depending on system type. Please see the "Managing TCP/IP Listeners" chapter for more information.
December 1999 HL*1.6*56: VISTA HL7 Site Manager & Developer Manual 3-13
_______________________________________________________________________________December 1999 HL*1.6*56: VISTA HL7 Site Manager & Developer Manual 3-13
Managing a VISTA HL7 System
3.6 HL7 Shutdown
When you shut down your system, you should include shutting down VISTA HL7 as part of your normal shutdown procedure. Explicitly shutting down VISTA HL7 helps avoid message resynchronization problems between systems.
To gracefully shutdown VISTA HL7, execute the following steps in the listed order:
1.For OpenVMS sites only, if you have any TCP/IP listeners implemented through UCX, use UCX to shut those listeners down. Do this by disabling the each listener's service in UCX.
2.Stop the TCP/IP Link Manager with the "TCP Link Manager Stop/Start" option.
3.Run the "Stop All Messaging Background Processes" option. This stops all running links, filers and non-UCX TCP listeners.
HL7 System Actors
* A client (subscriber) protocol set up for each destination for each message transaction type.
* HL LOGICAL LINK entries set up for each destination system, with all appropriate information including IP address and port.
All messages generated through the server (event driver) protocol will be directed to all appropriate client (subscriber) protocols, including receivers whose HL LOGICAL LINK identifies them as connected through TCP/IP.
[11:43:49 AM] richard.braman: http://www.va.gov/vdl/documents/Infrastructure/Health_Level_7_%28HL7%29/hl71_6p19.pdf
3.6 HL7 Shutdown
When you shut down your system, you should include shutting down VISTA HL7 as part of your normal shutdown procedure. Explicitly shutting down VISTA HL7 helps avoid message resynchronization problems between systems.
To gracefully shutdown VISTA HL7, execute the following steps in the listed order:
1.For OpenVMS sites only, if you have any TCP/IP listeners implemented through UCX, use UCX to shut those listeners down. Do this by disabling the each listener's service in UCX.
2.Stop the TCP/IP Link Manager with the "TCP Link Manager Stop/Start" option.
3.Run the "Stop All Messaging Background Processes" option. This stops all running links, filers and non-UCX TCP listeners.
Notes from Richard Braman:
HL7 System Actors
If the sending system is a VISTA system, the sending application (as defined in the Interface Workbench on the sending VISTA system) must have:
* A server (event driver) protocol set up for each message transaction type.
* A client (subscriber) protocol set up for each destination for each message transaction type.
* HL LOGICAL LINK entries set up for each destination system, with all appropriate information including IP address and port.
All messages generated through the server (event driver) protocol will be directed to all appropriate client (subscriber) protocols, including receivers whose HL LOGICAL LINK identifies them as connected through TCP/IP.
[11:43:49 AM] richard.braman: http://www.va.gov/vdl/documents/Infrastructure/Health_Level_7_%28HL7%29/hl71_6p19.pdf
http://www.hl7.org/implement/standards/v2messages.cfm
Glossary:
Monitor:
Incoming Filer:
Outgoing Filer:
Logical Link:
Node: e.g. MSCS HL7, NPTF, PSOTPBAA
HL Logical Link Node: e.g. MSC ALG, RA-MED
This is the name of the logical link that data will be communicated on. It is this name that will be displayed in the "NODE" column of the SYSTEMS LINK MONITOR display option. It is suggested that this name be the same name as the commercial application e.g. KURZWEIL1,KURZWEIL2,COPATH, or SUNQUEST1.
You may enter a new HL LOGICAL LINK, if you wish
Monitor:
Message:
Filer: relation with task?
Incoming Filer:
Outgoing Filer:
Queue:
