Recording + Notes.

 Requests for calendar invites to pwi@snomed.org

Discussion of best day for call.

Summary of previous week

Group approach to working

Ways of working:

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

• Generic binding principles

• Collection of profiles, bindings, etc.

• Relation to the “terminology services and resources” group

• Approach to Implementation Guide

• Meetings

• Biweekly (en_US) teleconferences

• Face-to-face

• at SNOMED International Business meetings

• at HL7 WGMs

Status of Resources wrt maturity and balloting.

Prioritisation

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

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

Bindings to FHIR Clinical Resources collaborative work

See Collaborative Work :

• ConceptMaps for FHIR code systems to SNOMED CT

Plan for following fortnight

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