About

The LabFlow team, and every claim is checkable.

A multi-tenant laboratory information system and a public marketplace, built and funded by the LabFlow team. This page states what that means before you have to ask.

See what is built Talk to the team that built it

The facts this page is held toverifiable

Built byThe LabFlow team

RepositoryPrivate. Not open source.

FundingSelf-funded. No investors.

CertificationNone. HIPAA conscious, not compliant.

Payment gatewayNone. Nothing is purchasable.

Published appsNone yet. Web is the live surface.

Six rows, and every other section on this page has to stay consistent with them. That is the point of putting them first.

Two products that need each other.

The first is a laboratory information system: patient registration, test ordering, specimen chain of custody, result entry, quality control, validation and the audited release of a signed report. The second is a public marketplace where a patient finds a laboratory and a laboratory applies to be listed.

They are one codebase because the marketplace is worthless if the laboratory behind it cannot produce a trustworthy result, and the laboratory system is harder to sell if nobody can find the laboratory.

Roles11

Chain stages6

Offline custody actions17

Result statuses8

Four counts, and each one counts something you can see on the features page. There is no user count, no laboratory count and no uptime figure here, because none of those would be true.

There is no team page, and no invented job titles.

LabFlow is written, deployed, supported and answered by the LabFlow team, in one time zone, with no larger organisation behind it. That is unusual for clinical software and it is the first thing a laboratory director should weigh, so it is stated here rather than buried in a footer.

It has consequences in both directions. Decisions are fast and there is nobody to hide behind when something is wrong. There is also no overnight rota, no independent review of the code, and no larger company behind the team. The risk that creates is set out below, with what does and does not protect you against it.

Who answersthe same team

Writes the codeThe LabFlow team

Runs the deployThe LabFlow team

Reads your emailThe LabFlow team

Signs a contractThe LabFlow team

A message reaches a real inbox rather than a ticket queue. That is a consequence of the size of the team, not a service promise, and it is the reason there is no 24/7 support claim anywhere on this site.

The domain was read, not surveyed.

Clinical laboratory practice is one of the best-documented fields in software, because it had to standardise before it could exchange anything. Four published rule sets carried most of the design. Naming them is more useful than claiming a research programme that did not happen.

LOINC

The universal code for "which observation is this". It is why a haemoglobin ordered at one laboratory means the same thing when a second laboratory receives the record, and why the test catalogue is coded rather than free text.

What it does not buy: LOINC identifies the observation. It does not tell you the reference interval, which is method and population specific and is resolved separately.

HL7 v2

The message format most analysers and most hospital systems still speak. LabFlow exports a released report as an HL7 v2 file and imports an order file as a draft a person confirms.

What it does not buy: a live feed. Nothing listens for messages or sends them across your network. That limit is stated on the features page as well.

FHIR

The newer resource model, for systems that expect it rather than a pipe-delimited message. A released report exports as a FHIR R4 bundle file, built from the same records as the report, so the two cannot drift apart.

What it does not buy: producing a valid resource is not the same as passing a named connectathon or a vendor certification. Neither has been done.

Westgard multi-rule quality control

The rule set that decides whether a control run is in control, and therefore whether a patient result produced beside it may be released at all. It is the reason release is a gate in LabFlow and not a button.

What it does not buy: the rules are evaluated. Choosing which rules apply to which analyte, and acting on a violation, remains the laboratory's professional judgement.

The ledger

Claims you will not find on this site, and what replaced them.

Health IT marketing is full of sentences that cannot be checked. These were all on this site until they were removed. They are listed rather than quietly deleted, because a vendor who tells you what they refuse to claim has told you something useful about everything else on the page.

HIPAA compliantRemoved

No software is HIPAA compliant. Compliance is a property of an organisation and its processes, and a certificate for it does not exist. LabFlow is HIPAA conscious: audit logging, least-privilege access, tenant isolation and recorded consent are designed in, and the word compliant is not used.

Serving laboratories around the worldRemoved

There are no laboratories using LabFlow in production, no pilot tenants, and therefore no user count to publish. A count of zero is the honest number, and it is on this page rather than absent from it.

Open source, built by a global communityRemoved

The repository is private and has one author. There is no community, no contributor list and no licence granting you the source. If source availability matters to your procurement, it is a conversation and not a checkbox.

AI-powered predictive analyticsRemoved

The features this described are rule-based, and the code says so in its own function names. A delta check is arithmetic against a previous result. A Westgard evaluation is a published rule set. Calling either one machine learning would mislead a reviewer about how the number in front of them was produced, which in a clinical system is the worst place to be vague.

We will sign a BAARemoved

A business associate agreement is a legal commitment, and advertising one that has never been drafted or reviewed is worse than offering nothing. It is not offered today. The same applies to on-premise deployment, a dedicated VPC, 24/7 phone support and nightly backups, all of which were listed and none of which exist.

Validated Cerner, Epic, athenahealth and Allscripts integrationsRemoved

LabFlow exports and imports HL7 v2 and FHIR as files, with no live feed. Nobody has validated a mapping against any of those four products, and the named-vendor list implied a certification programme that does not exist. Auto-faxing was on the same list and is also not built.

Insurance claim generation and denial managementRemoved

837P and 837I generation, 835 remittance parsing, ERA posting and patient statements were all described. None of them is built; invoices, payments and claim records are, with denials and appeals recorded by hand. If revenue cycle is what you need, LabFlow is not the product and saying so early is cheaper for both of us.

Calibration scheduling and trackingRemoved

There is no calibration scheduling or reminder module. Quality control is built and calibration dates and results are recorded on the equipment register, but the two were previously described as though they were one feature.

Available on iOSRemoved

