Add specialty clinical records on the shared shell (Phase 3).
Deploy Ladill Care / deploy (push) Failing after 1m2s

Visit-scoped structured forms for Emergency triage, Blood Bank requests,
and Dentistry odontogram with derived alerts, document upload, and KPI counts.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
isaacclad
2026-07-18 10:09:32 +00:00
co-authored by Cursor
parent 0181221fe8
commit 57358e4206
15 changed files with 1093 additions and 21 deletions
+9 -2
View File
@@ -1,6 +1,6 @@
# Care Queue Engine + Specialty Modules — Unified Plan
**Status:** Phase 2 complete (shell); Phase 3 next
**Status:** Phase 3 in progress (clinical depth on shell)
**Date:** 2026-07-18
**Repos:** ladill-care (primary), ladill-queue (healthcare removal)
**Related:** `docs/specialty-module-design-standard.md`
@@ -19,7 +19,14 @@
- `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
## Phase 3 notes (implementation)
- `care_specialty_clinical_records` — Visit-scoped structured JSON + derived alerts
- Emergency triage/notes, Blood Bank request/inventory, Dentistry odontogram/notes on existing workspace tabs
- Documents tab uploads to patient attachments (`specialty_{module}`)
- KPI strip includes open clinical records; no new queue backends
- Remaining modules inherit generic clinical_notes until rolled onto the same form pattern
---