# Health Plans: Your BI Tells You MLR Moved. Can Your AI Tell You Why? > Source: > Published: 2026-09-11 18:26:59+00:00 by [Aaron Zavora](/blog/author/aaron-zavora) and [Jonathan Thompson](/blog/author/jonathan-thompson) A health plan CFO closes the month after the usual round of extracts, spreadsheets, and manual reconciliation, and sees the financials are behind budget on a higher-than-expected medical loss ratio (MLR). A BI dashboard can surface the variance quickly. But “MLR is up” isn’t really the answer. It’s the beginning of the question. *Which line of business or market is driving it?*  *Are claim costs up and, if so, due to utilization, unit cost, or service mix?*  *Was a group or product mispriced?*  *Did population morbidity change?*  *And what corrective action can be taken?* The real opportunity for AI in payer finance isn't identifying the variance. It's understanding what caused it and what to do about it. AI transformation in finance results in three things changing at once. Answers arrive in minutes instead of a reporting cycle. Leaders double-click on their own, without a canned report or waiting on an analyst. AI can look past claims, revenue, and membership to clinical information, quality measures, and risk scores, reading all of it at the same time to assess what is driving the variance. That work was never practical when the expertise for both the data and the subject matter was siloed. The challenge then becomes whether AI can understand enough about a health plan’s data and business for finance to trust and act on its insights. That’s where Databricks and Abacus come together. Databricks provides the data and AI capabilities that let organizations interact with governed enterprise data in new ways. Abacus brings the payer-specific data foundation, business context, and operational knowledge those capabilities need when the questions involve healthcare finance. For years, business intelligence worked by anticipating the questions someone would want to ask. Teams built reports. Analysts created dashboards. Executives reviewed the metrics someone had decided belonged on the page. When a number moved, figuring out why meant leaving the dashboard, finding the right analyst or team to investigate, pulling another report or reconciling multiple systems of record. And every answer left something behind: another report to run, another dashboard to build and maintain. Each one was already stale by the time the next question arrived. More work for the team and diminishing returns. Conversational AI changes that interaction model. Instead of stopping at what a dashboard was designed to show, a finance leader can ask a question in plain language, get an answer, and follow it with another question based on what they just learned. The experience starts to look less like navigating reports and more like investigating the business. What really breaks down is the barrier between two kinds of expertise. The executive knows the business and owns the decision-making but cannot query the data; the analyst knows the data, where it lives, how it is structured, how to manipulate it, but not always which question matters. AI collapses that handoff: the person who needs the answer can now ask for it directly. But the quality of that conversation depends on what the AI understands underneath it. For years, the data modernization question was largely about access: can we bring claims, membership, provider, contract, clinical, and financial data together so people can use it? That remains essential, *but AI adds another requirement*. It needs to understand what that data means. Consider the metric of MLR, the share of premium revenue spent on medical care for a plan’s members. Easy to define, hard to calculate. Claims and premiums come on different structures and different timelines, and “medical” expense is really a stack of components, including medical claims, pharmacy claims and rebates, incurred but not reported (IBNR), payment integrity recoveries, risk adjustment transfers, provider settlements, and more. Then it has to be cut by line of business, market, or product, and defining those cohorts takes business logic that never comes out of the box. Without that context, an AI system can have access to enormous amounts of data and still not produce adequate insights. Much of this business context has traditionally lived in different places: *For AI to answer finance questions reliably, more of that context has to become explicit, consistent, and reusable.* That is why a payer-specific data foundation matters. Health plan data does not arrive neatly organized around the questions executives want to ask. Claims, eligibility, provider, contract, clinical, and financial information come from different systems, in different formats, with different relationships and timing. Before AI can reason across it effectively, the data has to be connected and organized in a way that reflects how a health plan operates. Abacus provides that payer-specific foundation: bringing healthcare data together in a consistent structure and adding the business context needed to understand the relationships among members, claims, providers, contracts, clinical information, and financial measures. Even on the same underlying data, the “same” metric is often defined differently depending on who is calculating it. One version lands in the CFO’s monthly reporting package, while another shows up in an ad hoc analytics request, and eventually someone has to reconcile them. AI does not solve that problem on its own. Without consistent definitions, it amplifies it. For finance leaders, the issue isn't simply accuracy. It's confidence that the answer reflects how the business operates. The same definitions that let finance, actuarial, and operations teams work from a consistent view of performance also give AI the context it needs to interpret a question correctly. The goal isn’t simply one place where the data lives; it’s a consistent understanding of what the data means wherever it is used, whether an executive is asking conversationally or an analyst is producing a traditional report. Go back to the CFO. MLR is above budget. Where? What’s driving it? Which populations, services, or providers account for the change? And what should the organization do next? Each question requires more context than the one before it. The first needs a financial measure and a budget comparison. The second needs the components underneath the variance. The third crosses claims, membership, provider, contract, and care management data. By the fourth, the conversation has moved from financial reporting into operations. That’s why the real opportunity isn’t a better way to display a KPI. It’s a connected path from executive signal to operational double-clicks, one finance can walk without repeatedly handing the problem back to analysts to reconcile another set of reports or data points. The AI doesn’t replace the judgment about what the organization should do; it shortens the distance between seeing that something changed and understanding it well enough to act. Without the back-and-forth, each iteration is faster, and faster iteration raises the value of the decision itself: care management activities start sooner, emerging trends get priced in earlier, and corrective action happens while it can still change the outcome. MLR is a useful example because it sits at the intersection of finance and operations, but the underlying architecture isn’t specific to MLR. The same connected payer data and business context can support questions across payment integrity, total cost of care, risk adjustment, quality, and provider performance. That changes how health plans can think about AI investment. The alternative is a collection of disconnected AI use cases, each built around its own data, its own definitions, and its own view of the business. It’s the same fragmentation health plans have spent years trying to eliminate, only with an AI interface on top. A common payer intelligence foundation creates a different path: get the underlying data and context right once, then reuse it as new questions, workflows, and AI experiences emerge. A health plan that has already connected and contextualized its data across use cases has a head start when new questions arise. On one foundation, AI can look across multiple domains simultaneously rather than one at a time. Poor performance is rarely driven by a single variable, whether underwriting, care management, risk adjustment, quality, network, or provider engagement. It is the interaction among them that matters, yet that multifaceted question is difficult to answer today because each domain sits with a different team and dataset. Databricks and Abacus solve different parts of this problem. Databricks provides the data and AI platform capabilities for governing enterprise data and building AI-powered analytical experiences, including conversational experiences that allow business users to ask questions about organizational data in natural language. Abacus brings the payer-specific foundation those experiences build upon: normalized and connected healthcare data, payer-specific models and business context, and deep understanding of how information moves across health plan finance and operational workflows. That distinction matters. A general-purpose platform provides powerful capabilities for building AI experiences, but health plan data comes with terminology, relationships, business rules, and operational complexity specific to the payer environment. Capturing that context is what allows those capabilities to answer the questions health plan leaders have. Together, Databricks and Abacus create a path from AI-ready technology to AI-ready payer data and ultimately to answers that reflect how a health plan operates. The interesting question for payer finance is no longer whether AI can generate an answer. It's whether the answer understands enough about the business to be useful and trusted. When a CFO asks why MLR moved, the technology should do more than surface the variance. It should help finance follow that question through the underlying payer data, understand what changed, and move the organization closer to action. That requires governed data, shared business meaning, and payer-specific context underneath the interface — and that’s what Databricks and Abacus are working toward together: not simply making health plan data easier to query but making the answers more useful to the people responsible for acting on them. Check this out in action at our webinar September 17, kicking off 9AM PT. Save your seat, [here](https://events.databricks.com/FY27Q3-WB-Healthcare/registration)! Subscribe to our blog and get the latest posts delivered to your inbox.