Objective: Any change requests for V2 vocabulary (table content) or V3 vocabulary (coremif code systems and value sets) will only be able to be processed using this new system in preparation for the May 2020 ballot cycle.
Prerequisite: As a prerequisite for beginning the Pilot, the first published official release of the HL7 terminology using the new formatting and process is required. This release will carry the initial HL7 Terminology version ID of 2.0.0 and its availability will be announced to the cochairs list.
To participate in UTG Pilot testing please email email@example.com.
Specific named individuals are being identified that will submit change request proposals. These people must have:
- A login to the HL7 JIRA production server environment; this login account will require UTG Submitter permissions.
- Ability to install software on their computers; in order to submit proposals, tools to edit the HL7 vocabulary resources and to manage the change branches in the GIT repositories requires client side software to be installed and configured.
- This software consists of:
- VocabTx server
- Instructions for downloading and installing the tooling may be found HERE.
Everyone that wishes to review, comment on, and vote on change requests to also get a UTG JIRA account; this account must have UTG Reviewer permissions. Please contact Joshua Procious at firstname.lastname@example.org (and CC Jessica Snell at email@example.com) to get set up in JIRA.
Robert Hausam Unifty ObservationInterpretation
John Moehrke IHE
Sheila Abner HSLOC
Ted KleinCorrect URL and metadata information for NANDA
Jessica SnellCorrect 'steward' UTG property
Proposals are submitted on the HL7 Jira system: jira.hl7.org (in the UP project)
Current build content may be browsed at https://build.fhir.org/ig/HL7/UTG/index.html
Documentation located on UTG Tooling and Proposal Documentation (download the Word Document)
Walk through submitting your proposal using the UTG process and tooling. Note any issues or documentation deficiencies.
Reported issues are listed in the table below with any appropriate comments from the UTG team
|Issue Reported||Reporter||Status||UTG Team Comment|
|Needs to be easier to find V2 Tables||Craig|
In addition to having this on our Background pages, a paragraph describing it will be put on the main tab text under CodeSystems->V2
|Clicking 'Clone in Sourcetree' doesn't work until the user logs in to the Sourcetree app||Craig||DONE||Need to document this for first time users|
|Provide guidance for naming cloned repository (i.e. UP-66)||Craig||DONE||Need to update in documentation|
|Sourcetree keeps asking for credential helper||Craig||Need to look into settings to see how to avoid this|
|Error installing FHIR Toolkit||Craig||Known issue with FHIR R4 toolkit (to be addressed)|
|Clarify documentation for cloning a branch to select the proposal branch (not master)||Craig||DONE|
Probably make it step 20b (or part of 20a) rather than 21.
|Need better explanation for adding 'cda' folder (this is a temporary work around)||Craig||DONE|
IMPORTANT: There is a bug with the Vocabulary Server that requires creating an empty folder labeled “cda” in the downloaded UTG Source of Truth content. Add the empty folder to the ‘sourceOfTruth’ folder prior to starting the Vocabulary Server. The folder path location should be like: C:\Users\username\Documents\UP-65\input\sourceOfTruth\cda.
|Unable to see diff in Sourcetree||Craig||Attempting to reproduce|
|May want to add documentation about making multiple changes in parallel||Craig||While multiple changes in parallel (multiple instances of UTG Editor and Vocab Server) are possible, we might want to encourage users to start with one instance at a time. Advanced users will likely go ahead and do this anyway if needed.|
|Fix 'ValueSet' tab on build pages||Jess||DONE||ValueSet should be Value Set for consistency|
|Difficulty Navigating to object in Proposal||Craig||The 'Published Example' link brings you to the Home page for a proposal branch. It can be difficult to figure out where to go to find the modified object.|
|Need to Document Concepts||Craig||Does not exist on build pages or Word doc|
|Need Better Definitions for Properties, including type of property||Craig||List needs to be extracted, reviewed, and documented.|
|Need Documentation for Removing Code Systems and Value Sets||Ted||DONE||This involves editing lists.|
|Need Documentation for Adding Code Systems and Value Sets||Jess||DONE||This involves editing lists.|
|Slashes in branch name cause build to fail||Bryn||DONE||Document that no slashes should be used in the branch name. Characters that are valid in the URL are OK.|
|Voting issues with 'Other' Proposal Types||Carmela||DONE||Did not display voting requirements and groups. This was not an issue with 'Other' but rather linking tickets in Jira.|
|Issue Selecting 'Enumerated' Rule for Value Sets in UTG Editor||Carmela||Clicking in the Radio button does nothing, but if you click on the word 'Enumerated' it let's you add codes. Once you add codes it moves it to the 'Selected' radio button even though it is still enumerated. The available area for the Enumerated section needs to be a little taller as you can't tell you have the option to add codes.|
|Not able to see Development section in Jira to create branch||Joel||This is a permission thing that has to do with the first time a user is set up with a Jira login. They must choose to allow Jira to communicate with BitBucket. Instructions need to be noted in the documenation.|
The following tickets were made as part of the Pilot test and demonstrate pushing a proposal through the UTG Jira workflow: