Reaffirmation: HL7 CDA® R2 Implementation Guide: Privacy Consent Directives

1a. Project Name Reaffirmation: HL7 CDA® R2 Implementation Guide: Privacy Consent Directives 1b. Project ID 1709 1c. Is Your Project an Investigative Project (aka PSS-Lite)? No 1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU? Yes 1e. Today's Date Jun 10, 2021 1f. Name of standard being reaffirmed HL7 CDA® R2 Implementation Guide: Privacy Consent Directives, Release 1 1g. Project Artifact Information A project artifact is balloting Normative (no STU) (this includes reaffirmations) 1h. ISO/IEC Standard to Adopt https://www.hl7.org/special/Committees/tsc/ballotmanagement/pi_index_nibs.cfm?ProjectNumber=553 1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption? No 1j. Unit of Measure N/A (no measurements are in the standard 2a. Primary/Sponsor WG Community Based Care and Privacy 2d. Project Facilitator Johnathan Coleman 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator Ioana Singureanu 2g. Publishing Facilitator Ioana Singureanu 2h. Vocabulary Facilitator Ioana Singureanu 2i. Domain Expert Representative David Pyke 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers 3a. Project Scope Reaffirmation of https://www.hl7.org/special/Committees/tsc/ballotmanagement/pi_index_nibs.cfm?ProjectNumber=553 Attachments 3b. Project Need Dependency for DS4P, other Consent related work 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates Sep 2021 Ballot 3f. Common Names / Keywords / Aliases: CDA Consent Directive 3g. Lineage see https://www.hl7.org/special/Committees/tsc/ballotmanagement/pi_index_nibs.cfm?ProjectNumber=553 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://gforge.hl7.org/gf/project/cbcc/frs/?action=FrsReleaseBrowse&frs_package_id=139 3j. Backwards Compatibility Yes 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? 3l. Reason for not using current V3 data types? 3m. External Vocabularies No 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products V3 Documents – Clinical (e.g. CDA) 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? 4c. FHIR Profiles Version 4d. Please define your New Product Definition 4d. Please define your New Product Family 5a. Project Intent Reaffirmation of a standard 5a. White Paper Type 5a. Is the project adopting/endorsing an externally developed IG? 5a. Externally developed IG is to be (select one) 5a. Specify external organization 5a. Revising Current Standard Info 5b. Project Ballot Type Normative (no STU) 5c. Additional Ballot Info Ballot Level/Iteration is currently Normative 3. 5d. Joint Copyright No 5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval. no 6a. External Project Collaboration 6b. Content Already Developed 100 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Regulatory Agency 6f. Other Stakeholders 6g. Vendors EHR, PHR 6g. Other Vendors 6h. Providers 6h. Other Providers 6i. Realm Universal 7d. US Realm Approval Date 7a. Management Group(s) to Review PSS CDA 7b. Sponsoring WG Approval Date Apr 06, 2021 7c. Co-Sponsor Approval Date 7c. Co-Sponsor 2 Approval Date 7c. Co-Sponsor 3 Approval Date 7c. Co-Sponsor 4 Approval Date 7c. Co-Sponsor 5 Approval Date 7c. Co-Sponsor 6 Approval Date 7c. Co-Sponsor 7 Approval Date 7c. Co-Sponsor 8 Approval Date 7c. Co-Sponsor 9 Approval Date 7c. Co-Sponsor 10 Approval Date 7e. CDA MG Approval Date Jul 13, 2021 7f. FMG Approval Date 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date 7j. TSC Approval Date Aug 09, 2021