<H3>Special Instructions</H3><p> <p>BPPC Portable Media Creators (PMC) must run test <b>BPPC_Portable_Media_Creator_Enforcement </b> before this test can be    run.  PMCs have no work to do in this test, but are included as an actor in this test    so that they get credit when Portable Media Importers process the documents they applied the consent    policies to.</p> <p>A Portable Media Importer must run this test if you support BPPC, ie you support the Basic Patient    Privacy Enforcement option. </p> </p> <H3>Description</H3> <p>In this test, the Portable Media Importer imports documents for two patients:</p>  <ul>     <li>BPPCNormal^[PMC_system_name]</li> <li>BPPCRestricted^[PMC_system_name]</li> </ul> <p>After the import the Portable Media Importer should display documents to the user (if it has display capabilities and if the policy    allows it).</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.107 </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 Portable Media Importer should import documents for the Normal patient and not import documents for the    patient who chose the Restricted policy.</p> <H3>Evaluation</H3> <p>The monitor should observe the Portable Media Importer in real time importing documents. The monitor should observe documents imported/displayed (but display is not required) for the Normal patient only. If    any documents are imported for the Restricted patient, that is a failure.</p> <p>The monitor may ask the Portable Media Importer to show how Privacy Consent policies are configured on    its system, and how it determines how to enforce confidentiality codes in the Affinity   Domain.</p>