You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ballot#197 Nell Lapres, Epic, on behalf of Isaac Vetter, [email protected] | We should remove the "resource" SMART launch parameter. This was discusse...
#190
Closed
jmandel opened this issue
Dec 21, 2017
· 0 comments
Nell Lapres, Epic, on behalf of Isaac Vetter, [email protected]
Comment: We should remove the "resource" SMART launch parameter. This was discussed in smart-on-fhir/smart-on-fhir.github.io#138
Summary: Remove "resource" SMART launch parameter.
Josh's Triage Notes
Merge with theme: "Omit Needless Launch Contexts"
Disposition
Persuasive with mod.
Given their limited use, standardized concepts for "location" and "resource" should be removed from the specification. "smart_style_url" should be marked as "experimental" to indicate that there may be backwards-incompatible changes to the style document pointed to by the smart_style_url.
Vote Details
Pro-Con-Abstain: 7-0-0
Date: 2017-10-19
The text was updated successfully, but these errors were encountered:
Ballot Weight
NEG Correction
Where
Scopes and Launch Context :: http://hl7.org/fhir/smart-app-launch/scopes-and-launch-context/
What
Nell Lapres, Epic, on behalf of Isaac Vetter, [email protected]
Comment: We should remove the "resource" SMART launch parameter. This was discussed in smart-on-fhir/smart-on-fhir.github.io#138
Summary: Remove "resource" SMART launch parameter.
Josh's Triage Notes
Merge with theme: "Omit Needless Launch Contexts"
Disposition
Persuasive with mod.
Given their limited use, standardized concepts for "location" and "resource" should be removed from the specification. "smart_style_url" should be marked as "experimental" to indicate that there may be backwards-incompatible changes to the style document pointed to by the smart_style_url.
Vote Details
Pro-Con-Abstain: 7-0-0
Date: 2017-10-19
The text was updated successfully, but these errors were encountered: