From Goinvo.com by Sharon Lee, GoInvo and Jen Patel, GoInvo
We spoke to leading experts in the field and borrowed best practices on the management of patient health information (PHI) to outline an open and ethical approach for designing patient-centered, meaningful consent. The wisdom and guidance of Jane Sarasohn-Kahn, Joyce Lee, Ernesto Ramirez, Gabriel Martinez-Santibañez, Charles Schick, and Woody MacDuffie helped immensely on this journey.
What is Informed Consent?
“Informed consent: The process by which a patient learns about and understands the purpose, benefits, and potential risks of a medical or surgical intervention, including clinical trials, and then agrees to receive the treatment or participate in the trial1.”
At a baseline, meaningful consent requires2:
- comprehension, AND
Consent materials should cover both benefits and risks of participation2.
When patient health data is involved, meaningful consent should also effectively communicate3:
- how patient data will be used,
- who will have access,
- how it will be protected, and
- what rights the patient has over the shared data.
The gap in comprehension
Informed consent is especially important in medicine and health related services. Patients need to adequately weigh the pros and cons of their involvement to make the best choice for their health. Unfortunately, three issues with traditional consent can prevent patients from fully understanding what they are agreeing to.
- Consent documents are usually filled with complex legal language4.
- The consent process is usually rushed4.
- Comprehension is rarely measured. In other words, most consent processes don’t track what patients understand.
An opportunity for re-design
Pew Research Center found that 77% of Americans have smartphones as of 20186. Despite this, many patient consent processes are still filled out on paper. From a survey conducted in 2017 with 146 respondents from top biotech, pharma, CRO, and IRB organizations, 53% reported their organizations still didn’t use electronic consent7.
Paper consent often requires extra steps of downloading PDFs, printing, signing in separate software, and then scanning, mailing, or emailing it in. A mobile consent process allows patients to work through consent whenever and wherever they want2. It allows them to complete the consent process in their own time, supports the patients’ future reference of the agreement, and can allow patients to manage or revoke their consent as the terms allow.
As researchers, healthcare providers, and healthcare companies shift to eConsent, a few researchers have explored best practices for their design. Groups, including Sage BioNetworks and AllofUs, are pushing the needle away from lengthy, complex terms and conditions and towards truly meaningful consent.
We hope that this list of guidelines to improve patient comprehension can help to inform eConsent design.
9 Guidelines for eConsent Design
1. Meet Accessibility Standards
At the most basic level, the consent process must meet the needs of those with disabilities (see WCAG2.1 guidelines).
2. Make Consent Front and Center
The gateway to involvement in the Resilience Project is a 10 minute screening + consent process (Goinvo designs with Mount Sinai and Sage Bionetworks from 2015).
3. Use Plain, Concise Language
Legalese can sound like a foreign language to patients. Plain, concise language can be read quickly and understood, making it more accessible8. Plain language should be at or below a 5th grade reading level in order to support the comprehension of those with low literacy9.
4. Set Time Expectations
Consent can feel like an endless stream of content. Cue patients in on how long it will take them through a comment at the start, a progress bar, or other. This allows patients to evaluate whether they currently have enough time to complete the consent process and can help prevent patients from rushing to the end.
5. Organize Content into Bite-sized Sections
In a “novel multi-media approach to addressing transparency and comprehension within electronic informed consent,” Sage Bionetworks suggest focussing on the essential and organizing content deliberately10. Breaking the consent document into bite-sized, topic-focused chunks can help the participant better grasp the sections. Keeping content succinct can help prevent the reader from skimming.
6. Use Visual Storytelling
Humans are visual and aural communicators. Adding straight forward icons, illustrations, animations, or even videos can help to engage the reader. Visuals serve as a memorable indicator of topic that can help bolster understanding10. One research group found that using friendly comic strip visuals improved “patient comprehension, anxiety, and satisfaction11.”
7. Provide Real-Time Help
Supporting comprehension takes more than just clear wording and accessibility. It means providing help and resources to patients when and where they need it. Resources and support can take many forms such as a ‘Learn More’ or ‘Help’ button, a support chat, a toll-free phone number with a helpful human resource on the other end, and more10.
8. Use “Repeat Back” to Engage the Brain
The National Quality Forum developed an approach called Safe Practice 10 with in-person patient consent to improve comprehension. Part of this practice includes a “teach back” or “repeat back” technique where the patient is asked to recall primary details from consent that has just been discussed with them. Multiple studies have found that having the patient recall the information improves comprehension12. Similarly with eConsent, a short quiz can help engage the patient’s mind in a new way and help them retain the major takeaways of the agreement.
Bonus: 9. Keep Measuring + Iterating!
There is always room for improvement in consent design. Before releasing the consent process, set lofty goals for your designs and test them with representative users. Are users able to answer questions on the primary consent take-aways after going through the process? After releasing your consent process, are there systems in place to continue receiving feedback and measuring comprehension?