<H3>Special Instructions</H3>   <ul>    <li>Notification Senders are required to support one of the "Acknowledgement Request..." options     (SMTP, POP3 and/or IMAP). To run this test, you will need to seek a Notification Receiver which     supports the "Send Acknowledgement" option.</li>    <li>For the purpose of testing NAV acknowledgements, the Notification Sender will create an email     account for itself that it will encode in the notification as an embedded <b>mailto</b> link.     This can be a gmail account, for example. </li>    <li>Test <b>NAV_Exchange_Notification</b> should be run in parallel with this one. Steps 10-60     are the same in both tests, plus a few more added at the end here, so you can get credit for     both tests. </li>    </ul> <H3>Description</H3>   <p>In this test, a Notification Receiver (XDS Doc Consumer) acknowleges receipt of a notification    message by sending an email to the Notification Sender (XDS Doc Source or Doc Registry).</p> <h3>Evaluation</h3>  <p>The acknowlegement must be sent immediately upon receipt and processing of the notification    message on the Notification Receiver (Document Consumer).</p>   <p>The Connectathon monitor will ask to see the email received on the <strong>Notification    Sender</strong> (Document Source or Doc Registry) system. Check:</p>   <ol>    <li>The Subject of the email contains: "XDS%20Acknowledgement: signataureId value"</li>    <li>The content type of the message is ASCII text.</li>    <li>The first line of the message contains "OK" , or, "NOT OK" if this is a negative     acknowledgement.</li>    <li>One or more blank lines follow the 'ok' line.</li>    <li>The remaining text may be a plain text message suitable for human viewing, but not processed     by the Notification Sender actor.</li>    <li>The entire message body shall contain no more than 100 lines or 3000 characters of data     (incl. CR and LF).</li>   </ol>   <p>Ihe NAV supplement indicates that the Notification Sender "processes" the acknowledgement    message. The TF is intentionally vague when it uses the term "process". There are no specific    "Expected Actions" in the ITI-28 transaction. Certainly, no user interface is required. IHE tries    not to define application behavior. You should be able to describe to the connectathon monitor    how your system behaves when it receives the acknowledgement (as expected), and what it does in    the event no acknowledgement comes back (ie is there something that would trigger the user at the    Doc Source to resend the email?). </p>