Terminology Service Task Force

Owned by Davide Sottara
Last updated: Apr 18, 2016

Scope:

Almost every clinical application leverages (coded) concepts from both standard, national and local terminology systems. 
The ability to look up concepts in a terminology system, to resolve the relationships between two or more concepts, the
expansion of a valueset definition, their maintenance across versions over time are but some of the basic operations that  
would be beneficial to the components and services supporting an application.

Candidate components include, but are not limited to:

  • Terminology system curation tools
  • Knowledge artifact authoring tools (e.g. rules, quality measures, etc..)
  • (Synthetic) Data curation tools
  • Data repositories implementing "semantic" queries (e.g. FHIR servers)
  • Knowledge execution runtime (e.g. CDS engines)
  • Data validation and conformance implementations (e.g. FHIR validation based on profiles)
  • Data Aggregation systems e.g. supporting dashboard-like applications
  • Data normalization / alignment / transreption, both offline and online 

Current action items:

  • Evaluate FHIR TS as a runtime API for applications
  • Evaluate candidate implementations
     
  • Work with the terminology content WG to define the "endorsed" content, if any 
  • Evaluate, provide feedback and assist with the evolution of the candidate specifications
    • CTS-2 consolidation roadmap
  • Define a test framework to validate the functionality of a candidate implementation for the purpose of use by an application

References and Links:

An initial email thread discussing the topic (Oct 29, 2015)