Chapter 5: Clinical Reasoning, Assessment, & Plan

Welcome to Last Minute Lecture.

This free chapter overview is designed to help students review and understand key concepts.

These summaries supplement not replaced the original textbook and may not be redistributed or resold.

For complete coverage, always consult the official text.

Welcome back to another Deep Dive.

Today, we are tackling something that I think every single one of us has wondered about at some point.

You know that feeling when you go to the doctor, you're sitting there on that crinkly paper, and you tell them a few, um, seemingly random things.

Totally unconnected.

Yeah, like, doc, my throat hurts, or I have this weird pain in my side.

Maybe, you know, I've been feeling a bit dizzy lately.

And then suddenly within minutes, they're just nodding.

They've got it.

It feels like they've already figured it out.

Exactly.

They seem to know exactly what's going on.

They start ordering specific tests or writing prescriptions before you've even finished your story.

It really feels like a magic trick, doesn't it?

Like they're pulling a rabbit out of a hat.

You give them all this noise, and somehow they give you a clear signal.

It's this black box of medical diagnosis.

You feed in the raw symptoms, this, you know, machine whirs, and out pops the answer.

But today, we are going to crack that box wide open.

I like that.

We aren't just admiring the magic trick.

We are going backstage to see how all the mirrors and trapdoors actually work.

And for that, we're diving deep into chapter five of Bates's Guide to Physical Examination and History -Taking.

A classic text, for sure.

And this specific chapter is, I'd argue, the pivot point of the entire book.

It's titled Clinical Reasoning, Assessment, and Plan.

Which, I'll admit, sounds a bit dry.

But our mission today is to decode it.

We want to understand how a clinician moves from simply gathering data,

you know, asking questions, poking around, using the stethoscope.

All the stuff from the earlier chapters.

We're actually synthesizing all of that into a diagnosis and, you know, a concrete action plan.

And I think we should be explicit right up front.

If you are a student, a resident, a PA, or just starting out on your clinical journey, this deep dive is absolutely for you.

Yeah, we're talking directly to you.

We know the Bates text can be dense.

And chapter five, I mean, it's full of tables and diagrams and heavy cognitive theory concepts.

It can be overwhelming.

It really can.

So our goal is to break all of that down into plain English, step by step.

Okay, so, lay it out for us.

What is the roadmap for this journey?

How are we going to deconstruct what feels like medical intuition?

We're going to follow the chapter's exact sequence because it builds this logical scaffolding for your brain.

Okay.

We'll start with the psychology of reasoning.

How our brains actually work when we're solving these complex problems.

Then we'll move to the structure.

How do you gather and organize all the chaotic data a patient gives you?

Right.

How do you sort the wheat from the chaff?

Precisely.

From there, we'll talk about problem representation and these things called illness scripts, which are just fascinating concepts for understanding how experts think.

I love that term, illness scripts.

It sounds very Hollywood, like we're casting a movie for a disease or something.

It's a great way to think about it.

And we will absolutely get deep into it.

Then we have to talk about the traps.

The mistakes.

The cognitive errors that can lead even the best doctors astray.

And finally, we'll get super practical.

How do you document your thoughts in the assessment and plan?

And then how do you communicate all of that to other doctors in what's called the oral presentation?

Hopefully without boring everyone to tears or, you know, missing the diagnosis completely.

That's the goal.

We want to move you from just reporting facts.

The patient said this.

I found that to actually analyzing them.

Okay.

Let's unpack this.

Let's start with the brain.

The text opens with this concept of dual processing theory.

This sounds like something out of a computer manual.

What is going on here?

It does sound really technical, but it's actually rooted in behavioral economics.

It comes from Daniel Kahneman, the Nobel laureate.

The text explains that when we make decisions, any decision, any decision, whether we're diagnosing a patient or decided what to eat for lunch, we use two distinct cognitive systems.

They're just called system one and system two.

System one and system two.

Okay.

Very creative names.

Let's break them down.

What is system one?

So system one is the intuitive system.

It's fast.

It's automatic.

