Project Summary for Creating and Managing Data Type Flavors in HL7 v2.x Specifications
Visit Project Insight to see the full project details. *
Project Details
Number | 1397 View Ballot Items List (with NIBs) |
---|---|
Name | Creating and Managing Data Type Flavors in HL7 v2.x Specifications |
Sponsor(s) | Conformance Work Group |
Co-Sponsor(s) | Infrastructure and Messaging Work Group |
Steering Division | Infrastructure |
Description | When HL7 v2.x implementation guides are developed, data types often are (and should be) constrained to suit a particular use for a message element. Therefore, multiple specializations of a data type are required that necessitates a distinct specification and identifier. Each specialization becomes a data type flavor. Currently the various implementation guides create these data type flavors independently using their own style and naming conventions. Because of lack of coordination among the v2 authors, duplicate data type flavor definitions (in terms of requirements) are created with inconsistent naming conventions. This is problematic since the same requirements are being specified but in a different manner. There is an opportunity for HL7 to create a repository (library) of reusable documented data type flavors with consistent specifications and naming conventions. The project, in summary, entails:
1. Providing a methodology for creating data type flavors. 2. Creating an initial set of data type flavors that are currently in use in implementation guides and uses cases that indicate the intent of the data type. 3. Creating an HL7 repository to publish and manage the data type flavors (including Realm specific libraries) 4. A method for users to propose and submit new data type flavors (for consideration.) 5. A method for vetting and approving proposed data type flavors. [Responsibility of Conformance and InM, this is a profiling mechanism and so is in Conformance’s domain.] 6. Once a repository and publication of standard data type flavors are available, possibly requiring newly published HL7 v2.x balloted IGs to use published data type flavors when applicable. |
Project Facilitator | Craig Newman, Rob Snelick |
Status | Archived |
SD Approval Date | Mar 20, 2018 |
TSC Approval Date | Apr 11, 2018 |
Type | Ballot - STU to Normative |
Objectives / Deliverables | Submit for STU Ballot (First Ballot Cycle) - Target: 2018 May Ballot Complete STU Reconciliation - Target: 2018 Sep WGM Request STU Publication - Target: 2018 Sep WGM STU Period - 12 months - Target: 2018 Sep - 2019 Sep Submit for Normative Ballot - Target: 2019 Sep Ballot Complete Normative Reconciliation - Target: 2020 Jan WGM Submit Publication Request - Target: 2020 Feb Receive ANSI Approval - Target: 2020 Mar Project Close - Target: 2020 Apr On-going updates to Standardized library - consider as part of harmonization process: As another project |
Next Milestone Date | 2019 January WGM |
Project End Date | 2020 May WGM |
Project Intent | Supplement to a Current Standard |
Project Need | This project will provide the following benefits: - Single source of truth helps developers and implementers to create better and faster implementations of the interface. - Enforce clarity and consistency across implementation guides. - Validation becomes more standardized across implementation guides. - Supports re-usability. - Improve quality of implementation guides up-front as users try to use data types. |
Implementers | 1) NIST - Immunization Guide Authoring Management Tool (IGAMT) 2) HL7 v2 Implementation Guide Authors |
Security Risks | No |
External Drivers | Project has no external calendars or deadlines. Project is being tackled now on the heels of work to support ONC Certification in the US. ONC certification testing revealed the lack of clarity in the HL7 v2 guides, and better defining data flavors will help v2 implementation guide authors to write consistent, concise and clear requirements. |
Common Names / Keywords/ Aliases | Data Type Flavors Master Data Type Library |
Lineage | n/a |
Dependancies | n/a |
Project Document Repository | Confluence Under Conformance WG |
Backwards Compatibility | Yes |
External Vocabularies | N/A |
Products | V3 Messages-Infrastructure |
Joint Copyright? | No |
External Pjt Collaborators | NIST – National Institute of Standards. Federal agency with mutual interest; no formal MOU. |
Realm | Universal |
HL7 Affiliate | |
Stakeholders | Clinical and Public Health Laboratories, Immunization Registries, 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 | 2018 May Ballot Cycle Info: STU Ballot results: Met basic vote requirements. 16 Negatives to reconcile Document Name: HL7 Version 2 Specification: Data Type Specializations, Release 1 |
Misc Notes | 2020 May: PMO archiving 3-Year Plan item Other Stakeholders and Ventdors: 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 14, 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.