20:00 UTC on Tuesday 6 August 2019 - 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
Next FHIR DevDays Amsterdam, November 20 – 22, 2019
|4||Free SNOMED CT Set for FHIR||50|
25 June. Grahame keen to see work done on both sides to bring us closer together in the ValueSets concerned with clinical safety:
- AdverseEvent.outcome (red)
- Condition.clinicalStatus & AllergyIntolerance.clinicalStatus (amber) These are the same items although in separate Valuesets. HL7 could discuss making them a single ValueSet.
Grahame looking for times for a face to face meeting, see Zulip.
See updates here: Observation binding
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.
Revisit any outstanding questions on Allergies.
External publication of v0.1 of the AllergyIntolerance resource
|8||Vital Signs||X||Daniel Karlsson|
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 :
v3.4.0 (publication Aug 19?)
These two separate resources existed in the FHIR 3.0.1 Spec. Rob Hausambut have been removed in 4.0 and replaced with ServiceRequest
Need to revisit the original questions raised in this group wrt the two separate resources of yore, and consider whetehr the same issues persists wrt the new single ServiceRequest resource.
|No content found.|