Stream: fhircast-github
Topic: fhircast-docs / Issue #183 May 2019 Ballot Comment:
Github Notifications (FHIRcast) (Apr 30 2019 at 19:53):
hl7-fhircast-bot opened Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_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 #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_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 #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_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 #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_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 edited Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 05 2019 at 03:19):
isaacvetter commented on Issue #183
NOTE on ANSI modal verbs: The usage of ANSI modal verbs consistently provides a vehicle for quickly discerning the conformance criteria.
HL7 adheres to ISO/IEC directive, Appendix G: ANSI modal verbs ("SHALL", "SHOULD", "MAY", "SHALL NOT", "SHOULD NOT", "MAY NOT") SHALL be capitalized. See FHIR conformance rules, section 2.1.0.1 "Conformance Language". http://hl7.org/implement/standards/fhir/conformance-rules.html
Github Notifications (FHIRcast) (May 07 2019 at 12:42):
wmaethner labeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:24):
NiklasSvenzen unlabeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:24):
NiklasSvenzen labeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:31):
wmaethner labeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:31):
wmaethner unlabeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 15:31):
wmaethner unlabeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (May 08 2019 at 17:54):
wmaethner labeled Issue #183
## May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 04 2019 at 20:36):
isaacvetter labeled Issue #183:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_This issue was imported by @hl7-fhircast-bot from the consolidated FHIRcast May 2019 ballot spreadsheet._
Github Notifications (FHIRcast) (Sep 11 2019 at 20:41):
wmaethner closed Issue #183:
May 2019 Ballot Comment:
Submitted by Anthony Julian
Chapter/section: Overview
Url: https://fhircast.hl7.org/specification/May2019Ballot/index.html
Type: NEG :exclamation: Clarification
In Person requested: Yes :bust_in_silhouette:Summary:
Comment: subscring misspelled; See note on ANSI modal verbs; saying "the app deletes" is not strong enough. If you don’t mind lots of junk in the subscriptions, you could say "The app MAY delete". But best practice would be "The app SHALL delete". Oauth authentication is mandatory.
Existing wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscring app may query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app deletes its subscription when it no longer wants to receive notifications. In all cases the app authenticates to the Hub with an OAuth 2.0 bearer token.
Proposed wording: An app subscribes to specific workflow events for a given session, the subscription is verified and the app is notified when those workflow events occur; for example, by the clinician opening a patient's chart. The subscribing app MAY query a session's current context and initiate context changes by accessing APIs exposed by the Hub. The app SHALL delete its subscription when it no longer wants to receive notifications. In all cases the app SHALL authenticate to the Hub with an OAuth 2.0 bearer token.
_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
