Cloud healthcare records · synthetic-data pilot
Clinical records and alerts, built small-clinic first.
AuroraMed is a cloud healthcare-records platform with live charts, in-facility messaging, code alerts and a tamper-evident audit trail, designed to start in small clinics and scale to hospitals. Version 0.5.0 (Waves 1 to 4) is a working pilot on synthetic data, with outside connections simulated, and this site says plainly what is built and what is not.
- Synthetic data only
- No patient data needed to evaluate
- Live synthetic demo hub
Design principles we build to (not certifications)
What works in the pilot today
Four waves built, exercised on synthetic data
These features run on the live synthetic demo hub in version 0.5.0. Each one has limits, which are listed on the status page.
Live patient charts Pilot
A nurse enters a vital sign and the doctor's open chart updates live, with reconnect replay. Signed notes and orders sit in the same chart.
Messaging and Memo Desk Pilot
Facility-only direct and group messaging with receipts, plus Memo Desk for long-form internal memos and formal notices that need acknowledgement.
Codes and alerts Pilot
22 editable default code templates, full-screen imminent-threat takeover, acknowledgement rosters, escalation timers and two-person cancel. Alerts reach connected terminals only.
Registration Pilot
Check-digit MRNs, live duplicate warning, unknown-patient registration, two-person merge and unmerge, masked national IDs with audited reveal.
Notes, orders and results Simulated
Signed notes, structured orders and a clinical inbox. Lab and imaging results come from a simulated connector.
Tour →Scheduling and billing Simulated
Booking, check-in, coverage, claims and remittances. The payer side is simulated.
Tour →E-prescribing and portal Simulated
Simulated pharmacies with synthetic decision support (not DEA EPCS), and a patient portal activated in person.
Tour →On-site hub and downtime Pilot
An on-site hub, downtime mode, backup and a restore drill. Tested on synthetic data only.
Tour →Coded lists Pilot
Problems, allergies, medications and immunizations from bundled code-set subsets. Medication reconciliation must decide every active drug before saving.
Audit and break-glass Pilot
A hash-chained audit log with a verify button, VIP flags, and emergency access that needs a reason, expires, alerts privacy staff and forces review.
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
AuroraMed Packaging
One engine, a version of the app for each customer
AuroraMed Packaging assembles a customer-specific version of the app from a signed configuration: which modules appear, who may do what, how alerts are routed and how it looks.
- A 35-module capability catalog; six safety and privacy modules stay locked on, and only the pieces a customer selects are compiled into its app.
- Safety floors cannot be switched off, and are enforced again on the server, so a forged configuration cannot raise privileges.
- Two presets are tested on synthetic data: Small Clinic (light, 25 of 36 pieces on) and Hospital (dark, all pieces on).
- Signed packages are checked for tampering; publishing needs two different operators.
Honest limits
- Custom fields, rollback UI and staged rollout are not built.
- The demo signing key is a demo key and is not production key management.
- Each customer currently means a separate facility on one shared hub, not a dedicated server. Dedicated deployments are planned.
- Customer desktop builds are unsigned and not offered for public download.
What Waves 2 to 4 added
Phase 1 is complete, and Phase 2 has not started
Waves 2, 3 and 4 were released as v0.3.0, v0.4.0 and v0.5.0 between September 30 and October 1, 2026. Each is built and tested by the developer on synthetic data, and a module is Pilot or Simulated only after its live self-test passes. Phase 2 has not started and we publish no dates.
| Wave | Added | Honest limit |
|---|---|---|
| 2 · v0.3.0 | Permission matrix, server circuit, signed notes, vitals, orders, inbox, forms Pilot | Lab and imaging are simulated Simulated |
| 3 · v0.4.0 | Scheduling, on-site hub and sync, downtime, backup, printing, messaging and alert completion Pilot | Coverage, eligibility and billing use a simulated payer side Simulated |
| 4 · v0.5.0 | Patient portal Pilot, decision support, e-prescribing, FHIR and HL7 Simulated | Not DEA EPCS; no real pharmacy, partner or drug database |
Solutions by role
Pick your starting point
The same platform, described honestly for each audience.
Small clinics
The starting point, with installation and equipment sold separately.
Read more →Hospitals
Governance, zones, chain of command and what is still designed.
Read more →Physicians and nurses
What you can do today and what is still to come.
Read more →IT and security
Controls in place, open findings and honest limits.
Read more →Why AuroraMed
How the approach differs, by category
This compares categories of approach, not named products. Each approach has real strengths, and individual products vary.
| Paper and spreadsheets | Traditional on-site suite | Cloud-only service | AuroraMed (design) | |
|---|---|---|---|---|
| Works without internet | Yes | Usually | Usually not | On-site hub and downtime mode, tested on synthetic data only Pilot |
| Small-clinic starting point | Yes | Often heavy | Often yes | The design target Designed |
| Tamper-evident audit | No | Varies | Varies | Hash-chained audit with verify button Pilot |
| Live team alerts | Shouting and phones | Varies | Varies | Code alerts with escalation Pilot |
| Track record and references | Decades | Often long | Varies | None yet. Pilot on synthetic data No claim |
| Independent security review | Not applicable | Varies | Varies | None yet Open |
Fair objections
The doubts you should have, answered
A records system is a serious purchase. These are the objections we would raise ourselves.
“Is this real, or a mock-up?”
The pilot runs: sign-in with MFA, live charts, notes and orders, messaging, alerts, registration, scheduling, an on-site hub and audit. It runs on synthetic patients only. Anything that reaches an outside system is labelled Simulated, and the rest Designed.
See the status page Pilot
“What if the internet goes down?”
An on-site hub keeps alerts and messaging running locally and replicates when the internet returns, and downtime mode supports charting. It is tested on synthetic data only, has never run a real site drill, and a replication conflict has no resolution screen yet.
On-site hub and downtime Pilot
“Are we locked in?”
Ownership of patient data by the clinic and standards-based export are design principles. Export tooling is not built and no contract terms are written yet, so ask for a test export before you commit to anything, from us or anyone.
Risk and exit Designed
“Is it compliant?”
We make no compliance or certification claims. Privacy controls are designed with the intent of the main laws in mind, and nothing has been reviewed by counsel or audited.
What we do and do not claim No claim
“Is it secure?”
There is no independent review yet. We publish our own dated test counts and our open findings so you can judge for yourself.
Security whitepaper Open
“You have no customers. Why now?”
That is correct, and we will not invent logos. An early pilot lets a small clinic influence the design and see every limit first. If you need a proven system today, use one, and use our buyer’s guide to choose well.
Pricing
Prices that scale with the cost of serving you
Pricing is discussed directly with each organisation while terms are being finalised.
Large hospital
for pricing
Scales with servicing, buildout and certified maintenance crews.
Medium clinic
for pricing
Replica and failover profile, in design.
Small clinic
for pricing · up to about 20 patients
Installation and AuroraMed-sold equipment are paid separately. The clinic supplies its own electricity and internet.
Low-risk way to evaluate
Try it without risking a single patient record
The demo runs entirely on synthetic data. You do not need to share patient information, connect any system or sign a long contract to see how it behaves.
- Evaluate with made-up patients only.
- Ask any question: the help center answers 1,000 concerns, including the uncomfortable ones.
- Data ownership and exit are design principles we can discuss openly, with a written agreement to follow when a real pilot begins.
- Open items are published rather than hidden.
Pilot partners
AuroraMed does not have customers yet, so there are no logos or testimonials on this site, and we will not invent any. When a clinic joins the pilot programme, we will show its name and words only with its written permission.
Want to help shape the first version, small clinic first?
Talk to us about the pilotQuestions we hear first
Straight answers
Is AuroraMed a finished product?
Can we put real patient records in it?
Is it HIPAA, LGPD or GDPR compliant?
Does it connect to our lab, pharmacy or insurers?
What does it cost?
Does it work if the internet goes down?
Is it available in Spanish?
Who runs AuroraMed and who are its customers?
See it on synthetic data
Request a walkthrough of the pilot. It takes one email and no patient information.