To validate an ABA dashboard against source records, create locked cases with known eligibility, calculations, missing states, corrections, filters, permissions, alerts, and exports. Compare the displayed cohort and value with the source evidence for every case. Test role and accessibility behavior as well as arithmetic. Hold clinical release when a defect can hide records, alter denominators, expose data, or change a decision prompt.

Define source truth for each case

Lock source records, states, definitions, corrections, cutoff, expected cohort, formulas, precision, and responsible reviewer.

Test filters and denominators

Cover date, person, program, phase, setting, collector, missing, invalid, zero-opportunity, preliminary, corrected, and finalized states.

Test every display path

Compare headline tiles, tables, graphs, tooltips, drill-downs, alerts, exports, print views, and accessible labels.

Verify permissions and privacy

Use role-specific cases for allowed, restricted, masked, exported, shared, and audited access.

Exercise corrections and late data

Confirm that revisions preserve history, update affected derivatives, retain decision snapshots, and route material changes.

Set severity-based gates

Block release for defects affecting safety, privacy, cohort identity, calculations, clinical prompts, or required evidence; track lower-severity issues transparently.

Build Rina's source-to-dashboard validation suite

Create a versioned source-to-dashboard validation suite for the validate ABA dashboard against source records question. Include the client priority, exact decision, responsible roles, response and opportunity definitions, source records, measurement unit, sampling frame, numerator, denominator, missing and invalid states, access method, burden, risk, calculation lineage, tool version, review date, and approval evidence. A second reviewer should be able to reconstruct both the evidence and the workflow state.

Work through Rina's example

Rina's suite contains 24 locked cases. Twenty-one match the source cohort, calculation, state, and display. One filter hides zero-opportunity sessions, one rounds before aggregation, and one role can open a restricted detail. Validation is 21 of 24, or 87.5%. The dashboard remains unreleased until all three defects pass repair and regression testing. Show all source counts, held items, conditions, and calculation steps before the percentage. This fictional clinical dashboard migration example illustrates one governance pattern and supplies no universal threshold, required tool, treatment recommendation, compliance conclusion, or causal claim.

Audit Rina's evidence trail

Rina's suite stores source fixtures, expected cohort, expected calculations, expected permissions, actual output, screenshots, logs, dashboard version, query version, defect severity, owner, repair, and rerun. All 24 original cases remain due. The audit checks current definitions, raw records, source identity, collector and reviewer roles, client communication access, sampling, corrections, calculations, displays, permissions, decision use, and unresolved holds. Reviewers preserve the evidence available at each earlier decision rather than letting a later system state rewrite history.

Address Rina's main governance risk

A correct headline score can coexist with a wrong cohort, hidden hold, privacy defect, or misleading drill-down. Rina's acceptance examines each layer instead of checking the top tile alone. A clean percentage can conceal an incomplete cohort, incompatible definition, biased sample, inaccessible process, wrong source, or unauthorized decision. Review the numerator, denominator, excluded states, client impact, and authority before accepting the display.

Choose Rina's next action

The release owner reruns the full critical suite after every fix, confirms rollback and monitoring, and documents which dashboard functions support review. Treating clinicians retain decision authority. Record the selected action, rationale, responsible role, client response, due date, evidence required for closure, and conditions that reopen review. Software may detect, calculate, compare, and route. The qualified professional makes case-specific clinical decisions within applicable authority.

Protect Rina's access and participation

Keep Rina's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, rest, relationships, and emergency help available during measurement. Offer accessible and private ways to ask questions, correct a record, decline optional observation, pause, or communicate distress. A system-quality test should improve evidence without creating an artificial or unsafe condition.

Apply current sources to Rina's review

Rina's source set supports faithful measurement and visual analysis while the suite translates those requirements into system tests. The BACB ethics hub and CASP public summary provide professional and clinical context. The BCBA Test Content Outline identifies measurement, validity, reliability, sampling, graphing, and data-based decisions as examination content. The WWC handbook supplies research-review standards. Reviews of single-case design and quality and systematic visual-analysis protocols support explicit methods and evidence trails. Research on graphing rate with fidelity illustrates the value of aligned measures. An evidence-based ABA framework places research, clinical expertise, context, and client values together. ASHA supports continuous AAC access.

Rehearse Rina's governance workflow

Test the source-to-dashboard validation suite with a missing source row, conflicting definition, zero-opportunity record, inaccessible form, declined observation, biased sample, stale calculation, software default, role-permission error, late correction, and decision with no owner. Confirm that every item remains visible, the correct denominator survives, urgent concerns route immediately, historical states remain reconstructable, and release gates stop affected use.

Close Rina's review

Review the source-to-dashboard validation suite with Rina, the responsible clinician, and specialists named by the manifest. Preserve raw evidence, definitions, access, sampling, burden, calculation and software versions, reviewer findings, corrections, decisions, and limits. Keep the page draft and noindex until the required clinical, client or family, accessibility, methods, technology, privacy, and legal reviews are complete.

Related resources

Sources