Why Providers Miss Chronic Conditions (and What Better Data Fixes)

Dhini Nasution
Dec 7, 2025
8 min read

Updated: Dec 8, 2025

Chronic disease is now the default, not the exception. Yet millions of patients with diabetes, hypertension, and kidney disease are either undiagnosed or poorly documented in the record, even when they are regularly touching the health system.

In the U.S., an estimated 8.7 million adults have diabetes but don’t know it—about 23% of all adults with diabetes. CDC
More than 11 million Americans are thought to have undiagnosed hypertension. Lippincott Journals
Chronic kidney disease (CKD) is often present in labs but missing from the problem list or billing codes, leading to under-treatment and lack of follow-up. NIH.PMC.NCBI

For clinicians, this is not news. What’s less discussed is why this happens and what kind of data infrastructure actually fixes it—without adding yet another inbox or alert.

This article breaks that down from a provider-operations point of view.

What does it mean to “miss” a chronic condition?

When we say conditions are “missed,” we’re usually talking about three related but distinct failures:

Undiagnosed The patient clinically meets criteria (e.g., repeated A1c ≥ 6.5%, eGFR < 60, multiple elevated BPs), but no formal diagnosis has been made. Example: A patient repeatedly has hypertensive-range blood pressures in urgent care, but “hypertension” is never added to the problem list. JAMA Network
Undocumented (or under-documented) The condition is recognized by the clinician but not consistently documented in the problem list, assessment, or claims. CKD is a classic case: one study found that about 20–25% of patients with moderate CKD had no CKD documented in the EHR; these patients were also less likely to receive guideline-recommended care. NIH.PMC.NCBI
Under-coded (or mis-coded) The condition is present in free text or labs but coded non-specifically or not at all, which undermines quality measures, risk adjustment, and care coordination. For value-based care and risk-bearing contracts, this is where missed conditions turn into revenue leakage and performance penalties.

All three ultimately come from the same root issue: our data and workflows were not designed for continuous, longitudinal detection of chronic disease.

Why providers miss chronic conditions

None of this is about individual competence. The evidence shows it’s a system problem made up of several layers.

1. Silent or subtle diseases

Many chronic conditions are asymptomatic or nonspecific early on:

Hypertension: Often no symptoms until late complications; large proportions of adults with hypertension are unaware of it. JAMA Network
Type 2 diabetes: Can progress for years with vague complaints like fatigue or blurry vision; population-level data show 8–10% of the diabetes burden may be undiagnosed even in high-income countries. NIH.PMC.NCBI
CKD: Frequently discovered only through routine labs; even then, staging and documentation are often missed or incorrect. CMS

In busy primary care or SNF settings, it is easy for these “quiet” conditions to remain in the background.

2. Fragmented and noisy data

Clinicians rarely see a single, clean longitudinal story:

Labs in one system, hospital notes in another, outside consults scanned as PDFs, and claims data invisible at the point of care.
Important patterns (e.g., three elevated BPs across three sites, or progressive eGFR decline over 18 months) are statistical signals spread across multiple visits and settings, not obvious in a single encounter.

Research on diagnostic error repeatedly highlights information availability and integration as major contributors: critical results not seen, not communicated, or not synthesized in time. NIH.PMC.NCBI

3. Cognitive overload and time pressure

Primary care and LTC clinicians manage:

15–20 minute visits, often with multiple complaints
Complex medication lists and social issues
Performance pressures around access, throughput, and documentation

Studies of diagnostic error in primary care show that task overload, competing demands, and cognitive biases (anchoring, premature closure) are common drivers of missed or delayed diagnosis, even for common conditions like CHF, pneumonia, or renal failure. NIH.PMC.NCBI.American Academy of Family Physicians

When the visit is dominated by acute issues, chronic risk signals in the chart become background noise, not actionable insights.

4. EHR problem lists and coding gaps

Even when conditions are recognized, they’re often not reliably represented in the data:

One CKD study found that low recognition in the EHR problem list was associated with lower use of CKD-specific processes of care (e.g., ACEi/ARB prescriptions, urine protein measurement). NIH.PMC.NCBI
CMS has highlighted mis-recognition of CKD stage among primary care providers; in one test case, stage 4 CKD was correctly recognized only ~63% of the time. CMS

