<H3>Special Instructions</H3> <ul> <li>More than Acquisition Modality may participate in this test, eg an hemodynamic system and cath modality.   In this test, the term 'Modality' refers to any acquisition device in the cath lab. <li>Use the RIS Mall to register a patient and create an order (Requested Procedure) for this test. <li>The Modality should be configured to send MPPS to the DSS/OF. <li>The Modality will C-STORE objects in this test, but storage to an Image Manager is not part of the evaluation.  If there is not an available Image Manager to C-STORE to, the Modality should be configured to send its objects to the Connectathon CENTRAL_ARCHIVE. </ul> <H3>Description</H3> This test assumes that at least two modalities will acquire data for a procedure: <ul> <li>Hemodynamics system (typically starts the procedure) <li>Cath modality <li>Potentially an analysis or measurement system <li>EP lab systems:  EP recording system, EP logging system, Mapping system, X-ray angiography/fluoroscopy, intercardiac echo system </ul> <p> One or more of these systems may participate in this test.  If there is only one modality available, <i><u>the DSS/OF will still assume that it will be creating SPSs for the other types of systems.</u></i> </p> <p> In this test, the Modality(ies) and DSS/OF test their interfaces for these actions: <ul> <li>Modality Worklist <li>Multi-modality procedure update by the DSS/OF (CARD TF-1:B.2 and TF-2:4.1.1) <li>The Patient Not Registered / Unscheduled Case C5 (Card TF-1:3.4.5, Rad TF-2:4.6.4.1.2.3.2 and Table A.1-2) </ul> Note that the ability of the DSS/OF to forward MPPS messages as a PPS Manager is not exercised in this test. </p> <H3>Evaluation</H3> Connectathon Monitor will ask the <b>Acquistion Modality</b> and/or <b>Hemodynamic system</b> to show evidence that:  <ul> <li>it supports Broad MWL queries.  The Modality operator should demonstrate on its user interface the ability to query by combination of SPS Start Date, Modality type, Scheduled AE title. <li>In the Unscheduled Case, the MPPS message sent by the Modality (captured on the DSS/OF) contains: <ul> <li>(0010,0010) Temporary Patient ID created by the Modality (Patient ID reconciliation is not evaluated in this test) <li>(0020,000D) Study Instance UID created by the Modality.   (See characteristics of UIDs below.)  <li>(0008, 1032) Procedure Code Sequence is empty <li>In (0040,0270) - Scheduled Step Attributes Sequence, the following attributes are empty (zero-length): <ul> <li> (0008,1110) Referenced Study Sequence <li>(0008,0050) Accession Number <li> (0032,1060) RP Description <li> (0040,1001) Requested Procedure ID  <li> (0040,0007) SPS Description <li> (0040,0008) Scheduled Procedure Code Sequence <li>(0040,0009) SPS ID </ul> </ul> </ul> <p>Connectathon Monitor will ask the <b>DSS/OF </b>to show evidence that: </p> <ul> <li>It properly supports MULTI-MODALITY PROCEDURE UPDATE.  After it received the first PPS In Progress Message it creates SPSs for each modality in the procedure.  The MWL provided to all modalities in the cath lab contain the SAME Study Instance UID.   <p> In the first Scheduled Case, it is the Study Instance UID generated by the DSS/OF. </p> In the Unscheduled Case, it is the Study Instance UID generated by the Modality whiich started the procedure. </p> <li>It creates valid DICOM Study Instance UIDs (0020,000D): <ul> <li>UIDs should not be longer than 64 chars, <li>should not contain leading zeroes in a non-zero component,  <li>should not end with a "." or a space character (no space padding for UIDs!)  <li>in general should start with "1.2", "1.3" or "2.16" (other roots are theoretically possible but very unlikely to be legal). </ul> </ul> 