A modern LIS built around your laboratory workflow
Not a records database with screens attached. The LIS models the whole path a specimen takes — catalog, order, accession, testing, result, release — and the rules that govern each transition.
Orders today
Awaiting accession
Pending results
Median TAT
Specimens in progress
| Accession | Patient | Test | Stage | Elapsed |
|---|---|---|---|---|
| A-284119 | P. Nakamura | CMP | Testing | 2h 14m |
| A-284120 | R. Oyelaran | Tox screen | Confirmation | 5h 02m |
| A-284121 | J. Whitfield | CBC w/ diff | Verified | 1h 46m |
| A-284122 | S. Bhattacharya | PGx panel | Send-out | 31h 08m |
| A-284123 | M. Okonkwo | Lipid panel | Released | 3h 27m |
Accessions by hour
Routing
- In-house312
- Reference74
- Held32
Illustrative interface. Figures are examples, not customer data.
Order → requisition → data → eligibility → accession → specimen → testing → result → review → release → billing
Each transition is a state with its own rules and its own exceptions. Select a stage to see what the LIS does there.
01Order
A provider places an order.
Orders reach the laboratory through the portal, an EMR interface, an API call, or as a document — a faxed or scanned requisition. All four paths land in the same order queue rather than four separate inboxes.
- Provider
- Ordering provider, NPI and the facility the order came from
- Patient
- Demographics, insurance and prior history if the patient is known
- Tests
- Test selection against your catalog, with CPT and diagnosis codes attached
What the platform does here
- Portal ordering for providers and clinics
- EMR/EHR order interfaces over HL7 or API
- Document intake for faxed and scanned requisitions
- Standing order and recurring order support
Documents are classified and read before a person touches them, so a faxed requisition arrives as a structured draft order.
What the LIS covers
Configuration, people and places, order and specimen handling, testing and results, and the architecture underneath all of it.
Catalog and configuration
The test catalog is the spine of the system. Get it right and most downstream behaviour follows from it.
Test catalog
Tests, panels and profiles with specimen requirements, containers, methodology and reportable ranges.
Test configuration
Result types, reference ranges by demographic, flags, reflex rules and routing on a per-test basis.
CPT and ICD associations
Billing codes attached at the level that actually bills, so the claim does not need reinterpretation later.
Report templates
Report layout, interpretation blocks, methodology and signature configuration per test or per client.
People and places
Who orders, where they order from, and who inside the laboratory can do what.
Provider management
Ordering providers with NPI validation, contact details and delivery preferences.
Facility management
Client facilities with their own catalogs, report formats, delivery routes and billing arrangements.
Patient management
Patient records with matching rules, merge handling and full demographic history.
Users and roles
Role-based permissions covering entry, verification, release, billing and administration.
Order and specimen
From the order arriving to the specimen being ready to test.
Order management
Orders from the portal, EMR interfaces, API and documents, all in one queue with one set of rules.
Requisition management
Requisitions and attachments linked to the order, with the original document retained.
Accessioning
Accession number generation, receipt recording and rejection workflows with documented reasons.
Barcode and label workflows
Label printing to your formats, aliquot labelling and barcode-driven specimen handling.
Specimen tracking
Specimen state from receipt through testing, storage or send-out, visible without asking.
Sample received status
Explicit receipt status so 'we never got it' becomes an answerable question.
Testing and results
Where the laboratory's actual work is recorded, checked and signed out.
Testing workflow
Worklists by department, bench or instrument, with status visible per specimen.
In-house testing
Result entry with reference ranges, units, flags and delta checks applied automatically.
Reference laboratory routing
Per-test routing rules, send-out creation, partner code mapping and return tracking.
Result entry
Manual entry, import and interface ingestion against the correct accession.
Result verification
Configurable verification requirements before a result becomes releasable.
Result release
Release as a controlled, role-gated action with a record of who released what and when.
Report generation
Reports rendered to your laboratory's format, per test type and per client where needed.
Critical result workflows
Critical values surfaced and the notification workflow your laboratory defines, documented.
Amended results
Versioned amendments with the original retained and delivery of each version recorded.
Result history
Prior results for the patient available in context during verification.
Platform and architecture
The parts that decide whether the system can still be used in five years.
Audit trails
Field-level change history with previous value, new value, acting user and timestamp.
Multi-location support
Several facilities and testing locations under one laboratory, each with its own configuration.
Multi-tenant architecture
Laboratory groups running several laboratories with data isolation enforced at the platform level.
API integrations
Authenticated REST APIs scoped per consumer and per organization.
HL7 messaging
ORM, ORU and ADT message handling with per-counterparty mapping and visible error queues.
FHIR-ready architecture
A resource model structured for FHIR exchange, so it can be added per counterparty.
EMR/EHR connectivity
Order and result interfaces scoped per clinical system, with constraints stated up front.
LIS questions
Can the LIS run alongside a system we already have?
Yes. Laboratories commonly begin with one workflow connected by interface — document intake, eligibility, results delivery or billing — and expand from there rather than replacing everything at once.
How configurable is the test catalog?
Tests carry their own specimen requirements, result structure, reference ranges, flags, reflex logic, routing rules, billing codes and report template. Group-level catalogs can be inherited by individual sites.
Does the LIS handle send-out testing?
Yes. Routing between in-house and reference testing is a rule on the test. Send-outs are created, transmitted with mapped partner codes, tracked to return and reconciled against the original order.
What happens to results that need to be corrected?
Amendments are versioned. The original stays in the record, the amendment is identified on the report, and the delivery log shows which recipients received which version.
Lab Portal
The provider, clinic and patient experience on top of the LIS.
Billing & RCM
Claims built from the same order the laboratory ran.
Integrations
HL7, FHIR-ready architecture, EMRs, reference labs and APIs.
AI Automation
Document intake, extraction and human-in-the-loop review.
Results Management
Managed operational support for result workflows.
What is an LIS?
A plain explanation of what an LIS actually does.
Ready to modernize your laboratory?
Whether you need a complete LIS, billing infrastructure, workflow automation, integrations, or managed operational support, let's build the right solution for your laboratory.