Stream: fhircast-github
Topic: fhircast-docs / Issue #217 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #217
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_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 #217
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_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 #217
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 02:42):
isaacvetter commented on Issue #217
This page is outside of the normative-track content and is intended to be supplemental material that is not part of the specification and is not being balloted.
Hey Tony,
I can't find the difference between the above existing and suggested wording. How about we go with:
Proposed wording: Use of SMART requires that a synchronizing app support the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Isaac
Maybe the import into github dropped a strikethrough?, no strikethrough in the (unified google sheets spreadsheet](http://bit.ly/fhircast-May-2019-ballot-comments) nor in the original excel spreadsheet. If I'm overlooking this change, let me know.
Github Notifications (FHIRcast) (May 08 2019 at 15:11):
wmaethner labeled Issue #217
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:12):
wmaethner commented on Issue #217
Like #219 and #218 this is outside the normative track
Github Notifications (FHIRcast) (May 09 2019 at 13:31):
wmaethner commented on Issue #217
## Montreal May 2019 Working Group Vote
Isaac Vetter moved the following disposition, seconded by Reinhard Egelkraut
Disposition: Not related
Disposition Comment: Will address later:+1: For: 6
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (May 09 2019 at 13:31):
wmaethner labeled Issue #217
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 05 2019 at 14:15):
wmaethner unlabeled Issue #217:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 10 2019 at 20:28):
isaacvetter commented on Issue #217:
I can't find the above quoted paragraph in the https://fhircast.hl7.org/syncconsiderations/ page.
Closing
Github Notifications (FHIRcast) (Sep 10 2019 at 20:28):
isaacvetter closed Issue #217:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section:
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: Cant glom the meaning - two eithers set up a quandry.
Existing wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
Proposed wording: Use of SMART requires either that a synchronizing app supports the SMART on FHIR specification and specifically either be launched from the driving app or use the Hub's authorization server's login page.
_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
