This wiki has undergone a migration to Confluence found Here

Vocabulary Tooling - 28-June-2016

From HL7Wiki
Revision as of 20:53, 28 June 2016 by Rhamm (talk | contribs) (→‎Agenda)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Minutes 28-June-2016

Call to Order

  • Ted Klein
  • Rob Hausam
  • Russ Hamm

Agenda Check

  • No Changes


  • No announcements.


  • This call at 4:00PM Eastern overlaps with FHIR Methodology, and as such needs to be rescheduled to accomodate attendees on that call.
  • Russ to set up a Doodle Poll to reschedule thse calls.
  • Russ to reach out to SG and YW regarding interest in these calls.


  • Review objectives and schedule of tasks
    • Investigate suitability of FHIR vocabulary services for all HL7 product families. HL7 needs to converge its multiple silos of vocabulary maintenance tooling and persistence stores. The current VML, VMIF, MSAccess, and RoseTree tools need updates and maintenance, and we have limited ability to do this. In addition, any significant failure in these tools may cripple our ability to publish V3 ballots and the Normative Editions since we have limited ability to debug and fix the current tooling. The FHIR services and tools are actively being used, maintained, and enhanced, and it makes sense to investigate their suitability before seriously evaluating tooling outside of HL7. This evaluation will serve as input into the existing Vocabulary project 947, HL7 Vocabulary Maintenance Tooling.
  • Review of capabilities of current FHIR Terminology Service
    • Import capabilities, V2/V3/CDA
      • To our knowledge there is no publically facing API or set of functions that can perform imports of the HL7 vocabularies.
      • To our knowledge the only data format would be packaging existing terminology into FHIR resources and submitting them as FHIR resources to the terminology service.
    • Editing
      • Updates can be made to the CodeSystem and Value set resources as changes to the resource (as with any other FHIR Resource). This is a PUT/POST operation outlining the desired end state of the Resource. This creates a new version of the Resource (Resources are versioned).
      • To our knowledge, this would require the entire resources to be republished with each update.
    • Change tracking
      • Change tracking is on the entire Resource, not on individual components of the Resource.
    • Access (browser, etc.)
  • Gap alignment between FHIR capabilities and Tooling Requirements


  1. Draft of requirements -July 2016
  2. Updated FHIR value set editing tool - August 2016
  3. Initial MIF generation from FHIR resources tool - September 2016
  4. Draft of report with gaps - 2016 Sep WGM
  5. Addressing of gaps with FHIR team - Fall 2016
  6. Final report draft - December 2016