Archive

Every entry published on this site, newest first, grouped by the month it appeared. Each row carries its date and the topic it is filed under.

August 2026

4 August 2026Why clinical interfaces are hard to designInterfaces

July 2026

21 July 2026Alert fatigue and the economics of interruptionAlerts
7 July 2026Data entry, forms and the cost of a fieldInterfaces

June 2026

23 June 2026Terminology, units and numbers on screenTerminology
9 June 2026Accessibility in clinical softwareAccessibility

May 2026

26 May 2026How usability actually gets measuredMeasurement
12 May 2026From paper to screenHistory

April 2026

28 April 2026The note and its templatesInterfaces
14 April 2026Finding one number in a whole recordInterfaces

March 2026

31 March 2026Interruption and recoveryAlerts

Ephemera

AsideA field that everyone fills with the same value is not collecting data. It is collecting compliance, and it should be either removed or asked differently.

AsideHalf the arguments about screen density are really arguments about who has to scroll: the person entering, or the person reading it back six months later.

LinkThe human-factors literature on interruption, alerting and display design predates clinical software by decades. Much of what is rediscovered here was settled in aviation and process control long ago.

QuoteAn interface that cannot be resumed has not been designed for the way the work is actually done.