ITI-41 : Provide and Register Set-b

Simulator Description

You can access To the simulator here.

The aim of this module is to simulate a document source actor on the transaction ITI-41, IHE domain.

This module allow vendors to submit documents, folders and associations between documents, folders and submissionSet.

To access to this simulator, you have to check the menu Simulator --> IHE --> ITI-41

menu access


System configuration



If you your system's configuration doeas not appear on the list of configuration to select, please go from the menu to SUT-Configurations --> Repositories-configurations. Then you will see all avalable configuration for testing. To add your configuration you have to click on the button "Create Registry Configuration". If you don't see this button, that's means that you are not logged in. Only logged users are allowed to add a system configuration to the XDStarClient tool.

To log in this tools, you have to use the link "cas login" on the menu. The login and password are the same one of gazelle test management EU-CAT. If you don't have a login and a password on EU-CAT, please create an acount.


After login, you will be able to add a repository configuration, on the page :



Water clicking on the button "Create Repository Configuration", you will be able to add your configuration to the tool :


Metadatas edition and configuration

  • Initialization of the request

When going from the menu to simulators --> IHE --> ITI-41, and after selecting your configuration, a GUI for editing metadata and for configuring your submission request appear : metadata

This GUI contains two sides : a tree to represent folders and documents, and a side to represent metadata for each component on the submissionSet.

The patient Id will be used for all submitted documents, folders and for the submissionSet. The sourceId is by default the one of the XDStarClient, and the uniqueId is automatically generated from the XDStarClient.

If a metadata is present by default on the table of metadatas, that's mean that this metadata is required. For example, for submissionset, the XDSSubmissionSet.contentTypeCode is required. The value that you can select for this metadata are the displayName of codes that will be used for bern CAT. These codes can be token from, or from the SVS simulator as REST request. OID that I have defined for each code are : contentTypeCode

classCode confidentialityCode formatCode healthcareFacilityTypeCode practiceSettingCode eventCodeList typeCode mimeType folderCodeList associationDocumentation


Additional metadata can be added to the submissionSet, by clicking on the button "add optional metadata on the bottom of the table of metadata. A list of Optional metadata will appear, and you can then select the one you want. Aditional metadata can be deleted from the table after being added :

additional param

  • Attach XDSFolder to submissionSet

To Attach an XDSFolder to an XDSSubmissionSet, you have to click on the icon "add xdsfolder to the submissionSet", on the tree of list attached documents and folder :


When clicking on add folder, a new XDSFolder appear on the tree. On the right side, we can see list of required metadata related to the XDSFolder :

xdsfolderFor each XDSFolder, we can attach an XDSDocument by clicking on the icon "add XDSDocument to the folder.

  • Attach XDS Document Entry

To attach an XDSDocumentEntry to an XDSFolder or to the submissionSet, you have to click on the icon add doc. You can see then that an entry on the tree is added, containing a link to the XDSDocument entry. On the left side, we see an upload component, to upload your document to submit : 
uploadAfter uploading your file, you will see that a list of metadata has been rendered.This list contain the XDS metadatas required. To add optional metadata, you have to click on the button "Add optional Metadata", and then select your metadata to add, and finally add your data on the table of metadata :
After creating our submissionSet, with folders and documents, we can then send the request using the button "execute". 
The request sent is MTOM/XOP request, to the specified configuration's URL.
The result of the communication is chown on a table on the bottom of the page : 
from the id com-lumn, you can access to a permanent link to the message (the request and the response). Action button are : view and validate.
The view button show the two messages : request and response. The second button is validate messages, it let you to validate the request and the response to a schema and to a model driven validation. The validation of metadata is done only for request ITI-41 : 

List of Provide and Register Set-b Messages

We can get all messages sent by this tool from the menu : Messages --> Provide and Register Set-b Messages :