What Happens When an ABA Session Note and Data Disagree?

Define the mismatch precisely

A narrative may say “independent” while the data show a gesture prompt. A note may describe four opportunities while the graph uses five. A device may use a newer definition than the written program. State the exact fields and units that differ.

Preserve both sources

Avoid choosing the value that looks better or overwriting the older record. Keep authorship, service time, entry time, device logs, forms, program versions, and correction history. Ask each observer what the record represents without pressuring anyone to match another account.

An ABA note data disagreement may reveal different questions

A note can summarize the whole encounter while a data stream covers one observation window. A caregiver report and direct count use different sources. Confirm whether the same response, opportunity, person, setting, and period were measured before calling the difference an error.

Assign correction and interpretation separately

The RBT Ethics Code requires accurate documentation and escalation under supervisor direction. The BACB Ethics Code addresses documentation, accuracy, correction, supervision, and data evaluation for covered behavior analysts.

The BCBA Test Content Outline covers operational definitions, measurement, agreement, validity, graphing, and interpretation as examination content. The CASP public summary supports individualized evaluation without prescribing this workflow.

A practical denominator

Ten records are sampled. Three contain mismatches. Review completeness is 10 of 10. Two mismatches are corrected and one remains unresolved, so resolution is 2 of 3. Keep the unresolved record in the denominator with an owner and next action.

Questions families can use

Ask which fields differ, whether the records cover the same event, what each source shows, who reviewed them, what was corrected, whether graphs or decisions changed, and how an unresolved discrepancy is shown.

Build the note-data discrepancy case

The note-data discrepancy case should preserve and compare a narrative note and data record before correcting the right source and reviewing clinical or payer impact. Capture note and data identifiers, authors, service and entry times, response and opportunity definitions, plan versions, observation windows, prompts, supports, setting, source device or form, exact mismatch, reviewer, correction authority, clinical interpretation, affected graph or report, claim review, unresolved state, and next action. Add the source, actor, actual date and time, current state, responsible owner, and next action so the family can reconstruct the record without relying on a generic completed label.

Use states suited to the note-data discrepancy case: created, entered, signed, reviewed, transmitted, held, corrected, disputed, superseded, or closed with reason. Keep service delivery, documentation, clinical validity, authorization, claim release, adjudication, payment, privacy rights, and personnel matters in separate lanes.

Preserve source, authorship, and chronology

For the note-data discrepancy case, identify who directly observed, who supplied reported information, who entered the record, and who later reviewed or changed it. Preserve actual service, entry, signature, correction, transmission, and release times. A later action should not rewrite an earlier timestamp or hide the original author.

Within the note-data discrepancy case, label client report, caregiver report, device data, schedule, time record, clinical interpretation, and payer correspondence by source. Each note-data discrepancy case source supports limited facts. A planned appointment does not prove every service event, and a signature does not prove that every statement is accurate.

Follow the record in order

1. Define the exact fields and units that differ. Open the note-data discrepancy case with the exact record, event, and question.
2. Preserve both records and their histories. Preserve the original and relevant source artifacts.
3. Determine whether the sources cover the same event and question. Compare definitions, times, roles, and applicable requirements.
4. Correct factual errors through authorized roles. Make any authorized change traceable.
5. Review affected clinical conclusions, reports, and claims. Record downstream review, family communication, and prevention.

Every rate in the note-data discrepancy case needs a defined due or eligible cohort. Report raw counts, missing items, invalid events, late records, and unresolved discrepancies. Avoid calculating a success rate only from records that happened to be complete.

Prepare for the main complication

A note may summarize a whole visit while an app covers one observation window. A narrative and count can therefore differ without either being false. Confirm response, opportunity, setting, time, and source before labeling one record wrong.

When that issue occurs, return to the note-data discrepancy case. Preserve what was originally documented, the new evidence, the person who made the decision, the effective date, and every affected graph, report, payer submission, safety action, or family update. Keep uncertainty visible until disposition.

Work through a concrete example

Ten records are sampled and three contain mismatches. Two are corrected; one remains unresolved because the device used a newer definition. Review completeness is 10 of 10 and resolution is 2 of 3. The open case retains an owner and next action.

The example illustrates how to organize the note-data discrepancy case. It does not establish a universal note field, signing deadline, correction right, payer requirement, or privacy outcome. The practice must apply the current law, payer source, professional duty, contract, and record policy that governs the actual event.

Questions families can ask about the note-data discrepancy case

• Which exact fields differ?
• Do the records cover the same event and definition?
• What does each source show?
• Who may correct and interpret the record?
• Which downstream decisions need review?

Request a written answer tied to the note-data discrepancy case when it affects note and data identifiers, authors, service and entry times, response and opportunity definitions, plan versions, observation windows, prompts, supports, setting, source device or form, exact mismatch, reviewer, correction authority, clinical interpretation, affected graph or report, claim review, unresolved state, and next action. If an answer remains unknown, record the source checked, responsible role, next action, due date, and consequence for any clinical, privacy, payer, or record decision.

Review downstream impact and closure

Before closing the note-data discrepancy case, check current care, graphs, progress reports, treatment decisions, safety follow-up, supervision, authorization materials, claims, family communication, and privacy obligations that used or depended on the information. Mark reviewed and unaffected items as well as changed ones.

The note-data discrepancy case closes only when the mismatch has a supported disposition. Preserve the unresolved record rather than choosing the value that makes performance look better.

Prepare the family's next action

Use the note-data discrepancy case to tell the family what can be requested next: an explanation, accessible copy, factual correction, formal amendment review when applicable, clinical discussion, payer reconciliation, privacy review, or complaint escalation. Give the responsible contact, required information, expected response milestone, and any deadline that comes from the governing source. Keep an urgent safety or medical route separate from routine record correspondence.

Give the client or family a concise, accessible note-data discrepancy case explanation of the disposition and available next route. Preserve the dated note-data discrepancy case explanation, original record, and later change so another reviewer can reconstruct the sequence without exposing unrelated personnel information. Record when the explanation was delivered and whether a factual correction or unanswered question remains.

When the note-data discrepancy case closes, identify the retained source records, applicable retention rule or policy, and future event that would reopen review. This prevents a corrected field or transmitted document from losing the history needed for later care, payer, privacy, or quality questions.