Backporting R5 Subscriptions to R4 as an Implementation Guide

1a. Project Name Backporting R5 Subscriptions to R4 as an Implementation Guide 1b. Project ID 1642 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 Jul 20, 2020 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 FHIR Infrastructure 2d. Project Facilitator Eric Haas 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator Gino Canessa 2g. Publishing Facilitator Eric Haas 2h. Vocabulary Facilitator Gino Canessa 2i. Domain Expert Representative Gino Canessa 2j. Business Requirements Analyst Gino Canessa 2k. Conformance Facilitator Eric Haas 2l. Other Facilitators 2m. Implementers TBD ( Da Vinci Public Health Use Cases) reference implementation Microsoft 3a. Project Scope Create the Subscription R5 Backport Implementation Guide which will enables servers running version R4 of FHIR to implement a subset of the reworked R5 Subscriptions API in a standardized way. CI build of Implementation Guide: https://build.fhir.org/ig/HL7/fhir-subscription-backport-ig/ Attachments 3b. Project Need The goal of publishing this guide is to define a standard method of back-porting newer subscriptions for greater compatibility and to provide a bridge to adoption of the reworked subscription design prior to the adoption of the R5 FHIR standard. Current approach to subscriptions: "Search semantics", sort of. More like "new resource match" semantics. Moderately flexible, like searches Doesn't scale across resource types (?) No criteria semantics for any named events No way to advertise what able to subscribe to. In R5, subscriptions are broken into a 1) topic, which defines the resource(s) for the subscription and the events on which they happen, and 2) a subscription, which is the registration of a communication channel optionally with some additional filtering. 3c. Security Risk No 3d. External Drivers Da Vinci and Public Health Use Cases 3e. Objectives/Deliverables and Target Dates Implementation Guide ready for January Ballot. 3f. Common Names / Keywords / Aliases: Subscription Backport IG. R5 to R4 Subscriptions 3g. Lineage R5 Subscriptions 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://github.com/HL7/fhir-subscription-backport-ig 3j. Backwards Compatibility No 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? No 3l. Reason for not using current V3 data types? NA 3m. External Vocabularies Unknown 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies NA 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 R4 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 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, Clinical Decision Support Systems 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 FHIR 7b. Sponsoring WG Approval Date Jul 20, 2020 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 Jul 22, 2020 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date Oct 05, 2020 7j. TSC Approval Date Oct 05, 2020