Platform
One platform, labelled honestly
AuroraMed is a cloud records system with a syncable on-site hub. This page shows every major area and its status, so you never have to guess what is real. Connections to outside systems are simulated.
What is in the pilot
Version 0.5.0, verified October 2, 2026. Synthetic data only.
Live charts Pilot
Chart entries push live to the clinicians allowed to see that patient: structured vitals, signed notes, orders and results.
Live charts tour →Codes and alerts Pilot
Code catalog, pings, critical results, escalation and full-screen imminent-threat alerts.
Clinical communication →Notes, orders, lab and imaging Simulated
Signed notes, structured orders, a clinical inbox and forms. Lab and imaging connections are simulated.
Tour →Scheduling, coverage and billing Simulated
Booking, check-in, claims and remittances. The clearinghouse and payer are simulated.
Tour →Prescribing and portal Simulated
Simulated e-prescribing with synthetic decision support, and a patient portal activated in person.
Tour →On-site hub and downtime Pilot
An on-site hub, signed sync, downtime mode, backup and a restore drill.
Tour →Server circuit Pilot
Every module is proven by a live self-test after each deploy.
Server circuit →Modules Pilot
All 36 pieces built in Waves 1 to 4, with their status.
Modules →AuroraMed Packaging Pilot
Assemble a customer-specific app from a signed configuration with locked safety floors and a 35-module catalog.
AuroraMed Packaging →Desktop and tablet Pilot
Windows portable app and a tablet web build from one code base.
Desktop app →Security controls Pilot
Deny-by-default roles, MFA, lockout, audit chain, break-glass. With open findings published.
Trust Center →Architecture Designed
A cloud hub plus an on-site hub are built. The federated ledger, sealed terminals and a hardware limiter are designed, not built.
Architecture →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
What is not in the pilot
Stated once, clearly.
- Any real outside connection: laboratory, imaging, pharmacy, prescription-monitoring, clearinghouse, insurer, FHIR or HL7 partner. All are simulated inside the hub Simulated
- DEA-compliant electronic prescribing of controlled substances (EPCS), and a licensed drug-interaction database Designed
- Telehealth, patient payments, proxy access and text-message sign-in Designed
- Medication administration with barcode checks (eMAR) Designed
- A screen to resolve a replication conflict between the on-site and cloud hubs Designed
- Privacy operations, key management, a security program and compliance documents Designed
- Spanish or Portuguese product screens (English only today)
- Any certification, audit or real patient data No claim