Fires after a claim status save that changed the status. Every status route (the claim page, the API, staff FNOL and agent or insured submission) saves through claims.views.save_claim_status, which emits this event once the change is committed. previous_status is None when the claim had no status yet. changed_via tells an agent or insured submission apart from any other status change. revision_id is the policy revision in force on the loss date.
Field
Value
Topic
claims.claim_status_changed
Schema ID
BritecoreClaimStatusChanged.v1
Version
1.0.0
Payload schema
Code
{ "$schema": "https://json-schema.org/draft/2020-12/schema", "$id": "https://docs.britecore.com/schemas/events/claim_status_changed.json", "title": "ClaimStatusChangedEvent", "description": "Fires after a claim status save that changed the status. Every status route (the claim page, the API, staff FNOL and agent or insured submission) saves through ``claims.views.save_claim_status``, which emits this event once the change is committed. ``previous_status`` is None when the claim had no status yet. ``changed_via`` tells an agent or insured submission apart from any other status change. ``revision_id`` is the policy revision in force on the loss date.", "type": "object", "properties": { "event_id": { "type": "string", "format": "uuid", "description": "Unique identifier for this event instance." }, "event_date": { "type": "string", "format": "date-time", "description": "Timestamp the event was emitted (UTC)." }, "schema_id": { "type": "string", "description": "Schema identifier. Stable per event type.", "const": "BritecoreClaimStatusChanged.v1" }, "version": { "type": "string", "description": "Schema version.", "const": "1.0.0" }, "topic": { "type": "string", "description": "Topic the event was published on." }, "triggering_user": { "type": "object", "description": "User that triggered the event.", "properties": { "id": { "type": "string" }, "external_system_reference": { "type": "string" } } }, "data": { "type": "object", "properties": { "claim_id": { "type": "integer" }, "claim_number": { "type": "string" }, "policy_id": { "type": "integer" }, "revision_id": { "type": "string" }, "previous_status": { "type": "string" }, "status": { "type": "string" }, "has_policy": { "type": "string" }, "changed_via": { "type": "string" } }, "required": [ "claim_id", "claim_number", "policy_id", "revision_id", "previous_status", "status", "has_policy", "changed_via" ] } }, "required": [ "event_id", "event_date", "schema_id", "version", "topic", "data" ]}
The schema is also published as a standalone JSON Schema artefact you can
fetch and consume programmatically. See schemas/events/claim_status_changed.json
on the published portal.