Allow activity to be redistributed between sites

Open
#235 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
r
Domain
data

Research direction

Start by reviewing the Shiny app's demand-model input and output flow, focusing on how hospital sites and activity are represented. Compare redistribution as an input decision versus an output adjustment, including support for new sites; done requires an agreed approach and defined behavior.

Written by the indexing model from the issue text.

Description

could enhancement question

Providers may plan on changing where activity is delivered in future within their own set of hospital sites. For instance, they may decide that elective ENT activity will no longer be provided at site A, and instead have all activity at site B. Or, they may decide that a certain proportion of activity may be delivered elsewhere.

We may even need to consider "new" sites that do not map to existing facilities.

This could be an input decision, or it could be performed on the outputs. The benefit of the latter would be you could tweak after the fact, but you would lose the ability to introduce stochasticity to the results

Dominant language
R
Stars
2
Forks
1
Avg merge
15h 39m
Merged PRs (30d)
6

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from The-Strategy-Unit/nhp_inputs

All issues in The-Strategy-Unit/nhp_inputs

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.