Skip to end of metadata
Go to start of metadata

This is the initial prototype Confluence page to describe the UTG (Unified Terminology Governance) process and operations at HL7.

On this page you will be able to sign up to watch different areas for proposals for changes in vocabulary related to those areas in order to be able to review the proposals, comment on them, and vote on them.

These pages will be developed based on community feedback throughout 2020 as we move towards being able to go live with this new approach to vocabulary maintenance at HL7.

Project Overview

HL7 maintains multiple terminologies - v2, v3, CDA value sets and FHIR. However, ongoing maintenance of these terminologies proved to be resource intensive and quite opaque to much of the community and thus a need for a  uniform vocabulary governance process or strategy across all the HL7 product lines was identified  As FHIR and associated implementation guides became more popular and as HL7 continued to grow, this was identified as an increasing issue.  There is a need to maintain the terminologies that support all of HL7’s products (v2, v3, FHIR, CDA, etc.) in a way that is responsive and improves quality while reducing the resources that both HL7 and its volunteers must put into the process.  As well, there’s a need for the process to align with the community’s expectations for a more modern, continuous peer-feedback related process. The UTG process intends to solve these issues.

The UTG process decreases the burden on HL7 resources by having the proposal submitter create and submit the content that they needed added, modified, or deleted in their own development branch (via BitBucket directly through Jira). Proposals are submitted using a Jira-based workflow that is open to the community (both submitting and voting). Automated checks and validations ensure that the content meets proposal requirements. The proposal goes through a consensus workflow to come to a resolution. If approved, the use of the Bitbucket branching allows simplified integration into the master repository.

The UTG project is scheduled to replace existing vocabulary maintenance processes (including harmonization) for HL7 internationally published normative standards in mid 2020. Additional information about project details, requirements, project management, and documentation can be accessed at the Unified Terminology Governance Project (UTG) Page

The second UTG session geared towards the HL7 community can be found below:

HL7 Education on Demand (free access):

HL7 YouTube:

UTG Content

Please see for the UTG landing page. 

The UTG resources are being rendered at This page contains the current versions of UTG content. Resource history is also be maintained on this page.

All of the Code Systems and Value Sets for the Code Systems that are not ballot-bound are maintained through this UTG process as of Q2/Q3 2020. For a list of ballot-bound Code Systems and Value Sets, click here (NEED TO fill out).

Proposal Workflow Summary

This section provides a high-level overview of the workflow process for submitting a proposal and participating in consensus review.

Please see UTG Tooling and Proposal Documentation for more details (this will undergo major edits prior to go live).

Proposal Submission

The steps below describe the process for submitting a proposal. More detailed information on the process is documented at UTG Tooling and Proposal Documentation (this area is not yet complete)

  1. Get access to HL7 Jira by requesting an account on
  2. Install required tooling (Vocabulary Server, UTG Editor, and Sourcetree)
  3. Draft the proposal (written information) on the UTG Jira Project
  4. Create and download a branch to edit content using Sourcetree
  5. Use Vocabulary Server and Editor to create content change(s)
  6. Commit content change(s) to branch using Sourcetree
  7. Submit proposal in Jira

Consensus Review

Anyone wishing to participate in the Consensus Review of proposals in flight is welcome to participate. No tooling is required to participate. Weights are voted and there are several requirements (i.e. votes from specific users and groups) that must be met for the content to be approved or rejected.

  1. Get access to HL7 Jira by requesting an account on
  2. Open issues can be viewed in the UP project on the UTG Jira Project
  3. Review details of proposal and view rendered version of proposed content via link on ticket
  4. Use comments to discuss the proposal if necessary.
  5. Vote Affirmative or Negative

If approved, the proposal enters the UPSM project to be published.

  • No labels