Page tree

Date/Time 

20:00 UTC on Tuesday 4 December 2018 - 90 minutes.

Objectives

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

Meeting Details

Onlinehttps://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


Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions5

Recording + Notes.

2

Summary of previous week (TS) and previous TB


5
3Free SNOMED CT Set for FHIR80

Free SNOMED CT set for FHIR

  • Are the mappings suggested complete and ready as a recommendation?
4AllergiesXRevisit any outstanding questions on Allergies.
5Vital SignsXDaniel Karlsson

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.

See Spreadsheet attached to: SNOMED on FHIR Meeting (TB) - Tuesday 21 August 2018

Issues / Discussion :

  • Normative vs. descriptive purpose - 1, 2, or 3 profiles?
  • Unresolved modeling issues

6

v3.0.1

ProcedureRequest

ReferralRequest


v3.4.0 (publication Aug 19?)

ServiceRequest

X

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

http://build.fhir.org/servicerequest.htmlServiceRequest

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?
7Next meeting5


18 December - Rob's Birthday


Meeting Files

No files shared here yet.



Previous Meetings

TitleCreatorModified
No content found.