Built for connected healthcare operations
elaj brings appointments, patients, scheduling, billing, clinical documents, and public booking into one secure bilingual platform—across every clinic and branch.
One connected platform
From the first booking request to the final payment and clinical document, elaj keeps operational work connected and in context.
See month, week, or day calendars; filter by branch, doctor, and status; and reschedule with drag and drop when permitted. Availability respects branch hours, doctor overrides, leave, exceptions, breaks, and overbooking rules.
Patients see only bookable branches, assigned doctors, and valid time slots. Guest booking is standard, with optional account creation and signed slot validation.
Global patient identities, clinic profiles, recent documents, visit history, invoices, and financial visibility—all within the appropriate tenant and branch scope.
Manage services and branch availability, issue printable invoices, take split payments through a cashier workspace, and view real accounting aggregates in the tenant currency and VAT settings.
Run medical document analysis on demand for quick summaries and specialist reports, or extract identity fields into empty patient form fields for mandatory staff review before saving.
Appointment journey
elaj connects the public patient journey with the staff workflow, while rechecking availability before an appointment is written.
Clinical documents
Create laboratory and radiology order requests with tenant catalogs, draft–issue–cancel workflows, immutable issue snapshots, global document numbers, Code 128 barcodes, and bilingual A4 printing.
Full capability map
A clear view of the operational capabilities documented in elaj—without inflated promises.
Multi-tenant organizations with clinics, branches, doctors, services, and branch-level public booking controls.
Clinic hours, doctor weekly overrides, leave, date-specific closures or overrides, breaks, and overlap validation.
Patient charts, visit timelines, appointment history, financials, medical documents, and optional reviewed identity extraction.
Service pricing, invoices, A4 printing, split-payment POS, payment methods, collector tracking, and accounting overview.
AWS SES email plus Twilio or custom HTTP SMS, per-type controls, per-appointment flags, and multiple reminder rules.
Tenant lab and radiology catalogs, draft/issue/cancel lifecycle, snapshots, doctor license/signature support, and print settings.
Manual Gemini-based medical document analysis and structured identity field extraction with confidence and human confirmation.
Country, timezone, date and number formats, currency, VAT, working hours, slot duration, channels, and tenant logo.
Audit logging, role-based permissions, consent records, DSAR workflows, retention rules, breach register, and account closure.
Clinic-specific booking, scoped branches and doctors, signed slots, guest flow, optional accounts, and safe patient matching.
Offline payments today with an online-ready gateway and webhook architecture, including signature validation controls.
Import/export tools, real tenant-scoped aggregates, activity tracking, and secure modular domain separation.
Security & control
elaj is designed around tenant isolation, explicit permissions, scoped public booking, and traceable changes across sensitive and commercial work.
Frequently asked questions
elaj is a bilingual, multi-tenant clinic management platform that connects internal clinic operations with a public patient booking flow.
Yes. An organization can manage multiple clinics, branches, doctors, services, schedules, and tenant-scoped operational settings.
Yes. Guest booking is the default. A patient can optionally request an account during booking without blocking the booking workflow.
Availability follows branch closures, doctor leave, date overrides, weekly schedules, breaks, assignment checks, overlap rules, and a final validation when the booking or reschedule is saved.
Authorized users can manually request medical document analysis for summaries and specialist reports. On the new-patient form, identity fields can be extracted into empty fields and must be reviewed before saving. Both are subject to plan and tenant AI enablement.
Yes. The system is designed for Arabic and English usage, with tenant-level locale settings and RTL/LTR support for clinical request printing.
The platform includes invoices, POS, payment records, and offline payment workflows. Its payment architecture is online-ready and supports gateway webhooks; the README does not claim a universally active online gateway.
Start with a platform designed for connected schedules, clearer workflows, and bilingual care operations.