<H3>Special Instructions</H3> In order to run that test the Data Manager needs :  <ul> <li>A friendly Order Placer </li> <li>Some way to have the observation entered in the POCDM actor : Using observations from a friendly POCRG is a solution. Other solution might be to use a simulator</li> </ul> <H3>Description</H3> The purpose of this test is to test the LAB-32 transaction between the Data Manager actor and the Order Filler. There are 2 cases to test in this test : <ol> <li>Unordered observation : in this case the Order Filler needs to return an order number</li> <li>New observation : in this case the Order Filler needs to search in its record for an order that matches the criteria found in the observation provided in ORU^R31 message</li> </ol> <H3>Evaluation</H3> <ol> <li>Unordered Observation <ul> <li>Check that the message send from the POCDM to the OF is of type ORU^R30</li> <ll>Use the proxy, and check the validation of the message by the Gazelle HL7 External Validation Service tool</li> <li>Check that the OF generates a new filler order number and provides it correctly to the POCDM (the value is provided in the ACK^R33 message at MSA.3</li> <li>Check that the ORU^R30 triggers a LAB-2 message (From the OF to the OP). The purpose of this message is for the OF to request the OP an Placer Order number. It is understood that the OP is not part of this test and that the OP may not provide any response. We are checking here the "TRIGGERING" of the LAB-2 message. The integration with the LAB-2 message will be tested in the group test.</li> <li>In case we actually have an OP acting in this test, check that the Placer Order Number is correctly stored in the OF database.</li> </ul> </li> <li>New observation  <ul> <li>Check that the message send from the POCDM to the OF is of type ORU^R31</li> <li>Use the proxy, and check the validation of the message by the Gazelle HL7 External Validation Service tool</li> <li>Check that the Order Filler tries to match an existing order in its data base, corresponding to this set of observations. The criteria used are in the context of the connectathon based only on the Patient. (Note that this are relaxed policies. In the real life the criteria, which are depending on site-defined policies, may be more complex.) </li> <li>In case no order can be matched in the Order Filler data base : Please check the evaluation steps of "Unordered Observation"</li> <li>If an order is matched :Check that the ORU^R31 triggers a LAB-1 message. "Order status change" notified by the Order Filler to the Order Placer is the purpose of this message. </li> </ul> </li> </ol>