Page tree

Date

20:00 UTC on Tuesday 5 December 2017 - 90 minutes.

Objectives

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

Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions5

 Recording + Notes.

 Requests for calendar invites to pwi@snomed.org

Discussion of best day for call.

2

Summary of previous week


5

How many members only attending every two weeks?

See Review and maintenance of Using SNOMED CT with FHIR page

3

Group approach to working


20

Ways of working:

  • Binding to specific clinical resources, e.g. Observation, AllergyIntolerance

  • Generic binding principles

  • Collection of profiles, bindings, etc. Format of output?

  • Relation to the “terminology services and resources” group

  • Approach to Implementation Guide

  • Meetings

    • Biweekly (en_US) teleconferences

      • Representation from specific HL7 WG on this call?

    • Face-to-face

      • at SNOMED International Business meetings

      • at HL7 WGMs

4

Status of Resources wrt maturity and balloting.

Prioritisation

10

http://wiki.hl7.org/index.php?title=FHIR_Ballot_Prep#January_2018_Cycle

http://build.fhir.org/resourcelist.html

The current candidate list is:

  • Framework, XML, JSON, RESTful API, Search, Data types
  • CodeSystem, ValueSet, ConceptMap. (But not all operations on those resources)
  • Bundle, OperationOutcome, Parameters, StructureDefinition, SearchParameter, CapabilityStatement, OperationDefinition
  • Patient, Observation
5Binding to FHIR Clinical Resources20

https://docs.google.com/presentation/d/1F1feYMi1YG4Yus9EY6ZEkQ3bY7A-GjAjjXgUes9ftkc

6Review of proposals for possible

Bindings to FHIR Clinical Resources collaborative work

20

See Collaborative Work :

Plan for following fortnight

7Review of current relevant HL7 tracker items20

There are a number of trackers that may be relevant, either as specific items to discuss and provide feedback on, or just as context for understanding how/where there are existing binding linkages between FHIR elements and SNOMED CT:

AdverseEvent.event - binding to SNOMED CT Clinical Findings (Example) - inappropriate

AllergyIntoleranceType should be SNOMED - 2016-09 core #508

Review the IHTSDO recommendations for using SNOMED CT in Observation

SNOMED CT provides representation of required value set - 2016-09 daf #6

Michael Lawley says: There are more.  I found these simply by searching for "snomed" : GForge search for SNOMED

8Next TB meeting (19 Dec 2017)

Identify resources to be discussed. Location for profiles.

 

Meeting Files

No files shared here yet.


 

Previous Meetings

TitleCreatorModified
No content found.