It relies heavily on what we call heuristics, which are basically mental shortcuts.

Habits.

Exactly.

Habits we've formed over time.

It's just pure pattern recognition.

So system one is kind of like when you see a red light while you're driving and you just hit the brake.

You don't sit there and look, a specific wavelength of light is illuminating, indicating I should depress the pedal.

Right.

You just do it.

It's instant.

It's immediate.

And in medicine, this is the experienced doctor who walks into a room, glances at a blistering rash on a patient's torso, and their brain just goes, that shingles instantly.

They don't have to look it up.

They don't have to weigh probabilities.

Nope.

The pattern just matches and the answer appears.

That's system one in action.

Okay.

So that's the fast lane.

That's the autopilot.

What about system two?

System two is what the book calls the hypothetical deductive system.

That is a mouthful.

It is a mouthful, but it basically just means it's slow.

It's tempered, logical, and analytic.

It relies on probabilities and rigorous analysis, and it's very resource intensive for your brain.

So if we go back to the driving analogy, if system one is driving home on a familiar road, what is system two?

System two is driving in a foreign country on the wrong side of the road in a torrential rainstorm while you're trying to read road signs in a language you only kind of know.

Oh, wow.

Okay.

So you are gripping the wheel, the radio is off, you're leaning forward.

You're hyper -focused on every single decision.

You are consciously processing every single input.

And in medicine.

In medicine, this is the student.

When you're learning, everything is system two.

A patient says chest pain, and you have to literally stop and think, okay, what causes chest pain?

Heart, lungs, muscles, ribs.

You are building the logic brick by brick.

So here's the big question then.

Is one better than the other?

Should we all be striving to be in system two all the time because it's more logical, or is the goal to become a system one wizard?

And that is the trap.

The text really emphasizes that competent clinicians use a blend of both.

You have to.

Why?

Well, if you use system two for every single thing,

like deciding which pen to pick up or diagnosing a common cold, you'd be mentally exhausted by noon.

You would just burn out.

But on the other hand, if you only use system one, you become incredibly prone to errors because you're relying too much on intuition in those shortcuts.

You might miss the subtle details that don't fit the pattern.

The art of medicine is learning how to toggle between them.

So there's a diagram in the text, figure five one, that tries to describe this cycle.

It shows the patient's story interacting with data acquisition.

Can you walk us through that visual?

It seems like it's trying to map out this toggling process you're talking about.

Yeah, it's a great little diagram.

Imagine a circle and surrounding this circle are three key things, knowledge, context, and experience.

Okay, so those are the filters you're bringing to the table.

Exactly.

Now inside the circle, the process flows like this.

First, you get the patient's story.

That leads to data acquisition, you know, asking questions, doing the exam.

That data then helps you build what the book calls an accurate problem representation, which is just a fancy way of summarizing the case, right?

From that summary, you generate a hypothesis.

Then you search your mental database for an illness script, a model of a disease, to see if it matches.

That leads to a diagnosis.

But you said it's a cycle.

And here's the key.

It is a cycle.

If the script doesn't fit, if that puzzle piece is the wrong shape, you go back.

You loop back to data acquisition.

You ask more questions.

You order a test.

So it's iterative.

You don't just move in a straight line from A to B.

You loop back if things don't make sense.

Precisely.

And for the student, this cycle is often conscious and slow.

That system, too, working really hard.

For the expert, the cycle can spin so fast it looks like a straight line.

That's system one taking over.

But the underlying steps are actually the same.

Okay, that's a fantastic foundation.

So let's get into the nitty gritty.

We understand the brain software now.

Let's talk about step one, gathering and organizing the data.

The text makes a really interesting point here.

It says the data comes from everywhere.

History, physical exams, labs, old records.

But the challenge isn't just getting the data.

No, not at all.

It's figuring out how to group it.

And that is the biggest hurdle for a novice, isn't it?

You have a patient with 10 different complaints.

My head hurts.

My toe itches.

I'm tired.

I have a cough.

Are those 10 different problems?

Or are they one problem that's manifesting in 10 different ways?

That's the question.

