Resources
Migration and onboarding guide
A realistic outline. No migration tooling is built. This is the plan and the honest gaps.
Diagram: only the configuration step exists in the pilot.
| Step | What the design calls for | Status |
|---|---|---|
| 1. Discover | Inventory current records, forms, printers, devices and staff roles; choose the tier | Designed, not yet built |
| 2. Configure | Assemble the customer version with AuroraMed Packaging: modules, roles, alert catalog, layout. Test in a synthetic-data environment | In the pilot (v0.2.0, synthetic data) for the Packaging step, synthetic only |
| 3. Install | Scripted, image-based installation of the on-site server and terminals; the clinic supplies electricity and internet | Designed, not yet built |
| 4. Load | Users through the admin console (one at a time today; bulk import planned). Patients by back-entry or standards-based import. Vendor-specific importers: none, and none decided | Designed, not yet built |
| 5. Accept | Scripted acceptance tests for network, hardware, attestation, printer, alert test and backup test, then a go-live review. Never run at a site | Designed, not yet built |
| 6. Run in parallel | Downtime procedures and back-entry support the transition. No parallel-run tooling is specified | Open decision |
| 7. Train | Role-based guides and quick-reference cards are planned; none is written | Designed, not yet built |
Available now
- A synthetic-data demonstration to rehearse workflows.
- The admin console for users, facilities, units, locations and care teams.
- Large-text, high-contrast and reduce-motion preferences.
Not available
- Bulk patient import and any legacy-EHR importer.
- Paper-chart scanning or back-entry tooling.
- Training materials, installation crews and go-live support.
- A published duration or price for installation.
Planning a move?
Tell us what you use today. We will tell you which parts we could and could not help with.