DATA DELIVERY · ADDED TO VCA CLAIMSCORE

DataBridge

DataBridge is the add-on to VCA ClaimsCore that pushes your claims data into your own data warehouse, on a schedule you choose.

TYPICAL FOR

VCA CLAIMSCORE

Every Claim Your Team Handles

  • Worked by adjusters and managers
  • In your own loss types and terms

The record stays here, in VCA

WHERE IT LANDS

Your Own Data Warehouse

  • Structured tables
  • The fields and tables you ask for
  • Delivered securely

Governed and queried by your own team

THE PROBLEM IT SOLVES

The reports your business runs on are only as current as the claims data behind them. Getting that data out usually means a manual export or a custom API project, and by the time it lands it is out of date and needs cleaning.

WHAT IT DOES

How does DataBridge deliver your claims data?

As structured extracts from ClaimsCore, into infrastructure you own.

Delivery

Direction
One way, out of VCA ClaimsCore
Schedule
Hourly, daily or weekly, as you set it
Each Delivery
Only what changed since the last one

Where It Lands

Destination
Your own data warehouse
Data Model
Structured tables, for analysis
Your Additions
More fields or tables, on request

Security

In Delivery
Extracted and delivered securely
Access
Yours to control, in your own environment
The Platform
Covered by VCA's SOC 1 and SOC 2 reports
Security at VCA →

WHY IT MATTERS

What Changes When the Data Is Already There

Your analysts stop exporting claims data by hand and start from structured tables in your own warehouse.

  • Current Data for Analysis

    Dashboards, reports and analysis run on data as current as the last delivery, instead of on the last manual export.

  • Claims Beside Your Policy Data

    Your analysts work with the claims data beside the policy data already in your warehouse, instead of reconciling separate exports.

  • No Connector to Maintain

    Your data team gets the feed without building a custom API connector or keeping one running.

  • Reports Under Your Governance

    Management and compliance reports run from the copy in your own warehouse, under your own access controls.

HOW IT FITS

Where does DataBridge fit?

ClaimsCore stays the record the claim is worked in, and each connection around it does one job. DataBridge's job is your warehouse.

  • Policy Data InPolicyConnect brings policy and coverage detail onto the claim from your policy administration system, at first notice.PolicyConnect →
  • Claims Data OutDataBridge delivers your claims data to your warehouse, for your analysts to work from.The Delivery Spec →
  • Partner and Finance SystemsVCA's API framework connects policy-system, partner and finance systems.What VCA Connects To →

How a Carrier Runs It →Captives and Self-Insureds →VCA Insights →

WHY VCA

Why Data Leaders Choose VCA

Your feed is only as good as the platform behind it, and VCA goes deep in claims.

  • Depth of Claims ExpertiseWhat reaches your warehouse comes from the claims your team works in ClaimsCore every day, in a platform built from the claim up, by an adjuster, for the people who work the claim.Why VCA →
  • Speed of ImplementationDiscovery first, then live in weeks, because VCA sticks to the essentials of claims. ClaimsCore goes live in 3 to 4 weeks on a Standard License, 8 to 16 weeks on an Enterprise License, and 12 weeks to 6 months on a Carrier License.
  • Capital EfficiencyNo rip-and-replace across a suite. ClaimsCore is the claims layer beside the systems you already run, at a fraction of what a core replacement costs, and DataBridge is added when your data team wants the feed.

Client Stories, by Seat →

Questions About DataBridge

What is DataBridge?

DataBridge is the add-on to VCA ClaimsCore that delivers your claims data out of VCA and into infrastructure you own: your own data warehouse. It pushes structured, incremental updates on a schedule you choose, hourly, daily or weekly, and fields or tables can be added on request.

What data does DataBridge deliver?

Your claims data from VCA ClaimsCore, as structured tables built for analysis. Fields or tables can be added on request, to meet the reporting your analysts do.

Does DataBridge send data back into VCA?

No. DataBridge runs one way, out of VCA ClaimsCore. Policy data comes in through PolicyConnect, and partner and finance systems connect through VCA's API framework.

How current is the data DataBridge delivers?

As current as the last delivery. DataBridge delivers on a schedule you set, as often as hourly, or daily or weekly, and each delivery carries only what changed since the last one, so it stays small.

How is data secured in delivery?

DataBridge extracts and delivers the data securely, into your own environment, where you control access and storage. The platform the data leaves from is covered by VCA's SOC 1 and SOC 2 reports, examined by Prescient Assurance.

Who is DataBridge for?

DataBridge is built for carriers, MGAs and TPAs: their data and analytics teams, who build reporting, dashboards and analysis in their own data warehouse. If your team does not run a warehouse, ClaimsCore's own reports cover its claims, and VCA Insights adds analytics inside VCA, in a single dashboard you can view for a specific team or a specific client.

What does setting up DataBridge involve?

A VCA implementation starts from your existing claims process: the goal is to move it into VCA, not to change everything your team does. Each DataBridge feed is set up with your team: the fields and tables your reporting needs, and how often it is delivered. Your team does not build or maintain a custom API connector.

Can we run ClaimsCore without DataBridge and add it later?

Yes. VCA ClaimsCore is complete on its own, and DataBridge is added to it when you want your claims data in your own warehouse. Adding it later does not mean a second claims system: DataBridge works from the claims already in ClaimsCore.

Bring us a claim where the promise was hard to keep

Bring the reports your team builds today. We will specify the feed with you before anything is built.

Request a Demo

Security at VCA →How to Evaluate Claims Software →