Stream: fhircast-github
Topic: fhircast-docs / Issue #164 May 2019 Ballot Comment: Reque...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot opened Issue #164
## May 2019 Ballot Comment: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Submitted by Ron Parker on behalf of Kenn Sinn
HL7 Canada (ken.sinn@ehealthontario.on.ca )
Chapter/section: Security Considerations
Url: http://fhircast.org/security-considerations/#experimental-websockets-support
Type: A-S Enhancement
In Person requested: Yes :bust_in_silhouette:Summary: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Comment: The prescribed model for intent verification only works for server based architecture due to the fact that you cannot post to a single page app. In order to support single page app FHIRcast should support websocket as it is supported in the sandbox project. Can this be an officially supported feature of FHIRcast?
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot labeled Issue #164
## May 2019 Ballot Comment: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Submitted by Ron Parker on behalf of Kenn Sinn
HL7 Canada (ken.sinn@ehealthontario.on.ca )
Chapter/section: Security Considerations
Url: http://fhircast.org/security-considerations/#experimental-websockets-support
Type: A-S Enhancement
In Person requested: Yes :bust_in_silhouette:Summary: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Comment: The prescribed model for intent verification only works for server based architecture due to the fact that you cannot post to a single page app. In order to support single page app FHIRcast should support websocket as it is supported in the sandbox project. Can this be an officially supported feature of FHIRcast?
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot labeled Issue #164
## May 2019 Ballot Comment: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Submitted by Ron Parker on behalf of Kenn Sinn
HL7 Canada (ken.sinn@ehealthontario.on.ca )
Chapter/section: Security Considerations
Url: http://fhircast.org/security-considerations/#experimental-websockets-support
Type: A-S Enhancement
In Person requested: Yes :bust_in_silhouette:Summary: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Comment: The prescribed model for intent verification only works for server based architecture due to the fact that you cannot post to a single page app. In order to support single page app FHIRcast should support websocket as it is supported in the sandbox project. Can this be an officially supported feature of FHIRcast?
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):
hl7-fhircast-bot edited Issue #164
## May 2019 Ballot Comment: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Submitted by Ron Parker on behalf of Kenn Sinn
HL7 Canada (ken.sinn@ehealthontario.on.ca )
Chapter/section: Security Considerations
Url: http://fhircast.org/security-considerations/#experimental-websockets-support
Type: A-S Enhancement
In Person requested: Yes :bust_in_silhouette:Summary: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Comment: The prescribed model for intent verification only works for server based architecture due to the fact that you cannot post to a single page app. In order to support single page app FHIRcast should support websocket as it is supported in the sandbox project. Can this be an officially supported feature of FHIRcast?
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 06 2019 at 18:24):
isaacvetter commented on Issue #164
related to #104
Github Notifications (FHIRcast) (May 08 2019 at 14:19):
isaacvetter commented on Issue #164
Resolution: Considered for future use
Websocket support is critical path for FHIRcast, we still need more implementer feedback and experience. Following STU1 ballot, will publish #57 and specifically test websocket support at connectathon in Sept.
Mover: Isaac, Will
Affirmative, Abstaintion, Negative: 14-0-0
Github Notifications (FHIRcast) (May 08 2019 at 14:19):
wmaethner labeled Issue #164
## May 2019 Ballot Comment: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Submitted by Ron Parker on behalf of Kenn Sinn
HL7 Canada (ken.sinn@ehealthontario.on.ca )
Chapter/section: Security Considerations
Url: http://fhircast.org/security-considerations/#experimental-websockets-support
Type: A-S Enhancement
In Person requested: Yes :bust_in_silhouette:Summary: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Comment: The prescribed model for intent verification only works for server based architecture due to the fact that you cannot post to a single page app. In order to support single page app FHIRcast should support websocket as it is supported in the sandbox project. Can this be an officially supported feature of FHIRcast?
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 05 2019 at 03:56):
isaacvetter commented on Issue #164:
Kenn, we agree!
We're working hard on a websockets spec to quickly follow this STU1.
Check out https://github.com/HL7/fhircast-docs/wiki/Websocket-proposal
The Sept connectathon is intended to support and encourage exactly this use-case.
Getting through our STU1 ballot is a pre-req for adding websocket support, so, I'm closing this issue. Please feel free to reach out.
Isaac
Github Notifications (FHIRcast) (Sep 05 2019 at 03:56):
isaacvetter closed Issue #164:
May 2019 Ballot Comment: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Submitted by Ron Parker on behalf of Kenn Sinn
HL7 Canada (ken.sinn@ehealthontario.on.ca )
Chapter/section: Security Considerations
Url: http://fhircast.org/security-considerations/#experimental-websockets-support
Type: A-S Enhancement
In Person requested: Yes :bust_in_silhouette:Summary: Request for Websocket to be officially supported, to enable Single Page Applications to use FHIRcast.
Comment: The prescribed model for intent verification only works for server based architecture due to the fact that you cannot post to a single page app. In order to support single page app FHIRcast should support websocket as it is supported in the sandbox project. Can this be an officially supported feature of FHIRcast?
_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
