20:00 UTC on Tuesday 23 June 2020 - 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 Baltimore September 18 - 25 Fully Virtual. Connectathon 9 -11 Sept.
21 July DK proposal to add Language item to Terminology Track: Advertisement of proposed extension - Designation extension also use of token (a la Peter Jordan ) in HTTP GET request eg designation=http://snomed.info/sct|281000210109
"Discussion of an extension proposed by the SNOMED on FHIR workgroup to support the querying and returning of designations according to their 'context of use' such as clinical speciality language, national dialects (eg US / GB English) and Patient Friendly Terms. The proposal is intended to be terminology agnostic, and In SNOMED CT this feature is expressed via Language Reference Sets"
SI Business 6 - 7 + Expo October 7 - 9 . Confirmed fully virtual.
Nov 17 - 20 FHIR Dev Days also virtual.
|4||FHIR Shorthand||10||Daniel Karlsson|
TODO: Daniel to overwrite https://github.com/IHTSDO/snomed-ig so we can see that being built by the HL7 build tooling.
A generic SNOMED CT concept for "key worker" (or just "target population") is needed to state an immunization reason, or a reason for an immunization recommendation.
DK Both FHIR and SNOMED have reasonably elaborate models for dealing with these which creates "interesting" opportunities for binding discussions.
Discussion on why Specimen (which - as an industry - has been around forever) is only at maturity level 2. Perhaps there's a lack of production implementations. DK: Specimen is a potential candidate for a SOF Published Profile.
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
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.