Case Study 1: Dr. Okafor's Two Ways of Learning Pharmacology — Memorize vs. Understand

This case study follows Dr. James Okafor, a composite character introduced in Chapter 2 and developed through Chapters 6 and 11. His experiences reflect common patterns documented in medical education research on surface vs. deep approaches to learning. He is not a real individual. (Tier 3 — illustrative example.)

Background

You've seen James Okafor at several points in this book. In Chapter 2, he was building schemas for congestive heart failure — asking "why?" questions that connected symptoms to mechanisms, contrasting similar conditions, and predicting what he'd see on diagnostic tests. In Chapter 6, you saw the consequences of sleep deprivation on his clinical reasoning. In Chapter 11, you watched him transfer diagnostic thinking across medical specialties.

Now we're going to zoom in on something more specific: the two fundamentally different ways James could approach pharmacology, and why one produces understanding while the other produces only the illusion of it.

This is a case study about depth of processing in action — in a context where the stakes couldn't be higher.

The Challenge

Second-year medical students face a pharmacology curriculum that is, by any measure, overwhelming. Over a single semester, James needs to learn approximately 300 drugs across dozens of categories. For each drug, he needs to know:

• The drug's class and mechanism of action
• Its primary clinical uses
• Its side effects and adverse reactions
• Its drug-drug interactions
• Its contraindications (when it should NOT be used)
• Its pharmacokinetics (how the body absorbs, distributes, metabolizes, and excretes it)

Do the math: 300 drugs multiplied by six categories is 1,800 individual facts. And that's a conservative estimate — many drugs have multiple uses, multiple side effects, and multiple interactions.

The volume alone is daunting. But the real challenge isn't volume — it's the type of knowledge required. Board exams don't test isolated facts. They test the ability to reason through clinical scenarios: "A 58-year-old woman with hypertension and a history of asthma presents with ankle swelling. Which of her current medications is most likely responsible?"

To answer that question, you can't just know that Drug X causes ankle swelling. You need to know why it causes ankle swelling (its mechanism), which class of drugs has that side effect (so you can match it to the patient's medication list), and why the question mentions asthma (because a common alternative medication is contraindicated in asthma — the question is testing whether you'd switch to a dangerous alternative).

This is the terrain where depth of processing becomes a survival skill.

The Surface Approach: Sarah's Spreadsheet

James's classmate Sarah is not lazy. She is organized, dedicated, and studies more hours per week than almost anyone else in their class. Her approach:

Step 1: Read the textbook entry for each drug.

Step 2: Enter the information into a master spreadsheet with columns for Name, Class, Mechanism, Use, Side Effects, Interactions, and Contraindications.

Step 3: Review the spreadsheet repeatedly before the exam, covering one column at a time and trying to recall the others.

Sarah's spreadsheet is a work of art — color-coded by drug class, alphabetized within each class, with hyperlinks to relevant lecture slides. She has invested dozens of hours in its creation.

But watch what happens at the encoding level:

When Sarah enters "Amlodipine — calcium channel blocker — blocks L-type calcium channels in vascular smooth muscle — hypertension, angina — peripheral edema, dizziness — avoid in severe heart failure," she is doing two things:

1. Reading and comprehending each phrase (shallow semantic processing)
2. Typing it into the correct cell (structural processing — she's interacting with the spreadsheet layout)

She understands the words. She could define each term if asked. But she has not built connections. The fact that amlodipine causes peripheral edema exists in her spreadsheet as an isolated datum. It is not connected to why it causes edema (calcium channel blockers dilate arterioles more than venules, causing fluid to leak from capillaries into tissues) or to how this differs from the edema caused by heart failure (which involves venous congestion, not arteriolar dilation).

Sarah's encoding is semantic but not elaborative. She has processed meaning at the sentence level but not at the explanatory level.

The Deep Approach: James's Question Cascade

James reads the same textbook entry. Then he closes the book.

"OK, amlodipine. Calcium channel blocker. But what does that actually mean? Calcium channels are involved in muscle contraction — when calcium flows into smooth muscle cells, the muscle contracts. Block the channels, and the muscle relaxes. Vascular smooth muscle lines the walls of blood vessels, so relaxing it means the vessels dilate. Dilated vessels = lower blood pressure. That's why it treats hypertension."

"But why peripheral edema? If the arterioles dilate but the venules don't dilate as much, there's a pressure imbalance. More blood gets pushed into the capillary bed but can't drain as efficiently. The increased capillary pressure forces fluid out into the surrounding tissue. Ankles swell because gravity pulls the fluid down."

"How is that different from heart failure edema? In heart failure, the heart can't pump effectively, so blood backs up in the venous system. The venous congestion increases capillary pressure from the drainage side, not the supply side. Same symptom — swollen ankles — but completely different mechanism. A board question could test whether I know the difference."

"And why avoid it in severe heart failure? Because the vasodilation reduces afterload, which seems like it should help — but amlodipine can also have negative inotropic effects (reducing the heart's contractile force). In a heart that's already failing, reducing contractile force could be dangerous. Although... actually, amlodipine is one of the safer CCBs in heart failure compared to verapamil or diltiazem, because it's dihydropyridine-selective. Let me check that."

James checks. He was right — and the process of checking has now created an additional memory trace, connected to the moment of uncertainty and resolution.

Notice what has happened. James has processed the same information as Sarah, but his encoding is qualitatively different:

The Exam

Six weeks later, James and Sarah sit for the same pharmacology exam. Here's a sample question:

A 62-year-old woman has been taking amlodipine for hypertension. She presents with bilateral ankle swelling. Her physician considers switching her to an alternative antihypertensive. The patient also has a history of asthma. Which of the following medications should be AVOIDED as a replacement?

A) Lisinopril B) Hydrochlorothiazide C) Propranolol D) Losartan

