Why this matters
The first days of live treatment are the highest-risk window of the whole project. Untested interfaces, unvalidated migrated data, and thin first-week coverage are the most common reasons a go-live destabilizes. Most of that risk is preventable with a disciplined checklist and clear ownership.
T-30 to T-8: Foundation
- Confirm scope, systems in play, and every integration point (EHR, scheduling, billing, treatment machines, imaging).
- Confirm build validation and environment readiness.
- Provision user accounts, roles, and security.
- Review master data and dictionaries.
- Finalize the training plan and identify superusers.
T-7 to T-1: Validation and rehearsal
- Validate migrated data with counts, spot checks, and reconciliation against source.
- Test interfaces end to end: ADT, orders, results, scheduling, and charges.
- Run a full dry run for a simulated patient from referral to treatment to charge.
- Confirm downtime and read-only procedures.
- Set the command center, escalation tree, and on-call schedule.
Go-live day
- Stand up the command center and confirm staffing and hours.
- Walk the first patient hour by hour with a superuser present.
- Confirm issue logging and triage is live.
- Clear every sign-off gate before opening to full volume.
First week and stabilization
- Run daily huddles and issue review.
- Monitor and resolve interface errors.
- Reconcile charge capture against treatments delivered.
- Maintain documentation and a known-issue list.
- Work the optimization backlog and transition to steady-state support.
Common failure points
- Interfaces tested only on the happy path.
- Migrated data that was never reconciled to source.
- No owner for charge reconciliation.
- First-week coverage that depends on one person.
- Downtime workflow that is undocumented or untested.
Signs you may need outside support
- No dedicated interface tester.
- No charge validation owner.
- Single-person support coverage.
- A compressed timeline with little slack.
Common questions
- Is this checklist specific to MOSAIQ?
- It is organized around a MOSAIQ go-live, but the structure applies to most oncology information system go-lives. The interface, data validation, and charge reconciliation steps are broadly relevant.
- Is GlobalSABT affiliated with Elekta or MOSAIQ?
- No. GlobalSABT is independent and vendor-neutral. MOSAIQ is referenced only to describe the environment. We are not affiliated with, certified by, or endorsed by Elekta or any vendor.
GlobalSABT is an independent consulting company and is not affiliated with, certified by, or endorsed by Epic, Varian, Elekta, Oracle Cerner, or any other system vendor. Product names describe environments only. Do not submit Protected Health Information, patient identifiers, medical record numbers, or confidential clinical data through this form.