|
| 1 | +--- |
| 2 | +title: "Multidisciplinary analytical pipelines: Productionising a business critical simulation model" |
| 3 | +author: |
| 4 | + - "[Chris Beeley](mailto:chris.beeley1@nhs.net)" |
| 5 | +date: 2025-12-04 |
| 6 | +date-format: "D MMMM YYYY" |
| 7 | +format: |
| 8 | + revealjs: |
| 9 | + theme: [default, ../su_presentation.scss] |
| 10 | + transition: none |
| 11 | + chalkboard: |
| 12 | + buttons: false |
| 13 | + preview-links: auto |
| 14 | + slide-number: false |
| 15 | + auto-animate: true |
| 16 | + footer: | |
| 17 | + Learn more about [The Strategy Unit](https://www.strategyunitwm.nhs.uk/) |
| 18 | +--- |
| 19 | + |
| 20 | +## Intro |
| 21 | + |
| 22 | +* This presentation is about building a model to predict the future |
| 23 | +* Doing it well required high quality collaboration from a range of staff in different teams with very different skillsets |
| 24 | +* I think the stuff "around" the modelling is non-obvious and this presentation is intended to help others treading a similar path |
| 25 | + |
| 26 | +## Why? |
| 27 | + |
| 28 | +* New Hospital Programme came to the Strategy Unit c.2020 |
| 29 | +* Predict demand for the future of the hospitals c.2041 |
| 30 | +* We built on existing work and knowledge in the SU as well as the literature |
| 31 | +* I was not here! |
| 32 | + |
| 33 | +## The principles |
| 34 | + |
| 35 | +* Probabilistic |
| 36 | +* [Transparent and open source](https://www.strategyunitwm.nhs.uk/news/transforming-hospital-planning-open-source-demand-and-capacity-model) |
| 37 | +* Collaborative |
| 38 | +* Reproducible |
| 39 | +* By the NHS, for the NHS |
| 40 | +* [(And now award winning)](https://www.strategyunitwm.nhs.uk/news/strategy-unit-demand-model-wins-prestigious-florence-nightingale-award) |
| 41 | + |
| 42 | +## So what does it do? |
| 43 | + |
| 44 | +<img src="https://media1.giphy.com/media/v1.Y2lkPTc5MGI3NjExMTc3dXMyanF0cjJoem16bjhieDZ5djRqZ2RoNDd2eG43aDg3aXkweSZlcD12MV9pbnRlcm5hbF9naWZfYnlfaWQmY3Q9Zw/l2JdSlA1a1zKVAyze/giphy.gif" alt="'Gif of Homer Simpson pressing a button and saying 'do something cool'" height="500"> |
| 45 | + |
| 46 | +## So what does it do? |
| 47 | + |
| 48 | +* Demographic change |
| 49 | +* Non-demographic change |
| 50 | +* Types of potentially mitigable activity |
| 51 | +* More to come |
| 52 | + |
| 53 | +## The model |
| 54 | + |
| 55 | +* Sample the parameters (assume normal) |
| 56 | +* Calculate demand at IP, OP, A&E level |
| 57 | +* Do this 256 times and plot the distribution |
| 58 | +* The results are conceptually at row level, but not in practice |
| 59 | + |
| 60 | +## Structure of the project |
| 61 | + |
| 62 | +* Not going to show a big confusing diagram |
| 63 | +* [There is one if you want one](https://connect.strategyunitwm.nhs.uk/nhp/project_information/project_plan_and_summary/components-overview.html) |
| 64 | +* Three places that stuff happens, partly because of IG |
| 65 | +* We store and process data in Azure (SQL -> databricks; Docker) |
| 66 | +* We host the reports and dashboards separately, with no data on this server, only results |
| 67 | +* And we have a plethora of scripts, notebooks, and other gubbins on laptops |
| 68 | + |
| 69 | +## Versioning, RAP, and audit |
| 70 | + |
| 71 | +* Versioning is really challenging |
| 72 | +* We learned a lot! |
| 73 | +* Are we Apple or Microsoft? |
| 74 | +* RAP is important for audit too |
| 75 | +* We continue to wrestle with versioning of data to support old model runs |
| 76 | + |
| 77 | +## RAP is awesome... right? |
| 78 | + |
| 79 | + |
| 80 | + |
| 81 | +## Challenges |
| 82 | + |
| 83 | +* All models are wrong |
| 84 | +* Consistency versus accuracy |
| 85 | +* "It is difficult to make predictions, especially about the future" |
| 86 | + * "This model is simple" |
| 87 | + |
| 88 | +## The national elicitation exercise |
| 89 | + |
| 90 | +* We asked experts to predict likely levels of mitigation in the future, in a structured way |
| 91 | +* We also made some whizzy data science tools to do it with- which ended up being really important and useful |
| 92 | +* It's not my area so I won't say any more- this was Prof Mohammed and team |
| 93 | +* We show these values to trusts to help them make better guesses about the future |
| 94 | + |
| 95 | +## Challenges- users |
| 96 | + |
| 97 | +* Complexity correctness versus accessibility correctness |
| 98 | +* Who is a user? What do they want? (I'll talk more about this in a talk later on) |
| 99 | +* Hospital vs ICB vs NHP vs director vs data scientist vs... perspective |
| 100 | + |
| 101 | +## Challenges- decision making |
| 102 | + |
| 103 | +* Different analytical teams |
| 104 | + * Theoretical ideas to... |
| 105 | + * Pragmatic interpretations |
| 106 | + * All delivered with data science |
| 107 | +* NHP |
| 108 | +* Strategic versus operational |
| 109 | +* Prioritising |
| 110 | + |
| 111 | +## Challenges- openness and transparency |
| 112 | + |
| 113 | +* The work it takes to actually make this happen |
| 114 | +* Running the code |
| 115 | +* IG and sharing |
| 116 | + |
| 117 | +## The future |
| 118 | + |
| 119 | +* National and regional model runs |
| 120 | +* Bring your own data (FDP?) |
| 121 | +* Understanding more about categories of potentially mitigable activity, who thinks what's possible, and why it matters |
| 122 | +* Increasing understanding of the shift from hospital to the community |
0 commit comments