<H3>Special Instructions</H3> <ul>    <li>For the purpose of NAV testing at the connectathon, the Notification Receiver will create an     email account and share the email address with the Notification Sender. This can be a gmail     account, for example. The Notification Sender will configure its system to send notification     messages for documents used during this test to this email address. The mechanism for how this     is configured is not specified by the NAV profile.</li>    <li>Note that in the Notification message (in Digital Signature format), the Registry in which     the document will be registered is identified by an OID in urn format. The OIDs are assigned by     Connectathon Managers. For the NA2009 connectathon, these are found here (If the Registry used     for this test is not listed, please see the Connectathon Manager to get it added):      <i>http://ihewiki.wustl.edu/wiki/index.php/NA2009-NAV_registry_OIDs#North_America_2009_Connectathon:_recommendedRegistry_OID_values_for_Document_Registries</i></li>    <li>If the Notification Sender is an XDS Registry, it will have to recruit Document Source to     send a documents to a Document Repository known to your Registry. This is required to trigger     notification. </li>    <li>IThe Notification Sender needs to inform the Notification Receiver (XDS Consumer) which XDS     Repository and Registry will receive the document. The Notification Receiver can then configure     its system with the recommendedRegistry value it will receive in the notification message.</li>    <li>The patient name used for the documents in this test is a combination of last name "NAV",     with the first name being the Notification Sender vendor's name, eg NAV^ABCMedicalCompany.     Demographics for these patients may be pre-created for you in the Connectathon patient     registration tool.</li>    <li>The Notification Sender (XDS Doc Source or Registry) and Notification Receiver (XDS Doc     Consumer) will want to ensure they support the same version (XDS.a/XDS.b) before starting this     test. </li>    <li>If the Notification Sender and Receiver support the acknowledgement option, you will want to     run test <b>NAV_Acknowledgement_Option</b> at the same time as this one.</li> </ul>  <H3>Description</H3>    <p>In this test, a Notification Sender (XDS Doc Source or Registry) requests sends a notification    about document(s) to the Notification Recipient (XDS Doc Consumer).</p>  <h3>Evaluation</h3>  <p>The Connecthon monitor will ask the <strong>Notification Receiver</strong> to show how it maps    an OID identifier for the Notification Sender/XDS Registry (ie the value of recommendedRegistry    in the XML Digital Signature notification attachment) to the URL used to query the registry. The    profile does not specify how this must be done (ie a gui is not required).</p>   <p>The Connectathon monitor will ask to see the email received on the <strong>Notification     Receiver</strong> (Document Consumer) system. Check:</p>   <ol>    <li>The Subject line of the message is human-readable.</li>    <li>The first part of the message must contain text that indicates the purpose of the message is     to notify the receiver that documents are available. This part may also optionally contain     instructions to the receiver on how to use this message.</li>    <li>The email contains an attachment formattd as a W3C XML Digital Signature. (Specified in NAV     TI Supplement Vol 2: 3.25.41.1.2.1)</li>   </ol>   <p>On the Notification Receiver, the Connectathon monitor will want to witness some link in your    application between the receipt of the notification and some meaningful activity; ie you will use    the content in the notification to query the Registry for the document in the notification's    manifest.</p>   <p>The Connectathon monitor will ask the Document Consumer to query the Document Registry. The    monitor should see that one or more documents for patient NAV^vendor-name is available to be    retrieved.</p>   <p>The Connectathon monitor may ask the Notification Sender to trigger sending another    notification so he/she can see it arrive real-time on the Notification Receiver.</p>   <p>The Connecthaton monitor may examine the xml attachment. It's possible this will only be done    if troubleshooting. (See notification document structure specified in NAV TI Supplement Vol 2:    3.25.41.1.2.1) </p>  