FHIR Chat · fhircast-docs / Issue #137 May 2019 Ballot Comment: Corre... · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / Issue #137 May 2019 Ballot Comment: Corre...


view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot opened Issue #137

## May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot labeled Issue #137

## May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot labeled Issue #137

## May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Apr 30 2019 at 19:52):

hl7-fhircast-bot edited Issue #137

## May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 18:33):

wmaethner commented on Issue #137

## Montreal May 2019 Working Group Vote

Isaac Vetter moved the following disposition, seconded by Ricardo Quintano

Disposition: Persuasive
Disposition Comment: Will fix as described

:+1: For: 12
:expressionless: Abstain: 0
:-1: Against: 0

:tada: The motion passed! :tada:

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 18:33):

wmaethner labeled Issue #137

## May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Jul 02 2019 at 18:55):

wmaethner labeled Issue #137:

## May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._

view this post on Zulip Github Notifications (FHIRcast) (Sep 11 2019 at 20:45):

wmaethner closed Issue #137:

May 2019 Ballot Comment: Correct word identifer: should be identifier

Submitted by Ricardo Quintano Neira
Chapter/section: Event Notification Request
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: A-T

Summary: Correct word identifer: should be identifier

Comment: Correct word identifer: should be identifier

"In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub."

Existing wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifer that is universally unique for the Hub.
Proposed wording: In addition to a description of the subscribed event that just occurred, the notification to the subscriber MUST include an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub.


_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