Stream: fhircast-github
Topic: fhircast-docs / Issue #114 May 2019 Ballot Comment: Why a...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #114
## May 2019 Ballot Comment: Why an app can only subscribe to workflow events?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-QSummary: Why an app can only subscribe to workflow events?
Comment: "An app subscribes to specific workflow events for a given session…"
Why an app can only subscribe to workflow events?
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart.
_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 #114
## May 2019 Ballot Comment: Why an app can only subscribe to workflow events?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-QSummary: Why an app can only subscribe to workflow events?
Comment: "An app subscribes to specific workflow events for a given session…"
Why an app can only subscribe to workflow events?
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart.
_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 #114
## May 2019 Ballot Comment: Why an app can only subscribe to workflow events?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-QSummary: Why an app can only subscribe to workflow events?
Comment: "An app subscribes to specific workflow events for a given session…"
Why an app can only subscribe to workflow events?
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 30 2019 at 03:11):
isaacvetter commented on Issue #114:
Hey @bvdh,
I think that limiting our scope to workflow events is what gives FHIRcast meaning. I'd love to hear your ideas on how this should be different.
Isaac
Github Notifications (FHIRcast) (Jun 18 2019 at 05:40):
bvdh commented on Issue #114:
In previous Connecthaton discussions we also entertained scenario's where the same channel would be used for:
- other context changes (e.g. creation, update, deletion of resources)
- passing speech-2-text information (the text that was recorded).So far as I understand the different resolutions, these events are not in scope of FHIRCast 1.0, but they will be in scope for future versions. As such "workflow-events" seams to be a little bit narrow.
Workflow events seams to suggest to reflect to steps taken in a clinical workflow. I suggest to rephrase it to workflow _related_ events.
Github Notifications (FHIRcast) (Jul 15 2019 at 21:06):
isaacvetter commented on Issue #114:
Proposed resolution: Persuasive
Proposed resolution comment: Update the term "workflow events" to the more flexible phrase "workflow related events" throughout the specification and supporting documentation.
Github Notifications (FHIRcast) (Jul 24 2019 at 14:06):
wmaethner commented on Issue #114:
## :landline: II Working Group Vote (7-24-2019)
Block vote 3Ricardo Quintano Neira moved the following disposition, seconded by @isaacvetter
Disposition: Persuasive
Disposition Comment: Will fix as described in the issue comments or by the commenter:+1: For: 11
:expressionless: Abstain: 1
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jul 24 2019 at 14:10):
wmaethner labeled Issue #114:
## May 2019 Ballot Comment: Why an app can only subscribe to workflow events?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-QSummary: Why an app can only subscribe to workflow events?
Comment: "An app subscribes to specific workflow events for a given session…"
Why an app can only subscribe to workflow events?
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart.
_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 #114:
May 2019 Ballot Comment: Why an app can only subscribe to workflow events?
Submitted by Ricardo Quintano Neira on behalf of @bvdh
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-QSummary: Why an app can only subscribe to workflow events?
Comment: "An app subscribes to specific workflow events for a given session…"
Why an app can only subscribe to workflow events?
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart.
_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
