01 — Our Story
Labevol

Built for labs. Grew with clinics. Ready for ER.

Labevol started as a focused LIMS in Ramallah. As the labs that used it grew into clinics and medical centers, the platform grew with them — three system types, one product, one chart per patient.

Our Mission

Empower laboratory, clinic, and medical-center teams with software that simplifies daily workflows, reduces errors, and shortens turnaround times. Every panel completed faster is a patient who waits less.

Our Vision

To become the LIMS-plus-clinic-plus-ER platform of choice across the MENA region — intuitive, efficient, locally fluent. We evolve the practice without breaking what's already trusted.

The evolution

Four chapters.

01 · 2025

Origin — a LIMS for Palestinian labs

Labevol started as a focused LIMS for standalone medical laboratories. We built the workflow we knew best: patient → order → sample → result → report → WhatsApp delivery, with bilingual PDFs, Levey-Jennings QC, and ILS billing baked in.

  • First lab onboarded in Ramallah
  • Bilingual (Arabic + English) reports
  • WhatsApp delivery from your own lab number
02 · 2025

Clinics asked next

Many of the labs that adopted Labevol also ran outpatient clinics — and they wanted one chart for both. So we added the Visits module: outpatient encounters, vitals, specialty-tuned exams (OB/GYN, Peds, Cardio, GI, ENT), prescriptions from a 2,700-drug catalog, imaging orders, and one invoice that rolls up the visit, lab, imaging, and meds.

  • Specialty-tuned doctor exams
  • Structured prescriptions with auto-complete
  • One invoice per visit — lab + imaging + Rx
03 · 2026

Medical centers and ER

Medical centers needed more: triage on condition-of-arrival, serial vitals plotted on a timeline, a dedicated NURSE role that records vitals and nursing notes without overwriting the doctor's clinical fields, and a discharge PDF signed by both doctor and nurse.

  • ESI 1–5 triage acuity
  • Multi-row vitals timeline
  • NURSE role with scoped permissions
  • ER-specific PDF with triage + nursing sections
04 · Today

Architecture beliefs

Labevol is multi-tenant by design. Every record belongs to an organization; every query is org-scoped. Permissions are resource:action strings — not coarse roles — so you can give one user exactly the powers they need. And because Palestinian and MENA infrastructure varies, you can self-host on AWS or Hetzner, or run the managed cloud.

  • Multi-tenant + org-scoped at the query layer
  • Permission-based ("orders:create" not "ADMIN")
  • Self-hosted on AWS / Hetzner — or managed cloud
  • Full activity audit log on every record

The four pillars

01 / Pillar

Accuracy first

A lab's job is to be right. Our job is to make that easier — flagging, validating, signing. Every feature is built with clinical precision in mind.

02 / Pillar

Speed matters

Every minute saved is a result delivered, a decision unblocked, a patient relieved. From triage to WhatsApp delivery, Labevol is optimized end-to-end.

03 / Pillar

Built for teams

Receptionist, nurse, technician, doctor, manager — one system, one chart, zero handoffs lost. Multi-branch, role-based, real-time.

04 / Pillar

Local fluency

Arabic-aware, ILS-native, MENA-ready. We don't ship a translation — we ship a fit. Workflows that match how facilities in the region actually work.

Architecture beliefs

Multi-tenant by default

Every record belongs to an organization; every query is org-scoped. Cross-tenant leakage is impossible by construction.

Permissions, not roles

Roles are display labels. Authorization is resource:action — "orders:create", "visits:triage" — so any role can be customized per user.

Self-host or cloud

Run on AWS or Hetzner under your own control, or use the managed cloud. We don't ship a Vercel-only stack.

Audit everything

Every clinical and financial mutation logs to an immutable activity trail.

Origin · Ramallah, PS

Labevol is built and operated from Ramallah. We understand the regional healthcare landscape because we're part of it.