Date/Time

20:00 UTC on Tuesday 27 March 2018 - 90 minutes.

Note that Europe moves into Summer Time on 25 March

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: https://chat.snomedtools.org/channel/snomed-fhir
(instructions and guide here - Getting Started with Rocket Chat)

Attendees

@Rob Hausam, @Peter Williams,

Apologies

@Daniel Karlsson

Meeting Recording

Discussion items

	Description	Mins	Owner	Notes & Actions

	Description	Mins	Owner	Notes & Actions
1	Welcome and introductions	5	@Peter Williams @Rob Hausam	Recording + Notes. Europe moving to summer time. Call will now finish at Midnight in CEST. Next TB meeting will be during the SI Business Meeting, see 2018-04-11 - SNOMED on FHIR Meeting (TS & TB) @Peter Williams remove invite from calendar, add invite for the Wednesday.
2	Summary of previous week	5	@Peter Williams @Rob Hausam	Summary of previous week: 2018-03-20 - SNOMED on FHIR Meeting (TS)
3	Profile for Specimen Resouce	65	@Rob Hausam	Specimen binding Suggestion from @Jim Case that the type attribute would be better bound to (< Substance plus < Morphologic Abnormality plus < Physical Object (or selection thereof)) rather than Specimen as it avoids any potential conflict with the other attributes and is effectively opening up post coordination, rather than sticking to a inherently restricted set of pre-coordinated concepts. Similarly (@Former user (Deleted)), the method attribute is currently a selection of SNOMED CT concepts plus a V2 valueset. Two main options: Use Specimen hierarchy for "type" and then constrain what can appear in the other fields (and how we deal with conflict!) Put all information into a post coordinated expression in the "type" attribute (@Jim Case noted that some aspects - like the shipping container - may not be characteristics intrinsic to the specimen). @Jim Case also suggested that using these decomposed fields would only be used outside of a SNOMED context. Otherwise could be achieved - (PWI: more safely due to MRCM) - with post coordinated. @Rob Hausam to seek opinion from Riki Merrick
4	Condition Resource	TBD	@Linda Parisien	Condition Resource All please review the above page
5	ValueSets	10	@Daniel Karlsson	How do we produce and publish ValueSets? Tools? Question for @Daniel Karlsson - Were you suggesting that we systematically replace HL7 ValueSets with SNOMED CT equivalents? Or are there places where ValueSets are required that aren't currently specified?
6	Next meeting	5		Both streams - Wednesday 11 April 12:30 - 15:30 UTC Face to Face in London, or usual Zoom details.

Meeting Files

	File	Modified
Labels No labels Preview View	Text File meeting_saved_chat.txt	2018-Mar-22 by Peter Williams

Previous Meetings

Title	Creator	Modified
No content found.

2018-03-27 - SNOMED on FHIR Meeting (TB)