AIS can push externally received events to a PACS when the connected PACS agent supports event writing. Use this feature when an event is received outside of the PACS and must be delivered into the PACS through AIS.
Before using the endpoint, make sure the PACS agent supports the ExternalEventsPush feature and that your role has the ExternalEventsPush permission. The PACS must also be connected and active.
To write an event, send the event payload as the request body:
Endpoint:
POST /ais/v1/tenant/{tenantId}/pacs/{pacsId}/externalEvents
Header:
Content-Type: application/json
Example of the request body:
{ "eventType": "example", "eventId": "evt-123" }
The event payload format is PACS-specific. AIS forwards the payload to the PACS agent and does not validate the event content beyond requiring a non-empty body.
AIS accepts the request asynchronously. A successful request returns 202 Accepted with a response URL. Poll that URL to check the result:
GET /ais/v1/tenant/{tenantId}/pacs/{pacsId}/externalEvents/response/{messageId}
When the PACS agent processes the event successfully, the response endpoint returns 204 No Content. If the PACS agent rejects the event or cannot process it, AIS returns the agent error from the response endpoint.
You can also provide a Task-Callback-Uri header on the original request if your tenant is configured to allow callbacks. AIS will call that URI when the operation finishes, and the callback will include the result location.