Peter G. Williams

Rob Hausam

Recording + Notes.

Jane Millar

Peter G. Williams

Request received for documentation of progress and process.

• Write up 3 groups of work - Green items to GG, Amber items with questions to HL7 and questions for SNOMED International to appropriate group.
• Jane Millar To write overview - draft to RH, DK, PW

Sharing our output with HL7 - specific output or questions for Rob?

Split: What needs to be addressed by SI and what should be passed over to HL7? Staged / Iterative approach suggested. Severities currently green - shall we start there.

Communicating this to: GG (if we go to Patient Care, it would need context supplied which RH could give). 3rd option is FHIR Infrastructure Work Group. Agreed GG in first instance. HTA is considered to work at a more strategic level.

RH suggested mapping based on the stated definition of the code in FHIR ie where no strict definition is given then a strict lexical match is sufficient, but where full definition is given our mapping should be commensurately specific.

DK: We should include (consider) previous mapping work done by LB and GG - FHIR Expression Templates. So individual value mappings exist within the context of a wider information model mapping.

Peter G. Williams

Rob Hausam

2019-02-12 - SNOMED on FHIR Meeting (TS)

2019-02-05 - SNOMED on FHIR Meeting (TB)

Jane Millar

Jeremy Rogers

Daniel Karlsson

Free SNOMED CT set for FHIR

• Are the mappings suggested complete and ready as a recommendation?

• Peter G. Williams write up "Green" mappings to send to Grahame
• Rob Hausam report back on progress with HL7 re "Amber" mappings
  

Daniel Karlsson

Jeremy Rogers

Publishing Profiles

• Wrapped by implementation guide - in this case https://github.com/IHTSDO/snomed-ig
• Value set publish to a live SI hosted Snowstorm instance. Alternatively Michael Lawley has offered to host.
• Additional hosting on Simplifier (STU3, not yet R4 - January?)
• Suggestion to review work already done to ensure R4 compatibility
• Would value sets also be published as reference sets? Maintain via Refset tool and published in MLDS. Note: UK experienced substantial 'getting off the ground' effort in this area. Sweden have worked through ~10 (will request promotion of content to International Edition where appropriate).
• HL7 FHIR Registry?
• Option to have multiple profiles available at the same time using slicing.
• Chance to do some technical work at HL7 San Antonio

• Peter G. Williams discuss Rory Davidson
• Peter G. Williams re-run tooling to include existing profiles in appropriate hierarchy.

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:

1. Where we only use the code field for clinical content (plus the administrative fields)
2. Where we restrict the code field to atomic values and all other resource fields should also be populated. Note that this does not solve the role group problem.

Daniel Karlsson

Vital Signs Resource

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 :

• Normative vs. descriptive purpose - 1, 2, or 3 profiles?
• Unresolved modeling issues

Daniel Karlsson

Neither of these exist in the FHIR 3.0.1 Spec. Rob Hausam

http://build.fhir.org/servicerequest.html → ServiceRequest

Questions:

• What determines which FHIR resource to use: the location of the data item in the sending system’s information model, or the semantics of the particular code regardless of where it was found? Some hybrid of both?

• If the resource to be used is determined at least partly by the location in the sending information model, how does a requesting system cope with the fact that different implementations (or different users of the same implementation) both can and do secrete essentially the same clinical info in very different parts of the host information model?

Tuesday 12 March 2019