To merge unmerge and correct duplicate ABA client records safely, investigate before combining anything. Confirm that both records describe the same person, preserve each source and audit trail, decide field-level survivorship, obtain accountable approval, repair linked encounters and documents, and validate every downstream system. Keep a supported unmerge or corrective route. A matching name, phone number, payer ID, or caregiver never proves identity by itself.

Define Gideon's duplicate-record decision file

Gideon distinguishes suspected duplicates, confirmed duplicates, related people, aliases, former names, shared contacts, and erroneous cross-links. He freezes automated consolidation while identity or clinical history remains disputed. The unit names the person, event, source, purpose, responsible role, effective period, downstream systems, unresolved work, and closure evidence. This prevents a complete status from hiding an identity, access, clinical, privacy, or payer gap.

Build Gideon's page-specific control record

Gideon's file records both identifiers, matching attributes and sources, conflicts, relationship clues, person confirmation when appropriate, representative involvement, record classes, services, diagnoses, plans, allergies and health supports, communication methods, payers, contacts, documents, media, portals, authorizations, claims, access logs, merge decision, qualified approvers, field-by-field survivor, retained source history, redirect rules, downstream repair, notice, unmerge basis, and validation. No value disappears merely because another value wins the current display.

Put Gideon's control into daily use

Gideon stages each merge instead of running one irreversible command. The comparison view groups identity, contacts, clinical history, access, payer, documents, media, appointments, messages, claims, and audit events. Each field receives a proposed survivor, retained alternate, conflict state, owner, and reason. The dry run lists object counts and shows what every portal, report, export, and queue will display afterward. A second authorized reviewer confirms high-risk cases. During the merge window, affected records remain read-only except through an approved urgent-care route. The system creates a permanent redirect while preserving both original identifiers and the provenance of post-merge edits. Validation compares before-and-after counts and samples clinical meaning, access, disclosure, and claim links. Gideon keeps an unmerge design ready, including how to assign data created after consolidation. If a complete reversal would create another integrity problem, the records leader uses attributable corrections and scoped relinking instead. Clients and families receive clear communication when the duplicate affected access, care, privacy, or financial records. Gideon also preserves a searchable merge rationale for later review.

Protect client access and clinical meaning in Gideon's workflow

Gideon keeps accessible communication, AAC, language and disability access, consent and assent when applicable, dissent, privacy, health, safety, client priorities, ordinary supports, and source attribution visible. Administrative, technical, payer, or audit completion does not determine clinical appropriateness. Immediate safety action and mandated duties follow their own current routes.

Work through Gideon's fictional example

Gideon reviews 18 suspected pairs. Eleven are confirmed duplicates, four are different family members sharing a contact, two lack enough evidence, and one is a test record that entered production. Nine confirmed pairs merge cleanly. Two remain held for conflicting clinical histories. This fictional cohort teaches evidence and denominator discipline. It does not set a treatment, privacy, payer, coding, billing, legal, retention, accessibility, or technical standard.

Keep Gideon's denominator honest

Decision completion is 16 of 18 pairs, or 88.9%. Safe merge completion is 9 of 11 confirmed duplicate pairs, or 81.8%. The four nonduplicates and one test record have their own dispositions. Neither rate calls a held pair a failed client identity.

Assign Gideon's decisions to the right roles

An authorized identity or records leader owns the merge decision. Qualified clinicians resolve clinical contradictions and assess care effects. Privacy and security roles assess access and disclosure. Payer and billing roles repair member and claim links. Software proposes candidates and field differences while humans approve the result.

Address Gideon's main failure mode

A merge can create a plausible single chart that hides two people's histories. An unmerge can also lose post-merge changes unless the system records provenance for every field and object.

Validate Gideon's control with real transitions

Gideon rehearses a false-positive pair, a confirmed pair with conflicting addresses, two siblings on one phone number, a portal delegate, open notes, active authorizations, submitted claims, offline devices, and a later unmerge. He verifies every object count before and after.

Place Gideon's clinical and organizational sources correctly

Gideon uses the CASP public overview only for high-level organizational context. The BACB Ethics Code applies to BCBA and BCaBA certificants and applicants as defined by the Code; BACB has no separate jurisdiction over organizations or corporations. These sources support accountable roles, documentation, confidentiality, client involvement, assessment, intervention, supervision, and correction boundaries. They do not approve this workflow, create legal authority, or replace state, payer, employer, and role-specific rules.

Apply Gideon's payer evidence boundary carefully

Gideon treats the current CMS Program Integrity Manual, Chapter 3 and Medicare signature guidance as Medicare medical-review materials. Chapter 3 currently says services are expected to be documented when rendered; delayed or corrected entries may occur; the date and author should be identifiable; and a change or addendum should be clearly and permanently noted. These materials do not establish one universal ABA documentation, signature, payer, or state rule.

Use Gideon's privacy purpose and access routes separately

Gideon applies HHS minimum-necessary guidance to applicable uses, disclosures, and requests while preserving its treatment exceptions and entity scope. The HHS access guidance addresses an individual's HIPAA access right to a designated record set, subject to the rule. HHS TPO guidance and 45 CFR 164.508 describe distinct disclosure pathways. Verify covered-entity or business-associate status, purpose, authority, recipient, data, and other law rather than making one generic release form the answer.

Protect Gideon's data and communication context

Gideon uses the current HHS Security Rule overview for regulated ePHI safeguards and the HHS de-identification guidance for its two HIPAA methods and residual-risk boundary. The DOJ Title III overview covers equal opportunity, effective communication, and reasonable modifications for covered public accommodations. ASHA's AAC portal says AAC users should always have access to their tools or devices. Entity scope, state law, professional duties, contracts, and the particular data use still require separate review.

Choose Gideon's review triggers

Gideon reopens the duplicate-record decision file after a new system, field, record class, interface, vendor, site, role, payer, law, policy, access request, client preference, identity conflict, correction, outage, disclosure, incident, or audit finding. The review records the changed fact, affected people and records, immediate safeguard, accountable owner, due date, corrected source, downstream propagation, communication, and independent validation.

Finish Gideon's review without losing open work

Review the duplicate-record decision file with the people whose records and communication are affected, qualified clinicians, health-information and privacy leaders, and the specialists named in the manifest. Confirm source, identity, encounter, author, version, purpose, authority, access, client message, downstream use, exception, and validation evidence. Keep unresolved work visible and keep this page draft and noindex until every required external review is complete.

Related resources

Sources