FHIR Chat · fhircast-docs / PR #316 Simple wording fixes to Event Not... · fhircast-github

Stream: fhircast-github

Topic: fhircast-docs / PR #316 Simple wording fixes to Event Not...


view this post on Zulip Github Notifications (FHIRcast) (Jun 22 2020 at 23:45):

wmaethner opened PR #316 from stu2-eventnotification-section to master:

Issues addressed:

  • FHIR-25655
  • FHIR-25838
  • FHIR-25839
  • FHIR-25840
  • FHIR-25841
  • FHIR-25843
  • FHIR-25846
  • FHIR-25848

view this post on Zulip Github Notifications (FHIRcast) (Jun 22 2020 at 23:45):

wmaethner requested isaacvetter and NiklasSvenzen for a review on PR #316.

view this post on Zulip Github Notifications (FHIRcast) (Jun 22 2020 at 23:45):

wmaethner requested isaacvetter and NiklasSvenzen for a review on PR #316.

view this post on Zulip Github Notifications (FHIRcast) (Jun 23 2020 at 17:42):

isaacvetter submitted PR Review.

view this post on Zulip Github Notifications (FHIRcast) (Jun 23 2020 at 17:42):

isaacvetter created PR Review Comment:

`context` | Required | array | An array of named FHIR objects corresponding to the user's context after the given event has occurred. Common FHIR resources are: Patient, Encounter, ImagingStudy and List. The Hub SHALL only return FHIR resources that the subscriber is authorized to receive with the existing OAuth 2.0 access_token's granted `fhircast/` scopes.

view this post on Zulip Github Notifications (FHIRcast) (Jun 23 2020 at 17:42):

isaacvetter updated PR #316 from stu2-eventnotification-section to master:

Issues addressed:

  • FHIR-25655
  • FHIR-25838
  • FHIR-25839
  • FHIR-25840
  • FHIR-25841
  • FHIR-25843
  • FHIR-25846
  • FHIR-25848

view this post on Zulip Github Notifications (FHIRcast) (Jun 23 2020 at 17:42):

isaacvetter submitted PR Review.

view this post on Zulip Github Notifications (FHIRcast) (Aug 04 2020 at 18:10):

isaacvetter submitted PR Review.

view this post on Zulip Github Notifications (FHIRcast) (Aug 04 2020 at 18:10):

isaacvetter created PR Review Comment:

The HTTP request notification interaction to the subscriber SHALL include a description of the subscribed event that just occurred, an ISO 8601-2 formatted timestamp in UTC and an event identifier that is universally unique for the Hub. The timestamp SHOULD be used by subscribers to establish message affinity (message ordering) through the use of a message queue. The event identifier MAY be used to differentiate retried messages from user actions.

view this post on Zulip Github Notifications (FHIRcast) (Aug 04 2020 at 18:10):

wmaethner updated PR #316 from stu2-eventnotification-section to master:

Issues addressed:

  • FHIR-25655
  • FHIR-25838
  • FHIR-25839
  • FHIR-25840
  • FHIR-25841
  • FHIR-25843
  • FHIR-25846
  • FHIR-25848

view this post on Zulip Github Notifications (FHIRcast) (Aug 04 2020 at 18:17):

wmaethner updated PR #316 from stu2-eventnotification-section to master:

Issues addressed:

  • FHIR-25655
  • FHIR-25838
  • FHIR-25839
  • FHIR-25840
  • FHIR-25841
  • FHIR-25843
  • FHIR-25846
  • FHIR-25848

view this post on Zulip Github Notifications (FHIRcast) (Aug 04 2020 at 18:18):

wmaethner merged PR #316.


Last updated: Apr 12 2022 at 19:14 UTC