Gazelle Test Management has a feature that allows participants in a testing session to share sample objects with other participants.
In Gazelle Test Management, a "sample" is any object or message that an application creates and is used by another application. Typical samples include:
Gazelle Test Management uses profiles and actors selected during System Registration to determine which systems are 'creators' of samples and which systems are 'consumers' of samples
Creators upload a file containing their sample into Gazelle Test Management (Testing-->Sample exchange). Consumers find samples uploaded by their Creator peers. Consumers download the samples and are able to test them with their application.
Test cases follow below...
Overview
The AIR Evidence Creator will submit samples AI Results (SR objects) produced by its system and the associated DICOM images. The goal of this test is to prepare Consumer actors so they are not surprised during Connectathon.
In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the usual preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
DICOM SR(s) DICOM Segmentation, Parametric Map or KOS IOD(s) DICOM image(s) |
AIR Evidence Creator |
AIR Image Mgr, Image Display, Imaging Doc Consumer |
Instructions for Evidence Creators:
FIRST, prepare the sample(s)-->
Evidence Creator system must provide a sample that includes both DIOM SRs and image objects. Although it is likely that an Acquisition Modality (ie not Evidence Creator) will be the source of images for which AIR SR objects are created, we ask the Evidence Creator to submit them together as a 'sample'
The AI result SR objects(s) Evidence Creator should be representative of what the system would created during expected clinical use when an AI algorithm is run.
3. Validate the SR using EVSClient (green arrow in on the sample page). You must select the DICOM validator from Pixelmed. During the Connectathon, we will be looking for a validation result with no errors (warnings are OK).
4. Evidence Creator of the AI result SR object should also upload the images of the study to which the SR pertains.
5. If you have this ability, render the objects you produced as a reference. The goal during Connectathon is for an Image Display partner to examine your rendered images and SR objects and compare that to what their software produces. Perform a screen capture and/or save as JPEG or other reasonable format. Upload the screenshot onto the sample page in Gazelle Test Management.
Repeat Steps 1 - 5 for each AI algorithm and resulting AI sample.
Finally, create a short txt file indicating you have completed the upload step. Upload '''that''' txt file into Gazelle Test Management as the result file for this preparatory test.
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 Consumers:
Finally, for both Creators & Consumers
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)
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.
Before Connectathon -- for APPC Content Consumers:
(1) Read Connectathon test APPC_10_Read_This_First. Find this on your Test Execution page in Gazelle Test Management. 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:
Finally, for both Creators & Consumers:
This is a family of tests. Each of the tests (40180-01, 02, 03, ...) is for a specific document type, but the instructions are the same. We have different test numbers to let us keep track of the document type in Gazelle Tests Management.
Please refer to the list of document types in the table below.
The goal is 'No Surprises' at the Connectathon
Creators....please upload your samples two weeks before the normal due date for Preparatory tests. This is to allow other participants to review your result.
1. Create a document according to the test number (see table below). Name the file using this convention:
2. Upload the document into Gazelle Test Management under menu Testing-->Sample exchange.
3. In Gazelle Test Management for this test instance, upload a brief note (txt file) indicating this task is done and upload the file as the results for this test.
4. Finally, change the status of the test to "Verified by Vendor". This is a signal to the Technical Manager that you have completed the task associated with your actor.
5. Repeat these instructions for each document type you can create.
1. Find samples uploaded by other vendors for test 40180-xx in Gazelle Test Management under menu Testing -> Sample exchange on the Samples available for rendering tab. (When a Content Creator or Form Filler has uploaded a sample, you will see a small triangle in front of their system name.) This page will evolve as vendors add samples, so be patient. The deadline for Creators to submit samples is typically two weeks prior to the Preparatory test deadline. Technical Managers of each testing event publish the deadline.
2. Retrieve the documents created by the other vendors. "Process/render" them so that you are confident your software understands the content.
For Content Consumer actors, "Process/render" means to apply one or more of the options:
For Form Manager actors, "Process/render" means to take the prepop data and make it part of the form.
3. You will perform one or more of those actions on the sample documents and then provide evidence that you have performed this action. That evidence will be some screen capture or database dump from your system. Upload that evidence into Gazelle Test Management as the results for this Preparatory test.
Document Types for this sample-sharing test:
|
Preparatory |
IHE Profile Document type |
| 40180-01 | XDS-MS Referral Document |
| 40180-02 | XDS-MS Discharge Summary |
| 40180-03 | ED Referral |
| 40180-04 | XPHR Extract |
| 40180-05 | XPHR Update |
| 40180-06 | Antepartum History and Physical |
| 40180-07 | Antepartum Summary |
| 40180-08 | Antepartum Laboratory Report |
| 40180-09 | Antepartum Education |
| 40180-10 | Triage Note |
| 40180-11 | ED Nursing Note |
| 40180-12 | Composite Triage and ED Nursing Note |
| 40180-13 | ED Phyisician Note |
| 40180-14 | Immunization Content |
| 40180-15 | Sharing Lab Report (XD-LAB) |
| 40180-16 | ITI - Basic Patient Privacy Consent acknowledgement (not CDA, but BPPC) |
| 40180-17 | ITI - XDS-SD Scanned Document |
| 40180-18 | Labor/Delivery Admission History and Physical |
| 40180-19 | Labor/Delivery Summary |
| 40180-20 | Maternal Discharge Summary |
| 40180-21 | EMS Transfer of Care |
| 40180-22 | Patient Plan of Care (PPOC) |
| 40180-26 | eNursing Summary |
| 40180-27 | Newborn Discharge Summary |
| 40180-28 | Postpartum Visit Summary |
| 40180-29 | EMS Transport Summary |
| 40180-30 | Interfacility Transport Summary |
| 40180-31 | RECON |
| 40180-32 | Patient Care Plan (PtCP) |
| 40180-33 | RIPT |
| 40180-34 | International Patient Summary (IPS) - CDA, CDA Complete, and CDA Occ Data Health Options |
| 40180-100 | QRPH - CRD: Clinical Research Document |
| 40180-101 | QRPH - DSC: Drug Safety Content |
| 40180-106 | QRPH - PRPH-Ca: Physician Reporting to a Public Health Repository-Cancer Registry |
| 40180-108 | QRPH - QRPH - BFDR-E - Birth and Fetal Death Reporting - Enhanced |
| 40180-109 | QRPH - EHDI - HPoC: UV Realm: Hearing Plan of Care UV Realm |
| 40180-110 | QRPH - EHDI - HPoC: US Realm: Hearing Plan of Care US Realm |
| 40180-111 | QRPH - HW: Healthy Weight |
| 40180-113 | QRPH - QME-EH: Quality Measure Execution - Early Hearing |
| 40180-114 | QRPH - VRDR: Vital Records Death Reporting |
| 40180-200 | CARD - CIRC: Cardilogy Imaging Report Content |
| 40180-201 | CARD - CRC: Cath Report Content |
| 40180-202 | CARD - RCS-C: Registry Content Submission - Cardiology |
| 40180-203 | CARD - EPRC-I/E: Electrophysiology Report Content - Implant/Explant |
| 40180-300 | EYECARE - GEE: General Eye Evaluation Content |
| 40180-301 | EYECARE - EC-Summary: Eye Care Summary Record Content |
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 Preparatory test deadline.
| 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 |
Some image sets are too large to upload, and Gazelle reports an error. If you encounter this, please contact the Connectathon Technical Project Manager for instructions on alternatives.
Create a short txt file indicating you have completed the upload step. Upload '''that''' txt file into Gazelle Test Management as the result file for this preparatory test.
You may submit more than one set.
Creators and Consumers: In Gazelle Test Management, 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.
There is no specific evaluation for this test. Feedback comes as Consumers partners test with DICOM objects in their lab. The goal is no surprises.
In this “test”, Creators of FHIR Resoruce submit a sample data set that will be reviewed by other Consumer test partners. The goal of this test is to prepare Consumer actors 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 Preparatory test deadline.
| Sample | Creator(s) | Consumer(s) |
| FHIR Resource (json or xml format |
Content Creator | Content Consumer |
These are generic instructions for uploading samples into Gazelle Test Management. Individual IHE Profiles and FHIR IGs contain definitions and constraints for specific content types.
Create a short txt file indicating you have completed the upload step. Upload '''that''' txt file into Gazelle Test Management as the result file for this preparatory test.
You may submit more than one set.
Creators and Consumers: In Gazelle Test Management, 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.
There is no specific evaluation for this test. Feedback comes as Consumers partners test with DICOM objects in their lab. The goal is no surprises.
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 Test Management, 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 |
Overview
The goal of this “test” is to provide samples for other vendors to display. You should submit a “representative sample” of the data produced by your system.
GSPS objects are supported in the Consistent Presentation of Images profile. CPI Evidence Creator actors create GSPS objects (requirement) and may optionally produce images. Likewise, CPI Acquisition Modalities actors create images and GSPS objects.
Each system (Modality or Evidence Creator) should submit samples of the Image and/or GSPS objects. The goal of this test is to prepare Consumer actors (Image Manager, Image Display) so they are not surprised during Connectathon.
In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the Preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
DICOM image(s) DICOM GSPS(s) |
CPI Acquisition Modality and Evidence Creator |
Image Mgr, Image Display |
Instructions for DICOM Image and GSPS Creators:
FIRST, prepare the samples-->
Both Modality and Evidence Creator systems must provide samples that include both images and GSPS objects. Acquisition Modalities will be the source of images for which GSPS objects will be created.
The GSPS objects and images created by the Modality or Evidence Creator should be of the same genre as those normally generated by the Evidence Creator during expected clinical use.
To insure adequate testing of capabilities, the set of GSPS objects you create should include at least 15 elements drawn from the following GSPS capabilities:
SECOND, upload your samples -->
Instructions for DICOM Image and GSPS Consumers:
Finally, for both Creators & Consumers
The purpose of this exchange of IMR samples is to enable testing prior to Connectathon week and reduce 'surprises'.
In this “test”, Creators of IMR reports 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 Preparatory test deadline. (During Connectathon, your Report Creator will also be required to create a report based on a study provided by the Connectathon Techincal Manager.)
| Sample | Creator(s) | Consumer(s) |
|
IMR Bundle |
Report Creator |
Report Reader Rendered Report Reader |
|
DICOM study |
The Report Creator must also provide the DICOM study associated with its report(s). The study will include images, and may optionally contain Structured Report (SR), different types of Presentation States (PR), or Segmentation objects. Providing this sample ensures that the Report Creator has access to images (that the Image Manager will store) that are compatible with its reporting application. |
Image Manager |
Some image sets are too large to upload, and Gazelle reports an error. If you encounter this, please contact the Connectathon Technical Project Manager for instructions on alternatives.
Creators and Consumers: In Gazelle Test Management, 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.
There is no specific evaluation for this test. Feedback comes as your partner Consumers partners test with the report & images in their lab. The goal is no surprises.
In this “test”, the Image Display in the Integrated Reporting Application (IRA) profile submits a sample DICOM study that will be the subject of reporting using the interactions defined in IRA. The goal of this test is to enable Consumer actors (e.g., Report Creator, Evidence Creator) to have access to these studies prior to Connectathon events.
In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the usual Preparatory test deadline.
| Sample | Creator(s) | Consumer(s) |
|
DICOM study |
The Image Display must provide at least one DICOM study that it will have availabile for reporting using the IRA profile. The study will include images, and may optionally contain Structured Report (SR), different types of Presentation States (PR), or Segmentation objects. Providing this sample ensures that the Consumer systems have access to studies on the Image Display that are compatible with its reporting-related application. |
Content Creator (grouped w/ Report Creator, Evidence Creator...) |
Some image sets are too large to upload, and Gazelle reports an error. If you encounter this, please contact the Connectathon Technical Project Manager for instructions on alternatives.
Creators and Consumers: In Gazelle Test Management, 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.
There is no specific evaluation for this test. The goal is no surprises.
Overview
The goal of this test is to provide samples for other vendors to display. The KOS creator will submit a “representative sample” of the data produced by its system.
KOS objects are supported in the Key Image Notes profile. CPI Evidence Creator actors create GSPS objects (requirement) and may optionally produce images. Likewise, CPI Acquisition Modalities actors create images and GSPS objects.
Each system (Modality or Evidence Creator) should submit samples of the Images and the KOS objects containing references to some images. The goal of this test is to prepare Consumer actors (Image Manager, Image Display) so they are not surprised during Connectathon.
In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the usual preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
DICOM image(s) DICOM KOS(s) |
KIN Acquisition Modality and Evidence Creator |
Image Mgr, Image Display |
Instructions for DICOM Image and KOS Creators:
FIRST, prepare the samples-->
Both Modality and Evidence Creator systems must provide samples that include both images and KOS objects. Acquisition Modalities will be the source of images for which KOS objects will be created.
The KOS objects and images created by the Modality or Evidence Creator should be representative of what the system would created during expected clinical use.
Note: In order to identify the creator of the note, it would be most beneficial if the Patient Name chosen reflected the company/product of the system creating the Key Object Note. This is relatively easy for Modalities as they create the original images. This may take more imagination by Evidence Creators as they typically do not create the original images. By having the company/product name in the Patient Name field, other tests will be much easier to perform because your test partners will easily identify your images/KOS..
Instructions for DICOM Image and GSPS Consumers:
Finally, for both Creators & Consumers
The goal of this “test” is to provide MRRT Report Templates that are 'consumed' by other systems.
In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the usual Preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
MRRT Report Template |
Report Template Creator |
Report Template Manager, Report Creator |
FIRST, prepare the samples-->
We expect the Report Template Creator to create and provide a “representative sample” of the templates that represents the template-creating capabilities of your application AND that incorporate as many of the template structures defined in the MRRT Profile as possible. he better the samples you provide, the better interoperability testing we will have.
Using your Report Template Creator application, create a template using this guidance:
SECOND, upload your samples -->
In the REM profile, Dose Information Reporter systems are required to have the capabililty to de-identify Dose SR objects. See RAD TF-2: 4.63.4.1.2.1 .
In this test, Dose Information Reporters perform de-identification and then submits it as a sample into Gazelle Test Management
In order to facilitate this testing, please submit your samples 2-3 weeks before the usual Preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
Radiation Dose SR (De-identified) |
REM Dose Information Reporter |
Dose Registry |
FIRST, prepare the samples-->
SECOND, upload your samples -->
For the Connectathon, meaningful interoperability testing for the REM profile between Modalities and Dose Info Consumers, Reporters and Registers will rely largely on the quality of the data sets supplied by the Acquisition Modality vendors. The goal of this “test” is to provide REM-compliant Radiation Dose SRs that are 'consumed' by other systems.
In order to facilitate this testing, Creators....please submit your samples 2-3 weeks before the usual Preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
Radiation Dose SR |
REM Acquisition Modality |
Dose Information Consumer, Dose Information Reporter, Dose Registry |
FIRST, prepare the samples-->
SECOND, upload your samples -->
We have been testing REM for several years, and we've collected sample Dose SRs from Modalities that have tested REM at various connectathons. To expand the number of samples you have to test with, we point you to this collection of SRs.
There is no log to upload for this test.
For the Connectathon, meaningful interoperability testing for the REM-NM profile between Radiolpharmceutical Activity Suppliers (RAS) and Modalities as creators of DICOM objects, and Image Managers, Dose Info Consumers, Reporters, Registers as consumers of those objects, will rely largely on the quality of the data sets supplied by the RAS and Modality vendors. In this “test”, you create a sample data set that will be reviewed by other participants. The goal of this test is to prepare other actors (Image Manager, Dose Info Consumer, Dose Info Reporter, Dose Register) 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 Preparatory test deadlines.
| Sample | Creator(s) | Consumer(s) |
|
Radiopharmaceutical Radiation Dose Structured Reports (RRDSR) Images that reference RRDSRs |
REM-NM RAS REM-NM Acquisition Modality |
Dose Information Consumer, Dose Information Reporter, Dose Registry, Image Manager |
FIRST, prepare the samples-->
SECOND, upload your samples -->