Training Simulator with Incident Digital Twin

Overview#

Call-takers, dispatchers, and crews learn fastest when they re-run the hardest calls their service has actually handled, in a sandbox where mistakes are safe. The Training Simulator with Incident Digital Twin replays de-identified historical incidents at original timing so trainees experience the real workflow without touching live data.

The module streams the original call audio, AVL pings, and dispatch events from a recorded incident into a sandbox tenant, lets the trainee handle the call through the production console, and then scores the trainee's decisions against the recorded outcome. Certification and recertification results are captured in the audit trail for HSE clinical governance.

Last Reviewed: 2026-05-05 Last Updated: 2026-05-05

Key Features#

Incident Digital Twin Replay: Re-stream the original call audio, AVL pings, and dispatch events from a real incident at the original timing, so trainees handle the call as it actually unfolded.
Sandbox Tenant Isolation: All training-mode incidents live in a dedicated sandbox tenant scoped by organization_id, with no co-mingling with production data at any point in the pipeline.
De-identified Replay Source: Replays are sourced only from fully de-identified historical incidents or synthetic fixtures, with caller, patient, and crew identifiers removed before the replay package is built.
Decision Scoring Against Recorded Outcome: Trainee call-handling, triage, and dispatch decisions are compared to the recorded outcome of the original incident, surfacing where the trainee diverged and why it matters.
Visible Training-Mode Indicator: A persistent training-mode banner is enforced in the call-taker console, dispatcher view, and responder mobile app so no participant can mistake a drill for a live event.
Certification and Recertification Audit Trail: Completion records, scores, and reviewer sign-offs are recorded against trainee identity in the audit trail for clinical governance and recertification cycles.
Same Workflow as Production: Replay events use the same CloudEvents 1.0 envelope and the same canonical incident model as production, so trainees practise on the exact console and procedures they use on shift.
Federated Simulation Ready: Where joint exercises require multiple simulators to share a synthetic scenario, the engine can participate in federated runs without changing the trainee experience.

Use Cases#

Call-Taker Onboarding: A new call-taker works through a curated set of de-identified historical calls in the sandbox tenant before being rostered onto live calls.
Dispatcher Recertification: A dispatcher re-runs a complex multi-vehicle incident from the prior year and earns a recertification record stamped into the clinical governance audit trail.
Crew Refresher After Critical Incident: An ambulance crew replays a difficult cardiac or paediatric case as a digital twin to review decision points without exposing the original patient or family.
Cross-Role Joint Exercise: A call-taker, a dispatcher, and a responder mobile user run the same replayed incident together to practise hand-offs across the full chain.
HSE Clinical Governance Review: A training officer pulls the audit trail of a trainee's certification attempts to evidence competence at recertification time.
Major Incident Drill: A federated simulation run pulls in a de-identified mass-casualty replay so multiple agencies can rehearse coordinated response on a shared synthetic picture.

Integration#

Production Console Reuse: Trainees use the same call-taker, dispatcher, and responder mobile interfaces as production, with a training-mode banner enforced on every surface.
Pseudonymisation Vault: Historical incidents pass through the vault before becoming a replay source, ensuring caller, patient, and crew identifiers never leave the production tenant in identifiable form.
CloudEvents Replay Bus: The replay engine emits events on the same CloudEvents 1.0 envelope used in production, so the canonical incident model and downstream consumers behave identically in training.
Existing ePCR Training Workflow: The simulator complements the existing ePCR training app by extending training coverage from clinical record practice into the full call-handling and dispatch workflow.
Learning Record Store: Trainee experience records flow to a learning record store using xAPI statements, with optional SCORM completion records where HSE certification requires it.
Identity and Audit: Certification outcomes are recorded against the trainee's existing platform identity and written into the same audit trail used for clinical governance evidence.
Federated Simulation Bridge: Where a joint exercise requires multiple simulators, the engine can speak DIS, HLA, or OpenLVC so external defence and emergency services simulators can join the same scenario.

Open Standards#

IEEE 1278.1 DIS: Distributed Interactive Simulation primitives are used so the replay engine can interoperate with established defence and emergency services simulators.
HLA IEEE 1516: High Level Architecture support enables federated simulation runs where multiple training systems must share a synthetic scenario.
OpenLVC: Open Live Virtual Constructive interoperability allows the simulator to take part in mixed live, virtual, and constructive exercises.
CloudEvents 1.0: Replay events match the production envelope, so trainees experience the same canonical incident model and the same downstream behaviours as a live shift.
SCORM 2004: Training content packaging and completion records align with SCORM where HSE certification or external learning management systems require it.
xAPI (Tin Can): Learner experience records are emitted as xAPI statements so progress, attempts, and outcomes can flow to an external learning record store.
ISO/IEC 19796-1: Quality management for learning, education, and training underpins the certification and recertification process.
GDPR: Pseudonymisation requirements are honoured at the replay-source boundary, ensuring training never exposes identifiable caller, patient, or crew data.