<H3>Special Instructions</H3>  <p>This test addresses the ability of a DOR (or DOF) to integrate patient demographic information from an ADT system with physiologic data. This test provides data for two patients. If the system only supports one patient, document this. If the system does not utilize the PIB option, do not conduct this test. </p>  <p>If both PAM and PDQ options are supported, this test will be accomplished with one patient identified via the system's database of prior PAM transmissions and the other via a query. If the DOR supports only PAM or PDQ, both patients will be identified using the only appropriate option. PAM or PDQ qualifying tests, if any, should be performed first. </p>  <p>The user selects or validates the patient identification obtained and the sending system incorporates the patient identity into the messages transmitted to a DOC. </p>  <p>This test applies to a</p> <ul> <li>DOR and a DOC</li> <li>DOF within the same system as a DOR and a DOC </li> <li>Standalone DOF when it needs ADT support, and a DOC</li> </li> </ul>   <p><u>Related Tests: </u> Developers may efficiently integrate this test with DEC_PIB_Unsuccessful_Identification and the appropriate one to one test: </p> <ul> <li>DEC_DOR_DOC_One_to_One_Communication_Periodic_Data</li> <li>DEC_DOR_DOC_One_to_One_Communication_Infrequent_Data  (data such as infusion pumps, NIBP devices or channels and beds) </li> </li> </ul>   <p>NOTE: While these test names include DOR and DOC, they apply to DOFs as well. </p>  <H3>Description</H3> <p>DORs (and DOFs) will send, and DOCs (and standalone DOFs) will receive physiologic and/or operational  parameters for two patients. If your system does not support multiple patients you need to make this known to your test partners and the project manager. </p>  <p>Read the appropriate one-to-one test before proceeding. If this test is combined with that one, please follow the requirements for that test where those requirements differ from the following. </p>  <p>Sending systems will send at least three messages for each patient with reasonable values for four parameters assuming the patient is in an ICU or OR.  </p> <ul> <li>If the system only supports infrequent data (e.g., Vital Signs Monitor (VSM) or Non-Invasive Blood Pressure (NIBP) data then it will send two messages for at least two patients, with some change in parameter values in the second set of messages for each patient. </li> <li>If infrequent data is included with other data, the VSM or NIBP monitor need only send one message with one or more patients' data. </li> <li>If the DOR supports both validated and unvalidated data, this test is performed with unvalidated data. </li>  </li> </ul>   <p>The sequence of messages is not important if this test is not combined with a one-to-one test. </p>  <p>Parameter values should be realistic for a patient in a cardiac ICU bed or on an OR table. </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> <p>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> 