To receive a webhook at the end of the digitization process, you need to contact the representatives of Ornament to set up the integration on our side.
You will need to provide the endpoint to which the webhook will be sent, and (optionally) an authorization header that should be passed in the requests.
After setting up the integration, the following events will be sent to the specified endpoint:
| Event | Description |
|---|---|
| NEW_SUBMISSION | The Imageset was successfully processed, and a Submission was created. |
| REJECT_IMAGESET | The Imageset was rejected. |
| SPLIT_IMAGESET | As a result of processing, additional Imagesets were generated. This can happen if one Imageset contains lab results for different dates. |
The data sent in the body of the webhook contains the following fields:
| Field | Description |
|---|---|
| id | Unique identifier in UUID format |
| transactionId | Transaction identifier |
| eventTypeTitle | Name of the event type (see table above) |
| version | Data model version. The current version is 1.0 |
| payload | JSON object with data (description of the JSON fields below) |
| createdAt | Event creation date |
| deliveredAt | Date the event was received by the recipient |
The payload field contains the following fields:
| Field | Description |
|---|---|
| iid | Unique UUID of the imageset, which matches the value of the imagesetIid field from the response to the request for sending the file set for digitization |
| sid | Unique UUID of the submission generated as a result of digitization (only for NEW_SUBMISSION events) |
| rejectionReasonId | ID of the rejection reason (only for REJECT_IMAGESET events) |
| comment | Additional text comment (only for REJECT_IMAGESET events) |
You can use these events to initiate the retrieval of digitization or interpretation results.