In value-based models, this translates into:

Inaccurate risk scores (HCC / RAF)
Misaligned panel acuity
Under-resourced care management for those who are actually high risk

If the EHR can’t “see” the condition, none of the downstream systems can either—quality, risk, CCM, or population health.

Why missed chronic conditions matter

1. Clinical outcomes

Undiagnosed or under-documented conditions mean:

Delayed treatment (e.g., no statin or ACEi/ARB where indicated)
Faster progression to complications (ESRD, MI, stroke, heart failure)
More emergency visits and unplanned admissions

Evidence around CKD is particularly stark: early recognition and interventions can significantly delay progression, yet under-recognition is common. CMS

2. Quality and value-based performance

For organizations in risk-bearing arrangements:

Conditions that are not captured, coded, and revisited annually may not be reflected in RAF or other risk models.
Quality measures (HEDIS, Stars) often depend on having both a diagnosis and appropriate follow-up documented in the measurement year.

The result: sick populations that look “average” on paper—and contracts priced or evaluated as if that were true.

3. Operational burden

Ironically, poor data quality creates more work:

Manual chart reviews to “hunt” for conditions ahead of audits or submissions
Back-and-forth between coders, clinicians, and care managers
Fire drills at the end of the year to close gaps that could have been surfaced earlier

Fixing chronic-condition visibility is therefore not just a clinical or financial issue; it’s a workflow and burnout issue.

What “better data” actually looks like

Better data is not just “more fields” or “more alerts.” For providers, better data means the right clinical story, at the right time, in the right workflow.

1. Longitudinal, integrated patient timelines

Instead of each visit being a separate island, high-functioning systems create:

A single longitudinal view aggregating vitals, labs, medications, problem list, consults, and claims.
Simple, clinically meaningful signals:
“3+ hypertensive readings in last 12 months without a hypertension diagnosis”
“eGFR < 60 for ≥ 3 months without CKD staging”
“Multiple oral steroids + wheeze + rescue inhaler use, no COPD/asthma diagnosis”

This is exactly what many national disease management programs do at scale—using integrated data to systematically detect high-risk or undiagnosed patients. JMIR Medical Informatics

2. Computable phenotypes and registries

A computable phenotype is a machine-readable definition of a disease using structured data: lab thresholds, diagnosis codes, medications, time windows, etc. Examples:

CKD phenotype defined by repeated eGFR and albuminuria values rather than codes alone. Nature
Diabetes phenotype defined by A1c, fasting glucose, and anti-diabetic medication use, not just ICD-10.

When you define these phenotypes and run them routinely across your data:

You build live registries (e.g., CKD, diabetes, heart failure) that don’t depend solely on billing codes.
You can compare coded vs. phenotype-positive cohorts to find patients who are “hiding in plain sight.”

3. Clinical decision support that respects workflow

The literature is clear: clinical decision support (CDS) can improve chronic disease care when it’s integrated thoughtfully into the EHR. NIH.PMC.NCBI

Effective CDS for chronic conditions typically:

Surfaces fewer, higher-yield signals (e.g., “suspected CKD based on labs”) rather than a flood of alerts.
Shows concise context: key labs, prior diagnoses, meds, and relevant guidelines.
Supports one-click actions:
Add/update diagnosis
Order confirmatory testing
Refer to nephrology/endocrinology
Enroll in CCM/TCM program

In other words, it turns data into decisions and decisions into orders, without forcing clinicians into a separate tool.

4. Closing the loop: from alerts to accountability

Better data systems also track:

Whether the suggested action was accepted, modified, or dismissed, and why.
Which conditions are consistently being overlooked, and in which clinics or subpopulations.
Trends over time in undiagnosed vs. diagnosed and documented vs. phenotype-positive patients.

This “CDS exhaust data” can be analyzed to identify knowledge gaps, workflow bottlenecks, and training needs, not just individual errors. Wolters Kluwer

A practical roadmap for provider organizations

You don’t need a greenfield tech stack to start fixing missed chronic conditions. Here’s a pragmatic sequence many organizations follow.

Step 1: Define your top 5 conditions and phenotypes

Start with conditions that:

Drive the most cost and risk (e.g., diabetes, hypertension, CKD, heart failure, COPD).
Are common sources of underdocumentation and quality gaps.

