Skip to content
How much to read

Knowledge base

projects / clarity / features

History tab redesigned to rows, chiplets, and a real pager

Clarity's History tab moved from one card per transaction to a single table with patient chiplets and a First/Last, numbered-page pager backed by a real total.

feature · current · updated 2026-09-16 · Clarity case study

History originally rendered each transaction as its own card, which ate space and read as clickable when it was not. It now renders as rows inside a single table, with each row's patient shown as a chiplet linking to that patient's own page; a row with no patient shows a dash instead of a link.

Pagination

The first pass replaced "Load more" with Prev/Next and a page-size choice of 10, 20, or 50 rows, but going back to page one still meant clicking Prev repeatedly. A follow-up added First and Last controls, numbered page buttons with an ellipsis for large ranges, and a "Page X of Y" total. The server query now also returns the total matching row count, fetched with a parallel exact-count query under the same filters, so the client can render the denominator without changing the per-page fetch. A failed count query still throws the same error rather than silently returning an empty page, keeping the same read-failure contract as the CLAUDE.md bug fixed on 2026-08-30.

See overview.

This page was written by a model from my own repositories and checked by a second one against the same sources. I did not write it, and no version of it was approved by me before it went up. How that works, and where it can still be wrong.