<H3>Special Instructions</H3><p> <p>Report Managers run one instance of this test.</p> <p>In this test you will capture sample messages you will create for the Monitor to evaluate.  Report Manager will upload a sample MDM, and a copy of the PDF, into kudu under <b>Connectathon --> Connectathon...Objects</b> <p>The Report Manager must solicit the help of a Report Creator  to submit one report to the Report Manager.</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> <p>    If your Report Manager supports the DICOM Storage option (ie  is not grouped with a Report Repository), after completing this test, you  should immediately proceed to run test <strong>DRPT_RM_Mapping_DICOM_Option.</strong> </p> </p> <H3>Description</H3> <p>This test verifies that the Report Manager is submitting valid PDF/A documents encapsulated in    a properly-formatted MDM message using the CARD-7 transaction. The Report Manager's    ability to change the status of a report is tested in another test.</p>  <H3>Evaluation</H3> <p>You will find the samples from this system in kudu under <b>Connectathon --> Connectathon...objects</b></p> <p>It will be more efficient if you do the evaluation of test    <strong>DRPT_RM_Submission_Scrutiny</strong> and <strong>DRPT_RM_Mapping_DICOM_Option</strong> at    the same time for one Report Manager system.  Note, however, that if a Report Manager    does not support the <strong>DICOM Storage</strong> option, it is not required to run test     <strong>DRPT_RM_Mapping_DICOM_Option.</strong> </p> <p>The Connectathon Monitor will inspect the MDM message    submitted by the Report Manager into Kudu under <b>Connectathon --> Connectathon...Objects</b>  Patient name should be:     <em>RMs-kudu-system-name^SCRUTINY</em>. </p>  <p>Verify: </p><ol start="1" type="1">     <li>The encapsulated document is valid PDF/A (tool needed).</li>     <li>MSH Segment - required fields:</li> </ol><ol start="1" type="1">     <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.   Value:  MDM^T02</li>      <li>MSH-10               Message Control</li>      <li>MSH-11               Processing ID</li>      <li>MSH-12               Version ID</li>     </ul> </ol><ol start="3" type="1">     <li>EVN Segment - required fields:</li> </ol><ol start="1" type="1">     <ul type="disc">      <li>EVN-2                      Recorded Date/Time</li>     </ul> </ol>   <ol start="4" type="1">     <li>PID Segment - required fields:</li> </ol><ol start="1" type="1">     <ul type="disc">      <li>PID-3                        Patient Identifier List</li>      <li>PID-5                   Patient Name</li>     </ul> </ol><ol start="5" type="1">    <li>PV1 Segment - required fields:</li> </ol>  <ol start="1" type="1">     <ul type="disc">      <li>PV1-2                        Patient Class </li>     </ul> </ol>  <ol start="6" type="1">     <li>ORC Segment - required fields:</li> </ol><ol start="1" type="1">     <ul type="disc">      <li>ORC-1                             Order Control</li>      <li>ORC-2                             Placer Order Number (if the value of Assigning Authority indicates that the Placer Order number      was generated by the Report Creator, the Report Manager must be able to replace it with an      identifier supplied by the Order Placer ) </li>      <li>ORC-3                             Filler Order Number (if the value of Assigning Authority indicates that the Filler Order number      was generated by the Report Creator, the Report Manager must be able to replace it with an      identifier supplied by the Order Filler )</li>     </ul> </ol>  <ol start="7" type="1">     <li>OBR Segment - required fields:</li> </ol>  <ol start="1" type="1">     <ul type="disc">      <li>OBR-1                             Set ID</li>      <li>OBR-2                             Placer Order Number Placer Order Number (if the value of Assigning Authority indicates that the      Placer Order number was generated by the Report Creator, the Report Manager must be able to      replace it with an identifier supplied by the Order Placer )</li>      <li>OBR-3                             Filler Order Number (if the value of Assigning Authority indicates that the Filler Order number      was generated by the Report Creator, the Report Manager must be able to replace it with an      identifier supplied by the Order Filler )</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> </ol>  <ol start="8" type="1">     <li>TXA Segment - required fields:</li> </ol><ol start="1" type="1">     <ul type="disc">      <li>TXA-1                  Set ID</li>      <li>TXA-2                  Document Type</li>      <li>TXA-12                Unique Document Number</li>      <li>TXA-14                Placer Order Number (if the value of Assigning Authority indicates that the Placer Order number      was generated by the Report Creator, the Report Manager must be able to replace it with an      identifier supplied by the Order Placer )</li>      <li>TXA-15                Filler Order Number (if the value of Assigning Authority indicates that the Filler Order number      was generated by the Report Creator, the Report Manager must be able to replace it with an      identifier supplied by the Order Filler )</li>      <li>TXA-17                     Document Completion Status.  Value must be one of:  PA, AU, LA</li>      <li>TXA-22                Authentication Person, Time Stamp</li>     </ul> </ol>  <ol start="9" type="1">     <li>      <em>NOTE:  This segment is optional in the msg sent by the RM.<br> OBX Segment for      Study Instance UID – required fields:</em>     </li> </ol>  <ol start="1" type="1">     <ul type="disc">      <li>       <em>OBX-1                   Set ID</em>      </li>      <li>       <em>OBX-2                   Value Type = HD</em>      </li>      <li>       <em>OBX-3                   Observation Identifier.  Value is 113014^DICOM Study^DCM</em>      </li>      <li>       <em>OBX-5                   Observation Value.  Value shall include the Study Instance UID as an ISO OID</em>      </li>      <li>       <em>OBX-11                 Observation Result Status.  Value must be:</em>      </li>     </ul> </ol>  <ol start="10" type="1">     <li>OBX Segment for the Encapsulated Report - required fields:</li> </ol>  <ol start="1" type="1">     <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>  <ul>     <li>      <em>Note:  Additional OBX segments may be present</em>     </li> </ul> 