2018-04-17 - SNOMED on FHIR Meeting (TS)

2018-04-17 - SNOMED on FHIR Meeting (TS)

Date

20:00 UTC on Tuesday 17 April 2018 - 90 minutes.

Objectives

  • FHIR Terminology Services and Resources

Meeting Details

Onlinehttps://snomed.zoom.us/my/snomedhl7

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

Chathttps://chat.snomedtools.org/channel/snomed-fhir
          (instructions and guide here - Getting Started with Rocket Chat)

 

Attendees

@Rob Hausam@Peter Williams@Former user (Deleted)@Anne Randorff Højen@michael lawley@Peter Jordan, @Former user (Deleted)@Reuben Daniels@Yongsheng Gao

Apologies

@Dion McMurtrie

Meeting Recording

https://snomed.zoom.us/recording/share/QjMkCcRBTwlbNbOl-oDb1q5GndZfUgcm4ge_dFjq8LawIumekTziMw 

 

Discussion items

Description

Mins

Owner

Notes & Actions

Description

Mins

Owner

Notes & Actions

1

Welcome and introductions

5

@Peter Williams

@Rob Hausam

Recording + Notes.

 

2

Summary of previous week

5

@Peter Williams

@Rob Hausam

@Dion McMurtrie

@Jeremy Rogers

@Daniel Karlsson



3

New items

 

 

  • SNOMED CT "Universal" Edition

  • SNOMED CT canonical CodeSystem resource

  • Check and fix ECL in the FHIR spec

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

4

Review of "Using SNOMED with FHIR" page

 

60

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

5

Review of TS Collaborative Work

20

@Dion McMurtrie

Collaborative Work

6

Any other business

0

@Peter Williams

 

 

Meeting Files

  File Modified
No files shared here yet.

Copyright © 2025, SNOMED International