Please use a compatible browser :Google Chrome or Mozilla Firefox
Page expired. Any change will be lost. Try to refresh the page.
Gazelle update scheduled, unsaved changes will be lost :
Your session will timeout :
Redeployed...
Logged out...
The server is restarting. Any change will be lost.
 

Test : CHXDS.b_DOC_REG_ITI-18

Test Summary

Id
13436
Keyword
CHXDS.b_DOC_REG_ITI-18
Name
CHXDS.b_DOC_REG_ITI-18
Version
1.2
Test Author
aeschlimann
Last modifier
vhofman
Status
ready
Type
master type
Is external tool ?
Is Orchestrable
is Validated ?
Peer Type
No Peer
Test validated by
aberge
Short Description
This test is to verify the SUT capacity to provide document metadatas through an ITI-18 transaction with a XDS document consumer.
Last changed
1/26/24 7:28:11 AM

Test Description in English

Special Instructions

In this test case, we will test an ITI-18 transaction initiated by a simulator acting as a XDS Document Consumer.

The metadata stored in your Document Registry will be initialized through an ITI-42 Register Document Set request sent by the project that will be executed on Gazelle Webservice Tester (GWT).


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. A test suite has been designed to issue requests from different HealthCare Professionnals with different access rights for document metadata 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-18 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-18 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-18 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:


  1. Access Gazelle Webservice Tester and log into the application
  2. Go to menu "Run";
  3. Select the test project name EPR XDS Document Registry from the drop-down list;
  4. Select test suite [ITI-42] Registry Initialization by ticking the checkbox in front of its name in order to add the metadata to your system
  5. Enter the URL of your system under test endpoint (shall be a secured endpoint)
  6. Click on "Run" button
  7. Wait for the script to complete its execution;
  8. Reproduce steps 3 to 7 but this time tick the box for [ITI-18] Query Testing - nominal cases at step 5
  9. When the script stops, copy the permanent link of the execution to the evidence test step in Gazelle Test Management
  10. Reproduce steps 3 to 7 but this time tick the box for [ITI-18] Query Testing - invalid cases at step 5
  11. When the script stops, copy the permanent link of the execution to the evidence test step in Gazelle Test Management
  12. Reproduce steps 3 to 7 but this time tick the box for [ITI-18] Query Testing - error cases at step 5
  13. When the script stops, copy the permanent link of the execution to the evidence test step in Gazelle Test Management


To validate your messages :

- The conformance of the ITI-18 responses sent back by your system shall be assessed. In Gazelle Webservice Tester, validate the message in EVSClient. To do so:

  1. Click on the play icon next to the response type;
  2. You have been redirected to EVSClient, select validator: XDS-CH in the EPR group and press the "Go" button;
  3. Once the page of the validator opens, select the appropriate entry in the drop-down list and click on "Validate";
  4. 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-18 transaction must be "Passed".

The validations on EVS Client for the ITI-18 transaction must return "Passed".



Test Roles

Keyword
# to realize
Card Min
Card Max
Optionality
URL
URL Doc
EPR_XDS.b_DOC_CONSUMER_SIMU
Integration profileActorOptionIs tested ?
Keyword
Keyword
Keyword
Keyword
IntegrationProfile XDS.b-Cross-Enterprise Document SharingActor DOC_CONSUMER-Document ConsumerNONEfalse
IntegrationProfile XUA-Cross Enterprise User AssertionActor X-SERV-USR-X-Service UserNONEfalse
111Required
CH_ADR_PROVIDER_SIMULATOR
Integration profileActorOptionIs tested ?
Keyword
Keyword
Keyword
Keyword
IntegrationProfile XUA-Cross Enterprise User AssertionActor X-SERV-PROV-X-Service ProviderNONEfalse
IntegrationProfile CH:ADR-Authorization Decision RequestActor AUTH_DECI_PROV-Authorization Decision ProviderNONEfalse
111Required
EPR_XDS.b_DOC_REGISTRY_SUT
Integration profileActorOptionIs tested ?
Keyword
Keyword
Keyword
Keyword
IntegrationProfile XDS.b-Cross-Enterprise Document SharingActor DOC_REGISTRY-Document RegistryNONEtrue
IntegrationProfile XUA-Cross Enterprise User AssertionActor X-SERV-PROV-X-Service ProviderNONEfalse
IntegrationProfile XUA-Cross Enterprise User AssertionActor X-SERV-USR-X-Service UserNONEfalse
IntegrationProfile CH:ADR-Authorization Decision RequestActor AUTH_DECI_CONS-Authorization Decision ConsumerNONEfalse
111Required

Test Steps


Step Index
Initiator Role
Responder Role
Transaction
Secured
Message Type
Option
Description
9EPR_XDS.b_DOC_REGISTRY_SUTEPR_XDS.b_DOC_REGISTRY_SUTNoneRequired[OTHER_ACTION] : The system is configurated to be able to register its audit messages.
10EPR_XDS.b_DOC_REGISTRY_SUTEPR_XDS.b_DOC_REGISTRY_SUTNoneRequired[OTHER_ACTION] The Document Registry is configured to communicate properly with the ADR provider simulator.
19EPR_XDS.b_DOC_CONSUMER_SIMUEPR_XDS.b_DOC_REGISTRY_SUTITI-40Provide X-User AssertionRequired[TRANSACTION] : Runing the project on GWT initiate an ITI-40 in parallel to the ITI-18 request from the Document Consumer simulator to the SUT
20EPR_XDS.b_DOC_CONSUMER_SIMUEPR_XDS.b_DOC_REGISTRY_SUTITI-18RegistryStoredQueryRequired[TRANSACTION] : Runing the project on GWT initiate an ITI-18 request from the Document Consumer simulator to the SUT
30EPR_XDS.b_DOC_REGISTRY_SUTCH_ADR_PROVIDER_SIMULATORITI-40Provide X-User AssertionRequired[TRANSACTION] : An ITI-40 is sent in parallel to the ADR Authorization Decision request from the SUT to the ADR Decision Provider
40EPR_XDS.b_DOC_REGISTRY_SUTCH_ADR_PROVIDER_SIMULATORAUTH_DECISION_REQUESTAuthorizationDecisionRequestRequired[TRANSACTION] : An ADR authorization decision request is sent to an ADR provider simulator to retrieve an access decision according to the confidentiality level (normal, restricted and secret) and policy set.
50EPR_XDS.b_DOC_REGISTRY_SUTEPR_XDS.b_DOC_REGISTRY_SUTNoneRequired[EVIDENCE] : The links to the validations of all messages on GWT is provided.
70EPR_XDS.b_DOC_REGISTRY_SUTEPR_XDS.b_DOC_REGISTRY_SUTNoneRequired[EVIDENCE] : The SUT proves that a link to this test instance has been added to both the XUA_X-SERVICE-PROV_ITI-40 test case and the XUA_X-SERVICE-USER_ITI-40 test case.
80EPR_XDS.b_DOC_REGISTRY_SUTEPR_XDS.b_DOC_REGISTRY_SUTNoneRequired[EVIDENCE] : The SUT proves that a link to each relevant EVS Client validations has been added to the CHADR_FOR_CONSUMER test case.

Tool index

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top