Page tree

Date

20:00 UTC on Tuesday 28 November 2017 - 90 minutes.

Objectives

  • FHIR Terminology Services and Resources

Discussion items

ItemDescription

Mins

OwnerNotes & Actions
1Welcome and introductions5

 Recording + Notes.

 Requests for calendar invites to pwi@snomed.org

2Summary of previous week5
3Group approach to balloting20

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
4Review of proposals for possible Terminology Services and Resources collaborative work30

See Collaborative Work :

Plan for following fortnight

5Value set versioning25

CodeSystem, ValueSet and ConceptMap resource naming, identification and versioning

Relevant HL7 Specification: http://www.hl7.org/implement/standards/product_brief.cfm?product_id=437

6Deprecated SNOMED RT IdentifiersCFCarry Forward to 12 Dec

Current issue relating to old deprecated SNOMED International / SNOMED RT codes : https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14013&start=0 that SNOMED International and/or individuals may have a position on.

The specific thread that relates to this is https://chat.fhir.org/#narrow/stream/terminology/subject/SNOMED.20srt

7SNOMED IG hostingN/ALinked from _http://snomed.org/fhir/ig ?

 

Meeting Files

No files shared here yet.


 

Previous Meetings

TitleCreatorModified
No content found.

4 Comments

  1. Apologies - I'm unable to attend this week's meeting.

  2. Current issue relating to old deprecated SNOMED International / SNOMED RT codes : https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=14013&start=0 that SNOMED International and/or individuals may have a position on

  3. There are a number of trackers that may be relevant to next weeks call, 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

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