Stream: fhircast-github
Topic: fhircast-docs / Issue #177 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #177
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #177
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #177
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #177
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot edited Issue #177
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 21:20):
isaacvetter commented on Issue #177
duplicate of #125
Github Notifications (FHIRcast) (May 06 2019 at 18:35):
isaacvetter edited a comment on Issue #177
duplicate of #125, see proposed wording in #125.
Github Notifications (FHIRcast) (May 06 2019 at 19:50):
ajuliansr commented on Issue #177
Concur.
Github Notifications (FHIRcast) (May 21 2019 at 13:15):
wmaethner labeled Issue #177:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 21 2019 at 15:52):
isaacvetter commented on Issue #177:
## :telephone_receiver: CDS Working Group Vote (5-21-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
Ricardo moved the following disposition, seconded by @NiklasSvenzen
Disposition: Persuasive
Disposition Comment: We will clarify that SMART on FHIR support is a SHOULD, not a SHALL, but that guidance on the exchange of the hub.topic (and hub.url) is currently not defined in this specification.:+1: For: 9
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (May 21 2019 at 15:52):
wmaethner labeled Issue #177:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:07):
isaacvetter edited a comment on Issue #177:
## :telephone_receiver: II Working Group Vote (5-21-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
Ricardo moved the following disposition, seconded by @NiklasSvenzen
Disposition: Persuasive
Disposition Comment: We will clarify that SMART on FHIR support is a SHOULD, not a SHALL, but that guidance on the exchange of the hub.topic (and hub.url) is currently not defined in this specification.:+1: For: 9
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Sep 05 2019 at 04:05):
isaacvetter commented on Issue #177:
Resolved. Spec updated to clarify that SMART is recommended, not required,
Github Notifications (FHIRcast) (Sep 05 2019 at 04:05):
isaacvetter closed Issue #177:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Smart launch example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Session Discovery states that the app must be launched using SMAR on FHIR or SMART on FHIR standalone launch.
Existing wording: Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible. See other launch scenarios for guidance.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Last updated: Apr 12 2022 at 19:14 UTC