The text calls this clustering.

And it offers some really good strategies for the novice on how to do this.

Because if you don't cluster, you just have a meaningless laundry list.

Let's run through these strategies.

The first one is pretty intuitive.

Anatomic location.

Yeah, this is the most straightforward one.

You cluster findings by body part.

The text gives a clear example.

If a patient has a scratchy throat and you look in and see an inflamed pharynx and maybe you feel some swollen glands in the neck, you cluster those together.

It's a pharynx problem.

It's a pharynx problem.

Easy enough.

Or a headache.

That points to the skull or brain.

But the text warns us it can get tricky pretty fast.

Take chest pain.

Oh, chest pain is notorious.

Everyone hears that and immediately thinks heart attack.

Right.

But is it the heart?

Is it the esophagus?

The muscles of the chest wall?

The lungs?

Even the skin, like with shingles.

If you just cluster by chest, you might miss the nuance.

So what's the next layer?

You add a qualifier.

If you cluster by exertional pain relief by rest, now you're pointing specifically toward the cardiovascular system.

So what anatomy is a starting point, but you often need more.

Okay.

Another strategy mentioned is age, which seems a bit broad.

I mean, how does knowing someone's age help you organize their symptoms?

It's a probability game, really.

It helps you decide whether it be a lumper or a splitter.

A lumper or a splitter.

I like that.

The text notes that young, healthy patients are much more likely to have a single disease causing all their symptoms.

So if a 20 -year -old comes in with fever, cough, and joint pain, you try to lump them all into one diagnosis.

You look for a single cause.

Occam's razor.

The simplest explanation is usually the right one.

Exactly.

But with older patients, they often have multiple chronic conditions.

So if an 80 -year -old has fever, cough, and joint pain, the joint pain might just be their chronic arthritis acting up, while the fever and cough are a brand new pneumonia.

So you split the symptoms into different buckets.

Split them.

So age guides your whole strategy for organization right from the start.

That's a really helpful rule of thumb.

Now let's talk about timing.

This was my favorite part of this section.

The text gives a fantastic example involving syphilis that really clarifies how the timeline is the diagnosis.

This is a classic, classic example of how timing defines the problem.

So let's look at two different scenarios in the book.

Scenario A, a patient has a yellow penile discharge, and then three weeks later, a painless ulcer appears on the penis.

Okay, I'm visualizing the timeline.

Discharge first, then the ulcer.

The timing here suggests two separate infections.

The discharge is likely gonorrhea, which has a really short incubation period.

The ulcer is likely syphilis, which takes much longer to show up.

So even if he got them at the same time.

They manifest on different clocks, so you document them as two separate problems.

Okay, now what's scenario B?

Scenario B, a patient has a penile ulcer first.

That ulcer heals up on its own.

Then six weeks later, they develop a rash on their palms and soles and swollen lymph nodes.

Okay, so ulcer first, then rash much later.

In this case, the timing suggests one problem, syphilis.

The ulcer was primary syphilis.

The bacteria then spread through the blood, and six weeks later it caused secondary syphilis, which is the rash.

Same disease, just different stages.

That is fascinating.

So the novice might just see ulcer and rash in both cases, but the timeline tells the real story.

In one case, it's a co -infection.

In the other, it's a progression.

Exactly.

If you don't map it out chronologically, you completely miss the connection.

Now, the text mentions multi -system conditions as sort of the expert level skill.

This is where you link seemingly unrelated things across different body systems.

There were two really detailed examples in the text that I want to walk through because they showed just how powerful this logic can be.

Let's do the plumber.

This is a classic teaching case.

Okay, the 60 -year -old plumber.

He's a smoker.

He comes in with a cough.

He's coughing up blood hemoptysis, and he's lost weight.

So immediately, your system one thinking kicks in.

60 -year -old smoker plus coughing blood plus weight loss equals lung cancer.

That's the anchor.

Right.

That's the first guess.

But then you start seeing other things on the exam that seem totally random.

He has cyanotic nail beds.

His fingernails are turning blue.

Which links back to the lung's lack of oxygen.

