The LCSD simulator is developed in conformance with the IHE technical framework, that means that national extensions are not (yet) taken into account.
This simulator can be an Initiator and a Responder.
As an initiator, this simulator is aimed to send messages to a responder. So, if your system is ready to listen and accessible from the Internet, you will be able to send some messages to it.
As a Responder, this simulator is aimed to listen messages from an initiator.
By now, this simulator can act as two different actors:
The table below gathers the supported affinity domains, transactions and SUT actors.
The simulator has been developed with the purpose of helping the developers of actors, such as the_ Code Set Master_ and the Code Set Consumer actors. We have tried to manage most of the use cases, and most of message defined in the technical framework for those actors are supported by the simulator.
The following table summarize the actors, profiles and transactions supported by the LCSD simulator.
Integration Profile | Actor | Affinity Domain | Transaction | System Under Test |
---|---|---|---|---|
LCSD | CSM | IHE | LAB-51 | Code Set Master |
LCSD | CSC | IHE | LAB-51 | Code Set Consumer |
Today the simulator supports all type of messages defined in the TF for the LCSD profile, except the batch option for which further development is required.
First of all, note that, like the other applications from Gazelle testing platform, the HMW Simulator is linked to our CAS service. That means that, if you have an account created in Gazelle, you can use it, if you do not have one, you can create one now by filling the form here. Create an account in Gazelle is free. The login link (“cas login”) is located in the top right corner of the page.
If your system acts as an HL7 responder in one of the transactions offered by the simulator (for example your system is Code Set Consumer and supports LAB-51 transaction), you will have to enter its configuration in the application.
In order to proceed, go to “System Configurations” and hit the “Create a Configuration” button. You can also copy or Edit an existing configuration (one of yours !).
In both cases, the simulator needs to know:
If you are logged in when creating the configuration, you will be set as the owner of the configuration. If you do not want other testers to send messages to your SUT you can uncheck the box “Do you want this configuration to be public?” and you will be the only one to be able to select your system in the drop-down list and to edit it (if logged in!).
Before sending messages to your system under test, ensure that your firewall options give to LCSD Simulator the access to your system.
The CSM Simulator allows the users of the simulator to send Code Sets to CSC actors. The CSM simulator provides some sample Code Sets (at least one for each message type that can be used to feed client Code Set Consumer. In this case, the CSM Simulator acts as an initiator and the CSC SUT as a responder.
To communicate with your system under test, the simulator needs your system’s endpoint configuration. The CSC actor acts as a Go to the “How to get started” part of this tutorial for further details.
A tab with all messages for the transaction and the actor selected is available at the bottom. You can find your messages in using the filter fields.
You can display the codes send in each HL7 messages. To do that, just hit the buton in the action column. A new window will appear to display all codes contained in the selected HL7 message and send by the CSM actor.
The simulator can act as a Code Set Consumer and receive messages from a distant system that implements the Code Set Master actor.
You can display the codes send in each HL7 messages. To do that, just hit the buton in the action column. A new window will appear to display all codes contained in the selected HL7 message and send by the CSM actor.
The CSC Simulator is a responder and is able to respond to your CSM SUT with the appropriate Acknowledgment message. If the CSM message send to the CSC Simulator is not consistent with the IHE technical framework, the CSC will respond with an error Acknowledgment.
For further details about this functionnality of the LCSD Simulator, go to the HL7 messages validation page.