<H3>Special Instructions</H3> <p>This test addresses the ability of a DOF to function and identify a patient when the PIB option (using PAM and/or PDQ) fails to provide patient demographic information for a patient. The DOF provides a secondary way to identify the patient and link that identification with the patient's physiologic data.  </p>  <p> If the DOF is a standalone system, this test is appropriate. If the DOF is part of a DOR/DOF system, it is necessary to test only the DOR version of this test (DEC PIB Unsuccessful Identification). 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> <H4>A standalone DOF must find a DOR to assist with this test.  </H4> <p>If both PAM and PDQ options in PIB are supported, this will be accomplished by first attempting to obtain identification with PAM, and then with PDQ. That may be a manual or automatic attempt. </p>  <p><u>Related Tests: </u> Developers may efficiently integrate this test with DEC_DOF_With_PIB_Option and/or the appropriate one to one test: </p> <ul> <li>DEC_One_to_One_Communication_Periodic_Data</li> <li>DEC_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>Conduct the appropriate one-to-one test and the DEC_DOF_With_PIB_Option test before proceeding. </p>  <p>The patient sought has the name Peter Rabbit. This patient's demographics will not be sent in PAM messages, nor will it be in the ADT system's database. </p>  <p>For PAM, this patient won't be in the DOR's database. For PDQ, query all as appropriate: </p> <ul> <li>Query by name. </li> <li>Query with location SICU room 1, bed 1. </li> <li>Query with MRN 1234. </li> </ul>   <p>When the attempt to identify the patient fails, the DOR may use any method it supports to provide sufficient patient identification to send three messages (or only one if the DOR or DOF supports data from devices sending only infrequent data). For example, if a hospital assigns temporary patient identification using the hospital name and a number (e.g., hospital name_sequential number), the DOR could use as temporary MRN: Hospital_DOR Name n, where Hospital is the facility identifier, DOR Name is the manufacturer's name or DOR's identification, followed by the number 1. </p>  <p>The user selects or validates the patient identification obtained and the DOR or DOF incorporates the patient identity into the messages transmitted to the DOC or DOF. </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 the system provides both periodic and infrequent data, there is no need to send the infrequent data. </li> <li>If the DOR supports both validated and unvalidated data, this test is performed with unvalidated data. </li> </ul>   <p>The sequence of messages is not important. </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>     <p>For PAM, this patient won't be in the DOR's database. For PDQ, query all as appropriate: </p> <ul> <li>Query by name. </li> <li>Query with location SICU room 1, bed 1. </li> <li>Query with MRN 1234. </li> </ul>   <p>When the attempt to identify the patient fails, the DOR may use any method it supports to provide sufficient patient identification to send three messages (or only one if the DOR or DOF supports data from devices sending only infrequent data). For example, if a hospital assigns temporary patient identification using the hospital name and a number (e.g., hospital name_sequential number), the DOR could use as temporary MRN: Hospital_DOR Name n, where Hospital is the facility identifier, DOR Name is the manufacturer's name or DOR's identification, followed by the number 1. </p>  <p>The user selects or validates the patient identification obtained and the DOR or DOF incorporates the patient identity into the messages transmitted to the DOC or DOF. </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 the system provides both periodic and infrequent data, there is no need to send the infrequent data. </li> <li>If the DOR supports both validated and unvalidated data, this test is performed with unvalidated data. </li> </ul>   <p>The sequence of messages is not important. </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> 