The-Strategy-Unit / The-Strategy-Unit/open-plan-docs
Handle transfers (admimeth 81) in capacity conversion
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 3
- Forks
- 1
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 14
Description
At some point we should check to see what (if any) activity doesn't end up contributing to capacity. My assumption is that we would want the vast majority of activity to be assigned to a functional area - although there might be some exceptions.
For transfers, I think we might need a CLASS_TRANSFER and then we have the choice:
include with the non-elective group; or
keep as a distinct sub-group
At the moment the non-elective group contributes both to ward beds and to assessment beds. My instinct is that transfers should perhaps only contribute to ward beds and NOT to assessment beds.
From @paulseamer from https://github.com/The-Strategy-Unit/nhp_functional_area_mapping/pull/52#discussion_r3712513372
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the capacity conversion logic for admimeth 81 and review the linked functional-area mapping discussion. Done means agreeing whether transfers are a distinct class or part of the non-elective group, and defining whether they contribute to ward beds, assessment beds, or both.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100