Status and limits — what is not built
Every product area planned for LabFlow is built, and the web application is live at labflow.aoneahsan.com. The user guide documents each one. This page lists what is still being finished, what is not built, and the claims LabFlow does not make.
Built, not yet finished
| Area | Where it stands |
|---|---|
| The Android app | On Google Play. The next version, 2.8.0, is built and waits for its release. See The Android app |
| Card payments | On. A laboratory's owner pays for Single laboratory or Multi-site by card on the website, under Settings → Plan & billing; see settings |
Things frequently assumed to exist
Some of these are named because an earlier version of this site claimed them. None is true today.
| Claim | Status |
|---|---|
| A live HL7, ASTM or FHIR interface to analysers, an EMR or a hospital system | Not built. HL7 v2 and FHIR R4 are exported and imported as files; nothing is sent or received automatically |
| Validated EMR vendor mappings (Epic, Cerner, and others) | Not built, and never validated against any EMR vendor |
| A public or REST API, webhooks, an OpenAPI document | Not built. LabFlow exposes no third-party API |
| An iOS application | Not built, and not planned |
| A browser extension or an EMR add-on | Not built |
| Paying an invoice or buying a plan inside the application | Not offered. A patient can tell the laboratory they intend to pay; payment is arranged outside the application. Plans are arranged with the LabFlow team and applied by an administrator |
| Notifiable-disease reporting to a public-health authority | Not built. Population pages count; they submit nothing |
| A symptom checker or any diagnostic advice | Refused by design. See telemedicine |
| Whole-slide imaging | Not built. The slide viewer holds one uploaded image per specimen |
| Machine learning or predictive analytics | Not built, and not intended. Where LabFlow evaluates rules, they are arithmetic on recorded data, and the product says so |
| Patient statements | Not claimed here |
| Part 11 validation documentation | Not built. The audit trails and versioning exist; the documentation package does not |
| HIPAA compliance, FDA clearance, CAP or CLIA accreditation, SOC 2 | Not claimed. LabFlow is HIPAA-conscious — see On compliance |
| On-premise deployment, a dedicated VPC, a BAA, 24/7 phone support | Not offered |
Two result statuses that exist but are never written
The result_status vocabulary carries eight values. Six are reachable from the application. preliminary and validated are present and not written by any screen — they are in the vocabulary and in the filter because the workflow they belong to is real. A status no screen can produce is documented here rather than quietly removed.
See result review and release for the statuses that are in use.