Stream: fhircast-github
Topic: fhircast-docs / Issue #101 May 2019 Ballot Comment: Clari...
Github Notifications (FHIRcast) (Apr 30 2019 at 19:51):
hl7-fhircast-bot opened Issue #101
## May 2019 Ballot Comment: Clarify where an event's "key" value comes from.
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Event Catalog
Url:
Type: A-S ClarificationSummary: Clarify where an event's "key" value comes from.
Comment: It's not clear to the reader that the "key" value is defined in the specification under the "Context" header in the table assosiated with each event. This should be clarified and improved, such that an implementer knows what value to use for key and future event creators know to define these keys.
_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 #101
## May 2019 Ballot Comment: Clarify where an event's "key" value comes from.
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Event Catalog
Url:
Type: A-S ClarificationSummary: Clarify where an event's "key" value comes from.
Comment: It's not clear to the reader that the "key" value is defined in the specification under the "Context" header in the table assosiated with each event. This should be clarified and improved, such that an implementer knows what value to use for key and future event creators know to define these keys.
_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 #101
## May 2019 Ballot Comment: Clarify where an event's "key" value comes from.
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Event Catalog
Url:
Type: A-S ClarificationSummary: Clarify where an event's "key" value comes from.
Comment: It's not clear to the reader that the "key" value is defined in the specification under the "Context" header in the table assosiated with each event. This should be clarified and improved, such that an implementer knows what value to use for key and future event creators know to define these keys.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 30 2019 at 03:17):
isaacvetter commented on Issue #101:
Proposed resolution: Persuasive
Proposed resolution comment: Clarify that the specification dictates the value of an event's "key".
Github Notifications (FHIRcast) (Jun 18 2019 at 15:49):
wmaethner labeled Issue #101:
## May 2019 Ballot Comment: Clarify where an event's "key" value comes from.
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Event Catalog
Url:
Type: A-S ClarificationSummary: Clarify where an event's "key" value comes from.
Comment: It's not clear to the reader that the "key" value is defined in the specification under the "Context" header in the table assosiated with each event. This should be clarified and improved, such that an implementer knows what value to use for key and future event creators know to define these keys.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Jun 18 2019 at 15:49):
wmaethner commented on Issue #101:
## :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) (Sep 11 2019 at 20:51):
wmaethner closed Issue #101:
May 2019 Ballot Comment: Clarify where an event's "key" value comes from.
Submitted by @MichaelTClifton on behalf of @wmaethner (wmaethne@epic.com )
Chapter/section: Event Catalog
Url:
Type: A-S ClarificationSummary: Clarify where an event's "key" value comes from.
Comment: It's not clear to the reader that the "key" value is defined in the specification under the "Context" header in the table assosiated with each event. This should be clarified and improved, such that an implementer knows what value to use for key and future event creators know to define these keys.
_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
