Product and desktop app
AuroraMed Packaging
The engine that builds customer-specific versions from a signed configuration.
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
C0407What is AuroraMed Packaging?
An engine that authors, validates, previews, signs, ships and builds a customer-specific version of the app from a signed configuration manifest.
C0408What can be switched on or off?
Thirteen modules with dependencies, four of which are locked on for safety and privacy: overview, alerts, audit and settings.
C0409Can a module be hidden but still reachable?
No. A disabled module is not shown and its programming interface answers with an error for that customer, so hiding a menu is never the only control.
C0410Is the configuration signed?
Yes, as a signed package using ECDSA P-256 over canonical JSON. A modified package fails verification. Production signing-key custody is undecided and the demo key is not production grade.
C0411Who can publish a configuration?
The hub requires two different vendor operators, one to propose and another to approve, and it re-verifies and re-validates before applying.
C0412Are there preset configurations?
Two: a Small Clinic preset with a light teal theme and fewer modules, and a Hospital preset with all thirteen modules, longer passwords and a four-level chain of command.
C0413Can a configuration weaken security?
No. Floors such as mandatory multi-factor for privileged tiers, password length and idle lock limits are enforced at validation and again at enforcement.
C0414Can a customer get a branded app?
The engine builds a customer-named portable Windows app and a web bundle. It has not been launched on Windows outside the developer's check.
C0415Does each customer get a dedicated server?
Not in the pilot. Customers are separated as tenants on one hub with tested isolation. Dedicated per-customer deployments and on-site servers are planned, not built.
C0416Can custom fields and reports be added?
Not yet. The element registry beyond the thirteen modules is not built.
C0417Can a configuration be rolled back?
Versions only roll forward today. A rollback interface and staged rollout are not built.
C0418Is a demo mode available for sales?
The pilot is a synthetic-data demonstration hub. A customer-facing demo-mode switch is not documented as built.