One view of every member, across three health plans
Value-based care runs on knowing every member's story. It should fit on one screen.
- Service
- Value-based care finance
- Status
- in production
- Built
- April 2026 (first prototype February 2026)
103
releases since July 2026, each tested on a staging site first
Source: Commit history, Oct 2026
330,000+
claim lines in one plan's monthly file
Source: Commit history and notes, Jul–Aug 2026
13,837 / 2,491
new and restated claim lines found in one plan's July file, matching an independent check exactly
Source: Commit history and notes, Jul–Aug 2026
The problem
Each health plan sends monthly files in its own layout: spreadsheets, text files, comma-separated files. The value-based-care surplus and deficit lived in a workbook with one sheet per plan. Leadership's monthly risk-score workbook was another file. Answering "what is going on with this member?" meant opening all of them.
What was built
Importers read each plan's files into one structure: members, medical claims and, where the plan sends them, pharmacy claims, with previews, duplicate handling and record counts. One page per member brings together claims and spending flags, hospital and ER use, risk, value-based balance, plan risk scores, coding gaps and upcoming visits, with a one-page printable summary.
Because each plan resends months of history every month, every upload is compared with what is already stored. New and restated claim lines are logged, lines the plan dropped are retired, and a timeline shows exactly what each file added. Snapshots let the data be restored to how it was before any of the last three uploads.
What was hard
Order of operations. Before the dashboard held any real patient data, it was built and tested on de-identified data, with every identifying detail replaced by consistent stand-ins. The security controls came next, then a penetration test and leadership's review. Only then did real data go in.
The files are big: one plan's monthly file runs past 330,000 claim lines, so uploads had to survive database time limits and the browser's limits on large files. And an early "delete this upload" button turned out to rely on a marker that one re-upload proved unreliable; it was withdrawn and replaced with restore-to-before snapshots, which need no guessing.
Result
One place to see every member of the three plans. 103 releases since July 2026, each previewed on a staging site and shipped through a tracked change request. On one plan's July file, the comparison logged 13,837 new and 2,491 restated claim lines, matching an independent reconstruction exactly.
Not measured: minutes to answer a leadership question about a member, before and after. It is the figure that would matter most, and it isn't claimed.
Where the numbers come from
The commit history and build notes from April to October 2026.