Build an ABA Quality Improvement Project Record

To build an ABA quality improvement project source record, define the operational or clinical question, purpose, scope, accountable authority, people affected, client and workforce protections, current process, measure set, data sources, baseline, and planned change. Record owners, dates, implementation, analysis limits, decisions, communication, corrections, and closure. Classify quality improvement, research, program evaluation, care, compliance audit, employment review, payer reporting, and public claims separately.

Define Vera's quality-improvement project source record

Vera begins with the decision the practice needs to make. She states who can authorize the work, who can change care or operations, and who reviews privacy, research, employment, payer, or public-reporting questions. 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 Vera's page-specific fields

Vera records project identifier, problem and evidence, aim, purpose and classification, scope and sites, affected clients and workforce, client input and AAC, accountable sponsor, clinical owner, privacy and data owners, research-review question, current workflow, measure specifications and versions, data sources, baseline period, exclusions, change package, start and stop, actual exposure, implementation evidence, analysis plan, safety and equity checks, unwanted effects, decisions, public-claim boundary, corrections, retention, and closure. The project record links to clinical source records without silently changing them.

Connect Vera's project to a decision

Before collecting new data, Vera names the decision the project will support, the person authorized to make it, and the evidence needed for action. She records hold, continue, adapt, expand, and stop criteria along with the next review date. When the measure or source changes, the decision waits for revalidation. This keeps a favorable dashboard from becoming an automatic clinical, workforce, payer, or public decision.

Preserve Vera's client and workforce protections

Vera 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 Vera's evidence chain

Vera 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 Vera's units and denominators aligned

Vera 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 Vera's description from cause

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

Vera locks 18 QI project records. Twelve contain purpose, authority, scope, protections, measure versions, baseline, change exposure, analysis limits, decisions, and corrections. One has no classification review, one lacks AAC input, one changes care without a clinical owner, one uses an undefined rate, one publishes a causal claim, and one has no correction path. Five repair; the classification file stays 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 Vera's measures honestly

Initial project-record completeness is 12 of 18, or 66.7%. Seventeen validate, or 94.4%. Projects, measures, cohorts, people, observations, actions, and outcomes use separate denominators.

Address Vera's main quality risk

A worthy improvement aim can still create privacy, burden, access, or research-boundary problems. Vera records those decisions before collecting or changing data.

Test Vera's record against hard cases

Vera tests local workflow change, multi-site project, clinical procedure change, staff evaluation, payer request, publication plan, small cohort, AAC access, correction, and closure.

Review Vera's decision handoff

Vera 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 project source record.

Scope Vera's organizational and professional sources

Vera 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 Vera's measure sources as examples

Vera 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 Vera's improvement tools within scope

Vera 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 Vera's project before acting

Vera 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 Vera's quality data and access boundary

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

Vera reopens the quality-improvement project source record 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 Vera's quality record with limits visible

Review the quality-improvement project source record 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.

Build an ABA Quality Improvement Project Source Record