Skip to content

Informed Consent Governance

Ensure agreement is informed, voluntary, specific, revocable where appropriate, and granted by someone with authority to consent.

The Diagnostic Story

Symptom: The system treats assent as consent even though the person had no real option to refuse, could not understand what they were agreeing to, or was not actually the one with authority to grant permission. Scope keeps expanding beyond what was originally agreed, and no workable path to withdraw exists once the agreement is on record.

Pivot: Separate the components that make permission meaningful: who has authority to consent, what material information must be disclosed and understood, whether refusal is genuinely available, what scope and duration are covered, and how the consent state can be revised or withdrawn.

Resolution: Permissions are meaningful, traceable, and specific. Disputes drop because scope and conditions were documented rather than inferred. The system can show, for any action taken, what permission covered it and how that permission was obtained.

Reach for this when you hear…

[clinical research] “Signing the form is not the same as consenting — if the patient could not have said no without losing care, that is not voluntary.”

[platform governance] “We have checkbox consent for everything and meaningful consent for nothing — our terms grant us the right to do things people never actually agreed to.”

[enterprise data] “The original approval covered that use case, not this one — we need to go back and get explicit permission or we are operating outside our authorization.”

Mechanisms / Implementations

  • Consent Form (consent_form):: Captures disclosure, agreement, scope, signature or acknowledgement, and often the record of authorization.
  • Opt-In Flow (opt_in_flow):: Presents a permission request before a user enters a feature, data use, program, or relationship that requires affirmative agreement.
  • Informed Consent Conversation (informed_consent_conversation):: Uses dialogue, question-and-answer, teach-back, and deliberation to establish understanding before agreement.
  • Data Consent Settings (data_consent_settings):: Lets users grant, narrow, revoke, or inspect data permissions at different levels of granularity.
  • Research Consent Protocol (research_consent_protocol):: Structures participant disclosure, voluntary enrollment, scope, withdrawal, recordkeeping, and continuing review for research participation.
  • Withdrawal Procedure (withdrawal_procedure):: Operationalizes refusal, revocation, narrowing, opt-out, deletion, stopping participation, or review of existing permission.
  • Assent / Consent Distinction (assent_consent_distinction):: Differentiates affirmative participation by a person from legally or institutionally authorized consent by a guardian, representative, or accountable actor.
  • Plain-Language Disclosure (plain_language_disclosure):: Provides layered, accessible, and decision-relevant explanation of material information.
  • Granular Permission Dashboard (granular_permission_dashboard):: Shows separate permissions, purposes, actors, and revocation controls in a single reviewable place.
  • Consent Renewal Prompt (consent_renewal_prompt):: Requests renewed agreement when purpose, risk, duration, actor, or context changes materially.

Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.

Built directly on (2)

Also references 7 related abstractions

Variants

Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.

Granular Consent Governance · implementation variant · recognized

A consent-governance variant that breaks permission into separable purposes, actors, durations, or data/action categories instead of asking for one blanket approval.

Dynamic or Ongoing Consent · temporal variant · recognized

A consent-governance variant that treats permission as a maintained relationship requiring updates, reminders, renewal, and revocation over time.

Proxy or Representative Consent · governance variant · recognized

A consent-governance variant for cases where permission is granted by an authorized representative, guardian, delegate, or collective decision process.

Assent Plus Authorized Consent · governance variant · candidate

A narrower variant in which an affected party’s affirmative participation is sought alongside formal consent from an authorized actor.