That fits the cluster.

So far, so good.

But then he has dysphagia trouble swallowing.

Why would a lung problem cause trouble swallowing?

That seems like a throat or esophagus issue.

It does.

And a novice might say, okay, problem number two, swallowing issue.

But the expert links this.

The cancer in the chest.

Wow.

Okay.

Then you notice pupillary asymmetry.

One pupil is a different size from the other.

Specifically, one is constricted.

Now that seems completely random.

How on earth does a lung tumor affect your eye?

Exactly my question.

It seems random, but the expert knows the anatomy.

The cervical sympathetic chain.

It's a nerve bundle that controls the pupil.

It runs right past the apex, the very top of the lung.

A tumor growing right there, called a pankos tumor, can press on that nerve and cause the pupil to shrink.

It's called Horner's syndrome.

So the eye is literally telling you about the lung.

Precisely.

And then the text mentions the final piece.

Jaundice yellow skin.

Which implies liver issues.

Which, in this context, implies liver metastasis.

So the novice has a list.

One, cough.

Two, swallowing issue.

Three, eye issue.

Four, liver issue.

The expert looks at all that and says, this is all lung cancer.

One diagnosis explains every single disparate fact.

That is the Sherlock Holmes moment.

It's incredibly satisfying when it clicks like that.

It is.

And the second example is just as powerful.

The young man with odinophagia, which is painful swallowing, fever, purple skin lesions, and diarrhea.

Again, seemingly disconnected.

You've got throat, skin, gut.

But when you cluster them as a multi -system condition in a young man, the pattern just screams AIDS.

The purple lesions are likely Kaposi's sarcoma.

The painful swallowing isn't just a sore throat.

It's likely candid aesophagitis.

The diarrhea is likely cryptosporinium or another opportunistic infection.

So again, instead of treating three different things, you recognize that the underlying immune system failure is the root cause of all of them.

Exactly.

It's efficient thinking.

But to get there, you have to be able to represent the problem correctly.

Which brings us right to step two.

The problem representation.

Or, as it's often documented, the summary statement.

The text calls this a synthesis.

It's not just a list of facts.

And they track a case study in box 5 -2 that shows how the statement evolves.

I think this is crucial for listeners to hear the difference between an okay summary and a great one.

Yes.

Let's follow this patient.

It's a 57 -year -old male.

Right.

So stage one.

The patient walks into the ER.

He has chest pain for two hours.

The initial problem representation is just.

57 -year -old male with acute onset chest pain.

Very broad.

Could be anything.

Heartburn, muscle strain, panic attack.

It's too broad.

It doesn't trigger enough specific answers in your brain.

So you take a history.

You find out he was shoveling snow.

So the pain is exertional.

It's retro -sternal deep behind the breastbone.

He has shortness of breath.

He smokes a pack a day.

And critically, he has a known history of heart failure.

Okay.

That changes the picture dramatically.

So the stage two summary becomes a 57 -year -old male with congestive heart failure and a 35 -pack year smoking history presenting with acute, severe, exertional, retro -sternal pain and associated shortness of breath.

That's so much witcher.

The words exertional and retro -sternal are heavy hitters there.

Huge.

But we aren't done.

Then you do the physical exam.

And on the exam, you find an S3 gallop, a very specific extra heart sound.

You hear crackles in his lungs.

You see edema or swelling in his legs.

So stage three, the final synthesis captures it all.

A 57 -year -old man with congestive heart failure presenting with exertional pain.

Examination is notable for a new S3 gallop by basilar crackles and bilateral lower extremity edema.

So why is it so important to write it out like that?

Why go through the effort of crafting that specific paragraph?

Because that specific combination of words activates the illness script in the doctor's mind.

When I hear S3 gallop, crackles, edema, chest pain, my brain instantly unlocks the acute heart failure ischemia script.

You just said chest pain and leg swelling.

I might not make that connection as strongly.

I might think blood clot.

So the words you choose, the text calls them semantic qualifiers.

They actually program your brain to find the right answer.

Exactly.

Words like acute versus chronic, unilateral versus bilateral, exertional versus resting.

These are like little binary switches that narrow down the search field in your mind.

Which leads us perfectly to step three, generating hypotheses and illness scripts.

We've got our summary statement.

Now we need to figure out what caused it.

The text offers two main ways to do this.

One for the novice and one for the pro.

The novice method is the exhaustive method.

You might've heard the mnemonic vindicate.

Vindicate.

Sounds intense.

It is.

It stands for a list of categories.

Vascular, infectious, neoplastic, drug -related, inflammatory, congenital, autoimmune, trauma, endocrine.

So you basically run the symptom through every single one of those letters.

Yes.

You literally say, could this chest pain be vascular?

Maybe a clot.

Could it be an infectious, maybe pneumonia?

Could it be trauma?

Did he get hit?

It ensures you don't miss anything.

It's great for learning, but it is terrible for time management.

Why is that?

Because if you did this for every single patient in a busy clinic, you would never go home.

You just can't consider every possibility for every symptom.

So how do the experts do it so fast?

They use illness scripts.

This is the pattern recognition method we talked about.

And the text uses the fire truck analogy, which I think is just brilliant.

Please explain the fire truck.

If I ask you to picture a fire truck, what do you see in your mind's eye?

I see a big red truck, a ladder on top, flashing lights, a siren, maybe a Dalmatian if we're being old school.

Right.

That is your script or your prototype for a fire truck.

But let's say you're walking down the street and you see a large yellow truck with a ladder and lights and a siren.

I'd still think it's a fire truck, just a yellow one from the airport, maybe.

Exactly.

You recognize it as a variant of the script.

It doesn't match perfectly, but it matches enough of the key features.

An expert clinician does the exact same thing.

Their script for appendicitis is the red fire truck, young patient, lower quadrant pain, nausea, vomiting, fever.

The textbook presentation.

The classic.

But what if an older patient comes in with just some vague abdominal pain and a fever?

The expert recognizes the yellow truck, atypical appendicitis.

The novice might miss it because it doesn't match the red truck perfectly.

They might say, well, the pain isn't in the right spot, so it can't be appendicitis.

That makes so much sense.

So experience is just building a bigger and bigger database of prototypes and all their variations.

Yes.

You learn the red truck, then the yellow truck, then the green truck.

And to refine these scripts, we use defining and discriminating features.

The text has a great visual for this.

Figure 5 -2.

It's a Venn diagram comparing dementia, depression, and delirium.

Ah, the 3Ds of geriatrics.

They're so often confused because they can look really similar on the surface.

Right.

And the diagram shows the phrase impaired memory right in the center where all three circles overlap.

That's a shared feature.

If a patient has impaired memory, it could be dementia, it could be delirium, it could be depression.

Just knowing they have memory loss doesn't help you choose between them.

It's a non -discriminating feature.

So what are the discriminating features, the ones that live on the outer edges of the Venn diagram?

These are the unique markers.

For dementia, the discriminator is globally disordered cognition that happens over a long timeline.

For delirium, the key is fluctuating awareness.

They are lucid one moment and completely out of it the next.

The lights are flickering on and off.

And depression.

For depression, it's anhedonia, the profound lack of pleasure or a flat effect.

So you look for the unique markers to tell them apart.

You diagnose by difference, not by similarity.

Exactly.

You don't focus on the overlap, you focus on the edges where they differ.

Which brings us to step 4, testing and selecting the diagnosis.

You've got your list of possibilities, now you have to narrow it down.

The text talks about eliminating possibilities first.

Right.

You test your hypothesis against the actual findings from the patient.

The text gives an example of a patient with a headache.

You might think, could this be a cluster headache?

That's your hypothesis.

But then you look at the data you've collected.

And the patient has a throbbing bifrontal, meaning both sides, headache with nausea.

The script for a cluster headache says the pain should be unilateral, one side, and boring, like a drill.

And it usually comes with a runny nose or a tearing eye, which is called lacrimation.

So if the patient doesn't have those things.

You eliminate cluster headache, it doesn't fit the script.

