<H3>Special Instructions</H3> <p>This test is provided to minimize the risk of a failure during a Showcase. The test is successful if no system fails, and it provides some information about the behavior of the IOP/IOC/Pump system under two conditions: </p> <ol>  <li>Loss of communication/power interruption at the pump</li> <li>Loss of communication/power interruption at the IOC</li>  </ol>  <p>This test is out of scope of the PIV profile, and therefore any behavior consistent with the design of the systems is acceptable as long as no system fails to operate following the loss of communications. </p>  For this test, Clinician uses a BCMA to initiate PCD-03 transactions consistent with the steps provided below. Vendors will document when the pump is off or on, when the IOC is available, and when it is not. </p>  Clinician uses the BCMA Programmer to enter patient and pump identification and to identify the drug, its concentration, and volume to be delivered. </p>  <H3>Description</H3>  <p>Developer prepares the BCMA Programmer to provide patient and pump identification and to identify the drug and the delivery parameters. Patient demographics are developed as described in the Kudu test page PCD_Patient_Demographics. Specific drug and parameters are given in the Kudu test page PIV_Parameter_Tables, http://ihe-kudu.wustl.edu/na2009/connectathon_test.php.  </p>    <p>The test includes these major components: </p> <ol>  <li>The pump is turned off or power is removed at the beginning of the test sequence. The IOP and IOC are available when the message is sent. If the clinician was to receive a confirmation message or error message that is documented. </li> <li>The pump is turned on/power is restored and the systems work as intended. If the system recognizes that the pump didn't receive the requested instructions and these are sent again, this is documented. IOP either retransmits existing request(s) or clinician must initiate new request or clinician must take some other action. </li> <li>The IOC is then turned off and a message is sent. The IOP times out at the network level. If the clinician was to receive a confirmation message or error message that is documented. </li> <li>The IOC is turned on and the behavior is documented. If the system recognizes that the IOC didn't receive the requested instructions and these are sent again, this is documented. IOP either retransmits existing request(s) or clinician must initiate new request or clinician must take some other action. </li> The complete system should function as designed with all components active. </li>  </ol>  <p>The pump should run long enough to make it obvious that some fluid was delivered. If the IOP and IOC implement the DEC PCD-01 profile, that data may be used to help document what happened. </p>  <p>Parameters should be sent from actual devices (preferred), simulators or, if necessary from parameter tables provided by the Project Manager (least desirable). </p>  <H3>Evaluation</H3> <p>Monitor will preferably observe the sequence of events, the resilience of the systems and the ability of the design and clinician actions that lead to successful delivery of the medication. </p> 