PIMSY API
PIMSY is an electronic health record (EHR) and practice management system built for behavioral and mental health providers. With an unofficial API, you could synchronize client and provider rosters, create and manage appointments, validate and track authorizations, assemble and submit claims, and ex
What is PIMSY?
PIMSY provides behavioral health EHR and practice management capabilities for outpatient, residential, and community-based programs. Core workflows include scheduling, client intake, documentation (treatment plans, progress notes, assessments), telehealth, e-prescribing via partners, utilization/authorizations, and integrated billing from charge capture through claim submission and ERA reconciliation.
Core product areas include:
- Scheduling and session management (individual and group)
- Client records, demographics, and insurance management
- Treatment plans, goals/objectives, and progress notes
- Telehealth scheduling and links
- E-prescribing (via partnered solutions), labs/documents
- Authorizations and utilization tracking
- Billing and claims (837/835), ERA/EDI workflows
- Reporting, audit trails, and role-based security
Common data entities:
- Clients (patients) and contacts/guardians
- Providers/clinicians and clinical programs
- Appointments/sessions (including telehealth)
- Treatment plans, goals, and plan reviews
- Progress notes and clinical documents (signatures, lock status)
- Authorizations (payer, service code/CPT, units, dates)
- Insurance policies and payers
- Claims, service lines, and remittances (ERAs)
- Locations, groups, and (where applicable) beds/assignments
The PIMSY Integration Challenge
Organizations rely on PIMSY daily, but turning portal-based EHR workflows into automated pipelines is hard:
- Portal-first delivery: Scheduling, notes, and billing actions live primarily in web apps or batch exports, not a unified public API
- MFA/SSO and security controls: Strong authentication and network policies complicate headless automation
- Batch EDI and timing windows: 837 generation, ERA retrieval, and payer submissions follow batching constraints
- Clinical compliance: Signed/locked notes and e-signatures require audit trails and immutable status handling
- Coding and payer nuances: CPT/HCPCS, modifiers, and authorization rules vary by plan and line of business
- Change management: Form templates, required fields, and coding updates evolve over time
How Supergood Creates PIMSY 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 behavioral health objects (clients, sessions, notes, authorizations, claims) behind stable schemas
- Aligns with customer entitlements and licensing constraints to ensure compliant access
- Bridges batch exports and EDI flows with signed URL retrieval and delivery for claims and ERAs
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your PIMSY product mix, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened PIMSY adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as PIMSY evolves.
API Endpoints
Authentication
/sessionsEstablish 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.
Clients
/clientsRetrieve client demographics, insurance, and care team context for downstream scheduling, intake, and analytics.
Appointments
/appointmentsCreate or update an appointment/session with service details and optional telehealth configuration. Authorization checks are applied when provided.
Authorizations
/authorizationsRetrieve client/payer authorizations with allowed units, service codes, and date ranges. Use this to validate scheduling and claim eligibility.
Claims
/claimsAssemble an 837P claim from completed sessions. Supergood normalizes service lines and can route the generated file to the configured submission channel.
Use Cases
Intake and Scheduling Sync
- Push new clients from your intake system into PIMSY with demographics and insurance - Create appointments (including telehealth links) and keep external calendars in sync - Route confirmations and reminders with status updates back to your CRM
Authorization-Aware Scheduling and Eligibility
- Validate coverage and authorizations before booking sessions - Track units remaining to prevent over-utilization and denials - Surface payer-specific rules for front desk and care coordinators
Clinical Documentation and QA
- Pull note metadata and status to power QA workflows - Enforce sign/lock steps and attach supporting documents programmatically - Export plan and note summaries to analytics pipelines
Claims Generation and Reimbursement Automation
- Assemble compliant 837P claims from sessions and authorizations - Submit via your configured channel (payer portal or clearinghouse) and track statuses - Retrieve ERAs and reconcile payments alongside note and authorization evidence
Analytics and Outcomes Reporting
- Centralize schedules, documentation metadata, and financials in your data warehouse - Monitor productivity, utilization, and no-show rates - Build measurement-based care and population health dashboards
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, schedules, notes metadata, authorizations, and claim artifacts
Security
Encrypted transport, scoped tokens, and audit logging; respects PIMSY entitlements and compliance requirements
Webhooks
Optional asynchronous delivery for schedule changes, claim generation, and remittance updates
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume scheduling 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
Frequently asked questions
Supergood supports workflows across commonly used PIMSY scheduling, client charting, authorization tracking, and billing tools, subject to your licensing and entitlements. We scope coverage (e.g., appointments, note metadata, authorizations, claims/ERAs) during integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For batch flows, we manage EDI timing windows, generate 837 files, and retrieve signed URLs or delivery confirmations programmatically.
Yes. You can assemble 837P from completed sessions with payer-specific formatting. We can route submissions via your configured channel (payer portal or clearinghouse) and return statuses and ERA artifacts for reconciliation.