<H3>Special Instructions</H3><p> <p>DEC_Validated_Data_RC is defined in the context of DOR/DOC pairs where the DOR and/or the DOC supports validated messages or both validated and unvalidated messages. It also tests DOFs to verify that they do not fail or compromise the validation indicator when transmitting validation flags. Validation means the caregiver has reviewed the results. </p> <ul> <li> If the DOR is capable of sending only unvalidated data do not perform this test. </li> <li> If no DOC capable of distinguishing validated from unvalidated data is available, do not perform this test. </li> <li> If the DOR is capable of sending validated data this test evaluates its ability to send messages containing the validation flag and to support a DOC that can distinguish the validation flag. If the DOR is capable of only sending validated messages this test may be combined with the DEC_One_to_One_Communication test. </li> </ul> <p>NOTE: A DOC must succeed in accepting data with or without the validation flag. A DOC capable of distinguishing validated/unvalidated data should test against at least one DOR that sends validated messages and be able to identify whether the validation is entered/not validated, or final. It may also distinguish among other values for the flag. </p> <p>NOTE: This test can be coordinated with the One to One Communication test.</p> <p>NOTE: This test need be performed only once for DORs and for DOCs that support validated messages. These systems, however, may be asked to conduct the test multiple times to satisfy other partners&rsquo; needs for testing. </p> <p>There are three variations of this test; be sure you select the right one:</p> <ul> <li>DEC_ Validated _RC</li> <ul> <li>DOR and DOC; the DOR and the DOC have succeeded with DEC_One_to_One_Communication </li> </ul> <li>DEC_ Validated _FC</li> <ul> <li>DOR and DOF are contained in the same system; the DOR and DOC have succeeded with DEC_One_to_One_Communication </li> </ul> <li>DEC_SPD_ Validated _RFC</li> <ul> <li>Standalone DOF, input to the DOF requires the DOF to act as a DOC, and will need a DOR as partner; the DOF has previously succeeded in testing as a DOC with a DOR to assure it can receive PCD-01 messages.</li> </ul> </ul> <p>NOTE: Test names are the same for all systems. They play partner roles. Developers of sending systems are responsible for coordinating with their partners <em>in advance of the Connectathon</em> to assure that the receiving systems are able to receive <em>and preferably distinguish, validation of </em>at least the minimum three physiologic parameters required for this test. Parameter values should be realistic for a patient in a cardiac ICU bed or on an OR table. </p> </p><H3>Description</H3><p>Conduct DEC_One_to_One_Communication before proceeding.</p><p>DORs will send, and DOCs will receive physiologic parameters for any patient in a previous test. DOR will send validated data to a DOC that can distinguish validated data from unvalidated data. </p><p>NOTE: This test need be conducted only once to verify the ability to send or receive validated data.</p><H3>Evaluation</H3><p>Project manager or monitor will observe the displays provided by the sending system and partner. The physiologic parameters and their measurement values, including the time of parameter measurement will be compared. The type of display/documentation by the receiving system is not constrained, it need only be clinically useful.</p><p>Success: For the DOR, if there is evidence that validated data was sent, and for the DOC that validation was distinguished, and the patient, measurements and time of measurement sent matches those received, will indicate the test has been successful. </p> 