CareLogic By Qualifacts

Supergood | CareLogic by Qualifacts API

Alex Klarfeld

Alex Klarfeld

— 7 min read
Supergood | CareLogic by Qualifacts API

Programmatically access client rosters, scheduling, clinical documentation, payer authorizations, and behavioral health billing workflows in CareLogic by Qualifacts with a stable REST API. Supergood builds and operates production-grade, unofficial CareLogic integrations so your team can automate core EHR and revenue cycle processes without heavy custom engineering.

CareLogic is an EHR used by behavioral health and human services agencies to manage intake and episodes of care, document services, track treatment plans and outcomes, schedule individual and group sessions, and support billing to Medicaid, commercial payers, and Managed Care Organizations (MCOs). With an unofficial API, you could synchronize client and provider rosters, create appointments, validate authorizations, capture billable service events tied to diagnoses and programs, assemble claims, and reconcile remittances—end to end.

If you’re a clinic, provider group, or revenue cycle team, integrating your tech stack with CareLogic unlocks concrete data flows and features:

  • Pull: Client demographics and episodes, provider rosters, appointments, treatment plans, progress notes, payer authorizations, service events, claim statuses, remittance summaries
  • Push: New/updated clients and providers from your source systems, scheduled appointments (individual/group, telehealth), clinical notes and signatures, billable service events with diagnosis pointers, claim submissions
  • Build: Authorization-aware scheduling, real-time documentation and compliance checks, automatic claim assembly for 837P/I, reconciliation dashboards driven by service and remittance data

What is CareLogic by Qualifacts?

CareLogic EHR provides clinical, operational, and financial tools tailored to behavioral health and human services organizations. The platform spans intake and referral, episodes of care and programs, treatment planning and documentation, outcomes measurement, scheduling, authorizations and eligibility, and claims/remittances.

Core product areas include:

  • Client intake, demographics, and episodes of care
  • Scheduling (individual and group), telehealth support, and calendars
  • Clinical documentation (progress notes, assessments, treatment plans)
  • Diagnoses (ICD-10) and service coding (CPT/HCPCS) with modifiers and place-of-service
  • Payer management, authorizations, and eligibility tracking
  • Billing and revenue cycle (837P/I generation, 835 remittance reconciliation)
  • Outcomes and measurement-based care (e.g., PHQ-9, GAD-7)
  • Reporting and compliance (audit trails, signatures, note locking)

Common data entities:

  • Clients (patients) and contacts
  • Providers/staff and credentials
  • Programs and episodes of care
  • Appointments (individual, group, telehealth) and attendance
  • Progress notes and documentation artifacts
  • Diagnoses and diagnosis pointers for billing
  • Service events (billable encounters) with service codes and units
  • Authorizations (payer, service code, units, date ranges)
  • Claims (837P/I) and remittances (835)

The CareLogic Integration Challenge

Organizations rely on CareLogic daily, but turning portal-first EHR workflows into automated pipelines is hard:

  • Strong enterprise security and compliance: SSO/MFA, role-based entitlements, and audit trails complicate headless automation
  • Portal- and form-centric flows: Documentation, signatures, and note locking often live in web apps, not unified public APIs
  • Payer-specific rules: Service codes, modifiers (e.g., telehealth 95/GT), diagnosis pointer requirements, and place-of-service constraints vary
  • Authorization and eligibility nuance: Units tracking, program alignment, and service-level constraints must be honored
  • Batch interfaces and timing: 837/835 EDI feeds, SFTP windows, and submission schedules require deterministic handling
  • Clinical workflow guardrails: Provider/client signatures and locked notes need compliant edit/amendment trails

How Supergood Creates CareLogic 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, scheduling, documentation, and claim objects so you can integrate once across programs and payers
  • Aligns with customer entitlements and licensing to ensure compliant access
  • Bridges batch exports and SFTP/EDI flows where applicable with signed URL retrieval and delivery

Use Cases

EHR/CRM-to-CareLogic Synchronization

  • Push client and provider rosters from your source systems into CareLogic
  • Maintain a single source of truth for demographics, programs, and episodes of care
  • Keep insurance and eligibility data synchronized across systems

