Find the cost and care patterns hidden in your claims
DecisionBox reads claims, member, clinical and prescriber data inside your own environment, and pinpoints the plan, provider or therapy driving a change, before the monthly review.
Pharmacy spend rose 4% in aggregate — DecisionBox surfaced a single therapeutic class driving most of it, concentrated in one plan segment.
Volume held flat; unit cost moved. The dashboard read total spend; the data read the class × plan segment carrying the entire shift, weeks before close.
Built for payers, providers, life sciences, and population health teams at health plans, PBMs, health systems, pharma, MedTech, ACOs, and value-based care organizations.
Aggregate metrics look fine. The cohort underneath is where the cost actually moved.
Three benchmarks every healthcare commercial and operational leader recognizes. Each points to the same gap: your data already holds the signals — cohort drift, cost concentrations, cross-system leakage — but they only surface when somebody asks the right question. Most months, nobody does.
Of healthcare leaders plan to increase agentic AI investment in the next 2-3 years. The discovery loop is where the spend lands when it lands well — not in pilots that don't touch cost, quality, or outcomes.
Source: Deloitte, 2026 Global Healthcare OutlookOf healthcare and life sciences leaders are already using or assessing AI agents. Most efforts sit in narrow pilots; the cohort-level cost and quality work is where the broader budget moves next.
Source: NVIDIA, State of AI in Healthcare and Life SciencesOf early adopters expect cost savings above 20% — vs. only 13% of watchers. The gap shows up first at the cohort level, weeks before it shows up in the executive review.
Source: Deloitte, 2026 Global Healthcare OutlookFrom a finding to a plan
Three structural shapes DecisionBox finds across payer, provider, life sciences, and population health data: a single-cohort drift the aggregate concealed, a cross-system pattern the dashboard couldn't see, and an aggregate mirage that averaged two opposing shifts into a flat line. The shapes below are representative of what the engine surfaces; specific numbers come from the customer's own data.
Pharmacy spend moved in aggregate, but DecisionBox surfaced a single therapeutic class driving most of it, concentrated in one plan segment.
- shape
- aggregate spend up; segment-level unit cost up
- dimensions cut
- therapeutic class × plan × segment
- competing causes ruled out
- utilization volume, generic mix shift
- signal precedes monthly close by
- ~2-3 weeks
Route the affected class × plan segment to pharmacy analytics for formulary review; surface the unit-cost driver in the next clinical committee; instrument segment-level spend alongside the aggregate KPI.
- target
- act on the cohort-level signal before close
- effort
- small (analytics handoff + committee surfacing)
Out-of-network referrals concentrated in two specialties for a specific payer mix. The retention dashboard couldn't see the pattern because the signal lived across three systems.
- shape
- leakage concentrated by specialty × payer mix
- systems joined
- EHR + referral system + claims
- dimensions cut
- specialty × payer × geography × PCP
- pattern type
- structural, not anecdotal
Route the affected referral pattern to network development for specialty-level contract review; instrument cross-system leakage by specialty and payer as a standing monthly report.
- target
- close the structural leakage before the next contract cycle
- effort
- medium (network development handoff + report build)
The latest formulary change showed neutral aggregate impact. The data read two opposing segment-level shifts — one absorbed it, one dropped persistence sharply.
- shape
- aggregate flat; two opposing segment moves
- systems joined
- claims + member + benefit + cost-share
- dimensions cut
- cost-share × plan type × geography × cohort
- common failure mode
- aggregate hides offsetting shifts
Treat the two segments separately in the next benefit committee; instrument segment-level persistence alongside the aggregate KPI; flag the change-impact decomposition as a standing post-implementation review.
- target
- stop averaging two populations into one signal
- effort
- small (committee surfacing + KPI add)
Same engine, different findings for every team.
Healthcare data is rarely owned by one team. DecisionBox runs against the same claims, member, clinical, and prescriber data — and tunes its discoveries to the team reading the output. Four teams, one engine, plus the cross-cutting capability that ties them together.
For health plans, PBMs, and TPAs — the medical-economics review, decomposed.
Built for actuarial, network, pharmacy, member analytics, fraud & abuse, and risk adjustment teams. DecisionBox reads claims, member, pharmacy, and network data together and surfaces the cohorts dragging the aggregate. The same engine that finds utilization spikes in a provider cohort after a network change finds pharmacy class drift in one segment, or coding gaps against the panel benchmark. The deep dive lives in how DecisionBox decides what to investigate.
- Utilization spikes concentrated in one provider cohort after a network or formulary change
- Pharmacy spend drift — therapeutic classes moving in one segment without volume change
- HCC coding gaps — provider groups under-coding vs. the panel benchmark
- FWA signal — claim patterns inconsistent with procedure-norm distributions
- Risk adjustment cohort accuracy against actuarial baseline
Built for healthcare teams who want a cohort analyst running overnight, not three dashboards to reconcile.
Three things every finding from DecisionBox carries. None of them changes how your team works in your claims system, your EHR, your data platform, or whatever data tools and BI you already standardized on.
Sees what nobody had time to look into
DecisionBox picks which cohorts, providers, segments, and measures to investigate from your claims, member, clinical, and prescriber data. Findings ship into a queue your team triages in the morning. The cohort-level question stops sitting in the data waiting for the next QBR.
Every number you'd defend at the executive review
Your team re-runs anything, extends anything, overrides anything. No black boxes, no dashboard-rolled-up numbers the data can't validate, no "trust the AI."
Reads your data, not just the claims system and the EHR
Claims plus member enrollment, EHR-derived, pharmacy, referral, contract, and quality data — read together. The patterns the claims system can't see (because it only sees adjudication) and the patterns the EHR can't see (because it only sees the encounter) surface when your data is read end-to-end. Open source, AGPL v3. DecisionBox meets you on the stack you already run.
What Healthcare & Life Sciences security teams ask first
Does our data move?
No. DecisionBox only reads it where it is, and can run inside your own environment, on-prem or air-gapped.
What can the AI see?
Only what you allow. Personal and sensitive data is hidden before the AI sees anything.
Which AI does it use?
The one your company approved, in your cloud account or on your own servers.
Can we audit it?
Every action is recorded: who, what, when and under which rule.
See DecisionBox at work
The next executive review, with the cohort shifts already mapped.
Let's run it on your data.