Skip to main content
v2026.11,986 entries · CC-BY 4.0

Problem-Oriented Medical Record (POMR) and Problem-Based Charting

How Lawrence Weed’s 1968 Problem-Oriented Medical Record (POMR) established the problem list and SOAP note, and how modern EHR Problem-Based Charting works.

Written and maintained by CASRAI Editorial Board

Published

On this page

The Problem-Oriented Medical Record (POMR) is the foundational architecture for organizing longitudinal clinical documentation around a patient’s numbered list of active and resolved health problems rather than the hospital department or clinician type that generated the data. Introduced by physician-informatician Dr. Lawrence L. Weed in his landmark 1968 New England Journal of Medicine article, “Medical Records That Guide and Teach,” the POMR transformed clinical charting from unstructured, chronological prose into a scientific, auditable structure—giving rise to both the dynamic EHR problem list and the SOAP note.

How Did Lawrence Weed’s 1968 POMR Replace Source-Oriented Medical Records?

Prior to Weed’s 1968 framework, hospital charts were organized as Source-Oriented Medical Records (SOMR): physician progress notes were filed chronologically in one section, nursing notes in another, laboratory slips in a third, and radiology reports in a fourth. In patients with multiple chronic comorbidities, reconstructing why a medication was started or how a specific complication evolved required reading through dozens of unindexed pages across separate sections.

To make clinical reasoning transparent and scientific, Weed partitioned the Problem-Oriented Medical Record into four mandatory phases:

POMR Phase Original 1968 Definition (Weed) Modern EHR & HL7 FHIR Equivalent
1. Defined Database Comprehensive baseline intake comprising chief complaint, patient profile, past medical/surgical history, review of systems, physical exam, and baseline laboratory panel. Structured intake history, vital signs, baseline FHIR Observation panels, and social/family history tables.
2. Complete Problem List A dynamic, numbered “table of contents” placed at the very front of the chart listing every active and inactive/resolved problem at the highest level of diagnostic certainty supported by the evidence. Longitudinal EHR Problem List persisted as FHIR Condition resources (`category = problem-list-item`) coded in SNOMED CT and ICD-10-CM.
3. Initial Plans Numbered and titled to correspond to each problem on the Problem List, subdivided into three explicit buckets: Diagnostic (rule-outs/labs), Therapeutic (medications/procedures), and Patient Education. Problem-linked clinical order sets, FHIR CarePlan instances, and structured Assessment and Plan (A&P) templates.
4. Numbered Progress Notes Follow-up narrative notes (structured as Subjective, Objective, Assessment, Plan — SOAP), flow sheets, and discharge summaries strictly indexed by Problem Number and Title. Problem-Based Charting (PBC) progress notes, APSO notes, and longitudinal clinical flow sheets.

Diagnostic Precision Rule on the Problem List

