 <H3>Special Instructions</H3>  <p>Report Creators run one instance of this test.</p>    <p>This test should be done on the first day of the Connectathon. This test in included due to the absence of new MESA tests in the 2007-08 testing season.</p>   <H3>Description</H3> <p>This test verifies that the Report Creator is creating valid PDF/A documents encapsulated in a properly-formatted MDM message.</p>   <H3>Evaluation</H3> <p>The next two items should have been captured by the Report Creator in the kudu chat window. </p>    <p>Verify:</p>  <ol start="1" type="1">   <li>The values for Unique Document Number in TXA-12 is different in the three MDM messages</li>    <li>In the 3nd MDM message for the updated report, TXA-13, Parent Document Number contains the Unique Document Number of the document being replaced (ie the value of TXA-12 in the second (previous message).</li>    </ol>  <p>   The Connectathon Monitor will also manually inspect the MDM messages submitted by the Report Creator.         Patient names should be    <em><RC's-kudu-system-name>^SCRUTINY</em>    and    <em><RC's-kudu-system-name>^FINAL-CORRECT.</em>         For one message, do the complete verification:    </p> <ol start="3" type="1">   <li>The encapsulated document is valid PDF/A (tool needed).</li>    <li>MSH Segment - required fields:</li>  <ul type="disc">   <li>MSH-1            Field Separator</li>    <li>MSH-2            Encoding Characters</li>    <li>MSH-3            Sending Application</li>    <li>MSH-4            Sending Facility</li>    <li>MSH-5            Receiving Application</li>    <li>MSH-6            Receiving Facility</li>    <li>MSH-9            Message Type.</li>  <ul>   <li>Value:  MDM^T02 for patient <RC's-kudu-system-name>^PRELIMINARY</li>    >    <li>Value:  MDM^T10 for the update to final for patient <RC's-kudu-system-name>^FINAL-CORRECT</li>    </ul>   <li>MSH-10          Message Control</li>    <li>MSH-11          Processing ID</li>    <li>MSH-12          Version ID</li>    </ul>   <li>EVN Segment - required fields:</li>  <ul type="disc">   <li>EVN-2            Recorded Date/Time</li>    </ul>   <li>PID Segment - required fields:</li>  <ul type="disc">   <li>PID-3              Patient Identifier List</li>    <li>PID-5              Patient Name</li>    </ul>   <li>EVN Segment - required fields:</li>  <ul type="disc">   <li>PV1-2              Patient Class</li>    </ul>   <li>ORC Segment - required fields:</li>  <ul type="disc">   <li>ORC-1                        Order Control</li>    <li>ORC-2                        Placer Order Number (note that the Assigning Authority sub-component must also be specified; if the Report Creator does not have these identifiers from the actual Placer and Filler systems, it must fill the fields with an identifier that it creates, and identify the assigning authority as itself. )</li>    <li>ORC-3                        Filler Order Number (note that the Assigning Authority sub-component must also be specified; if the Report Creator does not have these identifiers from the actual Placer and Filler systems, it must fill the fields with an identifier that it creates, and identify the assigning authority as itself. )</li>    </ul>   <li>OBR Segment - required fields:</li>  <ul type="disc">   <li>OBR-1                        Set ID</li>    <li>OBR-4                        Universal Service ID</li>    <li>OBR-7                        Observation Date/Time</li>    <li>OBR-25          Result Status.   Value must be one of:  R  P   F  or  C</li>    </ul>   <li>TXA Segment - required fields:</li>  <ul type="disc">   <li>TXA-1             Set ID</li>    <li>TXA-2             Document Type</li>    <li>TXA-12           Unique Document Number – formatted as an OID (64 char limit)</li>  <li>   TXA-13                                                           Parent Document    <em>(this field only exists for the update message for patient</em>    <RC's-kudu-system-name>^FINAL-CORRECT. It contains the value of TXA-12 for this patient's preliminary report.    </li>   <li>TXA-17           Document Completion Status.  Value must be one of:  PA, AU, LA</li>    <li>TXA-22           Authentication Person (TXA-22.2 and/or TXA-22.3 shall be valued),  and Time Stamp (TXA-22.15 shall be valued)</li>    </ul>   <li>OBX Segment for Study Instance UID (included if the report is created for a Requested Procedure managed by a DSS/OF) - required fields:</li>  <ul type="disc">   <li>OBX-1          Set ID</li>    <li>OBX-2          Value Type = HD</li>    <li>OBX-3          Observation Identifier.  Value is 113014^DICOM Study^DCM</li>    <li>OBX-5          Observation Value.  Value shall include the Study Instance UID as an ISO OID</li>    <li>OBX-11          Observation Result Status.  Value must be 'O'</li>    </ul>   <li>OBX Segment for the Encapsulated Report - required fields:</li>  <ul type="disc">   <li>OBX-1        Set ID</li>    <li>OBX-2         Value Type = ED</li>    <li>OBX-3         Observation Identifier.  Shall contain the report title.</li>    <li>OBX-5.2         Type of Data.  Value is 'Application'</li>    <li>OBX-5.3         Subtype.  Value is 'PDF'.</li>    <li>OBX-5.4         Encoding.  Value is 'Base64'.</li>    <li>OBX 5.5         Data.  Value is the Base 64-encoded PDF (in PDF/A format)</li>    <li>OBX-11          Observation Result Status.  Value must be one of:  R  P   F  or  C</li>    </ul>   </ol> 