Stream: smart
Topic: SMART Ballot Reconciliation Meeting: 2018-01-30: Tuesday ...
Josh Mandel (Jan 30 2018 at 21:46):
Block Vote from Jan 4
Josh Mandel (Jan 30 2018 at 21:46):
Motion: Kevin Shekleton
Josh Mandel (Jan 30 2018 at 21:46):
Second: Michael Donnelly
Josh Mandel (Jan 30 2018 at 21:48):
3 votes for, 0 votes against, 1 abstain
Josh Mandel (Jan 30 2018 at 22:00):
# Rename profile to fhirUser, but document that the older profile claim remains, but deprecated. Indicate that profile will be removed in a subsequent version of the specification. Note that servers already implementing the profile claim should add fhirUser with the same value, but should preserve the profile claim until the deprecation cycle has been completed. SMART apps should prefer the fhirUser claim over profile.
Mover: Kevin Shekleton
Second: Michael Donnelly
Passes: 4-0-0
Josh Mandel (Jan 30 2018 at 22:17):
# ISsue 187. "Update our ""launch context"" docs to state that: launch context is a negotiation where a client asks for specific launch context parameters (e.g. ""launch/patient""); a server can decide which launch context parameterss to provide, using the client's request as an input into the decision process.
When granting a patient-level scopes like ""patient/*.read"", the server MUST provide a ""patient"" launch context parameter. "
Mover: Michael Donnelly
Seconder: Christian Knaap
Josh Mandel (Jan 30 2018 at 22:18):
Pass 4-0-0
Josh Mandel (Jan 30 2018 at 22:32):
# 185
"Asked and Answered.
Add langauge to specification to clarify:
Apps that need to read existing data from an EHR (e.g., FHIR `read` and `search` interactions) should ask for `read` scopes. Apps that need to write data to an ehr (e.g., FHIR `create`, `update`, and `delete`) should ask for `write` scopes. EHRs may decide what specific interactions and operations will be enabled by these scopes.
Moved: Michael Donnelly
Seconded: Kevin Shekleton
Passes 4-0-0
Josh Mandel (May 04 2018 at 17:22):
Documented this meeting on hl7 wiki
Last updated: Apr 12 2022 at 19:14 UTC
