Platform
Roadmap: what Wave 1 delivered and what Wave 2 is for
Wave 1 is built and verified on synthetic data. Wave 2 is being built. We publish no dates for it, and we will not mark anything shipped until it is tested.
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
Two waves, and everything after them
The order is fixed by dependencies, not by calendar dates. No dates are promised.
| Wave 1 (v0.2.0) | Wave 2 (v0.3.0) | |
|---|---|---|
| State | In the pilot (v0.2.0, synthetic data) Verified September 30, 2026 on synthetic data | Coming (Wave 2, rolling out) Being built; no test evidence published yet |
| Focus | Sign-in and privileged-user administration, registration, coded lists, audit chain, break-glass, AuroraMed Packaging, live hub | Clinical notes with signing, structured orders (CPOE), lab and imaging simulators, forms, a fuller permission matrix |
| Evidence | Developer test runs (dated, synthetic, internal) listed on the status page and in the changelog | None yet. We will publish a report before any Wave 2 item moves to “In the pilot” |
| Integrations | None live. Results arrive through a simulated internal interface | Simulators only. A simulator is not a connection to a real lab or imaging system |
What Wave 2 is not
So nobody assumes more than we have built.
- Not a real e-prescribing, pharmacy, billing or clearinghouse connection.
- Not HL7, FHIR or DICOM connectivity. FHIR is planned, not started.
- Not offline operation. Continued work without the internet depends on the on-site server, which is designed and not started.
- Not a certification, audit or legal review.
After Wave 2: designed, not started
The specification describes these. None has code in the pilot.
| Area | What it would add | Status |
|---|---|---|
| On-site server and offline operation | A closed server in the clinic that keeps working when the internet drops | 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 |
| Backup and disaster recovery | Tiered backups, restore drills, immutable copies | Designed, not yet built |
| Scheduling and check-in | Appointments, waitlists, reminders | Designed, not yet built |
| Patient portal | Records view, consent, requests, proxy access | Designed, not yet built |
| Billing and claims | Coverage, eligibility, claims and payments | Designed, not yet built |
| Pharmacy and e-prescribing | Medication ordering, dispensing, administration checks | Designed, not yet built |
| Interoperability | HL7 v2, FHIR R4, C-CDA, DICOM behind an interface engine | Designed, not yet built |
| Latin America profiles | Country profiles and the optional strict privacy tier | Designed, not yet built |
| Sealed terminals, read limiter, 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.
Tell us what should come first
Small clinics tell us what would make the pilot useful. That shapes the order.