The absence of the tearing eye and the presence of bilateral pain makes that diagnosis highly unlikely.

Then there's weighing probabilities.

This is where demographics come in again, right?

Absolutely.

Back pain is the example here.

If a 70 -year -old male comes in with new back pain, you have to keep metastatic cancer or severe osteoarthritis high on your list of possibilities.

The probability is just higher because of his age and sex.

But if a 25 -year -old female comes in with the exact same pain.

Cancer is way, way, way down the list.

The probability is just completely different based on the context circle we talked about at the very beginning.

And then there's the worst case scenario.

The text calls this a crucial rule of thumb.

This is the safety net.

It's basically the don't kill the patient rule.

A pretty important rule.

I'd say so.

No matter what you think the diagnosis is, you must always consciously ask yourself, what is the worst thing this could possibly be?

If a patient has a headache, you might think it's just tension, but you have to actively rule out meningitis or a subdural hematoma.

You have to explicitly think about it and document why it's not that.

Yes.

If they have chest pain, you have to rule out a pulmonary embolism.

You can't just assume it's the benign thing until you've considered and excluded the life threat.

And after all that, you settle on a working diagnosis.

Which is just the problem defined at the highest level of certainty you have at that moment.

Sometimes it's really specific.

Tension, headache.

Sometimes if you don't know yet, the diagnosis is just headache, cause unknown.

And that's okay.

Honesty is part of the reasoning process.

This all sounds very logical, very Spock -like, but we're human.

And the text devotes a whole section to cognitive errors.

The traps our brains fall into.

Box 5 -6 lists a bunch of these.

I want to go through them because I feel like I do these in my daily life, not just in medicine.

Oh, we all do.

These are fundamental flaws in human thinking.

In system one thinking, specifically.

Okay.

First up, anchoring bias.

This is locking onto the first piece of information you see.

The vignette in the text is a clinician who hears a patient describe an aura before their headache.

They instantly anchor on migraine.

Because migraines have auras, it fits.

It does.

But because they anchored so early, they stop looking for other clues.

They miss the red flags -like signs of intracranial pressure that suggest it's actually a brain tumor.

They found one clue that fit and they start the investigation right there.

Oof.

Okay, next is the availability heuristic.

This is the recent memory bias.

If you saw three cases of appendicitis yesterday, you were primed to see it again today.

It's available at the front of your mind.

So when an adolescent girl comes in with abdominal pain, you immediately say appendicitis.

And you might miss ovarian torsion, which is a surgical emergency.

Because you're diagnosing based on your recent memory, not the patient in front of you.

Exactly.

Confirmation bias.

This is a big one everywhere, but how does it work in medicine?

It's when you look only for evidence that proves you right.

And you subconsciously ignore evidence that proves you wrong.

So if I think a patient has a simple cold - You focus on the cough and the runny nose.

But you might subconsciously ignore the dull thud when you percuss their chest.

A sound which actually suggests pneumonia.

You literally don't see or hear the contradictory evidence because you're so focused on confirming your initial theory.

Diagnostic momentum.

This one sounds like physics.

It's the inertia of a label.

If the doctor in the ER said this patient has acid reflux and that patient comes up to you on the floor with the same pain, you just assume it's acid reflux.

You don't start from scratch.

You accept the label.

And if the first doctor was wrong?

Then everyone who comes after is wrong.

The vignette in the book mentions a patient treated for reflux who is actually having a heart attack.

The momentum of the first wrong diagnosis carried everyone right over the cliff with it.

That is terrifying.

Finally, visceral bias.

This is emotional.

It's letting your feelings toward a patient, good or bad, affect your judgment.

The text gives the example of a homeless patient.

A doctor might assume, oh, this person can't manage a complex plan, so they prescribe a simpler but less effective treatment without even discussing the better options.

Or maybe a patient you really like so you don't want to give them bad news and you end up minimizing their symptoms.

Exactly.

Positive or negative feelings can cloud your objectivity.

Just knowing these traps exist seems like it must be half the battle.

It is.

The text advises us to slow down,

