Betasky

Chapter 3: Waterfall Import Order


Chapter Overview

Data loads in a fixed six-level order. Your exports are grouped to match — reference data first, then staff, then patients, then clinical, then archive documents.


3.1 The six levels

LevelWhat we importWhat you provide
1BranchesBranch list from agency setup
2Physicians, payers, pharmacies, facilitiesReference CSVs or Report Center exports
3Users / cliniciansAxxess Employee List export (roles included in file)
4Patients, intake, emergency contactsPatient list + Profile PDF per MRN
5All care orders (every cert period) + medicationsApproved care order CSV + Med Profile PDFs
5bArchive PDFs (phased)Agency admin uploads in Betasky — not bulk import by Betasky
6Forward schedule (go-live)Built in Betasky after go-live — not bulk-imported from Axxess

Within each level we load structured rows first. Care order shells come from the CSV (all episodes). PDFs attach later when your admin uploads them in the dashboard.


3.2 Example Agency mapping

StepYour deliverablesBetasky result
Setupphysicians, payers, pharmacies, facilities (Report Center / Setup)Reference data
StaffEmployee List .xlsx from Report CenterLogins; Betasky maps Axxess Role → Betasky permissions
PatientsPatient List + Patient Roster + Profile PDFsPatient registry + intake
Care ordersApproved care order CSV (all cert periods, statuses)Every episode row → migration care order (Active / Expired / Discharged from CSV)
MedicationsMedication Profile PDF per active MRNMed list + signed reviews
Archive PDFsAgency admin uploads when readyPDF on care order + archive visit when extractable
Forward visitsScheduled fresh in Betasky post go-live

Part IV walks through each step for Example Agency.


3.3 Re-runs and fixes

If validation finds systematic issues (name order, wrong episode status), Betasky re-runs targeted fixes after your approval — not a full re-export from you unless files were wrong at source.


Next: Chapter 4 — Validation Before Go-Live