Sample Exchange tests

Gazelle has a feature that allows participants in a testing session to share sample objects with other participants.

In Gazelle a "sample" is any object or message that an application creates and is used by another application. Typical samples include: 

  • DICOM objects
  • CDA documents
  • ...others...

Gazelle Test Management uses profiles and actors selected during System Registration to determine which systems are 'creators' of samples and which system are 'consumers' of samples

Creators upload a file containing their sample into Gazelle.  Consumers find samples uploaded by their Creator peers.  Consumers download the samples and are able to test them with their application.

Refer to these help pages for sample-sharing "how to" in gazelle: https://gazelle.ihe.net/content/sample-sharing

Test cases follow below...

APPC_Sample_Privacy_Consent_Docs

Overview

The APPC profile enables creating Patient Privacy Policy Consent documents of many, many variations.  For Connectathon testing, we have defined tests based on use cases documented in the APPC Profile.   

It will help APPC Content Creators & Content Consumers to be familiar with the APPC tests prior arriving at Connectathon.

(Note:  We currently have no tool for evaluating APPC documents)

 

Instructions 

Before Connectathon -- for APPC Content Creators:

(1) Read Connectathon test APPC_10_Read_This_First.  Find this on your main Connectathon page in gazelle (menu Connectathon-->Connectathon).  This test specifies policies, organizations, facilities, and providers that you will need to encode in the APPC Policy Consent documents that you will create for Connectathon testing.

(2) Read the APPC Connectathon tests for Case1, Case5, Case6, and "Other".   For Connectathon, you will be required to create 3 documents.  

  • You must perform any 2 of these 3 tests: Case1, Case5, Case6.

  • You must perform test APPC_Other_Use_Case.

(3) We highly encourage Content Creators to create these documents prior to arriving at Connectathon.

  • Create the APPC documents according to the instructions in the test cases.
  • Upload your documents into the samples area of gazelle under menu Connectathon-->List of samples.  On the 'Samples to share' tab, find the entry for APPC.
  • Providing your APPC policy consent document early enables Content Consumers to test with your document in advance.

 

Before Connectathon -- for APPC Content Consumers:

(1) Read Connectathon test APPC_10_Read_This_First.  Find this on your main Connectathon page in gazelle (menu Connectathon-->Connectathon).  This test specifies policies, organizations, facilities, and providers that Content Creators will use in the policy consent documents they create

(2) Above, we asked Content Creators to provide their sample APPC documents in advance of Connectathon, so...

(3) Check for sample APPC documents provided by Content Creators:

  • In gazelle, look under menu Connectathon-->List of samples.  
  • Check the 'Samples available for rendering' tab under the 'APPC' entry.

 

Evaluation

Finally, for both Creators & Consumers

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor".  This is a signal to the Technical Manager that you have completed the task associated with your actor..

 

DICOM_Object_Sample_Exchange

Overview

In this “test”, Creators of DICOM objects submit a sample data set that will be reviewed by other Consumer test partners. The goal of this test is to prepare Consumer actors (Image Manager, Image Display) so they are not surprised during Connectathon events.

In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the usual pre-Connectathon test deadlines

Sample  Creator(s) Consumer(s)

DICOM image(s)

DICOM SR(s)

Acquisition Modality in various profiles

Evidence Creator or Modality in various profiles

Image Mgr, Image Display, Dose Reporter or Consumer

 

Instructions for DICOM Image or SR Creators;

  1. Determine a representative set of image(s), or a Structured Report, that would help other actors understand your content. We do not expect you to generate images for every combination of parameters; pick one set of parameters. However, if your system supports more than one SOP class, or can use more than one transfer syntax, we expect you to upload representative samples for each.  Create file(s) of these objects.
  2. Assuming you have this ability, render the images or SR that you produced as a reference. The goal is for an Image Display actor to examine your rendering and compare to what their software produces. Perform a screen capture and/or save as JPEG or other reasonable format.
  3. Upload sample objects and the screen capture snapshot into Gazelle under Connectathon-->Connectathon--> List of Samples. On the Samples to share tab, upload your sample image(s) under the DICOM_OBJECTS entry.  On the "summary" tab for the sample, you will see a list of Attributes.  Choose the attribute that best describes your sample (e.g. "NMI" for a Nuc Med image, "SWF.b" for a general sample for that profile, etc)  Refer to these help pages for details on managing samples in Gazelle.
  4. Some image sets are too large to upload into gazelle. If you encounter this, please contact the Connectathon Technical Project Manager to for instructions on alternatives.
  5. Create a short txt file indicating you have completed the upload step. Upload '''that''' txt file into gazelle as the result file for this pre-Connectathon test.
  6. As Image Display actors render your data, you may receive a request for interpretation or directives from the Connectathon Technical Project Manager to repair attributes. This may prove to be an iterative process. You may submit more than one set.
  7. There is no specific evaluation for this test.  Feedback comes as your partner Image Display and Image Manager partners test with your images in their lab.

