Special Instructions
In this test case, we will test the ITI-42 transaction initiated by a simulator acting as a XDS Document Repository.
As a pre-requisite : you have ran the CHXDS_DOC_REG_CONF
test. Your system needs to be properly integrated with Gazelle ADR Provider
simulator.
This test is executed using Gazelle Webservice Tester
as a
CH:XDS Document Registry actor. The tests played have been designed to
issue requests from different HealthCare Professionnals with different writing rights, for document with different confidentiality
level.
Important : TLS is mandatory to every request in the XDS profile, as a consequence every endpoint have to use HTTPS.
The Document Registry actor is expected to act as a X-Service
provider. This test will also be used to assess this role for ITI-42
transaction. 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 case of an
ITI-42
transaction. 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 case of an
ITI-42
transaction. In order to validate the conformity of your system in this
role, you'll need to follow the instructions
from this test case :
CHADR_FOR_CONSUMER
Description
- Before anything, configure your system to be able to test its role as X-Service Provider, X-Service User and ADR Consumer.
- Make sure to use the patient Nilesh (EPR-SPID :
761337610411265304^^^SPID&2.16.756.5.30.1.127.3.10.3&ISO)
- 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 menu "Run";
- Select the test project name EPR XDS Document Registry from the drop-down list;
- Select test suite [ITI-42] Registry Testing - nominal
cases by ticking the checkbox in front of its name;
- Enter the URL of your system under test endpoint (shall be a secured endpoint)
- 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
- Reproduce steps 3 to 8 but this time tick the box for [ITI-42] Registry Testing - invalid cases at step 5
- Reproduce steps 3 to 8 but this time tick the box for [ITI-42] Registry Testing - error cases at step 5
The conformance of the responses sent back by your system shall be
assessed. In Gazelle Webservice Tester,
validate the messages in EVSClient. To do so:
- Click on the play icon next to the response type;
- You have been redirected to EVSClient, select validator: XDS-CH in the EPR group 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";
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 "invalid case" and one "nominal case" needs to be checked)
The status of the transaction on GWT for the ITI-42 transaction must be "Passed".
The validations on EVS Client for the ITI-42 transaction must return "Passed".