Opus EHR API
With an unofficial API, you can unlock programmatic access to core Opus EHR data and workflows—patients, admissions, treatment plans, schedules, authorizations, and claims—so your systems don’t rely on manual exports or browser automation. If you’re a different tech company integrating with Opus EHR
What is Opus EHR?
Opus EHR provides behavioral health and addiction treatment EHR capabilities spanning intake, clinical documentation, scheduling, outcomes, and revenue cycle. Teams use Opus to coordinate care across programs, manage authorizations, and submit claims.
Core product areas include:
- Admissions and episodes of care (levels of care, bed assignments, census)
- Patient/client roster management with demographics and payers
- Scheduling (individual, group sessions) and attendance tracking
- Treatment planning (goals, objectives) and clinical documentation (progress notes, assessments)
- Payer authorizations and utilization tracking
- Billing and claims (837P/I) with remittance (835) reconciliation
- Outcomes measurement and reporting
- Telehealth and e-sign for consents/forms (varies by configuration)
Common data entities:
- Patients/Clients
- Admissions/Episodes and Programs (Detox, Residential, PHP, IOP, Outpatient)
- Providers/Staff
- Appointments and Group Sessions
- Treatment Plans and Clinical Notes
- Payers and Authorizations (service codes, units, dates)
- Claims and Remittances
- Beds and Census
- Referrals and Intake forms
The Opus EHR Integration Challenge
Organizations rely on Opus EHR daily, but turning portal-first workflows into automated pipelines presents hurdles:
- Program-specific structures: Levels of care, group vs. individual services, and documentation lock/sign workflows vary by program
- Authorization nuances: Service codes, units, and dates must align with program and payer rules; over-utilization prevention and updates are critical
- Strong enterprise security: SSO/MFA and role-based permissions complicate headless access; audit requirements limit bulk edits
- Portal-first delivery: Key scheduling, documentation, and census management exist in web apps or batch exports, not a unified public API
- Batch interfaces and timing windows: HL7/SFTP/EDI feeds, batching constraints, and submission windows need orchestration
- Reporting and export gaps: Users often request deeper API access for CRMs, call tracking, marketing automation, calendar sync, and bed board integrations
How Supergood Creates Opus EHR 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 patient, episode, authorization, scheduling, documentation, and claim objects across Opus deployments
- Aligns with customer entitlements and licensing constraints to ensure compliant access
- Bridges exports and SFTP/EDI flows where applicable with signed URL retrieval and delivery
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your Opus EHR product mix, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened Opus EHR adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Opus EHR 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.
Patients
/patientsRetrieve patient/client profiles with demographics, payer enrollments, and current program status. Use this for roster sync and intake handoffs.
Admissions
/admissionsCreate or update an admission/episode for a patient with program, level of care, authorization references, and bed assignment.
Authorizations
/authorizationsRetrieve payer/member service authorizations with allowed units, service codes, levels of care, and date ranges. Use this to validate scheduling and documentation eligibility.
Claims
/claimsAssemble an 837P/I claim from signed documentation and validated authorizations. Supergood normalizes service lines and can route the generated file to the configured submission channel.
Use Cases
Intake and Admissions Automation
- Convert CRM leads to patients and create admissions with program, level of care, and bed assignment - Attach required consents and referral sources to admissions automatically - Maintain a single source of truth for demographics and payers
Authorization Tracking and Utilization Management
- Validate active authorizations before scheduling services - Track remaining units and alert care coordinators in real time - Prevent over-utilization and surface authorization expirations
Scheduling and Group Attendance
- Sync calendars between Opus and your scheduling platforms - Create group sessions and mark attendance with billable/non-billable flags - Route exceptions (e.g., missing signatures) for resolution before billing
Clinical Documentation Export
- Pull signed progress notes, assessments, and treatment plan updates - Centralize outcomes reporting across programs and levels of care - Maintain machine-readable documentation packets with signatures and timestamps
Claims Generation and RCM Automation
- Bundle signed documentation into 837P/I claims with payer-specific formatting - Submit via clearinghouse or payer portals; track statuses and remittances - Reconcile payments with documentation provenance and audit trails
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 patients, admissions, authorizations, documentation, and claim artifacts
Security
Encrypted transport, scoped tokens, and audit logging; respects Opus EHR entitlements and compliance requirements
Webhooks
Optional asynchronous delivery for admissions, authorization updates, documentation locks/signatures, claim generation, and remittance updates
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume intake, scheduling, documentation, and claims 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 Opus EHR modules (e.g., patients, admissions/episodes, scheduling, treatment plans/notes, authorizations, claims), subject to your licensing and entitlements. We scope exact coverage during the integration assessment.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For batch flows, we manage SFTP/EDI timing windows, generate 837 files, and retrieve signed URLs or delivery confirmations programmatically.
Yes. You can assemble 837P/I from signed documentation with payer-specific formatting. We can route submissions via your configured channel (clearinghouse or payer portal) and return statuses and artifacts for reconciliation.