MESA/Image Display

From IHEWiki

Jump to: navigation, search

MESA/Image Display

Contents


Image Display Tests

Introduction

This document describes several tests for Image Display systems. The Display Consistency tests are defined in a separate document: Display Consistency Test Plan for Image Displays.

Integration Profiles and Test Procedures

This document lists a number of tests for Image Display Systems. You may not be responsible for all of these tests. Please refer to the Connectathon web tool to list the required tests for your system. The web address of this tool depends on the year and project manager. Please contact the appropriate project manager to obtain this information.

Message Attributes

Image Displays may make queries using a number of attributes. The tests defined in this document will request queries by specific attributes listed in the table below. It is expected that the Image Display software will contain other attributes as well; the tests require only that some attributes are present. The tests also allow you to perform multiple queries to cover all of the requested attributes. That is, we list a number of attributes in the table below and do not expect your system to use all of these attributes as matching keys in a single query.

Matching Key Attributes for Image Displays

Attribute Name Tag
Study Date 0008 0020
Accession Number 0008 0050
Patient Name 0010 0010
Patient ID 0010 0020
Modalities in Study 0008 0061


Message Values

Tests described in section 2 will require specific values in the matching keys. These are defined in tables in section 2.


Configuration

The MESA Image Manager maintains a database of DICOM applications used for C-Move operations. Add an entry for the storage SCP(s) associated with your workstation. Edit the text file $MESA_TARGET/db/loaddicomapp.pgsql (Unix) or $MESA_TARGET/db/loaddicomapp.sql (Windows NT) Use the existing entries as a template and add entries for your workstations as appropriate. The column names found in the SQL insert statements are described in the following table.

Column Name Description
aet DICOM Application Entity Title. Must be unique.
host Host name (or IP address) of the application.
port TCP/IP port number for receiving associations.
org The organization that operates the device. Useful if multiple organizations use the Image Manager.
com A comment field.


You can test your work as follows:

    perl  load_apps.pl imgmgr

The file $MESA_TARGET/runtime/imgmgr/ds_dcm.cfg is used to configure the MESA Image Manager. The only parameter users should change is the LOG_LEVEL value. Log levels are defined in Starting the MESA Servers. DICOM configuration parameters are listed in the table below.

Application AE Title Port
MESA Image Manager MESA_IMG_MGR 2350


Read the Runtime Notes section of the Installation Guide to determine the proper settings for the MESA runtime environment.


Starting the MESA Servers

These instructions assume you are using a terminal emulator on Unix systems or an MS DOS command window under Windows NT. Each test uses a command line interface; there is no graphical user interface. Before you start the test procedure, you need to start the MESA Image Manager servers. Make sure the appropriate database is running (PostgreSQL, SQL Server). To start the MESA servers:

1. Enter the Image Display exam folder: mesa_tests/rad/actors/imgdisp

2. Execute the appropriate script to start the servers:

     scripts/start_mesa_servers.csh  (Unix)
     scripts\start_mesa_servers.bat  (Windows)

Log levels are set for the MESA Image Manager in the file: $MESA_TARGET/runtime/imgmgr/ds_dcm.cfg. Log levels are:

0. no logging

1. errors

2. warnings

3. verbose

4. conversational (really verbose)

When you are finished running one or more tests, you can stop the servers:

    scripts/stop_mesa_servers.csh  (Unix)
    scripts\stop_mesa_servers.bat  (Windows)

Log files are stored in $MESA_TARGET/logs.


Submission of Results

Test descriptions below inform the reader to “submit results to the Project Manager”. This is does not mean “email”. The current submission process should be documented by the Project Manager, but will not include emailing files directly to the Project Manager.

Individual Tests

Test 281: Example Images and other DICOM objects

In this test, Image Displays will examine the DICOM samples provided by other participants. The goal of the test is to make sure the Image Display actors are not surprised by content when they arrive at a Connectathon.

Instructions

  1. Find sample images uploaded by other vendors for test 281 in gazelle under Connectathon -> List of samples.... See the "Samples available for rendering" tab. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the DICOM or zip files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. In gazelle, you can enter comments on individual samples. This will help your partners know your results.
  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 as the result file for this test.
  5. If you find issues with the images, send an email to the Connectathon Project Manager.
  6. The goal is no surprises.

Evaluation

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.

Test 282: Example GSPS objects

In this test, Image Displays will examine the GSPS samples provided by other participants. The goal of the test is to make sure the Image Display actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

  1. Find samples uploaded by other vendors for test 282 in gazelle under Connectathon -> List of samples.... See the "Samples available for rendering" tab. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the DICOM or zip files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. In gazelle, you can enter comments on individual samples. This will help your partners know your results.
  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 as the result file for this test.
  5. If you find issues with the images, send an email to the Connectathon Project Manager.
  6. The goal is no surprises.

Evaluation

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.

Supplemental Information

Test 285: DICOM SOP Classes

