The Post-Encounter Consent Signature

Several deficiencies exist, and they compound:

1. Comprehension was not established. Reading level mismatch (3rd grade vs. 11th-grade form) is a known risk factor for non-comprehension. Verbal summary alone does not substitute for a documented teach-back or comprehension check. The coordinator cannot attest that the participant understood risks, alternatives, or the washout requirement.
2. No copy provided. Most regulations and guidance require giving the participant a copy; without it he cannot review at home or consult family.
3. No source documentation. The consent process itself must be documented (date, who conducted it, that questions were answered). Absence creates an audit finding and undermines the ability to reconstruct what happened.
4. Daughter's presence is not itself a problem - but if she was asked to interpret or explain, that is a role the form does not authorize, and it raises questions about who actually obtained consent.

Validity: The signature captures voluntariness imperfectly and comprehension not at all. The washout - an intervention with real risk - proceeded on a consent of questionable validity. The correct action is to treat this as a potential noncompliance event: notify the PI, re-consent properly with a comprehension check and an appropriate reading-level tool, provide the copy, document the process, and report per institutional and IRB timelines.

Immediate obligations:

• Do not give clinical advice. The coordinator is not the prescriber. Route the call to the PI or the participant's treating clinician the same day.
• Assess and document the adverse event. Dizziness during a washout is plausibly related to the washout (an intervention required by the protocol). Capture onset, severity, whether it meets the protocol's AE/SAE definitions, and any action taken.
• Escalate to the PI for a clinical decision about safety and whether the participant should be withdrawn or the washout modified.
• Preserve the source record - including the fact that the consent copy was not given and the discussion was not documented. Do not backdate or 'clean up' the note.

What must NOT happen:

• The coordinator must not tell him to restart or not restart his medication.
• No one should retroactively write a consent note describing a process that did not occur.
• The event should not be left undocumented because it 'was probably the washout.'

After the safety issue is handled, the consent deficiencies go through the noncompliance pathway (PI notification, corrective action, IRB reporting if required).

A defensible corrective-action plan addresses the specific failure modes rather than generic 'retraining':

1. Comprehension tooling: adopt a teach-back script and a short comprehension checklist for every consent, with a documented pass criterion. Consider a plain-language summary sheet as an IRB-approved adjunct (not a substitute) for the 11th-grade form.
2. Reading-level review: request IRB review of a lower-reading-level consent for future protocols; flag this form as a known barrier.
3. Consent checklist embedded in the visit workflow: copy provided (yes/no), discussion documented (yes/no), questions answered (yes/no), interpreter/companion role noted. This converts an honor-system process into a verifiable one.
4. Same-day documentation standard for consent encounters, with a supervisory review before the screening visit proceeds.
5. Role clarity: written guidance on when a family member may be present versus when a qualified interpreter is required.
6. Verification: a sample audit of the next N consents by the PI or designee, with results reported to the IRB as part of the corrective-action closeout.

Each element should have an owner and a due date so the IRB can evaluate closure.