FHIR Shorthand Updates - PSS

1a. Project Name FHIR Shorthand 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 May 26, 2023 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 Mark Kramer 2e. Other Interested Parties (and roles) Chris Moesel (lead implementer), Lloyd McKenzie (user), Grahame Grieve (collaborator) 2f. Modeling Facilitator 2g. Publishing Facilitator 2h. Vocabulary Facilitator 2i. Domain Expert Representative 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers MITRE Corporation, Firely (Simplifier Integration), HL7 (IG Publisher integration), various IG authors (see: https://fshschool.org/fsh-finder/). 3a. Project Scope FHIR Shorthand is a specification of a domain-specific language (DSL) to allow Implementation Guide authors to define conformance resources (e.g., StructureDefinitions, ValueSets, etc.) and general instances (e.g., examples). This project is a continuation of the prior FHIR Shorthand project to improve the specification by adding new TU features, clarifying existing features, and promoting existing TU features to Normative status. Attachments FSHQuickReference.pdf 3b. Project Need The general need for FHIR Shorthand has been proven by its widespread adoption. A new version is needed to address limitations, implement user feedback, and improve support for FHIR R5 and beyond. 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates First ballot (STU) - May 2020 Ballot. First release (STU) - October 2020. Second ballot (Mixed Normative / TU) - September 2021 Ballot. Second release (Mixed Normative / TU) - February 2022. Third ballot (Mixed Normative / TU) - September 2023 Ballot. Third release (Mixed Normative / TU) - Early 2024. Additonal releases as needed. 3f. Common Names / Keywords / Aliases: FSH, SUSHI, Shorthand, IG, DSL, Language 3g. Lineage Originally based on similar free, open source tool called CIMPL (Clinical Information Modeling and Profiling Language) developed primarily by MITRE Corp. and used to develop early versions of mCODE, ODH, and other balloted IGs. 3h. Project Dependencies FHIR and FHIR IG Publication Tools 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/FHIRI/FHIR+Shorthand 3j. Backwards Compatibility Yes 3k. Additional Backwards Compatibility Information (if applicable) The next version of FHIR Shorthand will add and improve features without removing any existing features. 3l. Using Current V3 Data Types? No 3l. Reason for not using current V3 data types? FHIR datatypes (R4, R4B, R5) are used. 3m. External Vocabularies No 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies FHIR Shorthand 2.0.0 4a. Products FHIR Implementation Guide, Creating/Using a tool not listed in the HL7 Tool Inventory 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? FHIR R4 / R4B / R5 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 Updating FHIR Shorthand 2.0.0, published February 17, 2022, as well as additional future updates as needed. 5b. Project Ballot Type STU to Normative, Normative (no STU) 5c. Additional Ballot Info Mixed Normative / TU, promoting some prior TU content to Normative and introducing new TU content. 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 Collaboration w/ existing FHIR Shorthand users across a variety of IGs and Accelerators. 6b. Content Already Developed 99% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Standards Development Organizations (SDOs), Other 6f. Other Stakeholders FHIR Community (anyone who develops FHIR IGs and/or FHIR data for testing or demonstration) 6g. Vendors N/A 6g. Other Vendors 6h. Providers N/A 6h. Other Providers 6i. Realm Universal 7d. US Realm Approval Date 7a. Management Group(s) to Review PSS FHIR 7b. Sponsoring WG Approval Date Jun 05, 2023 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