To govern ambient AI recording and scribe tools in ABA services, define the clinical purpose, people and environment captured, authority, consent and assent when applicable, dissent and stop signals, AAC access, vendor data flow, audio retention, and alternatives before activation. Keep transcript and note output draft, require attributable review, limit reuse, and test deletion. Ambient capture never becomes a condition of receiving ordinary care.

Define Mateo's ambient capture and scribe release file

Mateo treats ambient capture as both a media operation and an AI drafting workflow. The microphone may collect the client, family, staff, other people, television, device speech, home details, and information outside the clinical purpose. The unit identifies approved use, client and event, source records, model and version, vendor, user and accountable author, output state, reviewer, downstream use, exception, and evidence needed for release or closure.

Build Mateo's page-specific control record

Mateo records approved scenario, client and encounter, participants, setting and bystanders, purpose, authority, consent and assent process, dissent and stop response, alternative, AAC and backup, device and microphone state, activation cue, audio and transcript flow, vendor and subcontractor, model and version, storage and retention, training or improvement setting, draft output, author review, speaker attribution, uncertainty, redaction, access, disclosure, deletion, incident, correction, and monitoring. The record states when capture actually began and ended.

Put Mateo's human-review boundary into practice

Mateo uses a visible and audible activation routine that works for the client's communication needs. Participants learn how to pause or stop, and staff honor withdrawal in nonemergency use. The session continues through a documented alternative when capture is declined. The device interface makes microphone state obvious and prevents accidental background operation. Afterward, the author checks speaker attribution, client communication, clinical facts, dates, and omitted events against independent notes or memory while still timely. Audio is not retained by default merely because the vendor offers storage. Every retained copy has a purpose, access rule, retention trigger, and deletion test. Mateo reviews whether ambient use changes client comfort, communication, staff attention, family participation, or note accuracy. Vendor changes, model updates, new settings, new languages, or an incident reopen approval. No excerpt enters staff training, marketing, or model improvement through an assumed clinical authorization.

Protect client communication and ordinary access for Mateo

Mateo preserves the client's direct communication, AAC, language and disability access, consent and assent when applicable, dissent, health, safety, privacy, priorities, and correction route. AI use never makes communication, food, water, bathroom access, mobility, prescribed care, rest, or emergency help conditional on tool participation or task performance.

Work through Mateo's fictional example

Mateo reviews 16 proposed uses. Eleven clear all gates. Two clients choose the nonrecorded option, one home setting contains an uninvolved person, one vendor retention term is unclear, and one AAC voice is assigned to the wrong speaker in testing. The cohort teaches AI governance and denominator discipline. It does not establish treatment effect, model safety, legal compliance, coding correctness, payer acceptance, accessibility, or product performance.

Keep Mateo's denominator tied to the locked population

Release readiness is 11 of 16 proposed uses, or 68.8%. Declined uses are valid choices, not failures. Draft accuracy, speaker attribution, deletion completion, and client experience use separate denominators.

Assign Mateo's decisions to accountable people

Clients communicate choice and dissent. Legally authorized people act only within scope. Qualified clinicians decide clinical need and author records. Privacy, legal, security, and procurement leaders govern data. Vendors process only within approved terms.

Address Mateo's main AI documentation risk

A quiet ambient tool can become invisible surveillance. Make activation, purpose, stop, retention, and alternatives understandable every time.

Test Mateo's workflow with difficult cases

Mateo tests decline, withdrawal, AAC speech, two speakers, bystander, home background, telehealth, device sleep, network loss, retained audio, deletion, model update, and released-note correction.

Check Mateo's release evidence

Mateo confirms the exact source set and versions, client and encounter, model and configuration, approved data route, generated draft, material edits, author and reviewer decisions, accessible client communication, release destination, correction path, monitoring cohort, and known limitations. The ambient capture and scribe release file retains unresolved work, owner, deadline, downstream trace, and the next revalidation trigger.

Use Mateo's ABA governance sources within their scope

Mateo uses the CASP public overview only for high-level organizational context. The BACB Ethics Code applies to BCBA and BCaBA certificants and applicants as defined by the Code; BACB has no separate jurisdiction over organizations or corporations. These sources support competence, documentation, confidentiality, client involvement, assessment, intervention, risk, supervision, and correction boundaries. They do not approve a tool or transfer clinical authority to software.

Keep Mateo's source record and medical-review boundary visible

Mateo uses current CMS Program Integrity Manual Chapter 3 as Medicare medical-review guidance. It currently says services are expected to be documented when rendered; delayed or corrected entries may occur; date and author should be identifiable; and changes or addenda clearly and permanently noted. AI output cannot supply facts that were not documented, and Medicare guidance does not become a universal payer, state, or AI rule.

Map Mateo's privacy, security, and vendor roles

Mateo uses the current HHS Security Rule overview, HHS cloud guidance, and HHS business-associate guidance to analyze actual covered-entity, business-associate, subcontractor, cloud, and security roles. A BAA or vendor certification does not complete purpose, permissible-use, minimum-data, configuration, risk analysis, access, incident, retention, and shared-responsibility work.

Use Mateo's AI frameworks as voluntary risk tools

Mateo treats the NIST AI Risk Management Framework and NIST Generative AI Profile as voluntary risk-management resources, not clinical, legal, coding, or payer authority. The profile helps teams examine generative-AI risks and actions. A framework, score, benchmark, or vendor evaluation does not prove safety, accuracy, fairness, accessibility, compliance, or fitness for this ABA use.

Protect Mateo's data-purpose and communication boundaries

Mateo uses HHS de-identification guidance for its two HIPAA methods and residual-risk boundary. Calling output synthetic or removing names is not itself a method. FTC staff guidance warns AI companies to honor privacy and confidentiality commitments. The OIG GCPG is voluntary and nonbinding. ASHA's AAC portal says AAC users should always have access to their tools or devices.

Choose Mateo's next review trigger

Mateo reopens the ambient capture and scribe release file after a model, prompt, retrieval, source, template, vendor, subprocessor, setting, language, client communication method, access role, data term, payer rule, incident, complaint, correction, audit finding, or regulation changes. The review records affected people and records, immediate safeguard, owner, deadline, communication, correction, downstream propagation, and validation.

Close Mateo's workflow without hiding uncertainty

Review the ambient capture and scribe release file with affected clients and authorized people, qualified clinicians, health-information, privacy, security, AI-governance, accessibility, language, payer, coding, and technical leaders, and the specialists named in the manifest. Confirm source support, authorship, authority, client access, model provenance, vendor terms, errors, downstream use, correction, and independent validation. Keep this page draft and noindex until every required external review is complete.

Related resources

Sources