Frequently Asked Questions

Sandbox is a free training environment with demo patients — no real PHI, no CMS submission, no live billing. Production is your live agency after go-live approval, with real patient data, OASIS export, and claims. You should complete setup and training in Sandbox before requesting Production access.

Yes. Production requires a valid CMS Certification Number (CCN), NPI, and an approved subscription. Sandbox does not require a CCN — use it to configure your agency and train staff first.

Visit app.betaskyhealth.com and choose self-service Sandbox signup for instant access, or contact Betasky for guided onboarding. After signup, configure agency settings, branches, payers, and users before admitting real patients in Production.

Sandbox ships with demo data — sample patients, care orders, visits, and OASIS — so you can explore immediately. Production starts clean after go-live approval; your real census comes from normal operations or an EMR migration.

Administrators: Sandbox Signup → Essential Setup (agency, branches, payers, users) → Go Live when ready. Clinicians: Dashboard Navigation and My Schedules. Billers: Claims Center and Payment Posting. For the full end-to-end path, read Complete Patient Journey.

Betasky uses agency roles (Agency Administrator, RN Case Manager, Scheduler, Biller, Home Health Aide, etc.) assigned per user. Roles control which menus and actions each person sees. Configure users in User Management after your role structure is defined.

Intake → care order (plan of care) → schedule visits → clinician documents on mobile or web → QA review → OASIS submission (when applicable) → claims and payment posting. The Complete Patient Journey chapter walks through every step.

OASIS assessments are linked to visits and care orders. Clinicians complete forms in the mobile app or dashboard; QA staff use the QA Center to review and approve before CMS submission from Production.

Yes. The docs hub offers a full PDF download of all 30 user guide chapters for offline reading or sharing with your team.

Target: within 2 weeks after Betasky accepts your complete migration zip. If the zip is missing files or has errors, the timeline pauses until you send a corrected package. Uploading archive PDFs to old care orders continues after go-live at your own pace.

One secure zip with Report Center exports: Patient List, Patient Roster, Employee List, physicians/payers/pharmacies, Profile PDFs, Medication Profile PDFs for active patients, and optionally care-orders.csv (one row per cert period — see migration guide). Do not scatter files across emails.

No. Visit and OASIS PDFs are archived on migration care orders. When your admin uploads a PDF, Betasky stores it and can register an archive visit on the episode timeline. We do not bulk-import chaotic Axxess Schedule Activity as editable live visits — history is preserved as documents plus archive visits.

No. Export the Axxess Employee List from Report Center — it already includes each person’s Role column (permissions), Title, Credentials, and email. Betasky maps those to Betasky roles during import. You spot-check logins and permissions after import.

You build a care order CSV with every certification period per patient. For in-care patients: older certs Expired, current cert Active, future certs Pending Assessment. For discharged patients: earlier certs Expired, final cert Discharged. Betasky imports all rows; your admin uploads PDFs afterward.

Your agency admin uploads in Betasky Care Order Details — anytime after care orders exist. Priority: go-live patients first, then recently discharged, then older retention window. Betasky does not bulk-upload every nursing note for you during the 2-week migration window.

Yes. Axxess is PDF- and Report Center–centric. Clinical history comes from Patient Chart → Schedule Activity prints, not one clean export. Care order status in Axxess is often wrong — you curate cert periods in care-orders.csv using your cutover date. An optional Betasky review call can spot-check that file before import.