This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201901 Terminology Services"

From HL7Wiki
Jump to navigation Jump to search
Line 28: Line 28:
==Track Administration==
==Track Administration==
Connectathon Management Tool: [ ConMan: WGM Baltimore September 2018]
Connectathon Management Tool: [ ConMan: WGM San Antonio January 2019]
Messaging & Communications: [ Zulip Chat Stream]
Messaging & Communications: [ Zulip Chat Stream]

Revision as of 06:57, 6 November 2018

Return to Connectathon 20 page Return to Jan 2019 Proposals

Terminology Services

Submitting WG/Project/Implementer Group

Vocabulary WG/FMG


The FHIR specification includes support for the provision of a terminology service - that is, a service that lets healthcare applications make use of codes and value sets without having to become experts in the fine details of the value sets and underlying code systems and their related resources. The management and proper use of terminology is fundamental to effective, interoperable data exchange, so this is an important capability to provide and test in the Connectathons.

David Hay's blog post on Terminology Services

Clinical input requested

Related tracks

Proposed Track Lead

See Connectathon_Track_Lead_Responsibilities Rob Hausam, Peter Jordan

Track Administration

Connectathon Management Tool: ConMan: WGM San Antonio January 2019

Messaging & Communications: Zulip Chat Stream

Test Support: Richard Ettema

Orientation Slides: Terminology Services Track Orientation Slides

Orientation Recording: Click here to play recording

Expected participants

  • Additional servers and clients


Please include information here regarding how much advance preparation will be required if creating a client and/or server.

FHIR Terminology Server

For service providers, implement the following operations from

Support additional capabilities:

Service providers are not required to implement all of this functionality - it's a lot to do. For new implementers, start at the top and work down (generally).

FHIR Terminology Client Consumer

Implement any one or more of:

  • Do a value set expansion of one of the value sets in the spec
  • Validate a code using the spec against a FHIR value set, a v2 value set, LOINC or SNOMED CT
  • Validate a code using the spec against a code system such as LOINC or SNOMED CT
  • Look up a display for a code (most appropriate for v2/FHIR conversion)
  • Translate a code from one value set to another, based on the existing value set and ConceptMap resources, and/or other additional knowledge available to the server
  • Maintain a client-side closure table based on server-side terminological logic
  • References to SNOMED CT and LOINC implicit value sets
  • Create (POST, PUT) ValueSet resources referencing in-line and/or external code systems

At least one server supports all of these operations and capabilities ( Other servers, including the Apelon server ( and the others listed above will support several of these operations and capabilities. For a list of functions supported by the Apelon Server, see the demo web app (, uid/pwd dtsadminuser/dtsadmin).


For all levels of testing the required pre-requisite is the fundamental requirement that all FHIR servers SHALL support the capabilities interaction.

The FHIR Terminology Servers under test are expected to have already downloaded and installed the required resources (Code Systems, Value Sets & Concept Maps).

Test Scripts

This track includes formal testing and reporting of test results utilizing a defined set of test scripts.

The TestScript and terminology content resources will be committed to the FHIR documents Github repository at: FHIR/documents/tree/master/connectathons Please contact Grahame Grieve if you require commit privileges to this repository; otherwise, you may forward your TestScripts and related artifacts to Richard Ettema who will get them committed.

Additional Resources:


Scenario Step 1 Name

Success Criteria:
Bonus point:


Security and Privacy Considerations