41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
# 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.
|