actively seek alternative diagnoses, and my personal favorite.

Remember, you are often wrong.

A dose of humble pie.

Essential for any good doctor.

Okay, so we've reasoned, we've diagnosed, we've tried to avoid the traps.

Now we have to write it all down.

Documentation.

The assessment and plan.

The text says this is the big shift from recording findings to analysis.

Right.

The history and physical are the facts.

Patient says X, I found Y.

The assessment and plan is what you think about X and Y.

It's your argument.

It's your thesis.

And we talked about those semantic qualifiers earlier.

Acute versus chronic.

Bilateral versus unilateral.

This is where they really shine, right?

Yes.

You use them here to make your summary concise and incredibly powerful.

Acute, severe, exertional chest pain tells a much bigger and more precise story than just chest hurts.

So let's talk about structuring the assessment and plan.

It's not just a big paragraph of text.

No, absolutely not.

It's a numbered list.

You prioritize the problems.

Problem number one is usually the chief complaint, the reason they came in today.

Then you list the other active issues.

And for each problem, you need an analysis and a plan.

To make this real, the text provides a deep dive case study of a patient named MN.

This is a detailed walkthrough of a full assessment and plan for a specific patient.

I really want to go through her problem list because it shows how comprehensive this needs to be.

Patient MN is a great example because she's complicated like most real patients are.

She's 54.

She has a lot going on.

So problem one is headaches.

Right.

So the assessment part analyzes the headache.

The text says it's likely a migraine because the pain is pulsatile and she has nausea.

It's less likely to be a tension headache because those are usually bilateral, though it's still possible.

And it's unlikely to be something dangerous like a tumor because she has no fever or stiff neck.

That's the reasoning.

What's the plan for it?

It's not just take a pill.

The plan is multi -promed, discuss triggers, work on stress management, and start with NSAIDs like ibuprofen.

And if it gets worse, then you consider prophylactic meds.

Problem two is elevated blood pressure.

And note the wording there.

It's not hypertension yet.

Why not?

Her BP is high.

Because you need more than one reading to officially diagnose the disease of hypertension.

So the problem is just the finding for now.

Elevated BP.

The plan is recheck in two weeks, discuss reducing salt intake, talk about weight loss.

You don't just jump to medication on a single reading.

That's a good distinction.

Problem three.

Cysticil with occasional stress incontinence.

This is a bladder issue.

The analysis links it to her coughing.

So the plan is to start with Kegel exercises.

Simple, conservative management first.

Now, problem five is really interesting.

Stress and housing insecurity.

This isn't a medical disease in the traditional sense.

No, but it is a major health factor.

The analysis notes her son -in -law has alcohol issues.

She has financial constraints.

There's family tension.

And what's the plan for something like that?

A social work referral.

Information about Al -Anon for her daughter.

It's a holistic plan.

You can't fix the headache if you don't address the crushing stress.

The text is very clear.

That these social determinants of health belong in the assessment and plan.

I love that.

Okay.

Problem seven.

Tobacco misuse.

She smokes a pack a day for 36 years.

And the analysis notes that she is in the pre -contemplative stage of change.

What does that mean, pre -contemplative?

It means she's not ready to quit.

She's not even really thinking about quitting yet.

So what's the plan then?

Do you just nag her about it?

No, that never works.

The plan is harm reduction and preparation.

You offer lung cancer screening with a CT scan.

You do spirometry to check her lung function.

And you offer support and resources if and when she changes her mind.

You have to meet the patient where they are.

And finally, problem nine is just health maintenance.

This is the checklist.

She's 54 and she's never had a colonoscopy.

So the plan is needs a colonoscopy.

Also, gun safety is mentioned.

Store the firearm unloaded and locked up.

That is incredibly comprehensive.

It covers the acute, the chronic, the social and the preventative all in one list.

That is what a complete assessment and plan looks like.

So once you have this initial plan, how do you keep track of it over time?

The text talks about progress notes.

Right.

So if you see the patient again a month later, you write a progress note.

The format for that is SOAP.

Objective.

Objective, what the patient tells you, how are they feeling.

