Date/Time
20:00 UTC on Tuesday 3 December 2019 - 90 minutes.
Objectives
- Bindings to FHIR Clinical Resources (e.g. value set bindings)
Meeting Details
Online: https://snomed.zoom.us/my/snomedhl7
Phone: See https://zoom.us/zoomconference for available phone numbers (meeting id 242-348-6949)
Chat: snomedIntl.slack.com #snomed-hl7-fhir
Attendees
Daniel Karlsson, Jeremy Rogers, Peter G. Williams,Rob Hausam, Jim Case, Andrew Perry, Eric Rose, Jane Millar, Jon Zammit, Kirstine Rosenbeck Gøeg, Monica Harry, Peter Jordan, Suzy Roy, Yongsheng Gao
Apologies
Meeting Recording
https://snomed.zoom.us/recording/share/dbNTvoMLCNvaZL_2wbD4eMK_MUvq8dIxkVeqSdhgJ5qwIumekTziMw
Discussion items
Item | Description | Mins | Owner | Notes & Actions | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Welcome and introductions | 5 | Recording + Notes. | |||||||||||||
2 | Summary of previous week (TS) and previous TB | 5 | ||||||||||||||
3 | Future meetings | 5 | HL7 Sydney, February. Business Meeting Agenda: https://hl7.sydney/programs.php Christmas Break: Skip 24 + 31 Dec. | |||||||||||||
4 | GPS | Question on translation of GPS. Content can be translated freely but will not be published by SNOMED International - expect possibly if translations had been officially published. | ||||||||||||||
5 | URI Standard update | 10 |
The SPLG workgroup discussed this http://snomed.info/valueSet/GPS Update this causes a problem in the tooling as it demands a capital V in ValueSet.
http://snomed.info/fhirStructureDefinition/example Update 3 Dec: Publisher tooling has specific requirements around URI construction that isn't compatible with the proposed URI standard.
| |||||||||||||
6 | 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. | |||||||||||||
7 | Implementation Guide | 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 | ||||||||||||||
8 | Procedure Resource | Procedure Expert assistance for CarePlan:
| ||||||||||||||
9 | Observation resource | See updates here: Observation binding | ||||||||||||||
10 | Cancer Disease Status | Carmela Couderc | http://hl7.org/fhir/us/mcode/2019Sep/StructureDefinition-onco-core-CancerDiseaseStatus.html http://hl7.org/fhir/us/mcode/2019Sep/ValueSet-obf-datatype-ConditionStatusTrendVS.html
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)|) | |||||||||||||
11 | Exemplar Profile | Publishing Profiles
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. | ||||||||||||||
12 | Allergies | Revisit any outstanding questions on Allergies. External publication of v0.1 of the AllergyIntolerance resource | ||||||||||||||
13 | Vital Signs | 10 | Daniel Karlsson | Vital Signs Profile of Observation Resource 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 :
2019-08-20: 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. | ||||||||||||
14 | v3.0.1 ProcedureRequest ReferralRequest v3.4.0 (publication Aug 19?) ServiceRequest | X | These two separate resources existed in the FHIR 3.0.1 Spec. Rob Hausambut have been removed in 4.0 and replaced with ServiceRequest http://build.fhir.org/servicerequest.html → ServiceRequest Questions:
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. | |||||||||||||
15 | Next meeting | 5 | 17 December: Procedure (not completed 3 Dec) followed by Care Plan KG: procedure code concern about overlap with reasonCode.
|
Meeting Files