This test is DEPRECATED for Image Display actors
In this test, Image Displays will examine the list of DICOM Storage SOP Classes listed by other participants. The goal of the test is to make sure the Image Display actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

  1. On this wiki, find the page that lists Test Software/Data for your Connectathon. Do not use data from a different connectathon unless you are explicitly given that instruction from the Connectathon Manager. (For the Eye Care connectathon: Find a folder on ftp://ftp.aao.org. Find 'Connectathon_2008_samples' and the test 285folder.)
  2. On the Test Software/Data page, you should see a link to Shared Data and test 285. That will give you access to a page that lists SOP Classes supported by other vendors.
  3. You will find a table called Results Table on the samples for test 285. Extract this table and place it in a spreadsheet that can be read by Excel. Fill in the columns labelled Reviewed and Comments. The Comments field is mainly an indicator of issues with the SOP Classes. If there are no issues, you can leave that blank.
  4. When you are finished, upload the spreadsheet into the Kudu / Gazelle tool.
  5. If you find issues with the SOP Classes, send an email to the Connectathon Manager now to wake him or her up. You can also contact the image provider directly to resolve issues.
  6. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the spreadsheet you provided to make sure you made a good faith effort to review the SOP Classes. If you find a SOP Class you do not support, you should contact the Connectathon Manager to make sure that does not derail your testing.

Supplemental Information

Test 311: Create/Render Encapsulated PDF

In this test, Image Displays will render one Encapsulated PDF document

References

Instructions

1. Locate the encapsulated PDF file $MESA_STORAGE/EYECARE/PDF1/pdf1.dcm.

2. Open/import the file into our system (DICOM Part 10 file), or

3.

  • Set the current directory to $MESA_TARGET/mesa_tests/rad/actors/imgdisp
  • DICOM C-Store the object to your system:
   perl 311/load_311.pl AETITLE HOST port


4. Render the Encapsulated PDF document.

5. Capture the rendered output (screen dump, camera) and submit it into gazelle as the result file for this test.

Evaluation

Supplemental Information

Test 312: Create/Render SWF Evidence Document

In this test, Image Displays will render one or more evidence documents provided by the Project Manager.

This test is not yet ready; please refer to 314.

References

Instructions

Evaluation

Supplemental Information

The goal of this test is to make sure your system can render the Evidence Documents produced by other systems. This also serves as a test of those documents.

Test 314: Render submitted Evidence Documents

In this test, Image Displays will render one or more evidence documents submitted by other systems.

References

Instructions

1. For Eye Care Evidence Creators, the AAO ftp site will contain evidence documents submitted by other vendros

2. Import and render all documents. Create a text file and indicate that you either successfully rendered each document or describe problems with the document.

Evaluation


1. Upload the txt file into gazelle as the results for this test.

2. Email the project manager immediately if you find large problems with any of the Evidence Documents.

Supplemental Information

The goal of this test is to make sure your system can render the Evidence Documents produced by other systems. This also serves as a test of those documents.

Image Display Test 500: Display Calibration

Image Displays supporting the Consistent Presentation of Images and Mammo-related profiles must calibrate their displays in accordance with DICOM PS 3.14. Instructions for this test are included in the document: Display Consistency Test Plan for Image Displays. See section 2.2.

Instructions

To run this test, you will need to follow the "Visualization" link on the MESA distribution page: http://ihedoc.wustl.edu/mesasoftware/12.x/display_consistency/index.html This gives you access to the tools and documentation needed to run this test.

When you have completed the test, upload the results into gazelle.

Image Display Test 501: Image Display SCU Query Keys

In this test, the Image Display is required to query the MESA Image Manager using specific matching keys. For each matching key and value in the table below, direct the Image Display to make one or more queries of the MESA Image Manager. Repeat or multiple queries are allowed. That is, you might choose to query several times with a certain matching key. We do not expect the Image Display to send individual queries with multiple matching keys (Patient Name and Patient ID), but the test software will allow that.

Attribute Name Tag Matching Key Value
Study Date 0008 0020 19950126
Accession Number 0008 0050 2001B20
Patient Name 0010 0010 CRTHREE*
Patient ID 0010 0020 CR3
Modalities in Study 0008 0061 MR


References

Instructions

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in section Starting the MESA Servers.

3. Load the data sets into the MESA Image Manager.

   perl 50x/load_img_mgr.pl

4. Send at least one DICOM Study Level C-Find request (Study Root model) to the MESA Image Manager for each attribute/matching key value defined in the table above.

Evaluation

1. Run the evaluation script to verify that each attribute was requested in a query.

   perl 501/eval_501.pl <AE Title of  Image Display>

Supplemental Information

Results will be found in the file 501/grade_501.txt. Upload this file into gazelle as the results for this test. If you need to clear the existing queries to run the test again, you can restart at step 3 or run this script:

     perl  scripts/clear_img_mgr_queries.pl

Image Display Test 502: SCU Query Evaluation

This test uses the queries sent by the Image Display during Test 501 and any other queries you want to evaluate. This test examines all queries sent by the Image Display to determine if they are legal DICOM queries. After you conclude Test 501, the MESA Image Manager will still have a record of the queries sent by your Image Display. If you want to send more queries to the Image Manager, you may do so. There are no required queries. You might want to send queries at the Series and SOP Instance level.

References

Instructions

Evaluation

Evaluate the Image Display queries as follows:

    perl  502/eval_502.pl <AE Title of Image Display>

Supplemental Information

Query results are stored in the file 502/grade_502.txt. Upload this file into gazelle as results for this test.

As above, you can clear the queries stored by the MESA Image Manager as follows:

    perl scripts/clear_img_mgr_queries.pl

Image Display Test 503: Presentation State SCU Query Keys

There are no extra requirements for Image Displays when querying for Presentation State objects. There are other optional keys that are not tested with this software.


Image Display Test 504: Key Image Note SCU Query Keys

This test is not complete and is not required. Image Displays supporting the Key Image Note Integration Profile are required to support certain keys as matching and return keys.

Image Display Test 505: Patient Information Updated in Image Manager

This test is not ready with this release of software. This test simulates patient updates on an Image Manager. This is an optional test as Image Displays are not required to honor patient updates (only suggested to). You will be asked to retrieve images from the MESA Image Manager. We will then change the patient name on the Image Manager and ask you to retrieve the images a second time. Your software should update your internal system with the new patient name. This test produces no results that can be recorded.

References

Instructions

1. Repeat steps 1 through 4 as defined in Test 501.

2. Retrieve the study for patient XXXX.

3. Select a new name for patient XXXX. Change the name of the patient in the MESA Image Manager as follows:

   perl 505/change_patient_name.pl <new  name>

4. Query the MESA Image Manager and retrieve the images for the renamed patient. Your system should be updated with the proper information.

Evaluation

Supplemental Information


Image Display Test 506: Patients Merged in Image Manager

This test is not ready with this release of software. This test simulates patient merges on an Image Manager. As with test 505, this is an optional test for Image Display systems. You will be asked to retrieve images from the MESA Image Manager. We will then merge two patients on the Image Manager and ask you to retrieve the images a second time. Your software should update your internal system with the new patient name and ID. This test produces no results that can be recorded.

References

Instructions

1. Repeat steps 1 through 4 as defined in Test 501.

2. Retrieve the study for patient XXXX.

Evaluation

Supplemental Information


Image Display Test 511: Render Key Image Note 511

In this test, Image Displays will render a Key Image Note that refers to a single image from a series.

References

Instructions

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in section Starting the MESA Servers.

3. Load the Image data sets into the MESA Image Manager:

   perl 50x/load_img_mgr.pl

4. Load the Key Object data sets into the MESA Image Manager:

   perl 51x/load_img_mgr.pl

5. Retrieve the Key Image Note for the patient CRTHREE^PAUL with series number 511.

6. Render this Key Image Note and the one referenced image.

7. Capture the rendered output (screen dump, camera) and submit the output into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 512: Render Key Image Note 512

In this test, Image Displays will render a Key Image Note that refers to two images from one series.

References

Instructions

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 50x/load_img_mgr.pl

4. Load the Key Object data sets into the MESA Image Manager:

   perl 51x/load_img_mgr.pl

5. Retrieve the Key Image Note for the patient CTFIVE^JIM with series number 512.

6. Render this Key Image Note and the one referenced image.

7. Capture the rendered output (screen dump, camera) and submit the output into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 513: Render Key Image Note 513

In this test, Image Displays will render a Key Image Note that refers to two images; each from a different series.

References

Instructions

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 50x/load_img_mgr.pl

4. Load the Key Object data sets into the MESA Image Manager:

   perl 51x/load_img_mgr.pl

5. Retrieve the Key Image Note for the patient MRTHREE^STEVE with series number 513.

6. Render this Key Image Note and the one referenced image.

7. Capture the rendered output (screen dump, camera) and upload this file into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 521: Consistent Presentation of Images

This test is for Image Displays that support the Consistent Display of Images integration profile. Instructions for this test are found in the document Display Consistency Test Plan for Image Displays.

http://ihedoc.wustl.edu/mesasoftware/12.x/display_consistency/index.html

Access the Word document imgdisplay_testplan.doc dated 2004.01.29

See all of sections 2.3 through 3.3.

There are two documents to submit into gazelle:

  1. Excel spreadsheet that shows you have completed the display calibration
  2. Form at the end of the PDF where you indicate you have tested your display with all of the synthetic images that are included.

Test 552: Example Key Image Notes

In this test, Image Displays will examine the sample Key Image Notes provided by other participants. The goal of the test is to make sure the Image Display actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

  1. Find samples uploaded by other vendors for test 552 in gazelle under Connectathon-->List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create an excel spreadsheet or similar document Create columns labelled Vendor and Reviewed (Y/N) and Comments
  4. When you are finished, upload the spreadsheet as the results for this test.
  5. If you find issues with the samples, send an email to the Connectathon Manager now to wake him or her up. You can also contact the sample provider directly to resolve issues.
  6. The goal is no surprises.

Evaluation

The evaluation of this test is performed by examining the spreadsheet you provided to make sure you made a good faith effort to review the sample images.

Supplemental Information

Image Display Test 1720: Evidence Documents – Vendor Interoperability

Instructions

  1. Find samples uploaded by other vendors for test 1720 in gazelle under Connectathon-->List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create an excel spreadsheet or similar document Create columns labelled Vendor and Reviewed (Y/N) and Comments
  4. When you are finished, upload the spreadsheet as the results for this test.
  5. If you find issues with the samples, send an email to the Connectathon Manager now to wake him or her up. You can also contact the sample provider directly to resolve issues.
  6. The goal is no surprises.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Image Display Test 20603: ED: Describe Image Display/Report Creator Methods

References

Instructions

1. Do not divulge any proprietary information. Create a text file with the following naming convention: CompanyName_Product_20603_ID.txt and submit the file as results for this test.

In 500 words or less for each, describe the following:

  • which SOP Classes (e.g, Comprehensive, Basic Text, etc.) your product supports
  • which Templates (eg., Echo, Procedure Log) your product extracts evidence from
  • If your Image Display is grouped with a Report Creator, describe the content you extract from the retrieved document for the report you create

Evaluation

Supplemental Information

MESA: No software required.

Test Cases: PDI

These test cases are generally associated with the Radiology PDI profile

Test Case 1931: Media “Reader” Read RSNA 2005 CD

The purpose of this test is for the Display actor to open the DICOMDIR file on the RSNA 2005 CD and render the images and other composite objects on the CD.

References

The data from the RSNA 2005 CD can be found here http://ihedoc.wustl.edu/mesasoftware/10.15.0/dist/ext_data/pdi_2005/index.htm

RAD TF

Instructions

To run this test, follow these steps:

1. Obtain the RSNA 2005 PDI Demonstration CD. If you do not have a physical copy of the CD, download the ISO image of the CD from the MESA distribution page and create a CD from the ISO image.

2. Use your DICOM application to open the DICOMDIR file on the RSNA CD.

3. Select and display all of the studies on the CD. For those studies with multiple images, you can select a small subset of the images.

4. Create a simple text file that lists each vendor that submitted data and a simple yes/no that indicates whether you could display the data. If you had problems displaying the data, submit further evidence or documentation (to Kudu/Gazelle). Also, send an email to the Project Manager so he/she can investigate.

Evaluation

1. Submit the text file as the results for this test.

Supplemental Information

Test Case 1932: Media “Reader” Reads Vendor CDs

The purpose of this test is for the Display actor to open the DICOMDIR file on CDs provided by vendors for the RSNA 2005 PDI demonstration and to render the composite objects on those CDs.

References

The sample CDs are found at http://ihedoc.wustl.edu/mesasoftware/10.15.0/dist/ext_data/pdi_2005/index.htm

Instructions

To run this test, follow these steps:

1. Obtain the vendor CDs from the RSNA 2005 PDI Demonstration. If you do not have a physical copy of the CDs, download the ISO images from the MESA distribution page and create a CD from the ISO image.

2. Use your DICOM application to open the DICOMDIR file on each vendor CD.

3. Select and display all of the studies on the CD. For those studies with multiple images, you can select a small subset of the images.

4. Create a simple text file. List each vendor that supplied a CD and indicate with a simple yes/no if you could display the images. If you believe the images or CD are faulty, submit additional screen shots or other documentation to illustrate the problem. Also, follow up with email to the Project Manager.

Evaluation

1. Submit the text file as the results for this test.

Supplemental Information

Nuclear Medicine Profile Tests

Image Display Test 2240: Vendor Sample NM Images

This test applies to Image Displays in the NM profile. This test allows Image Displays to test with sample image sets submitted by NM Acquisition Modalities.


Instructions

  1. Find samples uploaded by other vendors for test 2240 in gazelle under Connectathon-->List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create an excel spreadsheet or similar document Create columns labelled Vendor and Reviewed (Y/N) and Comments
  4. When you are finished, upload the spreadsheet as the results for this test.
  5. The goal is no surprises.


Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


1. Upload the spreadsheet as the results for this test.

2. Email the project manager immediately if you find large problems with any of the image sets.

Supplemental Information

The goal of this test is to make sure your system can properly render the NM images produced by other systems. This also serves as a test of those images.

Image Display Test 2400: NM Display Window Upper/Lower

Reference

Rad TF-1: E.5.1.

Instructions

Open or import the NM image in file MESA2400.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2400 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. This will be a synthetic image of a wedge with 8 bit data.

Image Display should have controls to display images using “Window Upper” and “Window Lower” values. Display the image using an upper value of 255 and a lower value of 155. You should see the bright part of the wedge on the right side of your display and the left side should be dark.

Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit that file as results for this test.

Evaluation

Supplemental Information

Image Display Test 2401: NM Display Pseudo-Color

Not available. Enter a note in Kudu that the test is not available.

Reference

Rad TF-1: E.5.1.

Instructions

Open or import the NM image in file MESA2401.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2401 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. Image Display actors should be able to load a pseudo-color table to map intensity values. The format of the table is unspecified. The test data includes an Excel spreadsheet that maps intensity values to RGB colors. The spreadsheet is in the file $MESA_TARGET/mesa_tests/rad/actors/imgdisp/color/2401.xls. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2402: NM Image Resizing 1

Reference

Rad TF-1: E.5.2.

Instructions

Open or import the NM image in file MESA2402.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2402 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. The test image is stored at 32x32 pixels. Display the image according to the Frame Zoom Guidelines in Rad TF-1: E.5.2. Use an upper value of 1280 and a lower value of 768. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2403: NM Image Resizing 2

Not available; enter a note in Kudu saying the test is not available.

Reference

Rad TF-1: E.5.2.

Instructions

Open or import the NM image in file MESA2403.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2403 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. The test image is stored at 64x64 pixels. Display the image according to the Frame Zoom Guidelines in Rad TF-1: E.5.2. Use an upper value of 1280 and a lower value of 768. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2404: NM Image Resizing 3

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-1: E.5.2.

Instructions

Open or import the NM image in file MESA2404.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2404 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. The test image is stored at 128x128 pixels. Display the image according to the Frame Zoom Guidelines in Rad TF-1: E.5.2. Use an upper value of 1280 and a lower value of 768. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2405: NM Image Resizing 4

Reference

Rad TF-1: E.5.2.

Instructions

Open or import the NM image in file MESA2405.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2405 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. The test image is stored at 256x1024 pixels. Display the image according to the Frame Zoom Guidelines in Rad TF-1: E.5.2. Use an upper value of 1280 and a lower value of 768. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2406: NM Image Display Query Keys

Reference

Rad TF-2: 4.14.4.1.2

Instructions

In this test, Image Displays will query an Image Manager for Study and Series level information and display that for the user. In particular, the Image Display is supposed to query for and be able to display the DICOM attribute Series Description (0008, 103E). The Image Display need not query by Series Description; it only needs to use that attribute as a return key and display the data.

1. Start the MESA servers as described in Starting the MESA Servers above.

2. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

3. Query the Image Manager for all NM studies (modalities in Study = NM)

4. Select one of the studies from the returned list. Display the study information including Series Description.

5. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2408: NM Image Display Attributes

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

In test 2408, the Image Display is required to display these attributes:

    0054  0220 View Code Sequence
    0040  0555 Acquisition Context Sequence
    0008  103E Series Description

The Image Display will retrieve a specific image from the MESA Image Manager, display the image and demonstrate the display of the attributes listed above. The Technical Framework does not specify how the values are displayed nor the actions required by the user.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2408.

5. Display the study information including the attributes listed above.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2410: NM Grid Display

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.2

Instructions

In test 2410, the Image Display is required to display an image using the Grid Display.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2410.

5. Display all frames of the image using a Grid Display.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2411: NM Fit Display

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.2

Instructions

In test 2411, the Image Display is required to display an image using the Fit Display.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

    perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2411.

5. Display all frames of the image using a Fit Display.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2412: NM Comparison Display

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.2

Instructions

In test 2412, the Image Display is required to display an image using the Comparison Display.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2412.

5. The image is a DYNAMIC image with two values for Energy Window. Use Energy Window to define two framesets. Display the framesets in a Comparison Display.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

Evaluation

Supplemental Information


Image Display Test 2413: NM Wholebody Display

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.2

Instructions

In test 2413, the Image Display is required to display an image using the Wholebody Display.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2413.

5. Display the image frames using a Wholebody Display.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

Evaluation

Supplemental Information


Image Display Test 2414: NM MPR Display

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.2

Instructions

In test 2414, the Image Display is required to display an image using the MPR Display.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

    perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2414.

5. Display the image frames using a MPR Display.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

Evaluation

Supplemental Information


Image Display Test 2415: NM Image Zoom

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.4

Instructions

In test 2415, the Image Display is required to display an image with zoom.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2415.

5. Display the image frames at 1x zoom. Repeat the display at 2x zoom. Capture both screen displays as described in step 6 below.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

Evaluation

Supplemental Information


Image Display Test 2416: NM Image Review Option

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3.5

Instructions

In test 2416, the Image Display is required to display images with the Image Review Option.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2416.

5. Display series 1 and series 2 at the same time. Series 1 is a dynamic image set; series 2 is a static image set.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

7. Select a hot spot on the image in series 2. Display the value of a selected pixel.

8. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

Evaluation

Supplemental Information


Image Display Test 2417: NM Result Screens

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.4

Instructions

In test 2416, the Image Display is required to display images with the Image Review Option.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2417.

5. Display all images (multiple series) sequentially. For each series/image, perform a screen capture as defined below.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation.

Evaluation

Supplemental Information


Image Display Test 2420: NM Image STATIC

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

Open or import the NM image in file MESA2420.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2420 <AE Title> host port

to push (DICOM C-Store) the image to your Image Display actor. This image has these values

Energy Window 1 value
Detector # 2 values


A tabular representation is:

Frame 1 2
Energy Window # 1 1
Detector # 1 2


This image has one value for Energy Window and two values for Detector. Select the second Detector and display the image in a Grid Display or Fit Display. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation. Use IE or other browser to display the file MESA2420CINE.gif. This should display a cine view of the data listed above. Be prepared to show your display to a Project Manager at the Connectathon. You do not need to submit a screen capture of the cine movie.

Evaluation

Supplemental Information


Image Display Test 2421: NM Image WHOLEBODY

Not available. Enter a note in Kudu saying the test is not available.

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

Evaluation

Supplemental Information

Test not defined.


Image Display Test 2422: NM Image DYNAMIC

Reference

Rad TF-2: 4.16.4.2.2.3 DICOM P3.3 C.8.4.8

Instructions

Open or import the NM image in file MESA2422.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2422 <AE Title> host port

This image has these values

Energy Window 1 value
Detector # 2 values (1, 2)
Phase # 1 values
Time Slice # 6 values


A tabular representation is:

Energy Window #
Frame 1 2 3 4 5 6 7 8 9 10 11 12
1 1 1 1 1 1 1 1 1 1 1 1
Detector # 1 1 1 1 1 1 2 2 2 2 2 2
Phase # 1 1 1 1 1 1 1 1 1 1 1 1
Time Slice # 1 2 3 4 5 6 1 2 3 4 5 6


Select the second Detector and first phase and display the frames in a Grid Display or Fit Display. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation. Use IE or other browser to display the file MESA2422CINE.gif. This should display a cine view of the data listed above. Use your Image Display system to display the same cine view. Discounting display speed, the displays should be equivalent. Be prepared to show your display to a Project Manager at the Connectathon. You do not need to submit a screen capture of the cine movie.

Evaluation

Supplemental Information


Image Display Test 2423: NM Image GATED

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

Open or import the NM image in file MESA2423.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2423 <AE Title> host port

This image has these values

Energy Window 1 value
Detector # 1 value
R-R Interval 3 values
Time Slot Multiple values


A tabular representation is:

Frame 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
Energy Window # 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Detector # 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
R-R interval 1 1 1 1 1 2 2 2 2 2 3 3 3 3 3 3 3 3
Time Slot # 1 2 3 4 5 1 2 3 4 5 1 2 3 4 5 6 7 8

Select the first Detector and first R-R Interval and display the frames in a Grid Display or Fit Display. Also, select the first Detector and third R-R Interval and display the frames in a Grid Display or Fit Display. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation. Use IE or other browser to display the file MESA2423RR1CINE.gif and MESA2423RR3CINE.gif. This should display a cine view of the data listed above. Use your Image Display system to display the same cine view. Discounting display speed, the displays should be equivalent. Be prepared to show your display to a Project Manager at the Connectathon. You do not need to submit a screen capture of the cine movie.

Evaluation

Supplemental Information


Image Display Test 2424: NM Image TOMO

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

Open or import the NM image in file MESA2424.dcm. From the imgdisp test directory, you can use the script:

    perl  scripts/send_nm_image.pl 2424 <AE Title> host port

This image has these values

Energy Window 1 value
Detector # 1 value
Rotation 2 values
Angular View 10 values

Display the frames in a Grid Display or Fit Display. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit to the Project Manager for evaluation. Use IE or other browser to display the file MESA2424CINE.gif. This should display a cine view of the data listed above. Use your Image Display system to display the same cine view. Discounting display speed, the displays should be equivalent. Be prepared to show your display to a Project Manager at the Connectathon. You do not need to submit a screen capture of the cine movie.

Evaluation

Supplemental Information


Image Display Test 2425: NM Image GATED TOMO

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

Evaluation

Supplemental Information

Test not defined.


Image Display Test 2426: NM Image RECON TOMO

Reference

Rad TF-2: 4.16.4.2.2.3

Not available. Enter a note in Kudu saying the test is not available.

Instructions

Evaluation

Supplemental Information

Test not defined.


Image Display Test 2427: NM Image GATED RECON TOMO

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

Evaluation

Supplemental Information

Test not defined.


Image Display Test 2428: NM Image Display Multiple Framesets

Reference

Rad TF-2: 4.16.4.2.2.3

Instructions

In test 2428, the Image Display displays multiple framesets taken from two different series of the same study.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the Image data sets into the MESA Image Manager:

   perl 24xx/load_img_mgr.pl

4. Retrieve the study with Patient ID MESA2428.

5. Display both series simultaneously.

6. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE. Label the file with your company name and test number and submit it into gazelle as results for this test.

Evaluation

Supplemental Information

Image Display Test 2435: Cardiac NM Option

This test applies to Image Displays which support the Cardiac NM Option. This test allows Image Displays to test with sample image sets submitted by NM Acquisition Modalities.

The Image Displays will ensure they are able to use MPR of two RECON TOMO short axis images to display them in the standard format approved by the American College of Cardiology (ACC NM Cardiac Display format). See Technical Framework references below .

Reference

Rad TF-1: Appendix E.5.2, E.5.2.1-3 Rad TF-2:4.16 Table 4.16-1 and 4.16.4.2.2.3.2

Instructions

  1. Find samples uploaded by other vendors for test 2435 in gazelle under Connectathon-->List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create an excel spreadsheet or similar document Create columns labelled Vendor and Reviewed (Y/N) and Comments
  4. When you are finished, upload the spreadsheet as the results for this test.
  5. The goal is no surprises.


Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


1. Upload the spreadsheet as the results for this test.

2. Email the project manager immediately if you find large problems with any of the image sets.

Supplemental Information

The goal of this test is to make sure your system can properly render the NM images produced by other systems. This also serves as a test of those images.

Image Fusion (FUS) Profile Tests

The tests in this section apply to Image Display actors in the Image Fusion Profile.

Image Display Test 3548: Image Fusion SCU Query Keys

<this test is not yet implemented in the MESA tools>

In this test, the Image Display is required to query the MESA Image Manager using specific matching keys. For each matching key and value in the table below, direct the Image Display to make one or more queries of the MESA Image Manager. Repeat or multiple queries are allowed. That is, you might choose to query several times with a certain matching key. We do not expect the Image Display to send individual queries with multiple matching keys (Patient Name and Patient ID), but the test software will allow that.

Attribute Name Tag Matching Key Value
Study Date 0008 0020 19950126
Accession Number 0008 0050 2001B20
Patient Name 0010 0010 CRTHREE*
Patient ID 0010 0020 CR3
Modalities in Study 0008 0061 MR


References

Instructions

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in section Starting the MESA Servers.

3. Load the data sets into the MESA Image Manager.

   perl 3548/load_img_mgr.pl

4. Send at least one DICOM Study Level C-Find request (Study Root model) to the MESA Image Manager for each attribute/matching key value defined in the table above.

5. After running this test, you should proceed to test 502.

Evaluation

1. Run the evaluation script to verify that each attribute was requested in a query.

   perl 3548/eval_3548.pl <AE Title of Image Display>

Supplemental Information

Results will be found in the file 3548/grade_3548.txt. Submit this file into gazelle as results for this test. If you need to clear the existing queries to run the test again, you can restart at step 3 or run this script:

     perl  scripts/clear_img_mgr_queries.pl

Image Display Test 3560: Apply BSPS and Display – same FoR

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2

Instructions

In test 3560, the Image Display is required to display the underlying and superimposed image sets (two series with the same Frame of Reference) according to the blending parameters in the BSPS.

Prepare to receive the test objects for this test. From the imgdisp test directory, you can use the script:

    perl scripts/store_fusion_objects.pl 3560  <AE Title> host port

to push (DICOM C-STORE) the BSPS and image objects patient Kumquat^K for this test to your Image Display actor.

1. Image Display should render the fused display

2. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

3. Label the file with your company name and test number and submit into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3562: Apply BSPS, Spatial Registration – different FoR

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2

Instructions

In test 3562, the Image Display is required to display the underlying and superimposed image sets (two series with the different Frames of Reference) according to the blending parameters in the BSPS and the transformations in the Spatial Registration object.

Prepare to receive the test objects for this test. From the imgdisp test directory, you can use the script:

    perl scripts/store_fusion_objects.pl 3562  <AE Title> host port

to push (DICOM C-STORE) the BSPS and image objects patient Lemon^L for this test to your Image Display actor.

1. Image Display should render the fused display with the specified transformations.

2. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

3. Label the file with your company name and test number and submit into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3600: Side-by-side display: underlying and superimposed

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2

Instructions

In test 3600, the Image Display is required to display the underlying and superimposed image sets (series) side-by-side (ie un-blended). Optionally, the Image Display may also display the underlying and superimposed image sets along with the fused display (all three visible at once); this 3-up display is not required in the Image Fusion profile.

Prepare to receive the test objects for this test. From the imgdisp test directory, you can use the script:

    perl  scripts/store_fusion_objects.pl 3600 <AE Title> host port

to push (DICOM C-STORE) the BSPS, Spatial Registration and image objects patient Grape^G for this test to your Image Display actor.

1. Image Display should display the two individual image sets, underlying and overlay, side-by-side.

2. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

3. Label the file with your company name and test number and submit to the Project Manager for evaluation.

4. This step is optional. If you are capable of displaying the underlying, overlay, and fused images at the same time so that all 3 are visible on the display, perform a screen capture of this and label the file with your company name and test number (3600-opt) and submit it into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3602: Adjusting transparency of the fusion overlay

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2

Instructions

In test 3602, the Image Display is required to demonstrate it provides the user the ability to adjust the transparency of the fusion overlay (blending factor).

Prepare to receive the test objects for this test. From the imgdisp test directory, you can use the script:

    perl scripts/store_fusion_objects.pl 3602  <AE Title> host port

to push (DICOM C-STORE) the BSPS and image objects for patient Berry^B for this test to your Image Display actor.

1. The Image Display should display the fused images with the default blending parameters.

2. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

3. Label the file with your company name and test number-BEFORE (eg XYZ-Company-3602-BEFORE.jpg) and submit it into gazelle as results for this test.

4. Next, the Image Display demonstrate that the user can adjust the transparency of the fusion overlay. Perform a screen capture of this modified display.

5. Label this second screen capture file with your company name and test number-BEFORE (eg XYZ-Company-3602-AFTER.jpg) and submit it into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3604: Display Multi-Planar Reconstructed planes of fused data

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2

Instructions

In test 3604, the Image Display is required to demonstrate its ability to do MPR display of fused data.

Prepare to receive the test objects for this test. From the imgdisp test directory, you can use the script:

    perl scripts/store_fusion_objects.pl 3604  <AE Title> host port

to push (DICOM C-STORE) the BSPS and image objects for patient Fig^F for this test to your Image Display actor.

1. The Image Display should display the fused images with the default blending parameters.

2. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

3. Label the file with your company name and test number and submit it into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3606: Controls for Upper Window and Lower Window Level (NM & PET)

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2 Rad TF-1:E.5.1

Instructions

In test 3606, the Image Display is required to demonstrate it provides direct independent control over the Upper Window Level and the Lower Window Level display parameters for NM and PET series.

Prepare to receive the test objects for this test. From the imgdisp test directory, you can use the script:

    perl scripts/store_fusion_objects.pl 3606  <AE Title> host port

to push (DICOM C-STORE) BSPS and image objects (PET/CT) for patient Raisin^R for this test to your Image Display actor.

1. The Image Display should display the fused images with the default blending parameters.

2. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

3. Label the file with your company name and test number and submit it into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3608: Display Series Description and Derivation Code Sequence

<Note: the datasets needed to run this test are not yet available in MESA_STORAGE>

Reference

Rad TF-2:4.17.4.2.3.2

Instructions

Test 3608 uses the same images as test 3606. The Image Display is required to display the values of Series Description (0008,103E) and Derivation Code Sequence (0008,9215) (Code Value, Coding Scheme, Code Meaning) to the user.

1. If you have not already done so, retrieve the images for test 3606; instructions are contained in that test.

2. The Image Display should display the fused images and demonstrate its display to the user of the values for Series Description and Derivation Code Sequence.

3. Perform a screen capture and store the result in a JPEG, GIF or other format that is easily displayable using IE.

4. Label the file with your company name and test number and submit it into gazelle as results for this test. There will be separate instructions for uploading the images (ftp, web upload). Do not email the images.

Evaluation

Supplemental Information

Image Display Test 3620: Image Fusion –Vendor Interoperability

Instructions

Test 3620 tests the display of BSPS, Spatial Registration and image objects for Fusion created by other vendors. Every vendor’s objects submitted to the MESA test tool for this profile in test 3620 must be tested and properly displayed. No MESA software required.

1. DICOM data sets (BSPS, Spatial Registration, image series) created by Acquisition Modality and Evidence Creator actors in the Fusion Profile for MESA testing will be made available to Image Display actors. You will find these samples in gazelle under Connectathon--List of samples. Select your system name and look under Objects to render to find the sample images, BSPS and Spatial Registration objects for test 3620. We ask vendors to submit these samples at least 2 weeks prior to the pre-connectathon test deadline.

2. The Image Display should store these DICOM objects and display the fused images so that you are confident your software understands the content. You should display the original and fused data; try modifying the fusion overlay; ensure you can navigate various dimensions of the data

3. Create a screen snapshot from your own product which demonstrates that the Vendor-created DICOM objects were used to create a fused display as applicable. You should create a file using the document naming convention of: YourCompanyName_YourProduct_ 3620_ID_n, where n is any number to that you make up to differentiate the files if your company has submitted multiple screen shots. Upload this file into gazelle as the results for test 3620.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the fused studies, you should notify the Project Manager. You will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

Mammography Acquisition Workflow Integration Profile Tests

This section describes tests that are specific to the IHE Mammography Acquisition Workflow Integration (MAWF) profile.

Image Display Test 4100: MAWF Vendor Interoperability - Recall Case

This test gives Image Displays access to sample images for the recall case created by MAWF Acquisition Modalities prior to the Connectathon. Modalities will create both FOR PRESENTATION and FOR PROCESSING images for a mammography study. Then they will simulate a "Recall" case and encode "Recall for patient symptoms/clinical findings" as the Reason for Requested Procedure. Modalities are asked to submit samples into gazelle 3 weeks prior to the MESA test deadline or earlier. The goal is to avoid surprises on the Connectathon floor.

References

RAD TF-2:4.16.4.2.2.5

RAD TF-2:4.5.4.2.2.2

RAD TF-2:4.8.4.1.2

Instructions

You will find these samples in gazelle under Connectathon -> List of Samples. Select your system name and look under Samples available for rendering to find the sample images for test 4100.

Your task is to test with these samples prior to the Connectathon. Do not complete this test before those samples are available. See expected behavior for Image Displays in the TF references above.

Create a short txt file indicating you have accessed these samples. List those that you have successfully tested with your Image Display. If you find a problem, contact the Project Manager who will facilitate working with the modality or EC vendor.

Upload that txt file into the gazelle system as results for this test.

Image Display Test 4102: MAWF Vendor Interoperability - View Correction

Image Managers in the MAWF profile are required to support DICOM KOS objects as well as mammography images.

This test gives you access to sample images and KOS objects created by MAWF Acquisition Modalities and Evidence Creators prior to the Connectathon. They are asked to submit samples into gazelle 3 weeks prior to the MESA test deadline or earlier. The goal is to avoid surprises on the Connectathon floor.

References

RAD TF-2:4.31.4.2.3.1

Instructions

You will find these samples in gazelle under Connectathon -> List of samples. Select your system name and look under Samples available for rendering to find the sample images and KOS objects for test 4102.

Your task is to test with these samples prior to the Connectathon. Do not complete this test before those samples are available. See expected behavior in the TF reference above.

Create a short txt file indicating you have accessed these samples. List those that you have successfully tested with your Image Display. If you find a problem, contact the Project Manager who will facilitate working with the modality or EC vendor.

Upload that txt file into the gazelle system as results for this test.

PERF - CT/MR Perfusion Imaging with Contrast Tests

This section describes tests that are specific to the Radiology CT/MR Imaging with Contrast Integration Profile.

Test Case 4550: PERF Vendor Interoperability - Exchange Enhanced CT and MR Image Samples

Test 4550 tests the display of DICOM objects created by Acquisition Modality actors in the PERF profile. Every vendors' objects submitted must be tested and properly displayed.


Instructions

1. Download the participant-supplied datasets for this test. These are found in Kudu under Connectathon-->List of samples. Select your system name and look under Samples available for rendering to find sample images for test 4550.

2. Render the studies according to requirements in the Technical Framework - RAD TF-2: 4.16.4.2.2.7.

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully render them. If not, detail the problem. Upload that file into gazelle as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

DIFF - MR Diffusion Imaging Tests

This section describes tests that are specific to the Radiology MR Diffusion Imaging Integration Profile.

Test Case 4650: DIFF Vendor Interoperability - Exchange Enhanced MR Image Samples

Test 4650 tests the display of DICOM objects created by Acquisition Modality actors in the DIFF profile. Every vendors' objects submitted must be tested and properly displayed.


Instructions

1. Download the participant-supplied datasets for this test. These are found in gazelle under Connectathon-->List of samples. Select your system name and look under Samples available for rendering to find sample images for test 4650.

2. Render the studies according to requirements in the Technical Framework - RAD TF-2: 4.16.4.2.2.6.

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully render them. If not, detail the problem. Upload that file into gazelle as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

BIR - Basic Image Review

This section describes tests that are specific to the Radiology Basic Image Review Profile

Test Case 4700: BIR Connectathon tests

The Image Display actor in BIR is unlike other IHE actors in that its requirements are primarily functional and do not require exchange of messages with other actors. At the Connectathon, a monitor will sit down at your system and run through a set of tests to evaluate the requirements in the BIR profile. With this test, we are providing you with the test steps and the accompanying images in advance of the Connectathon. We expect you to run these tests in your lab in preparation for the Connectathon itself.

Instructions

1. Download the Connectathon Test Plan for BIR Image Display actors: ftp://ftp.ihe.net/Connectathon/bir_data_sets/BIR_Image_Display_Connectathon_Tests-2014-04-07.pdf

2. Download the BIR test images (BIRTestData_2015.tar.bz2) found at ftp://ftp.ihe.net/Connectathon/bir_data_sets/

3. In that directory, you will also find an index to the BIR dataset. See ftp://ftp.ihe.net/Connectathon/bir_data_sets/_README_BIR_dataset_reference_2014-04-07.xls

4. Run the tests using your Image Display application. On or before the MESA test deadline, create a text file that briefly describes your progress in running these tests. Upload that file into gazelle as the result file for test 4700.

Evaluation

There is no pass/fail for this. We want to make sure you're making progress toward what is expected at the connectathon.

SMI - Stereotactic Mammography Imaging Tests

This section describes tests that are specific to the Radiology Stereotactic Mammography Imaging Profile.

Test Case 4950: SMI Vendor Interoperability - Exchange Stereotactic Mammography Image Samples

Test 4950 tests the display of DICOM objects created by Acquisition Modality actors in the SMI profile. All Modality vendors' objects submitted must be tested and properly displayed.


Instructions

1. Download the participant-supplied datasets for this test. Modality vendors are asked to upload these to the IHE FTP Site 2-3 weeks prior to the pre-Connectathon test deadline: ftp://ftp.ihe.net/Connectathon/samples/RAD-profiles/SMI_Samples/. Find the sub-directory for your connectathon.

2. Render the studies according to requirements in the Technical Framework - RAD TF-2: 4.16.4.2.2.1.X (in 2013, this section is in the SMI Trial Implementation Supplement.

3. There are very specific display requirements that will be evaluated at the connectathon. We highly encourage you to review the connectathon tests for rendering and try the tests in advance in your own lab. These connectathon tests can be found in gazelle: SMI_Display_Modality_Images" and SMI_Display_Annotation".

4. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully render them. If not, detail the problem. Upload that file into gazelle as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

DBT - Digital Breast Tomosynthesis Tests

This section describes tests that are specific to the Radiology Stereotactic Mammography Imaging Profile.

Test Case 5250: DBT Vendor Interoperability - Exchange Digital Breast Tomosynthesis Image Samples

Test 5250 tests the display of DICOM objects created by Acquisition Modality actors in the DBT profile. All Modality vendors' objects submitted must be tested and properly displayed.


Instructions

1. Download the participant-supplied datasets for this test. Modality vendors are asked to upload these to the IHE FTP Site 2-3 weeks prior to the pre-Connectathon test deadline: ftp://ftp.ihe.net/Connectathon/samples/RAD-profiles/DBT_samples/. Find the sub-directory for your connectathon.

2. Render the studies according to requirements in the Technical Framework - RAD TF-2: 4.16.4.2.2.1.7 (in 2014, this section is in the DBT Trial Implementation Supplement.

3. There are very specific display requirements that will be evaluated at the connectathon. We highly encourage you to review the connectathon tests for rendering and try the tests in advance in your own lab. These connectathon tests can be found in gazelle: DBT_Display_Modality_Images" and DBT_Display_Annotation".

4. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully render them. If not, detail the problem. Upload that file into gazelle as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

IID - Invoke Image Display profile tests

The tests in this section apply to Image Display actors in the Radiology domain Invoke Image Display profile.

Test Case 5100: IID - Prepare Connectathon Test Data

To enable Connectathon testing, the Image Display is required host studies on its Image Display.

There is one Connectathon test -- IID Invoke Display -- to exercise the Image Display and Image Display Invoker in the IID profile. The 'Special Instructions' for that test ask you to host a set of studies. This pre-Connectathon 'test' ensures you have the proper data loaded on your system prior to arriving at the Connectathon.

We do not provide specific studies for you, but rather define the characteristics of the studies you should bring


Instructions

1. Come to the Connectathon with:

  • at least 3 studies for the same patient, ie will have the same value in patient ID, but the accession number and study dates will be different for each of these studies.
  • at least one other study for a different patient
  • a study containing a KOS object identify at least one image in the study as a 'key image'


Evaluation

1. Create a text file indicating that you have prepared this test data. Upload that text file into gazelle as the result file for this pre-Connectathon test. That is your indication that you have prepared for Connectathon testing.

Echo Workflow Profile (ECHO) Tests

Test Case 20404: ECHO –Vendor Interoperability

Test 20404 tests the display of DICOM objects created Acquisition Modality actors in the ECHO profile. Import the objects which match the option your Image Display supports. Every vendors' objects submitted must be tested and properly displayed.


No MESA software is required for this test.

References


Instructions

1. Download the participant-supplied datasets for this test. These are found in the connectathon webtool

2. Render the studies according to requirements in the Technical Framework.

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully render them. If not, detail the problem. Upload that file as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Cath Workflow Profile (CATH) Tests

Test Case 20405: CATH –Vendor Interoperability

Test 20405 tests the display of DICOM objects created Acquisition Modality & Evidence Creator actors in the CATH profile. Import the objects which match the option your Image Display supports. Every vendors' objects submitted must be tested and properly displayed.


No MESA software is required for this test.

References


Instructions

  1. Find CATH samples uploaded by other vendors in gazelle under Connectathon-->List of samples. This page will evolve as vendors add samples, so be patient.
  1. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  2. Create an excel spreadsheet or similar document Create columns labelled Vendor and Reviewed (Y/N) and Comments
  3. When you are finished, upload the spreadsheet as the results for this test.
  4. If you find issues with the samples, send an email to the Connectathon Manager now to wake him or her up. You can also contact the sample provider directly to resolve issues.
  5. The goal is no surprises.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Evidence Document – Cardiology Options Tests

Image Display Test 20630: Evidence Display – Cath option

<this test is not yet implemented in the MESA tools>

Test 20630 tests the display of a well known SR.

References

Card TF-2:4.4.2

Instructions

In test 20630, the Image Display displays a known SR document.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the SR data sets into the MESA Image Manager:

   perl 20630/load_img_mgr.pl

4. The vendor should create a word file using the document naming convention of: CompanyName_Product_ 20630_ID_2008.doc. Using any vendor tool cut and paste in a screen snapshot from your own product which demonstrates that the DICOM SR information was displayed.

Evaluation

No MESA test script required for evaluation. Submit your snapshot to the Project Manager as your results for this test.

Supplemental Information


Image Display Test 20631: Evidence Display – Echo Evidence option

<this test is not yet implemented in the MESA tools>

Test 20631 tests the display of a well known SR.

Reference

Card TF-2:4.4.3

Instructions

In test 20631, the Image Display displays a known SR document.

1. Create/modify the SQL script to identify the Image Display under test.

2. Start the MESA servers as described in Starting the MESA Servers above.

3. Load the SR data sets into the MESA Image Manager:

   perl  20631/load_img_mgr.pl

4. The vendor should create a word file using the document naming convention of: CompanyName_Product_ 20631_ID_2008.doc. Using any vendor tool cut and paste in a screen snapshot from your own product which demonstrates that the DICOM SR information was displayed.

Evaluation

No MESA test script required for evaluation. Submit your snapshot to the Project Manager as your results for this test.

Supplemental Information


Image Display Test 20640: Evidence Display – Cath – Vendor Interoperability

References

Instructions

Test 20640 tests the display of SR objects created by other vendors. Every Evidence Creator which supports the Cath Evidence option will submit sample objects. Each of these must be tested and properly displayed.

MESA: No MESA software required.

Task Verify
C-Store and Display every (all) cath SR objects which are submitted by Evidence Creator vendors for test 20640 Visually verify that, in some reasonable format, the template data is displayed.

Instructions

  1. Find SRs uploaded by other vendors for test 20640 in gazelle under Connectathon -> List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create a word file using the document naming convention of: YourCompanyName_YourProduct_ 20640_ID__n.doc , where n is any number to that you make up to differentiate the files if your company has submitted multiple objects.
  1. Using any tool, cut and paste in a screen snapshot from your own product which demonstrates that the Vendor-created DICOM SR objects' information was displayed as applicable. Upload the snapshot(s) as the results for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the reports, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Image Display Test 20641: Evidence Display – Echo – Vendor Interoperability

References

Instructions

Test 20641 tests the display of SR objects created by other vendors. Every Evidence Creator which supports the Echo Evidence option will submit sample objects. Each of these must be tested and properly displayed.

MESA: No MESA software required.

Task Verify
C-Store and Display every (all) echo SR objects which are submitted by Evidence Creator vendors for test 20641 Visually verify that, in some reasonable format, the template data is displayed.

Instructions

  1. Find SRs uploaded by other vendors for test 20641 in gazelle under Connectathon -> List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create a word file using the document naming convention of: YourCompanyName_YourProduct_ 20641_ID__n.doc , where n is any number to that you make up to differentiate the files if your company has submitted multiple objects.
  1. Using any tool, cut and paste in a screen snapshot from your own product which demonstrates that the Vendor-created DICOM SR objects' information was displayed as applicable. Upload the snapshot(s) as the results for this test.


Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Image Display Test 20642: Evidence Display – CTA/MRA – Vendor Interoperability

References

Instructions

Test 20642 tests the display of SR objects created by other vendors. Every Evidence Creator which supports the CTA/MRA Evidence option will submit sample objects. Each of these must be tested and properly displayed.

MESA: No MESA software required.

Task Verify
C-Store and Display every (all) CTA/MRA SR objects which are submitted by Evidence Creator vendors for test 20642 Visually verify that, in some reasonable format, the template data is displayed.

Instructions

  1. Find SRs uploaded by other vendors for test 20642 in gazelle under Connectathon -> List of samples. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create a word file using the document naming convention of: YourCompanyName_YourProduct_ 20642_ID__n.doc , where n is any number to that you make up to differentiate the files if your company has submitted multiple objects.
  1. Using any tool, cut and paste in a screen snapshot from your own product which demonstrates that the Vendor-created DICOM SR objects' information was displayed as applicable. Upload the snapshot(s) as the results for this test.


Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Image Display Test 20643: Evidence Display – Stress Test – Vendor Interoperability

References

Instructions

Test 20643 tests the display of SR objects created by other vendors. Every Evidence Creator which supports the Stress Test Evidence option will submit sample objects. Each of these must be tested and properly displayed.

MESA: No MESA software required.

Task Verify
C-Store and Display every (all) Stress Test Evidence SR objects which are submitted by Evidence Creator vendors for test 20643 Visually verify that, in some reasonable format, the template data is displayed.

Instructions

  1. Find SRs uploaded by other vendors for test 20643 in kudu under MESA Tests -> Pre-Connectathon...Objects. This page will evolve as vendors add samples, so be patient.
  2. Retrieve the files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create a word file using the document naming convention of: YourCompanyName_YourProduct_ 20643_ID__n.doc , where n is any number to that you make up to differentiate the files if your company has submitted multiple objects.
  1. Using any tool, cut and paste in a screen snapshot from your own product which demonstrates that the Vendor-created DICOM SR objects' information was displayed as applicable. Upload the snapshot(s) as the results for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Stress Testing Workflow Profile (STRESS) Tests

Test Case 20730: Stress - SCU Query Keys

This test is not yet implemented in the MESA tools.

In this test, the Image Display is required to query the MESA Image Manager using specific matching keys. For each matching key and value in the table below, direct the Image Display to make one or more queries of the MESA Image Manager. Repeat or multiple queries are allowed. That is, you might choose to query several times with a certain matching key. We do not expect the Image Display to send individual queries with multiple matching keys (Patient Name and Patient ID), but the test software will allow that.

Attribute Name Tag Matching Key Value
Study Date 0008 0020 20050830
Accession Number 0008 0050 20730
Patient Name 0010 0010 Barkley*
Patient ID 0010 0020 311
Modalities in Study 0008 0061 ECG


References

Instructions

1. Start the MESA servers as described in section Starting the MESA Servers.

2. Load the data sets into the MESA Image Manager. From $MESA_TARGET/mesa_tests/card/actors/imgdisp

   perl 20730/load_img_mgr.pl

3. Send at least one DICOM Study Level C-Find request (Study Root model) to the MESA Image Manager for each attribute/matching key value defined in the table above.

Evaluation

1. Run the evaluation script to verify that each attribute was requested in a query.

   perl 20730/eval_20730.pl <AE Title of  Image Display>

Supplemental Information

Results will be found in the file 20730/grade_20730.txt. If you need to clear the existing queries to run the test again, you can restart at step 3 or run this script:

Test Case 20740: Stress ECG –Vendor Interoperability

Test 20750 tests the display of DICOM objects created by Evidence Creators and Acquisition Modality actors which support the Stress ECG, Stress Echo or Nuclear Medicine options in the Stress profile. Import the objects which match the option your Image Display supports. Every vendors' objects submitted must be tested and properly displayed.

Image Displays which support the (required) STRESS ECG option must support all of these SOP classes:

1.2.840.1000.5.1.4.1.1.9.1.1 12-Lead ECG Waveform

1.2.840.1000.5.1.4.1.1.9.1.2 General ECG Waveform

1.2.840.1000.5.1.4.1.1.88.22 Enhanced SR

1.2.840.1000.5.1.4.1.1.88.33 Comprehensive SR

1.2.840.1000.5.1.4.1.1.88.40 Procedure Log

1.2.840.1000.5.1.4.1.1.104 1 Encapsulated PDF

No MESA software is required for this test.

References

CARD TF-2:4.4.4

CARD TF-2:4.4.4.1

Instructions

1. Download the participant-supplied datasets for this test. These are found in gazelle under Connectathon-->List of samples

2. Render the studies according to requirements in the Technical Framework.

3. Create a text file which lists the available samples and a note for each indicating whether you were able to successfully render them. If not, detail the problem. Upload that file as the result log for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.


Supplemental Information

The goal of this test is to make sure your system can render the datasets produced by other systems. This also serves as a test of those objects.

Eye Care Domain Tests

The tests in this section apply to Image Display actors in the Eye Care Workflow Profile.

Test 281: Example Images and other DICOM objects

In this test, Image Displays will examine the DICOM samples provided by other participants. The goal of the test is to make sure the Image Display actors are not surprised by content when they arrive at a Connectathon.

Instructions

  1. Find sample images submitted onto ftp.aao.org; contact the project manager for login/password). Contact the connectathon manager to obtain the username/password. The contents will evolve as vendors add samples, so be patient.
  2. Retrieve the DICOM or zip files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. 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 test.
  4. If you find issues with the images, send an email to the Connectathon Project Manager.
  5. The goal is no surprises.

Evaluation

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.

50501: Eye Care Image SCU Query Keys

In this test, the Image Display is required to query the MESA Image Manager using specific matching keys. For each matching key and value in the table below, direct the Image Display to make one or more queries of the MESA Image Manager. Repeat or multiple queries are allowed. That is, you might choose to query several times with a certain matching key. We do not expect the Image Display to send individual queries with multiple matching keys (Patient Name and Patient ID), but the test software will allow that.

Attribute Name Tag Matching Key Value
Study Date 0008 0020 20050830
Accession Number 0008 0050 50501
Patient Name 0010 0010 Barkley*
Patient ID 0010 0020 311
Modalities in Study 0008 0061 OP


References

Instructions

1. Start the MESA servers as described in section Starting the MESA Servers.

2. Load the data sets into the MESA Image Manager.

   perl 50501/load_img_mgr.pl

3. Send at least one DICOM Study Level C-Find request (Study Root model) to the MESA Image Manager for each attribute/matching key value defined in the table above.

Evaluation

1. Run the evaluation script to verify that each attribute was requested in a query.

   perl 50501/eval_50501.pl <AE Title of  Image Display>

Supplemental Information

Results will be found in the file 50501/grade_50501.txt. If you need to clear the existing queries to run the test again, you can restart at step 3 or run this script:

     perl  scripts/clear_img_mgr_queries.pl


50502: Eye Care SCU Query Evaluation

This test uses the queries sent by the Image Display during Test 50501 and any other queries you want to evaluate. This test examines all queries sent by the Image Display to determine if they are legal DICOM queries.

After you conclude Test 50501, the MESA Image Manager will still have a record of the queries sent by your Image Display. If you want to send more queries to the Image Manager, you may do so. There are no required queries. You might want to send queries at the Series and SOP Instance level.

References

Instructions

Evaluation

Evaluate the Image Display queries as follows:

    perl  50502/eval_50502.pl <log level>

Supplemental Information

Query results are stored in the file 50502/grade_50502.txt. As above, you can clear the queries stored by the MESA Image Manager as follows:

    perl scripts/clear_img_mgr_queries.pl


Test 50216: ECED Example Evidence Document

In this test, Image Displays will examine the sample evidence documents provided by other participants. The goal of the test is to make sure the Image Display actors are not surprised by content when they arrive at a Connectathon.

References

Instructions

  1. Look for samples on the AAO ftp site. If you do not know the URL or login/password, contact the Project Manager.
  2. Retrieve the zip files created by the other vendors. Examine/import/render them so that you are confident your software understands the content.
  3. Create a word file using the document naming convention of: YourCompanyName_YourProduct_50216_ID__n.doc , where n is any number to that you make up to differentiate the files if your company has submitted multiple objects.
  1. Using any tool, cut and paste in a screen snapshot from your own product which demonstrates that the Vendor-created DICOM SR objects' information was displayed as applicable. Upload the snapshot(s) as the results for this test.

Evaluation

The evaluation of this test comes in the form of feedback you give to the creators of the data. If you find issues in displaying the studies, you will be asked to work with those vendors (and the Project Manager) to resolve those issues.

  1. If you find issues with the samples, send an email to the Project Manager. You can also contact the Evidence Creator vendor directly to resolve issues.
  2. The goal is no surprises.

Evaluation

The evaluation is represented in the feedback you provide - to make sure you made a good faith effort to review the sample reports.

Supplemental Information

Personal tools