The “Who Said It?” Problem: Why a Narrative Summary Should Separate Patient Reports from Provider Findings

A medical record can sound certain when it is not.

That is the problem.

One line says the patient had severe pain. Another says the provider observed reduced range of motion. Another lists a diagnosis in the assessment. Another carries an old condition forward in the problem list. Another bill shows a service date, but no treatment note sits beside it.

All of those details may belong in the case file.

But they do not mean the same thing.

In legal and medical-legal review, a narrative summary should not blur patient-reported history, provider findings, diagnostic results, treatment plans, and billing entries into one smooth story. The summary should help the reader understand who said what, when it was documented, and what type of record supports it.

That distinction can change how attorneys, claims professionals, experts, and reviewers understand the case.

Why “Who Said It?” Matters

Medical records are not written in one voice.

They include the patient’s words, the provider’s exam findings, nurse notes, therapist observations, imaging interpretations, medication lists, billing codes, intake forms, discharge instructions, and carried-forward history.

A weak summary may combine all of that into clean prose.

That may read well, but it can create risk.

For example, “the patient had weakness” is not as clear as “the patient reported weakness” or “provider documented reduced strength on exam.” The difference may look small, but it matters when the file is reviewed for case value, expert opinion, deposition preparation, or settlement discussion.

A narrative summary should not only tell the reader what the record says. It should show whose statement the fact came from.

Patient Reports Are Important, But They Are Not Provider Findings

Patient-reported complaints often start the medical story.

Pain level. Symptom onset. Prior injury history. Functional limitation. Medication use. How the injury happened. What makes symptoms worse. What treatment helped or failed.

These details matter, especially in personal injury and claims review.

But patient reports should be labeled as patient reports.

If a summary says, “The patient had radiating pain,” the reader may not know whether that came from the patient’s complaint, the provider’s assessment, or a diagnostic finding. A stronger summary says, “The patient reported low back pain radiating into the right leg.”

That wording is simple, but it protects accuracy.

It keeps the summary inside the record and avoids making reported history sound like an independent clinical finding.

Provider Findings Carry a Different Weight

Provider findings are different because they come from examination, assessment, observation, or clinical review.

A provider may document tenderness, swelling, limited range of motion, abnormal gait, reduced strength, positive orthopedic tests, wound findings, neurological deficits, or mental status observations.

Those details should stand apart from patient complaints.

For example:

“Patient reported neck pain” is one type of fact.

“Provider documented decreased cervical range of motion” is another.

“MRI documented disc protrusion” is another.

A good narrative summary keeps those layers clear. It does not make one sound stronger than the record supports, and it does not weaken useful provider findings by mixing them into general symptom language.

Diagnoses Need Source Context

Diagnoses can appear in several places.

They may be listed in an assessment, added to a problem list, copied forward from older records, mentioned in past medical history, or supported by diagnostic testing. Each source has a different meaning.

A diagnosis actively addressed during a specialist visit may deserve more attention than a diagnosis carried forward in a problem list with no discussion during the visit.

That is why source context matters.

A careful summary may say:

“Orthopedic note dated 05/14/2026 assessed lumbar radiculopathy after review of symptoms and exam findings.”

That is clearer than simply writing:

“Patient had lumbar radiculopathy.”

The first tells the reader who documented it and where it belongs in the medical story. The second may be too broad.

Problem Lists Can Quietly Confuse the Summary

Problem lists are useful, but they can also be misleading.

In electronic medical records, problem lists may include current conditions, old diagnoses, resolved issues, administrative entries, or items copied forward from earlier visits. If a narrative summary treats every problem-list item as actively treated, the medical story can become distorted.

For example, a problem list may include “back pain” during a visit for sinus symptoms. That does not automatically mean the back condition was evaluated during that encounter.

A strong summary should use careful wording:

“Back pain appears in the problem list; the visit note does not document active back evaluation during this encounter.”

That gives the attorney a clearer view without overstating or ignoring the information.

Intake Forms Need Careful Labeling

Intake forms can contain important facts, but they are usually patient-completed or patient-reported.

They may include prior injuries, symptom history, medication lists, pain scores, work status, allergies, and functional complaints. These details can be useful, especially when they reveal prior similar symptoms or new complaints after an incident.

