How to Prepare for an ABA Portal or Record-System Change

Map what is actually moving

Ask whether the change covers scheduling, clinical records, data collection, messaging, forms, signatures, billing, payments, telehealth or every function. Record the old-system cutoff, read-only period, new-system start, downtime process, support contact, expected migration scope and record owner.

A new portal account does not itself create a new provider relationship, consent, authorization or representative. Ask which previous permissions carry forward and which require a fresh decision.

Save a useful pre-migration snapshot

Before the cutoff, download or request current treatment plans, assessments, progress reports, signed agreements, consents, authorizations, schedules, statements, payment receipts and important messages that the family is entitled to receive. For covered entities, HHS access guidance describes the HIPAA access process and its scope.

Record each file's date and source. Avoid mass downloading information the family does not need or have authority to access. Preserve an accessible summary of upcoming appointments and urgent contacts outside the portal.

Rebuild access deliberately

Confirm the client's own access, each proxy or portal delegate, role, scope, expiration, preferred channel, confidential-communication request and revocation route. Test screen-reader use, keyboard access, language support, captions and a direct way to report errors. ASHA says AAC users should always have access to their communication tools or devices.

If a vendor handles PHI as a business associate, HHS business-associate guidance explains the regulated relationship. Families should still direct privacy questions to the covered provider named in its notice.

Reconcile the migrated record

After launch, compare the next appointments, active plan version, goals, safety information, health notes, communication profile, consent status, representatives, authorizations, open messages, balances and payment history with the pre-migration snapshot. Report missing, duplicated or incorrect items through the stated route.

Keep the original evidence and correction response. A display problem may differ from a source-record error. Ask which system is authoritative and who can correct each field.

Questions to ask before the next action

For this ABA system-migration register, assign each question to the practice owner, qualified clinician, privacy contact, billing team, vendor, health plan, family, client, advocate or lawyer with authority to answer it. Bring the current notice, agreement, record, schedule, authorization, claim, EOB or statement:

• Which functions and dates are affected?
• Which records should be saved before cutoff?
• Who owns the official record?
• Which access and proxy permissions remain valid?
• How will downtime protect care and communication?
• Which fields must match after migration?
• Where are errors and privacy concerns reported?

Mark each answer confirmed, open, disputed or decided. Add the source, version, effective period, owner, deadline and client view. Keep system access, record custody, consent, proxy authority, clinical accuracy, scheduling, authorization, billing and privacy-incident review as separate states. A missing safety, access, privacy, authority, clinical, payer or financial gate stays visible until the responsible role resolves it.

For each ABA system-migration register answer, record what the source actually proves and what remains undecided. When two sources conflict, preserve both versions, pause the affected release when needed, and ask the role with authority for written clarification. Keep the family informed while that review is open.

Proceed with the next planned action only when its required gates clear or an authorized interim path protects the client.

Build an ABA system-migration register

Client priorities, old and new systems, affected functions, cutoff and launch dates, downtime plan, record owner, support and privacy contacts, exports, forms, signatures, consents, representatives, portal delegates, appointments, plans, goals, health and safety data, AAC, authorizations, statements, payments, messages, discrepancies, owners, and resolutions belong in one current, role-limited ABA system-migration register. Give every field a source, version, effective date, state, owner, next action and recheck trigger. Preserve client report, family report, provider record, payer evidence, vendor response and qualified professional judgment as separate sources.

Give the client an accessible summary and invite corrections. Store identity, health, financial, payer and authority information only where approved people need it. The register should make the next action easier and expose unfinished work.

Prepare for one likely failure

Rehearse the response to failed login, inaccessible screen, missing appointment, lost message, duplicate account, wrong proxy, stale consent, missing safety information, incomplete data history, duplicate balance, phishing message, prolonged downtime, or the client losing a communication route. Name who protects immediate health and safety, who gives the client an accessible update, who preserves evidence, and which clinician, practice, payer, vendor, regulator, advocate or emergency role must act.

Keep AAC, communication, medication, mobility, food, water, bathroom, emergency help and other essential supports available. Record the event, actual response, temporary arrangement, missing evidence and condition for safe continuation. Review the result before closing the issue.

A fictional portal migration check

Elena locks 20 high-priority migration fields. Sixteen match the pre-migration snapshot. The proxy expiration, one signed agreement, the crisis contact, and an old credit remain unresolved. Migration verification is 16 of 20, or 80%.

The ratio measures the locked fields only. It does not prove the entire database migrated, validate privacy compliance, authorize a proxy, correct a balance, or show clinical readiness.

Measure the process without hiding open work

Define the ABA system-migration register review cohort before counting. Report verified items divided by every item due at the same checkpoint. Keep missing, failed and disputed items in the denominator and list their age, consequence and owner. If one item is inapplicable, record the source-supported reason before the period begins.

Focus on Elena's access, understandable communication, portal delegates, records, plan and safety accuracy, AAC, appointments, authorizations, balances, privacy, correction time, and family workload. Pair process counts with the client's direct report and any material clinical, access, privacy, payer, financial or safety outcome. A checklist percentage describes one stated process at one time. Legal rights, clinical effectiveness, satisfaction, causation and future continuity require separate evidence and decision authority.

Set the next review date

Review the ABA system-migration register before the old portal closes, on first login, before the next visit, after the first statement, after every reported discrepancy, and again after the migration support period ends. Close each item as confirmed, corrected, refunded, transferred, appealed, disputed, referred, held, declined, transitioned or ended. Record the authorized or qualified decision-maker, rationale, effective date, communication route and evidence.

At review, ask what the practice misunderstood and which burden should change first. Administrative transitions can shift clinical access, family time, trust and safety. One named owner remains accountable for every open item until final disposition.