The Integration Layer Approach: Why Rip-and-Replace Fails in Regulated Industries
Every few years, a pharmaceutical company embarks on a "digital transformation" initiative. The pitch is appealing: consolidate your fragmented quality systems into one unified platform. Eliminate the spreadsheets. Retire the legacy systems. Achieve operational excellence.
These initiatives usually fail.
Not because the technology doesn't work, but because the premise is wrong. Regulated industries aren't fragmented by accident—they're fragmented for good reasons. The winning strategy isn't consolidation; it's orchestration.
At Cohera, we built our entire platform around this insight. Here's what we learned.
Why Fragmentation Happens
Pharmaceutical companies typically run 8-15 quality-related systems:
- Document management: Veeva Vault, MasterControl, Documentum
- Quality management: TrackWise, Sparta TrackWise Digital, ETQ
- ERP/materials: SAP, Oracle
- Laboratory information: LIMS (LabWare, Thermo Fisher)
- Manufacturing execution: MES systems
- Supplier management: Various platforms or spreadsheets
- Training: ComplianceWire, Cornerstone
- Regulatory submissions: Veeva RIM, IQVIA
This fragmentation isn't incompetence. It's the result of rational decisions:
Best-of-breed wins. Each domain has a market leader optimized for that specific use case. Veeva Vault is exceptional for regulated document management. TrackWise is exceptional for CAPA and deviation tracking. No single system is best at everything.
Regulations require specific capabilities. Different regulations emphasize different things. A system optimized for FDA submission management isn't the same as one optimized for GMP manufacturing.
Validation freezes choices. Once a system is validated for GxP use, changing it requires significant effort. The validation cost alone can exceed the software cost.
M&A compounds fragmentation. Pharmaceutical companies grow through acquisition. Each acquired company brings its own systems.
Why Rip-and-Replace Fails
I've watched several "consolidation" initiatives fail in pharma. The pattern is consistent:
Year 1: Executive sponsor announces the vision. Vendor selected. Project team assembled. Energy is high.
Year 2: Implementation begins. Requirements explode as edge cases emerge. The consolidated platform can do 80% of what each specialized system does, but that missing 20% is critical.
Year 3: Customization begins. The "platform" becomes a heavily modified version that's hard to upgrade. Costs balloon.
Year 4: Parallel running. Old and new systems run simultaneously. Users hate it. Data synchronization is a nightmare.
Year 5: The project is quietly scaled back, declared "phase 1 complete," and the initiative loses steam. The old systems are still running.
Why does this happen?
Scope creep is inevitable. When you try to replace N systems, you need N sets of requirements. Each department has "must-have" features that the consolidated platform doesn't have.
Change management is overwhelming. Changing one system is hard. Changing 8 simultaneously is nearly impossible. User resistance compounds.
The switching cost is massive. Each system has years of data, custom workflows, integrations, and trained users. Migrating all of this is a multi-year effort.
Validation requirements multiply. You need to validate the new system, migrate and verify data, and retire the old systems—all while maintaining compliance. The validation effort alone can take years.
The Integration Layer Alternative
What if instead of replacing systems, you connected them?
An integration layer approach accepts that specialized systems exist for good reasons. Instead of fighting this, you embrace it:
Keep your best-of-breed systems. Veeva stays. SAP stays. TrackWise stays. Each continues to do what it does best.
Create a unifying data layer. The integration layer builds a coherent model of your data across systems. A supplier in SAP, a supplier contact in the supplier portal, and supplier documents in Veeva are all understood as the same entity.
Enable cross-system queries. "Show me all products that use materials from this supplier" is now answerable in seconds, even though the data lives in three different systems.
Automate cross-system workflows. When a certificate arrives, the integration layer can update records in multiple systems while maintaining audit trails in each.
How We Designed Cohera
Cohera is built as an orchestration layer. Here's the architecture:
Ontology Layer
At the core is a semantic model that defines objects and their relationships:
Supplier
├── has_many: Certificates
├── supplies: Materials
├── has: Contact_Persons
└── documented_in: Documents (Veeva)
Material
├── comes_from: Supplier
├── used_in: Products
├── has: Specifications (SAP)
└── tracked_by: Lot_Records
Certificate
├── belongs_to: Supplier
├── covers: Materials
├── stored_in: Document_System
└── verified_by: Quality_Events
This ontology is system-agnostic. A Material exists as a concept regardless of whether its master data lives in SAP, Oracle, or a custom system.
Connectors
We built connectors for common pharmaceutical systems:
- Veeva Vault (document management)
- SAP QM (quality management)
- TrackWise (CAPA and deviations)
- LIMS (laboratory data)
Each connector handles:
- Authentication and authorization
- Data synchronization (bi-directional where needed)
- Schema mapping to our ontology
- Change detection and event propagation
AI Agents
On top of the unified data model, AI agents automate workflows:
- Intake Agent: Processes incoming documents, extracts data, proposes record creation
- Impact Agent: When something changes, traces relationships to identify affected records
- Query Agent: Answers natural language questions about the unified data
Compliance Layer
Everything sits on a compliance foundation:
- Complete audit trails for all operations
- Electronic signature support
- Role-based access control
- Data retention and archival
The Benefits
This approach delivers benefits that consolidation can't:
Incremental adoption. You don't need to change everything at once. Start with one integration, prove value, expand.
Preserved investments. The millions you've spent on Veeva, SAP, and TrackWise aren't wasted. Those systems keep running.
Lower risk. If the integration layer fails, your core systems are unaffected. You can't say that about a failed consolidation.
Faster time to value. Connecting two systems takes weeks, not years. You see ROI quickly.
Innovation without disruption. When a better LIMS comes along, you can switch that system without affecting the entire ecosystem. The integration layer adapts.
Implementation Patterns
If you're considering an integration layer approach:
Start with a high-value connection. Pick two systems where the manual data synchronization is painful. Connect those first. For many companies, this is supplier certificates + materials management.
Invest in the data model. The ontology is the foundation. Get it right. Involve domain experts who understand how data actually flows in your operations.
Plan for bi-directional sync. Most integrations need to write back to source systems, not just read. This is harder than read-only integration.
Design for failure. What happens when Veeva is down? Your integration layer needs graceful degradation, retry logic, and clear user feedback.
Think about audit trails early. Every action that touches GxP data needs to be logged. Design this into the architecture from day one.
When Consolidation Makes Sense
I'm not saying consolidation is never right. It makes sense when:
- You're starting greenfield (new company, new site)
- Your existing systems are truly obsolete (unsupported, security risks)
- A single vendor genuinely covers all your needs
- You have the budget, timeline, and organizational patience for a multi-year transformation
For most established pharmaceutical companies, these conditions don't apply. The integration layer approach is more pragmatic.
The Lesson
After years of building software for regulated industries, I've learned that the best solutions work with how organizations actually operate, not how consultants think they should operate.
Pharmaceutical companies have multiple specialized systems because that's what works. The integration layer approach acknowledges this reality and builds value on top of it.
At Cohera, we say: "We don't replace your existing systems. We create an intelligent layer that makes them work together."
That's not a compromise—it's a strategy.