Stream: fhircast-github
Topic: fhircast-docs / Issue #125 May 2019 Ballot Comment: Contr...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #125
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot labeled Issue #125
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot labeled Issue #125
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot edited Issue #125
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 20:59):
isaacvetter commented on Issue #125
Hey @bvhd,
How would you recommend navigating this contradiction. FHIRcast subscribers should be OAuth clients. The spec should mandate this.
In the interim, there's lots and lots of existing software in the world that needs a smoother migration path from existing, proprietary context synchronization and having the Launch Scenarios page really is helpful.
Towards that end, how about we simply remove the offending sentence?
Existing working: 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.
Proposed wording: See other launch scenarios for additional information.
Github Notifications (FHIRcast) (Apr 30 2019 at 20:59):
isaacvetter edited a comment on Issue #125
Hey @bvhd,
How would you recommend navigating this contradiction? FHIRcast subscribers should be OAuth clients. The spec should mandate this.
In the interim, there's lots and lots of existing software in the world that needs a smoother migration path from existing, proprietary context synchronization and having the Launch Scenarios page really is helpful.
Towards that end, how about we simply remove the offending sentence?
Existing working: 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.
Proposed wording: See other launch scenarios for additional information.
Github Notifications (FHIRcast) (May 06 2019 at 22:17):
isaacvetter commented on Issue #125
During conversation at the Montreal, May 2019 working group meeting, @RicardoQuintano, @wmaethner, @NiklasSvenzen and myself talked through this issue and would like to:
Clarify that SMART on FHIR support is a SHOULD, not a SHALL, but that guidance on the exchange of the
hub.topic(andhub.url) is outside of the scope of the FHIRcast specification when not using SMART.
Github Notifications (FHIRcast) (May 06 2019 at 22:21):
isaacvetter assigned Issue #125
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 22:21):
NiklasSvenzen labeled Issue #125(assigned to isaacvetter)
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 07 2019 at 17:30):
bvdh commented on Issue #125
I agree with the previous comment, with a small change:
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.We might add a specification if time allows and someone makes a valid proposal.
(I remember that we discussed this during the San Antonio Connecthaton, but forgot with whom)
Github Notifications (FHIRcast) (May 07 2019 at 17:30):
bvdh edited a comment on Issue #125
I agree with the previous comment, with a small change:
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.A specification might be added if time allows and someone makes a valid proposal.
(I remember that we discussed this during the San Antonio Connecthaton, but forgot with whom)
Github Notifications (FHIRcast) (May 07 2019 at 22:26):
isaacvetter commented on Issue #125
:+1:
Proposed resolution: Persuasive
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.
Github Notifications (FHIRcast) (May 21 2019 at 13:53):
wmaethner labeled Issue #125 (assigned to isaacvetter):
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_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 #125:
## :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 #125 (assigned to isaacvetter):
## May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:08):
isaacvetter edited a comment on Issue #125:
## :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 10 2019 at 21:34):
isaacvetter commented on Issue #125:
Addressed in session discovery section:
If not using SMART on FHIR, the mechanism enabling the app to discover the
hub.urlandhub.topicis not defined in FHIRcast.
Github Notifications (FHIRcast) (Sep 10 2019 at 21:34):
isaacvetter closed Issue #125 (assigned to isaacvetter):
May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 10 2019 at 21:34):
isaacvetter labeled Issue #125 (assigned to isaacvetter):
May 2019 Ballot Comment: Contradiction with mandatory smart launch
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: SMART Launch Example
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: CorrectionSummary: Contradiction with mandatory smart launch
Comment: "Although FHIRcast works best with the SMART on FHIR launch and authorization process, implementation-specific launch, authentication, and authorization protocols may be possible."
Contradiction with mandatory smart launch indicated previously
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.
_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