The iOS platform was removed from the project. An Android application is built from the same codebase and has never been published to a store. The web application is the surface you can actually use today.

If you find a claim on this site that you cannot check, that is a defect and it is worth telling us about. Send it to the inbox.

Four rules the code is actually held to.

These are enforcement decisions, not values. Each one is visible in the behaviour of the product rather than only in a document.

A result is versioned, never overwritten

A correction is a new row pointing at the row it supersedes. The earlier value stays released and stays true as of when it was released, because that is the value a clinician acted on.

A tenant's data never leaves its boundary

Every list query has to prove that from its own filters rather than relying on the caller to be careful. A query that cannot prove it is treated as a bug even when it returns the right rows.

Release is a gate, not a button

A result whose quality-control run is out of control cannot be released, and the refusal names the rule that refused it. Overriding it is a recorded act with a person's name on it.

The audit log is not optional

Who did what, to which record, when. It is written by the same path that performs the action, so an action that skipped the log would also have skipped the work.

Self-funded, which changes the price and the pressure.

A quote reflects engineering and infrastructure cost. Nobody is going to be told to raise it because a board wants a different number, and equally there is no war chest behind it. Both halves of that are true at once, and a laboratory director should weigh both.

There are no investors, so there is no return to price for and no growth curve to hit by the end of a quarter.

It also means the free tier is subsidised by the paid shapes rather than by someone else's money, and that there is no plan to sell your laboratory's data to widen it.

Three columns, and nothing moves between them quietly.

A roadmap item described in the present tense is the most common lie in software marketing. These are kept apart on purpose.

Shipped

You can use it today

Patient registration and the shared patient record
Test catalogue, ordering and the worklist
Specimen accessioning and chain of custody
Result entry, reference-range resolution and delta checks
Westgard multi-rule quality control
Validation, the release gate and signed reports
Result versioning and amendment
Critical-value flagging and escalation
Roles, permissions and the audit log
HL7 v2 and FHIR export and import, as files
The public marketplace and laboratory applications
Platform administration

Planned

Named, and not described as done

The validation documentation package a Part 11 assessment expects
A published Android build
A payment path, web only, when there is something to charge for
Plan limits that are actually enforced rather than recorded

Planned means designed and not built. It does not mean soon, and there is no date on this page because there is no date worth trusting.

Not planned

Do not wait for these

Revenue cycle management: 837P, 837I, 835, ERA posting, patient statements
Calibration scheduling and reminders
An iOS application
On-premise deployment and a dedicated VPC
Auto-faxing

If one of these is a requirement, LabFlow is the wrong product for you and this is the cheapest possible place to find that out.

It is a laboratory system. It is not the rest of the hospital.

Adjacent categories that a laboratory system is regularly assumed to cover, and does not.

Not an electronic health record

It holds the laboratory's view of a patient, not their clinical history. It is designed to send results to whatever system does hold that.

Not a billing or claims system

No claim is generated, no remittance is parsed and no statement is produced.

Not an instrument driver

Messages are built and parsed. The middleware that talks to the analyser on your bench is a separate piece of infrastructure and it is yours.

Not a quality management system

Quality control runs are evaluated. Document control, competency records and non-conformance workflows are not part of it.

Not a substitute for your accreditation work

An audit trail helps an assessment. It does not pass one, and no vendor can promise that it will.

Not a diagnostic device

Every clinical decision in the product is made by a named person, and the software records who made it.

What happens to your laboratory if the LabFlow team stops.

This is the first question a serious buyer asks and it deserves a straight answer on a public page. Half of the answer is reassuring and half of it is not.

What protects you

Your data is exportable in formats other systems read

Released reports download as HL7 v2 and FHIR files, formats another laboratory system reads. An export is not a proprietary archive that only LabFlow can open.

The audit trail is data, not a feature

It is rows in your tenant, exportable with everything else. An assessment that needs seven years of history does not depend on the product still existing.

Nothing is locked behind a payment relationship

There is no gateway, so there is no subscription that can lapse and take your access with it while a dispute is resolved.

What does not

There is no source escrow

The repository is private and no escrow arrangement exists. If that is a procurement requirement, it has to be negotiated rather than assumed, and it is not offered today.

There is nobody on call

A serious incident is handled by the LabFlow team in one time zone. There is no overnight rota and no escalation path beyond the team, and no support tier on this site claims otherwise.

There is no larger company behind the team

Continuity of the product is continuity of the LabFlow team's attention. That is the honest shape of the risk, and it is why it is printed here rather than discovered later.

Four ways in, and all of them end at the same inbox.

There is no sales team to be routed to, so the route is short.

Ask a question about the productThe contact form. Expect a person, not an autoresponder.Ask what it would cost for your laboratoryThere is no price list, so this is a conversation. See /pricing for what drives the number.Apply to be listed as a laboratoryFive states, and a person reads the application. Listing a laboratory is not a self-serve checkout.Read the answers already written downThe questions that get asked most, including the awkward ones.

The rest of the argument

Features

Every capability, named, with the limit attached to it rather than in a footnote.

Benefits

What changes for a technician, a pathologist, a manager and a patient, one at a time.

Pricing

The plan shapes, what drives cost, and why no figure is printed yet.

FAQ

Searchable, including the questions a vendor would rather you did not ask.

If this page made you more sceptical, it worked.

The purpose of an about page in clinical software is not to be liked. It is to let you decide whether to spend an hour on the next conversation, with an accurate picture of who is on the other side of it.

Everything above is checkable. If any of it turns out not to be, that is the most useful email you could send.

Start a conversation Read what is built

Deliberately unavailable. No payment gateway exists, so a button that took your card details would be a lie about what happens next. Plan shapes are published at /pricing and quoted in conversation.