How Meridian Health bridged Slack and Teams in 48 hours post-merger

The challenge

Meridian Health's acquisition closed on a Friday. By Monday morning, 1,200 engineers needed to coordinate with 800 clinical operations staff — engineers on Slack, clinicians on Teams. The standard options were unacceptable: a full Slack-to-Teams migration would take 6–9 months and disrupt clinical workflows during a critical integration period. Slack Connect and Teams Connect both require the other side to operate within the same platform ecosystem.

The requirement from the CISO was clear: any solution needed a HIPAA Business Associate Agreement before a single patient-related message could cross the bridge.

Why SyncRivo

The IT team evaluated Mio and NextPlane alongside SyncRivo. Mio did not offer a HIPAA BAA. NextPlane required a custom federation deployment that the team estimated would take 4–6 weeks to implement. SyncRivo was the only vendor that offered both a self-serve setup path and an enterprise HIPAA BAA on a short timeline.

The evaluation criteria were straightforward:

• HIPAA BAA available before go-live
• No message storage on third-party infrastructure (zero data-at-rest)
• Sub-100ms delivery for incident coordination messages
• No guest accounts or cross-tenant trust agreements required
• IT-managed without requiring end-user training

SyncRivo met all five criteria.

The deployment

The Meridian IT team provisioned SyncRivo on a Thursday evening. OAuth authorization for both the Slack workspace and the Teams tenant was completed in under 30 minutes. Channel mappings for 14 cross-functional channels — including #incident-response, #clinical-ops, and #platform-engineering — were configured before midnight.

By Friday at 8:00 AM, both organizations were sending and receiving messages in their native platform. No end-user training was required. Engineers saw Teams users in Slack with their real names and job titles. Clinicians saw Slack messages appear in Teams with full sender context.

The HIPAA BAA was executed in parallel with the technical deployment. SyncRivo's legal team turned around the BAA within 48 hours of the initial request. InfoSec closed the security review before Day 1.

"We completed a merger between a Slack-heavy engineering org and a Teams-first clinical org. SyncRivo had both sides messaging each other within 48 hours — zero migrations, zero guest accounts, zero resistance."

Daniel R.

VP of IT Infrastructure, Meridian Health

Compliance and security architecture

Meridian's InfoSec team reviewed SyncRivo's SOC 2 Type II report and architecture documentation. Key controls confirmed during the review:

• Zero data-at-rest: SyncRivo routes messages in memory and does not persist message content to disk or database storage.
• TLS 1.3 encryption in transit: All webhooks and API calls use TLS 1.3 with certificate pinning.
• Per-tenant credential isolation: Meridian's OAuth tokens are stored in an isolated secrets vault. No cross-tenant access is architecturally possible.
• Audit logging: All routing events, configuration changes, and authentication events are logged to an immutable audit trail.
• HIPAA BAA: Executed covering all message routing activities involving patient-identifiable contexts.

Results

Sixty days after deployment, Meridian's integration team reported:

• Zero incidents attributed to cross-platform message loss
• Engineering and clinical teams coordinating in real time without platform switching
• Incident response times improved due to P1 alerts reaching both Slack and Teams simultaneously
• No HIPAA compliance findings in the post-merger IT audit