Date

20:00 UTC on Tuesday 29 May 2018 - 90 minutes.

Objectives

FHIR Terminology Services and Resources

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

@Dion McMurtrie, @Rob Hausam

Apologies

@Peter Williams, @Jane Millar

Meeting Recording

https://snomed.zoom.us/recording/play/JyQSiUkghYjmBAr2fsfiqpZqtpqbausYrU5zMpBV9yx9wLhUYQXXBiXgSUiXz4M-

Meeting chat:

00:36:17 Michael Lawley: Also, this thread is relevant: https://chat.fhir.org/#narrow/stream/48-terminology/subject/valueset.2Edesignation.2Euse.60.20for.20.60.2Etext.60
00:37:19 Peter Jordan: Apologies, have to leave to attend meeting at NZ MoH. Peter J
00:38:13 Michael Lawley: Specifically “The display in a Coding must be taken from the underlying code system definition”
00:40:48 Andrew Perry: A description may come from a local extension, published for example by a supplier in their namespace that may not be shared.
01:31:55 Michael Lawley: Relevant thread for the expansion and post coordination discussion https://chat.fhir.org/#narrow/stream/89-snomed/subject/SNOMED.20CT.20filters

Discussion items

	Description	Mins	Owner	Notes & Actions

	Description	Mins	Owner	Notes & Actions
1	Welcome and introductions	5	@Rob Hausam	Recording + Notes.
2	Summary of previous week	5	@Rob Hausam	2018-05-22 - SNOMED on FHIR Meeting (TB)
3	$validate-code behaviour	20	@Dion McMurtrie
4	Main item for discussion	60	@Dion McMurtrie	SNOMED CT canonical CodeSystem resource Review and attempt to resolve detail questions Issue around extensions and what this CodeSystem resource actually represents
5	Current items	10	@Dion McMurtrie	SNOMED CT "Universal" Edition Definitely useful to have a catalogue of all concepts ever issued if not a proper edition which may be much harder? Is this work for this group, or should this be handed on to a more appropriate SI group? Check and fix ECL in the FHIR spec Is there a way to systematically identify all ECL expressions in the FHIR spec? If we run these through validation is there appetite/volunteers to review and fix them as feedback to the spec? Is there a way to integrate ECL validation into the FHIR spec tooling to prevent recurrence? @Rob Hausam to progress Michael's tracker item on this issue. Normal form and normal form terse definition @Rob Hausam to progress returning NormalFormTerse to the page. @Former user (Deleted) to progress defining Terse Normal Form with the Family of Languages group (@Rob Hausam confirms needed for July) SLPG agreed that the Languages group is not the appropriate forum for this definition. Instead, we believe this should be defined in the DL subgroup of the Modelling Advisory Group. Also agreed that the terms that need defining are "Canonical Normal Form" (which is terse by definition) and "Necessary Long Normal Form"
6	Review of "Using SNOMED with FHIR" page	5	@Dion McMurtrie	All participants are invited to review this local copy of that page. Section 4.2.1.0.5 suggestion that we terse Normal Form properties (Peter J disagreed). Clarity needed on which Normal Form is being represented (eg breaking sufficiently defined concepts down to their primitive components, unlike what is supplied in the browser). Further discussion needed on what these properties are being used for. Perhaps only 1 is necessary since terms can be added/removed as required Supplements are a possible way to allow language reference set type functionality.
7	Review of TS Collaborative Work	5	@Dion McMurtrie	Collaborative Work
8	Any other business			Next Meeting: Tuesday 12 June Questions for next week:

Meeting Files

	File	Modified

No files shared here yet.

2018-05-29 - SNOMED on FHIR Meeting (TS)