Have you ever walked into a clinical documentation education session and heard a doctor say:
"So, this is about documenting for coding?"
In that moment, the conversation is already at risk of heading in the wrong direction.
Not because the clinician is unwilling to engage, but because documentation has been framed as something done for coders rather than as the mechanism through which the healthcare system understands patient complexity.
Perhaps the challenge isn't the message itself. Perhaps it's how we frame it.
Shifting the Conversation
When CDI education focuses on what coders need, clinicians can struggle to see the relevance to patient care.
Statements such as:
While technically correct, these messages can unintentionally shift the focus from accurately representing patient complexity to simply satisfying coding requirements.
A more effective approach is to help clinicians understand how their documentation shapes the healthcare system's understanding of the patients they treat.
After all, clinicians are the ones who assess, diagnose, and manage the patient's care. The healthcare system relies on their documentation to understand what occurred during the admission. Clinical coders do not determine the patient's diagnoses or clinical complexity; they translate the documented clinical story into healthcare data.
The Healthcare System Only Knows What You Tell It
Every day, clinicians care for complex patients, manage complications, coordinate multidisciplinary teams, and make difficult clinical decisions.
But the healthcare system cannot see any of that directly.
It cannot observe the patient.
It cannot interpret clinical reasoning.
It cannot infer diagnoses that were never documented.
The only thing the system sees is the documentation.
From that documentation, a range of stakeholders derive their understanding of what occurred during the admission:
Documentation is the lens through which the entire healthcare system views patient care.
If important clinical information is absent, the healthcare system cannot reliably recognise that it occurred, and that aspect of the patient's care may not be accurately represented in the resulting data.
A Different Way to Explain CDI
Instead of saying:
"The coder can't code sepsis unless you document it."
Try:
"If sepsis isn't documented, the healthcare system cannot recognise that this patient experienced sepsis during their admission, regardless of how clinically obvious it may have been to the treating team."
Instead of saying:
"We need greater specificity around heart failure."
Try:
“The type of heart failure helps communicate the complexity of the patient's condition. Without that information, the patient's clinical picture may not be fully understood beyond the bedside.”
Instead of saying:
"The coding standards require clarification."
Try:
“The healthcare system relies on your documented clinical judgement to understand what conditions affected this patient and the complexity of care that was required.”
The facts remain exactly the same.
What changes is the context.
Rather than viewing documentation as something done to satisfy coding requirements, clinicians can see how their documentation communicates clinical judgement, patient complexity, and the care provided to everyone who subsequently relies on the health record and the data derived from it.
Documentation Creates Data
Clinicians often care deeply about healthcare outcomes, service planning, patient safety, workload, and resource allocation.
What is sometimes less visible is that all of these areas rely on the data generated from clinical documentation.
Clinical documentation is the starting point. Clinical coders translate that documentation into standardised healthcare data, which is then used to understand the patients being treated, the complexity of care provided, and the resources required to deliver that care. The quality of healthcare data can never exceed the quality of the clinical documentation from which it is derived.
Hospitals use coded data to understand:
Governments use the same data to make decisions about health services and future investment.
Researchers use it to identify trends and evaluate care.
Health services use it to benchmark performance and identify opportunities for improvement.
Essentially, clinical documentation is the raw material from which healthcare data is created. Once translated into coded data, it shapes how patient complexity, healthcare activity, and clinical outcomes are understood across the health system, informing funding, quality reporting, research, workforce planning, service design, and future investment across the health system.
Moving from Compliance to Representation
When documentation education is framed as a compliance exercise, engagement can be difficult.
When it is framed as accurate representation of patient care, the conversation changes.
Most clinicians want their patients to be represented accurately.
Most clinicians want the complexity of their work to be recognised.
Most clinicians want healthcare data to reflect reality.
CDI professionals are uniquely positioned to help bridge the gap between the care delivered at the bedside and how that care is understood by the healthcare system.
The goal is not to teach clinicians how to document for coders.
The goal is to help clinicians understand that their documentation communicates clinical judgement, patient complexity, and the care provided to everyone who subsequently relies on the health record and the data derived from it.
Clinicians diagnose the conditions affecting their patients. They apply clinical reasoning, make complex decisions, and determine the patient's story.
Documentation is how that story is communicated to the healthcare system.
And the healthcare system can only see what clinicians choose to document.
Authors:
Dr Joe Vincent, Medical Projects Consultant, CDIA
Dr Sophie De'Ambrosis, Medical Doctor, CDIA