Project Summary for V2 Publishing Database Upgrade
Visit Project Insight to see the full project details. *
Project Details
Number | 905 View Ballot Items List (with NIBs) |
---|---|
Name | V2 Publishing Database Upgrade |
Sponsor(s) | Publishing Work Group |
Co-Sponsor(s) | PEST Work Group |
Steering Division | Organizational Support |
Description | To upgrade the V2 Publishing database and integrity scripts. |
Project Facilitator | Jane Daus, Sandy Stuart, Brian Pech |
Status | Archived |
SD Approval Date | Jul 9, 2012 |
TSC Approval Date | Jul 26, 2012 |
Type | - Other - |
Objectives / Deliverables | Research quality of existing database and analyze existing integrity scripts (determine if we need to move to different technology such as SQL) - Target: May 2013 (Orig: Sept 2012 WGM) Perform Upgrade - Target: Sept 2013 (Orig: January 2013 WGM) Perform test of upgrade, analyze results - Target: Dec 31, 2013 (Orig: February 28 2013) Perform clean up of results from test upgrade - Target: March 2014 (Orig: May 31, 2013) Project End Date - upgrade complete and ready to use - Target: May 2014 (Orig: Sept 2013 WGM) |
Next Milestone Date | 2017 May WGM |
Project End Date | 2017 May WGM |
Project Intent | New/Modified HL7 Policy/Procedure/Process |
Project Need | The current V2 Publishing database is an access database that is updated per V2 ballot; integrity scripts exist which are out of date and need to be upgraded to help streamline publishing of the V2 standard and improve the quality of publishing ballots as well as the standard. Often there are inconsistencies between V2 chapters such as code tables, element definitions, and field lengths. Also we currently have only one resource with the expertise needed to run the integrity scripts, which is complex and time consuming. |
Implementers | |
Security Risks | |
External Drivers | |
Common Names / Keywords/ Aliases | |
Lineage | |
Dependancies | Resources and budget dollars available for the research, upgrade, testing, and final implementation. |
Project Document Repository | |
Backwards Compatibility | Yes |
External Vocabularies | |
Products | V2 Messages-Clinical; V2 Messages-Departmental |
Joint Copyright? | |
External Pjt Collaborators | |
Realm | Universal |
HL7 Affiliate | |
Stakeholders | N/A |
Vendors | N/A |
Providers | N/A |
Ballot Cycle Info | |
Misc Notes | 2018 Feb: BPech: Publishing did a review of all its opened projects at the WGM in New Orleans -- V2 Publishing Database Upgrade (905) can be closed. PMO archived project. Dec 2014: BPech: still ongoing, dependent on availability of Frank Oemig and Lynn Lasko, please move next milestone date to 2015 May WGM, project end date 2016 Jan WGM Oct 2012: Updated target dates per B. Pech 3.g. Backwards Compatibility: The output of the standard should be backward compatible after the upgrade is complete. 5. Project Intent: To provide an updated database for the V2 standard to improve integrity scripts and automate them. 7.a.Stakeholders: other: all Work Groups associated with the V2 Standard |
U.S. Govt Interest? | |
USRSC Approval | |
FMG Approval | |
ARB Approval | |
Start Date | Jun 19, 2012 |
* 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.