Most medical malpractice cases are about how a doctor did the job: a mistake in surgery, a missed diagnosis, a wrong medication. But some of the most serious cases start earlier, in the conversation before the treatment ever began. The patient agreed to a procedure without being told about a risk that a reasonable person would have wanted to know, and then that risk happened.
In the District of Columbia, that is a claim of its own, called lack of informed consent. And D.C. law on it traces back to a case that changed the rule for much of the country.
The case: a 19-year-old, a back operation, and a risk no one mentioned
In 1959, Jerry Canterbury was a 19-year-old clerk-typist for the FBI with persistent pain between his shoulder blades. A Washington neurosurgeon recommended a laminectomy, an operation on the spine, to address what he suspected was a ruptured disc. Canterbury did not ask many questions. When his mother, a widow in West Virginia, called and asked whether the operation was serious, the surgeon told her it was "not anymore than any other operation."
Neither of them was told that the operation carried a risk of paralysis. At trial, the surgeon testified that paralysis could be expected in roughly one percent of these operations, and that he did not consider it good practice to mention that risk because it might scare patients away from surgery they needed.
The day after the operation, Canterbury was left alone in his hospital bed to urinate, with no one to help him and no side rail. He fell. Within hours he was paralyzed from the waist down and went back into surgery. Years later, at trial, he still walked on crutches and lived with urinary incontinence and paralysis of the bowels.
The trial judge took the case away from the jury. In Canterbury v. Spence, 464 F.2d 772 (D.C. Cir. 1972), the federal appeals court in Washington reversed and ordered a new trial against both the surgeon and the hospital. The testimony from Canterbury and his mother that the paralysis risk was never disclosed, the court held, was enough to put the question to a jury. The doctor's view that disclosure was bad practice did not defeat the claim as a matter of law.
The court's reasoning has been quoted ever since: it is "the prerogative of the patient, not the physician, to determine for himself the direction in which his interests seem to lie."
The rule in D.C. today: what a reasonable patient would want to know
A decade later, the D.C. Court of Appeals adopted Canterbury's approach for D.C. courts in Crain v. Allison, 443 A.2d 558 (D.C. 1982), and it remains the law. Earlier this year, in Pearson v. MedStar Washington Hospital Center, No. 24-CV-1187 (D.C. Feb. 19, 2026), the court restated the same framework.
Here is what that framework means in plain English.
The yardstick is the patient, not the medical profession. Some states only require doctors to disclose what other doctors customarily disclose. D.C. rejected that rule, noting how hard it is to get one doctor to testify against another. In D.C., a risk must be disclosed if a reasonable person in the patient's position would likely attach significance to it in deciding whether to go ahead.
Not every risk, but every material one. A small chance of a catastrophic outcome, like paralysis, can be material even when it is unlikely. At a minimum, the doctor must explain the condition, the proposed treatment, the alternatives, and the risks and benefits of going ahead and of doing nothing.
A signature is not the test. Hospitals use consent forms for nearly everything. But Crain says that consent obtained without the required information is "ineffective." What matters is whether the patient was actually told what a reasonable patient would need to know.
There are narrow exceptions. A doctor does not have to disclose a risk the patient already knows about. The duty also gives way in a true emergency, when the patient cannot consent, no family member is available, and waiting would cause greater harm, and in the rare case where the doctor reasonably believes the information itself would harm the patient.
What you have to prove
D.C. courts break the claim into a few questions:
| Question | What it means | Usual proof |
|---|---|---|
| Was there an undisclosed, material risk? | A risk a reasonable patient would have wanted to know about was not explained. | Your testimony and your family's, the consent form, the chart notes |
| Did that risk happen and injure you? | The harm you suffered is the very risk that went undisclosed. | Medical records and expert testimony |
| Would a reasonable patient have said no? | A prudent person in your position, fully informed, would have declined or chosen differently. | Your testimony, plus expert evidence on the alternatives |
Two details in that table matter a great deal.
First, the "would you have said no" question is judged objectively. Your own testimony counts, but the jury asks what a reasonable person in your position would have decided with the full picture. That is why the real alternatives matter so much: a different procedure, a more conservative course, a second opinion, or a different hospital.
Second, expert testimony is still required for the medical facts. A jury can decide on its own whether the doctor's explanation was reasonable. But a qualified medical expert must establish the nature and likelihood of the risk, the available alternatives, and how they compare.
Where these claims fail
Pearson shows how an informed consent claim can fall apart without that groundwork. The family argued that a hospital should have warned about the risks of a long hospital stay. The Court of Appeals affirmed judgment for the hospital and the patient's medical group. It held that a duty to disclose arises only for a treatment the provider is actually proposing, and that the family's experts never showed a safer alternative that the patient could have chosen instead. Without expert testimony comparing the risks, there was nothing for a jury to decide.
The lesson is not that these claims are weak. It is that they have to be built with the right experts from the start.
What this means if you or a family member was seriously hurt
Informed consent claims come up most often after surgery and invasive procedures, such as spinal surgery, cardiac procedures, anesthesia, and childbirth interventions, where a known but uncommon complication causes paralysis, brain injury, or death. They can also stand alongside a claim that the procedure itself was performed carelessly, as they did in Canterbury.
If you are in that situation:
- Write down what you were told, and by whom, while your memory is fresh. Include family members who were in the room or on the phone.
- Request a full copy of the chart, including the signed consent form, pre-operative notes, and any patient education materials.
- Do not assume the consent form ends the case. The question is what was actually explained, not what was signed.
- Move quickly. D.C. treats an informed consent claim as a form of medical negligence, so plan on the same timing rules that govern malpractice cases. D.C. requires written notice before most malpractice suits can be filed, and the statute of limitations keeps running in the meantime.
If the patient died, the family may have wrongful death and survival claims based on the same failure to inform. And D.C. does not cap pain and suffering damages in these cases, as we explain in our post on damages for pain and suffering in D.C.
Talk to a D.C. medical malpractice lawyer
If you or someone you love suffered a serious complication that no one warned you about, we can review what happened, what you were told, and whether the law gives you a claim. Call Posey Lebowitz at (202) 524-0123 or use our contact form for a free consultation.
This post is general information, not legal advice about your case.
Related articles
- Insurance Paid Your Medical Bills After a D.C. Injury? You Can Still Recover the Full Amount
- Hurt by a Product That Came With No Warning in D.C.? Why "Everyone Knows That" Doesn't End Your Case
- Hit by a Drunk Driver in D.C.? When the Bar That Kept Serving Them Can Be Held Responsible
- Hit by Someone Driving a Borrowed Car in D.C.? Why the Car's Owner Can Be Responsible
