Date/Time
20:00 UTC on Tuesday 17 July 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: snomedIntl.slack.com #snomed-on-fhir
Attendees
Rob Hausam, Peter G. Williams, Jeremy Rogers, Jane Millar, Linda Bird, Andrew Perry, Michael Lawley, David Sperzel, Jay Lyle, Peter Sergent, Yongsheng Gao, Øyvind
Apologies
Meeting Recording
https://snomed.zoom.us/recording/share/IiXShSk8wzW-Sf0rPpm65iosa6LpWMAWCBMe9NxT20WwIumekTziMw
Discussion items
Item | Description | Mins | Owner | Notes & Actions |
---|---|---|---|---|
1 | Welcome and introductions | 5 | Recording + Notes. Swapping weeks when missing a week eg July 24. Face to Face slot at the Vancouver Business Meeting (as well as an Expo slot). NB Next Meeting Tuesday 7 August 2018 due to skipping 24 July. Week about will change - expect calendar invites. Peter off July 31 (TS) & Aug 7 (TB) Jane Millar Linda Bird please record. | |
2 | Abstract for Expo Presentation | 5 |
| |
3 | Summary of previous week | 5 | Summary of previous week: | |
4 | Medication Resource | 10 | Any closing remarks?
Note: Original presentation including options for dealing with Code vs deconstructed fields: SNOMED on FHIR Meeting (20171017).pptx
| |
5 | v3.0.1 ProcedureRequest ReferralRequest v3.4.0 (publication Aug 19?) ServiceRequest | 60 | Neither of these exist in the FHIR 3.0.1 Spec. Rob Hausam http://build.fhir.org/servicerequest.html → ServiceRequest Questions:
| |
6 | Next meeting | 5 | NB Tuesday 7 August 2018 |
Meeting Files
- Jeremy Rogers would you be able to upload your presentation here please? Thanks! Update: See comments section in Medication Resource
Previous Meetings
Title | Creator | Modified |
---|---|---|
No content found. |
1 Comment
Jeremy Rogers
Here are my brief slides on the question of how the act of referring a patient can currently be plausibly coded in SNOMED CT, and how the three coding patterns currently available could make it more of a challenge to query a real individual patient EPR in order to ask the question 'what referrals does this patient have currently in flight?'