Healthcare · Salesforce + OMS Bidirectional Integration
UpScript HealthUpScript Health
×
Cloud Nerd

From Startup to Scale: Building UpScript Health's Salesforce Command Center in 12 Sprints

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

Industry
Healthcare
Duration
6 months
Services
Strategy & Roadmap · Architecture & Design · Build & Implement · Integrations · Migration & Modernization
Stack
Salesforce Sales CloudSalesforce Sales CloudSalesforce Service CloudSalesforce Service CloudMuleSoftMuleSoft

Discovery through production

12

Agile sprints delivered

From OMS via MuleSoft across 4 runs

23

Data tables migrated

Full order management lifecycle

22

Email automation flows

Phased as scope evolved with the business

4+

SOWs executed

The challenge

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.

The approach

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.

The outcome

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.

The problem

What was actually broken

01

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.

02

Order lifecycle had no automated communications

Every patient communication — order confirmation, prescription status, shipping updates — was sent manually by staff, creating delays, inconsistencies, and staffing overhead that didn't scale.

03

Historical data locked in OMS

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.

04

No middleware architecture defined

Before Salesforce could go live, UpScript needed a documented, reliable integration architecture. Without it, any future integrations would be built on an unstable foundation.

How we did it

The work, phase by phase

  1. 01
    Sprints 1–5

    Architecture Decision & 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.

    • Integration architecture decision document (Approach One vs. Two)
    • MuleSoft iPaaS middleware setup
    • OAuth 2.0 Named Credentials and Auth Provider in Salesforce
    • APEX REST API framework for Patient, Order, and Note objects
    • Sprint backlog with all Phase One MVP user stories
  2. 02
    Sprints 5–7

    Integration Build & Service Cloud

    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.

    • Integration architecture diagrams (synchronous, asynchronous, full-table sync patterns)
    • Email platform architectural decision document (SendGrid vs. Salesforce native)
    • Nightly batch reconciliation class for data consistency
    • Salesforce Service Cloud case management configuration
    • Complete discovery and design for all remaining Phase One MVP stories
  3. 03
    Sprints 8–12

    MVP Completion, Data Migration & Email Automation

    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 Salesforce ↔ OMS integration across all scoped objects
    • 22 Salesforce email automation flows with native templates
    • 4-run MuleSoft data migration of 23 data tables (Patient, Order, Note)
    • 50 hours of post-migration data validation
    • Error handling with 3-attempt retry logic and event log table
    • Production go-live and hypercare support
The results

What changed for UpScript Health

Real-time

Bidirectional OMS ↔ Salesforce sync

22

Automated patient email flows — zero manual send

23

OMS data tables migrated with zero data loss

Automatic retry logic on every integration call

Extensible

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

Salesforce Sales CloudSalesforce Sales Cloud
Salesforce Service CloudSalesforce Service Cloud
MuleSoftMuleSoft

Ready to do this?

What would we build
at your company?

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.

Book a Strategy Call