Migration and onboarding
Migration paths
What is built, what is planned, and what is open.
How to read status labels: In the pilot (v0.2.0, synthetic data) Simulated in the pilot Coming (Wave 2, rolling out) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0240Can we import our existing patients in bulk today?
Not yet. Bulk import is a listed gap. The pilot has a registration form with duplicate warnings, and an administration console for users and locations.
C0241How will data migration work?
The design calls for scripted image-based installation, interface mappings, signed configuration bundles and back-entry, but no migration tooling exists yet.
C0242Can we move from paper records?
Initial chart build from paper is a normal onboarding step and the design supports document capture and back-entry. Tooling is not built.
C0243Can we migrate from another EHR?
Through standards such as HL7 and FHIR exchange and document import, which are planned, not built. No vendor-specific importers exist.
C0244Which legacy systems will importers exist for?
Undecided. No connector to any legacy EHR is built, and the catalog research of major vendors informs future priorities only.
C0245How is go-live decided?
A go-live readiness review after scripted acceptance tests for network, hardware, attestation, printer, alert test and backup test is specified. It has not been run at any site.
C0246Can we run old and new systems in parallel?
Downtime-mode procedures and back-entry support transitions, but no parallel-run tooling is specified.
C0247Can we try it before committing?
A synthetic-data demonstration is available on request. Real patient data must not be entered into the pilot.
C0248How long does installation take?
No duration is published. Installation is a scripted checklist, and effort estimates exist only as internal planning ranges.
C0249Who installs the equipment?
The small tier pays installation and equipment sold by AuroraMed, and the clinic supplies electricity and internet. Installation crews and certified maintenance are planned, not yet staffed.
C0250Is there a training or test environment?
The design keeps test and training environments with synthetic data only and blocks restoring production data into them.
C0251Can templates and forms be loaded at setup?
A forms engine is planned. The repository holds mock form and contract drafts as design references for it.
C0252How are users loaded at launch?
The pilot's administration console creates users one at a time with forced password change and two-person approval for privileged roles. Bulk import is planned.
C0253Can a clinic set its own facility structure?
The pilot supports facilities, units, locations, a record-number prefix and care teams. Beds and rooms depth is limited.
C0254Can configuration move from test to production safely?
Signed configuration bundles for promotion are designed. The Packaging engine signs manifests today for pilot tenants.
C0255How long is parallel support after go-live?
Not defined. The support model for each tier is an open item.
C0256Do we need new hardware?
The small tier uses AuroraMed-supplied terminals and a one-cabinet server. The pilot itself runs on ordinary desktops and tablets with a browser or the desktop app.
C0257What about our existing printers?
Printers must be wired and non-networked on a closed loop in the design. Existing networked printers would not meet that rule.
C0258Can we bring our own tablets?
The design excludes personal devices from clinical services. Tablet hardware choices are an open decision.