Authorization-Aware Scheduling and Eligibility

  • Validate payer authorizations before scheduling appointments or posting service events
  • Track remaining authorized units and prevent over-utilization
  • Surface payer- and program-specific rules to schedulers

Clinical Documentation and Sign-Off

  • Create progress notes linked to appointments with required fields and templates
  • Capture provider/client signatures and lock notes with compliant amendments when needed
  • Enforce diagnosis pointers and place-of-service at the point of documentation

Claims Generation and Reimbursement Automation

  • Bundle billable service events into 837P/I claims with payer-specific formatting
  • Submit via configured channels (portal, gateway, or clearinghouse) and track statuses
  • Reconcile 835 remittances alongside documentation and authorization evidence

Audit and Compliance

  • Export complete documentation packets with timestamps, signatures, diagnoses, and amendments
  • Maintain machine-readable audit trails aligned to agency and payer requirements
  • Prove authorization alignment and claim provenance during reviews

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_1a2b3c",
    "name": "BH Admin",
    "entitlements": ["clients", "scheduling", "documentation", "billing"]
  }
}

Clients

GET /clients: Retrieve client demographics, episodes of care, programs, diagnoses, and payer details. Use this to maintain roster alignment across systems.

Query parameters

  • clientId: string
  • programId: string
  • activeOn: ISO 8601 date
  • providerId: string (primary clinician)

Example response

{
  "items": [
    {
      "clientId": "cl_92af01",
      "mrn": "MRN-12345",
      "name": {"first": "Ava", "last": "Nguyen"},
      "dateOfBirth": "1990-08-15",
      "sex": "female",
      "contact": {"phone": "+1-555-0145", "email": "[email protected]"},
      "address": {
        "line1": "200 Wellness Ave",
        "city": "Austin",
        "region": "TX",
        "postalCode": "78701"
      },
      "programs": [
        {
          "programId": "prog_outpatient",
          "name": "Outpatient Behavioral Health",
          "episodeId": "ep_abc123",
          "startDate": "2026-01-01",
          "endDate": null
        }
      ],
      "primaryPayer": {
        "payerId": "payer_tx-medicaid",
        "memberId": "TX12345",
        "eligibility": "active"
      },
      "diagnoses": [
        {"code": "F33.1", "description": "Major depressive disorder, recurrent, moderate", "effectiveDate": "2026-01-01"}
      ],
      "status": "active"
    }
  ],
  "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 posting of service events.

Query parameters

  • clientId: string
  • providerId: string
  • serviceCode: string (CPT/HCPCS)
  • activeOn: ISO 8601 date
  • payerId: string

Example response

{
  "items": [
    {
      "authorizationId": "auth_7342c1",
      "authorizationNumber": "A-2026-11872",
      "clientId": "cl_92af01",
      "clientName": "Ava Nguyen",
      "providerId": "prv_41cf92",
      "payerId": "payer_tx-medicaid",
      "program": "Outpatient BH",
      "serviceCode": "90834",
      "modifiers": [],
      "unitsAuthorized": 24,
      "unitsRemaining": 18,
      "startDate": "2026-01-01",
      "endDate": "2026-03-31",
      "status": "active"
    }
  ],
  "page": 1,
  "pageSize": 50,
  "total": 1
}

Appointments

POST /appointments: Create or update an appointment (individual or group) with service details, location/modalities, and authorization context.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/appointments \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "clientId": "cl_92af01",
    "providerId": "prv_41cf92",
    "programId": "prog_outpatient",
    "start": "2026-02-10T14:00:00Z",
    "end": "2026-02-10T14:55:00Z",
    "serviceCode": "90834",
    "modifiers": [],
    "location": {"type": "office", "placeOfService": "11"},
    "authorizationId": "auth_7342c1",
    "telehealth": {"enabled": false},
    "groupSession": false,
    "notes": "Follow-up therapy session",
    "referenceId": "ehr-cal-1122"
  }'

Example response

{
  "appointmentId": "apt_b38f90",
  "status": "scheduled",
  "clientId": "cl_92af01",
  "providerId": "prv_41cf92",
  "createdAt": "2026-01-19T16:02:10Z",
  "referenceId": "ehr-cal-1122"
}

Service Events

