An ABA appointment merge and split review controls when scheduling records may be combined or divided and how every affected fact and downstream record is reconciled. It verifies client and visit identity, service date and time, staff, location, modality, clinical source, payer evidence, documentation, messages, payroll, billing, and audit history. The workflow assigns authority, previews consequences, preserves originals, and provides a tested reversal or correction path.

Define merge and split precisely

A merge combines two or more schedule records into one governed record or relationship. A split divides one record into distinct visits or segments. State what happens to identity, duration, status, notes, assignments, authorizations, messages, and downstream work. Avoid using merge as a generic duplicate cleanup button. Some apparent duplicates represent separate services or corrections that require their own history.

Set eligible reasons

Examples may include an accidental duplicate, one visit recorded in two systems, a multi-part service entered incorrectly, or a recurring-series exception. Define allowed reasons, prohibited cases, reviewer, and evidence. Keep wrong-client, conflicting clinical content, finalized claims, incidents, and unclear service delivery on a stronger review path. The reason should drive the action rather than fit whichever button is easiest.

Verify identity

Compare organization, client, visit and series IDs, service, local date and time, time zone, duration, staff, supervisor, location, modality, source version, and external IDs. Review near matches separately. Never merge solely on name, date, and provider. Preserve each original ID and a crosswalk to the resulting record so later logs, exports, and corrections remain traceable.

Protect clinical authorship

The BACB Ethics Code supports qualified clinical decisions and accurate documentation for covered people. Operations may identify a discrepancy and coordinate review. Any change to clinician-authored content, service meaning, risk decision, or treatment record belongs to the qualified owner under the applicable correction process.

Keep payer states separate

Match payer, product, member, provider configuration, service, dates, units, authorization reference, claim state, and current source. HealthCare.gov cautions that preauthorization does not promise cost coverage. A merge or split should not convert authorization evidence into payment assurance, create units, or rewrite a payer decision. Route financial consequences to qualified billing review.

Preserve security and access

Classify entity, data, tools, and users. For HIPAA covered entities and business associates, the HHS Security Rule overview frames safeguards for ePHI. Limit merge and split permissions, require attributable approval, and log previews, actions, exports, and reversals. Test cross-organization and wrong-role attempts.

Preview downstream consequences

Before approval, list documentation, signatures, data collection, staff calendars, supervision, rooms, travel, notifications, payroll, claims, reports, incidents, authorizations, and integrations linked to each record. Show what will move, remain, duplicate, or become held. A clean schedule view can hide an orphaned clinical note or an extra payroll entry created by the same action.

Preserve originals and versions

Keep immutable references to the pre-action records, source versions, reason, requester, approver, execution time, transformation rule, and resulting IDs. Display correction lineage to authorized users. Avoid silent overwrite. If physical deletion is required later, retain the approved evidence needed to explain the action under the governing lifecycle and access rules.

A fictional merge review

North Valley ABA reviews 18 proposed appointment corrections. Eleven are eligible duplicate merges, four are eligible splits, two contain conflicting client identity, and one has a finalized claim requiring separate review. Actionable readiness is 15 of 18, or 83.3%. The three held cases remain in the cohort with owners and next steps.

Build the action register

Use request ID, reason, original visit and series IDs, client scope, source evidence, versions, service facts, clinical owner, payer and claim state, downstream links, preview, approvers, action, resulting IDs, messages, corrections, rollback or compensating path, reconciliation, and closure. Attach before-and-after comparisons. Keep held and denied requests visible.

Test merge cases

Test exact duplicates, partial duplicates, different staff, different times, recurring parent and exception, one canceled record, one completed record, and a wrong-client near match. Confirm the rule preserves intended duration, status, history, and downstream associations. Verify repeated submission is idempotent. A second merge request should not delete or absorb the surviving record.

Test split cases

Test one visit divided by service, location, modality, staff, time, or payer route only where policy supports it. Define allocation of duration and related evidence. Confirm no gap or overlap appears unless intended. Verify messages and calendars communicate the resulting schedule clearly. Hold any split that would create undocumented service facts or unsupported claim units.

Communicate the accepted schedule

Identify clients, caregivers, staff, supervisors, sites, and other roles who need the corrected facts. Use the approved accessible channel and preserve delivery evidence. Explain current date, time, location, and action without exposing internal cleanup detail unnecessarily. Provide a route for questions and corrections. A database repair remains incomplete when people continue relying on the superseded schedule.

Reconcile every consumer

Compare the resulting schedule with clinical records, data systems, portals, mobile apps, calendars, messages, payroll, claims, reports, archives, and integrations. Remove duplicates through controlled correction and route missing links. Keep all original records in the reconciliation cohort. Close only when each consumer matches the approved result or has a documented exception.

Exercise reversal and correction

Test an action found wrong after partial downstream use. Determine whether the system can reverse safely or needs new compensating records. Restore source meaning, preserve the incorrect action, reconcile downstream effects, and communicate current facts. Set stop conditions during bulk corrections. A reversal should never erase evidence that explains what users or systems saw.

Measure action quality

Report requests due, eligible, merged, split, held, denied, repeated, reversed, downstream-incomplete, and reconciled. Track time to decision and closure, client-impacting corrections, and recurrence by cause. Pair action counts with source defects. Use findings to improve duplicate prevention and record creation rather than making merge and split volume a productivity goal.

Reconcile duration and service facts

Before approving a merge or split, total each original duration, service segment, staff assignment, location, and applicable unit source. Define whether breaks, travel, documentation, overlap, or nonservice intervals belong in the schedule record under the practice's workflow. After the action, recalculate the resulting timeline and compare it with source evidence. Keep a difference of zero as a result to verify, not an assumption. If the action changes a clinical record, payroll item, authorization use, or claim candidate, route that consequence to its qualified owner and hold release until the required review is complete. Include a case where two records overlap and another where a gap is intentional. This check prevents a visually clean merged appointment from erasing time or a split from manufacturing unsupported duration. Preserve the arithmetic, source intervals, exclusions, reviewer, and accepted result in the action packet. Recheck the result after downstream corrections post. Record any remaining difference as an open exception. Confirm final totals in the closure review.

Related resources

Sources