Stream: fhircast-github
Topic: fhircast-docs / Issue #224 May 2019 Ballot Comment: Add d...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot opened Issue #224
## May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot labeled Issue #224
## May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot labeled Issue #224
## May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:54):
hl7-fhircast-bot edited Issue #224
## May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 07 2019 at 23:54):
isaacvetter commented on Issue #224
Hi @IoanaSingureanu,
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.
During conversation at the Montreal, May 2019 working group meeting, @wdvr, @wmaethner, @NiklasSvenzen and myself talked through this issue and will adopt the following wording:
Proposed wording: As part of a SMART launch, the app requests the
fhircastOAuth 2.0 scope and receives the location of the Hub and a uniquehub.topicurl, which serves as the identifier of the user's session. The SMART app launch receives the current context as SMART launch parameters and receives additional context event notifications when the SMART launch context changes during a session.
Github Notifications (FHIRcast) (May 08 2019 at 00:06):
isaacvetter edited a comment on Issue #224
Hi @IoanaSingureanu,
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.
Overall, FHIRcast does not support _all_ the functionality of CCOW. We've tried to make FHIRcast simpler, http-based and focused on the implementer.
During conversation at the Montreal, May 2019 working group meeting, @wdvr, @wmaethner, @NiklasSvenzen and myself talked through this issue and will adopt the following wording:
Proposed wording: As part of a SMART launch, the app requests the
fhircastOAuth 2.0 scope and receives the location of the Hub and a uniquehub.topicurl, which serves as the identifier of the user's session. The SMART app launch receives the current context as SMART launch parameters and receives additional context event notifications when the SMART launch context changes during a session.Further, we will create an additional, non-normative page on the FHIRcast website statin,g at least, some of the differences between FHIRcast and CCOW to better explain that FHIRcast is a lightweight alternative to CCOW. A full-featured FHIRcast hub will not support the same features as a CCOW context manager.
Github Notifications (FHIRcast) (May 23 2019 at 13:50):
wmaethner labeled Issue #224:
## May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:50):
wmaethner commented on Issue #224:
Proposed resolution:
Not related
- We will update and clarify the home page to call out the differences between FHIRcast and CCOW. Related post #248
Github Notifications (FHIRcast) (May 30 2019 at 14:21):
isaacvetter commented on Issue #224:
## :telephone_receiver: II Working Group Vote (5-30-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
Chris Carr moved the following disposition, seconded by @wmaethner
Disposition: Not related
Disposition Comment: We will update and clarify the home page to call out the differences between FHIRcast and CCOW and better describe the SMART launch context parameters as a mechanisms for establishing an initial shared context between applications.Related post #248
:+1: For: 3
:expressionless: Abstain: 1
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (May 30 2019 at 14:22):
wmaethner labeled Issue #224:
## May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 10 2019 at 21:01):
isaacvetter labeled Issue #224:
May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 12 2019 at 13:46):
isaacvetter closed Issue #224:
May 2019 Ballot Comment: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Submitted by Greg Staudenmaier on behalf of @IoanaSingureanu (ioana.singureanu@bookzurman.com )
Chapter/section:
Url:
Type: A-S
In Person requested: Yes :bust_in_silhouette:Summary: Add dependence on SMART Launch and launch contexts in addition to session-related events.
Comment: CCOW is widely implemented across VA and it's important to maintain the same functiionality as the industry migrates to CCOW relies on "common" contexts that may be changed by any of the CCOW-enable, desktop-integrated applications. It's important to maintain the same functionity, the hub.topics should support events relevant to session and context changes.
Existing wording: As part of a SMART launch, the app requests the fhircast OAuth 2.0 scope and receives the location of the Hub and a unique hub.topic url, which serves as the identifier of the user's session.
Proposed wording: Add "To support all the functionality currently avaialble in CCOW implementatoin , this specification relies on the "SMART-on-FHIR Launch" to provide authentication, application registration, and launch contexts (e.g. Patient/123, Encounter/456). Therefore SMART-on-FHIR Launch is a pre-requisite specification. Synchornizing application may use event notifications to indicate whether a SMART launch context was changed during a session. For example if the EHR is the "driving application" and an imaging application is "syncrhonizing", the user may change the encounter to view another diagnostic imaging study. That notification would be available to the EHR, if it subscrubed to that event and the user could then change context to the EHR to view the associated report. "
_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
