<H3>Special Instructions</H3> <p>Image Display please use the <em><a href=system_con_object.php>Objects Information</a></em> page to find out what your peers have uploaded on the central archive </p> <H3>Description</H3> The NMI_EC_Display test is used to determine if the NM Evidence Creator is entering the proper data in the DICOM NM images and to determine if the Image Display is rendering the images properly.  <p> Evidence Creators in the NMI profile create derivitive data from original NM image data.  In this test, the Evidence Creator must perform all of the functions it is capable of, which may include: </p> <ul> <li>Reconstruction, reorientation, filtering, or other processing of NM data, with output of NM modality image objects.  <li>Registration between an NM data set and another data set.  </ul> Evidence Creator actors have the same requirements as Acquisition Modalities for attributes which must be included in the DICOM header.  See RAD TF-2:4.8.4.1.2.2. or the Evaluation section for test NMI_MOD_Store. <p> The Evidence Creator should use the images produced in the NMI_MOD_Store as data for this test. The Evidence Creator should ask a modality to push images directly to it or to retrieve images from the Central Archive. Only data for a Myocardial Perfusion Study are necessary </p>  <H3>Evaluation</H3>  <p>Connectathon Monitors will use the Image Display to dump DICOM headers and to display images. If the Image Display cannot dump the DICOM header, we will find another method to check attribute values. <ul>  <li>E47: Check standard tags and datatypes. Are R and R+ tags present in the dataset?</li>  <li>E48: Can the cardiac processing package pick out the stress and rest files using the DICOM tages in the files, without using the series description.  (Note:  this step is likely to require pre-prepared data in which the DICOM tags and series descriptions are mutually contradictory; otherwise it may not be possible to test.)</li>  <li>E49: Short short axis data is created, does it have both the apex to base tag and the short axis tag?</li>  <li>E50: When inputting data, does the software distinguish between short axis and transaxial data by the presence or absence of the short axis tag, and does it use this tag and the apex to base tag to process data appropriately?   [To test this in a complete manner, we may need to manuallly change the tags, and verify that it changes the way the data appears in the processing program]. <(Note:  this step is likely to require pre-prepared data in which the DICOM tags and series descriptions are mutually contradictory; otherwise it may not be possible to test.)/li>  <li>E51: Ask workstation to display all data produced by Evidence Creator. Use analysis similar to that determined for modality.</li> </ul> </p>