KOS_Sample_Exchange

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..

  • The first KOS should reference a single image
  • The second KOS should reference 2-3 images
  • The title of the Key Object Note should be one of the titles drawn from DICOM CID 7010,
  • You will upload sample objects into Gazelle Test Management under Testing-->Sample exchange in the "KOS" entry.
  • Under "Actions", use the green triangle icon the validate your DICOM object(s) using Gazelle EVSClient.  We expect a validation result with no errors.
  • The creator of the KOS objects should also store all of the images of the study to which each KOS pertains.
  • There are extra worthless brownie points available for those who create Key Object Notes that refer to individual frames in a multi-frame image, or that reference GSPS objects associated with an image object, or that reference objects outside the current study.
  • 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/GSPS objects and compare 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.
  • 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 pre-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 DICOM Image and GSPS Consumers:

  1. Find sample images & GSPS objects uploaded by other vendors in Gazelle Test Management under Testing-> Sample exchange.    On the Samples available for rendering tab under the KOS entry, you willl find samples and screen captures submitted by other vendors.  This page will evolve as vendors add samples, so be patient. 
  2. Retrieve the DICOM or zip files created by the other vendors.  Refer to these help pages for details on this task in Gazelle.
  3. Examine/import/render them so that you are confident your software understands the content.
  4. 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 Test Management as the result file for this preparatory test.
  5. If you find issues with the images, send an email to the Connectathon Technical Manager.
  6. 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.
  7. The goal is no surprises.

Finally, for both Creators & Consumers

  1. 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.