AuroraMed v0.5.0 is a synthetic-data pilot. See exactly what's built →

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.

Illustration of a clinic chart with live alert and audit chain A stylised patient chart card with vital-sign lines, a live update tag, a stacked alert banner and a linked chain of audit blocks. All content is illustrative and synthetic. LIVE Critical result (synthetic) Acknowledge to continue #0041a9f3…c1 #00427be0…4d #0043d21c…8a Hash-chained audit log (pilot) · synthetic data only

Design principles we build to (not certifications)

Deny by defaultAccess follows role, care relationship and purpose.
Tamper-evidentPer-clinic audit chain with a verify button.
MFAOn by default for privileged roles in the pilot.
Labelled honestlyEvery capability is marked Pilot, Simulated, Designed or Open.
These describe how the pilot is built. They are not audits, ratings or third-party attestations. No independent security review has been done.

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.

WaveAddedHonest limit
2 · v0.3.0Permission matrix, server circuit, signed notes, vitals, orders, inbox, forms PilotLab and imaging are simulated Simulated
3 · v0.4.0Scheduling, on-site hub and sync, downtime, backup, printing, messaging and alert completion PilotCoverage, eligibility and billing use a simulated payer side Simulated
4 · v0.5.0Patient portal Pilot, decision support, e-prescribing, FHIR and HL7 SimulatedNot DEA EPCS; no real pharmacy, partner or drug database

Roadmap · Changelog · All 36 modules

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.

Comparison of approaches. General statements about other approaches may not apply to a particular product. Verify with each vendor.
Paper and spreadsheetsTraditional on-site suiteCloud-only serviceAuroraMed (design)
Works without internetYesUsuallyUsually notOn-site hub and downtime mode, tested on synthetic data only Pilot
Small-clinic starting pointYesOften heavyOften yesThe design target Designed
Tamper-evident auditNoVariesVariesHash-chained audit with verify button Pilot
Live team alertsShouting and phonesVariesVariesCode alerts with escalation Pilot
Track record and referencesDecadesOften longVariesNone yet. Pilot on synthetic data No claim
Independent security reviewNot applicableVariesVariesNone yet Open

Read the full buyer’s guide and evaluation checklist

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.

Talk to us about the pilot

Pricing

Prices that scale with the cost of serving you

Pricing is discussed directly with each organisation while terms are being finalised.

Large hospital

Contact us

for pricing

Scales with servicing, buildout and certified maintenance crews.

Medium clinic

Contact us

for pricing

Replica and failover profile, in design.

Where we start

Small clinic

Contact us

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 pilot

Questions we hear first

Straight answers

Is AuroraMed a finished product?
No. Version 0.5.0 is a working pilot that runs on synthetic (made-up) data. Waves 1 to 4 (Phase 1) are built, including notes, orders, scheduling, billing, e-prescribing, a patient portal and an on-site hub, but every connection to an outside system is simulated and nothing has been used with a real patient. The status page lists what is built, what is simulated and what is not.
Can we put real patient records in it?
No. The pilot must not hold real patient data. Several security findings from our own review are still open, and no independent security review has been done. Use the demo to evaluate workflows with synthetic data.
Is it HIPAA, LGPD or GDPR compliant?
We make no compliance or certification claim. We design against the ideas behind these rules (minimum necessary access, audit, consent, fast record access), but nothing has been legally reviewed or audited. See Privacy and compliance.
Does it connect to our lab, pharmacy or insurers?
Not today. Every external connector in the pilot (lab, imaging, pharmacy, clearinghouse, FHIR and HL7 partners) is simulated inside the hub, and none is connected to a real system. See Integrations.
What does it cost?
Please contact us for pricing. The model scales with the cost of serving each site: small clinics are the starting point, with installation and equipment sold separately. Terms are still being decided. See Pricing.
Does it work if the internet goes down?
In part. An on-site hub keeps alerts and messaging running when the internet is down, and downtime mode supports charting. It is tested on synthetic data only, we publish no uptime figure, and a replication conflict has no resolution screen yet.
Is it available in Spanish?
The product is English only today. Spanish pages on this website are a preview translation of key marketing pages, not a Spanish product.
Who runs AuroraMed and who are its customers?
AuroraMed is at pilot stage and has no customers to name. We will not show logos or testimonials until a real pilot partner gives written permission.

More: 1,000 answered concerns · search the help center

See it on synthetic data

Request a walkthrough of the pilot. It takes one email and no patient information.

See the synthetic-data demo first.Request a demo