20:00 UTC on Tuesday 17 December 2019 - 90 minutes.
- Bindings to FHIR Clinical Resources (e.g. value set bindings)
|Owner||Notes & Actions|
|1||Welcome and introductions||5|
Recording + Notes.
Summary of previous week (TS) and previous TB
HL7 Sydney, February. Business Meeting Agenda: https://hl7.sydney/programs.php
Christmas Break: Skip 24 + 31 Dec.
|4||URI Standard update||10|
The SPLG workgroup discussed this
Update this causes a problem in the tooling as it demands a capital V in ValueSet.
Update 3 Dec: Publisher tooling has specific requirements around URI construction that isn't compatible with the proposed URI standard.
|5||Free Set Response||5|
Update 3 Dec: Draft of notes arising from KL and subsequent SNOMED on FHIR meeting being reviewed. Intention to reach out to Grahame and Keith to discuss further. Amber mappings outstanding, but value of partial implementation questionable so need to discuss before further work is done. RH has given KeithC an update.
Did we conclude on the best approach(es) for semantic overlap between fields as discussed in Terminology Binding
Update: Option 4 seems the most elegant - "BodySite must always be a specialization or self of finding site" although BodySite is an easy example since the mapping to the SNOMED concept model (finding site) is well understood. It would not work for Condition.Status where resolved/remission is not represented in attribute values.
Update 17 Sept: If we were to express ValueSets for profiles using Refsets (which this group would have to curate and publish) then National Centres could add to those refsets using their own module.
Update 15 Oct >2 issues:
Rob Hausam Check with Lloyd McKenzie and Eric Haas if their two frameworks have been fully
Procedure Expert assistance for CarePlan:
Procedure (not completed 3 Dec) followed by Care Plan
KG: procedure code concern about overlap with reasonCode.
See updates here: Observation binding
|9||Cancer Disease Status|
Query about qualifier values used. Would it be better to use < 418138009 |Patient condition finding (finding)| ? (JR suggested immediate children ie "<!" rather than descendants)
See also 373117000 |Pathology examination findings indeterminate (finding)| (child of 250537006 |Histopathology finding (finding)|)
Options for Profile discussion:
Notes 26 Feb: UK working on pathology reporting - diagnostic / observation.
Suggestion that we try out two types of profile, both of which avoid issues of conflict between fields within the information model:
28 May: Plan to publish profile for the October conference (8 sessions + working between meetings. Completion for review Tues 14 October (or earlier since we'll need time to complete the IG?)
Tooling for profiles: Forge (.NET) is now R4
RH: Suggestion that "published" valuesets would be read-only.
Revisit any outstanding questions on Allergies.
External publication of v0.1 of the AllergyIntolerance resource
|12||Vital Signs||10||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 :
Update of the Vital Signs panel binding page.
Discussion about the Vital Signs FHIR profiles and how to profile those to SNOMED profiles. We are going to create SNOMED profiles on the specific FHIR Vital Signs profile (e.g. Heart rate) and declare conformance with a generic SNOMED Vital Signs profile.
v3.4.0 (publication Aug 19?)
These two separate resources existed in the FHIR 3.0.1 Spec. Rob Hausambut have been removed in 4.0 and replaced with ServiceRequest
Need to revisit the original questions raised in this group wrt the two separate resources of yore, and consider whether the same issues persists wrt the new single ServiceRequest resource.
14 January 2020