Add shared specialty module shell (Phase 2).
Deploy Ladill Care / deploy (push) Successful in 52s

Overview/Visits/History/Billing/Workspace layout with stage maps, KPIs,
patient header/timeline, and service catalogs seeded into Billing on activate.
Emergency, Blood Bank, and Dentistry ship first-class shell configs.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
isaacclad
2026-07-18 10:01:17 +00:00
co-authored by Cursor
parent 6cf5a24019
commit 0181221fe8
21 changed files with 1587 additions and 153 deletions
+9 -3
View File
@@ -1,6 +1,6 @@
# Care Queue Engine + Specialty Modules — Unified Plan
**Status:** Phase 1 in progress
**Status:** Phase 2 complete (shell); Phase 3 next
**Date:** 2026-07-18
**Repos:** ladill-care (primary), ladill-queue (healthcare removal)
**Related:** `docs/specialty-module-design-standard.md`
@@ -12,8 +12,14 @@
- Config: `CARE_QUEUE_DRIVER=native` (default) | `remote` (legacy Ladill Queue HTTP)
- Tables: `care_service_queues`, `care_service_points`, `care_queue_tickets`
- Service: `App\Services\Care\CareQueueEngine`
- Bridge / provisioner route to native when driver is `native`; PHPUnit sets `remote` so legacy Http::fake tests keep working
- Exit criterion: Care Pro demo issues / call-next / complete with `QUEUE_API_*` unset
## Phase 2 notes (implementation)
- Shared shell: Overview / Visits / History / Billing / Workspace + action panel + stage map nav
- `SpecialtyShellService` + `config/care_specialty_shell.php` (Emergency, Blood Bank, Dentistry stage maps & catalogs; defaults for others)
- Patient header + timeline partials reused on specialty workspace and patient chart
- Activate seeds billable services; workspace Billing tab posts into Billing Engine
- Exit: Emergency (+ Dentistry) demonstrate the standard on the in-app queue engine
---
+12 -6
View File
@@ -188,16 +188,22 @@ Use this prompt when implementing a specific specialty:
## Current implementation status (as of 2026-07)
Specialty modules today are a **thin Pro enablement layer**, not the full clinical product shell described above.
Specialty modules share a **specialty shell** on the Care Queue Engine. Per-module clinical forms deepen in Phase 3.
| Capability | Status |
| --- | --- |
| Module catalog + activate/deactivate | Exists (`config/care_specialty_modules.php`, `SpecialtyModuleService`) |
| Department + queue stub provisioning | Exists |
| Specialty Call next + waiting list | Exists (thin show page) |
| Workflow-driven episodes | Missing (use `Visit` as unit) |
| Unified patient timeline component | Partial (patient chart lists only) |
| Standard patient header / specialty shell | Missing |
| Department + queue provisioning | Exists (native Care Queue Engine) |
| Shared specialty shell (Overview / Visits / History / Billing / Workspace) | Exists (`SpecialtyShellService`, `care/specialty/shell.blade.php`) |
| Stage maps + service catalogs | Exists (`config/care_specialty_shell.php` — Emergency, Blood Bank, Dentistry first-class; others inherit defaults) |
| Standard patient header + timeline | Exists (reused on specialty workspace + patient chart) |
| Visit-backed specialty visits | Exists (open visits + history lists) |
| Service catalog → Billing Engine | Exists (seed on activate; add line from workspace Billing tab) |
| Specialty KPIs | Exists (overview strip) |
| Deep clinical forms / order sets / documents | Phase 3 |
**Program plan:** `docs/care-queue-engine-and-specialty-plan.md` (Phase 2 shell complete; Phase 3 rolls remaining modules onto clinical depth).
| Specialty dashboard KPIs | Missing |
| Left nav Overview / Visits / History / Module Tabs | Missing |
| Clinical workspace | Missing (falls through to appointments/consultations) |