A parent googling their child's diagnosis at 2am is doing safety-critical information work with tools designed for billing. Most patient-facing healthcare interfaces fail families not because the information is missing, but because it arrives in the wrong form, at the wrong time, at the wrong reading level.
Treating patient education as a design problem — with users, constraints and measurable outcomes — changes what you build.
“Health literacy is not the patient's job. It is the interface's job.”
Plain language is a clinical intervention
The average adult reads comfortably at roughly an 8th-grade level; stress and fear push comprehension lower. Yet discharge instructions and portal content routinely test at college level, dense with terms that mean nothing outside the profession. Rewriting to plain language measurably improves medication adherence and reduces readmissions — it is treatment, not copywriting.
The design discipline is ruthless: one idea per sentence, active voice, "what to do" before "why", and every instruction testable by a tired reader at 2am. If a sentence cannot be acted on, it is decoration.
Timing and context beat completeness
Interfaces dump everything at once — a 14-page discharge packet, a portal wall of documents — because completeness protects the institution. But families need the right slice at the right moment: tonight's medication tonight, the warning signs this week, the lifestyle guidance later.
Progressive delivery (staged messages, checklists that unlock, short videos before appointments) consistently outperforms the packet. Design for the moment of need, and let the archive exist for the few who want it.
Design for the family, not the file
Care is a team sport: spouses manage medications, adult children manage appointments, translators bridge languages. Yet most portals model exactly one authorized user and treat everyone else as a security problem. Proxy access, shareable summaries and multilingual content are core features, not edge cases.
The test we apply to every patient-facing screen: could a frightened non-expert, seeing this for the first time, correctly answer "what is happening, what do I do next, and when should I worry?" If any answer requires a phone call, the interface has failed at its one job.
Frequently Asked Questions
Why do patient portals fail at patient education?+
Because they are built around institutional needs — records, billing, liability — rather than the patient's moment of need. Content arrives all at once, at too high a reading level, modeled for a single user instead of the family actually managing care.
What reading level should patient education content target?+
Aim for roughly a 6th–8th grade reading level, with one idea per sentence and actions stated before explanations. Stress lowers comprehension further, so content that feels "too simple" to clinicians is usually calibrated correctly for patients.
