Laboratory software for reference laboratories
A reference laboratory is an interoperability business. Orders arrive from other laboratories and health systems, results have to return in their format, and reconciliation has to be exact.
Where the workflow bites
- Order01
- Testing06
- Release08
- Analytics10
What carries the weight
- Client laboratory onboarding
- Order and result exchange
- Send-out management
What makes this laboratory type different
Reference laboratories carry the integration burden for everyone who sends them work. Every client laboratory has a different system, a different test code set and a different expectation for how results come back.
Every client is an interface
Onboarding a client laboratory means mapping their catalog, their codes and their delivery format.
Test code mapping
Your catalog and theirs are never identical, and mismatches surface as failed orders.
Reconciliation at volume
What was sent, what was resulted and what was returned must reconcile continuously.
Client-specific reporting
Different clients need different report layouts, delivery routes and billing arrangements.
GetLabServices is configured around this workflow — not adapted to it afterward.
What matters most for this workflow
The whole platform is available. These are the parts that carry the most weight for this laboratory type.
Client laboratory onboarding
Per-client catalogs, code mappings, delivery routes and billing configuration.
Order and result exchange
HL7 and API interfaces for inbound orders and outbound results, with error queues that are actually monitored.
Send-out management
Outbound routing to your own reference partners, tracked to return and reconciled on import.
Per-client reporting
Volume, turnaround and revenue broken out by client laboratory.
Where this laboratory type feels the workflow most
Every stage applies. These are the ones worth looking at closely for your operating model.
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.
Reference laboratory questions
How are test code mismatches handled?
Mappings are configured per client between their code set and your catalog. Unmapped codes fail into an exception queue with the offending code visible, rather than silently creating the wrong order.
Can each client get its own report format?
Yes. Report templates and delivery routes are configured per client laboratory and per facility within it.
The platform
All six capabilities on one data model.
Managed services
Trained operational support where you need capacity.
Clinical Laboratories
High-mix routine testing across many ordering sites, where intake volume and turnaround time decide everything.
Molecular Laboratories
Panel-driven testing with complex result structures, batch workflows and demanding documentation requirements.
Toxicology Laboratories
Screen and confirmation workflows with chain-of-custody discipline and payer scrutiny on every claim.
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.