Yazh (Yaal), our Integration Gateway, brings a single claim from your legacy system or archive into ClaimCenter on demand. Older history stays in the archive until it is
The Problem
Old Claims Are Either in the Way or Out of Reach
Carriers moving to ClaimCenter have to decide what to do with years of claim history. Loading all of it is costly, and leaving it behind makes it hard to reach.
Loading All of History Weighs on ClaimCenter
Carriers do not want years of rarely used claim history sitting in ClaimCenter, where it can slow performance. So they leave it in the legacy system or archive.
Old Claims Stay Behind in Legacy
Guidewire recommends keeping closed claims in the legacy system and manually converting reopened claims into ClaimCenter.
A Claim Needs Its Policy First
ClaimCenter cannot create a claim without a policy. Bringing over one old claim means the policy term it belongs to has to exist in the new system too.
The Solution
How does InsOps Help?
Yazh (Yaal) Brings Legacy Claims Into ClaimCenter When They Are Needed
Pull one claim when it is needed
Your team or system sends a single legacy claim, only when someone needs it in ClaimCenter.
Policy first, then the claim.
If the policy term is not in ClaimCenter yet, it is created, and the claim goes on top of it.
Mapped once, confirmed by a person
LiLa suggests the mapping the first time a payload arrives. A person confirms it, and later payload changes are edited in the portal.
Value translation
Yazh (Yaal) translates your legacy codes into the values ClaimCenter expects.
Test calls and secured requests
Test the route before go-live. Every request passes a firewall, authentication, authorization and validation.
Every claim on one dashboard
Your team sees each request, response and error in one place.
FAQ