A core rule of Weed’s POMR is that a problem on the Problem List must be stated at its highest verified level of scientific synthesis—whether that is a confirmed etiological diagnosis (e.g., #1 Pulmonary tuberculosis), a physiological syndrome (e.g., #2 Congestive heart failure), an isolated symptom or physical finding (e.g., #3 Hemoptysis), an abnormal laboratory result (e.g., #4 Hypercalcemia), or a social determinant of health. As diagnostic workup progresses, the problem entry is updated in place (for example, updating #3 Hemoptysis → Squamous cell carcinoma of right upper lobe) so the chart’s table of contents never fragments a single pathophysiological process into disconnected symptom rows.

How Does Problem-Based Charting (PBC) Reduce Cognitive Load in Modern EHRs?

When early electronic health records digitized paper SOAP notes without linking the note body to the structured EHR Problem List, clinicians resorted to copy-pasting entire multi-problem Assessment and Plan sections from one encounter note to the next—causing “note bloat” and propagating outdated clinical statements. Modern enterprise EHRs (such as Epic Problem-Oriented Charting and Cerner Dynamic Documentation) implement Problem-Based Charting (PBC) to restore Weed’s architecture:

  • Persistent Overview vs. Encounter-Specific Assessment & Plan: For each active problem on the Problem List, PBC maintains two distinct text fields: a persistent Overview (summarizing baseline history, e.g., date of initial diagnosis, prior echocardiogram EF, or drug intolerances) and a visit-specific Assessment & Plan written for today’s encounter. Clinicians no longer copy-paste historical prose into today’s note just to preserve context.
  • Automatic Order and Medication Linking: When a clinician places laboratory requisitions, imaging orders, or medication prescriptions during an encounter and associates them with Problem #1 (`Type 2 diabetes mellitus`) or Problem #2 (`Essential hypertension`), the EHR automatically populates those orders under the corresponding problem heading in the SOAP Note Plan section.
  • Longitudinal Problem Timeline Inspection: Clicking any problem in the EHR Problem List displays a filtered chronological view of every prior Assessment & Plan entry, medication change, and diagnostic result tied to that single problem across years of care.

How Does POMR Relate to APSO Notes and the HL7 FHIR Condition Architecture?

In inpatient wards and complex specialty clinics where the Defined Database and automated lab flowsheets are already visible in structured EHR tabs, scrolling through pages of copied Subjective and Objective data to reach the Problem-Based Assessment and Plan slows chart review. Consequently, many health systems pair POMR with the APSO note format (Assessment, Plan, Subjective, Objective), placing the numbered Problem-Based Assessment and Plan at the very top of the note.

At the interoperability layer, HL7 FHIR R4 and US Core represent the POMR Problem List using the Condition resource:

  • Condition.category: Distinguishes a longitudinal POMR entry (problem-list-item) from a single-visit billing or triage diagnosis (encounter-diagnosis) or a nursing/social health concern (health-concern).
  • Condition.clinicalStatus and verificationStatus: Tracks whether a problem is active, recurrence, relapse, inactive, remission, or resolved, alongside diagnostic certainty (unconfirmed, provisional, differential, confirmed, refuted).
  • Problem-Linked Clinical Reasoning: Other FHIR resources link back to the problem entry via explicit reference elements—such as MedicationRequest.reasonReference, ServiceRequest.reasonReference, Procedure.reasonReference, and CarePlan.addresses—encoding Weed’s problem-to-plan linkage in computable graph edges.

Frequently Asked Questions

When should a hospitalist use Problem-Based vs. System-Based Assessment and Plan charting?

For general medical floors and outpatient clinics, Problem-Based A&P (organizing the note by numbered problems ranked in order of clinical acuity) is standard. In intensive care units (ICUs) managing critically ill patients with multi-organ failure, clinicians often use a System-Based A&P (Neurologic, Cardiovascular, Pulmonary, Renal/Fluids/Electrolytes, Gastrointestinal/Nutrition, Infectious Disease, Hematology, Prophylaxis) to ensure no physiological organ system or ICU bundle item is overlooked, while nesting active problems beneath each organ system.

What is problem list clutter and how do health systems govern problem list hygiene?

Problem list clutter occurs when self-limited acute encounters (such as an upper respiratory infection or ankle sprain from five years ago), duplicate SNOMED CT synonyms, and unmerged symptom codes remain marked `active` indefinitely. Health systems govern problem list hygiene by configuring acute-condition auto-expiration prompts, assigning primary care ownership of chronic problem reconciliation, and training AI medical charting assistants to suggest consolidating redundant symptom entries into confirmed diagnoses.

Why did Lawrence Weed oppose unindexed free-text clinical notes?

Weed argued that a physician’s progress note written without an explicit Problem Number acts like a laboratory reporting a chemical value without labeling which test or patient it belongs to: without problem-level indexing, neither human peers nor computer auditing systems can evaluate whether the diagnostic and therapeutic plan logically followed from the patient’s longitudinal data.

Follow CASRAI

Research-administration guidance, standards updates and independent tool reviews.

Ask CASRAI · free to try

Ask about Problem-Oriented Medical Record (POMR) and Problem-Based Charting

2 free questions a day, no account.

An AI assistant for research: funder rules, compliance, methods and publishing. It links the sources behind its answers and labels answers that come from a web search.

Answers draw on CASRAI's guides and dictionary plus the federal and funder documents we index: Federal Register, Grants.gov, Regulations.gov and UKRI.

Works on this site and inside Claude, Cursor and the AI tools you already use.

Everything CASRAI publishes — this page, the dictionary, the guides and the news — stays open to read, with no account and no card.

Referenced across the research world

University of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logoUniversity of Cambridge logoColumbia University logoCrossref logoUniversity of Edinburgh logoHarvard University logoUniversity of Oxford logoPrinceton University logoStanford School of Medicine logoUniversity College London logoORCID logo
  • University of Cambridge logo
  • Columbia University logo
  • Crossref logo
  • University of Edinburgh logo
  • Harvard University logo
  • University of Oxford logo
  • Princeton University logo
  • Stanford School of Medicine logo
  • University College London logo
  • ORCID logo

View CASRAI adoption →