Update README.md #1
Conversation
Added Changes to Event Payload Bundle Resource with Comments
|
@sjatwood review this PR |
| In addition to the focus resource ID, some events MAY also contain additional context such as the related Patient ID and/or Department ID (see example below). | ||
|
|
||
| As per the Subscriptions R5 Backport IG, the first entry in each notification Bundle will always be a SubscriptionStatus resource which contains metadata about the Subscription associated with the event as well as metadata about the event(s) contained in the Bundle (see `entry[0].resource.notificationEvent[*].focus` below). At present this will be the only entry in the Bundle since `full-resource` payload is not supported at this time. | ||
| As per the Subscriptions R5 Backport IG, the first entry in each notification Bundle will always be a SubscriptionStatus resource which contains metadata about the Subscription associated with the event as well as metadata about the event(s) contained in the Bundle (see `entry[0].resource.notificationEvent[*].focus` below). The second entry will be `AuditEvent` resource which will have information about the event. Additional Detail of the event would be part of the `extension[]` array. Note that extensions would be different for different events. |
There was a problem hiding this comment.
I wouldn't say "second entry" here because we want to leave open the expectation that a single Bundle may contain multiple events. I would rephrase along these lines:
The Bundle will also contain one AuditEvent resource corresponding to each entry in the
entry[0].resource.notificationEventarray. This resource captures some additional metadata about the event such as the user/agent whose action triggered the event as well as topic-specific extensions (where applicable) with additional context such as the related Patient, Department, etc. For a list of which extensions are provided for each subscription topic, see Subscription Topics below.
(and we should add those details below)
There was a problem hiding this comment.
@prasannakumarramani we should also update the example payloads in the sample code (see https://github.com/athenahealth/aone-fhir-subscriptions/blob/main/samplecode/java/send-appointment-notification.sh for example) to include the new payload structure, i.e. extensions instead of additionalContext.
Remove additional context from the example
Add Text to inform the timeout exceeding 2min
Added Changes to Event Payload Bundle Resource with Comments