To separate ABA monitoring quality assurance quality improvement program evaluation audit and research, classify the work before collecting or reusing data. Name the purpose, question, population, authority, participants, intervention, risk, privacy route, method, audience, decision, and intended external use. Routine monitoring observes current performance. Assurance checks a defined requirement. Improvement tests change. Program evaluation judges a program. Audit tests evidence or controls. Research seeks generalizable knowledge under applicable rules. Similar records never make these pathways interchangeable.

Define Imani's quality-work classification

Imani uses a classification conference for ambiguous work. A project can require parallel privacy, clinical, compliance, research, or employment review, with linked evidence and separate decisions. The label chosen by a sponsor never overrides the actual design and intent. The quality-work decision map names the problem, people, classification, authority, aim, measures, analysis, test, safeguards, decision, action, validation, learning, and review status.

Build the fields Imani needs

The working record captures request and original wording, trigger, sponsor, purpose, question, population, intervention or change, assignment or participant status, risk and burden, client involvement, data sources, prospective or retrospective design, comparison, randomization or allocation, external dissemination, generalizable-knowledge intent, authority, privacy route, minimum necessary, de-identification, clinical and safety review, research or IRB determination, audit standard, deliverable, decision use, linked processes, classification, reclassification trigger, and closure. Structured fields keep projects, populations, measures, versions, tests, decisions, and actions searchable. Narrative preserves client perspective, reasoning, uncertainty, deviations, unfavorable findings, and context while source data, corrections, and audit history remain attributable.

Keep improvement and clinical authority separate

Imani separates client choices, qualified clinical decisions, QI facilitation, privacy and research review, payer coverage, compliance, employment, reporting, and legal analysis. Software and teams can surface signals and enforce gates. They cannot authorize clinical content or turn a QI label into permission.

Apply Imani's workflow

Imani asks what the team will do to people or workflows, what it hopes to learn, who benefits, and where results will go. Qualified research and legal owners make determinations under current sources. Operations records the decision and blocks work until required gates clear.

Reclassify when the project changes

A local dashboard can become a prospective intervention, a conference abstract, a multi-site comparison, or a publication. Imani sets triggers for new data, changed population, randomization, broader dissemination, external sponsor, new risk, and secondary use. The team pauses affected work while the qualified review catches up.

Control urgent action and changed facts

Imani routes immediate danger, medical emergency, suspected abuse or neglect, privacy incident, and other time-sensitive duties through current authorized paths while learning continues. A changed population, risk, role, plan, measure, source, technology, payer rule, or intended use reopens affected gates. Interim action records authority, scope, expiry, communication, and reassessment.

Work through Imani's fictional example

Imani locks 34 quality requests. Twenty-six are classified with purpose, population, method, authority, privacy, risk, output, and change triggers. One QI project becomes research without review, two audits contain active interventions, one program evaluation lacks a population, two employment investigations are mislabeled QI, and two requests need parallel processes. Five repair. Three remain open. This synthetic example tests workflow and denominator logic. It supplies no clinical, research, privacy, payer, licensing, reporting, employment, peer-review, contract, or legal conclusion for a real person or organization.

Calculate Imani's measures honestly

Initial classification integrity is 26 of 34, or 76.5%. Thirty-one requests validate, or 91.2%. Requests, projects, people, records, tests, reports, and determinations retain separate units.

Address the main quality-work classification risk

A convenient QI label can bypass participant protection, privilege review, data limits, or the distinct authority required for audit, research, and employment decisions.

Test Imani's artifact against hard cases

Imani tests dashboard, chart audit, process test, program evaluation, case report, conference poster, multi-site study, staff investigation, and payer audit. Each case records classification, client involvement, authority, data, measures, safeguard, test, deviation, decision, action, validation, and next review.

Close with failed tests and open learning visible

Imani confirms client involvement, authority, data integrity, measure definitions, systems analysis, safe testing, stop decisions, negative results, action evidence, validation, recurrence, and residual uncertainty. The quality-work classification remains draft until every named reviewer finishes. Open work retains an owner, age, affected people, safeguard, and next action.

Place Imani's improvement work inside accountable ABA operations

Imani uses the CASP Organizational Guidelines public overview for high-level business, clinical-operations, and risk-management context. The ABA Practice Guidelines Version 3.0 public summary concerns ABA behavioral health treatment for people diagnosed with autism. CASP licenses the details. This quality-work classification is an editorial model, not a CASP QI protocol.

Apply behavior-analyst duties within their exact scope

Imani uses the current BACB Ethics Code, which applies to BCBA and BCaBA certificants and people who completed an application. It addresses competence, client involvement, consent and assent when applicable, assessment, intervention, risk, data, documentation, supervision, and evaluation. BACB has no separate organization or corporation jurisdiction, so organizational QI authority and other laws require separate sources.

Classify healthcare-operations data use before relying on HIPAA

Imani uses current 45 CFR 164.501, which includes specified quality assessment and improvement, case management, care coordination, competence review, auditing, and compliance activities in healthcare operations. The practice first confirms covered-entity or business-associate status, relationship, purpose, and every condition. A healthcare-operations label does not settle research, state law, privilege, or client consent to care.

Minimize and de-identify information accurately

Imani uses HHS minimum-necessary guidance for covered uses, disclosures, and requests where applicable and HHS de-identification guidance for Expert Determination and Safe Harbor. A removed name, aggregated chart, synthetic label, or internal QI purpose is not itself de-identification. The record preserves provenance, method, restrictions, and residual identification risk.

Use compliance guidance without overstating it

Imani uses the OIG General Compliance Program Guidance as voluntary, nonbinding orientation for quality, patient safety, reporting, risk assessment, auditing, incentives, and corrective action in federal healthcare compliance. Current clinical, privacy, payer, licensing, reporting, research, peer-review, employment, contract, and state sources control the actual project.

Analyze systems and individual duties together

Imani uses the AHRQ PSNet Systems Approach primer to examine latent conditions, process design, and interactions that contribute to error. This patient-safety orientation is not an ABA mandate and does not excuse individual conduct. The analysis can support system redesign while separate qualified owners address competence, supervision, employment, reporting, and clinical decisions.

Use PDSA as a learning method

Imani uses AHRQ's Plan-Do-Study-Act page, last reviewed March 2026, for the cycle of planning, testing, studying measures, and acting on learning. AHRQ supports short-cycle, small-scale tests before broader implementation. PDSA does not authorize a clinical intervention, remove consent or privacy duties, or prove an outcome was caused by the change.

Keep communication and AAC available throughout improvement

Imani uses the ASHA AAC Practice Portal, which says AAC users should always have access to communication tools or devices. Improvement work preserves the person's system, backup, positioning, vocabulary, wait time, and partner response. A participation metric never requires speech, eye contact, or one response form.

Related resources

Sources