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_CONS_ITI-18

Test Summary

Id
13438
Keyword
CHXDS.b_DOC_CONS_ITI-18
Name
CHXDS.b_DOC_CONS_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
aeschlimann
Short Description
This test verifies the SUT's ability to request a document metadatas through an ITI-18 transaction against a simulated XDS document registry (with the support of XUA).
Last changed
1/26/24 7:28:05 AM

Test Description in English

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) :

  1. Retrieve the metadatas corresponding to all four documents using their document entry patient ID (FindDocument query)
  2. Retrieve the metadatas corresponding to Document 1 using its document unique ID (GetDocument query)
  3. Retrieve the metadatas corresponding to all four documents using their their submission set patient ID (FindSubmissionSet query)
  4. 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]:
    1. Access the messages in Gazelle Webservice Tester from the "Mock messages";
    2. 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);
    3. We want to verify the conformance of the request sent by your SUT, click on the play icon next to the request type;
    4. You have been redirected to EVSClient, select XDS-CH and click on the "Go" button;
    5. Once the page of the validator opens, select the appropriate entry in the drop-down list and click on "Validate";
    6. When the validation report shows up, a pop-up raises, click on "OK";
    7. 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).



Test Roles

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

Test Steps


Step Index
Initiator Role
Responder Role
Transaction
Secured
Message Type
Option
Description
Assertions
1EPR_XDS.b_DOC_CONSUMER-WITH_XUAEPR_XDS.b_DOC_CONSUMER-WITH_XUA-Required[INSTRUCTION] Configure your system to contact Identity Provider Simulator to authenticate user aandrews (HCP) and to contact the Assertion Provider Simulator to get an assertion for this user
5EPR_XDS.b_DOC_CONSUMER-WITH_XUAEPR_XDS.b_DOC_REGISTRY_SIMUITI-40Provide assertionRequired[TRANSACTION] Each ITI-18 transaction shall be supported by a ITI-40 Provider X-User Assertion transaction. That means that we want your system to demonstrate its capability to enclose the SAML token with the SOAP header of the ITI-18 request.
10EPR_XDS.b_DOC_CONSUMER-WITH_XUAEPR_XDS.b_DOC_REGISTRY_SIMUITI-18RegistryStoredQueryRequired[TRANSACTION][EVIDENCE] : The SUT sends ITI-18 request(s) to retrieve document metadata.
40EPR_XDS.b_DOC_CONSUMER-WITH_XUAEPR_XDS.b_DOC_CONSUMER-WITH_XUANoneRequired[EVIDENCE] Upload evidence that the ITI-18 response has been integrated within your system (for example, a screen shot of the list of retrieved document entries)
50EPR_XDS.b_DOC_CONSUMER-WITH_XUAEPR_XDS.b_DOC_CONSUMER-WITH_XUANoneRequired[EVIDENCE] : The SUT proves that a link to this test instance has been added the XUA_X-SERVICE-USER_ITI-40 test case.

Tool index

    Copyright IHE 2024
  • Gazelle 7.1.7
Back to top