Date/Time
20:00 UTC on Tuesday 3 March 2020 - 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
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 | Upcoming events: SNOMED International Business Meeting April 5 - 8 SNOMED on FHIR meeting Sunday 5 April San Antonio HL7 Meetings + Connectathon May 16 -17 FHIR DevDays - June 16-18, 2020 Cleveland, OH SI Business + Expo October | |||||||||||||
4 | Follow up on Blood Pressure. | 10 | Is the "vital signs" scope too limited? Distinction being made between "Vital Signs" blood pressure and general blood pressures. No conclusion reached on "panel codes". Compromise to use whatever is recorded on the system and where none available use a high level concept. | |||||||||||||
5 | Specimen | 30 | Ulrike Merrick | Specimen binding. Update from HL7 Specimen Project Group by Ulrike Merrick (and offer to review this group's work!) information for the HL7 specimen project calls: Mondays 2 -3 PM ET join web: Description:Online Meeting Link: https://join.freeconferencecall.com/ord Online Meeting ID: ord If not on FCC or not wanting to use VOIP, use the following dial-in: Dial-in Number (United States): (515) 6065332 Access Code: 294586 International Dial-in Numbers: https://www.freeconferencecall.com/wall/ord#international DK Both FHIR and SNOMED have reasonably elaborate models for dealing with these which creates "interesting" opportunities for binding discussions. | ||||||||||||
6 | Why use SNOMED with FHIR? | 5 |
JR: Since the case for using SNOMED in EHRs is overwhelming, FHIR must also DK: FHIR used for communicating data that has already been captured. Would be impossible to use SNOMED as a transmission terminology if the data were not already at that level of granularity. | |||||||||||||
7 | URI Standard update | 2 | Update 3 March 2020, the next draft of the SPLG URI Spec will suggest: The SPLG workgroup discussed sticking to the naming conventions of the particular technology being referenced, which will avoid current issues with IG tooling, so for example: http://snomed.info/fhir/ValueSet/gps | |||||||||||||
8 | SNOMED concepts appearing in large clinical valuesets |
Secondly could the links use the SNOMED URIs for those concept instead of linking directly into our browser application (which might change) eg http://snomed.info/id/23406007 Query from Daniel and Jeremy if the substrate could be restricted to the GPS without changing the definition of the ValueSet.
| ||||||||||||||
9 | Implementation Guide | 31 | The Implementation Guide is now building fine. Please everyone have a look and share comments. http://build.fhir.org/ig/IHTSDO/snomed-ig/index.html | |||||||||||||
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 14 Jan 2020: Update from Rob on his progress with a new FHIR Template infrastructure. Required migrating/juggling what we had already built on older infrastructure. Sits under our implementation guide materials at build.fhir.org/ig/IHTSDO/snomed-ig/branches/new-template/ as Option 6: SNOMED Specific Profiles Differential Table view shows the difference between the parent resource and our SNOMED-specific further profiling of it. Discussion around practicalities of handling bindings where the ECL isn't very pretty, but the enumerated membership list could change very frequently e.g. a list of codes for vaccine preparations (or procedures) that are specifically relevant to some national childhood immunisation programme, and which can therefore change monthly as new vaccine preparations become available. Preferred implementation solution would be for suppliers to be able to consume ECL, however complex. Discussion about what kind of separation should exist between the Implementation Guide (which should list things we think everybody should be doing in some certain way) and any more discursive musings that have have not reached that level of consensus or experience. Thoughts on whether the IG should be balloted, and how to assess the maturity of any of it? Should each SNOMEDonFHIR published profile have its own (1-5) maturity metric stated?
RH: Suggestion that "published" valuesets would be read-only.
| ||||||||||||||
12 | Next meeting | 5 | 17 March 2020 Discussion of Specimin |
Meeting Files