2021-05-11 - SNOMED on FHIR Meeting (TB)

2021-05-11 - SNOMED on FHIR Meeting (TB)

Date/Time 

20:00 UTC on Tuesday 11 May 2021 - 90 minutes.

Objectives

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

Meeting Details

Onlinehttps://snomed.zoom.us/my/snomedhl7?pwd=UCtmRkdHZ3pVNDB1MnJuZmg2b3hUZz09

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

Zulip Chat: https://chat.fhir.org/#narrow/stream/179202-terminology



Attendees

 @Rob Hausam @Daniel Karlsson ,@Peter Williams

Meeting Recording

https://drive.google.com/file/d/15LU-afvkofZPCLizUay66OPkhEMqx_5S/view?usp=sharing

Discussion items

Description

Mins

Owner

Notes & Actions

Description

Mins

Owner

Notes & Actions

1

Welcome and introductions

5

@Rob Hausam

@Peter Williams

Recording + Notes.



2

Summary of previous week (TS) and previous TB

0

@Rob Hausam

@Peter Williams

2020-09-01 - SNOMED on FHIR Meeting (TB)

3

Future meetings

0

@Rob Hausam

@Peter Williams

HL7 Connectathon next week (GMT based) 18 - 19 May

4

Observation Profile with Symptoms

30

@Jay Lyle

@Daniel Karlsson

https://drive.google.com/file/d/1pgeT7c9zkxTgyeqHs_6SR96t1tjPY-Mp/view?usp=sharing

Previous SNOMED on FHIR Discussion: Observation binding

See also: http://build.fhir.org/observation-mappings.html

5

Negation, Null Flavours and Degree of Certainty

55

@Daniel Karlsson

@Jeremy Rogers

See discussion page:  Flavours of Null and Degrees of Certainty

See also https://build.fhir.org/extension-iso21090-nullflavor.html  (RH says not really used, see http://build.fhir.org/codesystem-data-absent-reason.html instead - note used for Observation and not Condition.   Also extension which allows for http://build.fhir.org/valueset-data-absent-reason.html 

Note that the context for "why is there no data here" could relate to either a clinical context eg patient was not asked, or could be a machine/system statement eg not applicable in this setting / not specified.   Note that this does not necessarily indicate a process failure.  Not asking a question could be the appropriate action.  Distinction could be made between question totally not applicable and question-could-be-applicable-but-choice-made-not-to-ask.

Also question of ICD-like NOS/NEC for distinct bucket counting (eg "Other" combined with free text element, see As Text)

TODO  IG should clarify uses of Null Flavours for specific contexts.

6

Next meeting





Suggested to review http://build.fhir.org/observation-mappings.html (check use cases for "fit for")

2nd Week of June?

Meeting Files

  File Modified
No files shared here yet.

Copyright © 2025, SNOMED International