SNOMED on FHIR

Space shortcuts

Page tree

Versions Compared

Old Version 1

changes.mady.by.user Peter G. Williams

Saved on

compared with

New Version Current

changes.mady.by.user Peter G. Williams

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date/Time 

20:00 UTC on Tuesday 21 August 2018 - 90 minutes.

Objectives

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

Meeting Details

Online: https://snomed.zoom.us/my/snomedhl7

Phone: See https://zoom.us/zoomconference for available phone numbers (meeting id 242-348-6949)

Chat: snomedIntl.slack.com #snomed-on-fhir


Attendees

Rob Hausam, Jeremy Rogers

Apologies

Peter G. Williams

Meeting Recording

Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions5

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).

2Abstract for Expo Presentation5

Jane Millar

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

Summary of previous week


5

Rob Hausam

Summary of previous week:

4Vital Signs

Vital Signs Resource

Jeremy's work to compare Vital signs profile and SNOMED Subhierarchy - issues with eg blood pressure. Complex expression constraints available which cover the use of observables by the NHS(UK). Mapping to LOINC codes.

5

v3.0.1

ProcedureRequest

ReferralRequest


v3.4.0 (publication Aug 19?)

ServiceRequest

60

Jeremy Rogers

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?
56Nextmeeting5

Rob Hausam

Tuesday 4 Sept 2018


Meeting Files

Attachments


Previous Meetings

Content Report Table
maxResults12
showCommentsCounttrue
spaces@self
labelsmeeting-agenda