Overview
The problem list in an EHR is the structured record of a patient's active and resolved medical conditions, ordered for quick clinician reference. Accurate problem list management is a foundational enabler of many downstream processes: HCC coding pulls from the problem list during chart prep, quality measures reference it for denominator and numerator identification, clinical decision support triggers on items in the list, and care-coordination handoffs rely on its completeness.
Problem list hygiene has been a persistent challenge in EHR operations. Lists accumulate stale entries — resolved conditions never deactivated, conditions entered with low specificity ("diabetes" without subtype), duplicate entries (both "CHF" and "heart failure"), and outright errors (copy-paste from a consult that doesn't match the current patient). The 21st Century Cures Act and patient-access rules further elevated problem-list accuracy: patients now see their problem lists in patient-portal apps, and inaccuracies trigger complaint workflows.
Good problem-list governance involves several practices. At every primary-care encounter, the provider reviews the list and confirms, updates, or removes entries. Specialists add and update conditions in their specialty scope (cardiology adds and updates heart-failure detail; endocrinology manages diabetes subtype specificity). A periodic clean-up review — often tied to the annual wellness visit — addresses stale entries and consolidates duplicates.
Structured coding on problem-list entries matters. Lists maintained in free text cannot feed downstream HCC or quality workflows automatically. Lists maintained with coded ICD-10-CM entries feed risk-adjustment suspect engines, quality-measure abstraction, and care-management workflows without manual lookup. Best-practice EHR configuration requires a coded entry for each active problem-list item.
For HCC accuracy, problem list management is a first-order control. A prospective risk-adjustment program's suspect-condition engine typically ingests the problem list to identify conditions that should be evaluated during the upcoming visit. If the list is stale or incomplete, the suspect list misses recapture opportunities. Conversely, if the list contains entries without MEAT-supporting current-year documentation, the suspects are misleading and drive non-compliant recapture attempts.
EHR-vendor features vary in support for problem-list management. Epic's "chronic conditions" view and problem-list templates support structured management; Cerner/Oracle's problem-list workflows similarly support coded entry; smaller vendors vary. Regardless of vendor, the operational practice — reviewing and updating the list at each encounter — determines quality more than tooling.
CDI programs that invest in Problem List Management standards catch revenue leakage at the earliest possible point — before the claim leaves the practice. The highest-leverage interventions are a provider-facing Problem List Management quick-reference, embedded templates in the EHR, and quarterly audits against suspect condition and prospective risk adjustment. Reviewers flag Problem List Management patterns that repeatedly trigger coder queries as candidates for the next template revision.
Industry benchmark
Industry studies (HIMSS, AMIA) report 30–50% of EHR problem lists contain stale or inaccurate entries without active management. Practices running structured problem-list reviews report 85–95% accuracy on audited samples.
Worked example
A primary-care practice launches a problem-list cleanup initiative: providers review and update the list at every annual wellness visit and specialist MA huddles include problem-list verification. Over 12 months, aggregate accuracy rises from 62% to 91%. Downstream HCC recapture improves by 14% as the suspect engine becomes more reliable, and patient-portal problem-list complaints decline by 40%.
Frequently asked questions — Problem List Management
Who owns the problem list?
The primary-care provider typically owns the longitudinal list, with specialists contributing in their scope. Governance models vary — some systems assign PCP ownership by policy; others use shared-ownership conventions with periodic reconciliation.
Can a resolved condition stay on the list?
Typically yes as a resolved entry for historical reference, but it should be explicitly marked resolved and not coded on current-year claims or counted for risk adjustment. Structured EHR fields distinguish active vs resolved entries.
How does problem list quality affect risk adjustment?
Directly. Suspect-condition engines and prospective-review workflows pull from the list. Stale or incomplete lists produce missed recaptures; overpopulated lists produce suspect noise that fatigues providers.
Disclaimer
This glossary entry is operational reference for revenue-cycle and medical-billing professionals. It is not legal, clinical, or contractual advice. Industry benchmarks cite named public sources where available; always verify against the current guidance from the authority body before relying on a number in a contract, policy, or compliance filing.