Health IT Usability

Writing on the design of clinical software

Abstract flat drawing of a grid of empty on-screen form fields, each a pale blue outlined rectangle with a short label rule above it.
Header image 1 of 3 in the rotating pool: a grid of empty form fields.

Why clinical interfaces are hard to design

·Interfaces·

Diagram of four stacked labelled bands reading interrupted work, dense long-lived record, several roles on one screen, and the task cannot be abandoned, each drawn as a blue outlined bar.

It is common to hear that clinical software is badly designed, and less common to hear a precise account of what makes it difficult. The difficulty is not that the people who build it are careless. It is that four constraints, each individually manageable, arrive together and interact badly.

Most software is designed for someone sitting down to do one thing. Clinical software is designed for someone doing four things at once, on a record that outlives every version of the program that has ever displayed it.

Continue reading this entry → Single entries open in a full-width reading column with the sidebar dropped.

Recent entries

From the stream

Aside

Two screens can present exactly the same data and differ entirely in how long it takes to answer a question from them. That difference is the whole subject of this site, and it is almost never visible in a feature list or a specification.

Quote

The measure of a record is not how much it holds. It is how quickly the next reader finds the one thing they came for.

A working maxim for this site, not a quotation from anyone.