Reaffirmation of HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1b. Project ID
1668
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
Jan 20, 2022
1f. Name of standard being reaffirmed
HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1g. Project Artifact Information
A project artifact is balloting Normative (no STU) (this includes reaffirmations)
1h. ISO/IEC Standard to Adopt
n/a
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
Infrastructure & Messaging
2d. Project Facilitator
Anthony (Tony) Julian
2e. Other Interested Parties (and roles)
2f. Modeling Facilitator
Anthony (Tony) Julian
2g. Publishing Facilitator
Anthony (Tony) Julian
2h. Vocabulary Facilitator
Sandra Stuart
2i. Domain Expert Representative
2j. Business Requirements Analyst
2k. Conformance Facilitator
2l. Other Facilitators
2m. Implementers
3a. Project Scope
The Health Level Seven (HL7) Standard applies to the electronic exchange of data in all healthcare environments. Within the context of healthcare messaging, the HL7 standard is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions
Attachments
3b. Project Need
Creates: Infrastructure for transmission of Version 3 messages
Supports: Messaging of all HL7 Version 3 domain content
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
3c. Security Risk
No
3d. External Drivers
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
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
V3 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
Other
6f. Other Stakeholders
Developers of Standards
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
7b. Sponsoring WG Approval Date
Jan 18, 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
7h. Architecture Review Board Approval Date
7i. Steering Division Approval Date
7j. TSC Approval Date
Jan 31, 2022
 Show Changes
Version
3
Modifier
Anne Wizauer
Modify Date
Feb 01, 2022 22:29
1a. Project Name
Reaffirmation of HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1b. Project ID
1668
1c. Is Your Project an Investigative Project (aka PSS-Lite)?
No
1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?
Yes
1e. Today's Date
Jan 20, 2022
1f. Name of standard being reaffirmed
HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1g. Project Artifact Information
A project artifact is balloting Normative (no STU) (this includes reaffirmations)
1h. ISO/IEC Standard to Adopt
n/a
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
Infrastructure & Messaging
2d. Project Facilitator
Anthony (Tony) Julian
2f. Modeling Facilitator
Anthony (Tony) Julian
2g. Publishing Facilitator
Anthony (Tony) Julian
2h. Vocabulary Facilitator
Sandra Stuart
3a. Project Scope
The Health Level Seven (HL7) Standard applies to the electronic exchange of data in all healthcare environments. Within the context of healthcare messaging, the HL7 standard is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions
3b. Project Need
Creates: Infrastructure for transmission of Version 3 messages
Supports: Messaging of all HL7 Version 3 domain content
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
3c. Security Risk
No
3d. External Drivers
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS
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)
6i. Realm
Universal
7b. Sponsoring WG Approval Date
Jan 18, 2022
7j. TSC Approval Date
Jan 31, 2022
Version
2
Modifier
Anne Wizauer
Modify Date
Jan 20, 2022 22:19
1a. Project Name
Reaffirmation of HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1b. Project ID
1668
1c. Is Your Project an Investigative Project (aka PSS-Lite)?
No
1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?
Yes
1e. Today's Date
Jan 20, 2022
1f. Name of standard being reaffirmed
HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1g. Project Artifact Information
A project artifact is balloting Normative (no STU) (this includes reaffirmations)
1h. ISO/IEC Standard to Adopt
n/a
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
Infrastructure & Messaging
2d. Project Facilitator
Anthony (Tony) Julian
2f. Modeling Facilitator
Anthony (Tony) Julian
2g. Publishing Facilitator
Anthony (Tony) Julian
2h. Vocabulary Facilitator
Sandra Stuart
3a. Project Scope
The Health Level Seven (HL7) Standard applies to the electronic exchange of data in all healthcare environments. Within the context of healthcare messaging, the HL7 standard is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions
3b. Project Need
Creates: Infrastructure for transmission of Version 3 messages
Supports: Messaging of all HL7 Version 3 domain content
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
3c. Security Risk
No
3d. External Drivers
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS
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)
6i. Realm
Universal
7b. Sponsoring WG Approval Date
Jan 18, 2022
Version
1
Modifier
Anthony Julian
Modify Date
Jan 20, 2022 20:04
1a. Project Name
Reaffirmation of HL7 Version 3 Standard: Transmission Infrastructure, Release 2
1b. Project ID
1668
1c. Is Your Project an Investigative Project (aka PSS-Lite)?
No
1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?
No
1f. Name of standard being reaffirmed
HL7 Version 3 Standard: Transmission Infrastructure, Release 2
2a. Primary/Sponsor WG
Infrastructure & Messaging
2d. Project Facilitator
Anthony (Tony) Julian
2f. Modeling Facilitator
Anthony (Tony) Julian
2g. Publishing Facilitator
Anthony (Tony) Julian
2h. Vocabulary Facilitator
Sandra Stuart
3a. Project Scope
The Health Level Seven (HL7) Standard applies to the electronic exchange of data in all healthcare environments. Within the context of healthcare messaging, the HL7 standard is primarily concerned with the data content of exchanges between healthcare applications, the sequence or interrelationships in the flow of messages and the communication of significant application level exceptions or error conditions
3b. Project Need
Creates: Infrastructure for transmission of Version 3 messages
Supports: Messaging of all HL7 Version 3 domain content
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
3c. Security Risk
No
3d. External Drivers
Referenced in IHE-XCPD which is built on V3 Query and MCCI, and cited in 2016 Interoperability Standards Advisory (ONC)
Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS
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)