FHIR Chat · fhircast-docs / Issue #218 May 2019 Ballot Comment: · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / Issue #218 May 2019 Ballot Comment:


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

hl7-fhircast-bot opened Issue #218

## May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


_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:53):

hl7-fhircast-bot labeled Issue #218

## May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


_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:54):

hl7-fhircast-bot labeled Issue #218

## May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


_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 05 2019 at 02:35):

isaacvetter commented on Issue #218

This page is outside of the normative-track content and is intended to be supplemental material that is not part of the specification and is not being balloted.

Mandating application UI feels outside the scope of an interoperability specification. There are also no ANSI modal verbs because this page is not part of the specification.

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 15:10):

wmaethner commented on Issue #218

Like #219 outside the normative track

view this post on Zulip Github Notifications (FHIRcast) (May 08 2019 at 15:10):

wmaethner labeled Issue #218

## May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


_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 19:01):

wmaethner commented on Issue #218

Duplicate of #219

view this post on Zulip Github Notifications (FHIRcast) (May 09 2019 at 13:27):

wmaethner labeled Issue #218

## May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


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

view this post on Zulip Github Notifications (FHIRcast) (Jun 05 2019 at 14:15):

wmaethner unlabeled Issue #218:

## May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


_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 05 2019 at 03:53):

isaacvetter commented on Issue #218:

Mandatory notification of synchronization failure should depend upon the expectations of the user. Additionally, this content is outside of the normative-track content. Resolving this issue.

view this post on Zulip Github Notifications (FHIRcast) (Sep 05 2019 at 03:53):

isaacvetter closed Issue #218:

May 2019 Ballot Comment:

Submitted by Anthony Julian
Chapter/section: Same machine, same time
Url: https://fhircast.hl7.org/syncconsiderations/
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:

Summary:

Comment: Failure notification should be mandated.

Existing wording: . Synchronization failure may introduce clinical risk and therefore user notification of synchronization failure is suggested.


_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