Siam Kazi is a Data Reporting and Analytics Consultant on Kaiser Permanente's National Medicare Finance team, working within the Payment Adjustment Reconciliation and Reporting (PARR) function. The work is exactly what it sounds like: validating CMS payment data, supporting SOX control processes, and producing CMS/MBE reporting and risk adjustment analytics across every KP Medicare market.
In practice, that means living inside MMR files, PPR/PRS reconciliation, HCC risk adjustment, the V24/V28 model transition, and Part D payment data — the exact formats Zeebrafish AI was built to decode. This isn't a product built by outsiders trying to reverse-engineer what Medicare finance teams need. It's built by someone who was asked those questions, in that seat, this year.
Before moving into PARR, Siam spent eight years on Kaiser Permanente's Health Plan Product, Service & Administration team, leading market strategy analysis that reached Director, VP, and SVP-level stakeholders — and, on occasion, KP's most senior executive leadership. And before Kaiser Permanente, he worked as a Senior Financial Systems Analyst at The Walt Disney Company, inside Disney's Corporate Financial Systems group, supporting BI planning and reporting for Corporate, Studio, Consumer Products & Interactive, and ABC TV on SAP HANA, SAP BW, SAP BusinessObjects, and IBM Cognos TM1.
That pattern — finding the manual, high-stakes, poorly-tooled financial process and automating it — runs through the entire career. Zeebrafish AI is the same pattern applied to the biggest, least-automated manual process in Medicare finance: reading CMS's own data.
Every month, CMS sends health plans payment and membership data in file formats that predate almost everyone currently working with them — fixed-width layouts with no headers, cryptic field codes, and a 200-page technical manual as the only documentation. Understanding them is a skill, not a tool. And it's a skill that lives almost entirely in a handful of people's heads.
Working inside PARR made that gap impossible to ignore. The people who could fluently read an MOR or a PPR/PRS file were often the most senior — and closest to retirement. Junior analysts were left re-deriving field meanings by trial and error, or waiting on a colleague's availability. Consultants filled the gap at hundreds of dollars an hour, for work that, once you know the format, takes minutes.
Zeebrafish AI was built to put that expertise into software instead of letting it walk out the door with the next retirement. It's the tool Siam wished existed the first time he had to decode a flat file with nothing but a printout of the CMS record layout and a highlighter.
The mission is straightforward: no health plan finance team should be one retirement, one vacancy, or one $400/hour invoice away from being unable to read the data CMS sends them every month. Zeebrafish AI's goal is to become the standard first step in every CMS reconciliation cycle — the layer between raw government data and a finance team's actual decisions.
That starts with plain-English explanation of any CMS flat file, and extends into the Payment Integrity Engine — independently recomputing what CMS should have paid and flagging exactly where it didn't — natural-language querying over financial data, and eventually direct connections into the data warehouses (Databricks, Snowflake) health plans already run.
MARx is the CMS system that calculates what Medicare Advantage and Part D plans actually get paid — risk scores, bids, rebates, and adjustments rolled into one number per beneficiary, per month. It's the source of truth, and it's also a black box. Shadow MARx is Zeebrafish's independent, parallel recomputation of that same payment logic, built directly from CMS's own published formulas — the same kind of manual cross-check Siam runs by hand on the PARR team today, now built into software.
Live today for MMR files, tested against every CMS payment scenario. Two edge cases the engine can't fully resolve from the MMR alone are disclosed in full, by design, on our Trust & data handling page — we'd rather flag what we can't verify than guess.