<H3>Special Instructions</H3> This test is similar to the SWF_ORDERS test case, but only exercises the transactions between an Order Placer and Order Filler.  To exercise the Image Manager transactions, run SWF_ORDERS. <p> Use the RIS Mall as an ADT simulator to register patients. If there is an idle ADT actor that wants to collaborate, you are free to use that system; that ADT system will not be recognized in the test results. </p> <H3>Description</H3> This test verifies the ability of the Order Placer and DSS/Order Filler to exchange order and status information (RAD-TF-1: 3.3.3 and RAD-TF-2: 4.3.4) ' patients are registered; orders are created and cancelled at both the OP and DSS/OF.  <p> <strong>NOTE:</strong>  The following transactions are tested in other test cases and are not verified in detail here, but you could check for the proper exchange of these messages </p> <ul> <li>[RAD-1] ADT notifies OP and DSS/OF of new patient registration. <li>[RAD-12] ADT notifies OP and DSS/OF patient update or merge. </ul> <H3>Evaluation</H3> <p> On the <strong>OP</strong> user interface or database, verify that: </p> <ul> <li>The order for SYS_NAME^SWF-ORDERS1 is cancelled (order number was recorded in the Kudu chat window). <li>There is new order/procedure for patient SYS_NAME^SWF-ORDERS2. </ul> <p> On the <strong>DSS/OF</strong> user interface or database, verify that: </p> <ul> <li>There is no order waiting to be scheduled for patient SYS_NAME^SWF-ORDERS1 (it was cancelled). <li>There is a new procedure for patient SYS_NAME^SWF-ORDERS2. <li>A copy of the ORR message from the OP (transaction RAD-3) has been captured, eg in [test-case-no]-orr-msg.txt.  ORC-2 should contain the Placer Order number recorded at the OP for patient SYS_NAME^SWF-ORDERS2 . </ul>  