<H3>Special Instructions</H3><p>  <p>Content Consumers please use the <em><a href=system_con_object.php>Objects Information</a></em> page to find the sample BPPC document(s) your peers have submitted. </p> <p>The BPPC Content Creators must run test<b> BPPC_Content_Creator </b>before this test can be run.  Content Creators have no work to do in this test, but are included as an actor in this test so that they get credit when Content Consumers display the contents of the Consent documents they created in the earlier test.</p> <p>BPPC Content Consumers  run this test to demonstrate their ability to display  'Patient Privacy Consent Acknowlegement' documents made by Content Creators as specified in ITI TF-2:5.1.2 and TF-2:5.1.3.</p> <p>BPPC Content Consumers must support the <b>Basic Patient Privacy Acknowledgement View </b>option. </p> </p><H3>Description</H3><p> <p>This is a test of the display of a patient's Consent  document per the BPPC profile.  The  application of the restrictions in privacy consents on other documents for this  patient is tested in another test.</p>     <p>BPPC Content Consumers are not required to use XDS/XDM/XDR  to retrieve Consent documents, but many Content Consumers will have this  capability, and we will use it in the test where possible.</p>     <p>In this test, the Content Consumer actor displays Consent  created in test <strong>BPPC_Content_Creator</strong> for patients as follows (the patient's  first name is the Content Creator's system name in kudu):</p>     <ul>      <li>NormalConsent^[system-name]</li>      <li>RestrictedConsent^[system-name]</li>     </ul>     <p>If possible, the Content Consumer will retrieve  the document.</p> </p> <H3>Evaluation</H3> <p>The monitor will examine the two Patient Privacy  Acknowledgement documents as they're displayed on the Content Consumer's  application.  The BPPC profile requires  display capabilities of the Content Consumer actor; the system must demonstrate  a reasonable rendering of the contents of the Consent document.  If the Content Consumer can only retrieve the  document into its database, but not display it, it will fail this test.</p><p>The Consent documents contain:</p><ul>     <li>An 'author'; this is the patient, guardian or  legal guardian issuing the consent acknowledgement.</li>     <li>A text description of what the patient consented  to.  It should differ in the two documents</li>     <li>Once code indicating the policy agreed to; the  two documents should contain different codes - Normal and Restricted</li>     <li>The effective dates of this consent is  specified.   If the Content Creator has  this capability, the 'normal' consent should be in effect for the week of the  connectathon, and the 'Restricted' consent should be in effect for the current  calendar year.</li> </ul> 