20:00 UTC on Tuesday 7 July 2020 - 90 minutes.
- Joint meeting to look at moving SNOMED FHIR Implementation Guide to FSH
|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
SI Business + Expo October. Confirmed fully virtual.
FSH-ized IG here: https://github.com/danka74/snomed-ig-fsh
Joint meeting between the two groups (TS & TB) discussing the IG at next weeks meeting (2020-06-30).
|5||Interim Release of FHIR||5||Peter Jordan|
Proposed version "R4A", updates to Subscription, Medication Knowledge.
2020-06-23: Community is pushing against a new version. Likely won't happen.
|6||SNOMED on FHIR deliverables plan||10|
Discuss: Requirements for publishing - quality criteria, technical , maintenance plan needed before we commit to publish?
Investigate use of query Refset as a way to avoid coding ECL into Profiles. Could we detect a change in expansion membership. JR suggests mapping between FHIR XPath (identifying location in profile) and Query.
Option for "use at your own risk / best efforts for maintenance" / STU / Maturity Level (traditionally two named implementers are required). "Aim for best practice"
2020-06-23: Internal discussion to be held.
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
|10||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)|)
Update 31 March 2020 - PWI: links above no longer work. I was unable to find obvious alternative via http://hl7.org/fhir/us/mcode/
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.
21 July 2020.