One record,
to rule
them all.
A cloud-native LIS with the billing engine built in — not exported to a partner. The order, the result, the 837P and the 835 posting are one object in one platform.
Built by a team that has run CLIA/CAP-regulated laboratories — toxicology and molecular PCR at volume. Meet the founders →
Six stops. One record. No breaks.
"When the LIS and the billing platform are two systems, this line breaks twice — once at the export, once again at reconciliation. Every break is a place where money goes missing and nobody owns the answer."
Run the bench. Get paid for it.
The same record that tracks the specimen runs the claim. Both sides of the lab — clinical and financial — finally looking at the same data.
Run the bench.
- Accessioning, worklists, and specimen tracking for clinical and molecular volume
- Bidirectional instrument interfaces with QC and auto-verification rules
- Reflex and panel logic, including custom panels that bill as components
- EHR result delivery over HL7 v2 and FHIR R4
- Multi-site and multi-tenant from the first record
Get paid for it.
- Eligibility checked at order entry, before the specimen is drawn
- 837P built from the order itself — no export, no re-keying
- ERA and 835 auto-posting, denial worklists routed to the coder
- Reference lab billing: pass-through, direct, and client bill
- Modifier −90, anti-markup; MolDx Z-codes as first-class fields
What actually changes when the claim and the specimen are the same record.
Not a feature list. These are the specific things that stop being possible the moment your billing lives at another company.
Your analyzers, already spoken for.
Interfaces we have built, not a roadmap. Send us your instrument list and we will tell you what exists today.
Built for accredited laboratories, with the audit trail an inspector expects to find.
Encryption in transit and at rest, role-based access, complete access logging.
Standards-based result delivery and EHR connectivity, not a proprietary export.
With the FDA LDT rule vacated in 2025, CLIA and CAP remain the governing framework. We build to it.
The bench, the director, the informatics team, and the person who closes the books.
"Most of what I did on the old system was tell the computer things it already knew. Now the confirmation worklist comes up pre-populated and flags only the parameters that are out of spec. That is the job I was trained for."
"We were running an LIS and a billing platform from two vendors and one person whose entire job was reconciling them. Month-end close took four days. On Lab A SaaS the claim is built off the order record, so there is nothing to reconcile."
"We asked four vendors about our analyzer list, and Lab A SaaS was the only one that came back with what they had already built instead of a quote for development."
"Multi-site was the requirement that eliminated most of the vendors we looked at. Lab A SaaS is multi-tenant in the data model, so a second site is a configuration rather than a project."
Show us your worst denial report.
Thirty minutes, your actual data, no slides. We will walk one specimen from accession to posted payment, and you can tell us where your current stack loses it.
Book a demo