Betasky

Chapter 15: Example Agency — Post-Import Reconciliation


Chapter Overview

After the main import, validation sometimes finds systematic issues that Betasky fixes before your sign-off. This is normal — not a failed migration.


15.1 Episode status corrections

When: Legacy "Active" disagrees with cert end date at cutover.

Example Agency: A small number of patients needed status updates after date-based review.

Your role: Confirm the corrected list matches your knowledge of who was in care on cutover date.


15.2 Name field corrections

When: CSV had LAST, FIRST mapped into wrong columns.

Example Agency: Names reconciled across patient records and intake before sign-off.

Your role: On future migrations, export separate first/last columns if possible — tell us your format upfront.


15.3 Medication re-import

When: A PDF batch was incomplete or a parser improvement applies to your files.

Your role: Re-send any missing Medication Profile PDFs; Betasky re-runs import for affected patients only.


15.4 Re-run Chapter 6 checklist

After any reconciliation, your admin should complete the full Verification Checklist again.


Next: Chapter 16 — Migration Timeline