Transparency
What's built today
Every capability, its status and its limits. Version 0.5.0 (Waves 1 to 4, Phase 1 complete), verified October 2, 2026. The pilot runs on synthetic data only.
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
Communication and alerts
| Capability | Status | Limits |
|---|---|---|
| Live chart push | In the pilot (v0.5.0, synthetic data) | Alerts and pushes reach connected clients only. |
| Facility messaging, patient-linked threads | In the pilot (v0.5.0, synthetic data) | Not end-to-end encrypted. IM text limit is 4,000 characters. |
| Memo Desk: drafts, due dates, retention and holds | In the pilot (v0.5.0, synthetic data) | Memo body limit 100,000 characters. No rich text, folder search or delegation. |
| Codes and alerts (22 default templates), drills and timing reports | In the pilot (v0.5.0, synthetic data) | No pager, SMS or overhead paging. Timers are example values. |
| Two-person cancel of imminent-threat alerts | In the pilot (v0.5.0, synthetic data) | Who counts as the two people is a setting; the owner’s default is still pending. |
| Critical result alerts | Simulated in the pilot (no real external system) | Results come from a simulated lab and imaging connector. |
Patient record and orders
| Capability | Status | Limits |
|---|---|---|
| Registration, duplicate warning, two-person merge and unmerge | In the pilot (v0.5.0, synthetic data) | No national-ID validators; matching untuned on real data; no ADT merge or FHIR linkage messages. |
| Coded problems, allergies, medications, immunizations | In the pilot (v0.5.0, synthetic data) | Bundled code sets are subsets (ICD-10-CM 14,594 codes, RxNorm 1,367, LOINC 50 curated). No SNOMED CT or CPT. |
| Structured vitals, calculators and NEWS2 | In the pilot (v0.5.0, synthetic data) | Synthetic patients only. |
| Clinical notes with templates, signing, co-signing and addenda | In the pilot (v0.5.0, synthetic data) | Synthetic patients only. |
| Orders (CPOE core), order sets, verbal-order read-back | In the pilot (v0.5.0, synthetic data) | Not a licensed order catalog. |
| Lab and imaging connectors, results and critical-result chain | Simulated in the pilot (no real external system) | Simulated HL7 v2 inside the hub; no real laboratory or imaging system. |
| Clinical inbox and tasks | In the pilot (v0.5.0, synthetic data) | Synthetic data only. |
| Forms, consents and e-signature | In the pilot (v0.5.0, synthetic data) | 36 curated mock templates. A drawn signature is not a certified e-signature. |
| Clinical decision support | Simulated in the pilot (no real external system) | Synthetic rule table (about 40 drugs, 12 interactions); not a licensed drug database. |
| E-prescribing and pharmacist verification | Simulated in the pilot (no real external system) | Simulated pharmacies and monitoring check; not DEA EPCS. |
| Audit chain and verify button | In the pilot (v0.5.0, synthetic data) | Tamper-evident, not write-once storage. |
| VIP and break-glass | In the pilot (v0.5.0, synthetic data) | Compartments are flags plus an attested purpose, not a consent engine. |
| Printing: Code 128 wristbands, labels, chart prints | Simulated in the pilot (no real external system) | Logged and rate-limited queue to a simulated printer; no real printer driver. |
Front office, billing and patients
| Capability | Status | Limits |
|---|---|---|
| Scheduling, check-in and rooming | In the pilot (v0.5.0, synthetic data) | Synthetic data only. |
| Coverage and eligibility | Simulated in the pilot (no real external system) | Simulated 270/271-style check; no payer connection. |
| Charges, claims, remittance and statements | Simulated in the pilot (no real external system) | Simulated clearinghouse; synthetic fee schedule and code sets; no licensed CPT. |
| Patient portal | In the pilot (v0.5.0, synthetic data) | In-person identity proofing only; no text-message codes, proxy access or payments. |
| FHIR R4-style read-only interface and HL7 ADT out | Simulated in the pilot (no real external system) | No partner connected; inbound HL7 is validated and not applied. |
Platform, operations and security
| Capability | Status | Limits |
|---|---|---|
| Permission matrix (23 role classes by 103 actions) | In the pilot (v0.5.0, synthetic data) | Enforced on the server and tested on synthetic roles. |
| Server circuit and deploy gate | In the pilot (v0.5.0, synthetic data) | Proves each module with synthetic data, not that an outside system exists. |
| Multi-tenant hub (four synthetic tenants) | In the pilot (v0.5.0, synthetic data) | One shared cloud hub. Dedicated deployment per customer is planned. |
| AuroraMed Packaging (35-module catalog, two presets, signed packages) | In the pilot (v0.5.0, synthetic data) | Demo signing key; no rollback UI or staged rollout; builds unsigned. |
| On-site hub and signed, encrypted replication | In the pilot (v0.5.0, synthetic data) | Conflicts pause sync and have no resolution screen; secrets are demo-grade. |
| Downtime mode, sealed downtime reports, offline read cache | In the pilot (v0.5.0, synthetic data) | The cache is in memory only and read-only. No uptime figure is published. |
| Backup, restore drill, promote with two people | In the pilot (v0.5.0, synthetic data) | Promote records the decision only. No off-site or immutable copy. |
| MFA (TOTP), lockout, idle lock, two-person privileged changes | In the pilot (v0.5.0, synthetic data) | Passwords use PBKDF2, not Argon2id. No FIDO2 or single sign-on. |
| Field encryption of national IDs and MFA secrets | In the pilot (v0.5.0, synthetic data) | No key rotation, no per-tenant keys yet. |
| Federated ledger, sealed terminals, hardware read limiter, analog timing layer | Designed, not yet built | Designed, not built. Effectiveness of screens and hardware is untested. |
| Real laboratory, pharmacy, clearinghouse, FHIR and HL7 connections; DICOM; SMS or pager | Designed, not yet built | None built. Every connection above is a simulation. |
| Privacy operations, key management, security program, compliance artifacts | Designed, not yet built | Not started (Phase 2). |
| Spanish or Portuguese product screens | Not offered / no claim made | English only. Spanish and Portuguese website pages are marketing previews. |
Checks we ran, and what they are
Run by the developer on synthetic data between September 30 and October 1, 2026, and listed without being combined: 137 unit tests pass (re-run on October 2, 2026); end-to-end suites of 108, 201, 64, 114, 93 and 85 checks pass on the live hub; a permission-matrix run of 8,565 checks had none failed; security probes of 34, 105, 96 and 58 checks found no breach; click-throughs of 37, 25, 28 and 26 of 27 steps passed; a scan of 427 screens found no problems; and the server circuit was green with all 36 pieces on three tenants. These are internal tests. They are not an audit, not a penetration test, and not proof for real patient data.
Open security findings (published, not hidden)
- The demo signing private key is in the demo code base; production key custody is undecided.
- Site secrets for sync and the backup signing key are demo-grade.
- Passwords use PBKDF2-SHA256, not Argon2id, and there is no breached-password check.
- The field-encryption key has no rotation and no per-tenant keys.
- Privacy compartments are flags, not a legal consent engine.
- The audit chain is not write-once and has no external anchor.
- There is no per-IP rate limit.
- One live click-through step (an on-screen message for a too-short override reason) failed and its cause is unresolved.
Our own review states the pilot must not hold real patient data until these are addressed and an independent review has been done.
Questions about a specific item?
Search all 1,000 answered concerns, or ask us.