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 : CH:MHD_ITI-65_Append

Test Summary

Id
13557
Keyword
CH:MHD_ITI-65_Append
Name
CH:MHD_ITI-65_Append
Version
Bern2020
Test Author
r.hilary
Last modifier
NicolasBailliet
Status
ready
Type
connectathon
Is external tool ?
Is Orchestrable
is Validated ?
Peer Type
Peer To Peer
Short Description
ITI-65 test for the MHD Doc Source and Doc Recipient to test appending a document submitted into an XDS environment
Last changed
9/21/20 9:30:03 AM

Test Description in English

Special Instructions

An MHD Document Recipient that supports the XDS on FHIR option is required to be grouped with a Doc Source that supports the  Doc Replacement, Doc Addendum, Doc Transformation options so that the Doc Recipient can transfer these functionalities from an ITI-65 submission it receives from a MHD Doc Source into an XDS environment. 

Partners that are helpers for this test:

This is an optional test for an MHD Document Source, and the Source will only be able to perform the test if it supports appending a document using ITI-65.  (Unlike XDS, the MHD Document Source has no options to enable it to declare its support its ability to submit a document and then replace it.)

This is an optional test for XDS.b Document Registry and Repository systems.  If you perform this test, you are assisting an MHD Doc Recipient that is grouped with an XDS Doc Source who can submit to your Repository & Registry.

The challenge for the MHD Doc Recipient is to find an MHD Doc Source that supports one or more of replace, append, transform.

Choosing test partners:

In this test, the MHD Document Recipient is the system-under-test.  

When choosing partners for this test:

  • The MHD Document Source and Doc Recipient partners must be from different companies.
  • It is OK for the MHD Document Recipient and the XDS Doc Repository to be from the same company (ie the MHD Recipient is submitting to its own XDS Repository) .  Gazelle generally prohibits this, so you will need to seek help from a Connectathon Technical Manager in order to start this test.

Description

This test enables an MHD Document Source and Document Recipient to demonstrate support the ability to append a document previously submitted using ITI-65, and have the replacement occur in the XDS Registry/Repository that is 'behind' the Doc Recipient.

References:  ITI TF-1: 33.2.2, ITI TF- 2c: 3.65.4.1.2.3 and 3.65.4.1.3.1 (in the MHD TI Supplement).