But intake details should not be written as though a provider independently confirmed them unless the record shows that.

For example:

“Patient intake form reports prior right shoulder pain in 2022.”

That is more accurate than:

“Records confirm prior right shoulder condition.”

The first preserves the source. The second may move too far.

Diagnostic Reports Should Stay in Their Lane

Diagnostic testing often gives the case important structure.

MRI reports, CT scans, X-rays, EMGs, ultrasounds, labs, pathology reports, and operative findings may all become central to review. But even diagnostic records should be summarized carefully.

A radiology report can document findings. It does not automatically answer causation, damages, impairment, or legal significance.

A good narrative summary should state the finding and identify the source:

“Lumbar MRI dated 06/02/2026 documented L4-L5 disc protrusion.”

It should not stretch the finding into an unsupported conclusion.

If a treating provider later reviewed the MRI and changed the treatment plan, the summary should connect that next step separately. That gives the reader both the diagnostic fact and the clinical response.

Recommendations Are Not the Same as Completed Treatment

This is another common summary problem.

A provider may recommend therapy, injections, imaging, surgery consult, medication changes, or follow-up care. But a recommendation does not mean the treatment happened.

A narrative summary should separate:

• Recommended treatment
• Ordered testing
• Scheduled follow-up
• Completed procedures
• Missing records after the recommendation

For example, “provider recommended cervical MRI” is different from “cervical MRI completed.”

If the MRI report is missing, the summary should say so. That helps the legal team know what is documented and what still needs follow-up.

Billing Records Should Not Replace Clinical Records

Billing records can support the financial side of a case, but they do not always explain the medical facts.

A bill may show a date of service, CPT code, charge, adjustment, or balance. It may suggest that a visit or procedure occurred, but it may not show the complaint, exam findings, diagnosis, treatment plan, or response.

If a bill is present without a matching treatment note, the summary should flag that clearly.

Example:

“Billing record lists pain management visit on 07/18/2026; corresponding clinical note not included in available records.”

That sentence is useful because it avoids overclaiming. It tells the attorney what exists and what is missing.

Why This Matters During Case Review

When source types are blurred, the case can start to look stronger, weaker, or cleaner than the records actually support.

A patient complaint may be mistaken for an objective finding. A problem-list entry may be treated as active treatment. A recommendation may be written as completed care. A bill may be treated as clinical proof. A diagnosis may be repeated without showing who made it or whether it was current.

Those small wording problems can affect:

• Demand preparation
• Expert review
• Deposition preparation
• Claims evaluation
• Mediation strategy
• Trial planning

The narrative summary does not need to argue the case. It needs to keep the medical facts clean enough for qualified professionals to evaluate.

What a Source-Aware Narrative Summary Should Do

A strong narrative summary should be readable, but it should also preserve the structure of the evidence.

It should help the reader understand:

• Who documented the information
• Whether it was reported, observed, tested, diagnosed, billed, recommended, or completed
• Whether the same detail appears across multiple records
• Whether later records support or conflict with it
• Whether the source is missing, unclear, or incomplete

That is how a summary becomes useful without becoming careless.

Where Narrative Summary Support Fits

For attorneys, claims teams, IME/QME providers, and medical-legal reviewers, narrative summary services can help organize complex medical records into a clear, readable summary while preserving source context.

LezDo TechMed prepares narrative summaries based on the agreed case scope. The summary may include patient-reported complaints, provider findings, diagnoses, procedures, diagnostic reports, medications, treatment plans, prior history, gaps, contradictions, billing-support concerns, and missing records when relevant.

LezDo TechMed does not diagnose, determine causation, decide liability, assign damages, or give legal opinions. The summary presents documented medical facts so qualified professionals can evaluate them in context.

Final Thought

The question is not only, “What does the record say?”

The better question is, “Who said it?”

Was it the patient? The treating physician? A specialist? A therapist? A radiologist? A billing statement? A copied problem list?

A narrative summary that answers that question gives the reader a cleaner, safer way to understand the medical story. It keeps reported symptoms separate from provider findings. It keeps diagnostic results separate from opinions. It keeps recommendations separate from completed care.

That kind of precision may not make the summary louder.

But it makes it much easier to trust.