Audit ABA Quality Improvement Records and Results

To audit ABA quality improvement documentation from question to result, lock a cohort of completed, active, paused, abandoned, published, and corrected projects. Trace purpose, classification, authority, measure versions, cohorts, provenance, missingness, baseline, change exposure, implementation, analysis, causal limits, client experience, actions, reporting, corrections, and reproducibility. Recalculate selected results from source snapshots and follow each material finding into dashboards, policies, plans, payer reports, and public claims.

Define Eli's quality-improvement documentation audit

Eli audits whether another qualified reviewer can reproduce the decision chain. A polished presentation without source, cohort, or version evidence fails that test. The record names the question, decision, authority, people and settings affected, measure version, data source, owner, protection, correction path, and evidence required before any result can be used.

Build Eli's page-specific fields

Eli records audit cohort and lock date, project and classification, sponsor and owners, client protections, measure specifications, cohort reconciliation, source snapshots, queries, transformations, missing and excluded states, baseline, change package, actual exposure, analysis plan and deviations, variation, causal language, client experience, access and burden, actions and validation, sustainment, external or public report, correction, downstream recipients, audit finding, severity, remediation owner, retest, and closure. One source defect links to every impacted derivative without duplicate counting.

Connect Eli's audit findings to a decision

Eli assigns each finding a decision impact: informational, correction required, output held, action reopened, governance review, or external reconciliation. He records which dashboards, plans, policies, payer reports, or public statements relied on the affected evidence. A repaired source receives a targeted retest and recipient update. This turns audit findings into controlled decisions while preventing one defect from being counted repeatedly across derivatives.

Preserve Eli's client and workforce protections

Eli records direct client and family input through accessible methods, including AAC, and separates care decisions from project decisions. Essential communication, health, safety, privacy, mobility, food, water, bathroom access, pain care, and emergency help remain protected. Workforce participation, performance review, and employment action use their own authority. Administrative tools can calculate and route; qualified people make clinical, legal, privacy, employment, research, and public-claim decisions.

Version Eli's evidence chain

Eli assigns versions to the question, measure, cohort, source snapshot, query, transformation, change package, analysis, dashboard, and report. Each derivative identifies its inputs and generated time. Corrections preserve the earlier result, explain the reason, recalculate affected outputs, and create reconciliation tasks for every clinical, payer, policy, training, governance, or public recipient.

Keep Eli's units and denominators aligned

Eli identifies whether the unit is a person, episode, encounter, claim, service line, staff member, observation, opportunity, task, action, site, or period. Numerator and denominator use compatible units and the same maturity rule. Pending, missing, excluded, duplicate, and invalid candidates remain visible in the reconciliation. Counts accompany every rate, and N/A replaces 0% when no unit is eligible.

Separate Eli's description from cause

Eli reports timing, association, trend, variation, and concurrent change with precise language. A before-and-after difference, run-chart shift, or improved average can guide investigation and action. It does not by itself isolate the effect of the change. Stronger causal language requires a design and evidence that address plausible alternatives, measurement change, exposure, and chance.

Work through Eli's fictional example

Eli locks 30 QI projects. Twenty-two pass the full chain. Eight contain 12 findings: one classification gap, two measure defects, one denominator drift, one provenance break, one hidden exclusion, one weak baseline, one exposure gap, two causal overclaims, one missing client-access check, and one correction failure. Six repair; two remain open and their public summaries stay held. The example is synthetic and checks arithmetic, source structure, and interpretation. It does not establish a standard, benchmark, legal classification, privacy route, clinical result, causal effect, or outcome for another practice.

Calculate Eli's measures honestly

Initial project integrity is 22 of 30, or 73.3%. Final validation is 28 of 30, or 93.3%. Projects, measures, findings, affected outputs, actions, and results use separate denominators.

Address Eli's main quality risk

A high project-completion rate can reward superficial work. Eli emphasizes reproducibility, client impact, validated action, and corrected downstream claims.

Test Eli's record against hard cases

Eli traces local project, multi-site project, changed measure, hidden exclusion, source migration, small cohort, public claim, failed action, correction, and abandoned work.

Review Eli's decision handoff

Eli confirms purpose, authority, classification, protections, measure and cohort versions, provenance, missingness, baseline, exposure, analysis, client experience, unwanted effects, actions, sustainment, correction, open work, owner, and next review before releasing the quality-improvement documentation audit.

Scope Eli's organizational and professional sources

Eli uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management scope. CASP sells the details. The BACB Ethics Code applies to covered people and addresses competence, client involvement, consent and assent when applicable, confidentiality, documentation, risk, data, and evaluation. BACB has no separate corporate jurisdiction.

Use Eli's measure sources as examples

Eli uses AHRQ Quality Indicators to illustrate technical specifications with a measure description, numerator, denominator, and exclusions. Those indicators use hospital administrative data and are not ABA measures. The AHRQ measure-development page supports objective, standardized, comprehensible numerator, denominator, and data-source specifications. The practice must validate its own measure.

Use Eli's improvement tools within scope

Eli uses the AHRQ QI toolkit page for project planning, process mapping, PDSA, run-chart, control-chart, and related tool concepts. The page hosts older primary-care materials and does not prove that one tool fits an ABA question or that a plotted change was caused by the project.

Classify Eli's project before acting

Eli uses the HHS OHRP Quality Improvement Activities FAQs for the boundary between activities limited to implementing a practice for care improvement and collecting implementation data, and research designed to contribute to generalizable knowledge. The guidance is nonbinding and predates the revised Common Rule; responsible institutional review remains necessary when classification is uncertain or the activity changes.

Protect Eli's quality data and access boundary

Eli uses the HHS Privacy Rule summary for the statement that quality assessment and improvement can be health care operations within HIPAA scope. The HHS access FAQ explains that some quality records using PHI may or may not be in a designated record set depending on whether they are used to make decisions about individuals. Privacy, security, access, state law, contracts, and research rules still require separate analysis.

Choose Eli's next review trigger

Eli reopens the quality-improvement documentation audit when purpose, classification, authority, client input, measure, cohort, source, workflow, exposure, result, missingness, unintended effect, action, public use, correction, or governing source changes. The record preserves the prior version and identifies every affected output, decision, owner, and validation step.

Close Eli's quality record with limits visible

Review the quality-improvement documentation audit with the client and authorized people as applicable, qualified clinical and quality leaders, data and privacy owners, and every specialist named in the manifest. Confirm reproducibility, access, burden, causal limits, corrections, and unresolved work. Keep the page draft until every named review is complete.

Audit ABA Quality Improvement Documentation From Question to Result