Summary and recommendation
myAvatar, Netsmart's behavioral health EHR system, offers no SCIM provisioning capabilities on any plan. Despite being an enterprise-focused platform with custom pricing for mid-to-large behavioral health organizations, myAvatar lacks both native SCIM support and documented integrations with major identity providers like Okta or Microsoft Entra. This forces IT teams to manually manage user accounts across what is often a mission-critical system handling sensitive patient data and clinical workflows.
This creates a significant operational burden for healthcare IT teams who must manually provision, update, and deprovision user accounts in myAvatar while maintaining compliance with HIPAA and other healthcare regulations. Without automated provisioning, organizations face increased security risks from delayed deprovisioning of terminated staff who retain access to sensitive patient records, along with the administrative overhead of coordinating user lifecycle management across clinical and IT teams.
The strategic alternative
myAvatar has no native SCIM. That leaves a workflow gap in offboarding, access reviews, and license cleanup unless your team handles the app another way. 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? | No |
| SCIM tier required | N/A |
| SSO required first? | No |
| SSO available? | Yes |
| SSO protocol | SAML 2.0 |
| Documentation | Not available |
Supported identity providers
| IdP | SSO | SCIM | Notes |
|---|---|---|---|
| Okta | Via third-party | ❌ | No Okta OIN integration found for Netsmart myAvatar |
| Microsoft Entra ID | Via third-party | ❌ | No Microsoft Entra integration documentation found |
| Google Workspace | Via third-party | ❌ | No native support |
| OneLogin | Via third-party | ❌ | No native support |
The cost of not automating
Without SCIM (or an alternative like Stitchflow), your IT team manages myAvatar accounts manually. Here's what that costs:
The myAvatar pricing problem
myAvatar gates SCIM provisioning behind premium plans, forcing significant cost increases for basic user management.
Tier comparison
| Plan | Price | SSO | SCIM |
|---|---|---|---|
| Enterprise | Custom quote |
Pricing structure
| Plan | Price | SCIM |
|---|---|---|
| Enterprise | Custom quote | ❌ Not available |
Market reality for myAvatar
What this means in practice
Without native SCIM support, myAvatar user management relies entirely on manual processes:
For a 200-user behavioral health organization, this typically means 2-3 hours weekly of manual user administration work.
Additional constraints
Summary of challenges
- myAvatar does not provide native SCIM at any price tier
- Organizations must rely on third-party tools or manual provisioning
- Our research shows teams manually provisioning this app spend significant hidden costs annually
What myAvatar actually offers for identity
No native identity management features
Based on available documentation, Netsmart myAvatar does not offer:
Enterprise deployment model
myAvatar operates on a custom Enterprise pricing model designed for mid-to-large behavioral health organizations:
| Feature | Details |
|---|---|
| Deployment options | On-premise or cloud-based |
| Pricing | Custom quotes only |
| Target market | Healthcare organizations with 100+ users |
| Compliance focus | HIPAA, behavioral health regulations |
The reality: myAvatar's Enterprise model assumes IT teams will handle identity management through manual processes or external systems. There's no built-in automation for user lifecycle management.
What this means for IT teams
Without native identity features, myAvatar administrators must:
This manual approach creates significant operational overhead and compliance risks in healthcare environments where user access must be tightly controlled and auditable.
What IT admins are saying
myAvatar's lack of automated provisioning creates significant operational overhead for healthcare IT teams managing user lifecycles:
- Manual user creation required for every new clinician, even with SSO
- No centralized user management across multiple behavioral health facilities
- Time-intensive onboarding process for clinical staff who need immediate system access
- Compliance audit challenges when tracking user access changes manually
The recurring theme
Healthcare organizations using myAvatar face the double burden of manual user management combined with strict HIPAA compliance requirements. When clinical staff turnover is high, IT teams spend excessive time on routine provisioning tasks that should be automated, taking focus away from critical healthcare technology initiatives.
The decision
| Your Situation | Recommendation |
|---|---|
| Small behavioral health practice (<20 users) | Manual management acceptable with infrequent staff changes |
| Mid-size organization with stable clinical staff | Manual management with focus on HIPAA compliance documentation |
| Large healthcare system (100+ users) | Use Stitchflow: automation essential for compliance and efficiency |
| Multi-location behavioral health network | Use Stitchflow: centralized provisioning critical for operational consistency |
| Enterprise with strict audit requirements | Use Stitchflow: automated audit trail essential for healthcare compliance |
The bottom line
myAvatar has no native SCIM. That means one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Close the myAvatar workflow gap
myAvatar is one gap in a broader workflow. Stitchflow builds and maintains the offboarding, access review, or license workflow across every app in your environment.
Technical specifications
SCIM Version
Not specifiedSupported Operations
Not specifiedSupported Attributes
Plan requirement
Not specifiedPrerequisites
Not specifiedKey limitations
- No public SCIM documentation available
- Enterprise-focused customized pricing
- Designed for mid-to-large behavioral health organizations
- Available as on-premise or cloud-based deployment
- Healthcare-specific compliance requirements (HIPAA)
Documentation not available.
Close the workflow gap in
myAvatar
myAvatar has no native SCIM. That leaves one more workflow gap in offboarding, access reviews, and license cleanup unless your team handles it another way.
Start with the free gap diagnostic

