Special Instructions
In this test case, we will perform an ITI-18 transaction initiated by the SUT to a simulator acting as a XDS registry.
ITI-18 is grouped with ITI-40 transaction, in this case the Document Consumer act as an X-Service User. This part is checked in the test case XUA_X-SERVICE-USER_ITI-40. You must create a test instance of this and paste the link in the step 5.
Important : TLS is mandatory to every request in the XDS profile, as a consequence every endpoint have to use HTTPS.
Description
- Using the datas provided in XDS.b_CONSUMER_CONF, perform ONE or more of the following transactions (the transactions supported by your system) :
- Retrieve the metadatas corresponding to all four documents using their document entry patient ID (FindDocument query)
- Retrieve the metadatas corresponding to Document 1 using its document unique ID (GetDocument query)
- Retrieve the metadatas corresponding to all four documents using their their submission set patient ID (FindSubmissionSet query)
- Retrieve the metadatas corresponding to BOTH Document 3 and 4 by a ObjectRef
Query, using their submission set unique ID (GetSubmissionSet&Content query)
Please note that :
For each ITI-18 transaction, an ADR request is performed by the registry simulator to an ADR simulator to retrieve an access decision according to the confidentiality level (normal, restricted and secret).
This decision is based on the policy set prealably defined by the patient in the Policy Repository.
The Document Registry shall disclose the document metadata according to the rights given to the HCP in response to ITI-18.
The datas given to you (assertion, PID, ...)are known from both the document registry and ADR simulator and should return the datas and documents requested.
The messages exchanged between your SUT and the simulator should have been recorded and be available in
Gazelle Webservice Tester. For each test step flagged with [TRANSACTION]:
- Access the messages in Gazelle Webservice Tester from the "Mock messages";
- Find out the message of interest, you can use the filters to ease your search (we also recommand to do it before you move to the next step);
- We want to verify the conformance of the request sent by your SUT, click on the play icon next to the request type;
- You have been redirected to EVSClient, select XDS-CH and click on the "Go" button;
- Once the page of the validator opens, select the appropriate entry in the drop-down list and click on "Validate";
- When the validation report shows up, a pop-up raises, click on "OK";
- Copy the permanent link of the message in the test step using the "add link" feature.
Evaluation
The validations on EVS Client must return passed.
The responses returned for each query must have a status "Success" and return the requested metadata according to the request type (LeafType/ObjectRef).