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

Training and staff adoption

Staff adoption

How the design tries to reduce friction and support learning.

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

C0259Will staff need a lot of training?

Training depends on scope. The design lists role-based user guides, quick-reference cards and a competency curriculum, but none has been produced. The pilot is small enough to learn from its own screens.

Designed, not yet builtPermalink

C0260Are there training materials?

Planned deliverables include clinical user guides by role tier, quick cards for tablets, alerts and downtime, and an administrator guide. They are not written yet.

Designed, not yet builtPermalink

C0261How does the design handle shared-login habits?

By preventing shared credentials technically, while keeping security friction low, since clinics have variable IT literacy and high turnover.

Designed, not yet builtPermalink

C0262Can staff with large text needs use it?

The pilot has large-text, high-contrast, light theme and reduce-motion preferences.

In the pilot (v0.2.0, synthetic data)Permalink

C0263Are alerts easy to recognise under stress?

Alerts use colour plus pattern plus plain text, so they do not rely on colour alone, and emergency alerts take over the full screen with a deliberate acknowledgement.

In the pilot (v0.2.0, synthetic data)Permalink

C0264Is the touch target large enough for gloved hands?

Not yet: buttons in the pilot are 36 px against a 48 px target in the specification. It is a known, unfixed defect.

Open decisionPermalink

C0265Are there usability metrics?

Time to chart, tasks per session and usability score per release are planned measures. None has been collected.

Designed, not yet builtPermalink

C0266Can I set the screen language for each user?

Localization is a specification target. The pilot screens are English only.

Designed, not yet builtPermalink

C0267Can the front desk and nurses see different screens?

Yes: navigation and permissions follow the role tier and the tenant's manifest.

In the pilot (v0.2.0, synthetic data)Permalink

C0268How are nurses supported on handoff?

A nursing handoff feature is designed in the nursing module. It is not built in the pilot.

Designed, not yet builtPermalink

C0269How does the system reduce typing?

Type-ahead over coded lists exists in the pilot. Templates, order sets and ambient documentation are planned, with AI off by default.

Designed, not yet builtPermalink

C0270Is there a patient-facing guide?

Patient education content is part of the planned portal and forms library. Nothing is published.

Designed, not yet builtPermalink

C0271Who supports super-users?

Support for each tier is undecided; escalation paths and severity levels are designed.

Designed, not yet builtPermalink

C0272Can staff practice without real patients?

Yes. Everything in the pilot uses synthetic, clearly labelled records, which suits practice and demonstrations.

In the pilot (v0.2.0, synthetic data)Permalink

C0273How are drills supported?

Code alerts support drill mode in the pilot, and the design calls for unit-level downtime drills.

Designed, not yet builtPermalink
See the synthetic-data demo first.Request a demo