Healthcare Management Simulation: The Decision a Dashboard Cannot Measure

Training in healthcare management is usually built at two extremes: classroom teaching that transmits protocol and regulation on one side, and years of on-the-job experience on the other. The gap between them shows up on the morning a new manager is left alone for the first time. What characterises that morning is not one difficult decision but a set of tasks that all arrive at once and all look urgent. The Healthcare Management scenario in SimAna Decision Box fits that morning into a single session. In this article we examine how the scenario is built and what the inbox format measures that a dashboard cannot.

One day, one inbox, twenty decisions

The participant plays the Deputy Chief Physician of a 200-bed general hospital, responsible for its operational management, patient safety and clinical quality. The session lasts sixty minutes and covers a simulated working day: the first email lands early in the morning, the closing email arrives in the afternoon.

The agenda is a hospital's real agenda. Four surgical site infections appear in the surgical ward within seventy-two hours, three of them from the same operating room. The head nurse reports a critical nursing shortage. The emergency department overflows. The budget collides with a deferred medical-equipment investment. A medication-error incident report arrives. Gap areas remain in the JCI accreditation preparation. A patient complaint turns into legal risk. The day also holds an ethics consultation request on an end-of-life decision and a telehealth pilot project.

Each of the twenty emails carries three response options and the choice cannot be taken back. As in a real inbox, the decision made is the decision that moves things forward.

Eight roles, one desk

The emails do not come from a single source. The scenario's eight characters represent eight different legitimate interests pressing on a manager's desk in a hospital:

The purpose of this design is not variety but conflict. When the head nurse sends an urgent staffing request while legal counsel wants an answer on a pending file, the participant is forced to make a choice. Which one is taken first, which is delegated and which is left waiting is the session's real data.

The document is there to verify the claim

Four hospital documents sit on the scenario's shared drive and can be opened throughout the session: the infection control protocol for surgical site infection, the nurse staffing and shift status table, the JCI accreditation gap checklist and the monthly hospital quality indicators.

These documents are not scenery. The infection protocol states that the normal surgical site infection rate is one to two cases a month and that four cases in seventy-two hours means a suspected outbreak. In other words, the phrase "this could be an outbreak" in the morning's first email is a claim the participant can verify. In the same way the staffing table shows the current nurse headcount, the budgeted headcount and the day and night ratios by unit; whether there is a measurable gap behind the head nurse's phrase "critical level" is something the participant reads there.

That is the behaviour being measured: did the participant decide by verifying a claim against a document, or by trusting the tone of urgency in an email? This distinction never appears on a dashboard. A dashboard holds only the outcome; an inbox holds the path to the outcome. The scenario's content maintenance follows the same principle: when a number in a document contradicts a number in an email, that is not treated as a deliberate consistency test but as a content error and corrected — because a participant who opens a document to verify something must find a reliable source there.

Five competencies and an unequal weight

The scenario measures five competencies: patient safety, resource management, quality improvement, ethical decision-making and crisis management. How many points each response option writes to each competency is fixed while the scenario is authored; no human judgement enters the session result.

The weights are not equal: patient safety carries one and a half times the weight of the other four. This is a healthcare organisation's own ordering of values written into the scoring, and it matters, because without weighting the resulting number describes not the participant but the way the scenario happens to be written. In one scenario the total points available for patient safety can be several times the total available for ethical judgement; raw percentages are then not comparable across competencies. Weighting and predefined anchors solve that problem, which is why the score is built on the same logic on the Field Operations side.

The decision writes the story

Decision Box runs on a branching scenario engine. When a response is selected, one or more of four things is triggered: points are written to a measured competency, a new email lands a few minutes later, an instant message arrives from a character, or immediate feedback is shown to the participant.

The instant messages are the most instructive part of this structure, because they bring the field consequence of a decision back within the session. When the participant chooses a bridging solution for the nursing gap, the message from the head nurse confirms the work done while also naming its limit: as long as headcount stays where it is, this is a bridge and not a fix. This is the sentence an instructor would say at the end of a session, moved inside the session, and it is how experiential learning tools shorten the feedback loop.

Healthcare is a larger part of the library than it looks

The Decision Box library holds twenty-two ready scenarios and only one of them carries "Healthcare Management" as its category. Look at the organisation each is set in, however, and the picture changes: the business analytics scenario is set in a company selling patient management software and health data analytics to hospitals, the cultural awareness scenario in a medical device manufacturer producing pacemakers and stents, the ethical decision-making scenario in a generic drug maker supervised by the medicines authority, and the exporting scenario in a medical supply company exporting surgical materials and orthopaedic implants.

Five scenarios, roughly a quarter of the library, are set in the health ecosystem. For a hospital group or a medical company this makes more than a single sector scenario usable: within the same framework it is possible to measure ethics, supply, data and culture in a healthcare context too.

Two lenses, two different questions

SimAna's healthcare portfolio consists of two products and they are not alternatives to each other. They look at the same hospital from two different heights:

Using the two in sequence in a management development programme covers a wider competency surface than either product alone; which product answers which need is treated separately.

Conclusion

Among business simulations the inbox format looks unusually modest: there is no live scoreboard and no quarterly balance sheet. What it measures, though, is the operation that fills most of a hospital manager's day — deciding which of the simultaneous demands is taken first, and doing so while real evidence is available. What distinguishes the Healthcare Management scenario is that it puts the evidence in the participant's hands and records whether they used it. That is one of the plainest and hardest behaviours a training tool can measure.