Sarah's experience: She remembers that amlodipine causes edema. She looks at the options. She needs to find the one that's contraindicated. She knows propranolol is a beta-blocker, but she can't remember why it would be avoided. She vaguely recalls something about beta-blockers and breathing, but the connection isn't there. She guesses C, uncertain.

James's experience: He sees the question and immediately recognizes the pattern. "They're telling me the patient has asthma — that's a big clue. Propranolol is a non-selective beta-blocker. Beta-2 receptors are in the lungs. Blocking beta-2 causes bronchospasm. In a patient with asthma, that could trigger a life-threatening attack. The answer is C." He is confident, and he's correct.

Both students spent similar amounts of time studying. Sarah arguably spent more time, because her spreadsheet was comprehensive and she reviewed it multiple times. But James's time was spent building a causal web that allows him to reason through novel clinical scenarios, not just recall stored facts.

The Deeper Lesson: Two Types of "Knowing"

This case study illustrates a distinction that goes beyond study technique. Sarah and James represent two fundamentally different relationships with knowledge:

Sarah knows THAT. She knows that amlodipine is a calcium channel blocker. She knows that propranolol is a beta-blocker. She knows that amlodipine causes edema. These are facts she has stored and can retrieve when the cue matches perfectly.

James knows WHY. He knows why amlodipine works (mechanism), why it causes edema (pathophysiology), why propranolol is dangerous in asthma (receptor biology), and how to reason from mechanism to clinical decision. His knowledge is organized around explanations, not associations.

This distinction maps directly onto the levels of processing framework:

• Knowing THAT requires semantic encoding at a basic level — understanding the meaning of each fact.
• Knowing WHY requires elaborative processing — building causal connections, generating explanations, predicting consequences, and integrating facts into a coherent framework.

The difference isn't just academic. In medicine, the difference between knowing THAT and knowing WHY is the difference between a doctor who follows protocols and a doctor who can adapt when the patient doesn't fit the protocol. James will be a better physician not because he's smarter than Sarah, but because his encoding builds the kind of flexible, transferable knowledge that expert clinical reasoning requires.

What James Can Teach You

You probably aren't studying pharmacology. But the principle applies to every subject:

In history: You can know THAT the Treaty of Versailles was signed in 1919, or you can know WHY its terms made a second world war more likely. One is a fact. The other is understanding.

In economics: You can know THAT raising interest rates reduces inflation, or you can know WHY (higher rates increase the cost of borrowing, which reduces spending, which decreases demand, which puts downward pressure on prices). One lets you answer a definition question. The other lets you predict what will happen in a scenario you've never seen.

In literature: You can know THAT Jay Gatsby represents the American Dream, or you can know WHY Fitzgerald chose specific symbols, scenes, and narrative techniques to build that representation — and how those choices reflect the social anxieties of the 1920s.

In every case, the "why" version requires more effort during encoding. It requires you to stop, think, generate questions, and construct explanations. It is a desirable difficulty (Chapter 10). It feels harder and less productive than simply recording the fact. And it produces dramatically better understanding, retention, and transfer.

The Question That Changes Everything

If you take one thing from this case study, let it be this: the single most powerful thing you can do to deepen your processing is to ask one simple question every time you encounter a new fact or concept:

"Why?"

Why is this true? Why does this happen? Why does it matter? Why is it different from that other thing?

That question — asked genuinely, with the patience to construct an answer — is the engine of deep processing. Dr. Okafor doesn't have a special brain. He has a special habit. And habits can be learned.

Discussion Questions

1. Diagnose the encoding. At what specific point does Sarah's study method fail to engage deep processing? Is there a version of the spreadsheet approach that could work at a deeper level? What modifications would be needed?

2. Analyze the exam performance gap. The exam question about propranolol and asthma requires knowledge that was technically available to both students. Why could James access it and Sarah couldn't? Frame your answer in terms of retrieval pathways and the interconnectedness of encoded knowledge.

3. Evaluate the "knowing THAT vs. knowing WHY" distinction. Is there a place for "knowing THAT" in learning? Are there situations where fact-level knowledge is sufficient? When does the difference between THAT and WHY matter most?

4. Apply to your own field. Choose a topic from your own area of study. Write one fact about it (knowing THAT) and then construct the "knowing WHY" version — the causal explanation, the connections, the implications. Notice how much more effort the WHY version requires. Evaluate honestly: which version do you typically study?

5. Connect to transfer. How does James's elaborative encoding prepare him for transfer — using his pharmacology knowledge in clinical situations he's never studied? Connect your answer to the transfer concepts from Chapter 11 (near vs. far transfer, structural similarity, abstract schemas).

6. Design an intervention for Sarah. If you were Sarah's study partner and could observe her spreadsheet method, what specific changes would you recommend? Be concrete: don't just say "study deeper." Describe exactly what she should do differently and when.

7. Examine your own habits. Be honest: in your current studies, are you more like Sarah or more like James? What percentage of your study time is spent at Sarah's level vs. James's level? What would it take to shift that ratio?

End of Case Study 1. Dr. Okafor's story continues in Chapter 16 (Self-Testing and Practice Exams), Chapter 21 (Deliberate Practice), and Chapter 25 (From Novice to Expert).