Platform

Integration Hub

Sync an insurer's existing systems into iqava — continuously, in one standardized shape — so eligibility, provider networks and analytics work day one, even before anyone migrates.

What it's for

The hardest problem in an insurance network — keeping member lists, policies and claims in step between parties who don't share a database — mostly disappears when the insurer runs on iqava (it's all one system). For insurers not yet on iqava, the Integration Hub delivers the same value by syncing their systems into iqava.

How it works

The Hub promotes iqava's Data Connectors into a platform-wide sync layer. Every source — a SQL database or an HTTP/JSON API — is pulled, mapped to iqava's own canonical model, and loaded idempotently, so a re-sync updates rather than duplicates.

Their systemConnectorMap → canonicalIdentity spineMirrorReconcile

Connect a source
A read-only connection with encrypted credentials — SQL (PostgreSQL, MySQL, SQL Server, Oracle) or a REST API (with paginated pulls: page, offset or cursor).
Map to the canonical model
One mapping profile turns the source's columns into a canonical entity — policy, member, provider, claim, account or contact — LOB-agnostic, so standardizing across many insurers is one profile per source, never source-by-source.
Sync idempotently
An identity spine keys every record by its source id (or a natural key) and remembers a content hash, so an unchanged record is skipped and a changed one is updated — never duplicated. Freshness is tiered: watermark pulls, content hash-diff, or webhook push.
Mirror, then (optionally) master
In mirror modetheir system stays the source of record and synced records are read-only in iqava (no rip-and-replace) — member apps, eligibility and analytics work immediately. When you're ready, cut over to master mode and iqava owns the data.
Trust every run
Each sync reconciles source-vs-iqava counts and control totals; drift surfaces in the run history — an eligibility check nobody trusts is worthless.

Where to find it

Console → Administration → Integration Hub shows your mirror totals per entity, your sources, sync run history with reconciliation, and a browser for the mirrored read model.

What's coming

Available today: SQL + REST sources, the canonical mirror, idempotent sync and the Hub dashboard. On the roadmap: a guided REST-connector & mapping authoring flow, AI-assisted schema mapping, and file-drop (SFTP / email-in) sources.

Related: the Data Connectors guide (the SQL importer the Hub builds on) and Health & Provider Network (a flagship consumer of synced member and provider data).