ClaimHub
Tracks medical insurance claims against EOBs, bills, and receipts
ClaimHub keeps track of a household’s medical claims. Every explanation of benefits, provider bill, and payment receipt arrives on paper, and the question is always the same: does the bill match what the insurer said is owed, has it been paid, and is there proof. ClaimHub answers that on one Mac with no server, no cloud, and no accounts; the data stays in a local SQLite library alongside the original PDFs.
The main workflow is scan, drop, confirm. Drop a scanned PDF on the app and it stores the original unchanged, splits a multi-document scan at the page boundaries it detects (with a review screen to split or merge groups before import), and reads each document’s fields with Claude. Each document lands in an Inbox card with low-confidence fields flagged for correction. The matcher then scores it against existing claims on patient, provider, date of service, and amount: a confident hit links automatically with an Undo, a likely one asks for a tap to confirm, and anything else offers the candidates by hand. A receipt becomes a “Log this payment?” card that only writes the ledger when confirmed. The machine proposes, the user confirms.
Other things it does:
- The claim is the hub: EOBs and bills attach to it through join tables, a reconciliation strip compares what the EOBs say is owed with the bill’s balance, and signed, dated adjustments (write-offs, discounts, corrections) explain any gap with an audit trail.
- A claims register with owed, paid, and outstanding totals, a payments ledger with a receipt attachable as proof, editable payments, a notes card per claim, and three-part HSA substantiation (EOB, bill, receipt).
- Reports: outstanding total, a year-end medical and HSA summary that doubles as a substantiation packet, CSV export, and print to PDF.
- A Providers tab to confirm name aliases and merge duplicates, since the insurer names the facility and the bill names the practice.
- Encrypted backup to a single passphrase-protected file and restore into a fresh folder. The API key is kept in the macOS Keychain, and every auto-action is logged and reversible.