Register all active platform services and base features in core DB so admin can manage them, add delivery/hospitality/sports-center backend phases, update apps catalog and production deploy tooling. Co-authored-by: Cursor <cursoragent@cursor.com>
90 lines
3.0 KiB
Markdown
90 lines
3.0 KiB
Markdown
# Phase: Doctor Panel
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Identifier | `healthcare-13-2` |
|
|
| Status | Planned |
|
|
| Owner | Platform |
|
|
| Module(s) | `healthcare.doctor_panel`, `healthcare.visit_sessions`, `healthcare.visit_notes` |
|
|
| Service(s) | `healthcare` |
|
|
| Depends On | `healthcare-13-0`, `healthcare-13-1` |
|
|
| ADR(s) | TBD |
|
|
| Manifest | [phase-manifest.yaml](../../ai-framework/phase-manifest.yaml) |
|
|
| Framework | [ADR-013](../../architecture/adr/ADR-013.md) · [ADR-018](../../architecture/adr/ADR-018.md) · [ADR-019](../../architecture/adr/ADR-019.md) |
|
|
|
|
## Objective
|
|
|
|
Provide doctor-facing operational APIs: daily schedule view, patient queue for the current session, visit session lifecycle, and visit note shells (metadata + Storage refs) — without clinic-wide admin, patient portal UI, or full medical record engine.
|
|
|
|
## Enterprise Phase Discovery
|
|
|
|
> **Required before Implementation.**
|
|
|
|
| Field | Value |
|
|
| --- | --- |
|
|
| Discovery date | TBD at implementation |
|
|
| Inputs reviewed | Phase 13.1 handover · appointment engine APIs |
|
|
|
|
### Target Responsibility (this phase when Complete)
|
|
|
|
- Doctor dashboard queries (today's appointments, queue order)
|
|
- VisitSession aggregate linked to Appointment
|
|
- VisitNote shells with Storage file refs (no binary storage)
|
|
- Queue actions: call next, start visit, finish visit, defer
|
|
- Permissions `healthcare.doctor_panel.*`, `healthcare.visit_sessions.*`
|
|
- Events `healthcare.visit_session.*`, `healthcare.visit_note.*`
|
|
|
|
### Explicitly Excluded
|
|
|
|
- Clinic staff management (13.3)
|
|
- Patient self-service (13.4)
|
|
- Structured EHR / legal medical record (13.5)
|
|
- E-prescription to pharmacy (13.6)
|
|
- Frontend doctor UI (frontend phase)
|
|
|
|
## Business Analysis
|
|
|
|
| Item | Detail |
|
|
| --- | --- |
|
|
| Actors | Doctor, clinic nurse (optional delegate) |
|
|
| Business capabilities | View schedule; manage queue; document visit notes (shells) |
|
|
| Success metrics | Queue ordering consistent; visit tied to appointment |
|
|
| Non-goals | Billing codes, insurance claims, AI scribe |
|
|
|
|
## Scope
|
|
|
|
### In Scope
|
|
|
|
- Aggregates: VisitSession, VisitNote, DoctorQueueEntry (or query-only view)
|
|
- APIs scoped to authenticated doctor context
|
|
- Link visit completion → appointment status `completed`
|
|
- Alembic `0003_phase_132_doctor_panel`; version `0.13.2.0`
|
|
|
|
### Permissions
|
|
|
|
| Permission | Description |
|
|
| --- | --- |
|
|
| `healthcare.doctor_panel.view` | Dashboard and queue read |
|
|
| `healthcare.visit_sessions.manage` | Start/finish/defer visits |
|
|
| `healthcare.visit_notes.manage` | Create/update note shells |
|
|
|
|
## Out of Scope
|
|
|
|
- Clinic management (13.3)
|
|
- Patient portal (13.4)
|
|
- Medical record legal archive (13.5)
|
|
- Pharmacy routing (13.6)
|
|
- Delivery (13.7)
|
|
|
|
## Completion Criteria
|
|
|
|
- [ ] Doctor-scoped APIs + tenant isolation tests
|
|
- [ ] Visit session lifecycle tied to appointments
|
|
- [ ] Handover + registry at `0.13.2.0`
|
|
|
|
## Related Documents
|
|
|
|
- [Phase 13.1](phase-13-1-appointment-engine.md)
|
|
- [Healthcare Roadmap](../../healthcare-roadmap.md)
|
|
- [Module Registry](../../module-registry.md#healthcare)
|