Reconcile Conflicting ABA Plan Versions Across Systems

To reconcile conflicting ABA plan versions across systems, identify the authoritative clinical decision and every distributed copy, then pause affected use when staff cannot determine which instruction controls. Compare identifiers, content fingerprints, effective scope, and timestamps. Preserve each conflicting artifact, correct the distribution path, notify affected users, and review sessions exposed to the mismatch. Never resolve the conflict through silent overwrite or whichever copy was edited last.

Inventory every plan surface

Include the clinical record, portal, mobile app, data collector, scheduling note, staff handout, printed binder, caregiver copy, integration, cache, and offline downtime packet.

Build the inventory around actual workflows rather than the intended architecture. Ask each role where they look before a session, what they download or print, and what remains available when a connection fails. Record the owner, location, format, last verified content, users, and update path for each surface. An undocumented spreadsheet or photographed binder page can matter as much as a formal integration.

Identify authoritative evidence

Trace the qualified approval, client review, exact content, effective scope, release event, and supersession history. Last modified time alone does not decide authority.

Authority comes from the approved clinical decision and its governed release, not from whichever system has the newest timestamp. Confirm the author and approver, the content they reviewed, the population and settings covered, the effective conditions, and any later withdrawal or supersession. If those facts cannot be reconstructed, qualified review must determine the safe prospective instruction while the discrepancy remains preserved for investigation.

Contain uncertain use

Pause the affected component or assignment when the mismatch creates clinical, safety, or access uncertainty. Maintain needed communication, health support, and emergency action.

Contain only the uncertain scope when that can be done safely. Name the affected goal, procedure, staff group, location, or date range, and tell recipients what remains authorized. Provide an accessible route for questions and report new concerns promptly. When immediate health or safety needs arise, follow the responsible emergency or medical pathway rather than waiting for the documentation investigation to finish.

Compare content and metadata

Check version IDs, fingerprints, goals, definitions, procedures, prompts, access, risks, roles, measures, dates, and system transformations. Record the exact differences.

Use a line-by-line or field-by-field comparison for clinically meaningful content. A matching file name can hide changed prompting steps, response definitions, mastery criteria, or communication supports. Also check whether formatting, truncation, export logic, or a failed sync altered meaning. Preserve screenshots, exports, hashes, and system timestamps with their collection context so the reconciliation can be repeated and challenged.

Review exposed sessions

Define the mature cohort, determine which version each session used, preserve unknowns, and route clinical, safety, privacy, documentation, authorization, and claim questions separately.

Start with every session that could have encountered the mismatch, then classify exposure using evidence such as access logs, cached content, staff report, contemporaneous notes, and materials used. Keep unknown sessions in the denominator. Qualified roles should decide whether any client follow-up, record amendment, supervision, safety review, privacy response, payer communication, or claim correction is warranted, with each decision and its basis recorded separately.

Repair and test distribution

Correct the source or integration, invalidate stale caches, replace controlled paper copies, test each user role and setting, notify recipients, and confirm that rollback remains possible.

Test the repaired route as the people who use it, including offline, low-connectivity, delegated, and printed workflows. Verify the content itself, not merely a successful sync message. Track who received the correction, who demonstrated readiness, and which locations remain unresolved. Close the incident only after authoritative content is consistently available, exposed sessions are reviewed, and preventive ownership and monitoring have clear accountable roles.

Build Hugo's cross-system version reconciliation

Create a versioned cross-system reconciliation for the plan-copy conflict. Preserve the controlling plan identity, exact changed components, source evidence, direct client communication, caregiver and interdisciplinary input, qualified authorship and approval, lifecycle state, effective scope, training and readiness, distribution, implementation evidence, exceptions, correction history, rollback path, review dates, and accountable owners. Another qualified reviewer should be able to reconstruct both the decision and what users actually received.

Work through Hugo's example

Hugo's EHR shows v5, the mobile app shows v4, and a printed binder shows v3. Across 12 mature sessions, eight used the controlling v5 and four may have used an older component. Correct-version exposure is 8 of 12, or 66.7 percent. All four exceptions stay visible for clinical, documentation, safety, and claim-impact review. Show every numerator, denominator, excluded state, unresolved item, and date before calculating a percentage. This fictional clinic with EHR, mobile, and offline copies example illustrates one local control and supplies no universal release threshold, clinical instruction, training dose, effective date, or outcome guarantee.

Address Hugo's main release risk

A technically newer copy may still be unapproved, scoped to another setting, or corrupted. Hugo's reconciliation starts from qualified decision evidence; application chronology alone cannot establish the controlling plan. Review clinical meaning, implementation feasibility, access, safety, and system behavior separately. A technical success does not prove clinical fit, while a clinical approval does not prove that the correct version reached every user.

Choose Hugo's next action

System owners correct the propagation defect and verify content fingerprints. Qualified reviewers assess the affected sessions, communicate any care correction, and close each exception with evidence. Record the responsible role, authority, action, effective scope, due date, evidence needed for closure, communication, and next review. Software may control state, distribution, and alerts. Appropriately qualified professionals make case-specific clinical decisions within scope.

Protect Hugo's access and participation

Keep Hugo's AAC, interpreters, mobility, food, water, bathroom use, prescribed care, health support, movement, rest, relationships, and emergency help available during planning, training, implementation, pause, and rollback. Provide an accessible way to accept, decline, pause, withdraw when applicable, report discomfort, ask a question, and correct the record. A caregiver or staff signature does not author Hugo's experience.

Apply current sources to Hugo's workflow

The BACB ethics hub, current Ethics Code, CASP public summary, and BCBA Test Content Outline provide professional, client-involvement, evaluation, documentation, and training context within their stated scopes.

An evidence-based ABA framework supports integrating research, expertise, client values, and context.

A treatment-integrity practitioner guide, the Essig reporting review, research on the impact of treatment integrity, and an additional reporting review support explicit definitions, measurement, observer quality, and cautious interpretation.

ASHA supports continuous AAC access.

Rehearse Hugo's release workflow

Test the cross-system version reconciliation with an urgent safety concern, client withdrawal, unavailable AAC, medical question, absent supervisor, incomplete training, late staff assignment, system outage, stale mobile cache, conflicting paper copy, changed data definition, missing payer document, rollback trigger, and post-release adverse effect. Confirm that safe pause, qualified authority, version evidence, distribution, communication, and follow-up remain correct.

Close Hugo's review

Review the cross-system version reconciliation with Hugo, the responsible clinician, affected staff, and the specialists named by the manifest. Preserve the source evidence, plan content, direct client input, decisions, limitations, implementation record, open findings, and next review. Keep the page draft and noindex until the required clinical, treatment-integrity, client or family, accessibility, interdisciplinary, safety, privacy, software, payer, and legal reviews are complete.

How to Reconcile Conflicting ABA Plan Versions Across Systems