Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Review each KPI for patients in transfer #556

Open
mbarton opened this issue Feb 6, 2025 · 3 comments
Open

Review each KPI for patients in transfer #556

mbarton opened this issue Feb 6, 2025 · 3 comments
Assignees
Labels
high high priority (max 3 items)

Comments

@mbarton
Copy link
Member

mbarton commented Feb 6, 2025

Check each KPI, if it should include patients who have left the PDU

@anchit-chandran
Copy link
Contributor

anchit-chandran commented Feb 19, 2025

relates #631

@mbarton
Copy link
Member Author

mbarton commented Feb 20, 2025

Thanks for the write up on #631 @anchit-chandran. I see that issue talks about KPI 1 (with KPI 5 already correct). Are there any other KPIs that need updating apart from 1?

@anchit-chandran
Copy link
Contributor

anchit-chandran commented Feb 20, 2025

KPI1 is used as the base query set for the other denominators so a change to this will have knock-on effects unless those other kpis also specify a filter for transfers.

From a quick ctrl f, almost all other denominators are affected as they use KPI1 for their base queryset: 2,3,4,8-12

The denominators are then used in all subsequent calculations.

In summary, the change would mean that if a patient has been marked as leaving a PDU (date+reason leaving service are filled), all data related to that Patient instance is filtered out of kpi calculations).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
high high priority (max 3 items)
Projects
None yet
Development

No branches or pull requests

3 participants