Page tree


20:00 UTC on Tuesday 17 July 2018 - 90 minutes.


  • Bindings to FHIR Clinical Resources (e.g. value set bindings)

Meeting Details


Phone: See for available phone numbers (meeting id 242-348-6949)

Chat: #snomed-on-fhir

Discussion items



OwnerNotes & Actions
1Welcome and introductions5

Recording + Notes.

Swapping weeks when missing a week eg July 24.

Face to Face slot at the Vancouver Business Meeting (as well as an Expo slot).

NB Next Meeting Tuesday 7 August 2018 due to skipping 24 July. Week about will change - expect calendar invites.

Peter off July 31 (TS) & Aug 7 (TB) Jane Millar Linda Bird please record.

2Abstract for Expo Presentation5
  • Check slot for Jeremy's presentation.
  • Check timing for working meeting possibly after presentations.
  • Jane Millar collate all FHIR Presentations. (UK, SI, 3rd Slot)

Summary of previous week

4Medication Resource10

Any closing remarks?

Note: Original presentation including options for dealing with Code vs deconstructed fields: SNOMED on FHIR Meeting (20171017).pptx

  • Peter Sergent to follow up on MedicationAdministration - will it move to use the new complex "Dosage" datatype?




v3.4.0 (publication Aug 19?)



Neither of these exist in the FHIR 3.0.1 Spec. Rob Hausam


  • What determines which FHIR resource to use: the location of the data item in the sending system’s information model, or the semantics of the particular code regardless of where it was found? Some hybrid of both?
  • If the resource to be used is determined at least partly by the location in the sending information model, how does a requesting system cope with the fact that different implementations (or different users of the same implementation) both can and do secrete essentially the same clinical info in very different parts of the host information model?
6Next meeting5

NB Tuesday 7 August 2018

Meeting Files

  File Modified
Microsoft Powerpoint Presentation FHIR Resources - Procedure or Referral Request And Observation.pptx 2018-Jul-17 by Jeremy Rogers


Previous Meetings

No content found.

1 Comment

  1. Here are my brief slides on the question of how the act of referring a patient can currently be plausibly coded in SNOMED CT, and how the three coding patterns currently available could make it more of a challenge to query a real individual patient EPR in order to ask the question 'what referrals does this patient have currently in flight?'