chore(task): archive 07-02-operations-dashboard-integration
This commit is contained in:
@@ -0,0 +1 @@
|
||||
{"_example": "Fill with {\"file\": \"<path>\", \"reason\": \"<why>\"}. Put spec/research files only — no code paths. Run `python3 .trellis/scripts/get_context.py --mode packages` to list available specs. Delete this line once real entries are added."}
|
||||
@@ -0,0 +1,40 @@
|
||||
# Operations Dashboard Integration Design
|
||||
|
||||
## Summary
|
||||
|
||||
Upgrade the dashboard into a cross-module operations summary now that health, care, emergency, elder, bed, and admission data are persisted.
|
||||
|
||||
## Data Boundary
|
||||
|
||||
The dashboard remains a Server Component:
|
||||
|
||||
- elder/bed/admission data from `modules/core/server/operations.ts`
|
||||
- health data from `listHealthAdminData`
|
||||
- care data from `listCareExecutionData`
|
||||
- emergency data from `listEmergencyIncidentData`
|
||||
|
||||
Load optional module data only when the viewer has the corresponding read permission. Do not fabricate metrics when permission or data is absent.
|
||||
|
||||
## UI Boundary
|
||||
|
||||
`DashboardHome` stays presentational. It receives:
|
||||
|
||||
- primary metrics
|
||||
- bed occupancy chart data
|
||||
- recent admissions
|
||||
- work queues for health, care, and emergency
|
||||
|
||||
Dashboard items should link into modules:
|
||||
|
||||
- health reviews -> `/settings/health`
|
||||
- care tasks -> `/care`
|
||||
- emergency events -> `/emergency`
|
||||
- admissions -> `/beds`
|
||||
|
||||
The dashboard is not a mutation surface.
|
||||
|
||||
## Compatibility
|
||||
|
||||
- Existing bed occupancy chart remains data-backed.
|
||||
- Existing admission list remains data-backed.
|
||||
- Top badge-style tag should be removed to match the module cleanup direction.
|
||||
@@ -0,0 +1 @@
|
||||
{"_example": "Fill with {\"file\": \"<path>\", \"reason\": \"<why>\"}. Put spec/research files only — no code paths. Run `python3 .trellis/scripts/get_context.py --mode packages` to list available specs. Delete this line once real entries are added."}
|
||||
@@ -0,0 +1,29 @@
|
||||
# Implementation Plan
|
||||
|
||||
## 1. Start Task
|
||||
|
||||
- Start Trellis task.
|
||||
- Preserve unrelated dirty settings/dialog files.
|
||||
|
||||
## 2. Server Data
|
||||
|
||||
- Update dashboard page to load health/care/emergency summaries when permitted.
|
||||
- Keep all reads organization-scoped.
|
||||
- Build route hrefs with `getWorkspaceHref`.
|
||||
|
||||
## 3. Presentational UI
|
||||
|
||||
- Extend `DashboardHome` props for health reviews, care tasks, and emergency events.
|
||||
- Add compact queue sections with links to modules.
|
||||
- Remove top badge tag.
|
||||
|
||||
## 4. Verification
|
||||
|
||||
- `pnpm lint`
|
||||
- `pnpm type-check`
|
||||
- `pnpm test`
|
||||
- `pnpm build`
|
||||
|
||||
## Rollback
|
||||
|
||||
- Revert dashboard page and `DashboardHome` changes.
|
||||
@@ -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.
|
||||
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"id": "operations-dashboard-integration",
|
||||
"name": "operations-dashboard-integration",
|
||||
"title": "运营看板整合优化",
|
||||
"description": "",
|
||||
"status": "completed",
|
||||
"dev_type": null,
|
||||
"scope": null,
|
||||
"package": null,
|
||||
"priority": "P2",
|
||||
"creator": "TalexDreamSoul",
|
||||
"assignee": "TalexDreamSoul",
|
||||
"createdAt": "2026-07-02",
|
||||
"completedAt": "2026-07-03",
|
||||
"branch": null,
|
||||
"base_branch": "main",
|
||||
"worktree_path": null,
|
||||
"commit": null,
|
||||
"pr_url": null,
|
||||
"subtasks": [],
|
||||
"children": [],
|
||||
"parent": "07-02-operations-module-roadmap",
|
||||
"relatedFiles": [],
|
||||
"notes": "",
|
||||
"meta": {}
|
||||
}
|
||||
Reference in New Issue
Block a user