A source-oriented medical record (SOMR) is a method of organizing a patient’s chart by the source of the information rather than by the patient’s medical problems. Each department or provider type gets its own section: physician notes in one tab, nursing notes in another, lab results in a third, radiology reports in a fourth, and so on. It’s one of the oldest and most straightforward ways to structure a medical chart, and it’s still used in many healthcare settings today.
How a Source-Oriented Record Is Organized
In a source-oriented system, documentation is grouped by who created it or where it came from. A typical chart might have separate sections for physician progress notes, nursing assessments, laboratory results, imaging and radiology reports, pathology findings, medication records, and therapy notes. Within each section, entries are usually arranged in chronological order, with the most recent note on top.
This structure mirrors the way healthcare teams naturally produce information. A nurse documents vital signs and patient observations in the nursing section. A physician writes an assessment and plan in the physician section. A lab technician’s blood work results land in the laboratory section. Each professional knows exactly where to file their documentation and where to find notes from their own discipline. That predictability is the system’s greatest practical strength.
Where Source-Oriented Records Are Still Used
Source-oriented records tend to work best in settings where care is relatively straightforward and the care team is small. Long-term care facilities, nursing homes, walk-in clinics, and outpatient rehabilitation centers are common examples. In these environments, patients typically have stable or non-acute conditions, and fewer providers need to coordinate complex treatment plans. The simplicity of filing by source creates less friction when only a handful of people are documenting in the chart.
In contrast, hospitals with large multidisciplinary teams and patients juggling several active conditions tend to favor other documentation methods that make it easier to track each problem individually.
The Fragmentation Problem
The biggest drawback of a source-oriented record is that it scatters information about a single condition across multiple sections of the chart. If you want to understand the full picture of a patient’s diabetes management, for example, you’d need to check the physician notes for the treatment plan, the nursing section for daily blood sugar readings, the lab section for long-term glucose markers, and possibly the nutrition or pharmacy sections for diet and medication changes.
This kind of fragmentation forces clinicians to click through or flip through many different sections and mentally piece together a timeline. Research in health informatics has shown that this sequential viewing creates real cognitive burden. Providers must hold information in memory while searching for related details elsewhere in the chart. When a clinician reads a progress note and has to switch back and forth to a lab values section to cross-check current results against previous ones, it becomes a repetitive, time-consuming subtask.
That fragmentation isn’t just annoying. It can lead to suboptimal diagnostic reasoning when clinicians can’t easily see how a patient’s symptoms, test results, and treatments connect over time. It also contributes to the navigational complexity that research has linked to physician burnout in electronic health record systems.
How It Differs From Problem-Oriented Records
The main alternative to source-oriented documentation is the problem-oriented medical record (POMR), developed by Dr. Lawrence Weed in the 1960s. Before the POMR existed, progress notes addressed all of a patient’s medical issues in bulk, which made it easy to lose track of individual conditions and potentially overlook critical concerns.
The POMR flips the organizing principle. Instead of grouping notes by who wrote them, it groups them by the patient’s active medical problems. Each problem gets its own contained documentation using the SOAP format: subjective information (what the patient reports), objective data (exam findings and test results), assessment (the clinician’s interpretation), and plan (next steps). This creates what’s essentially a note within a note for every condition.
The practical difference is significant. In a source-oriented record, tracking a patient’s pneumonia means hunting through multiple tabs. In a problem-oriented record, everything related to that pneumonia, from the initial cough complaints to the chest X-ray interpretation to the antibiotic plan, lives together under one problem heading. This makes it much easier for any provider, even one seeing the patient for the first time, to quickly understand the trajectory of a specific illness.
The tradeoff is that problem-oriented records require more deliberate organization from the documenting clinician. Each note demands that the provider categorize findings by problem, which takes more effort than simply adding a chronological entry to a departmental section.
Source-Oriented Records in Electronic Systems
Modern electronic health records don’t force a strict choice between source-oriented and problem-oriented views. Most EHR platforms store data in a structured database and let clinicians view it in multiple ways. You can pull up a source-oriented view to see all lab results together, then switch to a problem-oriented view to see everything related to a specific diagnosis.
That said, the underlying challenge of fragmentation hasn’t disappeared with digitization. Even in electronic systems, important clinical information sometimes lives in forms outside the main record, in scanned faxes, staff messages, or separate modules that require additional navigation. Display fragmentation, where a user must click through many different screens to assemble a complete clinical picture, remains a well-documented problem in EHR design. The source-oriented structure contributes to this when clinicians need to synthesize information across departments.
Strengths and Limitations at a Glance
Source-oriented records have clear advantages in the right context:
- Easy to learn and use. The filing logic is intuitive, since each discipline documents in its own section.
- Quick access to discipline-specific data. If you need all the lab results or all the nursing notes, they’re in one place.
- Low documentation burden. Providers simply add entries in chronological order without needing to categorize by problem.
The limitations become more apparent as clinical complexity increases:
- Hard to track a single condition. Information about one problem is spread across every section that touched it.
- Cognitive load for complex patients. Clinicians must mentally reconstruct a patient’s story from scattered pieces.
- Risk of missed connections. When related data points aren’t grouped together, patterns can go unnoticed.
For facilities with stable patient populations and small care teams, the simplicity of source-oriented documentation often outweighs its limitations. For acute care hospitals managing patients with multiple overlapping conditions, problem-oriented or hybrid approaches typically serve clinicians and patients better.