Plans designed around your laboratory
Laboratory implementations vary too much for a public price list to be honest. Volume, test mix, the number of interfaces, the state of the data being migrated and how much operational support you want all change the shape of an engagement. So we scope first, then quote.
Platform
The GetLabServices software, configured for your laboratory.
For: Laboratories that want a connected system and will run their own operations.
- LIS, lab portal and analytics
- Billing and revenue-cycle workflows
- Configuration for catalog, roles, rules and delivery
- Standard integration interfaces
- Implementation and training
- Most common
Platform + Managed Services
The software, plus trained operational staff working your queues.
For: Laboratories that need capacity as much as they need a system.
- Everything in Platform
- Data entry and document processing
- eFax queue monitoring and validation
- Results processing and delivery support
- Billing operations and AR follow-up
Enterprise
Multi-laboratory deployments with custom infrastructure and integrations.
For: Laboratory groups and healthcare organizations operating several sites.
- Multi-tenant group configuration
- Group-level governance and reporting
- Custom infrastructure arrangements
- Multiple EMR and reference lab interfaces
- Dedicated implementation programme
Custom Development
Purpose-built portals, interfaces, tools and applications.
For: Laboratories with a workflow that configuration alone will not cover.
- Technical discovery and design
- Custom portals and applications
- Bespoke APIs and interfaces
- Dashboards and internal tools
- Ongoing maintenance
Six things that change the shape of an engagement
These are the variables we work through during scoping. None of them is knowable from a website form, which is why there is no price on this page.
Volume and test mix
Specimen volume, panel complexity and the proportion of send-out testing.
Number of interfaces
Each EMR, reference laboratory, instrument and clearinghouse connection is scoped individually.
Migration scope
What has to move from the existing system, and what state that data is currently in.
Operational support
Whether you run the queues yourself or want our team working them.
Sites and users
Single laboratory, multi-site group, and how many people need access.
Custom work
Anything the platform does not do today that your workflow genuinely requires.
Pricing questions
Why is there no price list?
Because a public number would be misleading. Two laboratories with similar volume can differ by an order of magnitude in scope once interfaces, migration and operational support are counted. We would rather scope your workflow and give you a figure that survives contact with reality.
What does the scoping process involve?
A working session to walk your current workflow end to end, a review of the interfaces and data involved, and a written scope with the assumptions stated. You get the scope whether or not you proceed.
Can we start with one part of the platform?
Yes, and many laboratories do. A common starting point is a single workflow — document intake, eligibility, results delivery or billing — connected to the existing system, with the rest phased in later.
Are managed services priced separately?
Managed services are scoped and priced against the volume and the queues they cover. They can be added to a platform engagement or, in some cases, delivered against a laboratory's existing system.
Let's scope it properly.
A working session to walk your current workflow end to end, a review of the interfaces and data involved, and a written scope with the assumptions stated. You keep the scope either way.