Luna LXD
Home / Work / Sepsis: Recognise & Respond
Healthcare organisation · placeholder

Sepsis: Recognise & Respond.

A branching clinical scenario that puts the learner at the bedside of a deteriorating patient — and lets them feel, safely, the cost of recognising sepsis too late.

The brief

Make the stakes
feel real.

Sepsis training is often a list of criteria to memorise. The client wanted something that changed behaviour — a module where clinicians practised the actual decision: notice the early signs, escalate in time, or watch a manageable situation become a crisis.

That meant a scenario with consequences. Choices had to branch into meaningfully different outcomes, with time pressure that mirrored the ward, and debriefs that explained why a path went the way it did.

It also had to stay rigorously accessible — a timed, branching interaction that still works fully by keyboard and screen reader.

25m
Run time
L3
Build level
4
Branching paths
AA
WCAG 2.1 target
lunalxd.com.au/sepsis/scenario
Sepsis · Bed 4
14:20 · Obs just charted
Temp 38.9, HR 116, BP dropping. Your move?
Escalate nowRecheck in 30Reassure
Decide →
Interaction
Timed branching
The shape

One patient,
many endings.

Format
Single-patient branching scenario with timed decision points
Feedback
Immediate consequence plus reflective debrief on each path
Assessment
Decision quality tracked across the scenario, not a quiz at the end
Accessibility
Keyboard-operable, screen-reader friendly, reduced-motion safe

Project details

  • Client · Healthcare organisation (placeholder)
  • Role · LXD & Storyline build
  • Run time · ~25 minutes
  • Build level · L3 · Branching
  • Audience · Ward & acute-care nurses
  • Output · SCORM package

Tools

  • Articulate Storyline
  • Affinity Designer
  • Figma
  • Clipchamp

Skills

  • Scenario & branching design
  • Clinical content authoring
  • Interaction & motion design
  • Accessible interaction patterns
  • SCORM packaging
Inside the build

Selected screens.

On-brand mockups — illustrative of the build style, not client screenshots.

My response to the briefApproach

How it came together.

Rather than teach the sepsis criteria and then test them, the module drops the learner straight into a shift. A single patient's condition evolves in response to their decisions, so the criteria are learned in the place they'll actually be used — under mild time pressure, with incomplete information.

Each ending is followed by a debrief that connects the outcome back to the clinical reasoning, turning even a "wrong" path into a teaching moment.

Storyline drove the branching logic, with variables tracking the quality of decisions across the scenario rather than a single end-of-module score. A restrained countdown created urgency without panic, and the interface kept the obs chart visible so learners reasoned from data, not memory.

Visually, a calm clinical palette with the Luna accent system kept the focus on the patient. Motion was minimal and purposeful — a pulse on changing vitals, a gentle transition between scenes.

Timed, branching interactions are exactly the kind that often quietly exclude learners using assistive technology. Keeping the scenario fully keyboard-operable and screen-reader friendly — without softening the time pressure that made it effective — took deliberate design and testing.

Balancing realism with fairness was the other challenge: paths had to feel consequential without punishing reasonable judgement calls, so the debriefs do real work explaining nuance.

Start a project

Want a scenario that sticks?