FHIR Infrastructure Minutes CC 20180130
Contents
SMART Ballot Reconciliation
Tuesday Q4 at Jan 2018 WGM
Key docs for our call: Ballot Themes List with prioritized issues in red at the bottom; and Ballot Summary Spreadsheet with full ballot comments + dispositions so far.
Attendees:
- Josh Mandel
- Christian Knaap
- Michael Donnelly
- Kevin Shekleton
- Attila Farkas
Topic #1 - Block Vote #2
Motion: Kevin Shekleton Second: Michael Donnelly 3 votes for, 0 votes against, 1 abstain
Topic #2: fhirUser vs Profile
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
Topic #3: Launch context negotiation (187)
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
Pass 4-0-0
Topic #4: Read and write scopes (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
<End of quarter>
