Document ABA Quality Data Provenance and Lineage

To document ABA quality data provenance extraction and reconciliation, trace every reported element to its source system, record or transaction, field definition, relevant author, event time, extraction method, query or export version, run time, transformation, linkage, deduplication, validation, and correction. Preserve source snapshots and row counts through each stage. When systems conflict, apply a documented hierarchy or route the discrepancy instead of silently choosing the convenient value.

Define Yara's quality data provenance and reconciliation record

Yara treats a dashboard value as a controlled derivative. It carries its source, transformation, version, and known limitations wherever the result appears. 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 Yara's page-specific fields

Yara records project and measure version, source owner, system and environment, table or form, field and definition, author or transaction source, event and entry times, time zone, query text or report parameters, software version, run time, snapshot identifier, row counts, joins, linkage keys, filters, exclusions, deduplication, calculation, rounding, manual override, data lineage, access controls, validation sample, reconciled totals, discrepancies, correction, downstream dashboards and reports, owner, and release. Raw, cleaned, derived, and published datasets remain separately labeled.

Connect Yara's data chain to a decision

Yara records which output informed each operational or clinical decision and the exact source snapshot available at that time. A broken lineage, failed reconciliation, or unresolved source conflict places the affected output on hold. When corrected data changes a decision-relevant result, the owner receives both versions, the size of the change, and a required reconsideration task rather than a silent dashboard refresh.

Preserve Yara's client and workforce protections

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

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

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

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

Yara traces a 60-row source extract. Two duplicate encounter rows are removed under the declared rule, three rows fail client linkage, and one has an invalid date. The analysis-ready set is 54. Review fixes two linkage failures, creating a versioned 56-row set; the original 54-row result remains reproducible. The invalid row and one unresolved linkage stay visible. 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 Yara's measures honestly

First-pass reconciliation is 54 of 60 candidate rows, or 90.0%. Corrected readiness is 56 of 60, or 93.3%. Rows, people, encounters, measures, and projects remain separate units.

Address Yara's main quality risk

Copying a result into a slide can break its evidence chain. Yara includes measure, cohort, snapshot, and generated time with every derivative.

Test Yara's record against hard cases

Yara tests duplicate, wrong time zone, manual export, changed field, failed join, late correction, stale dashboard, multi-system conflict, access limit, and rerun.

Review Yara's decision handoff

Yara 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 data provenance and reconciliation record.

Scope Yara's organizational and professional sources

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

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

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

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

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

Yara reopens the quality data provenance and reconciliation 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 Yara's quality record with limits visible

Review the quality data provenance and reconciliation 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.

Document ABA Quality Data Provenance, Extraction, and Reconciliation