For each condition, define:

The ICD-10 basis (what counts as “documented”).
The phenotype basis (labs, vitals, meds, timelines).
What “good management” looks like: key labs, meds, follow-up intervals.

Step 2: Build “hiding in plain sight” lists

Using your existing EHR + data warehouse (or a partner):

Identify patients who meet the phenotype but lack a diagnosis code.
Identify patients with a diagnosis but missing key elements of care (e.g., no A1c in 12 months, no ACEi/ARB in albuminuric CKD).

Prioritize:

High-risk segments (older adults, multiple comorbidities).
Value-based contract panels (ACO, Medicare Advantage, SNF/LTC aligned populations).

Step 3: Deliver insights into native workflows

Avoid standalone dashboards that nobody checks. Instead:

Surface suspected conditions inside the EHR workflow (in-basket, chart banner, problem list assistant, or care management queue).
Give clinicians short, traceable evidence: “eGFR 52, 49, 47 over 13 months; UACR 45 mg/g.”
Offer pre-built order sets and documentation shortcuts so that acting on the signal takes seconds, not minutes.

Step 4: Engage care managers and pharmacists

Not every gap needs to be solved in a 15-minute visit:

Create care management worklists for outreach: BP recheck visits, lab follow-ups, high-risk medication reviews.
Allow non-physician team members (RNs, pharmacists, NPs, social workers) to advance the workup and education between physician visits. AHA Journals

This team-based model is essential for closing chronic care gaps at scale.

Step 5: Measure and iterate

Track:

Reduction in phenotype-positive but uncoded patients per condition.
Improvements in time to diagnosis, and in adherence to key care processes (labs, meds, follow-ups).
Impact on utilization and contract performance, recognizing that clinical outcomes may lag.

Use these data to refine phenotypes, CDS rules, workflows, and training.

Where AI fits—and where it doesn’t

AI and advanced analytics can accelerate this entire process, but they are not magic.

Useful applications include:

NLP on free text to surface unstructured evidence of chronic conditions that never made it into discrete codes. NIH.PMC.NCBI
Risk models that prioritize which phenotype-positive patients are most likely to benefit from outreach.
Automated evidence summaries that explain to clinicians why a condition is being flagged, in a way that is auditable and clinically transparent.

However:

AI models must be trained on representative, high-quality data and regularly validated to avoid bias.
The real value is not just predicting “who is sick,” but making it easy for teams to do the right thing once those patients are identified.

Takeaway: Missing conditions are a data and workflow problem, not a character flaw

Providers are not “missing” chronic disease because they don’t care or don’t know. They’re doing the best they can in a system where:

The signals are diffuse and spread across time and systems.
The tools are often built for billing, not for longitudinal reasoning.
The workload and cognitive load are already beyond reasonable.

The good news: this is fixable. With better data integration, computable phenotypes, thoughtful CDS, and team-based workflows, organizations can:

Find the patients who are “hiding in plain sight.”
Treat conditions earlier and more consistently.
Align documentation, risk, and resources with the true burden of disease in their population.

If you’re designing your provider strategy around chronic disease management, the most important question is no longer “Do we have data?” but “Can our system recognize and act on the chronic disease signals we already have?”

That’s the gap worth closing.

References

Centers for Disease Control and Prevention. National Diabetes Statistics Report. CDC
Million Hearts / HHS. Undiagnosed Hypertension – Patients Hiding in Plain Sight. Lippincott Journals
Jolly SE, et al. “CKD in an Electronic Health Record Problem List.” Clin J Am Soc Nephrol. NIH.PMC.NCBI
CMS. Chronic Kidney Disease Often Undiagnosed in Medicare Beneficiaries. CMS
Singh H, et al. “Types and Origins of Diagnostic Errors in Primary Care Settings.” JAMA Intern Med. JAMA Network
Patterson BW, et al. “Scope and Impact of EHR-Integrated Clinical Decision Support.” J Am Med Inform Assoc. NIH.PMC.NCBI
Wang SH, et al. “Role of Health IT in Enhancing Chronic Disease Management.” NIH.PMC.NCBI
Shang N, et al. “Medical Records–Based CKD Phenotype for Early Disease Recognition.” Nature