<H3>Special Instructions</H3><p> <p>Content Creators should run this test on the first day of the Connectathon.</p> <p>Content Creators in the BPPC Profile run one instance of this test to demonstrate their ability to create a 'Patient Privacy Consent Acknowlegement' document with content as specified in ITI TF-2:5.1.2 or ITI TF-2:5.1.3</p> <p>The Content Creator may support either the Basic Patient Privacy Acknowledgement option (ie with no scanned document content) or the Basic Patient Privacy Consent Acknowledgement with Scanned Document option. </p> </p> <H3>Description</H3> <p>This is a test of the creation 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 Creators are not required to use XDS/XDM/XDR to submit their content, but many Content Creators will have this capability, and we will use it in the test where possible.</p> <p>All Affinity Domains at the Connectathon have the following two privacy policies which patients can choose from:</p><ul> <li>The 'Normal Policy' (Normal Sharing for Treatment) have the confidentiality policy specified by the OID 1.3.6.1.4.1.21367.2006.7.108 </li> <li>The 'Restricted Policy' (Sensitive Restricted Sharing) have the confidentiality policy specified by the OID 1.3.6.1.4.1.21367.2006.7.109 </li> </ul><p>In this test, the Content Creator actor creates Consent documents for two 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>Store the document and reference information in the Kudu tool. You will find the page in the Kudu tool by selecting Connectathon and then Connectathon Images/CDs/Objects. The link to that page is <em><a href="system_con_object.php">Objects Information</a></em> </p> <p>If possible, the Content Creator will submit the document via XDS/XDM/XDR.</p> <H3>Evaluation</H3> <p>The connectathon monitor may ask the Content Creator to demonstrate the process of creating a Patient Privacy Consent Acknowlegement document with its system.</p> <p>Monitors please use the <em><a href="system_con_object.php">Objects Information</a></em> page to find the sample document(s) the Content Consumers have submitted. This may also be done by using a Document Consumer to retrieve the Consent Document from the Document Repository.</p> <p>The monitor will examine the two Patient Privacy Acknowledgement Documents stored in the Repository for patients NormalConsent^[system_name] and RestrictedConsent^[system_name]. </p> <p>The Consent documents shall 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>One code indicating the policy agreed to; the two documents should contain different codes; see test description</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> 