<H3>Special Instructions</H3>  <p>This test applies to the SPD option. The option requires a DOC to query a DOF using the PCD-02 transactions. Then the sending DOF transmits, and the receiving DOC acquires, messages using the PCD-01 transactions. </p>  <p>This test applies to a</p> <ul> <li>DOF (as part of a DOR/DOF system and as a Standalone DOF) </li> <li>DOC that supports the SPD option. </li> </ul>  <p>Standalone DOFs must arrange for a DOR for data input. A Standalone DOF is a device/system that is not part of the device/system that contains the DOR, and that relies upon a separate DOR for patient data. </p>  <p>This test includes: </p> <ul> <li>Subscription for, and transmission of filtered data, filtering by location, </li> <li>Subscription for, and transmission of filtered data, filtering by MRN, </li> <li>Subscription for, and transmission of a snapshot of data, </li> <li>Subscription for parameters not in the system, </li> <li>Subscription for a patient (MRN) not in the system, and</li> <li>Subscription for a patient by location. </li> </ul>  <p>Data from the DOF should contain at least two parameters for each type of device the DOF system supports (e.g., bedside monitor with multiple parameters, infusion pump, VSM, NIBP).  If, for example, a system supports bedside monitors and ventilators, messages will contain 2 different parameters for parameter types within the bedside monitor (heart rate, invasive blood pressure, etc.) and for the ventilator. Parameters for each patient should differ in some easily recognizable way. </p>  <H3>Description</H3> <p>A DOC sends requests (subscriptions) for data filtered as described abpve. The DOF is not required to respond when the query is for parameters that are not supported. If it does respond it will be as agreed to by the partner systems since this is out of scope of the profile. </p>  <p>The 'failed' subscription is followed with another subscription that can be met. This shows that the systems continue to function without any difficulty. </p>  <p>For data that can be supplied, the DOF sends a sufficient number of messages for each of the patients specified in the query to document successful transmission and receipt of the data. If the DOF supports both validated and unvalidated data, this test is performed with unvalidated data. Each message may include any number of additional parameters. </p>  <p>Parameter values should be realistic for a patient in a cardiac ICU bed or on an OR table. </p>  <p>When messages are sent for multiple patients the patients will be interleaved in some manner. I.e., a sufficient number of messages is sent for each patient to see that the DOR and DOC are capable of supporting multiple patients at the same time. Messages should not be closer in time than 30 seconds apart. </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>  <u>Patient Demographics</u> Refer to the PCD_Patient_Demographics table and select two appropriate patients. </p>  <p>Developers are responsible for coordinating with their partners in advance of the Connectathon to assure that they will have the required number of partner systems that support the same physiologic or other parameters, with consistent coding. </p>  <H3>Evaluation</H3> <p>Project manager or monitor will observe the displays provided by the sending and receiving system(s). The patients' names and/or medical record numbers (MRNs), physiologic and other parameters, their measurement values, and the time of parameter measurement/acquisition will be compared. The type of display/documentation by the receiving system is not constrained, it need only be clinically useful. </p>  <p>NOTE: If other tests are conducted with this test, they will evaluated as described for those tests and the evaluation will be recorded for those tests. </p>   