Unified Terminology Governance Process (UTG); Working Prototype and Pilot (includes debugging, testing and Project Management) (ONC/Grant Project)

Project Name
Unified Terminology Governance Process (UTG); Working Prototype and Pilot (includes debugging, testing and Project Management) (ONC/Grant Project)

Project Number
1377

Project Type

Product Family

Products

Project Intent

Ballot Type

Project Need

Objectives and Deliverables
FY24: UTG Integration (not ONC funded) A. Complete SSO integration with GitHub B. Deploy automated IG build result C. Document the architecture that has been implemented UTG Automation A. Finalize and deploy UTG automation improvements with GitLab into production FY2024: Continue Project management FY2023: Continue Project management FY2022: Continue Project management FY2021: Rollout FY2020: Pre-Production and GoLive 2019 March Amendment: A fully working system for UTG that will: 1. View the published content at terminology.hl7.org 2. Download files and setup their local environment to create proposals for HL7 vocabulary changes 3. Draft and submit proposals 4. Auto- and Manual Validation of completeness and correctness of proposals 5. Post the proposal for discussion and voting, including notification of watchers, emails to stakeholder groups, etc. 6. Creation of the proposal-specific voting pools and levels 7. Voting, summation of totals, comparison against levels, etc. 8. Upon collection of sufficient votes, queue for implementation, rejection, or return to submitter for rework 9. Implement approved changes in the Source of Truth (HL7 Git repository) using the UTG maintenance tooling 10. Commit update 11. Generate new current release of HL7 Vocabulary and publish to terminology.hl7.org 12. Generate new full release of all HL7 maintained UTG vocabulary 13. Generate new V3 release including coremif generation 14. Generate new V2 release including update to the v2 publishing tools 15. Mark proposal complete, notify submitter and participants 16. Show tracking and statistics for proposals in flight 17. Document usability issues, new requirements for full production, bugs, etc. 2019 FY Amendment: 1. Applicable programming code and documentation (via links to project pages, Github, and other sources) 2. Demonstrate a working pilot the week of January 13, 2019 at the January 2019 Working Group Meeting in San Antonio 3. Provide a summary report describing results of the prototype demonstration and defining next steps for completing and implementing UTG. 4. Provide status reports to the HL7 CTO and/or PMO upon request (most likely quarterly) In exchange for satisfactory and timely submission of materials as approved by HL7 and according to the agreed upon delivery schedule defined below, 1. Working Prototype in the HL7 JIRA and Confluence instances for UTG, along with the integrated value sets and code systems editing tools from Grahame Grieve. Demonstration of full lifecycle processing of harmonization proposals, although perhaps not all of the functions will be fully automated yet. Includes JIRA and Confluence templates and screens, dashboards, FHIR valueset and codesystem editors, and HL7 content store. 2. Interface to retrieve content for local creation of a proposal with the edited terminology from the download tools in the HL7 gitHUB environment where the UTG source of truth will be maintained. This includes the migration of the content and tooling install packages from Grahame's personal development server to the HL7 servers. 3. Interface to refresh content in UTG from the external sources such as VSAC, LOINC, SNOMED CT, and PHINVADS where some of the underlying code systems on which HL7 published value sets are built are maintained, and new releases are made available from. 4. Interface to push output for CDA and V3 content to Trifolia for generation of HL7 ballot IGs. 5. Documentation outline for how to operate the system, and how to maintain the JIRA environment for it; note will be an outline, not final full user documentation (as this is a prototype). 6. Outline of steps needed to proceed to production release. Additional scope added in April, 2018: Perform work as described below in Section 2 of the UTG Persistance Notes document: (http://confluence.hl7.org:8090/display/VOC/UTG+Persistance+Model+Notes): 1. Make design changes to the folder structure and the CodeSystem and ValueSet resources 2. Implement LIST resource entries for all content objects identified 3. Modify import code at: (https://github.com/grahamegrieve/vocab-poc) to insert into the modified resources; also fix the bugs and address gaps as noted 4. Perform the refresh of the content for the November 2017 harmonization cycle 5. Update the code system editor and value set editor tools to work with the modified resource design a) Validate that the resource being editable is actually allowed to be edited by the user (Role Based Access) b) Make sure the fields added from coremif in step 3 above are included for editing 6. Modify the code system editor and value set editor to prevent editing the content that is EXTERNAL and lock records during editing according to pre-defined edit rules.

Project Document Repository
On the HL7 Wiki Page titled: FHIR: Enhancing Implementation (ONC Grant Project) at: http://wiki.hl7.org/index.php?title=FHIR:_Enhancing_Implementation_(ONC_Grant_Project) https://confluence.hl7.org/display/VOC/Unified+Terminology+Governance+Project+%28U

Collaboration Efforts

Dependencies

Stakeholders
N/A

Implementers

External Drivers

Common Names

Lineage

External Vocabularies
N/A

Backwards Compatibility
N/A

Joint Copyright
No