Coming Soon! “What Wasn’t Written”

Not every call is documented the way it actually happened. A report is completed, submitted, and archived, and on paper the call is finished. The timeline is clear, the interventions are recorded, and the outcome is defined within the limits of documentation. It creates a version of events that is structured, defensible, and necessary.

But it is not complete.

There are always elements that do not make it into the chart. These are not errors or omissions in the traditional sense—they are the parts of the call that do not translate into checkboxes or narrative fields. A hesitation before a decision, a subtle shift in tone, a moment that felt unresolved but could not be articulated. These details exist alongside the documented version, but remain outside of it.

What Wasn’t Written exists in that space.

This is not a book about dramatic calls or clinical breakdowns. It does not attempt to classify outcomes as right or wrong, nor does it frame experiences in terms of success or failure. Instead, it examines what remains after the call is cleared—the impressions, the questions, and the details that persist despite their absence from the official record. These are the aspects of the job that are often recognized but rarely addressed.

In EMS, documentation is designed to capture measurable information: vital signs, treatments, timelines, and observable findings. It functions as both a legal record and a clinical summary. However, the practice itself extends beyond what can be formally recorded. There is a parallel layer of experience that develops through repetition, pattern recognition, and exposure to patients in uncontrolled environments. That layer influences clinical judgment, perception, and future decision-making, yet it is largely undocumented.

What remains after documentation is often intangible, but not insignificant. Certain calls linger without an obvious reason. A detail may resurface later, prompting reconsideration or doubt. A brief interaction may carry weight that cannot be justified within the structure of a report. These experiences do not disrupt the workflow in the moment, but they accumulate over time, shaping how providers interpret and respond to subsequent situations.

This book examines those moments without attempting to resolve them. It does not offer closure, correction, or reassurance. It presents them as they are—unresolved, sometimes uncomfortable, and often overlooked. The goal is not to define them, but to acknowledge their presence within the work.

What Wasn’t Written is intended for those who recognize that documentation represents only one version of a call. It is for the providers who understand that there is always a second version—less structured, less certain, but no less influential. That version does not get submitted or reviewed, but it is carried forward nonetheless.

Because what is written is only the official account.
The rest is what stays with you.

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *