Nexus is a hospital information system (HIS) covering the full clinical and administrative surface of a hospital — admissions, ward and specialty boards (ICU, Maternity, Emergency, Operations), laboratory and radiology (with FHIR R5 and LIS/DICOM integration), pharmacy, finance, HR, and reporting.
Stack
| Layer | Technology |
|---|---|
| Backend | Go (module hospital-management), chi router, PostgreSQL |
| Frontend | Lit 3 web components, Vite, TypeScript |
| Interop | FHIR R5 resource mapping, LIS (MLLP) and DICOM device integration |
| Auth | JWT-based sessions with role-based access control (RBAC) |
| i18n | Full RTL/LTR support (Arabic and English) via logical CSS properties |
Layout
backend/internal/— domain packages:auth,fhir,lis,orchestrator,specialty,notify,storage, and per-featurehandlers.frontend/src/pages/— one Lit page component per module (wards, lab, pharmacy, radiology, finance, HR, and the specialty kiosks).frontend/docs/— the department-level guides, split here into a User Guide (business-level walkthrough for staff) and Technical Guides (routes/RBAC/API reference for engineers).
Design language
Nexus uses a deep-teal palette (clinical without being cold) with a warm clay
accent reserved for people — patient identity and care-team attribution never
share a color with system chrome or status indicators. This documentation
site is themed with the same tokens; see
frontend/src/styles/theme.js for the full palette and rationale.
User Guide
What each kiosk is for and how staff use it day to day — no technical detail.
Technical Guides
Routes, RBAC, tables, and API surface for engineers extending a module — see Technical Guides.