Instructions for DICOM Consumers;

  1. Find sample images uploaded by other vendors in Gazelle under Connectathon-->Connectathon -> List of samples.    On the Samples available for rendering tab you will find DICOM_OBJECTS submitted by other vendors.  This page will evolve as vendors add samples, so be patient. 
  2. Find the samples that are relevant for your storage or display application.
  3. Retrieve the DICOM or zip files created by the other vendors.  Refer to these help pages for details on this task in Gazelle.
  4. Examine/import/render them so that you are confident your software understands the content.
  5. When you are finished, create a .txt or other file that lists the samples you tested with, and a brief comment on your result (eg "ok", or "could not render"). Upload that txt file into gazelle as the result file for this pre-Connectathon test.
  6. If you find issues with the images, send an email to the Connectathon Manager.
  7. The evaluation of this test is performed by examining the text you provided to make sure you made a good faith effort to review the sample images. If you find problems with some samples, we will give your feedback to the Modality test partner.
  8. The goal is no surprises.

Finally, for both Creators & Consumers

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor".  This is a signal to the Technical Manager that you have completed this task.

 

EYECARE_Sample_Exchange

Overview

Prior to the Connectathon, it is very beneficial for participants to have access to sample DICOM objects, HL7 messages,CDA documents, etc produced by their test partners' applications.  We use Gazelle as an intermediary to exchange samples.  In Gazelle, a "sample" is any object or message that an application creates and is used by another application.

This table lists samples from IHE Eye Care domain profiles U-EYECARE, GEE, and EC-Summary.  Beneath the table are instructions for Creators to upload samples into Gazelle prior to the Connectathon, and instructions for Consumers who want to download samples to test in advance of Connectathon.  Note that due to the size of some DICOM objects, we have separate instructions for exchange of DICOM samples.

The deadline for sharing samples is typically 2-3 weeks prior to the Connectathon.  The due date will be announced by the Technical Project Manager.

Sample  Type Creator(s) Comsumer(s)
EYECARE-15 Patient Registration ADT^A04 Pat Registration Src Pat Registration Cons, DSS/OF in Model I & III
EYECARE-16 Appt Scheduling SIU^S* Appt Scheduler Appt Consumer
EYECARE-17 Charge Posting DFT^P03 DSS/OF w/ Chg Posting option Chg Processor
EYECARE-19 Pat Demog Update ADT^A08  DSS/OF in Model I & III Img Mgr in Model I & III
EYECARE-20 Merge Pat IDs ADT^A40 Pat Registration Src w/ Merging option Pat Reg Cons, DSS/OF, Img Mrg w/ Merging option
EYECARE-21 Procedure Scheduling OMG^O19 DSS/OF in Model I & III   Img Mgr in Model I & III 
EYECARE-22 Procedure Status Upd OMG^O19 Img Mgr w/ Proc Status Upd HL7 option DSS/OF w/ Proc Status Upd HL7 option
EYECARE-23 Refractive Meas (no PatID) XML Refractive Measurement Source (RMS) Refractive Measurement Consumer (RMC)
EYECARE-24 Refractive Meas (valid PatID) XML RMSI, RMS w/ Pat Device List option RMC w/ Pat Device List option 
GEE Document CDA Content Creator Content Consumer
EC Summary Document CDA Content Creator Content Consumer

 

Instructions for Creators

  1. Capture the sample content as produced by your system.  Create a file containing the contents of that message.
  2. In Gazelle,select menu Connectathon-->Connectathon-->List of samples
  3. On the "systems" dropdown list, select your system name
  4. On the "Samples to share" tab, find the entry for your sample, matching Column 1 above
  5. Upload the file containing your sample.  You may refer to this help page if you have never used Gazelle to upload samples

