Special Instructions
In this case we will test the Restricted Update Document [ITI-92] transaction, with a simulator acting as the RMU Update Initiator actor. Your system will receive multiple documents that will be then updated.
As a pre-requisite : Your system needs to be properly integrated with Gazelle ADR Provider
simulator. To do so use :
The Document Registry actor is expected to act as a X-Service
provider. This test will also be used to assess this role.
In order to do so, you'll need to follow the instructions
from this test case :
XUA_X-SERVICE-PROV_ITI-40
Moreover, the Document Registry actor is expected to act as a
X-Service user when sending an AuthorizationDecision query to an ADR
Provider.
This test will also be used to assess this role. In order to do so, you'll need to follow the instructions
from this test case :
XUA_X-SERVICE-USER_ITI-40
In
addition, the Document Registry actor is also expected to act as an
AuthorizationDecision Consumer. This test will also be used to assess
this role.
In order to validate the conformity of your system in this
role, you'll need to follow the instructions
from this test case :
You'll also need to configure your RMU Update Responder actor to work with the
following patient :
Name : Nilesh WITTWER-CHRISTEN
nameID : 761337610411265304
In order to test your system capacity to accept updates for deprecated document, you will also need to be able to receive ITI-57 transactions (XDS-MU).
Description
Before anything, configure your system to be able to test its role as X-Service Provider, X-Service User and ADR Consumer.
In this test, we will execute three DocumentEntry Metadata update. In
particular, we will update the parameter ConfidentialityCode of both an Approved and Deprecated document entry. In addition, we will also issue a deletion request for a deprecated document.
The test suite will first initialize documents in your XDS Document Repository, verify that the upload was successful (both the ITI-41 and ITI-42 transactions).
Then it might send an ITI-57 to deprecate this document entry (depending on the test suite), and afterward, an ITI-92 request with a modification to the document metadata will be sent to your system.
Finally, an ITI-18 request for the updated version of the document metadata will be send to the SUT. In the case of the deletion request, your system is expect to not return any metadata.
The requests will be sent to your SUT from Gazelle Webservice Tester. To execute this test:
- Access Gazelle Webservice Tester and log into the application;
- Go to the menu "Run";
- Select the test project name EPR Restricted Metadata Update from the drop-down list;
- Select test suite RMU - Document Initialization & Update by ticking the checkbox in front of its name;
- Fill-in the informations corresponding to your system
- Click on "Run" button
- Wait for the script to complete its execution;
- When the script stops, copy the permanent link of the execution to the test step in Gazelle Test Management
- Execute steps 2 to 8 using the test suite RMU - Deprecated Document update and deletion this time
The
conformance of the responses sent back by your system shall be
assessed. In Gazelle Webservice Tester,
validate the ITI-92 responses in EVSClient. To do so:
- Go to the "Resume" tab then search for below transactions :
- RMU - Document Initialization & Update / Initialization & Update / ITI-92 Restricted Metadata Update
- RMU - Deprecated Document update and deletion / Deprecated document deletion / ITI-92 - Restricted Metadata Update - Deletion Request
- Click on "Validation response"
- You have been redirected to EVSClient, select validator XDS-CH and
the validator CH XDS.b ITI-92 Restricted Update Document Set - response and hit 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 for returning the validation report to GWT, click on "OK"
Evaluation
The monitor will check that you copied the link to this test instance to the corresponding test step of the test case XUA_X-SERVICE-PROV_ITI-40 AND XUA_X-SERVICE-USER_ITI-40.
The
monitor will also check that you copied the link to the EVS Client
validations for your ADR Authorization Decision queries to the
corresponding test step of the test case CHADR_FOR_CONSUMER (one case is enough for the check)
The status of the transactions on GWT must be "Passed".
The validations on EVS Client must return "Passed".