Consent Is a Process, Not a Document

Part of Consent and Vulnerable Populations: What Consent Actually Is.

About 6 minutes. Free, in your language, no account needed.

Why this matters

Ask most people in clinical research what informed consent is and they will describe a form. It has sections, it gets approved by an ethics committee, the participant signs it, and it goes in the file.

That description is of the evidence of consent, not of consent. The form records that a process happened. If the process did not happen, the form records something untrue, and a signed form is exactly as complete either way.

Understanding this distinction is the difference between a consent process that protects participants and one that protects paperwork.

What consent actually requires

Three things, all of which must be true at the moment of agreement.

The person understands what they are agreeing to. Not that they were told. That they understood. These come apart constantly, and the gap is where most consent failures live.

The agreement is voluntary. Free from coercion and from undue influence, which is a broader category and includes an inducement large enough to distort judgment, and a dependent relationship in which refusal feels costly.

The person has the capacity to make this decision. The ability, right now, to understand, retain, weigh and communicate a choice about this particular question.

Remove any one and the signature means nothing, whatever the form says.

Why the form is the wrong focus

The document is necessary and it does specific, limited work: it records what the participant was told, it provides something to refer back to, and it evidences that the process occurred.

What it cannot do is establish that anyone understood anything. A 22-page form written at postgraduate reading level, handed to a participant in a waiting room, produces a signature and no understanding, and the file is indistinguishable from one where a clinician spent an hour in conversation.

Ethics committees scrutinize consent forms more closely than any other document precisely because the form is what they can see. That is a real limitation of the mechanism, and everyone working in the field should know it: the committee is reviewing the only artifact available to it, and the artifact is not the thing that matters most.

What the process looks like

Information given in a form the person can use, which means their language, their reading level, and enough time. A form translated correctly into a language the participant reads poorly is not information they can use.

An opportunity to ask questions, and the conditions that make asking feel possible. Many people will not ask a doctor a question in a room where the doctor is standing and they are on an examination table.

Time to consider, proportionate to the decision. A trial with serious risks and no urgency should not be consented in the same visit it is introduced.

A check on understanding. Not "do you have any questions," which almost always produces "no," but asking the person to describe in their own words what will happen and what the main risks are.

Documentation that the above occurred, with a date and the identity of the person who conducted it.

Continuation. Consent is not a moment. A participant may withdraw at any time, and new information that might affect their willingness must reach them.

The standing of the proposed competencies

CRLN-TRG-001 currently carries four informed consent competencies across four role tracks, and every one of them assumes a competent adult consenting for themselves.

A proposal exists to add competencies covering consent by a legal representative, assent and consent for minors, deferred and emergency consent, cluster and simplified consent, community engagement, and permission for secondary use of existing data.

That proposal is not adopted. The Methodology Review Board has one seated member and has not reached quorum, so no released version of the standard contains these competencies.

This module therefore teaches from the primary sources directly: Regulation (EU) No 536/2014 for the consent situations it addresses, the TDR Global Competency Framework for community engagement, and ICH E6(R3) for the general expectations. Where a jurisdiction's own law governs, it governs, and the module says so rather than implying a settled global answer.

In practice

A coordinator consents a participant for an oncology trial. The form is approved, the signature and date are correct, and the file is complete.

Two weeks later the participant asks the research nurse when the treatment will start working, and whether it is the same drug their oncologist mentioned.

The trial is randomized, placebo-controlled, and the participant has a 50 percent chance of receiving no active treatment. This is stated in the form, on page four, and the participant did not understand it.

Nothing in the file will ever show this. The consent process was documented perfectly and it did not achieve what consent exists to achieve, and the only reason anybody knows is that the participant happened to ask a question.

A single teach-back question at consent, asking the participant to describe what they will receive, would have surfaced it in thirty seconds.

What this looks like when it goes wrong

A site consents participants using an approved form in the local language. The form is a competent translation of the English original.

The population includes a substantial number of people with limited literacy, and the site's process is to hand the form over and ask them to read it and sign.

Participants sign. They are not refusing, they are not being deceived, and they have not been informed, because the mechanism of information transfer assumed a reading ability many of them do not have.

The file is complete. Every signature is genuine. An audit of consent documentation finds nothing, because documentation is not what failed.

Key takeaways