ABA duplicate appointment review determines whether two or more records represent the same intended visit, separate valid services, or an unresolved identity conflict. The review compares stable IDs, client, service, date, time, location, staff, series lineage, source events, and downstream use. It protects care and records by holding risky actions, assigning qualified decisions, preserving history, and reconciling every system after a duplicate is confirmed.

Define a duplicate candidate

A detector can flag identical IDs, same client and overlapping time, repeated source events, matching series occurrences, or similar records created within a short window. ABA duplicate appointment review begins with a candidate, not a conclusion. Group visits, concurrent approved services, split documentation records, and replacement versions may look alike while representing valid configurations. Preserve the detector rule and score so reviewers understand why the records entered the queue.

Compare stable identity and lineage

Collect visit ID, external IDs, series ID, parent event, source system, creation event, import or integration run, version, and previous replacements. Two rows with different IDs can still describe one visit after a retry or migration. Two rows with the same visible details can be valid when services or participants differ. Trace how each record came into existence before choosing which record, if any, should survive.

Compare operational facts

Review client, date, start and end time, time zone, service, setting, modality, site, staff, supervisor, access supports, status, confirmation, and notes needed for identification. Mark exact matches, meaningful differences, and missing data. Avoid using free text as the only match key. Display both records side by side and keep edits disabled until the reviewer records a disposition or receives the required qualified decision.

Preserve clinical authority

A duplicate detector may reveal two different clinical services or configurations. The BACB Ethics Code supports qualified assessment, intervention, supervision, risk, and documentation decisions for covered people. Operations can investigate identity and scheduling evidence. A qualified clinician resolves clinical meaning when the records reflect different planned services, dosage, supervision, or risk controls. Never delete a clinical record merely because its appointment resembles another.

Check payer and financial consequences

Review authorization links, units, claims, charges, remittances, refunds, and patient balances tied to each candidate. HealthCare.gov cautions that preauthorization does not promise cost coverage. A duplicate schedule record may create duplicate authorization reservations without producing duplicate claims, or the reverse. Route billing and payer corrections through qualified owners and preserve schedule, claim, adjudication, and payment as separate states.

Protect records and evidence

Determine HIPAA scope and data sensitivity before sharing candidates. For covered entities and business associates, the HHS Security Rule overview frames safeguards for ePHI. Restrict access, preserve audit history, and avoid exporting broad client lists for manual comparison when a role-limited queue can do the work. A merge or deletion should retain the original identity, author, timestamps, linked evidence, and reason according to the applicable record policy.

Use clear dispositions

Useful states include confirmed duplicate, valid separate records, linked replacement, unresolved identity conflict, false detector match, and referred for clinical or payer review. For a confirmed duplicate, choose the surviving operational record, freeze the duplicate, and list every link to move or close. For valid separate records, document the distinguishing fact so the detector can improve. Unresolved cases stay held under a defined safety rule rather than being forced into a binary answer.

Use a structured comparison worksheet

Place candidate A and candidate B in adjacent columns. Compare stable IDs, external event IDs, series and occurrence lineage, client identity, service, location, modality, local date and time, zone, duration, staff, supervisor, status, confirmation, source run, created time, last change, access supports, authorization link, documentation, charges, claims, payroll, and messages. Add a third column for the reviewer's finding and evidence. The worksheet should identify fields that are intentionally different and fields that cannot yet be verified. Include a hold decision, qualified-review route, surviving record when applicable, downstream tasks, client communication, and final approver. Avoid turning the worksheet into a broad export of client data; use a role-limited record with links to restricted evidence. Require a second review for wrong-client collisions or any pair tied to delivered care, clinical documentation, claims, or payment. At closure, verify each downstream task rather than accepting a checked master disposition with open corrections underneath it.

A fictional candidate cohort

Golden Field ABA reviews 30 candidates. Eighteen are confirmed duplicates caused by retry behavior, seven are valid separate services, three are linked replacement versions, and two remain unresolved because external IDs conflict. Disposition completeness is 28 of 30, or 93.3%. The two unresolved pairs stay in the denominator and cannot release downstream billing until identity is established.

Reconcile every downstream reference

Search calendars, client and staff portals, notifications, documentation, supervision records, authorizations, charges, claims, payroll, exports, analytics, and incident links. Move or close references under each system's approved correction process. Confirm that the surviving record shows the correct status and history. If a person received two confirmations, send a clear correction through the usable channel. Closing the duplicate queue before downstream reconciliation leaves operational contradictions in place.

Prevent deletion from hiding service history

A duplicate appointment can still contain unique notes, messages, timestamps, or decisions. Compare attachments and linked records before retirement. Keep delivered-service documentation under its governing correction and retention process. If both rows received documentation, route the question to qualified clinical and records owners. The scheduling team should never combine clinical content by copying text into one appointment. Preserve the distinction between duplicate scheduling shells and distinct records created through care.

Improve detector precision

Review false positives and missed duplicates by rule. Add series lineage, source event ID, status, service, time tolerance, and site only when evidence supports the change. Test the revised detector against a locked labeled set and new edge cases. Avoid tuning solely to reduce queue volume because weaker sensitivity can hide duplicates. Report precision and recall on the tested cohort when feasible, along with counts and consequences.

Stage duplicate cleanup

Begin with future, undelivered candidates because schedule and communication risk may be immediate and the downstream record set is smaller. Next review delivered visits without claims, then records tied to charges, claims, payroll, or clinical documentation under the relevant qualified owners. Lock each cleanup cohort and define the permitted disposition for its state. Preview which links, messages, series relationships, and reports will change before applying bulk actions. Reconcile the full cohort after every stage and stop when unexpected references appear. Keep correction timing and notices aligned with payer, workforce, record, and client requirements. This staged approach reduces the chance that a technically simple deletion disrupts a completed service record or financial workflow. It also lets the team improve detector and merge controls before handling the most consequential candidates.

Measure closure and recurrence

Track candidates, dispositions, confirmed duplicates, valid pairs, unresolved age, downstream reconciliations due and complete, client corrections, claim or payroll impact, source cause, and recurrence after fix. Report confirmed duplicates divided by reviewed candidates as detector precision for that defined cohort, not as the practice's overall duplicate rate. Keep candidate eligibility and detector version visible when comparing periods.

Related resources

Sources