IMR_Sample_Report_and_Study

Overview

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

Report Repository

DICOM study

The Report Creator must also provide the DICOM study(ies) associated with its report(s).  Each study will include images, and may optionally contain Stuctured 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

Instructions for Report Creators

    1. Identify a DICOM imaging study(ies) to report on.
    2. Create diagnostic report and format it as an IMR Bundle (as defined in the Store Multimedia Report [RAD-141] transaction).  
      --You should include hyperlinks that reference images in the DICOM study.  (We realize that the links won't "work" in the preparatory samples because Report Readers won't have access to your locally-stored study.)
      --You should create a report that exercises the full features of your reporting application, i.e. if you are able to include the (optional) ServiceRequest, ImagingStudy, and/or ImagingSelection Resources in your Bundle, you should do that.   Robust samples make for better testing!
    3. Render your report (refer to IMR Section 2:4.141.4.1.2.2.3).  You will submit the diagnostic report in HTML format as a sample.  You may optionally submit a PDF version of the rendering as a sample.
    4. If you have this ability, perform a screen capture of the rendered report and save it as JPEG or other reasonable format.  The goal is for an Report Reader actor to examine your rendering and compare to what their software produces.
    5. Submit your sample files into Gazelle Test Managment:
  • Access Gazelle menu Testing-> Sample exchange.
    • On the Samples to share tab,  find the IMR entry and upload these:
      • your IMR Bundle (XML or JSON)
      • the associated DICOM imaging study (you may upload individual .dcm files or a zip file containing the images)
      • the rendering of your report in html
      • (optional) the rendering of your report in PDF
      • (optional) a screenshot of your rendered report

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.

 

Instructions for Report Readers/Rendered Report Readers/Image Managers

  1. Find sample images in Gazelle Test Management under Testing -> Sample exchange.    On the Samples available for rendering tab, you will find IMR entries submitted by other vendors.  (When a Report Creator 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. 
  2. Find the samples that are relevant for your application:  Report Readers will download the IMR Bundle.  Image Managers will download the DICOM study.
  3. Retrieve the sample 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.  (We realize that the links won't "work" in the multimedia report because Report Readers won't have access to the Creator's locally-stored study.  During Connectathon week, the Report Creator will link to images hosted on the Connectathon floor.)
  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 Test Management as the result file for this preparatory test.
  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 report and images. If you find problems with some samples, we will give your feedback to the Report Creator test partner.

Evaluation

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.