Building a Scalable Integration Middleware Platform for a Growing Healthcare Ecosystem
A leading U.S.-based fertility EMR provider implemented a cloud-native Unified Services Layer to manage data exchange across its expanding partner ecosystem without adding equivalent engineering effort.
10+
Partner Systems Onboarded Through Configuration
80%
Reduction in Manual Integration Support Effort
95%
Automatic Recovery of Transient Delivery Failures
Introduction
A leading fertility EMR provider serving hundreds of clinics across North America had built individual integrations for patient engagement platforms, payment processors, genetics laboratories, digital consent tools, and other downstream systems.
That model worked when the partner ecosystem was small. As more integrations were introduced, however, each new connection added routing logic, authentication requirements, monitoring gaps, and maintenance work. Operations teams had limited visibility into whether data had reached the intended subscriber, while routine partner changes often required a software release.
Nalashaa designed and delivered the Unified Services Layer, or USL, as a central integration middleware platform for clinical data moving between the EMR and partner applications.
The platform identifies the correct subscribers for each event, applies partner-specific transformation and authentication rules, and dispatches data through managed workflows. New integrations can be configured through a BackOffice portal rather than coded into the core platform.
This shifted the client away from a growing collection of point-to-point connections and toward an integration model that could expand without creating the same increase in engineering effort, support demand, and operational risk.
The Unified Services Layer turns partner onboarding from a software development project into a configuration task, reducing integration timelines from weeks to days.
Business Challenge
The client's original integration model required a separate build for every downstream partner. Each connection had its own routing logic, authentication method, payload structure, and release process.
As the number of partners increased, four issues became increasingly difficult to manage.
-
Limited Delivery Visibility
Operations teams could not easily determine whether a clinical event had been delivered successfully to a partner application.
Confirming delivery often required database queries or developer assistance, making even routine investigations slow and dependent on technical teams.
-
Unreliable Failure Handling
Temporary API outages, timeouts, and other downstream issues had no consistent automated recovery process.
Failed deliveries could remain unnoticed until a partner or clinic reported missing data, increasing the time required to identify the affected transaction and determine what went wrong.
-
Engineering-Dependent Partner Changes
Adding a subscriber, updating authentication details, or modifying routing behavior generally required code changes and a software release.
This placed commercial onboarding behind engineering queues and made relatively small partner changes more disruptive than necessary.
-
Multi-Tenant Data Risk
The platform served hundreds of clinics, each with its own clinical data and subscriber relationships.
The client needed a reliable way to ensure that every event was routed only to the appropriate partner configuration while maintaining strict separation between clinic tenants.
The problem was no longer limited to integration development. The client needed a platform for operating, governing, and expanding the entire partner ecosystem.
Strategic Solution
Nalashaa developed the Unified Services Layer as a configurable middleware platform on Microsoft Azure.
Instead of embedding every partner connection into the EMR, the USL became the central point for subscriber resolution, transformation, authentication, delivery, monitoring, and recovery.
-
01
Centralized Integration Orchestration
All eligible clinical events pass through a common orchestration layer.
The platform determines which subscribers should receive each event, applies the relevant transformation rules, and dispatches the resulting payloads in parallel. This allows one source event to support multiple downstream workflows without duplicating integration logic inside the EMR.
Centralizing orchestration also gives the client one place to manage delivery behavior across the partner ecosystem.
-
02
Configuration-Driven Partner Onboarding
Nalashaa created a driver-based framework that separates partner behavior from application code.
Authentication methods, endpoint details, routing rules, subscriber mappings, and payload requirements can be maintained through database configuration and a BackOffice portal.
This allows many new partner connections and routine updates to be introduced without changing the core middleware code or waiting for a full engineering release.
-
03
End-to-End Transaction Visibility
Each clinical event generates a traceable transaction record as it moves through the USL.
The record captures the source event, tenant, subscriber selection, routing decisions, delivery attempts, acknowledgement status, and final outcome.
Operations teams can use the Transaction Monitor to investigate individual events in real time without querying production databases or relying on developers for routine checks.
-
04
Intelligent Fault Recovery
The platform includes automatic retry handling for temporary downstream failures such as API timeouts, service interruptions, and unavailable endpoints.
Acknowledgement tracking confirms whether a subscriber received the payload, while failed attempts are recorded against a structured error catalog.
This allows recoverable issues to be handled automatically and gives operations teams clearer information when manual intervention is required.
-
05
Multi-Tenant Security
Tenant isolation is enforced throughout subscriber resolution, routing, storage, and delivery.
Each clinic's data is processed according to its authorized partner configuration, preventing events from being exposed to an incorrect subscriber.
JWT, OAuth 2.0, API key controls, and AES-256 encryption protect data across different partner authentication and delivery models.
Key Capabilities Delivered
-
10+ Partner Systems
Onboarded via Configuration
-
80% Reduction
In Manual Integration Support Effort
-
100% Traceable
Full Transaction Audit Trail Across Subscriber Workflows
-
95% Auto-Recovery Success
For Transient Delivery Failures
Value Delivered
-
Accelerated Partner Onboarding
Reduced new partner onboarding timelines from multiple weeks to less than 3–5 days through configuration-driven integration workflows.
-
Operational Self-Sufficiency
Operations teams can trace, diagnose, and resolve integration issues independently through the Transaction Monitor. Reduced developer involvement in routine integration issue resolution by approximately 75%.
-
Zero-Loss Data Delivery
Improved downstream delivery reliability to greater than 99.9% through automated retry and acknowledgement handling.
-
Reduced Integration Cost
Reusable orchestration, authentication, and driver components reduce the amount of custom development required for each additional subscriber.
-
Ecosystem Scalability
The middleware can support additional partner systems without redesigning the core EMR or creating a new point-to-point architecture for every connection.
-
Governance & Compliance
Timestamped transaction records, payload histories, routing details, and acknowledgements provide a complete audit trail for clinical governance and compliance reviews.
Why Nalashaa
The value of the Unified Services Layer lies in the fact that it was not designed around one partner or one integration pattern.
The client's ecosystem included organizations with different authentication models, payload formats, acknowledgement mechanisms, and delivery expectations. Creating a reusable driver framework required a detailed understanding of both the EMR's clinical data model and the operational behavior of the systems receiving that data.
Nalashaa brought that context from an established platform engineering partnership with the client. The team understood how clinical events originated, how tenant and subscriber relationships were represented, and where integration failures could affect clinics and partner workflows.
That knowledge helped shape a middleware platform that could support diverse partner requirements without pushing their complexity back into the core EMR.
Conclusion
The client's point-to-point integration model had become difficult to scale because each new partner introduced more code, more monitoring gaps, and more operational dependency on engineering teams.
The Unified Services Layer replaced that model with a centralized platform for routing, transforming, securing, tracking, and recovering partner transactions.
New subscribers can now be onboarded through configuration, operations teams have a complete view of transaction activity, and temporary delivery failures can be resolved automatically in most cases.
As the partner network grows, the client can expand its healthcare ecosystem without allowing integration complexity and support effort to grow at the same rate.
Scale Your Partner Ecosystem Without Adding Integration Debt
Create a secure administration layer that simplifies clinic onboarding, improves transaction visibility, and reduces dependency on engineering teams.
Talk to a Healthcare Platform Engineering Expert