clabsi-risk-radar

A case had to be made, in numbers, for moving central line audits off paper.

CLABSI Risk Radar is an argument in the shape of a dashboard. The code has two real screens: a dashboard that puts a manual audit flow beside a digital one, and a long-form magazine article called Predict, Prevent, Protect that carries the methodology and results. The financial component estimates the cost of a single infection at twenty-five to forty-five thousand dollars and works forward from there. Every number in it is a hardcoded constant inside the components — surveyData, complianceData — because this was written to persuade, not to collect. Recognising that changed how I labelled it: this is a research presentation, and treating it as a live monitoring tool would be a misreading of my own build.

• Me: "Show manual against digital, side by side." → Two workflow diagrams on one screen, so the difference is visible rather than argued.
• Me: "Put the money in it." → A cost model built on published per-infection costs.
• Me: "Should this collect data too?" → Not in this build. It presents a case; it does not run the ward.

My own labelling. I had been describing it as a dashboard when the code is a persuasion piece with no persistence behind it.

Know which artefact you are making. A convincing static case is a legitimate output — as long as you never claim it is live.

• The clabsi-risk-radar Story

  From manual audits to digital excellence

  Ebook · $9.00

  Read it