Platform
Roadmap: four waves built, the rest not started
Phase 1 is finished: Waves 1 to 4 are built and tested by the developer on synthetic data, and release 0.5.0 closed it on October 1, 2026. Everything that touches a real outside system is still a simulation, and Phase 2 has not started. We publish no dates for it.
How to read status labels: In the pilot (v0.5.0, synthetic data) Simulated in the pilot (no real external system) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
Four waves done, and what comes after
The order is fixed by dependencies, not by calendar dates. No future dates are promised. Wave dates are the release dates in the changelog.
| Wave | Release | What it added | Evidence |
|---|---|---|---|
| 1 | v0.2.0 · September 30, 2026 Pilot | Sign-in and privileged-user administration, registration, coded lists, chart and live push, alerts and codes, IM and Memo Desk, audit chain, break-glass, AuroraMed Packaging | Developer test runs, listed on the status page |
| 2 | v0.3.0 · September 30, 2026 Pilot Simulated | Server-enforced permission matrix, the server circuit, clinical notes and signing, vitals and flowsheets, orders (CPOE core), lab and imaging (simulated), clinical inbox, forms and consents | Wave 2 report and live test runs recorded in the changelog |
| 3 | v0.4.0 · October 1, 2026 Pilot Simulated | Scheduling, coverage and eligibility (simulated), billing (simulated clearinghouse), on-site hub with sync, downtime mode, backup and restore drill, printing, IM and Memo completion, alert hardening | Wave 3 report; superseded by 0.5.0 the same day |
| 4 | v0.5.0 · October 1, 2026 Pilot Simulated | Clinical decision support (synthetic rules), e-prescribing (simulated pharmacies), FHIR and HL7 (simulated, read-only and outbound), patient portal, a regression pass and coverage re-score | Wave 4 and Phase 1 final reports |
What “built” means here
Built means the code exists, passes the developer’s own tests, and every module is proven by a live self-test on the server circuit. It does not mean ready for real patients: nothing has had an independent review, and the open findings on the Trust Center are still open.
What Phase 1 is not
So nobody assumes more than we have built.
- Not a real lab, imaging, pharmacy, PDMP, clearinghouse or insurer connection: those are simulators inside the hub.
- Not DEA-compliant electronic prescribing of controlled substances (EPCS). Not a licensed drug database.
- Not a certified electronic-signature or compliance system, and not a regulated medical device.
- Not offline-first everywhere: the on-site hub and downtime mode exist, but replication-conflict resolution has no screen yet.
- Not tested on real patients, and not independently penetration-tested.
- Not live for a customer. There is no customer.
After Phase 1: designed or not started
The specification describes these. Items marked Designed have no code in the pilot.
| Area | What it would add | Status |
|---|---|---|
| Privacy operations, key management, AppSec program, compliance artifacts | Breach workflow, key custody and rotation, a formal security program, and the documents a compliance review needs | Designed, not yet built |
| Real integrations | Live lab, imaging, pharmacy and PDMP, clearinghouse, FHIR and HL7 partners behind an interface engine. Today all of them are simulated | Designed, not yet built |
| DEA EPCS and a licensed drug database | Controlled-substance prescribing to the standard, and a licensed interaction and formulary source | Designed, not yet built |
| Documents, fax and immunization registry | Scanned documents, fax in and out, and registry exchange | Designed, not yet built |
| Patient portal extras | Proxy access, text-message sign-in codes, and payments. The portal today needs in-person identity proofing | Designed, not yet built |
| Pager and SMS gateways, real printer drivers | Delivery beyond the app, and printing to real printers beyond the simulated print queue | Designed, not yet built |
| Replication-conflict resolution screen | A guided way to resolve a conflict that pauses on-site and cloud sync | Designed, not yet built |
| Load, chaos and accessibility test programs | Independent test pieces beyond the developer’s own checks | Designed, not yet built |
| Federated ledger | Hashes, consent records and audit events shared across sites; patient records never on the ledger | Designed, not yet built |
| Latin America profiles | Country profiles and the optional strict privacy tier | Designed, not yet built |
| Sealed terminals, read-limiter hardware, transfer between servers, analog timing layer | Hardware and network hardening | Designed, not yet built |
| Transport orders (Elyria) | Optional interface to a separate company | Planned partner integration |
About “percent complete”
We do not publish a completeness percentage. Requirements differ enormously in size, and a single number would say nothing about clinical readiness. The specification catalog lists all 454 requirements one by one instead, with the status the developer’s own re-score gave each on October 1, 2026.
Tell us what should come first
Small clinics tell us what would make the pilot useful. That shapes the order.