Supergood | Core Solutions API
Programmatically access intake, client records, scheduling, clinical documentation, authorization tracking, and revenue cycle workflows in Core Solutions’ Cx360 with a stable REST API. Supergood builds and operates production-grade, unofficial Core Solutions integrations so your team can automate critical behavioral health operations without heavy custom engineering.
Core Solutions (Cx360) is an EHR platform used by behavioral health and human services organizations—including community mental health centers (CMHCs), CCBHCs, IDD/long-term services and supports, and substance use treatment programs—to manage intake, assessments, treatment plans, progress notes/encounters, scheduling, authorizations, and billing. With an unofficial API, you could synchronize client and staff rosters, manage appointments, submit encounters linked to treatment plans and payer authorizations, assemble claims, and pull outcomes data for reporting.
If you’re a behavioral health agency, CCBHC, county program, or integrated care network, integrating your tech stack with Core Solutions unlocks concrete data flows and features:
- Pull: Client demographics and program enrollments, schedules and appointments, treatment plans and goals, standardized assessments (e.g., PHQ‑9, CANS), authorizations with units remaining, encounter/clinical note exports, claim statuses and remittance summaries
- Push: Referrals and new clients from your CRM, appointments and telehealth session links, encounter/progress notes (with service codes and diagnoses), treatment plan updates, claim submissions referencing validated encounters
- Build: Authorization-aware scheduling, automated documentation from virtual care platforms, outcomes dashboards fed by assessment scores, revenue cycle flows that validate encounters before claim assembly
What is Core Solutions?
Core Solutions provides Cx360, a behavioral health and human services EHR that supports end-to-end clinical and administrative workflows for mental health, substance use disorder, and IDD providers. Typical modules include intake and eligibility, scheduling, assessments and treatment planning, clinical documentation (progress notes/encounters), care coordination, outcomes measurement, payer/authorization management, and billing (837/835) with remittance reconciliation. Many agencies also leverage client and caregiver/staff portals and integrations with ePrescribing and HIEs.
Core product areas include:
- Intake, referrals, and program enrollments/episodes
- Scheduling and appointment management (in-person and telehealth)
- Clinical documentation: assessments, treatment plans, progress notes/encounters
- Authorization tracking (payer, service code, units/dates)
- Outcomes and quality reporting (e.g., CCBHC measures)
- Billing and remittances (837/835) and payer/reimbursement reporting
- Consent and privacy controls (including 42 CFR Part 2 segmentation)
Common data entities:
- Clients/Patients and guardians/contacts
- Staff/Providers and service locations
- Programs/Enrollments/Episodes of care
- Appointments and schedules
- Treatment plans, goals, interventions
- Assessments (e.g., PHQ‑9, GAD‑7, CANS) and outcomes
- Encounters/Progress notes (service codes, diagnoses, time, units)
- Authorizations (payer, service code, limits, dates)
- Claims (837P/I) and remittances (835)
- Consents and 42 CFR Part 2 segmentation flags
The Core Solutions Integration Challenge
Organizations rely on Cx360 daily, but turning portal-based workflows and batch interfaces into automated pipelines is hard:
- Limited public APIs: Many agencies report relying on scheduled reports, CSV/flat-file exports, or custom projects for integrations rather than real-time endpoints
- Strong enterprise security: SSO/MFA, IP allowlists, and role-based access can complicate headless automation
- Consent segmentation: 42 CFR Part 2 and organizational consent policies require fine-grained access, filtering, and audit trails
- Portal-first workflows: Clinical note signing, plan approvals, and authorization updates often live in web apps or queues, not unified APIs
- Batch billing: 837/835 flows commonly run through SFTP/clearinghouse or payer portals with timing windows and status polling
- Custom forms: Agency-specific documentation templates can be hard to extract without normalized schemas
How Supergood Creates Core Solutions APIs
Supergood reverse-engineers authenticated browser flows, batch interfaces, and network interactions in Cx360 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, appointment, authorization, and encounter objects across deployments
- Enforces consent-aware filtering and 42 CFR Part 2 segmentation; aligns with customer entitlements and licensing
- Bridges batch exports and SFTP/EDI flows where applicable with signed URL retrieval and delivery
Use Cases
EHR/CRM-to-Cx360 Synchronization
- Push referrals and client demographics from your CRM/Intake tools into Cx360
- Keep payer, contact, and program enrollment data in sync across systems
- Maintain a single source of truth for demographics and eligibility
Authorization-Aware Scheduling and Eligibility
- Validate authorizations and remaining units before appointment creation
- Prevent over-utilization with real-time unit checks
- Surface payer/program-specific rules to schedulers and care coordinators
Clinical Documentation Automation
- Create encounters/progress notes from virtual care or mobile apps with correct service codes and diagnoses
- Attach assessment scores and plan goal IDs to notes; respect signing workflows
- Capture telehealth indicators and location-of-service metadata
Revenue Cycle and Claim Preparation
- Validate encounters against authorizations and signed plans prior to billing
- Bundle validated encounters into 837P/I claim files via configured channels
- Retrieve payer responses and remittances for reconciliation
Outcomes and Quality Reporting
- Pull assessment results and calculate standardized measure trends
- Feed dashboards for CCBHC reporting, grant metrics, and quality improvement
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_9fcb31",
"name": "BH Admin",
"entitlements": ["clients", "scheduling", "authorizations", "encounters"]
}
}
Clients
GET /clients: Retrieve clients with demographics, program enrollments, payer coverages, and consent flags (including Part 2 segmentation where applicable). Use filters to scope by program, activity, and update time.
Query parameters
- search: string (name/MRN)
- programId: string
- updatedSince: ISO 8601 timestamp
- activeOnly: boolean
- consentScope: string (e.g., "treatment", "payment", "operations")
Example response
{
"items": [
{
"clientId": "cli_42a7df",
"mrn": "A102938",
"externalIds": {"crm": "crm_2291"},
"firstName": "Ava",
"lastName": "Nguyen",
"dob": "1990-04-14",
"gender": "female",
"contact": {"phone": "+1-312-555-0123", "email": "[email protected]"},
"addresses": [{"line1": "12 Oak St", "city": "Chicago", "region": "IL", "postalCode": "60612"}],
"programEnrollments": [
{"programId": "prog_cmhs", "name": "Community Mental Health", "status": "active", "startDate": "2025-08-01"}
],
"payers": [
{"payerId": "payer_il-medicaid", "plan": "Managed Medicaid", "memberId": "IL1234567"}
],
"consent": {
"part2": true,
"consentIds": ["cons_77aa"],
"restrictions": ["substance_use", "psychotherapy_notes"]
},
"updatedAt": "2026-01-18T22:41:07Z"
}
],
"page": 1,
"pageSize": 50,
"total": 1
}
Authorizations
GET /authorizations: Retrieve payer/member service authorizations with allowed units, covered service codes, and date ranges. Use this to validate scheduling and encounter eligibility.
Query parameters
- clientId: string
- payerId: string
- serviceCode: string (CPT/HCPCS)
- activeOn: ISO 8601 date
- programId: string
Example response
{
"items": [
{
"authorizationId": "auth_5b139d",
"authorizationNumber": "BH-2026-00492",
"clientId": "cli_42a7df",
"clientName": "Ava Nguyen",
"payerId": "payer_il-medicaid",
"program": "CMHC",
"serviceCode": "90837",
"modifiers": ["GT"],
"unitsAuthorized": 24,
"unitsRemaining": 18,
"startDate": "2026-01-01",
"endDate": "2026-06-30",
"status": "active"
}
],
"page": 1,
"pageSize": 50,
"total": 1
}
Encounters
POST /encounters: Create or update an encounter/progress note with service details, diagnoses, and verification/signature metadata. Supports consent-aware submission and authorization checks.
curl --request POST \
--url https://api.supergood.ai/integrations/<integration_id>/encounters \
--header 'Authorization: Bearer <authToken>' \
--header 'Content-Type: application/json' \
--data '{
"clientId": "cli_42a7df",
"providerId": "prv_119c0b",
"locationId": "loc_outpatient-chi",
"programId": "prog_cmhs",
"serviceDate": "2026-01-19",
"timeIn": "2026-01-19T14:00:00Z",
"timeOut": "2026-01-19T14:53:00Z",
"telehealth": true,
"serviceCode": "90837",
"modifiers": ["GT"],
"diagnosisCodes": ["F33.1"],
"authorizationId": "auth_5b139d",
"units": 1,
"treatmentPlanGoalIds": ["goal_1002"],
"notes": "Focused on CBT techniques; client reports improved sleep.",
"signatures": {
"clinicianSigned": true,
"clinicianSignedAt": "2026-01-19T15:05:12Z"
},
"part2Sensitive": true,
"consentId": "cons_77aa",
"referenceId": "telehealth-session-9876"
}'
Example response
{
"encounterId": "enc_8a21f7",
"status": "validated",
"authorization": {"consumedUnits": 1, "unitsRemaining": 17},
"warnings": [],
"createdAt": "2026-01-19T15:06:01Z",
"referenceId": "telehealth-session-9876"
}
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, appointments, and encounter artifacts
- Security: Encrypted transport, scoped tokens, consent-aware filtering; respects Core Solutions entitlements and 42 CFR Part 2/HIPAA requirements
- Webhooks: Optional asynchronous delivery for appointment updates, encounter validation, claim generation, and remittance updates
Performance Characteristics
- Latency: Sub-second responses for list/detail queries under normal load
- Throughput: Designed for high-volume clinical documentation and batch billing 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 Core Solutions product mix (Cx360 modules), licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened Core Solutions adapter tailored to your workflows, consent requirements, and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Cx360 evolves.
Frequently Asked Questions
Q: Which Core Solutions products can this integration cover?
Supergood supports workflows across commonly used Cx360 modules—clients, scheduling, authorizations, clinical documentation, and billing—subject to your licensing and entitlements. We scope coverage (e.g., assessments, treatment plans, encounter exports, claim assembly) during integration assessment.
Q: How are MFA, SSO, and consent segmentation handled for automation?
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth where enabled. We enforce consent-aware filtering and 42 CFR Part 2 segmentation so only data within consent scope is accessible, with full audit trails.
Q: Can I post clinical notes/encounters directly into Cx360?
Yes. You can create encounters with service codes, diagnoses, time, and signatures. We validate against authorizations and treatment plan alignment and respect signing workflows and consent controls.
Q: Can I generate claims from validated encounters?
Yes. We can assemble 837P/I from validated encounters and route via your configured submission channel (clearinghouse, payer portal, or SFTP) and return statuses and artifacts for reconciliation.
Q: We’ve struggled to extract custom forms—can Supergood help?
Commonly reported pain points include limited real-time APIs and custom form data living in complex schemas or reports. We normalize key fields and expose machine-readable JSON for high-value forms and assessments while honoring consent and role-based access.
Related Integrations
- Netsmart myAvatar API - Programmatically access myAvatar with Supergood
Ready to automate your Core Solutions workflows?
Supergood can have your Core Solutions integration live in days with no ongoing engineering maintenance.