Instructions for Consumers

  1. In Gazelle,select menu Connectathon-->Connectathon-->List of samples
  2. On the "systems" dropdown list, select your system name
  3. On the "Samples available for rendering" tab, you will see an entry for each sample type for which you are a Consumer.
  4. The contents of this tab changes over time, as Creators upload samples.  Entries with a "+" sign contain samples from Creators. 
  5. Download available samples.  You may refer to this help page if you have never downloaded samples from Gazelle.

Finally, for both Creators & Consumers

  1. In Gazelle, select menu Connectathon-->Pre-Connectathon testing 
  2. Find the entry for this test instance, and change the status to "Verified by Vendor".  This is a signal to the Technical Manager that you have completed this task.

 

FHIR_CapabilityStatement

Test Summary

This test applies to test systems that have implemented one or more IHE Profiles based on HL7 ®© FHIR ®©.   The test applies to both Servers and Clients.

You will create a FHIR CapabilityStatement Resource that represents the FHIR capabilities in your system/product.  You will upload it as a sample into Gazelle Test Management.  Finally, you will use Gazelle EVSClient to validate your CapabilityStatement Resource.

ReferenceIHE (ITI) Appendix Z on HL7 FHIR, Section Z.3: "HL7 FHIR allows service implementers to publish a CapabilityStatement Resource describing the resources, transport, formats, and operations that can be performed on a series of resources for the service instance. The CapabilityStatement Resource is described in FHIR:  http://hl7.org/fhir/CapabilityStatement.html

Instructions

  • Create a CapabilityStatement Resource that represents the FHIR capabilities in your system/product.  
  • Upload the XML file for the CapabilityStatement Resource into Gazelle Test Management under Connectathon-->Connectathon--> List of Samples. On the Samples to share tab, upload your XML under the FHIR CapabilityStatement entry.   (Refer to these help pages for details on this task in Gazelle).  Though most will have one CapabilityStatment, you may upload more than one file.
  • After you upload the file, in the Actions column, find the green icon to validate the sample using EVSClient.
  • Within EVSClient, you will find a FHIR ®© menu to use for performing Resource validation.

Evaluation

  • Validate your CapabilityStatement Resource for FHIR R4.  The validation result should show "Passed".
  • The EVSClient creates a Permanent link to your results under FHIR®© -->Validation Logs
  • To record your results for this pre-Connectathon test in Gazelle Management, paste the Permanent link(s) to your EVSClient validation results into the comment field (ie. instead of uploading a log file).  
  • Change the status of the pre-Connectathon test to Verified by vendor

 NOTE:  You will be asked to provide this CapabilityStatement during Connectathon, so it is to your benefit to do this in advance of Connectathon.

XDS-I_Manifests_for_Two_Studies

Overview

Starting at the EU2018 Connectathon, we added a new no-peer Connectathon test that asks XDS-I Imaging Document Source systems to create manifests for two studies provided by Connectathon technical managers. This differs from earlier years where Imaging Document Source systems created manifests for studies they provide (you will still be able to do that for peer-to-peer Connectathon tests).

This pre-Connectathon test gives you the opportunity to prepare those manifests before you arrive at Connectathon, to save you some time in the beginning of the week. 

Instructions for XDS-I.b Imaging Document Source:

The Connectathon test you are preparing for contains all of the instructions, so we will not duplicate them here.

Instead...

  1. Go to Gazelle Test Management for your Connectathon.
    For EU: https://gazelle.ihe.net/EU-CAT/home.seam or for NA: http://ihe.wustl.edu/gazelle-na/home.seam
  2. On your Main Connectathon Page, filter the list of tests, and find the no-peer Connectathon test "XDS-I.b_Manifest_and_Metadata".
  3. Read the "Test Description" section to get an overview of the test.
  4. Perform test steps 10 through 40.  This will enable you to download the two DICOM studies (a DX study and a CT study) onto your Imaging Document Source, create two associated XDS-I manifests, and also upload the manifest for the CT study into the samples area of Gazelle.
  5. We will not evaluate your manifest prior to Connectathon.  You will also have to wait until Connectaton week to submit your manifests to the NIST XDS Toolkit so that your metadata can be checked.

We hope that reading the new Connectathon test, loading the two studies, and preparing the manifests in advance of the Connectathon, is helpful for you.