<H3>Special Instructions</H3> <p>None</p> <H3>Description</H3> <p>The purpose of the CPI_Archive test is for all creators of GSPS objects (Modalities, Evidence Creators) to create those objects and to store those on the Central Archive. The creator of the GSPS object should also store all of the images of the study to which the GSPS object pertains.</p> <p>In order to identify the creator of the object, it would be most beneficial if the Patient Name chosen reflected the company/product of the system creating the object. This is relatively easy for Modalities as they create the original images. This may take more imagination by Evidence Creators as they typically do not create the original images.</p> <p>By having the company/product name in the Patient Name field, other tests will be much easier to perform.</p> <p>The GSPS objects and images sent by the Evidence Creator should be of the same genre as those normally generated by the Evidence Creator during expected clinical use.  To insure adequate testing of capabilities, the set of GSPS objects should include at least 15 elements drawn from the following GSPS capabilities:</p> <ol> <li>a selection of display area (i.e., zoom)</li> <li>a spatial transformation (rotation and/or flip)</li> <li>a discernable adjustment to the Modality LUT, if appropriate to the image object</li> <li>a discernable adjustment to the VOI LUT</li> <li>a discernable adjustment to the Presentation LUT</li> <li>a setting of display shutters (extra worthless brownie points to people who do bitmap shutters)</li> <li>text annotation boxes</li> <li>an anchor line associating a text box located in display coordinates with an anchor point in image coordinates</li> <li>graphical objects in image coordinates</li> <li>graphical objects in screen coordinates</li> <li>specification of multiple graphical layers with different suggested colors</li> <li>frame selection, if the associated image object is multi-frame</li> <li>specification of mask and contrast frames for subtraction, if appropriate for the image object</li> <li>a bitmap overlay</li> </ol> <p>As all images/GSPS objects are stored to one Central Archive run this test one time, <strong>preferably on the first day of the connectathon</strong> so that others can test with your data during the rest of the connectathon.  The creator of the GSPS objects should present the Project Manager with a printed version of how the final image rendering should appear.  This should include both a list of the included 15 or more GSPS elements, and an image or description of how they should appear on the screen.  An actual printout of the image rendered correctly with the GSPS on a calibrated printer would be ideal, but barring that, any type of screen shot, or even a shot of the screen taken by a digital camera would be acceptable.</p> <p>Make sure that you upload a description of the GSPS object in the <em><a href=system_con_object.php?selected=create_object>Objects Information</a></em>.  Please upload there a screen capture of the object so that we can use it for comparison when your peers will render your objects.</p> <H3>Evaluation</H3> <p>In order to validate the test, the connectathon monitor will check:</p> <ul> <li>that the objects are stored on the Central Archive,</li> <li>that there is a corresponding entry in the <em><a href=system_con_object.php?selected=create_object>Objects Information</a></em>  section of the kudu webtool, and </li> <li>that there is a screen capture of the objects uploaded in the <em><a href=system_con_object.php?selected=create_object>Objects Information</a></em> section of the kudu webtool, and</li> <li>that the printed output adequately describes the displayed image.</li> </ul> <p>Note that samples stored to the Central Archive are checked by a DICOM validator.</p>