Supergood | Netsmart API
Netsmart is healthcare software used by behavioral health, human services, and post-acute care organizations to document care, manage treatment plans, schedule services, bill payers, and coordinate across programs. An unofficial API would let you programmatically read and write core EHR records like clients, authorizations, treatment documentation, and claims artifacts instead of relying on manual exports or portal clicks.
If you’re another tech company—like a telehealth vendor, care management platform, CRM, or RCM service—integrating with Netsmart means you could pull client demographics, diagnoses, episodes of care, appointments, and authorizations; push scheduled visits and completed notes; update treatment plan goals; and generate billing lines or claims. This unlocks features such as authorization-aware scheduling, automated documentation workflows, outcomes tracking, and revenue cycle automation across behavioral health and post-acute teams.
Programmatically access behavioral health EHR data, treatment plans, service documentation, payer authorizations, and reimbursement workflows in Netsmart with a stable REST API. Supergood builds and operates production-grade, unofficial Netsmart integrations so your team can automate critical clinical and billing pipelines without heavy custom engineering.
Netsmart is software used by community mental health centers, Certified Community Behavioral Health Clinics (CCBHCs), human services agencies, and post-acute providers to manage client records, plan and document services, coordinate care, and bill Medicaid and Managed Care Organizations (MCOs). With an unofficial API, you could synchronize clients and program enrollments from your systems, validate authorizations, create billable service events with compliant documentation, and reconcile claims and remittances—end to end.
If you’re a clinic, provider group, or revenue cycle team, integrating your tech stack with Netsmart unlocks concrete data flows and features:
- Pull: Client/consumer profiles, program enrollments and episodes, diagnoses, payer coverages, authorizations, schedules and service events, treatment plans, claim statuses, remittance summaries, outcomes/assessment scores
- Push: New/updated clients from your CRM/EHR, scheduled appointments/visits, completed service documentation (progress notes), treatment plan goals and updates, compliant signatures and addenda, charge lines or claim submissions
- Build: Authorization-aware scheduling, documentation assistants and QA, CCBHC reporting pipelines, automatic claim assembly (837P/I) from approved services, reconciliation dashboards driven by encounters and 835 remits
What is Netsmart?
Netsmart provides electronic health record (EHR) and care coordination platforms for behavioral health, human services, and post-acute care. The portfolio includes solutions such as myAvatar (behavioral health EHR), myEvolv (human services), and myUnity (post-acute), along with interoperability (CareConnect), ePrescribing, analytics, and revenue cycle services. Organizations use Netsmart to track clients across programs, manage treatment plans and assessments, document services and progress notes, handle referrals and care transitions, and connect documentation to billing and reimbursement.
Core product areas include:
- Client/consumer EHR for behavioral health and human services
- Post-acute EHR for home health, hospice, and senior living
- Scheduling, service documentation, and progress notes
- Treatment planning with goals, objectives, and interventions
- Payer management, prior authorizations, and eligibility
- Claims and remittance management (837/835)
- Interoperability (HIE, HL7/FHIR) and ePrescribing
- Patient engagement, telehealth, and portals
Common data entities:
- Clients/Consumers (patients)
- Staff/Clinicians and provider credentials
- Programs/Service lines and Episodes of Care (enrollments)
- Appointments/Schedules
- Service Events/Encounters (progress notes, CPT/HCPCS)
- Diagnoses (ICD-10/DSM-5), problem lists
- Treatment Plans (goals, objectives, interventions)
- Authorizations (payer, service code, units, dates)
- Payers/Plans and coverage
- Referrals and care transitions
- Assessments and outcomes (e.g., PHQ-9, CANS)
- Claims and Remittances
- Consents/Release of Information (ROI), 42 CFR Part 2 segmentation
The Netsmart Integration Challenge
Organizations rely on Netsmart daily, but turning portal-based EHR workflows into automated pipelines is hard:
- Multiple product lines and configurations: myAvatar, myEvolv, and myUnity differ by data model and permissions
- Strong enterprise security: SSO/MFA, IP controls, and environment-specific sign-in flows complicate headless automation
- Portal-first delivery: Clinical documentation, approvals, and batch exports often live behind web UIs without unified public APIs
- Hybrid standards landscape: HL7/FHIR, EDI 837/835, and SFTP/CSV batch feeds must be bridged and timed correctly
- Compliance nuances: Behavioral health privacy, 42 CFR Part 2 consent segmentation, and audit trails demand precise handling
- Payer complexity: Varying Medicaid/MCO service codes, modifiers, and billing rules across geographies and programs
How Supergood Creates Netsmart APIs
Supergood reverse-engineers authenticated browser flows, batch interfaces, and network interactions to deliver a resilient API endpoint layer.
- Handles username/password, SSO/OAuth, and MFA (SMS, email, TOTP) securely
- Maintains session continuity with automated refresh and change detection
- Normalizes client, authorization, and encounter objects across Netsmart product lines
- Aligns with customer entitlements and licensing constraints to ensure compliant access
- Bridges batch exports and SFTP/EDI flows where applicable with signed URL retrieval and delivery
- Applies consent/ROI rules and 42 CFR Part 2 segmentation to filter or mask restricted data
Use Cases
Data Synchronization Between Systems
- Push client rosters from your CRM/EHR into Netsmart and keep demographics, diagnoses, and coverage in sync
- Create appointments from your scheduling system and tie them to programs and authorizations
- Maintain a single source of truth for staff/clinician assignments and credentials
Authorization-Aware Scheduling and Eligibility
- Validate member coverage and authorizations before scheduling or service creation
- Track remaining authorized units to prevent over-utilization
- Surface payer- and program-specific rules to care coordinators
Documentation and QA Automation
- Generate service events with the correct codes/modifiers and capture required note fields
- Enforce documentation completeness checks and route approvals to supervisors
- Apply compliant reason codes on edits, preserving audit trails
Claims Generation and Reimbursement Automation
- Bundle approved services into 837P/I claims with payer-specific formatting
- Submit via configured channels (state portals, MCO gateways, or clearinghouses)
- Track claim statuses and reconcile remittances alongside encounter data
Audit and Compliance
- Export complete encounter packets with timestamps, signatures, and approval history
- Maintain machine-readable audit trails tailored to behavioral health privacy requirements
- Respect consents and 42 CFR Part 2 restrictions across all data pulls
Available Endpoints
Authentication
POST /sessions: Establish a session using credentials. Supergood manages MFA (SMS, email, TOTP) and SSO/OAuth when enabled. Returns a short-lived auth token maintained by the platform.
curl --request POST \
--url https://api.supergood.ai/integrations/<integration_id>/sessions \
--header 'Authorization: Basic <Base64 encoded token>' \
--header 'Content-Type: application/json' \
--data '{
"username": "[email protected]",
"password": "<password>",
"mfa": {
"type": "totp",
"code": "123456"
}
}'
Example response
{
"authToken": "eyJhbGciOi...",
"expiresIn": 3600,
"user": {
"id": "u_4c19fe",
"name": "EHR Admin",
"entitlements": ["clients", "authorizations", "encounters"]
}
}
Clients
GET /clients: Retrieve client/consumer records with program enrollments, diagnoses, and coverage so you can synchronize rosters and eligibility.
Query parameters
- programId: string
- updatedSince: ISO 8601 datetime
- mrn: string
- dateOfBirth: YYYY-MM-DD
- lastName: string
- active: boolean
Example response
{
"items": [
{
"clientId": "clt_a9213f",
"mrn": "MRN-104392",
"firstName": "Avery",
"lastName": "Nguyen",
"dateOfBirth": "1991-07-12",
"sex": "F",
"contact": {
"phone": "+1-555-0142",
"email": "[email protected]"
},
"addresses": [
{"type": "home", "line1": "42 Pine St", "city": "Rochester", "region": "NY", "postalCode": "14604"}
],
"primaryDiagnosis": {"code": "F32.1", "description": "Major depressive disorder, moderate"},
"programEnrollments": [
{"programId": "prog_bh_outpatient", "episodeId": "ep_7aa82d", "startDate": "2025-10-01", "endDate": null, "status": "active"}
],
"payerCoverages": [
{"payerId": "payer_empire-mco", "memberId": "M1234567", "plan": "Medicaid Managed Care", "startDate": "2025-01-01", "endDate": null}
],
"consents": [
{"type": "42cfr_part2", "status": "granted", "effectiveDate": "2025-10-01"}
],
"primaryProvider": {"staffId": "stf_11fd9a", "name": "Jordan Patel, LCSW"}
}
],
"page": 1,
"pageSize": 50,
"total": 1
}
Authorizations
GET /authorizations: Retrieve payer/member service authorizations with allowed units, service codes, and date ranges. Use this to validate scheduling and billable services.
Query parameters
- clientId: string
- payerId: string
- serviceCode: string (CPT/HCPCS)
- activeOn: ISO 8601 date
- programId: string
Example response
{
"items": [
{
"authorizationId": "auth_8c42a9",
"authorizationNumber": "AUTH-2026-11872",
"clientId": "clt_a9213f",
"payerId": "payer_empire-mco",
"programId": "prog_bh_outpatient",
"serviceCode": "90834",
"modifiers": ["GT"],
"unitsAuthorized": 24,
"unitsUsed": 6,
"unitsRemaining": 18,
"startDate": "2026-01-01",
"endDate": "2026-06-30",
"status": "active",
"diagnosisCodes": ["F32.1"]
}
],
"page": 1,
"pageSize": 50,
"total": 1
}
Service Events
POST /service-events: Create a billable encounter/progress note with documentation and signatures. Supports compliance checks, approvals, and linkage to authorizations.
curl --request POST \
--url https://api.supergood.ai/integrations/<integration_id>/service-events \
--header 'Authorization: Bearer <authToken>' \
--header 'Content-Type: application/json' \
--data '{
"clientId": "clt_a9213f",
"staffId": "stf_11fd9a",
"programId": "prog_bh_outpatient",
"authorizationId": "auth_8c42a9",
"serviceCode": "90834",
"modifiers": ["GT"],
"startTimestamp": "2026-01-19T14:00:00Z",
"endTimestamp": "2026-01-19T14:50:00Z",
"placeOfService": "02",
"locationOfService": "telehealth",
"diagnosisCodes": ["F32.1"],
"documentation": {
"noteText": "Reviewed mood symptoms, engaged in CBT techniques, assigned homework.",
"formId": "form_progress_note_v3",
"answers": {
"mse_affect": "congruent",
"safety_screen": "negative"
}
},
"signatures": {
"clinician": {"method": "certify", "timestamp": "2026-01-19T15:00:10Z"},
"client": {"method": "on_file", "timestamp": "2026-01-19T15:00:11Z"}
},
"referenceId": "telehealth-visit-48320"
}'
Example response
{
"eventId": "evt_59d3f0",
"status": "pending_approval",
"billable": true,
"compliance": {"complete": true, "missingFields": []},
"createdAt": "2026-01-19T15:01:02Z",
"referenceId": "telehealth-visit-48320"
}
Technical Specifications
- Authentication: Username/password with MFA (SMS, email, TOTP) and SSO/OAuth where enabled; supports service accounts or customer-managed credentials
- Response format: JSON with consistent resource schemas and pagination
- Rate limits: Tuned for enterprise throughput while honoring licensing and usage controls
- Session management: Automatic reauth and cookie/session rotation with health checks
- Data freshness: Near real-time retrieval of clients, authorizations, and encounter artifacts
- Security: Encrypted transport, scoped tokens, and audit logging; respects Netsmart entitlements and compliance requirements
- Webhooks: Optional asynchronous delivery for documentation approvals, claim generation, and remittance updates
Performance Characteristics
- Latency: Sub-second responses for list/detail queries under normal load
- Throughput: Designed for high-volume encounter ingestion and batch claims pipelines
- Reliability: Retry logic, backoff, and idempotency keys minimize duplicate actions
- Adaptation: Continuous monitoring for UI/API changes with rapid adapter updates
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Netsmart product mix, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened Netsmart adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Netsmart evolves.
Frequently Asked Questions
Q: Which Netsmart products can this integration cover?
Supergood supports workflows across commonly used Netsmart applications and modules—such as myAvatar (behavioral health), myEvolv (human services), myUnity (post-acute), and related RCM/interoperability components—subject to your licensing and entitlements. We finalize scope (e.g., authorizations, encounters, treatment documentation, claim assembly) during integration assessment.
Q: How do you handle 42 CFR Part 2 and client consents?
We apply consent and ROI metadata at query time, filtering or masking restricted records and fields to respect behavioral health privacy and 42 CFR Part 2 segmentation. All edits and reads are audited with timestamps and user context.
Q: Can I generate claims directly from approved service events?
Yes. We can assemble 837P/I from approved encounters with payer-specific formatting, route submissions via your configured channel (state/MCO portals or clearinghouse), and return statuses and EDI/835 artifacts for reconciliation.
Related Integrations
Intralinks API - Programmatically access the Intralinks VDR with Supergood
Ready to automate your Netsmart workflows?
Supergood can have your Netsmart integration live in days with no ongoing engineering maintenance.