Document ABA Quality Missing Data and Exclusions

To document ABA quality missing data exclusions and invalid records, distinguish absent, not yet due, no opportunity, ineligible, unavailable, invalid, duplicate, access-limited, corrected, and excluded states. Record the source, reason, decision owner, affected measure, denominator effect, remediation, and correction. Report missingness and exclusions with the result, and use sensitivity checks when reasonable choices could materially change interpretation.

Define Zane's missing-data, exclusion, and invalid-record register

Zane prevents a blank field from becoming zero, no event, failure, or exclusion by default. Each state has an operational rule and evidence requirement. 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 Zane's page-specific fields

Zane records project, measure and cohort versions, candidate unit, required element, expected source, due event, observed state, reason, responsible role, eligibility effect, numerator effect, denominator effect, temporary or permanent status, access restriction, invalidity rule, duplicate link, correction route, outreach or retrieval action, due date, imputation prohibition or approved method, sensitivity scenario, revised result, owner, review, and closure. Excluded cases stay in the candidate reconciliation even when absent from the final denominator.

Connect Zane's missingness record to a decision

Zane states how much missing, invalid, or access-limited data the intended decision can tolerate and who approves that boundary. He shows the result under plausible treatments of unresolved records when a sensitivity check is useful. If a choice changes the conclusion, the decision is held or narrowed. This makes uncertainty actionable while preserving the people and workflows hidden behind missing fields.

Preserve Zane's client and workforce protections

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

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

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

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

Zane reviews 30 eligible records. Twenty-four contain valid data, two are missing, one has no eligible opportunity, one is invalid after a device failure, one is access-limited, and one is corrected after cutoff. The primary version reports 24 valid of 30 eligible with every state shown. A later corrected version includes the repaired record without rewriting the original cutoff result. 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 Zane's measures honestly

Valid-data completeness is 24 of 30, or 80.0%. Missing, no-opportunity, invalid, access-limited, and late-corrected counts remain explicit. This rate does not equal clinical success.

Address Zane's main quality risk

Excluding difficult records can erase access barriers or system failures. Zane reviews missingness by site, person, communication method, workflow, and source.

Test Zane's record against hard cases

Zane tests blank, zero, no opportunity, invalid device, duplicate, access restriction, late data, corrected data, excluded case, and sensitivity analysis.

Review Zane's decision handoff

Zane 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 missing-data, exclusion, and invalid-record register.

Scope Zane's organizational and professional sources

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

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

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

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

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

Zane reopens the missing-data, exclusion, and invalid-record register 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 Zane's quality record with limits visible

Review the missing-data, exclusion, and invalid-record register 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.

Document ABA Quality Missing Data, Exclusions, and Invalid Records