Build an ABA Consent and Assent Source Record

To build an ABA consent and assent source record, identify the exact service or decision, governing source, person legally authorized to consent, and client participation. Preserve accessible information, material risks, expected benefits, alternatives, questions, consent and assent states, document versions, signatures or other evidence, refusal or withdrawal, effective period, linked records, corrections, and owner. Keep every decision attributable and time bounded.

Define Mara's consent and assent source record

Mara creates one source record for each consent decision and links every derivative form, plan, signature page, discussion note, and electronic event. The record shows what information the decision-maker actually received. The record identifies the decision, governing source, people, authority, accessible information, response, version, effective period, release gate, correction path, and evidence required before closure.

Build Mara's page-specific fields

Mara records client, decision, governing source, required consent type, legally authorized person and verification, client communication and AAC, interpreter and access, materials and version, service or procedure, purpose, benefits, risks, alternatives, voluntary nature, questions and responses, understanding check, consent state, assent applicability and signals, dissent, signer and method, dates, effective period, copies delivered, restrictions, withdrawal route, linked plan, staff release gate, correction, and recheck trigger.

Separate consent, assent, and related evidence for Mara

Mara labels treatment consent, client assent, dissent, HIPAA authorization, payer authorization, order, referral, service agreement, financial agreement, recording permission, privacy notice, acknowledgment, and clinical recommendation separately. Each has its own authority, scope, version, date, effect, and change path. A signature receives only the meaning supported by the governing source and presented document.

Preserve refusal and withdrawal in Mara's record

Mara provides an accessible way to ask, decline, pause, revoke, withdraw assent, or correct the record. The response identifies the exact permission affected, prospective effect, immediate safety and continuity needs, actions already taken, notifications, and follow-up. Pressure, retaliation, loss of ordinary supports, and deceptive delay trigger escalation and review.

Connect Mara's evidence to the actual event

Mara checks that the active authority, version, scope, setting, procedure, person, date, and restrictions match the planned service, disclosure, recording, or other event. A dashboard status cannot replace source evidence. Mismatches pause only the affected event while responsible roles address safe continuity and required communication.

Correct Mara's source and downstream records

Mara preserves original content, author, date, evidence, and reason for an addendum or correction. The owner identifies plans, schedules, service notes, disclosures, payer submissions, recordings, client copies, staff instructions, and system gates affected by the error. Reconciliation remains open until every material use reflects the authorized state.

Work through Mara's fictional example

Mara locks 18 source records. Thirteen connect authority, accessible information, version, decision, evidence, assent state, effective period, and linked service. One lacks AAC, one uses an outdated form, one has unclear authority, one records a signature without discussion, and one omits withdrawal. Four repair; the authority question stays held. The scenario is synthetic. It tests authority, access, version, scope, response, and denominator logic without establishing legal compliance, valid consent, valid assent, clinical quality, payer approval, client satisfaction, or outcome.

Calculate Mara's measures honestly

Initial source-record readiness is 13 of 18, or 72.2%. Seventeen validate, or 94.4%. People, decisions, forms, discussions, signatures, assent observations, and services retain separate counts.

Address Mara's main documentation risk

A complete signature page can hide the wrong version or decision. Mara ties the evidence to the presented content, participant, authority, and date.

Test Mara's record against hard cases

Mara tests initial service, optional procedure, plan change, interpreter, AAC, remote signature, limited authority, refusal, revocation, expired form, and corrected record. Each case states the governing decision, authority, accessible process, client response, version, release or stop rule, correction route, and closure evidence.

Close Mara's decision with limits visible

Mara confirms governing source, authority, access, client communication, consent and assent states, version, scope, dates, evidence, refusal or revocation, reconsent trigger, linked events, corrections, and unresolved work. The consent and assent source record remains draft until every named reviewer completes the required review.

Scope Mara's consent record within organizational guidance

Mara uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. The CASP ABA Practice Guidelines public summary concerns ABA behavioral health treatment for people diagnosed with autism. CASP sells the detailed guidance. Neither public page supplies this consent and assent source record or determines authority for a defined ABA service or procedure.

Use Mara's professional ethics source precisely

The BACB Ethics Code applies to covered people and addresses understandable communication, client and stakeholder involvement, required informed consent, assent when applicable, documentation, risk, and evaluation. BACB has no separate organization or corporation jurisdiction. Mara records the covered person's duty while preserving every additional law, license, payer, contract, and organizational requirement.

Keep HIPAA consent and authorization distinct for Mara

HHS consent-versus-authorization guidance explains that HIPAA permits a covered entity to use an optional consent process for treatment, payment, and healthcare operations. A HIPAA authorization is a detailed permission required for uses or disclosures that the Privacy Rule otherwise does not permit. It has specified elements and generally cannot be a condition of treatment or coverage except in limited circumstances. Mara keeps this privacy decision separate from consent to care.

Verify Mara's personal-representative scope

HHS personal-representative guidance explains that applicable law determines who acts and how far the authority extends. It addresses limited authority, minors, and abuse, neglect, or endangerment exceptions. Mara's record identifies the actual decision, jurisdiction, source, restrictions, and qualified review rather than using a permanent family or guardian label.

Apply the authorization rule only where Mara needs it

45 CFR 164.508 contains the Privacy Rule's authorization requirements, including core elements, required statements, compound-authorization rules, conditioning limits, revocation, and documentation. It governs HIPAA authorizations, not every clinical consent or assent process. The consent and assent source record names which permission applies and avoids copying the authorization structure onto unrelated decisions.

Use electronic-consent guidance within its published scope

HHS and FDA electronic informed-consent guidance concerns research consent under the Common Rule and FDA regulations. It also explains that electronic HIPAA research authorizations can be used when the electronic signature is valid under applicable law and the signed authorization copy is provided. Mara treats that as scoped evidence, not a universal rule for ABA service consent, and verifies every applicable electronic-signature and healthcare-consent source.

Make Mara's decision process accessible

For covered public accommodations, the DOJ Title III overview addresses equal opportunity, effective communication, reasonable modifications, and physical access subject to the law's standards. The ASHA AAC portal says AAC users should always have access to their communication tools or devices. Mara prepares usable materials, communication, time, alternatives, and an accessible response before seeking a decision.