How to use the HL7 Proxy during the Connectahton
From IHEWiki
Contents |
HL7 proxy
We provide an HL7 proxy during the connectathon, that helps checking the content of the HL7v2 messages exchanged during the connectathon. You are not forced to use the proxy, however using the proxy helps you find problems within your messages.
Advantages of using the proxy
- Capture and verification of the messages exchanged.
- Easier to show the monitors that you have done the work and that your messages were correct.
See kudu under Connectathon-->HL7 Proxy
How does it work
Each HL7 receiving actor is assigned a port on the HL7 Proxy machine (hl7-proxy.ihe-europe.net or 192.168.0.12 in Vienna 2009). See gazelle under Configurations--All Configurations to find out the proxy port number of your peers.
So whenever vendor A is testing with vendor B, and B receiving is HL7 messages, vendor A may send its HL7 messages directly to B, or it may chose to send them to via Proxy on the port indicated in red.
Each actor receiving HL7 messages is assigned a port on the proxy.
How to view captured messages in Kudu
If your system is implementing an actor that receives or send HL7 V2 messages, then you have the possibility to visualize the captured messages through the kudu interface.
As shown on the following figure the "Connectathon" menu in Kudu offers a link to the "HL7 Proxy" page
From this page the user has access to the incoming and outgoing messages.
The user has then access to the incoming messages sorted out by whom send it. The proxy knows only the hostname/ip address of the sender.
Finally when selecting a specific message in the list, the user has access to the validation of the message by the External Validation Services (EVS) developped for Gazelle. The page shows
- the message that is validated with syntax highlight.
- a link to the HL7 Message profile used for the validation
- Validation result from the NIST and/or the INRIA EVS
