Open Insurance Is Coming, and Your Data Isn't Ready to Be Shared

Open banking rewired financial services by forcing banks to expose customer data, with consent, through standard APIs. Open insurance is the same idea arriving at our industry — driven by regulation in some markets, by competitive and ecosystem pressure in others — and it asks a question most insurers can't yet answer comfortably: can you expose your data, cleanly and in real time, to a customer or a third party who has the right to it? For a lot of insurers, the honest answer is no, and the reason is the same data foundation problem that shows up everywhere else, now with the doors about to open.

What open insurance actually demands

Strip away the policy debate and open insurance is a set of concrete data capabilities. A customer (or a party they authorize) should be able to access their insurance data — policies, coverage, claims, history — through standard, secure APIs, in real time, with consent governing exactly what's shared and with whom. That's it. And every clause in that sentence is a data-foundation requirement: real-time access, a unified view of the customer's data, standard structure, and granular consent. Each one is something most insurers struggle with even for internal use.

Why insurers aren't ready

  • Real-time access. Open APIs expect current data on demand. If your policy and claims data lives in systems that update in batch and don't expose clean real-time interfaces, you can't serve it — you can only serve a stale snapshot.
  • A unified customer view. "Give this customer their data" assumes you can assemble all of it — across products and systems — for one resolved customer. If your customer 360 is broken internally, it's broken externally too, and now the customer sees the gaps.
  • Consent as data. Sharing with consent means capturing, storing, and enforcing granular, purpose-bound consent — who can see what, for what, until when. Most insurers hold consent as an unstructured checkbox, which can't drive an API.
  • Standardization. Exposing data through common structures means mapping your idiosyncratic internal models to shared schemas — a data-modeling and governance effort, not a quick API wrapper.

Why you can't bolt it on later

The tempting response is to treat open insurance as an API project — build a gateway, expose some endpoints, done. But an API in front of fragmented, batch, ungoverned data just exposes the fragmentation to the outside world. You can't API your way past a customer view you don't have, real-time data you can't produce, or consent you never captured as data. The insurers who'll handle open insurance gracefully are the ones whose internal data foundation — real-time access, resolved customer, governed consent — is already sound. For them, opening up is a controlled extension; for everyone else, it's an exposure of everything that was already broken.

What good looks like

  1. Real-time, API-ready access to policy and claims data, not batch snapshots.
  2. A resolved customer view that can assemble all of a customer's data on demand.
  3. Consent captured and enforced as structured data, granular and purpose-bound.
  4. Internal models mapped to standard schemas, governed so what you expose stays consistent and correct.

Open insurance turns your internal data foundation into an external-facing capability, which means every weakness you tolerated internally becomes visible to customers, partners, and regulators. Getting that foundation right — real-time access, a resolved customer, governed consent, standardized data — is exactly the kind of work we do with insurers at IntelliBooks.

Open insurance isn't primarily an API strategy. It's a data-readiness test, and the doors are opening whether or not you've passed it.

Comments

Post a Comment

Popular posts from this blog

Why Your Insurance Data Warehouse Didn't Fix Anything

You built the data warehouse. It took eighteen months and cost more than planned. Policy data, claims data, billing — it's all in there. The project was declared a success and everyone moved on. And yet: underwriting still can't see the whole customer. The AI initiative is still stalled. Someone still asks for a report and waits three weeks. Nobody says it out loud, but the question hangs there — what exactly did we buy? You're not alone, and it isn't because you built it badly. It's because a warehouse solves a problem you didn't have. The problem a warehouse solves Warehouses solve location . Before: your data was in eight systems. After: it's in one place. That's genuinely valuable — you can run a query across policy and claims without begging two teams for extracts. But notice what that fixes: it fixes where the data is . It doesn't touch what the data means , whether it's trustworthy, or whether the records refer to who you think t...
Read more

Embedded Insurance: Why the API Is the Easy Part

Embedded insurance is the idea that coverage should be offered at the moment of need, inside someone else's product — travel insurance at checkout, device protection when you buy the phone, cover for the rental car in the booking flow. It's one of the fastest-growing distribution models in the industry, and every insurer has a strategy slide about it. Most of those strategies underestimate the same thing, and it isn't the partnerships or the product. It's the data plumbing. Everyone assumes the API is the hard part. The API is the easy part. What embedded insurance really demands The promise of embedded is speed and invisibility: a customer buys a flight and, in the same breath, is offered exactly the right travel cover at exactly the right price, and accepts with one tap. No forms, no friction. Deliver that and you've won. But "exactly the right cover at exactly the right price in one tap" makes brutal demands on your back end: You must price i...
Read more

Insurance Knowledge Graphs: The Foundation AI Needs Before It Can Think

Every insurer wants enterprise AI. Few realise they're missing something much more fundamental. Knowledge. Not data. Knowledge. Insurance companies already possess enormous amounts of information. Policy systems contain customer records. Claims platforms hold loss histories. CRM systems track interactions. Document repositories store underwriting reports. Data warehouses consolidate analytics. Yet AI still struggles to answer surprisingly simple questions. Not because the information doesn't exist. Because the relationships between that information remain invisible. Data tells you what exists A customer database tells you who someone is. A policy database tells you what they bought. A claims system tells you what happened. An accounting platform tells you what was paid. Each system is internally consistent. Together they rarely behave like a connected enterprise. Humans mentally assemble those relationships every day. Computers usually canno...
Read more