Project Summary for Update and Separate the HL7 V2 Conformance Methodology Specification
Visit Project Insight to see the full project details. *
Project Details
Number | 1396 View Ballot Items List (with NIBs) |
---|---|
Name | Update and Separate the HL7 V2 Conformance Methodology Specification |
Sponsor(s) | Conformance Work Group |
Co-Sponsor(s) | Infrastructure and Messaging Work Group |
Steering Division | Infrastructure |
Description | The intent of the project is to update the conformance methodology used to profile message definitions and to separate (divorce) the conformance chapter (currently Chapter 2B) from the 'main' HL7 v2 standard.
- Provide an independent (separate) HL7 v2 Conformance Methodology standard. - Update the conformance constructs and profiling mechanisms used for implementation guide creation - Update the profile schema that supports the XML computable representation for implementation guides and message profiles - Deprecate by means of an errata the Conformance chapter/section from all prior V2 versions. (our expectation is that the content of conformance testing of existing IGs will not change, but going forward any new specification will use this updated conformance methodology). To be clear, the proposal is an updated method of how to specify conformance for new IGs. - Identify opportunities to encourage adoption by external implementation guide developers (e.g., IHE) to use the same conformance definitions and constructs. There are many versions of the HL7 v2 standard. An explicit conformance methodology was introduced into the standard in version 2.5 and revised in subsequent versions of the standard. The conformance methodology was part of chapter 2 initially and later became a subchapter (Chapter 2B Conformance). This document serves to replace (override) the conformance methodology in these earlier versions and it is intended to be applied to any HL7 v2 version. That is, if a developer is seeking to constrain a version 2.5.1 message event, they should use the conformance methodology prescribed in this document and not the conformance methodology given in version 2.5.1. |
Project Facilitator | Rob Snelick |
Status | Archived |
SD Approval Date | May 14, 2018 |
TSC Approval Date | Apr 1, 2019 |
Type | Ballot - Normative (no STU) |
Objectives / Deliverables | Submit draft for comment Ballot (First Ballot Cycle) - Target: 2019 Sept Ballot Complete ballot Reconciliation - Target: 2020 Nov/Dec WGM Submit for Normative Ballot - Target: 2020 Jan Ballot Complete Normative Reconciliation - Target: 2020 May WGM Submit Publication Request - Target: 2020 June Receive ANSI Approval - Target: 2020 July Project Close - Target: 2020 Aug |
Next Milestone Date | 2020 September WGM |
Project End Date | 2020 September WGM |
Project Intent | Revise Current Standard, Supplement to a Current Standard |
Project Need | HL7 v2 implementation guide specification has historically been ambiguous due to the lack of sufficient conformance profiling mechanisms and guidance. In recent years many updates and improvements have been developed and used in the creation of HL7 v2 implementation guides. However, these practices have not been formally documented in the HL7 v2 conformance chapter. Additionally, the profile schema that provides the format of the computable XML profile has not been updated. The need is to provide a formal specification for both the narrative and machine representation of current best practices of the HL7 v2 conformance methodology. Conformance and profiling of message definitions is independent of any one version of the HL7 v2 standard. Profiling activities should use the current conformance mechanisms for creating implementation guides. Currently, the conformance methodology is embedded in each v2 version. The need is to create and promote a process to use the latest profiling constraint mechanisms irrespective of the version of the HL7 v2 implementation guide. Considering that v2 is expected to be relevant due to the global install base, and it has been recognized that consistent, clear implementation guides are essential to the success of any wide ranging interoperability initiative, maintaining current conformance definitions and practices is critical. |
Implementers | |
Security Risks | No |
External Drivers | Project is being tackled now on the heels of work to support various certification efforts from ONC, HIMSS, IHE, etc. where implementation guides became a critical tool to drive consistency and clarity. Creation of certification testing tools revealed the lack of clarity in the HL7 v2 implementation guides being used, and better defining conformance will help v2 implementation guide authors to write consistent, concise and clear requirements. Project is related to the HL7 effort to use IGAMT (Implementation Guide Authoring and Management Tool) to create and publish HL7 v2 implementation guides. The conformance methods implemented in IGAMT will follow the requirements specified in this document. |
Common Names / Keywords/ Aliases | v2 Conformance |
Lineage | n/a |
Dependancies | There are no project dependencies. However, the relationship between this PSS and HL7 v2.9 and HL7 v2.+ warrants discussion. The specification being created in this PSS replaces conformance sections and chapters (chapter 2B) in previous and future versions of HL7 v2. The section or chapter in previous versions will be deprecated; this applies to all versions prior to and including version 2.8.2. The timeline of this specification and version 2.9 is not yet fully determined. It is estimated that v2.9 will be published first and therefore chapter 2B will be deprecated upon completion of this specification. This specification will be completed before v2.+ and v2.+ will reference it (as will all releases of v2.+). |
Project Document Repository | Conformance WG Confluence |
Backwards Compatibility | N/A |
External Vocabularies | N/A |
Products | V2 Messages-Infrastructure |
Joint Copyright? | No |
External Pjt Collaborators | n/a |
Realm | Universal |
HL7 Affiliate | |
Stakeholders | Clinical and Public Health Laboratories, Immunization Registries, Regulatory Agency, Standards Development Organizations (SDOs), Other (specify in Misc. Notes below) |
Vendors | Health Care IT; Lab; HIS; Other (specify in Misc. Notes below) |
Providers | N/A |
Ballot Cycle Info | 2019 Sept Ballot Cycle Info: COMMENT ONLY Ballot results: Did not meet basic vote requirements. 3 Negatives to reconcile Document Name: Version 2 Conformance Methodology, Release 1 |
Misc Notes | 2020 Sept: ANSI approved HL7 Version 2 Specification: Conformance, Release 1. PMO archived project. 2020 May: TSC approved Normative Publication Request for HL7 Version 2 Conformance Methodology Other Stakeholder and Vendors: Anyone implementing HL7 v2 or affected by HL7 v2 implementations. |
U.S. Govt Interest? | Yes |
USRSC Approval | Not Needed |
FMG Approval | Not Needed |
ARB Approval | Not Needed |
Start Date | Feb 13, 2018 |
* A Project Insight User ID and password is required to access Project Insight. Contact the HL7 PMO at for more information.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.