Ask Pathology Geek
What makes LIS integration so difficult?
LIS integration is difficult because many systems are decades old, highly customized, and rely on archaic messaging standards (like HL7 v2). Each integration is effectively a custom software project.
The Legacy Debt
Many modern digital pathology and AI tools are cloud-native and API-driven. They are forced to communicate with on-premise LIS platforms built in the 1990s. Bridging these modern architectures with legacy systems requires complex middleware and significant IT resources.
Hyper-Customization
There is no 'standard' LIS installation. A vendor might have 50 clients using the same LIS platform, but each client has customized their workflows, data fields, and reporting templates. An integration that works perfectly at Lab A may fail completely at Lab B.
The HL7 Bottleneck
Most laboratory data still moves via HL7 v2 messages. These text-based messages are notoriously flexible—meaning different labs use different fields to send the same information. Parsing and mapping these messages correctly requires deep domain expertise and careful testing.
Key takeaways
- Never assume an API makes integration easy; the LIS likely doesn't support modern APIs.
- Treat every LIS integration as a custom project due to local configuration differences.
- Invest in HL7 expertise—it remains the language of laboratory interoperability.