POST /service-events: Record a billable service event tied to an appointment with diagnoses, signatures, and documentation metadata. Supports modifiers and place-of-service.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/service-events \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "clientId": "cl_92af01",
    "providerId": "prv_41cf92",
    "appointmentId": "apt_b38f90",
    "programId": "prog_outpatient",
    "serviceCode": "90834",
    "modifiers": [],
    "units": 1,
    "placeOfService": "11",
    "diagnoses": [
      {"code": "F41.1", "pointer": 1},
      {"code": "F33.1", "pointer": 2}
    ],
    "progressNote": {
      "templateId": "tmpl_progress",
      "content": "Client presents with reduced anxiety; CBT techniques applied.",
      "signed": false
    },
    "providerSignature": {"status": "captured", "timestamp": "2026-02-10T15:05:00Z"},
    "clientSignature": {"status": "captured", "timestamp": "2026-02-10T15:06:12Z"},
    "authorizationId": "auth_7342c1",
    "referenceId": "ehr-doc-5541"
  }'

Example response

{
  "eventId": "sev_5f9a21",
  "status": "posted",
  "billableStatus": "ready",
  "noteId": "note_77c210",
  "createdAt": "2026-02-10T15:07:33Z",
  "referenceId": "ehr-doc-5541"
}

Claims

POST /claims: Assemble an 837P/I claim from posted service events. Supergood normalizes service lines and can route the generated file to the configured submission channel.

curl --request POST \
  --url https://api.supergood.ai/integrations/<integration_id>/claims \
  --header 'Authorization: Bearer <authToken>' \
  --header 'Content-Type: application/json' \
  --data '{
    "claimType": "837P",
    "payerId": "payer_tx-medicaid",
    "billingProvider": {
      "npi": "1234567890",
      "taxonomy": "Behavioral Health",
      "name": "Sunrise Behavioral Health",
      "billingAddress": {
        "line1": "300 Care Way",
        "city": "Austin",
        "region": "TX",
        "postalCode": "78701"
      }
    },
    "serviceEvents": [
      {"eventId": "sev_5f9a21", "units": 1, "serviceCode": "90834", "modifiers": [], "placeOfService": "11"}
    ],
    "submissionChannel": "clearinghouse",
    "referenceId": "billing-batch-feb10"
  }'

Example response

{
  "claimId": "clm_71af2b",
  "status": "queued",
  "edi": {"format": "837P", "size": 49280},
  "submissionChannel": "clearinghouse",
  "createdAt": "2026-02-10T16:05:42Z",
  "reviewUrl": "https://download.carelogic.example/signed/abc123...",
  "referenceId": "billing-batch-feb10"
}

Get full API Specs →

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 appointments, authorizations, documentation, and claim artifacts
  • Security: Encrypted transport, scoped tokens, and audit logging; respects CareLogic entitlements and compliance requirements
  • Webhooks: Optional asynchronous delivery for documentation status, claim generation, and remittance updates

Performance Characteristics

  • Latency: Sub-second responses for list/detail queries under normal load
  • Throughput: Designed for high-volume scheduling, documentation, 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

  1. Schedule Integration Assessment

Book a 30-minute session to confirm your CareLogic product mix, licensing, and authentication model.

  1. Supergood Builds and Validates Your API

We deliver a hardened CareLogic adapter tailored to your workflows and entitlements.

  1. Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as CareLogic evolves.

Schedule Integration Call →

Frequently Asked Questions

Q: Which CareLogic modules can this integration cover?

Supergood supports workflows across commonly used CareLogic modules and agency-facing tools, subject to your licensing and entitlements. We scope coverage (e.g., client intake/episodes, scheduling, documentation, authorizations, claim assembly, remittance retrieval) during integration assessment.

Q: How are MFA, SSO, and documentation/signatures handled for automation?

We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For documentation flows, we capture provider/client signatures, lock notes, and align with amendment/audit requirements programmatically.

Q: Can I generate claims directly from posted service events?

Yes. You can assemble 837P/I from service events with payer-specific formatting. We can route submissions via your configured channel (portal, MCO gateway, or clearinghouse) and return statuses and artifacts for reconciliation.

Ready to automate your CareLogic workflows?

Supergood can have your CareLogic integration live in days with no ongoing engineering maintenance.

Get Started →

Read more