<H3>Special Instructions</H3><p> <p>An XDR Document Source must run this test if it supports BPPC, ie it supports the Basic Patient Privacy Enforcement option.   This is a test where the Document Source applies a privacy policy to document it submits (eg a Medical Summary).  This is not a test where the Source creates a patient's Consent document; that is test <b>BPPC_Content_Creator</b>.</p> </p> <H3>Description</H3> <p>The Document Source actor which support the Basic Patient Privacy Enforcement option populate the confidentialityCode in the document  metadata with the list of OID values that identify the Patient Privacy Consent Policy(ies) that apply to the associated document. </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>The Document Source registers documents for two patients:</p><ul>     <li>BPPCNormal^[source_system_name]</li>     <li>BPPCRestricted^[source_system_name]</li> </ul> <H3>Evaluation</H3>  <p>The monitor may ask the Document Source to show how Privacy Consent policies are configured on its system, and how it determines which confidentiality codes to applied  to a given document.</p> <p>The monitor may ask the Document Recipient to show how it configures Privacy Consent policies and how they're enforced on its system. <p>On the Document Recipient, the monitor should observe documents displayed for the Normal patient. If    any documents are displayed for the Restricted patient, that is a failure.</p> <p> The monitor may ask to see the exchange of other documents between the Doc Source and Recipient real-time.</p>  