How the-strategy-unit/nhp_outputs works
NHP Outputs is a Shiny app for exploring scenario results from the New Hospital Programme demand model. Its documented user workflow is to open the app and explore interactive charts and tables or download results; upstream, scenarios are created in nhp_inputs, processed by the model, and stored in Azure for the app to read. The tree identifies modules for information, selection, activity, distribution, and principal-impact views. No source excerpts were supplied, so internal module calls and routing are not asserted; those feature modules are shown without speculative edges.
Main entry points: run_app.R NHP Outputs app
Components 15
App runtime
- NHP Outputs app
R/run_app.R
Information and downloads
- Home information
R/mod_info_home_server.R - Parameter information
R/mod_info_params_server.R - Downloads
R/mod_info_downloads_server.R
Scenario result views
- Measure selection
R/mod_measure_selection_server.R - Core activity
R/mod_model_core_activity_server.R - Result distributions
R/mod_model_results_distribution_server.R - Principal summary
R/mod_principal_summary_server.R - Length of stay
R/mod_principal_summary_los_server.R - Detailed impact
R/mod_principal_detailed_server.R - Change factors
R/mod_principal_change_factor_effects_server.R
Scenario pipeline
- Azure results storage
- Scenario inputs app
- NHP demand model
Other components
- App user
Connections 4
- App user → NHP Outputs app: explores results
README.md - Scenario inputs app → NHP demand model: provides scenarios
README.md - NHP demand model → Azure results storage: stores results
README.md - Azure results storage → NHP Outputs app: app reads
README.md