Validate one ITI-65 request with EVSClient, the validator is available in EPR > CH EPR mHealth (R4) > MHD [ITI-65] Provide Document Bundle Request.

    Evaluation

    If the Doc Source and Recipient support one or more of:  replace, or append, or transform associations:

    Examine the test steps to find the instructions for Document Recipients to be able to demonstrate for the Connectathon Monitor the results of the replace, append, and/or transform.

    For the validation of the ITI-65 request :

    • The permanent link of the validation must be provided in the proofs
    • The Validation must be PASSED


    Test Roles

    Keyword
    # to realize
    Card Min
    Card Max
    Optionality
    URL
    URL Doc
    DOC_SOURCE-MHD
    Integration profileActorOptionIs tested ?
    Keyword
    Keyword
    Keyword
    Keyword
    IntegrationProfile MHD-Mobile access to Health DocumentsActor DOC_SOURCE-Document SourceNONEtrue
    IntegrationProfile CH:MHD-Swiss Mobile access to Health DocumentsActor DOC_SOURCE-Document SourceNONEtrue
    IntegrationProfile MHD-Mobile access to Health DocumentsActor DOC_SOURCE-Document SourceCOMPREHENSIVE_METADATAtrue
    IntegrationProfile CH:MHD-Swiss Mobile access to Health DocumentsActor DOC_SOURCE-Document SourceXDS_ON_FHIRtrue
    IntegrationProfile CH:MHD-Swiss Mobile access to Health DocumentsActor DOC_SOURCE-Document SourceCOMPREHENSIVE_METADATAtrue
    111Optional
    DOC_RECIPIENT-MHD
    Integration profileActorOptionIs tested ?
    Keyword
    Keyword
    Keyword
    Keyword
    IntegrationProfile XDS.b-Cross-Enterprise Document SharingActor DOC_SOURCE-Document SourceNONEfalse
    IntegrationProfile MHD-Mobile access to Health DocumentsActor DOC_RECIPIENT-Document RecipientNONEtrue
    IntegrationProfile CH:MHD-Swiss Mobile access to Health DocumentsActor DOC_RECIPIENT-Document RecipientNONEtrue
    IntegrationProfile CH:MHD-Swiss Mobile access to Health DocumentsActor DOC_RECIPIENT-Document RecipientCOMPREHENSIVE_METADATAtrue
    IntegrationProfile CH:MHD-Swiss Mobile access to Health DocumentsActor DOC_RECIPIENT-Document RecipientXDS_ON_FHIRtrue
    IntegrationProfile MHD-Mobile access to Health DocumentsActor DOC_RECIPIENT-Document RecipientCOMPREHENSIVE_METADATAtrue
    IntegrationProfile MHD-Mobile access to Health DocumentsActor DOC_RECIPIENT-Document RecipientXDS_ON_FHIRtrue
    111Required
    DOC_REGISTRY_XDS.b
    Integration profileActorOptionIs tested ?
    Keyword
    Keyword
    Keyword
    Keyword
    IntegrationProfile XDS.b-Cross-Enterprise Document SharingActor DOC_REGISTRY-Document RegistryNONEtrue
    111Optional
    DOC_REPOSITORY_XDS.b
    Integration profileActorOptionIs tested ?
    Keyword
    Keyword
    Keyword
    Keyword
    IntegrationProfile XDS.b-Cross-Enterprise Document SharingActor DOC_REPOSITORY-Document RepositoryNONEtrue
    111Optional

    Test Steps


    Step Index
    Initiator Role
    Responder Role
    Transaction
    Secured
    Message Type
    Option
    Description
    Assertions
    10DOC_SOURCE-MHDDOC_SOURCE-MHDInstructionsRequiredIf it's available, please use the Gazelle Proxy to capture messages between the Doc Source and Recipient (we expect that the messages w/ the XDS Reg/Rep will be TLS and not captured by the Proxy).
    20DOC_SOURCE-MHDDOC_RECIPIENT-MHDITI-65HTTP POSTRequiredFirst, the Document Source creates a new document for its patient and sends it to the Doc Recipient. If you are performing the Replace, Append, and Transform tests in parallel, this initial document should be a DIFFERENT document for each of these separate tests. The validation link of the request must be provide in this step.
    30DOC_RECIPIENT-MHDDOC_REPOSITORY_XDS.bITI-41Provide and Register Doc SetRequiredThe Doc Recipient uses its grouped XDS Doc Source to submit the NEW document to the XDS Doc Repository.
    40DOC_REPOSITORY_XDS.bDOC_REGISTRY_XDS.bITI-42Register Doc SetRequiredThe XDS Doc Repository registers the document metadata to the Doc Registry.
    50DOC_SOURCE-MHDDOC_RECIPIENT-MHDITI-65HTTP POSTRequiredAPPEND: Next, create and submit a replacement for the document submitted in Step 20.
    60DOC_RECIPIENT-MHDDOC_REPOSITORY_XDS.bITI-41Provide and Register Doc SetRequiredThe Doc Recipient uses its grouped XDS Doc Source to send the replacement to the XDS Doc Repository.
    70DOC_REPOSITORY_XDS.bDOC_REGISTRY_XDS.bITI-42Register Doc SetRequiredThe XDS Doc Repository registers the document replacement to the Doc Registry (APND association).
    80DOC_RECIPIENT-MHDDOC_RECIPIENT-MHDInstructionsRequiredThe Document Recipient demonstrates that the first document was successfully replaced in the XDS environment

    Tool index

      Copyright IHE 2024
    • Gazelle 7.1.7
    Back to top