Stream: fhircast-github
Topic: fhircast-docs / Issue #97 May 2019 Ballot Comment: Clarif...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #97
## May 2019 Ballot Comment: Clarify that custom events are permitted.
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Event Notification Request Details
Url:
Type: A-S ClarificationSummary: Clarify that custom events are permitted.
Comment: The Event Catalog section specifically enables custom/extended events, but this section implies that they're not allowed. We should clarify this.
Existing wording: The hub.event is a user workflow event, from the Event Catalog.
Proposed wording: The hub.event is a user workflow event, from the Event Catalog (or an organization-specific event in reverse-domain name notation).
_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 #97
## May 2019 Ballot Comment: Clarify that custom events are permitted.
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Event Notification Request Details
Url:
Type: A-S ClarificationSummary: Clarify that custom events are permitted.
Comment: The Event Catalog section specifically enables custom/extended events, but this section implies that they're not allowed. We should clarify this.
Existing wording: The hub.event is a user workflow event, from the Event Catalog.
Proposed wording: The hub.event is a user workflow event, from the Event Catalog (or an organization-specific event in reverse-domain name notation).
_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 #97
## May 2019 Ballot Comment: Clarify that custom events are permitted.
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Event Notification Request Details
Url:
Type: A-S ClarificationSummary: Clarify that custom events are permitted.
Comment: The Event Catalog section specifically enables custom/extended events, but this section implies that they're not allowed. We should clarify this.
Existing wording: The hub.event is a user workflow event, from the Event Catalog.
Proposed wording: The hub.event is a user workflow event, from the Event Catalog (or an organization-specific event in reverse-domain name notation).
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 30 2019 at 03:21):
isaacvetter commented on Issue #97:
Proposed resolution: Persuasive
Proposed resolution: Will update wording as suggested.
Github Notifications (FHIRcast) (May 30 2019 at 03:21):
isaacvetter labeled Issue #97:
## May 2019 Ballot Comment: Clarify that custom events are permitted.
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Event Notification Request Details
Url:
Type: A-S ClarificationSummary: Clarify that custom events are permitted.
Comment: The Event Catalog section specifically enables custom/extended events, but this section implies that they're not allowed. We should clarify this.
Existing wording: The hub.event is a user workflow event, from the Event Catalog.
Proposed wording: The hub.event is a user workflow event, from the Event Catalog (or an organization-specific event in reverse-domain name notation).
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:51):
wmaethner labeled Issue #97:
## May 2019 Ballot Comment: Clarify that custom events are permitted.
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Event Notification Request Details
Url:
Type: A-S ClarificationSummary: Clarify that custom events are permitted.
Comment: The Event Catalog section specifically enables custom/extended events, but this section implies that they're not allowed. We should clarify this.
Existing wording: The hub.event is a user workflow event, from the Event Catalog.
Proposed wording: The hub.event is a user workflow event, from the Event Catalog (or an organization-specific event in reverse-domain name notation).
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:51):
wmaethner commented on Issue #97:
## :landline: II Working Group Vote (6-18-2019)
Block vote@isaacvetter moved the following disposition, seconded by Ricardo Quintano Neira
Disposition: Persuasive
Disposition Comment: Will fix as described in the issue comments or by the commenter:+1: For: 10
:expressionless: Abstain: 2
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Jul 02 2019 at 18:27):
wmaethner commented on Issue #97:
@isaacvetter Are custom events still allowed if we are going with the new event definition through FHIR resources, so does this proposal still make sense?
Github Notifications (FHIRcast) (Sep 11 2019 at 20:52):
wmaethner closed Issue #97:
May 2019 Ballot Comment: Clarify that custom events are permitted.
Submitted by @MichaelTClifton on behalf of @isaacvetter (isaac@epic.com )
Chapter/section: Event Notification Request Details
Url:
Type: A-S ClarificationSummary: Clarify that custom events are permitted.
Comment: The Event Catalog section specifically enables custom/extended events, but this section implies that they're not allowed. We should clarify this.
Existing wording: The hub.event is a user workflow event, from the Event Catalog.
Proposed wording: The hub.event is a user workflow event, from the Event Catalog (or an organization-specific event in reverse-domain name notation).
_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
