Respond to an AI Documentation Error or Hallucination in ABA Records

Define Sol's AI documentation integrity incident file

Sol treats the released record as the starting point for impact, while preserving the complete AI workflow for cause analysis. The word hallucination never replaces a precise description of what was wrong. 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 Sol's page-specific control record

Sol records detection, reporter, client and encounter, immediate safety and clinical action, source records and versions, model and deployment, prompt and retrieval, generated output, author edits and review, released record, error class and exact statement, confidence feature, affected people, records, plans, messages, disclosures, payer packages, codes, claims and payments, privacy or security event, containment, population query, author correction, qualified clinical reassessment, recipient notice, refund or reporting route, root condition, corrective action, validation, monitoring, and closure. Original content remains in the audit history.

Put Sol's human-review boundary into practice

Sol freezes the affected template, model version, or use case when continued release could cause harm. Clinicians receive the accurate source facts needed for safe care while the investigation continues. The team queries the full exposure population using model, prompt, source, date, reviewer, and output patterns rather than checking one record. Authors correct final records under the practice's policy and do not edit source facts to match the generated text. Qualified clinicians reassess plans or decisions that relied on the error. Privacy, security, payer, coding, billing, legal, and compliance owners evaluate their own consequences and clocks. Known recipients receive a traceable correction where required. Root analysis tests source retrieval, prompt design, model behavior, interface, human review, workload, and release gates. A warning banner or retraining session cannot close the issue until sampled source and downstream records validate. Sol monitors the repaired path and adjacent uses for recurrence.

Protect client communication and ordinary access for Sol

Sol 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 Sol's fictional example

Sol investigates 12 released records from one prompt version. Seven are correct. Three omit dissent, one invents caregiver agreement, and one carries another client's goal. Five records, two plans, one payer packet, and one family summary require correction. 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 Sol's denominator tied to the locked population

Affected-record rate is 5 of 12, or 41.7%. Downstream correction uses every known affected object due for repair. Incident closure requires all critical objects validated, while lower-risk open work remains aged and visible.

Assign Sol's decisions to accountable people

Authors correct records. Qualified clinicians reassess care. Privacy, security, payer, coding, billing, legal, and compliance roles decide within their domains. Technical teams preserve and contain. The model does not explain its own root cause authoritatively.

Address Sol's main AI documentation risk

Focusing on one dramatic invention can miss systematic omissions across many records. Search both wrong statements and absent required evidence.

Test Sol's workflow with difficult cases

Sol tests population discovery, wrong client, omission, distortion, stale source, calculation, released and held drafts, downstream plans, disclosures, claims, correction notice, model change, and recurrence.

Check Sol's release evidence

Sol 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 AI documentation integrity incident file retains unresolved work, owner, deadline, downstream trace, and the next revalidation trigger.

Use Sol's ABA governance sources within their scope

Sol 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 Sol's source record and medical-review boundary visible

Sol 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 Sol's privacy, security, and vendor roles

Sol 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 Sol's AI frameworks as voluntary risk tools

Sol 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 Sol's data-purpose and communication boundaries

Sol 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 Sol's next review trigger

Sol reopens the AI documentation integrity incident 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 Sol's workflow without hiding uncertainty

Review the AI documentation integrity incident 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

• Audit an AI-Assisted ABA Clinical Documentation System.
• Control Vendor Model-Training and Secondary-Use Rights for ABA Clinical Data.
• Govern Speech-to-Text Dictation in ABA Clinical Documentation.
• Log AI Model, Prompt, Source, Output, and Reviewer Provenance for ABA Documentation.

Sources

• Council of Autism Service Providers, Organizational Guidelines public overview.
• Behavior Analyst Certification Board, Ethics Code for Behavior Analysts.
• Centers for Medicare & Medicaid Services, Medicare Program Integrity Manual, Chapter 3.
• U.S. Department of Health and Human Services, HIPAA Security Rule.
• U.S. Department of Health and Human Services, Guidance on HIPAA and Cloud Computing.
• U.S. Department of Health and Human Services, Business Associates.
• U.S. Department of Health and Human Services, Guidance Regarding Methods for De-identification of Protected Health Information.
• National Institute of Standards and Technology, AI Risk Management Framework.
• National Institute of Standards and Technology, Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile.
• Federal Trade Commission staff, AI Companies: Uphold Your Privacy and Confidentiality Commitments.
• Office of Inspector General, General Compliance Program Guidance.
• American Speech-Language-Hearing Association, Augmentative and Alternative Communication.