Govern AI-Assisted Drafting of ABA Clinical Notes and Reports

Define Kira's AI drafting case file

Kira limits the tool to tasks it has been validated to support. A drafting assistant may organize verified facts, yet it does not observe care, assess the client, select goals, establish medical necessity, approve a plan, or authenticate a record. 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 Kira's page-specific control record

Kira records approved use and prohibited use, client and encounter, user and author role, model and version, vendor, configuration, prompt template, retrieval and source record versions, generated output, confidence or citation feature, unsupported claim, omitted fact, contradiction, bias or accessibility issue, author edits and decisions, clinical review, release state, downstream use, privacy and security path, retention, vendor training setting, incident, correction, monitoring cohort, and decommissioning trigger. Manual text and generated text remain distinguishable during review.

Put Kira's human-review boundary into practice

Kira validates a narrow workflow before wider release. The test set includes complete, missing, contradictory, corrected, stale, and wrong-client sources; different settings and communication methods; small and zero opportunity counts; dissent; and health or safety context. Reviewers score every material claim against the locked source set and record unsupported, omitted, distorted, misattributed, or overconfident output. Users may reject the draft without penalty and write directly. The interface requires source inspection rather than one-click acceptance and prevents the model from signing, selecting a billing code, or changing the plan. Kira checks whether automation changes documentation time, error discovery, record length, client voice, and reviewer workload. She monitors subgroup and accessibility patterns without claiming fairness from one aggregate rate. When a model or prompt changes, validation runs again. A released error triggers source-based correction and downstream trace review.

Protect client communication and ordinary access for Kira

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

Kira reviews 30 generated drafts. Twenty-four pass line-level source verification. Two invent support details, one omits dissent, one combines different dates, one imports a stale goal, and one attributes a caregiver statement to the client. All six are held. 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 Kira's denominator tied to the locked population

Draft verification is 24 of 30, or 80.0%. Claim-level support uses all material claims in the locked set. The six held drafts remain in the cohort. Editing effort, clinical quality, client experience, and downstream errors use separate measures.

Assign Kira's decisions to accountable people

The accountable author controls the record. Qualified clinicians make clinical decisions. Clients and families supply attributed perspectives. Privacy, security, legal, and procurement leaders govern data and vendors. Software drafts and flags without authority.

Address Kira's main AI documentation risk

A source citation can point to a real record while the generated sentence still overstates or reverses it. Review the claim and the cited evidence together.

Test Kira's workflow with difficult cases

Kira tests missing sources, conflicting records, stale plan, zero opportunities, dissent, client attribution, dates, calculations, copied language, prompt injection in records, model update, and correction propagation.

Check Kira's release evidence

Kira 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 drafting case file retains unresolved work, owner, deadline, downstream trace, and the next revalidation trigger.

Use Kira's ABA governance sources within their scope

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

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

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

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

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

Kira reopens the AI drafting case 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 Kira's workflow without hiding uncertainty

Review the AI drafting case 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

• Verify AI-Generated ABA Clinical Summaries Against Source Records.
• Govern Speech-to-Text Dictation in ABA Clinical Documentation.
• Govern Ambient AI Recording and Scribe Tools in ABA Services.
• Audit an AI-Assisted ABA Clinical Documentation System.

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.