diff --git a/presentations/2026-10-14_capcon_team_brief/app_scrn.png b/presentations/2026-10-14_capcon_team_brief/app_scrn.png new file mode 100644 index 00000000..cd362452 Binary files /dev/null and b/presentations/2026-10-14_capcon_team_brief/app_scrn.png differ diff --git a/presentations/2026-10-14_capcon_team_brief/docs_scrn.png b/presentations/2026-10-14_capcon_team_brief/docs_scrn.png new file mode 100644 index 00000000..e3ea7f51 Binary files /dev/null and b/presentations/2026-10-14_capcon_team_brief/docs_scrn.png differ diff --git a/presentations/2026-10-14_capcon_team_brief/index.qmd b/presentations/2026-10-14_capcon_team_brief/index.qmd new file mode 100644 index 00000000..f313ca5a --- /dev/null +++ b/presentations/2026-10-14_capcon_team_brief/index.qmd @@ -0,0 +1,333 @@ +--- +title: "OpenPlan Hospital Capacity Model" +subtitle: "" +date: last-modified +date-format: "D MMMM YYYY" +execute: + echo: false + eval: false +format: + revealjs: + embed-resources: true + scrollable: true + theme: [default, su_presentation.scss] + transition: none + preview-links: auto + slide-number: false + auto-animate: true + footer: | + Learn more about [The Strategy Unit](https://www.strategyunitwm.nhs.uk/) +--- + +## The problem with estimating capacity needs + +

How does this work?

+

Why do my results differ?

+

Something changed - What? Why? When?

+

Who decided that? Why?

+ +## +```{=html} + +``` + +## TRUST + + + +
+ +

+ + VARIABILITY +

+ +

+ + BLACK BOX +

+ +

+ + NON-AUDITABLE +

+ +

+ + ONE-OFF +

+ + +
+ +:::{.notes} +Fundamentally there is a problem with Trust +You need the capacity conversions to 'show their working' so you can trust that its correct and appropriate. + +But Trust is hard to come by when across the piste capacity conversion is + +VARIABLE +- some are simple worksheets, some more sophisticated approaches but they are fundamentally not comparable + +BLACK BOX +- The underlying decision making, the judgement calls, and the assumptions that have gone into the approach are not available for scrutiny. + +NON-AUDITABLE +- Cannot audit their approach fully: were their methods sound? Do they work for all cases you need to put them to? Can you fully understand its limitations?Are their assumptions justified? +- This potentially leaves the method open to manipulation/error + +ONE-OFF +- often the approach is not reusable, so the money spent on its procurement cannot benefit future applications. + +::: + +## OpenPlan Capacity Model + + + +
+ +
+ + Transparent +
+ +
+ + Robust +
+ +
+ + Validated +
+ +
+ + Uncertainty +
+ +
+ + Versatile +
+ +
+ + Accessible +
+ +
+ + + + +:::{.notes} + + +Lets briefly touch on how those elements are being enacted with the model we're building you. + +**Transparent** +- Our codebases are open code by default, meaning anyone can come and inspect any element of it, and see the decision making and discussions that have gone into a lot of it. +- We also host up to date open Quality Assurance logs and plans (in line with the government digital standards and National Audit Office approaches) +- All assumptions will be published alongside their justifications +- All limitations are clearly stated and explained - plus we provide a roadmap of future work that aims to address them where possible. + +**Robust** +We involved from the start a multi-disciplinary team of experts to guide us towards an agreed methodology. +The whole thing is openly version controlled, which means that when things change, we can always turn back the clock to find out exactly when/what/who and why of every change. + +**Validated** +We are validating the work as we go. +This involved a panel including -clinical colleagues, data engineers, analysts, methodology experts, statisticians, +user experience experts, and, crucially, real users. + +**We Account for uncertainty** +by sitting the capacity conversion on top of the demand model - it therefore +inherits all the uncertainty considerations that are pivotal to that model. +We also have plans to incorporate futher sources of uncertainty as part of our future work plans. + +**Adaptible** +We have created the tool in a way that makes future developments smooth and simple, ensuring we can keep up with updated data flows and new sources of robust information. This means the tool has longevity, should be of genuine utility to a broad anad changing audience, and reflects value for money. + +**Accessible** +We are designing the user elements with real people in mind - there should be no need to have the skills of our MDT, we want the tool to be unintimidating, useful and fool proof so the results you get are used to best effect. +Crucially we're avoiding guesswork about how users want to receive the tool - we are asking them, iteratively, to ensure we stay on the right lines and end up with something truly impactful + +We aim to deliver value on day 1, and to continue to increase that value over time. +::: + +## Talking to users + +![](raphaelsilva-group-2935521.svg){fig-align="center"} + +:::{.notes} +a key element has been iterative user feedback and stakeholder engagement. +Jake and Paul worked to validate the methodology with real users, and Nat and I +have gone thorough successive rounds of structured interviews with internal and +external potential users to gather their needs and understand any frictions through their eyes. All this rich info is fed back into a mega user feedback system Nat wrangles that allows us to trace a path right through from user need +to delivered features, to understand the frequency of themes that arise and ensure we're building what people need. +::: +## Progress so far + + + + +::: {.progress-container} + +::: {.progress-pair .fragment .current-visible} +::: {.progress-text} +An online application interface +::: + +![](app_scrn.png) +::: + +::: {.progress-pair .fragment .current-visible} +::: {.progress-text} +Near instant results workbook downloadable +::: + +![](tomfield-spreadsheet-2816806_1920 (1).jpg) +::: + +::: {.progress-pair .fragment .current-visible} +::: {.progress-text} +A user tested comprehensive supporting documentation website +::: + +![](docs_scrn.png) +::: + +::: {.progress-pair .fragment .current-visible} +::: {.progress-text} +Development roadmap +::: + +![](joshuaworoniecki-road-5089188.jpg) +::: + +::: + +:::{.notes} +SLIDE +We are on tract to release version 1 in October. + +This first version will include +- an online **application** on our Connect platform that will allow people who have run demand models in the past to easily select from their past scenarios one which they want to convert. + +- Results will be created and available for download near instantaneously, int he form of a **workbook**. this workbook will clearly state the values of ALL assumptions used, as well as the conversion results. + +- A full supporting **documentation** website will be availab that explains, in both layman-friendly and technical terms how the model works, what it provides, and all limitations. +This will be kept up to date with explanations of how the conversion model has changed over time. The site includes all assumptions inherent in the model alongside their justifications. + +- and the high-level development **roadmap** so you will always know what improvements are coming up. + +- On day 1 users will have the facility to submit **feedback** on the model and the documentation site, which will be triaged and acted upon subject to our comprehensive feedback review system. + +The process has been devised, tested, and iteratively improved upon for accuracy, +robustness, security and user experience. + +I'll pass over to my colleague Paul now and let him tell you about the conceptual framework he has built. + +::: + +## Future plans + +- Queueing theory +- New data feeds +- A results dashboard +- Replacing assumptions with local operational parameters +- Evaluation of SoA alignment +- Baseline conversion + +:::{.notes} +Our aims with version 1 of the model are to release a prototype that will deliver +value from day 1. +We are constantly prioritising potential extensions to ensure the roadmap is +taking us towards a tool that makes everyone's lives easier. + + +- Queueing theory to better account for unpredictable demand +- Incorporating new data feeds to remove some of the assumptions: criticial care, +diagnostic imaging. +- A results dashboard to deliver useful visualisations of output +- Allowing local operational parameters to be ingested instead of relying on +central assumptions +- Appraisal of the elements of SoA that are not yet covered to identify opportunities +to incorporate those. +- comparison of baseline year capacity estimates to known physical capacity + +As well as those extensions, what comes with the model includes: + +- seamless integration with the demand model - all improvements and updates there +will allow improvement in the capacity model results + +::: \ No newline at end of file diff --git a/presentations/2026-10-14_capcon_team_brief/joshuaworoniecki-road-5089188.jpg b/presentations/2026-10-14_capcon_team_brief/joshuaworoniecki-road-5089188.jpg new file mode 100644 index 00000000..a712b0bd Binary files /dev/null and b/presentations/2026-10-14_capcon_team_brief/joshuaworoniecki-road-5089188.jpg differ diff --git a/presentations/2026-10-14_capcon_team_brief/raphaelsilva-group-2935521.svg b/presentations/2026-10-14_capcon_team_brief/raphaelsilva-group-2935521.svg new file mode 100644 index 00000000..1ab097ff --- /dev/null +++ b/presentations/2026-10-14_capcon_team_brief/raphaelsilva-group-2935521.svg @@ -0,0 +1,2 @@ + + \ No newline at end of file diff --git a/presentations/2026-10-14_capcon_team_brief/su_presentation.scss b/presentations/2026-10-14_capcon_team_brief/su_presentation.scss new file mode 100644 index 00000000..b02d8824 --- /dev/null +++ b/presentations/2026-10-14_capcon_team_brief/su_presentation.scss @@ -0,0 +1,218 @@ +/*-- scss:defaults --*/ +$su-charcoal: #2c2825; +$su-charcoal-l20: lighten($su-charcoal, 20%); +$su-charcoal-l40: lighten($su-charcoal, 40%); +$su-charcoal-l60: lighten($su-charcoal, 60%); +$su-charcoal-l80: lighten($su-charcoal, 80%); + +$su-yellow: #f9bd07; +$su-yellow-l20: lighten($su-yellow, 20%); +$su-yellow-l40: lighten($su-yellow, 40%); +$su-yellow-l60: lighten($su-yellow, 60%); +$su-yellow-l80: lighten($su-yellow, 80%); + +$su-blue: #5881c1; +$su-white: #f5f4f3; +$su-red: #ec6555; +$su-slate: #686f73; + +// load in font awesome icons +@import url("https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.2.1/css/all.min.css"); + + +$body-bg: $su-white; +$body-color: $su-charcoal-l20; +$highlight-color: $su-yellow; +$link-color: $su-blue; +$footer-bg: $su-charcoal; +$footer-fg: $su-yellow; + +$presentation-heading-color: $su-charcoal; + +/*-- scss:rules --*/ + +.reveal .slide blockquote { + border-left: 3px solid $text-muted; + padding-left: 0.6em; + background: #F6F7F7; +} + +.reveal h2 { + padding-bottom: 0.3em; +} + +.reveal .footer { + color: $su-yellow; + background-color: $su-charcoal; + display: block; + position: fixed; + bottom: 0px !important; + padding-bottom: 12px; + padding-top: 12px; + width: 100%; + text-align: center; + font-size: 18px; + z-index: 2; +} + +.reveal .slide ul:not(.panel-tabset-tabby) { + li { + list-style: none; + /* Remove default bullets */ + } + + li::before { + content: "\25FC"; + /* Add content: \2022 is the CSS Code/unicode for a bullet; add a space for easier alignment! */ + color: $highlight-color; + /* Change the color */ + display: inline-block; + /* Needed to add space between the bullet and the text */ + width: 1.5em; + /* Also needed for space (tweak if needed) */ + margin-left: -1.5em; + /* Also needed for space (tweak if needed) */ + font-size: 66%; + } +} + +.reveal .progress span { + background-color: $su-yellow; +} + +.reveal .slide-logo { + z-index: 3; + bottom: -5px !important; +} + +.slide-background:first-child { + background-color: $su-charcoal; + background-image: radial-gradient($su-charcoal-l20 1%, transparent 5%); + background-position: 0 0, 10px 10px; + background-size: 30px 30px; + background-repeat: repeat; + height: 100%; + width: 100%; +} + +.slide-background:first-child .slide-background-content { + background-image: url("https://the-strategy-unit.github.io/assets/logo_yellow.svg"); + top: 0.5em; + right: 0.5em; + height: 4em; + width: 4em; + position: absolute; +} + +#title-slide { + text-align: left; +} + +#title-slide h1 { + font-size: 2em; + color: $su-yellow !important; +} + +#title-slide .subtitle { + color: $su-charcoal-l60; +} + +#title-slide .quarto-title-authors { + justify-content: left; + display: block; +} + +#title-slide .quarto-title-author { + padding-top: 1em; + color: $su-red; + padding: 0; +} + +#title-slide .quarto-title-author a { + color: $su-blue; +} + +#title-slide p.institute { + font-size: 0.75em; + color: $su-charcoal-l60; +} + +#title-slide p.date { + font-size: 0.5em; + color: $su-charcoal-l40; +} + +.reveal .slide-logo:first-child { + display: none; +} + +.inverse { + .slide-background-content { + background-color: $su-charcoal; + } + + h1, + h2, + h3, + h4 { + color: $su-charcoal-l40 !important; + } +} + +.reveal .imitate-title { + font-size: 2em; +} + +.reveal .inverse .imitate-title { + color: $su-yellow !important; +} + +.reveal .inverse { + color: $su-white; +} + +.text-bottom { + bottom: 1em; + position: absolute; +} + +.no-bullets ul { + list-style-type: none; + /* Remove bullets */ + padding: 0; + /* Remove padding */ + margin: 0; + /* Remove margins */ +} + +.small-table table { + font-size: 1.65rem; +} + +.small { + font-size: 1.2rem; +} + +.medium { + font-size: 2rem; +} + +.yellow { + color: $su-yellow; +} + +.light-yellow { + color: $su-yellow-l40; +} + +.light-charcoal { + color: $su-charcoal-l40; +} + +.very-light-charcoal { + color: $su-charcoal-l60; +} + +.center { + text-align: center; +} \ No newline at end of file diff --git a/presentations/2026-10-14_capcon_team_brief/tomfield-spreadsheet-2816806_1920 (1).jpg b/presentations/2026-10-14_capcon_team_brief/tomfield-spreadsheet-2816806_1920 (1).jpg new file mode 100644 index 00000000..d18a89d7 Binary files /dev/null and b/presentations/2026-10-14_capcon_team_brief/tomfield-spreadsheet-2816806_1920 (1).jpg differ