Most of what happens in a clinic is one clinician, one patient, one room. That is how it should be. But the same privacy that makes care personal also means nobody else sees your reasoning. If you are drifting toward a wrong conclusion, there is no one in the room to say so.
Case conferences are our answer to that problem. Once a week, the clinical team sits down and works through a handful of cases together. This post describes what that looks like, why we do it, and what students and new graduates in particular get from it.
What a case conference is
The format is simple. A clinician presents a case: history, examination findings, working diagnosis, plan, and what has happened since. Names and identifying details are removed. The rest of the team asks questions, offers alternative explanations, and challenges the plan.
The cases are not chosen because they are dramatic. The most useful ones are usually ordinary presentations that are not behaving as expected: the shoulder that should have improved by now, the back pain with one feature that does not fit, the patient whose progress has stalled without obvious reason. Cases that went well are reviewed too, because understanding why something worked is as instructive as understanding why it did not.
We also review cases where a referral was made, to ask whether it was made at the right time, and cases where one was considered and not made, to ask whether that was correct.
What it is designed to catch
Clinical reasoning is a skill, and like any skill it has characteristic failure modes. The literature on diagnostic error has described these in detail. The most common are not knowledge gaps; they are thinking shortcuts that usually serve us well and occasionally lead us astray.1
Anchoring is settling on a diagnosis early and then interpreting everything that follows through that lens. A patient says "sciatica" in the first minute, and the clinician spends the rest of the visit confirming it rather than testing it.
Premature closure is stopping the search once a plausible explanation is found, without asking whether anything else could also explain the picture. The hamstring strain that is really a referred pain from the lumbar spine is a classic example.
Availability bias is being influenced by recent or memorable cases. If you saw a stress fracture last week, every shin pain this week looks like one.
These errors are nearly impossible to notice from inside your own head. They are relatively easy for a colleague to spot, because the colleague has not anchored, has not closed, and did not see last week's stress fracture. That asymmetry is the whole value of peer review.
How the conversation runs
There are a few rules we hold to.
- The presenting clinician leads with their uncertainty. What are you least sure about? Where does the picture not fit? Starting there makes the discussion productive rather than defensive.
- Questions before opinions. Team members ask about what was examined and what was not before offering a different view. Often the alternative explanation dissolves once a missing detail is supplied.
- Evidence gets named. If someone proposes a change in plan, they say why. Sometimes that is a guideline, sometimes a trial, sometimes clinical experience. All three are legitimate, but we try to be clear about which one is doing the work.2
- The plan is written down. Every case ends with a concrete next step: a test to add, a referral to make, a reassessment date, or a decision to continue as planned.
Disagreement is normal and welcome. The point is not consensus. The point is that the presenting clinician leaves with a sharper view of the case than they arrived with.
Why this matters for a rehab-first approach
Our model depends on accurate assessment. If we are going to tell someone that their back pain is not dangerous and that movement is the treatment, we need to be confident we have ruled out the small number of cases where that is not true.3 If we are going to build a loading program around a working diagnosis, that diagnosis needs to hold up to scrutiny.
Case conferences are also where the regional interdependence principle gets tested in practice. A colleague who asks "did you look at the hip?" when a knee case is presented is not being pedantic. They are doing exactly what we tell patients we do: looking beyond where it hurts. We have written about why reassessment matters, and the conference is where reassessment becomes a shared responsibility rather than an individual habit.
What students and new graduates take from it
For a student or new clinician, the conference does two things that are hard to get any other way.
First, it makes expert reasoning visible. Experienced clinicians often cannot articulate how they arrived at a conclusion when asked in the moment. In a conference, with time to reflect, they can. Watching someone work through a differential out loud teaches more than any textbook chapter on the same condition.
Second, it normalizes uncertainty. New graduates often believe that confident clinicians are certain clinicians. The conference shows them that the most experienced people in the room are the ones most willing to say "I'm not sure" and "I might have this wrong." That shift, from performing certainty to managing uncertainty, is the core of the transition from student to clinician.
If you are a patient wondering whether your case has been discussed, the answer is possibly yes, anonymously, and in service of getting it right. If you are a student or clinician interested in how we structure our clinical work, the overview of our practice is a reasonable starting point. We think the quality of the thinking behind a treatment plan matters as much as the plan itself, and the conference is where that thinking gets stress-tested.
References
- Croskerry P. The importance of cognitive errors in diagnosis and strategies to minimize them. Acad Med. 2003;78(8):775-780.
- Lin I, Wiles L, Waller R, et al. What does best practice care for musculoskeletal pain look like? Eleven consistent recommendations from high-quality clinical practice guidelines: systematic review. Br J Sports Med. 2020;54(2):79-86.
- Hartvigsen J, Hancock MJ, Kongsted A, et al. What low back pain is and why we need to pay attention. Lancet. 2018;391(10137):2356-2367.
