Yazh (Yaal), our Integration Gateway, sends changes from your TPAs, vendors and source systems into ClaimCenter in the format it expects. Your adjusters work from the current claim.
The Problem
Claim Changes Reach ClaimCenter Out of Step
Claims keep changing after first notice of loss. TPAs, vendors and source systems send updates, closures and reopenings, and ClaimCenter applies its own rules to each one.
Updates Can Be Rejected as Out of Date
ClaimCenter uses checksums to prevent lost updates. Changes with outdated checksums are rejected, and each connector must handle the resulting errors.
Closures Run Into Validation Rules
In the base configuration, ClaimCenter will not close a claim that still has open exposures. It will not close an exposure that still has open activities. A sender that closes out of order gets an error back.
Reopenings Must Follow ClaimCenter’s Order
A closed claim has to be reopened before its exposures can be reopened. Reopenings can also carry a reason and a note, so each sender has to supply those in the form ClaimCenter accepts.
The Solution
How does InsOps Help?
Yazh (Yaal) Keeps ClaimCenter in Step With Every Claim Change
Mapped once, remapped when payloads change
LiLa suggests the mapping the first time a sender brings a payload. A person confirms it. Later payload changes are edited in the portal.
Value translation for closures and reopenings
Yazh (Yaal) translates a sender’s closure outcomes and reopening reasons into the values ClaimCenter accepts.
Alerts when ClaimCenter adds a required field
Your team gets an alert, and a default value is sent in the meantime so the flow does not break.
Test calls before go-live.
Senders and your team test the route before any live claim change is sent.
Secured requests
Every request passes a firewall, authentication, authorization and validation.
Requests, responses and errors on one dashboard.
Your team sees the status of each request and any error in the same place.
FAQ