The claims system checks evidence and decides settlement; only approved documents proceed to acknowledgement or signing.
If the table is wider than its frame, scroll horizontally to see all columns; use arrow keys when the table region has focus.
| Control point | Applicable design |
|---|---|
| Actors | Claimant and claims handler |
| Trigger | Assess claim evidence and approve settlement |
| Source system | Claims management system |
| Documents | Claim documents, acknowledgements and settlement agreement |
| Approval control | Assess claim evidence and approve settlement |
| Identity and authority | Match the participants, representation authority and document scope before requesting authorization. |
| Signing route | API or Agent connects an agreed VNeID/RS-HUB or Trusted SIC route; fallback requires an approved deployment policy. |
| Business exceptions | Missing evidence; dispute; beneficiary change |
| Downstream system | Claims management / payments |
The claims system checks evidence and decides settlement; only approved documents proceed to acknowledgement or signing.
Claimant; assessor; settlement approver review the document and representation authority before authorizing signing.
Correlate the signing request with claim record and settlement documents and its approved version; retain the transaction reference.
The approved provider creates the signature using the applicable certificate and authorization; do not change routes without approval.
Link claim, decision, signed record and payment reference; a signature does not establish payment completion.
Missing evidence; dispute; beneficiary change.
The Claims management system owner decides whether to amend, cancel or request a new signature. Reconcile delayed callbacks against the original transaction before creating a replacement.
This is a reference implementation workflow. The organization determines business policy, legal requirements and acceptance conditions.
