The 60-Second Patient Summary
Rounds compress complexity.
You may have spent thirty minutes reviewing the chart, speaking with the patient, checking overnight events, looking at laboratory results, and trying to understand what changed.
Then someone asks for the quick version.
That request is harder than it sounds.
A strong 60-second summary requires you to decide which facts deserve to survive compression. It also requires you to show your interpretation rather than recite the chart.
The skill is clinical reasoning in spoken form.
What the team needs from a short summary
A short presentation should help the listener answer four questions.
Who is this patient?
What changed?
What do you think is happening?
What should happen next?
The summary should orient the team quickly enough that the assessment and plan make sense.
That means the best summary is rarely the one with the most information.
It is the one with the highest signal.
Compression exposes whether you understand the case
Long presentations can hide weak organization.
You can include every detail and still leave the listener unsure what matters.
A 60-second summary removes that hiding place.
You have to choose.
Which diagnosis is driving the admission?
Which problem changed overnight?
Which laboratory trend matters?
Which negative finding changes risk?
Which issue still needs a decision?
If you cannot decide what belongs in the summary, the problem may be upstream in your own mental model.
That is why this exercise is useful even when no one formally asks for a one-minute presentation.
Use the SNAP structure
The original DDQX framework for this skill used the SNAP structure:
Summary Statement → Narrative Arc → Assessment → Plan
It is simple enough to remember under pressure and broad enough to adapt to different services.
Summary Statement
Begin with a one- or two-sentence clinical headline.
Include the patient’s relevant background, the reason for admission, and the active problem.
For example:
“Sixty-two-year-old with heart failure with reduced ejection fraction admitted for progressive dyspnea and volume overload, now improving after IV diuresis.”
That gives the listener a working model before the details begin.
Narrative Arc
Explain what changed.
The goal is not to replay the entire hospitalization.
Focus on the trajectory.
What happened overnight?
What is better?
What is worse?
What new information matters?
A useful narrative might include improving oxygen needs, persistent hypotension, rising creatinine, new fever, or a change in symptoms.
The narrative arc should make the current decision obvious.
Assessment
State what you think.
If the patient is improving, say what evidence supports that conclusion.
If a new problem is emerging, name it.
If the diagnosis remains uncertain, identify the leading explanation and the important alternative.
This is where the team hears your reasoning.
Plan
Finish with what should happen next.
The plan can include treatment, monitoring, a diagnostic step, a disposition issue, or a contingency.
A good plan also signals what you are watching.
“We will continue diuresis today, hold further beta-blocker titration while the pressure remains borderline, and trend renal function.”
That is more useful than a list of unrelated orders.
Connect SNAP with the 5P Approach™ to Clinical Reasoning
The 5P Approach™ to Clinical Reasoning explains the cognitive work underneath a strong summary.
Prioritize determines which facts belong.
Paraphrase creates the problem representation.
Prognose helps you anticipate what should happen next.
Pick turns that prediction into a recommendation.
Post-Mortem helps you compare your summary and plan with what ultimately happened.
The frameworks operate at different levels.
SNAP organizes the spoken presentation.
The 5P Approach™ organizes the reasoning that makes the presentation worth hearing.
Make the summary problem-oriented
Hospitalized patients often have several active problems.
A short summary should still have an organizing center.
If the patient was admitted for heart failure and now develops fever and hypotension, the summary should reflect that change rather than continuing to lead with yesterday’s problem.
Likewise, a stable chronic diagnosis should not take the same space as the issue controlling today’s decision.
Ask:
Which problem changes what the team needs to do now?
That problem deserves more attention.
Use trends rather than isolated numbers
Short summaries become cluttered when every laboratory value is recited.
Use trends when the trend is what matters.
“Creatinine rose from 1.0 to 1.5 after aggressive diuresis” communicates more than listing two basic metabolic panels.
“Oxygen requirement decreased from four liters to room air overnight” communicates trajectory.
“Weight is down two kilograms and edema is improving” communicates response.
Numbers deserve space when they change interpretation or management.
Do not hide uncertainty
A concise summary should not become falsely definitive.
If the clinical picture is mixed, say so.
For example:
“Volume status is improving, but the new hypotension and creatinine rise make me concerned we may be reaching the limit of further diuresis today.”
That statement tells the team where the uncertainty lives.
It also creates a natural transition into the plan.
Leave out details that do not change the decision
The hardest part of a short presentation is omission.
You may have worked hard to obtain a detail.
That effort does not guarantee the detail belongs in the summary.
Ask what would change if the information were removed.
If the listener would interpret the case the same way, the detail may belong elsewhere in the full presentation.
This is clinical Signal vs Noise applied to communication.
The 60-second summary is different from the one-liner
A one-liner is the compressed problem representation.
A 60-second summary is larger.
It includes the one-liner, the recent clinical trajectory, your current assessment, and the next step.
The one-liner tells the team what kind of patient this is.
The 60-second summary tells the team what is happening now.
Both depend on prioritization.
Prepare the summary before rounds
Do not wait until someone asks.
Before rounds, write four lines.
- Summary statement
- What changed
- What I think
- What I recommend
Then say it out loud once.
Speaking reveals clutter that looks reasonable on paper.
You will hear where the sentence is too long, where the chronology is unclear, or where you have not committed to an assessment.
The goal is not memorization.
It is organization.
Adapt the length to the setting
Sixty seconds is a useful training constraint.
Clinical communication still has to match the situation.
A new admission may require more context.
A stable follow-up patient may require less.
An acutely deteriorating patient needs a faster, more direct communication focused on the change and the immediate concern.
The skill is knowing how much information the listener needs for the decision in front of them.
A practical before-rounds checklist
Before you present, ask:
- Can I state the active problem in one sentence?
- Do I know what changed overnight?
- Can I explain whether the patient is better, worse, or unchanged?
- Do I have a prioritized assessment?
- Can I name the next step?
- Is there one contingency I need the team to hear?
If one of those answers is unclear, spend another minute on the case before rounds.
Practice without scripting
A summary should sound like you understand the patient.
Reading a memorized paragraph can sound polished while becoming brittle the moment someone interrupts.
Practice the structure.
Know the clinical story.
Then speak from the model.
This makes it easier to answer follow-up questions because you are not trying to recover your place in a script.
Use feedback at the level of the summary
Ask for narrow feedback.
“Was my summary too detailed?”
“Did I make the assessment clear enough?”
“Which part could I have omitted?”
“Did I get to the current problem fast enough?”
These questions are easier to answer than “How was my presentation?”
Then change one behavior on the next patient.
The standard
A strong 60-second patient summary helps the team understand your brain quickly.
It shows what you noticed.
It shows what you think changed.
It shows what you believe is happening.
It shows what you think should happen next.
That is why brevity can be a sophisticated clinical skill.
You are not merely speaking faster.
You are deciding what matters.
Next step: Build a SNAP summary for one patient before rounds, then use the 5P Approach™ to Clinical Reasoning to examine whether the quality of your summary reflects the quality of your underlying reasoning.
