All demonstrations
Health and care · demonstration
Shared CT scanner capacity
Is reporting capacity, portering or scanner time holding up emergency and ward requests?
The question tested
Emergency and ward requests join a shared CT pathway. The comparison tests an additional radiologist against the same fixed simulation seed.
Show how emergency and inpatient demand compete for a single diagnostic scanner and reporting team.
Simulation replay
Use the timeline to inspect the stored baseline run.
Stored comparison
Baseline compared with: Add one radiologist
| Measure | Baseline | Add one radiologist | Change |
|---|---|---|---|
| CT queue wait | 238.3 minutes | 238.3 minutes | 0.0 minutes |
| Reporting queue wait | 56.8 minutes | 0.0 minutes | -56.8 minutes |
| Radiologist utilisation | 97.1% | 61.0% | -36.1 points |
Illustrative financial outputs
| Measure | Baseline | Scenario | Change |
|---|---|---|---|
| Total cost | £11,306 | £11,626 | +£320 |
| Total revenue / value | £9,935 | £10,785 | +£850 |
| Net value | £-1,371 | £-840.5 | +£530 |
Stored run references: net_6a2556_single_run_baeee4 / net_6a2556_single_run_817187
Current model assumptions
- Emergency and ward requests are separate start points so the replay shows two streams merging into one CT queue.
- Radiology reports clear 65% of requests and admit 35%, giving the dashboard two terminal outcome counts.
Basis and limitations: Illustrative demonstration using synthetic demand, durations and costs. It does not represent a named hospital or a client engagement.
Have a similar capacity question?
We can model your actual process, demand and constraints, then test practical alternatives before you commit resources.
Discuss your process