Page tree


20:00 UTC on Tuesday 23 January 2018 - 90 minutes.


  • FHIR Terminology Services and Resources

Discussion items



OwnerNotes & Actions
1Welcome and introductions5

Recording + Notes.

Requests for calendar invites to

Session at April Business Meeting ( 8 - 11 April ) Wed?

2Summary of previous week5
4Review of "Using SNOMED with FHIR" page5

All participants are invited to review this local copy of that page prior to our next Terminology Services meeting. 

  • Jane Millar please adjudicate on use of IHTSDO vs SNOMED International. Answer: Legal documents should refer to "IHTSDO". User documentation should use SNOMED International.
  • Rob Hausam advise on time lines and channel for response
  • All comments to be received by 31 January 2018
5Deprecated SNOMED RT Identifiers10

See URIs antecedent SNOMED versions . RH previously asked "Can we have this in place for the (late) May ballot? Languages group meeting next Wed - 17th."


This weeks Star Topic


Attempt to achieve conclusion:

7Terminology Capabilities10

Overlap with FHIR Server capabilities / CodeSystem resource?

How do we determine for a given FHIR Server which code systems and versions are supported?

  • Sufficient to query the code system resource ? Is not considered sufficient (due to possibility of declared resources not being operationally implemented, ie used for simple storage). Could instead be declared in a capability statement.
8Review of proposals for possible Terminology Services and Resources collaborative work10
9Topic for next meeting5

Plan for following fortnight:

CodeSystem.Supplements (ReubenD) eg descriptions in additional languages. Question over what is permissible under SNOMED licence conditions.

Feedback from HL7 Meeting / Connectathon

10Any other business0


Meeting Files

No files shared here yet.