HL7 Privacy and Security Logical Data Model PSS

1a. Project Name HL7 Privacy and Security Information Model PSS renamed Privacy and Security Logical Data Model 1b. Project ID 1630 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 Security 2b. Co-Sponsor WG Community Based Care and Privacy 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballot 2d. Project Facilitator Mike Davis 2e. Other Interested Parties (and roles) Bernd Blobel, Beth Pumo KP, Kathleen Connor-Security WG Co-Chair Suzanne Gonzales-Webb-CBCP WG Co-Chair 2f. Modeling Facilitator Mike Davis 2g. Publishing Facilitator Mike Davis 2h. Vocabulary Facilitator Kathleen Connor 2i. Domain Expert Representative Suzanne Gonzales-Webb, Mohammad Jafari, Beth Pumo 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers Department of Veterans Affairs 3a. Project Scope Develop and publish up-to-date Security and Privacy Information Model aligned with the Composite Security and Privacy DAM, Privacy and Security Architecture Framework and other foundational security standards including ISO 10181 and ISO 22600. Attachments 3b. Project Need The current HL7 Composite Security and Privacy Domain Analysis Model information models is out of date (dates back to were completed in 2014). Since that time significant changes to class relationships including new relationships to other Security models have been developed such as Security Labeling, Audit, Trust and Provenance. These models need to connect more holistically in an updated, overarching conceptual model. 3c. Security Risk No 3d. External Drivers None 3e. Objectives/Deliverables and Target Dates Map, gap, and harmonize current HL7 and ISO authentication, access control, audit, provenance, and trust models. Consider alignment, revision, and addition of classes, attributes, and associations. Consider applicability of ISO DIS 23903 Interoperability and Integration Reference Architecture - Model and Framework: June - September 2020 for review during the WGM. Finalize documentation and modeling for January 2021 ballot. Reconcile and if necessary, reballot May 2021. 3f. Common Names / Keywords / Aliases: Privacy and Security Information Model 3g. Lineage Builds upon previous Composite Security and Privacy 2014. 3h. Project Dependencies None 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/SEC/HL7+Privacy+and+Security+Information+Model 3j. Backwards Compatibility Unknown 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? N/A 3l. Reason for not using current V3 data types? Conceptual model 3m. External Vocabularies 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products Logical Model 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 Revise 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 Security and Privacy Domain Analysis Model 5b. Project Ballot Type Normative (no STU) 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 6b. Content Already Developed 40% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs), Payors 6f. Other Stakeholders 6g. Vendors EHR, PHR, Health Care IT, Clinical Decision Support Systems, Lab 6g. Other Vendors 6h. Providers Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health 6h. Other Providers 6i. Realm Universal 7d. US Realm Approval Date 7a. Management Group(s) to Review PSS 7b. Sponsoring WG Approval Date Jun 09, 2020 7c. Co-Sponsor Approval Date Jun 09, 2020 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 7f. FMG Approval Date 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Jul 07, 2020 7j. TSC Approval Date Jul 27, 2020