<H3>Special Instructions</H3><p> <p>Enterprise Report Repository actors which support the <strong>By-Reference Reports option</strong> must run  this test.</p> <p>    A Report Creator is needed to help with this test by  submitting a report, but is specified as an optional actor in (ie it is not  required to complete 3 instances of this test).</p> </p><H3>Description</H3><p>This test verifies the interaction between the Report Manager and Enterprise Report Repository for submitting references to reports.</p><H3>Evaluation</H3><ol start="1" type="1">     <li>The       Enterprise Report Repository shall demonstrate for the Connectathon       Monitor that the reference to the report for patient <em>RM-kudu-system-name^EntRptRep-kudu-system</em>-<em>name</em> is stored on its system.&nbsp;       This may be done by viewing a database entry, displaying the report       (using the reference), or some other means.</li>     <li>The       Enterprise Report Repository shall demonstrate how its application makes       the report available (via its reference) to other systems in the       enterprise.&nbsp; Making the report       available is a requirement in the Technical Framework; however, the DRPT       profile does not specify how the Enterprise Report Repository must       accomplish this.&nbsp; The Connectathon       Monitor will have to exercise some judgment when assessing this       functionality, but an Enterprise Report Repository which just stores the       report reference (URL) in its database would not pass this test.</li>     <li>Verify       that when the report is accessed, the UPDATED version of the report is       presented.</li>     <li>View a       copy of the MDM^T09 (update) message.&nbsp;       Verify the following:</li> </ol><ol start="1" type="1">     <ul type="disc">      <li>MSH        Segment &ndash; required fields:</li>      <ul type="square">       <li>MSH-9&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Message Type.&nbsp;&nbsp; Value:&nbsp; MDM^T09</li>      </ul>      <li>TXA        Segment &ndash; required fields:</li>      <ul type="square">       <li>TXA-1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Set ID</li>       <li>TXA-2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Document Type</li>       <li>TXA-12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Unique Document Number</li>       <li>TXA-16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; includes the URL to access the         stored report document on the Report Manager (grouped with a RID         Information Source) </li>      </ul>      <li>There        are no OBX segments in an MDM^T09 message     </li>     </ul> </ol><p> 5. Each  updated version of a document must have its own unique document number.&nbsp; Verify that the value for TXA-12 is different  in the two MDM messages. </p> 