The XCPD Responding Gateway simulator is developed in conformance with the IHE Technical Framework. It also implements the epSOS extension to the profile. It has been developed to simulate the Responding Gateway actor of the XCPD (Cross Community Access) integration profile in connectathon (or pre-connectathon) tests when needed. This tool can participate as a responder in many tests like XCPD_Patient_Discovery thanks to its web service methods which provide to Gazelle a mean to communicate with it. A Web GUI is also available and enables the users to see their message sended to this simulators. Also, we can via the GUI request directly the database of XCPD Responding simulator by XCPD request message. Note that this tool is able to respond to requests using TLS, using the port 8443.
This simulator also supports the XUA (Cross Enterprise User Authentication) profile and can act as a X-Service User actor.
First developed for epSOS purposes, the epSOS instance of this simulator validate the assertion.
Transactions and Messages supported
As a Responding Gateway for XCPD, this simulator supports the ITI-55 transaction.
HomeCommunityId of th XCPD Responding Simulator
To communicate with the web service of the simulator responding gateway, the HL7V3 request must contain the following homeCommunityId : 18.104.22.1680.812.1000.990.1
The homeCommunityId is the sending and receiving device and organization.
Users can access to the XCPD Responding simulator by its web services, or by its GUI.
1. Responding Gateway simulator webservices
The web service responder of this simulator is http://gazelle.ihe.net/XCPDRESPSimulator-XCPDRESPSimulator/RespondingGatewayPortTypeImpl?wsdl.
For the TLS use, the web service of the simulator is https://22.214.171.124:1443/xcpd?wsdl.
Here is an example of a soap-ui project that use the unsecured webservice.
2. User Interface
The user can access to the responding gateway simulator Here .
This interface contains a page to describe the list of messages received by the simulator. For each transaction via the webservice of the simulator, we save the request, the response, the date of creation and the ip address of the initiating gateway.
On this table, for each message received, we can view it, we can validate it, we can view also the response and validate its content. We can also notice that for each couple of request/response, we have a permanent link, specified by a unique Id, the permanent link has this form : http://gazelle.ihe.net/XCPDRESPSimulator/transaction.seam?id=ID, exactly like it was done for XCPDINITSimulator.
On this permanent link, we specify the date of receiving the XCPD request, the IP of the sender and its country if we have this information, the type of the current trensaction, and the received message type. We can directly validate the received and the response messages from the current permanent link.
The GUI contains also a page on tools menu that lets to execute XCPD request directly within the use of the webservice, you have only to set the PRPAIN201305UV02 messages. The menu TestInstance which is common to all simulators contains list of TestInstance executed using gazelle with this simulator.