Stream: fhircast-github
Topic: fhircast-docs / Issue #121 May 2019 Ballot Comment: Inclu...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #121
## May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_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 #121
## May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_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 #121
## May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_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 #121
## May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 22:16):
isaacvetter commented on Issue #121
Hey @bvdh, we're struggling with this. How to describe the exchange of the
hub.topicwhen the type of launch mechanisms commonly used are not really appropriate to standardize?Can you help?
Github Notifications (FHIRcast) (May 07 2019 at 17:32):
bvdh commented on Issue #121
This one is related to #125. I suggest that we take the approach mentioned in my comment in #125 and consider a proposal for an OAuth less proposal when it is made in time for this release.
Github Notifications (FHIRcast) (May 30 2019 at 13:52):
isaacvetter commented on Issue #121:
Proposed resolution: Persuasive
Proposed resolution 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. Further, we will consider a proposal for an OAuth-less launch description if it is made in time for this release and has implementer support and feedback.
Github Notifications (FHIRcast) (Jun 04 2019 at 13:28):
wmaethner labeled Issue #121:
## May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:50):
isaacvetter commented on Issue #121:
Flagged as duplicate during --
## :telephone_receiver: II Working Group Vote (5-30-2019)Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
Resolved in #125.
Github Notifications (FHIRcast) (Jun 18 2019 at 15:54):
wmaethner labeled Issue #121:
## May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:48):
wmaethner closed Issue #121:
May 2019 Ballot Comment: Include scenario’s that are not dependent on security models.
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Session Discovery
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: EnhancementSummary: Include scenario’s that are not dependent on security models.
Comment: We should also include scenario’s that are not dependent on security models.
Existing wording: The app MUST either be launched from the driving application following the SMART on FHIR EHR launch flow or the app may initiate the launch following the SMART on FHIR standalone launch
_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
