About LabFlow
LabFlow is a multi-tenant Laboratory Information Management System for clinical laboratories, designed, built and maintained by the LabFlow team.
Contact the LabFlow team
| Channel | |
|---|---|
| aoneahsan@gmail.com | |
| Documentation corrections | github.com/aoneahsan/labflow-docs — issues and suggested edits |
| Support the project | Support LabFlow |
If you want LabFlow at your laboratory, email is the fastest channel.
What LabFlow is built with
React 19 and TypeScript on the front, one hosted Supabase Postgres project behind it, and row-level security as the actual access boundary rather than a layer of application checks over an open database. The schema is declared in TypeScript and the migrations are generated from it.
The design principles that shape it are on the architecture pages: one writer per value, append-only trails, versioned results, and no number on a screen that the database did not compute.
Licensing
The LabFlow application repository is private. This documentation repository is public, so the docs can be indexed, read and corrected without exposing the application's source.
Supporting the project
- Contribute financially — Support LabFlow.
- Send corrections. If a page here describes something that does not match the product, that is a defect in the documentation and worth an email or an issue. Accuracy is the point of this site.
Citing LabFlow
LabFlow team. LabFlow — Multi-tenant Laboratory Information Management System.
Documentation: https://labflow-docs.aoneahsan.com
Application: https://labflow.aoneahsan.com
Acknowledgements
- React, TanStack (Query, Router) and React Aria Components — the runtime, the routing and data layer, and the accessibility primitives.
- Supabase and PostgreSQL — the database, and the row-level security that makes multi-tenancy provable rather than promised.
- D3 — every chart in the product.
- LOINC — without a coded catalogue, a test name is just a word.
- Docusaurus — what you are reading.