caregap-analyzer

Joint Commission findings arrived as a stack of standard codes and department scores that nobody could hold in their head at once.

CareGap Analyzer began as a single screen: every TJC standard on one page, with its score per department. The code shows the whole product is one route — no login, no database, no upload. All of the audit content lives in a typed file called tjc-data.ts, where each finding carries a standard code, a description, a score map per department and the detailed written findings. Recharts turns those numbers into a bar chart and a heatmap; Embla puts the written findings into a carousel so a long inspection report can be walked through instead of scrolled. Choosing static data was not laziness. It let me see whether the shape of the information was right before deciding it deserved a backend.

• Me: "Show every standard against every department." → A heatmap, because a table of that size stops being readable.
• Me: "The written findings are the important part." → They went into a carousel instead of being buried under the charts.
• Me: "Where does the data come from?" → From a file I edit by hand. That is the honest answer, and it is also the current limitation.

Nothing crashed. What failed was the assumption that this could stay useful without history: the app shows one snapshot, so it can prove where you stand today but not whether you are improving.

A dashboard is a shape before it is a system. Get the shape right with a typed file of real numbers, and only then argue about a database.

• The caregap-analyzer Story

  Where the standards fall short

  Ebook · $9.00

  Read it