<H3>Special Instructions</H3> <ul> <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 images 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> In this test, the Modality and DSS/OF test their interfaces for these actions: <ul>  <li>Modality Worklist <li>The Unscheduled Case E4 - Intermittently Connected Modality with Ad Hoc Procedure, Patient Registered, Unscheduled Procedure (CARD TF-1: 4.3.3; 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. <H3>Evaluation</H3> Connectathon Monitor will ask the<b> Acquistion Modality</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  <li>(0008, 1032) Procedure Code Sequence is empty <li>In (0040,0270) - Scheduled Step Attributes Sequence, the following  <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> Connectathon Monitor will ask the <b>DSS/OF</b> to show evidence that: <ul> <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> <li>a RP/SPS has been created for this procedure using the modality-provided Study Instance UID received in the MPPS. </ul>   