I work on both sides of this line — regulated plain-language summaries for trial sponsors, and patient education for clinics. The regulated side is not better written. It is better checked, and one specific check accounts for most of the difference.
The expectation almost nobody outside pharma has heard of
Article 37 of the EU Clinical Trials Regulation requires sponsors to publish a lay summary of results for trials in the EU database, and Annex V sets out the essential content those summaries must carry.
The accompanying Good Lay Summary Practice guidance goes further than content. It addresses sentence structure, layout, use of graphics, accessibility and inclusivity — and it describes testing the summary with lay readers before publication.
That last element is the one that rarely crosses over into clinic patient education, and it is the one doing the most work.
What user testing actually involves
It is less elaborate than the phrase suggests. You give the draft to people who resemble the intended readers, ask them to find specific information in it, and record where they fail.
The value is not in their opinion of the document. Readers are poor judges of what they understood, and asking ‘was that clear?’ reliably produces a polite yes. The value is in watching someone hunt for the dosing instruction and not find it.
Failures cluster in predictable places: the action buried below the explanation, the term introduced before it is defined, the warning sign phrased as a clinical category, and the number that requires arithmetic the reader will not perform.
Why clinics skip it
Because nobody requires it, and because it looks like a research activity rather than a clinical one. There is no regulator asking a family practice whether its diabetes handout was tested on anyone with diabetes.
There is also a quiet assumption that clinical expertise implies communicative clarity. It does not. Knowing a subject deeply makes it harder, not easier, to notice which parts are unfamiliar to someone encountering them for the first time.
That is not a criticism of clinicians. It is a well-described property of expertise, and the only reliable correction is to watch a non-expert try to use what you wrote.
A version a small practice can actually run
Take one document. Find five people who are not clinicians — reception staff count, family members count. Give them the page and three tasks drawn from what a real patient would need: what do I take, when do I stop, what sends me to hospital.
Time them and note failures rather than opinions. Five readers will surface most of the serious problems, and the whole exercise takes under an hour.
Then fix only what more than one person got wrong. Single failures are noise; repeated failures are structure.
What it changes
The first time a practice does this, the usual reaction is mild alarm. Documents that have been in circulation for years turn out to hide the one instruction that mattered.
That is the point. It converts patient education from something judged on how it looks to something judged on whether it works, which is the same shift that regulated lay summaries were forced to make.
Clinics do not need the regulation to get the benefit. They need one hour and five people who are willing to say they could not find the answer.
References used in drafting
EU Clinical Trials Regulation 536/2014 Article 37 and Annex V, together with the European Commission’s Good Lay Summary Practice guidance on preparing, testing and publishing summaries of clinical trial results for laypersons, informed the description of regulatory expectations.
General usability-testing practice, including the convention that a small number of readers surfaces the majority of serious findings, informed the suggested five-reader exercise.
