Keep the incident, control state, and evidence together.

Claims Operations starts with evidence already in VitalSec, connects the incident to the bound policy, prepares the evidence package, sends it through the approved carrier connection, and keeps delivery and receipt status with the claim.

Bound-policy contextVersioned evidence packageApproved carrier connectionCarrier receipt status

Claims evidence workflow

Start the claim with evidence that already exists.

The incident, policy, control state, remediation history, and Evidence Continuity evidence do not need to be rebuilt after the fact. Claims Operations carries the authorized evidence into the claim.

Open the claim

Connect the incident to the bound policy so the claim starts with the correct organization and policy context.

Prepare the evidence

Create a versioned claims evidence package from the incident history, supporting proof, control state, and relevant records.

Confirm the carrier connection

Match the bound carrier to an approved Claims Operations connection before evidence leaves the organization.

Send

Send the approved evidence package through the carrier connection and prevent retries from creating duplicate submissions.

Track receipt

Keep the carrier reference and receipt status with the claim through submitted, acknowledged, under review, closed, or declined.

Claims Operations evidence delivery

Incident → evidence package → carrier receipt

Incident + bound policy

The claim begins in the correct organization and policy context.

Versioned evidence package

The evidence is fixed to a version before it is sent.

Approved carrier connection

The carrier reference comes back with the submission.

Carrier receipt status

Submitted

Acknowledged

Under review

Closed / Declined

Claims evidence package

Keep an exact version of what was sent.

Each package represents the claim evidence at that point in time. If the evidence later changes, Claims Operations creates a new version instead of silently changing the package that was already sent.

Incident timeline and current claim context

Control state and evidence relevant to the incident

Remediation, retest, and follow-up observations

Evidence Continuity evidence and source history

Bound policy and carrier context

Package version and delivery history

Approved carrier delivery

Keep the carrier handoff with the claim.

Claims Operations sends only when the claim is ready, the latest evidence package is fixed to a version, the policy is bound, and the carrier connection is approved. The claim keeps the carrier route, external reference, and delivery result so the handoff can be traced later.

Approved carrier connection

External carrier reference

Safe retry handling

Policy-to-carrier match

Carrier connections support standard secure authentication methods, including API keys, bearer tokens, OAuth client credentials, and mTLS where required by the carrier.

Delivery and receipt status

Know what was sent and where the claim stands.

Claims Operations keeps the external carrier reference and explicit receipt status with the claim instead of treating a send action as the end of the workflow.

SUBMITTED