HL7 FHIR US Public Health Profiles Library

1a. Project Name HL7 FHIR US Public Health Profiles Library 1b. Project ID 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 Public Health 2d. Project Facilitator John Loonsk; Sarah Gaunt 2e. Other Interested Parties (and roles) During the project proposal Structured Documents, Vocab, CQI, and CIC expressed interested in having a role in the project. We will reach out to these work groups to assess level of involvement. 2f. Modeling Facilitator Sarah Gaunt 2g. Publishing Facilitator Sarah Gaunt 2h. Vocabulary Facilitator Sarah Gaunt 2i. Domain Expert Representative John Loonsk, Laura Conn 2j. Business Requirements Analyst Sarah Gaunt 2k. Conformance Facilitator Sarah Gaunt 2l. Other Facilitators John Loonsk, Laura Conn 2m. Implementers eCR FHIR IG, MedMorph FHIR IG (This is an "abstract" library of profiles, it will never be directly implemented, rather its profiles will be referenced/used in other IGs). 3a. Project Scope After evaluation and harmonization analysis of two large multi-condition and multi-use case public health projects – eCR and MedMorph, it was determined that there are many common elements between the two IGs. The short-term scope of this library will include elements common to the above-mentioned FHIR IGs and will define a US Realm specific framework that defines common elements for the implementation guides. The longer-term scope of this will include analysis and inclusion of data elements from Vital Records Death Reporting, Vital Records Birth and Fetal Death Reporting, and other Public Health use cases. The US Public Health Profiles Library will be instituted in close conjunction with US Core and have an analogous process for implementation, moderation, review, and approval. The intent is to re-use US Core profiles wherever possible and only add profiles that are needed for common public health needs. The library will evolve over time and may be supported by an adjunct profiles registry that includes developing and informational profiles for public health use. Attachments 3b. Project Need The US Public Health Profiles Library will be a collection of reusable architecture and content profiles representing common public health concepts and patterns. It is intended as a complement to US Core that is used to ease implementation burden of healthcare organizations, electronic health record companies, public health agencies, and others involved in the US public health endeavor. To avoid defining the same profiles multiple times, we propose to create a US Public Health Profiles Library for use by Public Health and other FHIR standards development efforts to define appropriate FHIR profiles, value sets, etc., once and allow them to be referenced by each of the specific implementation guides. This USPHPL will provide a starting point and framework for inclusion in multiple use case specific implementation guides focused on the exchange of Public Health information to support interoperability among public health systems and reduce provider and implementer burden. 3c. Security Risk 3d. External Drivers 3e. Objectives/Deliverables and Target Dates STU 1: Sept 2022 Ballot STU 1: Jan 2023 Publication 3f. Common Names / Keywords / Aliases: 3g. Lineage eCR & MedMorph harmonization 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://github.com/HL7/fhir-us-ph-common-library-ig/tree/master 3j. Backwards Compatibility N/A 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 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products FHIR Implementation Guide, FHIR Profiles 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? 4 4c. FHIR Profiles Version 4d. Please define your New Product Definition 4d. Please define your New Product Family 5a. Project Intent Implementation Guide (IG) will be created/modified 5a. White Paper Type 5a. Is the project adopting/endorsing an externally developed IG? No 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 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 80% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? 6f. Stakeholders Regulatory Agency, Standards Development Organizations (SDOs), Other 6f. Other Stakeholders Public Health Agencies 6g. Vendors EHR, PHR, Health Care IT, Other 6g. Other Vendors PHA Surveillance System 6h. Providers Local and State Departments of Health, Healthcare Institutions (hospitals, long term care, home care, mental health) 6h. Other Providers 6i. Realm U.S. Realm Specific 7d. US Realm Approval Date 7a. Management Group(s) to Review PSS FHIR 7b. Sponsoring WG Approval Date 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 7f. FMG Approval Date 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date 7j. TSC Approval Date