Reaffirmation of HL7 V2: XML Encoding Rules, Release 2

1a. Project Name HL7 V2: XML Encoding Rules, Release 2 1b. Project ID 1748 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? Yes 1e. Today's Date Mar 30, 2022 1f. Name of standard being reaffirmed HL7 Version 2: XML Encoding Rules, Release 2 1g. Project Artifact Information A project artifact is balloting Normative (no STU) (this includes reaffirmations) 1h. ISO/IEC Standard to Adopt None 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? No 1j. Unit of Measure N/A (no measurements are in the standard 2a. Primary/Sponsor WG Implementable Technology Specifications 2d. Project Facilitator Paul Knapp 2e. Other Interested Parties (and roles) 2f. Modeling Facilitator 2g. Publishing Facilitator Paul Knapp 2h. Vocabulary Facilitator 2i. Domain Expert Representative 2j. Business Requirements Analyst 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers 3a. Project Scope The objective of this document is to present alternate encoding rules for HL7 Version 2.x messages (and a mechanism for determining alternate encoding rules for subsequent HL7 2.x versions) based on the Extensible Markup Language XML that could be used in environments where senders and receivers both understand XML. Attachments 3b. Project Need Some V2 implementers prefer more modern markup such as XML to older markup styles such as ER7. Provides additional specifications to supersede Release 1 Accommodates new features introduced beginning HL7 Version 2.3.1, e.g. the use of choices within message structures. 3c. Security Risk No 3d. External Drivers 3e. Objectives/Deliverables and Target Dates Reaffirmation Sept 2022 3f. Common Names / Keywords / Aliases: 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: http://www.hl7.org/documentcenter/private/standards/V2XML/HL7_V2_XML_R2_2018JAN_withErrata.zip 3j. Backwards Compatibility Yes 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? No 3l. Reason for not using current V3 data types? ITS V2 3m. External Vocabularies 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products V2 Messages – Infrastructure 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 Reaffirmation of a 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 5b. Project Ballot Type Normative (no STU) 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 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, Payors 6f. Other Stakeholders 6g. Vendors Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS 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 V2 7b. Sponsoring WG Approval Date Apr 13, 2022 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 Jul 15, 2022 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date 7j. TSC Approval Date Jul 25, 2022