# LabFlow documentation

> Documentation for LabFlow, a multi-tenant laboratory information system for clinical laboratories, fronted by a public directory where patients find laboratories, with patient and clinician portals. Built and maintained by the LabFlow team.

LabFlow records the clinical laboratory's work: patients, a test catalogue with panels and reference
ranges, orders, specimens with an append-only chain of custody, accessioning, barcode labels, result
entry at the bench, result review, and release gated by the releasing person's role. A released result
is amended by adding a new version, never by overwriting — the original stays readable, with who
changed it and why.

The backend is hosted Postgres on Supabase. Every row belongs to a laboratory and row-level security
refuses a read or a write that crosses that boundary, so isolation is a property of the database
rather than of application code that has to remember. Firebase serves the static web build and holds
no user data: there is no Firestore, no Firebase Authentication and no Cloud Functions.

Honest framing, because this is the part most documentation gets wrong: **LabFlow is
HIPAA-conscious, not "HIPAA-compliant"** — compliance is a property of an organisation and its
processes, and no software can hold it on your behalf. There is no FDA, CAP, CLIA or SOC 2
attestation. LabFlow is laboratory software, not a medical device, and it interprets nothing.

**What is built:** the public surface and directory, identity and laboratory setup, settings, user
management, forms, the clinical spine listed above, billing (invoices, payments, claims), stock and
equipment, quality control with Westgard rules, compliance and the audit trail, documents and workflow,
appointments and home collection, reports and analytics, research, population health and telemedicine
registers, the patient portal, the clinician portal, laboratory listing and My lab, a referral
programme, and platform administration (plans and limits, maintenance mode, the review queue).

**What is NOT built, and is not claimed anywhere:** a live interface to any analyser, EMR or hospital
system — HL7 v2 and FHIR R4 are exported and imported as files only. There is no public API, no
browser extension and no EMR add-on. There is **no iOS application in any form**. The Android app is
built but not released on Google Play. Email delivery is being moved onto one branded layout.

## Documentation

- [Introduction](https://labflow-docs.aoneahsan.com/docs/intro): what LabFlow is, what it runs on, and what it does not do.
- [Quick start](https://labflow-docs.aoneahsan.com/docs/getting-started/quick-start): from an account to a released result.
- [Create or join a laboratory](https://labflow-docs.aoneahsan.com/docs/getting-started/create-or-join-a-laboratory): the two ways in, and what each needs.
- [Finding your way around](https://labflow-docs.aoneahsan.com/docs/getting-started/finding-your-way-around): the shape of the application.
- [Architecture overview](https://labflow-docs.aoneahsan.com/docs/architecture/overview): the stack, and where each thing lives.
- [Tenancy and row-level security](https://labflow-docs.aoneahsan.com/docs/architecture/tenancy-and-rls): how one laboratory is kept out of another's records.
- [Records and trails](https://labflow-docs.aoneahsan.com/docs/architecture/records-and-trails): custody, audit, result versions, and the one-writer rule.
- [User guide](https://labflow-docs.aoneahsan.com/docs/user-guide/overview): one page per shipped area, indexed by task.
- [Patient portal](https://labflow-docs.aoneahsan.com/docs/user-guide/patient-portal): results in plain words, reports, invoices, sharing.
- [Clinician portal](https://labflow-docs.aoneahsan.com/docs/user-guide/clinician-portal): ordering and acknowledging critical results.
- [Interoperability](https://labflow-docs.aoneahsan.com/docs/user-guide/interoperability): HL7 v2 and FHIR R4 as files; no live interface.
- [Platform administration](https://labflow-docs.aoneahsan.com/docs/user-guide/platform-administration): plans and limits, maintenance, the review queue.
- [Android app](https://labflow-docs.aoneahsan.com/docs/getting-started/android-app): built, not yet released.
- [Status and limits](https://labflow-docs.aoneahsan.com/docs/roadmap): what is not built, stated plainly.
- [Hosting and publishing](https://labflow-docs.aoneahsan.com/docs/deployment/overview): how the application and this site are served.

## About and licensing

- [About LabFlow](https://labflow-docs.aoneahsan.com/docs/author): the LabFlow team — contact, corrections, citation.
- The LabFlow application source is a single private repository. There is no public source repository; this documentation site is published openly.

## Contact

- Email the LabFlow team: aoneahsan@gmail.com
- Application: https://labflow.aoneahsan.com