Notifications

Version Notice: SOFT Integration is available starting from API version 2026-08-01.
The API version you have selected does not include it. Switch to 2026-08-01 to access this functionality.

When the physician finishes the consultation in Invox Genesis, your system needs to know that the clinical result is ready. There are two channels, and they are not mutually exclusive.

ChannelDirectionRequires a public endpointCarries the result
WebhookPushYesYes
WebSocketPullNoNo

Webhook (push)

If your organization has an OnMedicalReportFinished destination configured, the result is delivered to it as soon as the consultation ends. This is the simplest option when your EHR can expose an HTTPS endpoint reachable from the internet.

WebSocket (pull)

If you cannot expose a public endpoint, open a WebSocket connection with the same signature you used to open Invox Genesis. When the consultation ends you receive a lightweight notice, and you then retrieve the result with Get consultation result over an authenticated call.

The WebSocket never transports clinical data or tokens: it only signals that the result is ready. The clinical content always travels over an authenticated HTTPS request or over your signed webhook.

Using both

Configuring the webhook and opening the WebSocket at the same time is a valid and recommended setup: the WebSocket gives you an immediate signal in the physician's browser session, and the webhook guarantees delivery even if the browser was closed.

Both paths are idempotent from your side: correlate them by requestId and ignore the second one you receive.

No channel configured

If the organization has no webhook configured and no WebSocket connection is open, the physician is warned before confirming the end of the consultation that the result will not be sent back automatically. The result is still retrievable with Get consultation result until it expires.

Table of Contents