What makes a diagnosis supported?
A supported diagnosis is one that is documented in a way that meets the coding and reporting requirements that apply to the encounter. In risk adjustment, the coder should be able to connect the diagnosis to the current medical record and explain why it is appropriate to report.
Support may include the provider naming the condition, describing its current status, discussing related symptoms or complications, reviewing relevant test results, monitoring the condition, continuing or changing treatment, or including the condition in the assessment and plan.
Do not limit your review to one section of the note. Relevant diagnosis documentation may appear in the history, exam, assessment, plan, medication discussion, test review, or follow-up instructions. The entire encounter should be considered, while still applying the rules that determine which conditions are reportable.
What makes a diagnosis unsupported?
An unsupported diagnosis is one that does not have enough current documentation to justify reporting it under the applicable coding and risk adjustment rules.
Common warning signs include an old diagnosis carried forward with no current discussion, a condition appearing only on a problem list, a coder inferring a disease from a medication or test result, a historical condition being treated as active, or documentation that is too vague to support the level of specificity selected.
Supported thinking
Read the full encounter, identify what the provider documented, verify the diagnosis code, and confirm the condition meets the applicable reporting rules.
Unsupported thinking
Start with an HCC list, search the chart for anything that looks similar, and code the condition because it could affect the risk score.
How should a coder decide whether to report a diagnosis?
| Step | Question to ask |
|---|---|
| 1. Identify the diagnosis | Did an appropriate provider document the condition in the current encounter or in documentation that is valid for the coding context? |
| 2. Review the whole note | What does the history, exam, assessment, plan, medication discussion, testing, and follow-up tell you about the condition? A diagnosis is not restricted to appearing only in the assessment and plan, but its location alone does not make it reportable. |
| 3. Look for current support | Is the condition monitored, evaluated, assessed/addressed, treated, or otherwise clearly incorporated into the patient's current care or management? |
| 4. Verify the ICD-10-CM code | Does the selected code match the provider's documentation and the required level of specificity? |
| 5. Apply official rules | Do ICD-10-CM guidelines, setting rules, payer requirements, or the applicable risk adjustment program affect whether or how the diagnosis is reported? In outpatient coding, report coexisting conditions when they require or affect patient care, treatment, or management; do not automatically report every condition merely because it appears somewhere in the chart. |
| 6. Escalate uncertainty | If the documentation is unclear or conflicting, should the case be queried or escalated under your organization's policy rather than guessed? |
Is a diagnosis supported if it is on the problem list?
Not automatically. Problem lists are useful, but they can contain conditions that are old, resolved, duplicated, nonspecific, or not addressed during the current encounter.
The coder should review the current documentation to determine whether the condition is active and reportable. A problem-list entry may be part of the evidence, but it should not replace the rest of the chart-review process. Conversely, a supported diagnosis does not have to appear only in the assessment and plan; the coder may need to use the entire note to understand the patient's current clinical picture.
The chart lists “CHF” in the problem list, but the visit note contains no current assessment, symptoms, monitoring, treatment discussion, or plan related to heart failure.
Coder response: Do not assume the condition is reportable solely because it appears on the list. Review the entire record and applicable rules.
The assessment states “Chronic systolic heart failure—stable,” the provider reviews daily weights and edema, and continues the current diuretic regimen.
Coder response: The current note contains clear evidence that the condition was assessed and managed. Verify the appropriate ICD-10-CM code and applicable reporting rules.
Can a medication or lab result prove the diagnosis?
A medication can support the clinical picture, but a coder generally should not infer a diagnosis solely from a medication. Many drugs are used for more than one condition, and the provider still needs to document the diagnosis when required by the coding rules.
The same principle applies to lab and imaging results. An abnormal value may support a provider-documented diagnosis, but coders should not automatically convert a test result into a diagnosis the provider did not make.
The medication list includes metformin, but the provider does not document diabetes anywhere in the encounter.
Coder response: Do not assume diabetes solely from the medication. Review the record and follow applicable coding rules.
An A1c result is elevated, but the provider does not diagnose diabetes.
Coder response: Do not independently diagnose the patient. Coding is based on provider documentation and applicable coding rules.
Why “history of” and current disease are not interchangeable
One of the most important chart-review skills is distinguishing an active condition from a past condition. A resolved cancer, prior stroke, healed ulcer, or previously treated infection may need a history or status code rather than an active-disease code, depending on the documentation and coding guidelines.
Never assume that a diagnosis coded in a previous year is still active this year. Current reporting must be based on current documentation and the rules that apply. Likewise, a condition documented as resolved should not be reported as though it remains active simply because it is still visible elsewhere in the record.
Does MEAT determine whether a diagnosis is supported?
MEAT—Monitor, Evaluate, Assess/Address, Treat—is a useful teaching framework for spotting evidence that a condition was actively addressed. It can help coders think more critically about the record.
But MEAT should not become a rigid yes/no formula. One MEAT element does not automatically make a diagnosis reportable, and the absence of an obvious MEAT word does not automatically make a diagnosis invalid.
The full documentation and official rules still control.
Supported or unsupported? Work through these examples
Assessment: “Type 2 diabetes with hyperglycemia. A1c 8.4. Increase basal insulin to 24 units nightly.”
Why it is supported: The diagnosis is documented, the current status is evaluated, and treatment is adjusted. The coder would still verify the correct ICD-10-CM code and apply any relevant coding guidelines.
Assessment: “CKD stage 3b, stable. Creatinine reviewed. Continue nephrology follow-up and avoid NSAIDs.”
Why it is supported: The condition is documented with specificity, current status, review of relevant data, and a management plan.
“COPD” appears on the problem list. The current visit is for a sprained ankle, and there is no mention of COPD elsewhere in the note.
Why it needs caution: The current encounter does not clearly show that COPD was addressed. Do not report it automatically without confirming the applicable rules and documentation.
The patient takes levothyroxine, but the provider does not document hypothyroidism in the current record.
Why it needs caution: Medication use alone is not a substitute for provider documentation of the diagnosis.
The note states “History of breast cancer, completed treatment, no evidence of disease.”
Why it matters: The documentation describes a history, not necessarily active malignancy. Code selection should reflect the documented status and applicable ICD-10-CM guidance.
Supported Diagnosis FAQ
Can a diagnosis be supported without medication?
Yes. Treatment is only one type of support. A condition may be monitored, evaluated, assessed, addressed, or otherwise documented in a way that supports reporting under the applicable rules.
Does “stable” count as support?
It can be meaningful when the provider is clearly assessing the condition and documenting its current status. The coder should still evaluate the complete note and applicable reporting rules.
If the patient has had the disease for years, can I code it every year?
Do not assume so. Risk adjustment reporting is based on current documentation and the rules for the applicable program and reporting period.
Can coders use clinical indicators to diagnose a condition?
Coders should not independently diagnose patients. Clinical indicators can help evaluate documentation, but diagnosis assignment must follow provider documentation and applicable coding rules.
What should I do when the documentation is unclear?
Follow your organization's compliant query, clarification, or escalation process instead of guessing or selecting a diagnosis based on its risk value. A compliant query should clarify the clinical record rather than steer the provider toward a particular diagnosis.
Read next: Clinical Documentation Barriers in Risk Adjustment →
Practice deciding what the documentation supports
Use MediCode Bootcamp’s free CRC study resources and case-based training to practice the same decisions risk adjustment coders make during chart review.
Free CRC Study SessionsReview MEATExplore CRC TrainingEducational note: Coding and risk adjustment requirements vary by setting, payer, program, and model. Always use current ICD-10-CM guidelines, official program requirements, payer policies, and organizational procedures. This guide also reflects MediCode Bootcamp's CRC curriculum emphasis on reviewing the entire note, reporting the complete supported clinical picture, distinguishing active from resolved conditions, and querying the provider instead of assuming when documentation is unclear.