Summary and recommendation
MedBridge supports SCIM provisioning, but only for customers on their Organization/Enterprise tier with custom pricing. If you're on their Pro ($250-275/user/year) or Premium ($300-325/user/year) plans, you're locked out of automated provisioning entirely. Additionally, SCIM support is currently limited to Okta through their OIN integration - Microsoft Entra ID users have no native provisioning path.
For a 50-person healthcare team on Premium, upgrading to Organization just for SCIM access means negotiating custom enterprise pricing that could easily double or triple your annual spend - potentially $150,000+ in additional costs for features beyond provisioning that you may not need. Meanwhile, teams using Entra ID face manual user management regardless of their plan tier.
The strategic alternative
MedBridge gates SCIM behind Enterprise/Organization. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across the rest of your stack. Stitchflow builds and maintains the IT workflows your team still runs manually, across every app, including the ones without APIs.
Quick SCIM facts
| SCIM available? | Yes |
| SCIM tier required | Enterprise |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | ✓ | ✓ | OIN app with full provisioning |
| Microsoft Entra ID | ✓ | ❌ | SSO only |
| Google Workspace | ✓ | JIT only | SAML SSO with just-in-time provisioning |
| OneLogin | ✓ | ✓ | Supported |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages MedBridge accounts manually. Here's what that costs:
The MedBridge pricing problem
MedBridge gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Pro (Education) | $250-275/user/year | ||
| Premium | $300-325/user/year | ||
| Organization | Custom pricing |
Plan Structure
| Plan | Price | SCIM |
|---|---|---|
| Pro (Education) | $250-275/user/year | ❌ |
| Premium | $300-325/user/year | ❌ |
| Organization | Custom pricing | ✓ |
What this means in practice
Without published Organization pricing, healthcare IT teams face opaque enterprise sales cycles to access SCIM. The jump from Premium's known $300-325/user/year to custom Organization pricing typically represents substantial increases:
| Team Size | Premium Plan Cost | Organization Tier Impact |
|---|---|---|
| 50 clinical staff | $15,000-16,250/year | Likely 30-50% increase |
| 100 clinical staff | $30,000-32,500/year | Likely 30-50% increase |
| 200 clinical staff | $60,000-65,000/year | Likely 30-50% increase |
Additional constraints
Summary of challenges
- MedBridge supports SCIM but only at Enterprise tier (Custom (Organization))
- Google Workspace users get JIT provisioning only, not full SCIM
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What the upgrade actually includes
MedBridge doesn't sell SCIM à la carte. It's bundled with Organization/Enterprise features:
Note that SCIM is only available through Okta's integration - Microsoft Entra and Google Workspace administrators are left without native provisioning options.
Stitchflow Insight
If you need comprehensive healthcare learning management features anyway, the upgrade may make sense. If you just want automated user provisioning, you're paying for specialized clinical education tools you may not fully utilize. We estimate ~60% of Organization/Enterprise features are healthcare-specific and irrelevant for general IT provisioning needs.
What IT admins are saying
Community sentiment on MedBridge's SCIM availability is mixed, with frustrations centered on limited IdP support and enterprise-only requirements. Common complaints:
- SCIM only works with Okta - no support for Microsoft Entra or Google Workspace
- Enterprise/Organization plan required, forcing costly upgrades for basic provisioning
- Healthcare-specific pricing models that can reach $300+ per user annually
- Limited integration options compared to other learning platforms
We're primarily an Entra shop and MedBridge's Okta-only SCIM support means we're stuck with manual provisioning for our clinical staff.
The jump to Organization pricing just for automated user management doesn't make sense for smaller healthcare practices.
The recurring theme
MedBridge's SCIM implementation creates vendor lock-in with Okta while pricing out smaller healthcare organizations that need automated provisioning.
The decision
| Your Situation | Recommendation |
|---|---|
| On Pro/Premium plans, need SCIM | Use Stitchflow: avoid the expensive Organization tier upgrade |
| On Organization but SCIM not included | Use Stitchflow: skip the Enterprise upgrade negotiations |
| Already on Enterprise with SCIM | Use native SCIM: you're paying for it through Okta |
| Using non-Okta IdP (Entra, Google, OneLogin) | Use Stitchflow: MedBridge only supports SCIM via Okta OIN |
| Small clinical team, low turnover | Manual may work: but healthcare compliance demands audit trails |
The bottom line
MedBridge gates SCIM behind Enterprise/Organization. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the MedBridge workflow gap
MedBridge gates SCIM behind Enterprise/Organization, but the bigger issue is the workflow around it. Stitchflow builds and maintains the offboarding, access review, or license workflow underneath.
Technical specifications
SCIM Version
2.0
Supported Operations
Create, Update, Deactivate, Groups
Supported Attributes
Not specifiedPlan requirement
Enterprise
Prerequisites
None
Key limitations
- Healthcare-focused LMS for clinicians and organizations
- SCIM available via Okta OIN integration
- EMR integrations with Epic, Cerner, NextGen, Raintree, Casamba
- 1500+ organizations and 200k+ healthcare professionals use MedBridge
- Organization/Enterprise plan required for advanced features
Documentation not available.
Configuration for Okta
Integration type
Okta Integration Network (OIN) app with SCIM provisioning
Where to enable
Required credentials
SCIM endpoint URL and bearer token (generated in app admin console).
Configuration steps
Enable Create Users, Update User Attributes, and Deactivate Users.
Provisioning trigger
Okta provisions based on app assignments (users or groups).
Docs
Okta OIN integration supports SSO via SAML and SCIM provisioning. Listed as supporting entitlements, universal logout, and workflows.
MedBridge gates SCIM behind Enterprise/Organization. The upgrade may unlock provisioning, but the workflow still has to complete across the rest of your stack.
Close the workflow gap in
MedBridge
MedBridge gates SCIM behind Enterprise/Organization plan. That can unlock provisioning, but it still does not complete the offboarding, access review, or license workflow across your stack.
Start with the free gap diagnostic
