documentLifecycle
A committed owner event is delivered to each subscribed, verified endpoint. Delivery is at least once with no ordering guarantee. The event id and body remain stable across retries; webhook-timestamp identifies the current attempt. Automatic retries stop within 72 hours of first durable acceptance. Event and delivery history expires after 30 days; current authority is required before each disclosure. Processing completion is separate from clinical publication and patient-record availability. document.downloaded means controlled server retrieval/decryption and durable audit acceptance before byte handoff, without proving remote consumption. Signatures use Standard Webhooks HMAC-SHA256 over webhook-id + '.' + webhook-timestamp + '.' + the exact request bytes.
Headers
- Type: stringwebhook
-id required - Type: stringwebhook
-timestamp required - Type: stringwebhook
-signature required
Body·
- Properties: 1Type: objectdatarequiredEmpty object
- Type: stringidrequired
- Type: stringFormat: date-timetimestamprequired
the date-time notation as defined by RFC 3339, section 5.6, for example, 2017-07-21T17:32:28Z
- typeconst:document.processedrequired
Responses
- 200
Acknowledged; any 2xx response acknowledges delivery
{
"id": "",
"type": "document.processed",
"timestamp": "2026-11-16T18:04:16.498Z",
"data": {
"status": "processed"
}
}