Skip to end of metadata
Go to start of metadata

Attendance can be found Here

Co-Chair and Key Participant information can be found on the Agenda found Here

Discussion items



Meeting started

Jim Case



Ted Klein

Ted explained the workflow for the UTG process and where the different tooling fit into the process and the output from the process.

The consensus group and voting processes and weighting is in document .

Ted Klein to provide a link on the main UTG page in confluence for this document.  Project Documents on confluence is not currently linked but ted will update this as well. will be the location of the tooling and documentation.

There will be browsable terminology content irrespective of the publication in which the content is included. The FHIR infrastructure will be leveraged to deliver content for community access.

For external terminologies there are downloadable files for internal and external terminologies.

Ted demonstrated the tools to be used which are JIRA assocaited tooling. It was also reported that we are obtaining vocabulary content from Trifolio for non VSAC CDA information.

External is a set of manifest lists, published in a similar manner to FHIR resources. These include things that HL7 need to be aware of that might be sited in our documents.

There is a need to consider how references to content in VSAC need to be further investigated

  • understand the use cases
  • how will the links be maintained and updated appropriately
  • what should be the processes used?

This discussion is welcome at the UTG calls.

Rob McClure to establish a page on the UTG site to document external code system functional and policy issues for further consideration and development.

9:32UTG toolsTed Klein

There are two JIRA sites - one for development one for 'source of truth'data. Prototype available.

Ted demonstrated the system prototype. The tooling includes:

  • proposal submission / withdrawal
  • manual review of submissions
  • concensus review
    • chain of comments and vote buttons will be included to track the process in detail
    • send back, send out for meeting, abandon, send to implementation actions included.
    • implementation sends the work to the ''source of truth'' maintenance process
  • Release will either be all current content, or individual release of resources (similar to the FHIR process). To find out what was in the relase 5 years ago - you go to the release manifest for that time which will be able to identify what was included at that time.

Publishing discussion on Wednesday will cover how the community will get access to content and link to published documents.

The process for submisison and current issues were explained. The system use online forms linking the content request to the part of the HL7 family to which it relates or if a change request for an external terminology (which will forward to HTA processes).

Not everyone will be able to access or download (due to local firewalls etc). The UTG team have investigated running on the HL7 servers but point to you rlocal copy of the content to make it work. How to prepare a proposal is a known issue but is being tested. This supports pointing to local version of proposal or content.

There is a SNOMED cache file to assist working with the latest SNOMED CT (international) release

The process for proposal drafting, submission and review were explained.

The editor processes particularly for content editing in hierarchies and subsumption implementation tooling were discussed and further discussion is needed to clarify that the intended process will meet needs.

The progress of the UTG project is encouraging and the next stage will be the to pilot the project.

IF you have further questions or want to know more, see the UTG page, and/or join the UTG calls These calls ahve been on Tuesdays - see the UTG confluence page.

Action items

  •  Ted Klein to provide link on the main UTG page in confluence to relevant documents for UTG process etc.
  • Rob McClure to establish a page on the UTG site to document external code system functional and policy issues for further consideration and development.
  • No labels