UTG Overview. Spring, 2018

Transcription

1 UTG Overview Spring, 2018

2 Unified Terminology Governance Project Ø Began over 3 years ago Ø Initial architecture approach was developed Ø Proof of Concept built on FHIR Tooling and JIRA Custom tooling being developed JIRA workflows and screens Ø Contract let to develop working Prototype based on the POC Ø Work has been underway since late 2017 on the Prototype 2

3 Crowd-Sourced Process Architecture 3

4 Continuous Process Ø Each Vocabulary Object Done Separately Related objects can be grouped together Ø Change requests can be submitted any time Ø Workflow runs on a submission-by-submission basis Ø Consensus is attained on a numeric basis rather than on a calendar schedule Ø Once approved by the stakeholders, the HL7 Terminology Creator updates the source of truth and posts the updates Ø Sets of updates are identified as a group for publishing purposes 4

5 Process Architecture updates Maintain Terminology changes harmonization Submit change requests voting HL7 Community Terminology Store Extract process Publish. Download, or View terminology Change is needed to HL7 Terminology Apply approved proposal using tooling updates Submitter Terminology Curator Validate/monitor/triage Completed Proposals and Endorsements Store Submitted Proposals Consensus Pool Out for voting to achieve consensus on submitted proposals Create and Submit completed Proposal for additions or changes to HL7 Terminology controversial Legend RED automated BLUE Tooling supported GREEN manual Parallel Processes APPROVED QUEUE Approve consensus Reject/Expire Document result High Level Architecture of Unified Terminology Governance Process 5

6 Content Architecture ØPersisted Source-of-Truth on HL7 Servers Content represented as FHIR resources with extensions Primary focus is on HL7 defined and published content Value Set Definitions and Code Systems (Tables) Convenience copies for content maintained and distributed by those outside of HL7 ØEditing tools run against any FHIR Terminology Service anywhere 6

7 Functions Architecture ØVocabulary editing and extraction based on custom FHIR-based tools ØRun against against any FHIR Terminology Service anywhere ØHL7 JIRA instance for workflow ØHL7 Confluence instance for consensus management 7

8 WorkFlow Management ØImplemented as a JIRA workflow Many custom changes to support HL7 needs ØCustom screens and fields for submission of requests for additions and/or changes to the HL7 vocabulary ØLeverages workflow designs being developed to use JIRA for HL7 Ballot workflow 8

9 JIRA Workflow 9

10 Proposal Screen (ODH Example) 10

11 Consensus Management ØImplemented using the HL7 Confluence instance ØCustom screens and fields and macros to implement an HL7 vocabulary maintenance consensus process ØLeverages work being done by the project implementing HL7 Ballot consensus processes in Confluence 11

12 Ø Content Set FHIR-Based Storage Product Family Specific V2, V3, CDA, FHIR, CIMI External Vocabulary convenience copies LOINC, SNOMED CT, WHO vocabularies, VSAC, PHIN (US CDC), ISO, Art Décor Extensions to resources to model the idiosyncratic details in the different product families E.g. V2 Tables, V3 Concept Domains Extensions to resources to support governance and extraction operations 12

13 Ø Tools to Operate FHIR-Based Tools Freely available, both Windows and OSX Terminology Server instance that may be run locally Editing Functions Both Community users and HL7 Terminology Curator Edit/Expand Value Sets, Edit Code Systems Extraction Functions For publishing HL7 artifacts For community users to pull HL7 vocabulary To push updates to external stakeholders who maintain their own convenience cipies of HL7 material Update Functions (Terminology Curator) HL7 update of external content 13

14 Current State Ø Calls continue every 2 weeks, plus sessions at all WGMs Ø JIRA space setup for the prototype UTG Prototype based on JIRA Service Desk Scheme Workflow implemented in this space Ø Initial screens to capture harmonization data have been created Need additional fields, controls Ø Architecture for up-front operations being designed Extracts for publishing and feed of external HL7 sources Setup environment Sign up as a submitter 14

15 UTG Next Steps Ø Finalize persistence model and move to the HL7 server environment Refresh content with current HL7 release Ø Update PoC tools for changed persistence model Ø Integrate hand-off between JIRA and Confluence for consensus discussions Ø Design up-front operations and screens to support them Sign up as a stakeholder with role(s) Prepare environment, download/install tools Help screens 15