Stream: fhircast-github
Topic: fhircast-docs / Issue #215 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #215
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #215
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #215
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot labeled Issue #215
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 02:52):
isaacvetter commented on Issue #215
Specifically on the imaging study events, we happened to also talk through this issue today during the connectathon and your recommendation was the same outcome that the group came to.
More specifically, we decided that:
1) context changes should generally be a complete replacement of the previously communicated context, not "deltas". (a POST, not PUT, not POST).
3) Events have a fixed context that is defined as part of the specification of that event. A Hub MUST not send additional content not defined in the specification as part a standard event (rather, a custom event should be defined).
3) Patient should be required on the imaging events.
3) The process for defining new events should include:
-- the full and required contextual information
-- the actual event itself should be clearly and described from a workflow such that it can be interoperably implemented.
Github Notifications (FHIRcast) (May 05 2019 at 13:27):
isaacvetter commented on Issue #215
Related to #249
Github Notifications (FHIRcast) (May 21 2019 at 13:04):
wmaethner labeled Issue #215:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 21 2019 at 15:24):
isaacvetter edited a comment on Issue #215:
Specifically on the imaging study events, we happened to also talk through this issue today during the connectathon and your recommendation was the same outcome that the group came to.
More specifically, we decided that:
1) context changes should generally be a complete replacement of the previously communicated context, not "deltas".
3) Events have a fixed context that is defined as part of the specification of that event. A Hub MUST not send additional content not defined in the specification as part a standard event (rather, a custom event should be defined).
3) Patient should be required on the imaging events.
3) The process for defining new events should include:
-- the full and required contextual information
-- the actual event itself should be clearly and described from a workflow such that it can be interoperably implemented.
Github Notifications (FHIRcast) (May 21 2019 at 15:33):
isaacvetter commented on Issue #215:
## :telephone_receiver: CDS Working Group Vote (5-21-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
@isaacvetter moved the following disposition, seconded by @wdvr
Disposition: Persuasive with Mod
Disposition Comment: We will update the imaging study events to require a patient. Will also clarify that context changes should generally be a complete replacement of the previously communicated context, not "deltas".
Further, as part of the to-be-defined process for creating new events, we will also require that events have a fixed context that is defined as part of the specification of that event. A hub MUST not send additional content not defined in the specification as part a standard event (rather, a custom event should be defined).:+1: For: 9
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (May 21 2019 at 15:34):
wmaethner labeled Issue #215:
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 23 2019 at 13:05):
isaacvetter edited a comment on Issue #215:
## :telephone_receiver: II Working Group Vote (5-21-2019)
Meeting notes: https://confluence.hl7.org/display/IMIN/Teleconferences
@isaacvetter moved the following disposition, seconded by @wdvr
Disposition: Persuasive with Mod
Disposition Comment: We will update the imaging study events to require a patient. Will also clarify that context changes should generally be a complete replacement of the previously communicated context, not "deltas".
Further, as part of the to-be-defined process for creating new events, we will also require that events have a fixed context that is defined as part of the specification of that event. A hub MUST not send additional content not defined in the specification as part a standard event (rather, a custom event should be defined).:+1: For: 9
:expressionless: Abstain: 0
:-1: Against: 0:tada: The motion passed! :tada:
Github Notifications (FHIRcast) (Sep 10 2019 at 18:45):
isaacvetter closed Issue #215:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Events
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: FHIR patient resource in context should NEVER be optional.
_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
