Salesforce and OMS had zero integration
Patient, Order, and clinical Note data lived only in the OMS. Salesforce was intended as the clinical CRM but had no data — making it unusable without manual data entry for every record.
A fast-moving telehealth company needed Salesforce to be the brain behind every patient order, prescription, and communication. Cloud Nerd delivered a bidirectional OMS integration, 23-table data migration, and 22 automated email flows — all in under six months.
Engagement at a glance
Discovery through production
Agile sprints delivered
From OMS via MuleSoft across 4 runs
Data tables migrated
Full order management lifecycle
Email automation flows
Phased as scope evolved with the business
SOWs executed
UpScript Health's Order Management System was the source of truth for patient data, prescriptions, and orders. Salesforce was the intended home for clinical CRM, service, and communications. But these two systems had never been connected. Every order update required manual reconciliation between systems. As UpScript scaled, this gap became a critical operational risk.
Cloud Nerd presented two integration architectural approaches and UpScript selected a full bidirectional sync — keeping both systems in real-time alignment. The team built a MuleSoft iPaaS middleware layer, developed APEX REST API services for each object type, built 22 Salesforce email automation flows, and executed a four-run data migration of 23 OMS tables.
Every update in the OMS now reflects in Salesforce within seconds, and vice versa. Clinicians and care coordinators work from a single Salesforce interface. Every patient lifecycle event triggers an automated, personalized email — zero manual intervention. All 23 historical data tables were migrated with zero data loss.
Patient, Order, and clinical Note data lived only in the OMS. Salesforce was intended as the clinical CRM but had no data — making it unusable without manual data entry for every record.
Every patient communication — order confirmation, prescription status, shipping updates — was sent manually by staff, creating delays, inconsistencies, and staffing overhead that didn't scale.
Years of patient records and order history existed only in the OMS. Moving it to Salesforce without disrupting live operations required a sophisticated multi-run migration strategy.
Before Salesforce could go live, UpScript needed a documented, reliable integration architecture. Without it, any future integrations would be built on an unstable foundation.
Cloud Nerd presented two integration approaches and UpScript selected full bidirectional sync. The MuleSoft middleware platform was set up, OAuth 2.0 Named Credentials configured, and APEX REST API framework built for Patient, Order, and Note objects.
Cloud Nerd completed Sprint 6 user stories, produced integration architecture diagrams for all three integration patterns, and configured Salesforce Service Cloud case management alongside a nightly batch reconciliation class.
The final phase delivered everything needed for production launch — all remaining integration development completed, 22 email automation flows built, and a four-run MuleSoft data migration of all 23 OMS data tables executed.
Bidirectional OMS ↔ Salesforce sync
Automated patient email flows — zero manual send
OMS data tables migrated with zero data loss
Automatic retry logic on every integration call
MuleSoft middleware ready for future integrations
What's next
With a reliable bidirectional integration and automated communication layer in place, UpScript Health has the platform foundation to scale patient volume, add new prescription products, and build Agentforce-powered care coordination workflows without re-architecting the integration layer.
Technologies in this engagement
Ready to do this?
Book a 30-minute strategy call. We'll walk through exactly what we'd do on your stack — no commitment, no pitch deck, just specifics.