Home
What LabFlow is, what it does not attempt, and four parts of the product you can operate on the page rather than read about.
Sitemap
A sitemap for people rather than for a crawler. Every page is here with what it actually answers, so the useful way to use this page is to type the thing you are trying to find out.
Search state goes into the address bar, so a link you send shows what you found rather than an empty page.
Both are generated from the same route list this page is generated from, in the same build. Two hand-maintained lists disagree within a week, which is why there is only ever one.
The list search engines read to discover pages. It carries every public address with the date it last changed, and nothing that sits behind sign-in. If you are wondering whether a page of ours is indexable, this file is the answer.
The same content as the feed page, in the format a reader application understands. Subscribe to it and a new explainer, or a revision to one of the legal documents, arrives without you checking.
What LabFlow is, what it does not attempt, and four parts of the product you can operate on the page rather than read about.
The public directory. Search laboratories by test, location and turnaround, and see what each one publishes about itself.
What is built, module by module, with a stated limit beside each claim rather than a checklist of adjectives.
What changes in a laboratory's day, argued from the workflow rather than from a percentage nobody can check.
Three plan shapes and no prices, because nothing is purchasable yet. The page says so rather than implying a checkout.
Four honest comparisons with established systems, each of which names the cases where the other one is the right answer.
The laboratory module of an electronic health record suite. Really a question about whether your laboratory sits inside a suite or beside one.
The same structural position from a different vendor, now part of Oracle Health, with a long installed base across hospitals.
The closest of the four in what it is for. This is the comparison where the difference is genuinely about maturity rather than category.
A configurable platform organised around the sample rather than the patient. Settle which of those two nouns your work is built on first.
Five explainers about the domain rather than about the product, with a search and a note about what is deliberately absent.
Six rules, what each is looking for, and the arithmetic explaining why running all of them produces more false rejections than real ones.
The honest answer is v2, and the reason is not technical merit. It is which systems you have to talk to this year.
One is organised around a patient and the other around a sample. Buying the wrong one is usually discovered at the first assessment.
Why a list query has to prove its own tenant from its own filters, and why the leak that follows from not doing it returns a clean success.
What queues, what cannot queue, and why a conflict in a clinical record has to reach a person instead of being resolved by a rule.
Who built this, how the domain was learned, and a ledger of the claims that were removed from this site along with what replaced them.
One inbox, the LabFlow team, no rota. The page says what that means for how long a Friday message waits.
Thirty-six answers grouped by subject, searchable, including the ones where the answer is that it is not built yet.
Seven of these are one page with seven addresses. Each address is real and each has its own document.
What is handled, in three groups, and the four companies that see any of it. Eleven clauses.
The agreement, including plans when nothing is purchasable, and the governing-law clause that is honestly still missing.
The same agreement at its second indexed address, which says on its face that it is a duplicate and which one is canonical.
Why the word used here is conscious, the safeguards that exist, and the six things that do not, starting with the absent agreement.
The engineering answer: the boundary, the roles, the audit trail, what leaves in an error report, and where the backups actually are.
A table of every key this site writes to your browser, and the reason there is no consent banner in front of it.
Every Android permission with what refusing it costs you, the one that is stripped out, and the one that is there and unused.
The request form, plus the four retention windows and the five things a deletion request cannot reach.
For people who already have an account at a laboratory that runs LabFlow.
Starts a laboratory tenant. It is free, nothing is purchasable, and no card is asked for at any point.
Sends a link to the address on the account. It never reveals whether an address has an account, which is deliberate.
Everything published on this site in date order, including revisions to the legal documents, which is the part a compliance reader wants and almost never gets.
This page. Every public address grouped and searchable, with the two machine-readable files at the top and a note about what is deliberately absent.
LabFlow is mostly an application behind a sign-in: worklists, result entry, validation queues, quality-control charts, reports, administration. Those addresses are not in this sitemap and not in the XML one, and the site's robots file tells crawlers to stay out of them.
A sitemap listing a page nobody can open is not helpful to a reader and is actively unhelpful to a search engine, which spends its crawl budget discovering that every one of them redirects to a sign-in form.
No dashboard, worklist, patient, order, result or report address appears in either sitemap. They exist; they are not public, and a sitemap is a list of public things.
The platform administration surface is not linked from anywhere public and is not listed anywhere public.
Directory entries are public and are discoverable through the directory, which is the page designed to search them. Enumerating them here would duplicate that badly.
Every page above is built. A sitemap listing a planned page is the fastest way to teach a search engine that this site returns errors.