For laboratories, clinics and collection agencies
The specimen made it.
The record did not.
Labs still reconcile the clinic, the collector, and the bench after the fact. Recollects start in that gap.
One record from the order to the signed report, for the lab, the clinic and the collector.
Barcoded, racked, and ready for the bench. The record should be just as ready.
What it does
One system from the order to the remittance
Seven things a laboratory, its clinics, its collectors and its billers do every day, in one record instead of seven.
Ordering
Providers order against the lab catalog, in the browser or straight from their practice system, with diagnosis codes attached.
Field collection
A scoped queue on a phone. Identity, kit barcode and time of collection are captured on the spot, not written up later.
Chain of custody
Collected, shipped, received, accessioned. Every hand-off is timestamped against the kit that carried the specimen.
Bench and instruments
Plate layouts, control wells and instrument imports stay attached to the run that produced them, with QC and reflex rules.
Signed release
Releasing freezes an immutable, coded report. A reprint next year is the report that was signed, not a re-render.
Billing
Release drafts the claim from the coded report. The payer's remittance posts payments, adjustments and denials back to it, with aging by payer and client.
Connections
An API for practice systems, external test-code mapping, LOINC and SNOMED on every result. HL7 v2 and FHIR in progress.
- 6
- stages on one record: order, collect, accession, test, release, bill
- 96/384
- well plate layouts with control wells and instrument import
- 4
- coding systems on the catalog: LOINC, SNOMED, CPT and ICD-10
- 3
- kinds of organization on the same specimen: lab, clinic, collection agency
- 7yr
- default retention for clinical and audit records, per tenant
- 100%
- of patient-data reads and writes written to the audit trail
The gap
What this actually costs
Not a missing feature. A week that keeps repeating.
A step gets skipped
Identity, kit, or time of collection is written up later. The specimen arrives. The history does not.
A bag misses the courier
You learn on Friday, when the clinic wants the result, that it never left the counter.
The inspector is in the lobby
Last month's custody trail lives in three inboxes and a spreadsheet named FINAL-v4.
A clinic gets tired of calling
They stop asking where the sample is. They send the next panel somewhere else.
Where it fits
- Clinical, molecular and specialty laboratories, from a single bench to a regional network
- Labs whose clinics and collectors still reach them by email, fax and spreadsheet
- Networks that want the clinic, the collector and the bench on one record
- Anyone replacing a legacy LIMS that only sees the specimen once it arrives
What it is not
- An electronic health record; clinics keep the one they have
- A bench-only system; the record starts at the order, not at accessioning
- A bolt-on portal; the clinic, the collector and the bench work from the same record
Where it is going
What we are building toward
A specimen should have one record, no matter how many organizations touch it.
The clinic orders from its own system
Practice systems send orders straight into the laboratory catalog through the intake API. HL7 v2 and FHIR adapters onto the same endpoint are in progress.
The collector never fills in paper
Identity, kit barcode and time of collection are captured on the phone at the moment of collection, and custody is signed at every hand-off.
The bench sees the whole story
Accessioning, plates, instrument import and QC rules all sit on the same record the order started, so nothing is reconciled after the fact.
The report is the end of an audited chain
Signed, immutable report versions, coded to LOINC, SNOMED, CPT and ICD-10, with every read and write of patient data logged for the life of the record.
Built around HIPAA from the first line: every request is scoped to one organization on the server, and a business associate agreement is part of onboarding.
What we would show you
One record, from the order to the payment behind it
One record, six stages, nothing reconstructed later.
Order
Providers order against the lab catalog, in the browser or from the practice system.
Collect
The collector works a phone queue. Identity, kit, and time are captured on the spot.
Accession
Receiving reconciles what shipped against what arrived.
Test
Plate, controls, and instrument results stay on the run that produced them.
Release
Signing freezes the report. A reprint next year is the report that was signed.
Bill
The claim is drafted from the signed report, and the remittance posts back to it.
Clinical data is scoped to one organization on the server. Reads and writes are logged. A business associate agreement is part of onboarding.
For clinics
Your practice system keeps ordering the way it already does
A clinic connects to a laboratory once. After that an order can come from the practice system itself, and the result goes back to where the order started.
API
One intake endpoint per lab–clinic connection, authenticated with a key rather than a person signing in.
Mapping
Your test codes map to the laboratory catalog once. Anything unmapped waits for a person instead of being guessed at.
Coding
LOINC and SNOMED live on the test definition, so a released result carries the codes downstream systems expect.
Retries
Resubmitting an order returns the one that already exists, so a retry after a timeout cannot create a second specimen.
HL7 · FHIR
In progress. The intake is format-neutral, so each feed becomes an adapter onto the same endpoint, not a second integration.
Before you ask
What labs ask first
Do we have to replace the EHR?
No. Clinics keep ordering the way they already do. The lab is the customer; the clinic is on the network so the specimen has one record, not so anyone has to learn another login.
Can it take orders from our practice system?
Yes. Each lab–clinic connection gets an API intake endpoint. The ordering system's test codes are mapped to the laboratory catalog once, and anything unmapped waits for a person to review. HL7 v2 and FHIR adapters onto the same endpoint are in progress.
Is it built for HIPAA?
Every request for clinical data is scoped to one organization on the server, permissions follow the role a person holds, and reads and writes of patient data are logged. A business associate agreement is part of onboarding.
Does it handle billing?
Yes. Signing a report drafts the claim from its CPT and ICD-10 codes, with the insurance that was captured on the order. When the payer's remittance comes back, payments, adjustments and denial codes post against that claim and it is marked paid on the same record, so receivables age by payer and by client without a second system. Electronic submission through a clearinghouse and live eligibility checks are in progress.
What size of laboratory is it for?
From a single bench to a regional network. The record model is the same whether one site or many are on it, and onboarding is planned around your volume and the systems you already run.
What does getting started look like?
A conversation about how a specimen moves through your lab today, then a plan: catalog, clinics, collectors and codes mapped together with you, not left as a ticket.
Get in touch
Tell us how your specimens move
Describe your process and what breaks. A person replies by email, and the first conversation is about your lab, not a walkthrough. Clinics and collection agencies are welcome too: say so, and we will include the lab you work with.
- A person reads this and replies by email.
- We will not add you to a list.
- Leave patient information out.