feature/cases #55
Reference in New Issue
Block a user
Delete Branch "feature/cases"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
0- Global patients + mobile normalization
Appointments, treatments, and case search all depend on patient identity
1- Org-type sidebar + permissions
Shell before feature work; hides Patients for labs
2- TreatmentDetail / LabCase schema + APIs
Backend foundation for the split model
3- Task templates + generation on send
Lab workflow engine before UI
4- Clinic two-step treatment UI
Needs Phase 2–3 APIs
5- Lab Cases inbox + task board
Needs Phase 3 API
Phase 0:
Prisma Patient schema — global mobile, remove organizationId
normalizeMobile util (backend + frontend) + tests
PatientsService global search + dedupe create
Update patient + appointment UI for mobile/dedupe
Migration + re-seed test patients
Phase 1:
TAB_CASES permissions in seed + backend/frontend constants
Sidebar orgTypes filter + /cases stub page
Staff permission grid + backend validation by org type
Route guards + backend guards for clinic-only endpoints
Phase 2:
Prisma schema TreatmentDetail + LabCase models
Rewrite treatments service + DTOs + controller
Update frontend types, API, TreatmentWorkspace bridge
Migration + build verify
Phase 3:
TreatmentWorkflowStep + LabCaseTask schema + migration
Seed workflow steps + task generation on send
Cases module — list, get, PATCH task
Cases API + minimal lab inbox UI
too much change bro.
.
feature/casesto WIP: feature/casesWIP: feature/casesto feature/casesfeature/casesto WIP: feature/casesWIP: feature/casesto feature/casesfeature/casesto WIP: feature/casesWIP: feature/casesto feature/cases