Difference between revisions of "FHIR Infrastructure Minutes WGM 201705"
Ron Shapiro (talk | contribs) |
(→Mon Q3) |
||
Line 69: | Line 69: | ||
Idea: keep it, but add a property to the concept itself stating whether it actually modifies meaning. Problem: some concepts are used in different places, with different meaning (most notably: boolean) | Idea: keep it, but add a property to the concept itself stating whether it actually modifies meaning. Problem: some concepts are used in different places, with different meaning (most notably: boolean) | ||
Resolution filed. | Resolution filed. | ||
+ | |||
+ | ==Mon Q4== | ||
+ | See [[FHIR_Workflow_Minutes_WGM_201705]] |
Revision as of 08:14, 10 May 2017
Contents
FHIR Infrastructure 2017 May Madrid WGM Minutes
Return to FHIR Infrastructure Minutes
Agenda
Mon Q2
Chair: Grahame Grieve
Attendance sheet: http://bit.ly/201705FhirSignup
R4 normative planning:
- straw poll for which FHIR-I resources should go normative
- 7 of 11 FMM Level 5 resources belong to FHIR-I
- those 7 were near unanimous for going normative, plus a couple others
- a few others received a smattering of votes
FHIR version in instances:
- discussion during FHIR connectathon on Saturday, did not come to a consensus on whether to do this or where to include it
- Google document highlighting some of the use cases and a recap of the discussion here
- Vocab reminded group that terminology versioning will always be important
- issue will be discussed between now and September WGM and a decision may be made at that time
Tracker Items:
- 8364 - New List operations $add and $delete - Closed because it can be done via patch - Chris G will create a task around more precise fetch (or add a note to one of his many existing tasks on this subject)
- 8806 - Fragment (SUBSETTED) profile - Ask security for connectathon experience - for consideration Madrid Thursday Q1
- 13224 - Clarify how default values work in presence of extensions - Motion put forth, but only passed 22-5-17--issed tabled for further discussion
Mon Q3
Chair: Josh Mandel
Minutes: Christiaan Knaap
Smart App Launch specification, part of FHIR
https://github.com/smart-on-fhir/smart-on-fhir.github.io
See branch into-hl7
Send in issues on the repo for amendments or changes
Planning: work through it, ballot it in September http://bit.ly/argo-auth
How is this related to CDS Hooks? It would enable presenting relevant app functionality based on the context (e.g. a diagnosis the clinician is typing is).
Just EHR -> App? That is the abstraction: app just accesses the 'EHR' being one FHIR endpoint. Under the hood multiple servers and services (FHIR and OAuth2) may be involved.
Open issues:
Filter: RWG: FHIR-I, Status: any open, Group: Discuss at WGM
GF#8776 Chris gives an overview. Links to searching through a tree, and to searching through a chain. Also relates to a closure in a vocabulary search (with an 'is-a' traversal) This limits to a 'partOf' element, so a relation to itself.
It looks like comparable concepts for Url (simple) and Token (that requires terminology evaluation). More generic solutions: add expressions to say how many levels you want to descend. Chris has implemented it just for 'partOf' relations. Circularity means an error. Go further: · mention in the SearchParameter somehow if this is possible for that parameter. · try it in a connectathon
GF#5173
Is-Modifier
Idea: keep it, but add a property to the concept itself stating whether it actually modifies meaning. Problem: some concepts are used in different places, with different meaning (most notably: boolean)
Resolution filed.