Educational simulation environment. Do not enter real patient information. AI content supports learning and reflection; it does not replace clinical judgment, local policy, or escalation pathways.

Administration

Configuration, roles and safety operations. Release 1 runs on synthetic or institutionally de-identified data only.

Access

Roles and outcomes

  • Nursing student / staff nurse

    Practise noticing, interpreting, responding and reflecting in a case.

  • Nurse educator / preceptor

    Assign scenarios, review reasoning traces, give rubric-based feedback.

  • Clinical nurse specialist / informaticist

    Curate evidence cards, pathways, terminology mappings, scenario quality.

  • Unit leader / QI lead

    See aggregate, de-identified analytics — never individual patient records.

  • AI-governance administrator

    Maintain the registry, approval gates, change history and feedback review.

Data state

Environment controls

Current data state
Synthetic / educational simulation
Production record access
Disabled — not available in release 1
Free-text chart import
Blocked pending de-identification review
EHR ingestion
Not connected. No silent ingestion path exists.
Regulatory status
None claimed. Any production clinical deployment requires formal regulatory, legal, clinical and organisational review.
Safeguards

Technical safeguards for future deployment

  • Access control

    Role-scoped access, minimum necessary for the stated purpose.

  • Audit controls

    Append-only trace of scenario, report and export activity.

  • Integrity

    Change history on every registered artefact and evidence card.

  • Authentication

    Named accounts; no shared educator logins.

  • Transmission security

    Encrypted transport for all traffic.

A prototype is not compliant merely because it has login and encryption. Compliance depends on the deploying organisation, its contracts, policies, risk analysis and operating controls.

Safety operations

Feedback and incident reporting

Anyone can report a concern about content, a signal, a mapping or an export. Reports are routed to the named artefact owner and recorded in the registry change history.

Alerts are never the sole safety mechanism, and audit trails cannot be deleted.