Consent Management Service PSS

1a. Project Name Consent Management Service 1b. Project ID 1624 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? No 1e. Today's Date 1f. Name of standard being reaffirmed 1g. Project Artifact Information 1h. ISO/IEC Standard to Adopt 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? 1j. Unit of Measure 2a. Primary/Sponsor WG Service Oriented Architecture 2b. Co-Sponsor WG Community Based Care and Privacy 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballot 2c. Co-Sponsor Update Periods at WGMs 2b. Co-Sponsor WG 2 Security 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballot 2d. Project Facilitator Jerry Goodnough, Mohammad Jafari 2e. Other Interested Parties (and roles) Stefano Lotti - this will provide input to the HL7 Service Interoperability Reference Architecture work 2f. Modeling Facilitator 2g. Publishing Facilitator Lorraine Constable 2h. Vocabulary Facilitator 2i. Domain Expert Representative 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators SOA - Vince McCauley 2m. Implementers Telstra Health SD Health Connect 3a. Project Scope Service Functional Model API capturing the results of the Consent Management Pilot which is addressing the use of existing FHIR resources for Consent Management with Patient Consent, as represented by the FHIR Consent Resource. The implementation guidance produced with address different types of exchanges including v2, Direct (C-CDA), eHealthExchange (C-CDA and XDS) and FHIR, Australian Secure Messaging Delivery (SMD) and MyHR (XDS). A companion reference implementation project is occurring as an ONC Leap Pilot. An Australian implementation is also considering developing a Consent Management Service. It is not the intent of this project to alter the FHIR Consent or related resources, only to address the APIs used with them. Any required changes to the base resources will be addressed via FHIR change requests to the responsible work group. Attachments 3b. Project Need Appropriate management of patient consent is a fundamental capability of care management. Defined Service included Service Functional Model and guidance for the use of existing standards will enable consistent integrations into existing software architectures. Consent Management is commonly addressed in regulation in participating jurisdictions. 3c. Security Risk No 3d. External Drivers ONC Leap Pilot 3e. Objectives/Deliverables and Target Dates Initial STU Ballot - January 2021 Service Functional Model Published - May 2021 Normative Ballot - May 2022 3f. Common Names / Keywords / Aliases: 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/SOA/Consent+Management+Service 3j. Backwards Compatibility No 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? N/A 3l. Reason for not using current V3 data types? 3m. External Vocabularies Unknown 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products V3 Services – Web Services (SOA) 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 Create new standard, Supplement to a current 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 STU to Normative 5c. Additional Ballot Info 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 Telstra Health / ONC Leap Pilot with SD HealthConnect 6b. Content Already Developed 6c. Content externally developed? 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? 6f. Stakeholders Clinical and Public Health Laboratories, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs) 6f. Other Stakeholders 6g. Vendors Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS 6g. Other Vendors 6h. Providers Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health) 6h. Other Providers 6i. Realm Universal 7d. US Realm Approval Date 7a. Management Group(s) to Review PSS 7b. Sponsoring WG Approval Date May 11, 2020 7c. Co-Sponsor Approval Date Jun 02, 2020 7c. Co-Sponsor 2 Approval Date Jul 07, 2020 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 7f. FMG Approval Date 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Jul 27, 2020 7j. TSC Approval Date