Date/Time
20:00 UTC on Tuesday 22 May 2018 - 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: https://chat.snomedtools.org/channel/snomed-fhir
(instructions and guide here - Getting Started with Rocket Chat)
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|---|---|---|---|
1 | Welcome and introductions | 5 | Recording + Notes. | |
2 | Summary of previous week | 5 | Summary of previous week: | |
3 | Update from HL7 Cologne | 20 | ||
4 | Condition Resource | 60 |
Discussion on https://www.hl7.org/fhir/v3/NullFlavor/cs.html and whether null type values (eg UK's "Unknown Severity") should have their use dictated. RH Said the FHIR approach was to not represent unknown data ie leave field blank. Note that the removals in the ECL for Condition.code were stated to avoid overlap with the Allergy resource ie to make the two valuesets disjoint. Issue with how to specify laterality if an implementer is not capable of doing post-coordination.
| |
5 | Profile for Specimen Resouce | 10 | Specimen binding - follow up Suggestion from Jim Case that the type attribute would be better bound to (< Substance OR < Morphologic Abnormality OR < Physical Object (or selection thereof)) rather than Specimen as it avoids any potential conflict with the other attributes and is effectively opening up post coordination, rather than sticking to a inherently restricted set of pre-coordinated concepts. Similarly (Linda Bird), the method attribute is currently a selection of SNOMED CT concepts plus a V2 valueset. Two main options:
Jim Case also suggested that using these decomposed fields would only be used outside of a SNOMED context. Otherwise could be achieved - (PWI: more safely due to MRCM) - with post coordinated. However (PWI notes): some members are some way off being able to use post-coordination and - at the same time - would experience restriction if limited to pre-coordinated content.
Suggestion (LB) for decomposition template that would describe the mapping from a post coordinated concepts into the various FHIR fields. | |
6 | ValueSets | 10 | How do we produce and publish ValueSets?
| |
7 | Next meeting | 5 | Tuesday 5 June 2018 |
Meeting Files
Previous Meetings
Title | Creator | Modified |
---|---|---|
No content found. |