This FHIR DSTU2 (Release 2) Consent profile describes how to use the Contract resource needs to represent and persist patient consent for treatment, research, or disclosure (e.g. 42 CFR Part 2, Title 38). Prior to FHIR Release 3 (STU3), implementers where required to use the Contract resource to represent an electronic patient's consent. Since a Contract is not sufficient to represent a granular consent, implementers need to use both a List and one or more Basic resources to define granular references to specific protected data types. The contained resources (List and Basic) allow us to enhance the structure of DSTU3 Contract specify protected data sets (e.g. HIV-related, Substance Use Disorder, STI) specified in a granular patient consent. A simple opt-in consent consistent with previous specifications and policies (e.g. DURSA) do not require any other resources besides the Contract conforming to the Consent-as-Contract). List of consent items (Basic resources). Dependencies: Consents that conform to this profile will include reference other resources: Patient (as patient and/or consenting party), RelatedPerson (as consenting party), Practitioner (custodians, information recipients), and Organization (custodian, custodians, information recipients). Typically, the resources referring to the patients, related persons, providers, organizations are described as external references to resources stored on the same server as the Contract (Consent-as-Contract) resource, Instances of Consent-as-Contract will reference a List resources that must conform to the profile specified in the parent implementation guide (URL: http://hl7.org/fhir/us/core/StructureDefinition/consent-as-contract-list).