This wiki has undergone a migration to Confluence found Here

2017-08-15 TermInfo Project Call

From HL7Wiki
Jump to navigation Jump to search

Return to TermInfo Project Meeting Agendas and Minutes

Meeting Information

TermInfo Project Conference Call

Web meeting (phone number are available for call-in if needed):

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

Date: 2017-08-15
Time: 4:00-5:00pm ET (20:00-21:00 UTC)
Chair Rob Hausam Scribe Rob Hausam
Attendee Name Affiliation


Rob Hausam Hausam Consulting LLC
Linda Bird SNOMED Int.
Peter Jordan
Daniel Karlsson

Apologies: Carmela Couderc


Agenda

Agenda Topics

  • Announcements
  • Agenda review
  • Minutes (as available)
  • Review action items (send any updates in advance!)
    • Update TermInfo Wiki and HL7 TermInfo project site information - some progress being made
  • Update on status of SNOMED CT - FHIR collaboration
    • No new information on funding for HL7 work
    • The situation remains that there is no funding allocated for specific work at this time in either organisation. We therefore want to build on the opportunities of sharing and contributing that started to emerge on the call.
    • Discussion forum on SnoChat - Linda will send next few days
      • Confluence (snomed.org/fhir)
    • Face to face session in Bratislava
  • Proposal for SNOMED+FHIR profiles for implementers with varying levels of proficiency (from Daniel)
    • I would like to propose the need for SNOMED+FHIR profiles for implementers with varying levels of proficiency. While some (few?) will be able to manage transformations between different, isosemantic, binding alternatives, it can be assumed that at least some (most?) will not. Thus, having one profile which does not require any transformation, having one and only one way to safely use SNOMED, and other compatible profiles where safe transformations can be applied for those who are able with still a limited number of guaranteed safe ways of using SNOMED. For example with the AllergyIntolerance resource, one profile might require that only clinical findings are used for the code attribute while other profiles might allow a choice between findings and substances and products (together with transformation rules that guarantee safe interpretation of all allowed SNOMED uses).


  • Future item: Review and update TermInfo PSS
    • Consider once project decisions are made

Supporting Information

Minutes

Prior Action Item Follow-up

Adjourn

Adjourned at 17:16 Eastern (21:16 UTC).

Linda - TermInfo tends to be a subgroup of SNOMED Int. - so we should be aware Linda shared notes from joint meeting 22nd June Australia - Dion - Wants work to go ahead Netherlands - Alexander Henket Canada UK - 1 or 2 people NZ

Some people have been contacting Jane

timelines - list of normative resources? - check maturity levels operations may have different levels of maturity

CodeSystem ConceptMap

should SNOMED Int host FHIR SNOMED IG? - not needed since on Git and FHIR build IG implementation is on GitHub

prioritize - building blocks Observation vs CodeSystem, ValueSet

Daniel - multiple level profiles Linda - e.g. Condition resource force pre-coordination? use expression constraints - finding site, etc. Daniel - might disallow bodySite, require pre-coordinated concept added to SNOMED extension? have at least one profile that does not require any further processing to interpret

expression constraint - e.g. exclude severity

Peter - give expressions to create on terminology server

Meeting Outcomes

Actions
Next Meeting/Preliminary Agenda Items
  1. Agenda review
  2. Approve previous meeting minutes

© 2012 Health Level Seven® International. All rights reserved.