1

Welcome and introductions

5

@Peter Williams

@Rob Hausam

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 @Former user (Deleted) please record.

2

Abstract for Expo Presentation

5

@Jane Millar

• Check slot for Jeremy's presentation.

• Check timing for working meeting possibly after presentations.

3

Summary of previous week

5

@Peter Williams

Summary of previous week:

• 2018-07-10 - SNOMED on FHIR Meeting (TS)

4

Medication Resource

10

@Jeremy Rogers (Unlicensed)

Any closing remarks?

• Medication 3 See confluence discussion page: Medication Resource

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

5

v3.0.1

ProcedureRequest

ReferralRequest

v3.4.0 (publication Aug 19?)

ServiceRequest

60

@Jeremy Rogers (Unlicensed)

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

http://build.fhir.org/servicerequest.html → ServiceRequest

Questions:

• 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?

6

Next meeting

5

@Peter Williams

NB Tuesday 7 August 2018