chore(task): archive 07-02-operations-dashboard-integration

This commit is contained in:
2026-07-03 00:57:51 -07:00
parent 9d73457f79
commit 4792aa5a77
6 changed files with 2 additions and 2 deletions

View File

@@ -0,0 +1,57 @@
# 运营看板整合优化
## Goal
Upgrade the existing operation dashboard into a cross-module summary after health, care, emergency, elder, bed, and admission data are available. The dashboard should summarize and route operators to work, not become a CRUD surface.
## Confirmed Facts
- The dashboard already uses real persisted elders, beds, admissions, and incidents.
- The dashboard currently does not include dedicated health or care-service metrics because those data sources do not exist yet.
- Recharts is already installed and the dashboard already uses a data-backed bed occupancy chart.
## Requirements
- Keep the dashboard as a Server Component data-loading surface with presentational components.
- Add health metrics after health data management exists:
- recent abnormal vital signs
- pending abnormal reviews
- chronic-condition coverage or counts where useful
- Add care metrics after care execution exists:
- today's care tasks
- pending/in-progress/completed care counts
- overdue/high-priority care count
- Add emergency metrics after emergency workspace exists:
- open safety events
- critical events
- recent resolved/closed events where useful
- Keep existing elder, bed, and admission summaries working.
- Use data-backed charts only; do not add fake visualization rows.
- Link dashboard items to the appropriate operational module route where practical.
## Acceptance Criteria
- [ ] Dashboard still loads persisted elder, bed, admission, and incident data.
- [ ] Dashboard includes persisted health summaries after health data is available.
- [ ] Dashboard includes persisted care execution summaries after care data is available.
- [ ] Dashboard includes persisted safety/emergency summaries after emergency data is available.
- [ ] Charts and tables are data-backed.
- [ ] Dashboard links route users into the relevant module instead of duplicating full workflows.
- [ ] `pnpm lint` passes.
- [ ] `pnpm type-check` passes.
- [ ] `pnpm build` passes.
## Dependencies
- Should run after health data management, care execution workspace, and emergency incident workspace are implemented.
- Should run after elder/bed context optimization if dashboard links depend on new detail surfaces.
## Out Of Scope
- Creating or editing records directly from the dashboard.
- Adding fake summary cards before backing data exists.
- Replacing the dashboard with a marketing landing page.
## Open Questions
- None currently blocking planning.