There’s a certain kind of work in health care that never quite fits anywhere. It’s not the structured clinical note. It’s not the templated visit. It’s everything else. The documentation that still matters, but doesn’t fit the system built to hold it.
Most documentation systems in health care are built around a simple assumption: that clinical work is structured, discrete, and tied to a defined patient encounter. That works well in many cases. It supports coding, billing, and standardized reporting. But not all documentation follows that model.
In many organizations, clinicians and administrative teams regularly deal with documentation that doesn’t fit neatly into structured workflows. This includes complex case summaries, multidisciplinary input, administrative and compliance documentation, and medical-legal reporting. This kind of work isn’t unusual. It’s part of how health care actually operates. And yet, it often doesn’t have a clear place to live.
When documentation doesn’t fit the system, it doesn’t disappear. It moves. Clinicians and teams find workarounds. They draft outside the EHR. They use separate tools for longer or more detailed narratives. They rework documentation just to make it fit required fields.
Over time, this creates a split. Some documentation lives inside the system, and some of it lives outside. That’s where the friction begins.
The impact isn’t always obvious at first. But over time, it shows up in ways clinicians and teams feel every day: duplication of effort, inconsistent documentation, lack of visibility into where information lives, and delays in getting complete, usable records. None of this is typically intentional. It’s the natural result of trying to make real-world work fit systems that weren’t designed for it.
There’s been a lot of attention on improving documentation through new technology, especially with AI tools that make it easier to capture information. But capturing information is only part of the problem. If the underlying workflow doesn’t match how documentation actually happens, new tools can end up feeding the same misalignment, just faster.
It’s easy to assume documentation challenges come down to user behavior: clinicians not following templates, or teams relying on manual processes. But in many cases, those behaviors are rational. When the system doesn’t accommodate the work, people adapt.
Not all documentation is structured. Not all of it is tied to a single encounter. And not all of it is designed for the same purpose. Some of it is narrative. Some of it spans time. Some of it supports decisions that happen outside the exam room. That’s the part no system really accounts for.
Health care has made real progress in standardizing clinical data. But there’s still a gap between how systems are designed and how documentation actually happens. Until that gap is addressed, the burden doesn’t go away.
It just moves somewhere else.
Sterling Garde is a health care executive.
