Arden Syntax for Medical Logic Systems v3.0-PSS

1a. Project Name Arden Syntax for Medical Logic Systems v3.0-PSS 1b. Project ID 1118 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 Arden Syntax 2b. Co-Sponsor WG Clinical Decision Support 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballotRequest periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2c. Co-Sponsor Update Periods At each WGM. 2d. Project Facilitator Robert Jenders 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator 2g. Publishing Facilitator Robert Jenders 2h. Vocabulary Facilitator 2i. Domain Expert Representative Klaus-Peter Adlassnig, Peter Haug 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers 1) Medexter Healthcare 2) Clinical Decision Support Group, University of Colorado Hospital 3a. Project Scope Arden Syntax v3.0 will be an updated successor to Arden Syntax v2.10 in the universal realm. The primary change in v3.0 over v2.10 will be incorporation of a standard data model for external data mappings in order to address the “curly braces” problem. The target data model will be based on the FHIR specification. The FHIR standards for data access are currently in a mixed normative/STU status. Therefore, the Arden Syntax v3.0 specification will be released as a STU. We anticipate that when a fully normative FHIR standard for data access and storage emerges, we will be able to move the specification to a normative standard. Attachments 3b. Project Need Key obstacles to widespread adoption of the Arden Syntax are the diversity of data models in current use and the consequent need to remap data elements when sharing computable knowledge (Medical Logic Modules). Use of the standard FHIR data models will enhance knowledge sharing by allowing organizations who have adopted the relevant FHIR models to use Arden version 3 Medical Logic Modules without the need to construct new mappings for essential data. This project scope statement is an updated version of an earlier, approved PSS that extends target dates to allow the FHIR standard to mature. 3c. Security Risk No 3d. External Drivers None 3e. Objectives/Deliverables and Target Dates Submit for STU Ballot: May 2023 Ballot Complete STU Reconciliation: May 2023 WGM Submit Publication Request: June 2023 Submit for Normative Ballot: May 2024 Submit Publication Request: June 2024 Project End Date: Sep 2024 WGM 3f. Common Names / Keywords / Aliases: Arden Syntax for Medical Logic Systems v3.0, Arden Manual, Arden Syntax Manual, Arden Standard, MLM Standard. 3g. Lineage The new document will extend Arden Syntax for Medical Logic Systems v2.10. 3h. Project Dependencies Prior to releasing a normative version of the Arden Syntax Standard using a data model based on FHIR, the FHIR specifications for reading and writing data should reach a sufficient maturity to be regularly adopted by industry. Because the FHIR standards are currently mixed normative/STU, the initial Arden Syntax v3.0 will be a Standard for Trial Use. 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/ARD/Arden+Syntax+v3.0 3j. Backwards Compatibility Yes 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 No 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies Arden 2.10. 4a. Products Arden Syntax 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 Arden Syntax for Medical Logic Systems v2.10 5b. Project Ballot Type STU to Normative 5c. Additional Ballot Info The sole purpose of this PSS is to update the timeline from the previous version and to accommodate the increased maturity of the FHIR standards. 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 70% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Quality Reporting Agencies 6f. Other Stakeholders 6g. Vendors EHR, PHR, Health Care IT, Clinical Decision Support Systems, HIS 6g. Other Vendors 6h. Providers Emergency Services, 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 7b. Sponsoring WG Approval Date Sep 20, 2021 7c. Co-Sponsor Approval Date Sep 21, 2021 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