The XDR Document Source Simulator has been developed to act as the actor Document Source for the profile XDR in tests.
This tool can participate as an initiator in many tests like Multi Document Submission thanks to its web service methods which provides to Gazelle a mean to communicate with it. A Web GUI is also available and enables the users to test their XDR responding register. From this GUI, connecthaton participants can retrieve the messages sent and received, documents uploaded during a test instance they have initiated. Note that this tool is able to send requests using TLS.
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 sends signed-body SOAP messages.
Installation of the XDR Document Source Simulator
You can download sources of the XDRSRCSimulator project from the INRIA Forge. This project required two additional modules: GSCommon-ejb and GSCommon-ui. Links to those sources are:
- Installation of XDRSRCSimulator
You have first to create a database on postgreSQL named xdr-src-simulator.
Command : createdb -e xdr-src-simulator -U gazelle -E UTF8 -W gazelle
Then you add the ear of XDRSRC Simulator to the deploy folder of jboss-5.1.0.GA.
You access to the User manual here.
Transactions and Messages supported
As an Document Source for XDR, the simulator supports the ITI-41 transaction.
Provide and register Document Source (ITI-41)
The following message types can be sent Provide and Register document source.
When you select the document type "eDispensation" or "eConsent", the simulator send two files the CDA file and the pdf (represents the copy of the CDA File).
When you select the document type "Pdf", the simulator send the Pdf file.
This simulator also supports the XUA (Cross Enterprise User Authentication) profile and can act as a X-Service User actor. You can't use the XUA if the XDS server recipient doesn't support XUA.
All simulators developed for interacting with Gazelle are built on the same model. The following diagram represents the different steps performed during a test instance.
|Input Contextual Informations|
|useXUA||null||indicates whether the simulator must turn
XUA mode on or off
|true or false|
|patientUniqueId||$XDSDocumentEntryPatientId||id of a patient known by the Responding
|normalized patient unique id|
|typeDocument||null||Type document generate to sent||eDispensation, eConsent, Pdf|
|Output Contextual Informations|
|XDR Recipient Soap Response|