Objective, what you find on exam today, any new data.

Assessment, is the problem better or worse or the same.

And plan, what are we doing now?

Continue the plan, change it.

And what about the patient problem list?

How is that different?

The problem list is crucial.

It lives outside of any single note.

It's like the table of contents for the patient's entire health record.

It lists all their active and inactive problems.

And the text notes that patient MN's list includes allergy to ampicillin.

Which is vital safety information.

You don't want that buried in a note from three years ago.

It needs to be on the front page of the chart so you don't accidentally prescribe a penicillin and cause a serious reaction.

Okay, we're in the homestretch here.

We've reasoned, we've written it all down.

Now we have to talk about it.

The oral presentation.

The text uses a really great visual metaphor here.

The funnel.

That's figure 5 -3.

It's the perfect way to think about it.

Picture a big funnel.

At the top, the wide part, is clinical information.

That's everything you gathered.

The hour -long interview, the full head -to -toe exam, all the labs.

Massive amount of data.

The middle of the funnel is the clinical documentation.

Your written note.

That's organized and it's already been filtered a bit.

But the oral presentation is that tiny little spout at the bottom.

Exactly.

It is the highly distilled essence.

And this is key.

You do not just read your note out loud.

That is the cardinal sin of the oral presentation.

Okay, so what are the rules of the road here?

Box 5 -12 gives some guidelines.

First and foremost, be brief.

Three to five minutes max.

Three to five minutes.

For a complex patient like M .N., that seems impossible.

It's hard.

That's why it's a skill.

You have to learn to omit non -contributory information.

Can you give me an example of that?

Sure.

If a patient comes in for a sprained ankle, you do not need to list their entire review of systems out loud.

No headaches, no vision changes, no chest pain.

You just say the review of systems was otherwise negative.

You focus only on the ankle.

The structure is very specific too.

It is.

Number one, the opening statement.

Chief complaint plus why they are here now.

Number two, the HPI.

A chronological story.

Number three, the physical exam.

Vitals.

Plus only the pertinent positives and negatives.

And number four.

The synthesis.

You say and in summary.

And then you give that concise problem representation we practiced earlier, which leads directly into your enumerated problem list.

So that synthesis is that powerful summary statement we spent all that time crafting.

Yes.

If you nail the summary statement,

the listener, who is usually your attending doctor, knows exactly what you're thinking and what direction you're heading.

It's really an audition for your thought process.

So if we zoom all the way out, we started with this black box, this intuitive magic trick.

But what we've actually found is that it's not magic at all, is it?

Not at all.

It's a rigorous structured process.

It's about moving from that fast system one intuition to that slow system two analysis and back again.

It's organizing data by anatomy and timing.

It's building and refining those illness scripts.

It's consciously checking for errors.

And it's communicating all of that, clearly.

It turns out the magic is just a whole lot of practice and a very specific way of thinking.

And that's the good news for you, the student.

If it were magic, you couldn't learn it.

But because it's a process, you can absolutely master it.

Before we wrap up, I want to leave our listeners with a provocative thought that comes right from the text.

We've talked about how logical and structured this all is.

But the chapter also mentions that patients often have clinically unexplained symptoms, you know, fatigue, anorexia, just general malaise.

This is the real frontier.

This is the green fire truck that turns out to be a cloud.

Exactly.

So how does this rigorous logical structure that we've just spent an hour breaking down, how does it handle the ambiguity when a patient is clearly suffering but doesn't fit any known script?

And that, I think, is where the science of medicine meets the art of medicine.

When scripts fail you, you have to fall back on the relationship, on empathy, and on just persistent, humble curiosity.

You manage the suffering even if you can't name the disease yet.

That's a very humbling thought to end on.

Indeed.

Thank you so much for joining us on this deep dive into Chapter 5 of Bates.

It's been incredibly illuminating.

My pleasure.

It was great.

And to all the students and learners out there, thank you for trusting the last -minute lecture team with your study time.

Go out there, build your scripts, and watch out for those cognitive traps.

We'll see you in the next deep dive.