The problem list is supposed to be the one place in the chart where any clinician can see, at a glance, what is going on with this patient. In too many EMRs it is instead a graveyard of resolved conditions, duplicate entries with slightly different wording, and vague placeholders like "abnormal lab" that nobody has touched in three years. A neglected problem list is more than untidy. It degrades clinical decision support, corrupts quality measures, and makes every handoff riskier.
Why the problem list matters
Modern EMRs use the problem list as an input, not just a display. Decision-support rules fire based on coded problems: a diabetes entry triggers foot-exam and retinal-screening reminders, a heart-failure entry drives medication alerts. Quality-measure denominators are frequently built from problem-list codes. Care-gap reports, registries, and risk-adjustment logic all read from it. Interoperability standards include the problem list as a core data class, so whatever is on your list travels with the patient to the emergency department, the specialist, and the patient's own app. An inaccurate list therefore produces inaccurate alerts, inaccurate measures, and inaccurate information downstream.
How problem lists decay
- Nobody removes anything. Adding a problem is easy and feels safe; resolving one feels like a clinical judgment someone else should make. The list grows monotonically.
- Encounter diagnoses leak in. Some configurations add every visit diagnosis to the problem list automatically, so a single episode of bronchitis becomes a permanent chronic problem.
- Duplicates accumulate. "Type 2 diabetes," "DM2," and "Diabetes mellitus without complication" coexist because free-text and picklist entries were never reconciled.
- Imported records pile on. Outside documents and migrated charts bring their own problem entries, often uncoded, and they land alongside the local list without review.
- Specificity is lost. A problem coded at go-live as "hypertension" is never updated when the patient develops hypertensive kidney disease, so the list understates severity.
Who owns the list
Ambiguity about ownership is the root cause of most decay. The workable model in most practices is shared maintenance with a designated steward: every clinician who sees the patient may add, update, or resolve problems within their scope, and the patient's primary care clinician (or the practice's designated steward for patients without one) reviews the whole list at a defined interval. Specialists should own the problems in their domain and resolve them when appropriate rather than leaving that to primary care. Put the policy in writing, including what belongs on the list (active chronic conditions, significant past history that affects care, relevant risk factors) and what does not (self-limited acute illnesses, symptoms already explained by a diagnosis, administrative flags that belong elsewhere).
A reconciliation routine
Reconciliation works best as a scheduled task with a checklist, not an aspiration.
- At every annual or comprehensive visit, the clinician reviews the full list with the patient. Patients frequently know that a problem resolved or was misdiagnosed long before the chart does.
- Merge duplicates into the single most specific coded entry, preserving the original onset date.
- Resolve, do not delete. Resolved problems move to history with a resolution date. Deletion destroys the longitudinal record and can remove the basis for past decisions.
- Update specificity when the clinical picture changes, and confirm the associated code reflects current documentation.
- Check imported entries from outside records before accepting them, and reject entries that are uncoded, duplicative, or unsupported.
- Add a brief overview note to complex problems so the next reader understands status, current plan, and who is managing it.
A useful test after reconciliation: could a covering clinician who has never met this patient read the problem list alone and give a safe, accurate one-minute summary? If not, the list is not done.
Coding and structure
Problems should be captured as coded concepts, with SNOMED CT as the standard clinical vocabulary in certified systems and ICD-10-CM mapped for billing. Coded entries are what make decision support, quality reporting, and exchange work; free-text problems are invisible to all of it. Encourage clinicians to pick the most specific concept available and to use the display-name feature, if the EMR offers one, to keep the human-readable label clear without sacrificing the underlying code. Record onset dates where known; many measures and risk models depend on them.
EMR configuration that helps
Several configuration choices make good behavior the path of least resistance. Turn off automatic promotion of encounter diagnoses to the problem list, or restrict it to a curated set of chronic conditions. Enable duplicate detection so the system warns when a clinically equivalent concept already exists. Surface the "last reviewed" date on the list itself and build a report of patients whose list has not been reviewed in over a year. Give specialists filtered views of their own domain so they are more likely to maintain it. Finally, monitor a few metrics: average problems per patient, the percentage of uncoded entries, the percentage of lists reviewed in the past twelve months, and the number of active entries older than a threshold with no associated recent documentation. Trends in those numbers will tell you whether the policy is working long before a quality audit does.
Common questions
What belongs on an EMR problem list?
Active chronic conditions, significant past medical and surgical history that affects ongoing care, and clinically relevant risk factors. Self-limited acute illnesses, symptoms already explained by a diagnosis, and administrative flags generally do not belong, though practice policy should define the boundaries.
Should resolved problems be deleted from the list?
No. Resolve them with a date so they move to history. Deleting removes the longitudinal record and can erase the basis for prior clinical decisions. Deletion should be reserved for entries that were made in error.
Who is responsible for maintaining the problem list?
Most practices use shared maintenance with a designated steward: every treating clinician may update problems within their scope, and the primary care clinician or steward reviews the full list at a defined interval, typically at each comprehensive visit.
Why should problems be coded rather than typed as free text?
Coded problems drive clinical decision support, populate quality-measure denominators, feed registries, and travel with the patient through interoperability standards. Free-text entries are invisible to all of those functions.