Case Study 2: One Fact, Three Readers — and the SOAP Note That Held It Together

DataField.Dev

Case Study 2: One Fact, Three Readers — and the SOAP Note That Held It Together

⚠️ Disclaimer: Educational only; not medical advice. This is a composite, fictional-but-realistic scenario; all clinical values, doses, and thresholds are illustrative placeholders.

A contrasting deep dive: how a single clinical situation generated three correct-but-different documents, and how the discipline of SOAP kept the underlying record honest.

The situation

A community clinic starts a patient—call him Mr. Adeyemi—on a new medication after a routine visit turns up an elevated risk marker. The same underlying reality now has to be written down for three different readers, in three different documents, none of which can be wrong, and all of which must agree on the facts. This is the three-audience problem from 36.4, in the field.

The clinical reality (the constant fact): - The marker is elevated; a medication is indicated to lower it. - The medication commonly causes mild, transient stomach upset early on. - It should not be used by people with severe kidney problems; the dose is adjusted in moderate kidney impairment.

Three documents flow from this single reality. Watch the fact stay constant while each document reshapes itself around its reader.

Document 1 — The clinical note (for the next clinician)

The clinician writes a SOAP note. Notice the separation of observation from interpretation, and that full medical vocabulary is help, not barrier, for this reader.

S: Asymptomatic; here for routine follow-up. No GI complaints currently. Reports no known kidney disease. O: [Marker] elevated at [value] (ref < [value]). Renal function within normal limits. (Illustrative.) A: Elevated [marker] warranting pharmacologic management. No contraindication identified. P: Start [medication] at [dose] once daily with food. Counsel re: expected mild GI upset, transient. Recheck [marker] and renal function in [interval]. Patient to report severe or persistent GI symptoms.

This is precise, fast to read, and uses terms a clinician needs ("contraindication," "renal function"). It also keeps the Assessment honest: "no contraindication identified"—acknowledging the limit of what's known, not overclaiming. A covering clinician could pick this up cold.

Document 2 — The patient instruction (for Mr. Adeyemi)

Same fact, rewritten at a 6th–8th-grade level, with the three patient questions answered and a teach-back built in.

Your new blood-test medicine

This medicine lowers a level in your blood that was too high. Lowering it helps protect your health over time.

Take 1 tablet once a day, with food. Taking it with food helps your stomach.

You might get an upset stomach when you start — feeling a little sick, or loose stools. For most people this is mild and gets better in a few days.

If your stomach upset is bad or doesn't go away, call us.

Tell us if you have any kidney problems, now or in the past — this medicine isn't right for everyone with kidney trouble.

Before you leave, we'll ask you to tell us how you'll take this and what you'd watch for — just so we know we explained it well.

Here "contraindicated in severe renal impairment" became "tell us if you have any kidney problems," because the patient's job is to disclose, not to assess his own kidney function. "GI adverse effects" became "upset stomach," paired with a coping action and an escalation trigger. The fact is intact; the reading level and called-for action are transformed.

Document 3 — The regulatory/label language (for the regulator and pharmacist)

Same fact again, now built to be audited: every claim tied to evidence, every term carrying its precise definition, no reassurance and no rounding.

In the pivotal trial (n = [N]), [medication] reduced [marker] relative to placebo (effect size and 95% CI as reported). Gastrointestinal adverse events (nausea, dyspepsia) occurred at a higher rate in the treatment arm than placebo, predominantly mild and transient; [X]% led to discontinuation. Contraindicated in severe renal impairment (defined as [criteria]). Dose adjustment required in moderate renal impairment per the approved label.

This version trades warmth for defensibility. "Mild stomach upset for most people" becomes a rate with a discontinuation figure; "kidney problems" becomes "severe renal impairment (defined as [criteria])." This is the closest of the three to the engineering and scientific registers of Chapters 33 and 35 — language whose job is to survive scrutiny.

The thing that could have gone wrong

Imagine the documents drift apart. The SOAP note's Assessment says "no contraindication" but never recorded that renal function was actually checked — so the basis for that claim is missing, and a later reviewer can't tell whether kidneys were assessed or assumed. Each such gap is a place where the three documents stop agreeing on reality, and in healthcare, documents that disagree about a patient are a hazard.

The safeguard is the one this chapter keeps returning to: the fact is constant; only the document changes. When you write the patient version, you are translating the same reality the clinician note recorded — not softening it, not omitting the safety caveat, not inventing reassurance the data don't support. The SOAP note is the anchor that keeps the other two honest: it forces you to record what you observed (renal function checked, value normal) separately from what you concluded (no contraindication). If the observation isn't there, the conclusion has nothing to stand on, and the leaflet built on top of it inherits the gap.

What this case teaches

Three readers, three documents, one fact. The clinician version optimizes for precision and speed; the patient version for comprehension and action; the regulator version for traceability and proof. Same reality, three shapes (36.4).
Getting the audience wrong is dangerous, not just ineffective. Hand Mr. Adeyemi the regulatory paragraph and he drowns; hand the regulator the leaflet and the claim is unverifiable; strip the clinician's note to plain language and you slow down care with vagueness.
SOAP keeps the record honest. By separating observation from interpretation, it ensures the claims in the patient and regulatory documents trace back to something actually measured.
Translation is not softening. Plain language changes the expression for the patient; it must never drop the safety caveat or inflate reassurance the evidence doesn't support. Truth is the constant across all three (36.7).

The skill on display is the one Chapter 40 asks your portfolio to prove: render expert content correctly for whatever reader is in front of you — including the reader who will be harmed if you get it wrong.