We are requesting development to allow service user status to be managed at individual site (community) level.
Current Limitation
While PCS allows service users to be linked to multiple sites, actions such as closing or suspending a file apply across all sites. This means a record is either open everywhere or closed everywhere.
Issue
This does not reflect operational practice, where a service user may move between sites (e.g. Harvest View to Walker Grange) and need to be:
Closed at one site, but
Remain active at another
Proposed Improvement
Enable site-level control, allowing:
Active in one site and closed/inactive in another
Independent suspension/closure per site
Benefits
Supports real care pathways and transitions
Improves data accuracy and reporting
Reduces risk of incorrect closures
Strengthens governance and audit