20:00 UTC on Tuesday 22 January 2019 - 90 minutes.
- Bindings to FHIR Clinical Resources (e.g. value set bindings)
|Owner||Notes & Actions|
|1||Welcome and introductions||5|
Recording + Notes.
|2||Face to face meeting at the April Conference||1|
Sunday 7 April 13:30 - 17:00 UTC
Summary of previous week (TS) and previous TB
|4||Update on HL7 Meetings||10|
Meeting with Keith & Grahame (notes by Daniel Karlsson):
Keith Campbell and Grahame Grieve are only interested in equivalences between FHIR concepts and SNOMED CT concepts (how equivalent is equivalent?) and thus we should aim to sort the cases into equivalent and non-equivalent. Keith’s intention is to allow (some?) reasoning across FHIR and SNOMED CT representations, with likely significant impact on the SNOMED CT concept model. If we can move from amber to green, that’s good but if it’s not possible it’s not possible. When we have agreed on a list of equivalences HL7 will take the rest and create SNOMED CT concepts in their extension to allow (partly?) representing FHIR CodeSystems content in RF2. SNOMED I will publish the set of equivalent SNOMED CT concepts as a free for use set.
We might still discuss what is our equivalence threshold, from lexical to concept-model equivalence, but I suggest that we limit the number of additional meetings we spend on this topic.
Jane: Clarified the function of the SNOMED on FHIR group with the HTA. Keith's use case is in transferring data between companies, so a shared extension would help with this. HTA discussion on how to input to this group - SNOMED on FHIR may be added as official project to HL7's list - RobH progressing.
Daniel: This group is being asked to check alignment and provide list of "Red" value sets to HL7 so that they can add concepts to SNOMED in some extension. Question around how much 'context' is included in our selection of concepts (on both sides).
Jeremy: Notes that mapping to only certain qualifier values could lead to records not being found if some wider SNOMED CT set of values is used which wouldn't match with a reduced set via FHIR. We should include discussion of how this map should be used in various situations.
Rob: FHIR R4 published in December. R5 work underway (ML: watch concept map going normative!), targeting Q3 2020. Lots of IGs being balloted (eg IPS). See list of resources going normative at https://onfhir.hl7.org/
|5||Free SNOMED CT Set for FHIR||20|
|7||Allergies||X||Revisit any outstanding questions on Allergies.|
|8||Vital Signs||X||Daniel Karlsson|
Jeremy's work to compare Vital signs profile and SNOMED Subhierarchy - issues with eg blood pressure. Complex expression constraints available which cover the use of observables by the NHS(UK). Mapping to LOINC codes.
See Spreadsheet attached to: SNOMED on FHIR Meeting (TB) - Tuesday 21 August 2018
Issues / Discussion :
v3.4.0 (publication Aug 19?)
Neither of these exist in the FHIR 3.0.1 Spec. Rob Hausam
Tuesday 5 February 2019
|No content found.|