Situation Awareness for Novel Epidemic Response FHIR IG

1a. Project Name Situation Awareness for Novel Epidemic Response FHIR IG 1b. Project ID 1617 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 2b. Co-Sponsor WG Orders & Observations 2c. Co-Sponsor Level of Involvement Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2c. Co-Sponsor Update Periods Monthly 2b. Co-Sponsor WG 2 Patient Administration 2c. Co-Sponsor Level of Involvement Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2c. Co-Sponsor 2 Update Periods Monthly 2d. Project Facilitator David Pyke 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator 2g. Publishing Facilitator Alex De Leon 2h. Vocabulary Facilitator 2i. Domain Expert Representative 2j. Business Requirements Analyst 2k. Conformance Facilitator David Pyke 2l. Other Facilitators 2m. Implementers Cerner, EPIC, Microsoft,others 3a. Project Scope The Situational Awareness for Novel Epidemic Response Implementation Guide enables transmission of high level situational awareness information from initially inpatient facilities to centralized data repositories to support the focus and response to novel influenza-like illness, such as COVID-19. The goal of publishing this guide is to encourage the creation of a community interested in extremely rapid development of interfaces that can support communication of aggregate patient status and outcome measures, bed, ventilator, and other resource measures, as well as test order and result measures to national, state, or local Public Health agencies/jurisdictions in this time of crisis. This project will focus on current and draft FHIR resources with possible new extensions. This scope was initially established to address US reporting requirements by FEMA, CDC to address COVID-19. However, other state, local, and additional countries' jurisdictional reporting needs are expected to be included as well as the project team expands as the pandemic is global. Nor are related or other outbreaks are not excluded from the scope. Other projects that may overlap will be considered as needed. Attachments 3b. Project Need COVID-19 has caused a need to have immediate awareness of available aggregate status, outcome, and resources for public health and other group monitoring, coordinating, and directing a course of action. Related and future outbreaks can immediately benefit from the work in this project be further prepared. 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates A FHIR IG for resource availability reporting Dates TBD 3f. Common Names / Keywords / Aliases: Situation Awareness for Novel Epidemic Response 3g. Lineage 3h. Project Dependencies None 3i. HL7-Managed Project Document Repository URL: https://github.com/HL7/fhir-saner 3j. Backwards Compatibility No 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? Yes 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 FHIR Extensions, FHIR Implementation Guide, FHIR Profiles 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? R4 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 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 80% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content Keith Boone, Audacious Inquiry Josh Mandel, Microsoft Dave Pyke, Ready Computing Many others 6e. Is this a hosted (externally funded) project? Yes 6f. Stakeholders Clinical and Public Health Laboratories, Immunization Registries, Regulatory Agency, Payors 6f. Other Stakeholders 6g. Vendors EHR, PHR, Health Care IT, Lab, HIS 6g. Other Vendors 6h. Providers Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, 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 FHIR 7b. Sponsoring WG Approval Date Mar 25, 2020 7c. Co-Sponsor Approval Date Mar 26, 2020 7c. Co-Sponsor 2 Approval Date Apr 02, 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 Apr 01, 2020 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Apr 03, 2020 7j. TSC Approval Date Apr 06, 2020