Purpose and audience
The proposed coordination hub for intake, review, triage and follow-up.
Intended users: Approved Central coordinators and assigned navigators. Intended benefit: Accountable coordination rather than unowned handoffs.
Access and prerequisites
The existing /central route is a public fictional demonstration, not staff authority. Real access would require: Trust-scoped staff permission, assignment, safeguarding review and current consent.
What you can explore
No live staffing, real triage, operational handoff or notification is available.
- Fictional intake queue
- Local routing and handoff demonstrations
- Proposed consent and referral review
- Escalation and resolution design
Explore the prototype safely
Open the Central demonstration using the module link. Read its notice before interacting. Inspect the relevant example view; use fictional, non-sensitive input only. Local changes demonstrate an idea, not an operational action.
Use the Connected Ecosystem map to inspect the Central connections. Continue to a role tour to understand proposed approvals. Do not try to bypass unavailable registration, assignments or administrative controls.
Example scenario
In fictional Alex’s support scenario, Central contributes only its permitted task. The input would be: A minimum necessary, consented request and reviewed urgency. The expected proposed output would be: Proposed assigned work, approved referrals, follow-up and an auditable resolution.
Inputs, outputs and connections
Receives: A minimum necessary, consented request and reviewed urgency.
Produces: Proposed assigned work, approved referrals, follow-up and an auditable resolution.
Related modules: Youth, Sites, Clinical, Financial, Community.
Privacy and approvals
A queue is not a universal youth directory. Staff only receive information approved for their assignment.
Trust-scoped staff permission, assignment, safeguarding review and current consent.
Troubleshooting and limitations
No live staffing, real triage, operational handoff or notification is available.
If a view is unavailable, do not submit personal details elsewhere to work around it. A simulated approval cannot activate a service or grant access. The help center cannot resolve an emergency or connect a live responder.
Status, evidence and operational dependencies
Current classification: Simulated. Source review: 18 October 2026. src/routes/central.tsx; docs/covcare-v56-production-development-readiness.md
Before operation: validate trust-scoped staff permission, assignment, safeguarding review and current consent. and document recovery, audit, retention, user impact and separately approved tests. Source presence does not establish published-runtime or provider success.