Yazh (Yaal), our Integration Gateway, brings a single claim from a legacy system or archive into your claims system on demand. Older history stays in the archive until it is needed.
The Problem
Old Claims Are Either in the Way or Out of Reach
Carriers moving to a new claims system must decide what to do with years of claim history. Loading all of it is expensive, and leaving it behind makes it hard to access.
Loading All of History Weighs on the New System
Carriers avoid storing years of rarely used history there because it can slow performance, so they leave it in the legacy system or archive.
Old Claims Stay Behind in Legacy
Closed claims often stay in the legacy system, and reopened claims have to be converted by hand.
A Claim Needs Its Policy First
A claims system cannot create a claim without a policy, so the related policy term must also exist in the new system.
The Solution
How does InsOps Help?
Yazh (Yaal) Brings Legacy Claims Over 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 your claims system.
Policy First, Then the Claim
If the policy term is not in your new system, it gets created, and the claim is added on top.
Mapped Once, Confirmed by a Person
LiLa suggests the mapping when the first payload arrives, and a person confirms it. Later payload changes are edited in the portal.
Value Translation
Yazh (Yaal) converts your legacy codes into the values your claims system expects.
Test Calls and Secured Requests
You can test the route before go-live. Every request passes through a firewall, authentication, authorization, and validation.
Every Claim on One Dashboard
Your team can see each request, response and error in one place.
FAQ
When does it make sense to bring over a single claim?
Do we have to migrate our claim history first?
Who confirms the mapping?
How is this different from batch and big-bang migration?