isaacclad/ladill-care
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source 
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
Download Patch File Download Diff File Expand all files Collapse all files
.cursor/rules/specialty-modules.mdc
+1 -1
View File
@@ -21,7 +21,7 @@ Full standard: `docs/specialty-module-design-standard.md`.
## Current reality
Today specialties are a thin layer and clinical call-next still adapts to Ladill Queue via `QueueClient`. Program direction: replace that with the Care Queue Engine, then build the shared specialty shell on it. Do **not** deepen per-specialty UIs on the remote Queue adapter.
Specialty modules use the **shared specialty shell** on the Care Queue Engine (`SpecialtyShellService`, Overview / Visits / History / Billing / Workspace). Stage maps and service catalogs live in `config/care_specialty_shell.php`. Deepen clinical forms per module in Phase 3 — do **not** invent one-off layouts.
## When adding or deepening a module