What is a clinical documentation barrier?
A clinical documentation barrier is something in the medical record that prevents the coder from confidently applying the correct diagnosis code or determining whether a diagnosis meets the reporting requirements for the encounter.
Examples include uncertain wording, missing specificity, conflicting statements, unclear disease status, missing authentication, or documentation that suggests a condition without the provider actually establishing it.
Documentation issues risk adjustment coders need to recognize
Uncertain diagnosis wording
Terms such as probable, suspected, rule out, questionable, compatible with, or consistent with require special attention because outpatient coding rules differ from inpatient rules.
History confused with active disease
A past condition, resolved disease, or cancer history should not automatically be coded as though it is still active.
Missing specificity
The note may name a disease but fail to document the stage, type, laterality, severity, relationship, or other detail needed for the most accurate code.
Conflicting documentation
Different sections of the note—or different providers—may describe the condition differently. Coders should not silently choose the version that produces a preferred code.
Diagnosis inferred from clinical data
Medications, labs, imaging, or symptoms may support a clinical picture, but coders should not independently diagnose a condition the provider has not established.
Authentication concerns
Missing or inadequate signatures and authentication can create problems when documentation must establish who provided or verified the care.
Probable, suspected, rule out: do not code them as confirmed outpatient diagnoses
The FY 2027 ICD-10-CM Official Guidelines say outpatient coders should not code diagnoses documented as “probable,” “suspected,” “questionable,” “rule out,” “compatible with,” “consistent with,” “working diagnosis,” or similar terms indicating uncertainty. Instead, code to the highest degree of certainty for that encounter, such as signs, symptoms, abnormal test results, or another documented reason for the visit.
The provider documents “Rule out appendicitis” for a patient with right lower quadrant pain, fever, and nausea and sends the patient for additional testing.
Coder thinking: In an outpatient encounter, do not code appendicitis as confirmed. Code the documented signs and symptoms to the highest degree of certainty, following the applicable guidelines.
This differs from certain inpatient settings, where uncertain diagnoses documented at discharge may be coded as if established under the inpatient guidelines.
History, resolved disease, remission, and active disease are not interchangeable
A frequent documentation barrier is unclear disease status. The FY 2027 outpatient guidelines instruct coders not to report conditions that were previously treated and no longer exist. History codes may be appropriate when the prior condition affects current care or treatment.
“History of right breast cancer. Treatment completed. No evidence of disease.”
Coder thinking: Do not automatically assign an active malignancy code. Code selection should reflect the documented status and the applicable ICD-10-CM guidelines.
Words such as history of, resolved, in remission, stable, recurrent, active, and status post can materially change code selection. Read the full note rather than relying on an old problem-list entry.
Signatures, authentication, and provider identity matter
Medical documentation has to be attributable to the person responsible for the care. CMS Medicare signature guidance explains that reviewers look for signed and dated documentation when signature requirements apply. CMS generally accepts handwritten and electronic signatures that authenticate the author; stamped signatures are generally not accepted except in a limited disability-related circumstance.
If a required signature is missing from certain medical documentation, CMS guidance describes when an attestation may be used. Exact requirements depend on the service, policy, record type, and audit context, so coders and auditors should follow the current rule that applies rather than rely on a single universal signature checklist.
Missing specificity and conflicting documentation
The FY 2027 guidelines direct coders to code to the highest level of specificity supported by the medical record. That does not mean selecting a more specific code simply because it exists; the documentation must support it.
Common gaps include missing CKD stage, unspecified heart-failure type, unclear diabetes complications, uncertain laterality, unclear cancer status, or a relationship between conditions that is not established under the applicable coding rules.
The assessment says “CKD stage 3b,” while another current section says “CKD stage 4.”
Coder response: Do not choose whichever stage maps to the more valuable HCC. Follow the organization's compliant clarification or query process.
A lab result is abnormal and the medication list suggests a possible chronic condition, but the provider never documents that diagnosis.
Coder response: Do not independently diagnose the condition. Use the clinical information to recognize that clarification may be needed, not as permission to create a diagnosis.
When should a coder clarify or query?
A compliant query or clarification process is appropriate when documentation is incomplete, conflicting, ambiguous, or clinically inconsistent and the missing information affects accurate code assignment. The purpose is to clarify the medical record—not to steer the provider toward a diagnosis that increases RAF or reimbursement.
A useful workflow is to review the entire encounter, identify the documented condition, compare the documentation with the ICD-10-CM Index, Tabular List, Official Guidelines, and applicable program rules, and then escalate uncertainty rather than guessing.
Read: What Is MEAT in Risk Adjustment Coding? →
Read: Supported vs. Unsupported Diagnoses →
How documentation barriers connect to RADV
In Medicare Advantage RADV audits, CMS validates whether diagnoses used for risk-adjusted payment are supported by the medical record. Current PY 2024 audit guidance emphasizes medical-record validation of submitted diagnoses and HCCs.
That makes documentation quality more than a coding convenience. A diagnosis that was submitted but cannot be validated from acceptable supporting documentation may contribute to a payment error or overpayment determination.
Clinical Documentation Barrier FAQ
Can I code “probable” diabetes in an office visit?
Not as a confirmed outpatient diagnosis. Follow the FY 2027 outpatient uncertain-diagnosis guideline and code to the highest degree of certainty documented for the encounter.
Can I use a medication to determine the diagnosis?
Do not infer a diagnosis solely from a medication. Medications can provide context, but diagnosis assignment must follow provider documentation and applicable coding rules.
Does a diagnosis have to be in the assessment and plan?
Not necessarily. Review the entire record, but the fact that a diagnosis appears somewhere in the note does not automatically make it reportable.
Should I pick the more specific code if the chart is unclear?
No. Specificity must be supported by documentation. If clinically important documentation is conflicting or incomplete, use the compliant clarification or query process.
Why do these barriers matter in risk adjustment?
Risk adjustment diagnoses can affect payment and may be reviewed through validation and audit processes. Accurate, attributable, supported documentation is essential for compliant reporting.
Go deeper than the article
Use this guide as a foundation, then build application skills through structured risk adjustment training. Choose the live CRC Boot Camp for focused review or the full self-paced CRC course for comprehensive preparation with ongoing instructor support.
Explore the CRC Boot CampView the Full CRC CourseSource note: This guide was shaped by MediCode Bootcamp's CRC curriculum on clinical documentation barriers and checked against current FY 2027 ICD-10-CM Official Guidelines, current CMS Medicare signature guidance, and current CMS RADV materials. Training examples are original and are not reproduced from proprietary course materials.
Official references: FY 2027 ICD-10-CM Official Guidelines • CMS Medicare Signature Requirements • CMS RADV Documents & Data