REM-NM_Sample_Exchange

Overview

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 with dose information encoded

REM-NM RAS

REM-NM Acquisition Modality

Dose Information Consumer, Dose Information Reporter, Dose Registry, Image Manager

 

Instructions for Creators:

FIRST, prepare the samples-->

  1. For RAS systems:  Determine a representative set of Radiopharmaceutical Radiation Dose Structured Reports (RRDSR) for your RAS that would help other actors understand your content. Good samples make for meaningful tests between vendors.
  2. For Modality systems: Determine a representative set of images for your modality that would help other actors unoderstand your content. In particular, we are looking for samples that demonstrate your ability to include dose information in your image objects per the requirements in RAD TF-2:4.8.4.1.2.5 for the REM-NM profile.
  3. Place the RRDSR(s) / image(s) in DICOM Part 10 files. (These are you 'sample' files.)

SECOND, upload your samples -->

  1. Upload sample(s) into Gazelle Test Management under Testing --> Sample exchange. On the Samples to share tab, upload your (s) under the REM-NM entry.   Refer to these help pages for details on managing samples in Gazelle.
  2. Assuming you have this ability, render a sample report using the template(s) you produced.  Perform a screen capture and/or save as JPEG or other reasonable format.  Upload the screenshot into Gazelle Test Management.
  3. 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.
  4. There is no specific evaluation for this test.  Feedback comes as your Consumer partners test with your content in their lab.

Instructions for Consumers

  1. Find sample RRDSRs and images uploaded by other vendors in Gazelle Test Management under Testing -> Sample exchange.    On the Samples available for rendering tab under the REM-NM 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 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 use the template in your system. If you find problems with some samples, we will give your feedback to the Modality test partner.
  7. The goal is no surprises.

Evaluation

  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.
  2. The evaluation of this test comes in the form of feedback from vendors who try to import/process/display the contents of your objects. If they find issues, you will be asked to work with those vendors to resolve those issues.