Stream: fhircast-github
Topic: fhircast-docs / Issue #107 May 2019 Ballot Comment: Provi...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #107
## May 2019 Ballot Comment: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Submitted by Mitra Rocca; Terrie Reed
Chapter/section: Overall
Url: https://fhircast.hl7.org/
Type: A-SSummary: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Comment: Since the "hub.topics" are meant to be events, it would be useful to create a hierarchy of events using a BNF grammar similar SMRT clinical context scopes. For instance: "session.*" hub.topic scope would correspond to all session-related events or alterantively an could subscribe to either "Session.close" or "session.change". Similarly the "hub.topic" could be centered on a a FHIR resource - similar to SMART scoes - "patient.selected" , "device.selected". The lesson of CCOW is that standardizeding the "contexts" and creating an extensible grammar/sytax are both needed for adption. Pub/sub topics provide a similar hierarchical approach to "topic" definitons.
_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 #107
## May 2019 Ballot Comment: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Submitted by Mitra Rocca; Terrie Reed
Chapter/section: Overall
Url: https://fhircast.hl7.org/
Type: A-SSummary: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Comment: Since the "hub.topics" are meant to be events, it would be useful to create a hierarchy of events using a BNF grammar similar SMRT clinical context scopes. For instance: "session.*" hub.topic scope would correspond to all session-related events or alterantively an could subscribe to either "Session.close" or "session.change". Similarly the "hub.topic" could be centered on a a FHIR resource - similar to SMART scoes - "patient.selected" , "device.selected". The lesson of CCOW is that standardizeding the "contexts" and creating an extensible grammar/sytax are both needed for adption. Pub/sub topics provide a similar hierarchical approach to "topic" definitons.
_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 #107
## May 2019 Ballot Comment: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Submitted by Mitra Rocca; Terrie Reed
Chapter/section: Overall
Url: https://fhircast.hl7.org/
Type: A-SSummary: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Comment: Since the "hub.topics" are meant to be events, it would be useful to create a hierarchy of events using a BNF grammar similar SMRT clinical context scopes. For instance: "session.*" hub.topic scope would correspond to all session-related events or alterantively an could subscribe to either "Session.close" or "session.change". Similarly the "hub.topic" could be centered on a a FHIR resource - similar to SMART scoes - "patient.selected" , "device.selected". The lesson of CCOW is that standardizeding the "contexts" and creating an extensible grammar/sytax are both needed for adption. Pub/sub topics provide a similar hierarchical approach to "topic" definitons.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 15 2019 at 22:05):
isaacvetter commented on Issue #107:
Proposed resolution: Duplicate of #108
Github Notifications (FHIRcast) (Jul 15 2019 at 22:05):
isaacvetter labeled Issue #107:
## May 2019 Ballot Comment: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Submitted by Mitra Rocca; Terrie Reed
Chapter/section: Overall
Url: https://fhircast.hl7.org/
Type: A-SSummary: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Comment: Since the "hub.topics" are meant to be events, it would be useful to create a hierarchy of events using a BNF grammar similar SMRT clinical context scopes. For instance: "session.*" hub.topic scope would correspond to all session-related events or alterantively an could subscribe to either "Session.close" or "session.change". Similarly the "hub.topic" could be centered on a a FHIR resource - similar to SMART scoes - "patient.selected" , "device.selected". The lesson of CCOW is that standardizeding the "contexts" and creating an extensible grammar/sytax are both needed for adption. Pub/sub topics provide a similar hierarchical approach to "topic" definitons.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jul 17 2019 at 14:45):
wmaethner commented on Issue #107:
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
@NiklasSvenzen moved the following disposition, seconded by @gkustas
Disposition: : Persuasive with Mod
Disposition Comment:: We will create a simple syntax for FHIRcast events modeled after SMART's scope syntax and based upon FHIR resources. Except for the "meta" sync-error event, we will move the Event Catalog out of the specification. sync-error will be renamed to syncerror. Per other comments, we will also define a process for the publishing of new events within the Event Catalog.FHIRcast events are an extensible syntax based upon FHIR resources, following the SMART on FHIR scope syntax.
Expressed in EBNF notation, the FHIRcast syntax for workflow related events is:
hub.events ::= ( fhir-resource ) '-' ( 'open' | 'close' )
imageThe event notification or request for context change message SHALL be accompanied by the fhir-resource named in the hub.events. Further, the Event Catalog may define additional resources to be included within the event.
Disposition:
Disposition Comment::+1: For: 14
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
svg generated from railroad diagrams
relevant to: #128, ...
Github Notifications (FHIRcast) (Jul 17 2019 at 14:45):
wmaethner labeled Issue #107:
## May 2019 Ballot Comment: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Submitted by Mitra Rocca; Terrie Reed
Chapter/section: Overall
Url: https://fhircast.hl7.org/
Type: A-SSummary: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Comment: Since the "hub.topics" are meant to be events, it would be useful to create a hierarchy of events using a BNF grammar similar SMRT clinical context scopes. For instance: "session.*" hub.topic scope would correspond to all session-related events or alterantively an could subscribe to either "Session.close" or "session.change". Similarly the "hub.topic" could be centered on a a FHIR resource - similar to SMART scoes - "patient.selected" , "device.selected". The lesson of CCOW is that standardizeding the "contexts" and creating an extensible grammar/sytax are both needed for adption. Pub/sub topics provide a similar hierarchical approach to "topic" definitons.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:50):
wmaethner closed Issue #107:
May 2019 Ballot Comment: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Submitted by Mitra Rocca; Terrie Reed
Chapter/section: Overall
Url: https://fhircast.hl7.org/
Type: A-SSummary: Provide etensible syntax for "hub.topic" scopes similar to SMART scopes and consistent with Pub/Sub event processing best-practices. This grammar could be used ot create an extensible event catalog.
Comment: Since the "hub.topics" are meant to be events, it would be useful to create a hierarchy of events using a BNF grammar similar SMRT clinical context scopes. For instance: "session.*" hub.topic scope would correspond to all session-related events or alterantively an could subscribe to either "Session.close" or "session.change". Similarly the "hub.topic" could be centered on a a FHIR resource - similar to SMART scoes - "patient.selected" , "device.selected". The lesson of CCOW is that standardizeding the "contexts" and creating an extensible grammar/sytax are both needed for adption. Pub/sub topics provide a similar hierarchical approach to "topic" definitons.
_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
