Overview
Frontend implementation of Lab Forms across livehealth-frontend (admin web app) and crelio-app (patient portal).
👤 Ritu Kataria📅 Updated: Mar 13, 2026🏷️ feature
Lab Forms — Frontend
The Lab Forms frontend is split across two repositories, each covering a distinct user audience:
| Repository | Audience | Primary Use Cases |
|---|---|---|
| livehealth-frontend | Lab staff, billing operators, admin users | Admin configuration, AOE capture during billing, consent management, history and values viewing |
| crelio-app (patient-ui) | Patients | Consent form submission, AOE capture in CRM patient context |
livehealth-frontend
The main web application for lab operations. Covers all three Lab Forms lifecycle phases: Configure, Capture, and View/Edit.
- Overview — Architecture, data models, feature flags, routes
- Admin Configuration — CRUD flows for creating and editing forms
- Form Capturing (AOE Modal) — AOE modal, rendering pipeline, skip logic, navigation
- Consent Management — Consent status, notifications, revocation
- History & Viewing — Consent history, AOE values, patient info values
- Editing AOE Responses — Post-submission AOE correction flow
- Redux State Management — LAB_FORM, GENERIC, LAB_FORM_VALUES slices
- API Reference — All API endpoints
- File Map & Design Decisions — Source file locations and key architectural decisions
crelio-app (Patient UI)
The patient-facing portal at static/patient-ui/src/. Renders Lab Forms (Consent, AOE) from backend JSON config. The same rendering pipeline is shared across all form types.
- Overview — Architecture, source locations
- Form Rendering Engine — Component hierarchy, field type mapping, architectural patterns
- State Management — Redux slices, validation flow, onChange chain
- Skip Logic & Conditionals — depends_on field visibility, skip_to_conditions navigation
- File Upload & Signature — S3 presigned URL flows for files and signatures
- AOE Forms & Submission — AOE reuse, submission payload, guest endpoint