ICANotes API
ICANotes is an EHR purpose-built for behavioral and mental health practices. It focuses on rapid, structured clinical documentation for psychiatry and therapy, plus scheduling, patient intake/forms, treatment planning, e-prescribing, and billing support. With an unofficial API, you could synchronize
What is ICANotes?
ICANotes provides an ONC-certified EHR optimized for behavioral health clinicians, including psychiatrists, psychologists, counselors, social workers, and multidisciplinary clinic staff. Its structured templates enable fast intake notes, progress notes, med management notes, and treatment plans while maintaining detailed audit trails. Practices use ICANotes to schedule sessions, capture DSM-5/ICD-10 diagnoses, manage medications (often through an integrated e-prescribing partner), collect signed forms, and support billing for common behavioral health CPT codes.
Core product areas include:
- Clinical documentation (intake, progress, med management, discharge)
- Treatment planning (problems, goals, objectives, target dates, progress)
- Scheduling and appointment management (in-person and telehealth)
- Client/patient roster with insurance and consents
- Diagnoses (DSM-5/ICD-10) and encounter coding (CPT/HCPCS modifiers)
- E-prescribing and medication management (typically via a partner such as DrFirst)
- Billing support and claim exports (837P, CMS-1500)
- Patient portal and intake forms with signatures
- Reporting and outcomes measures (e.g., PHQ-9, GAD-7)
Common data entities:
- Clients/Patients
- Providers/Clinicians
- Appointments/Sessions
- Encounters/Clinical Notes
- Diagnoses and Problem Lists
- Treatment Plans (goals, objectives, interventions)
- Medications/Allergies
- Insurance Policies and Guarantors
- Claims, Charges, Payments/Remittances
- Consents and Intake Forms
- Assessments/Outcome Scores (PHQ-9, GAD-7, etc.)
The ICANotes Integration Challenge
Organizations rely on ICANotes daily, but turning portal-first behavioral health workflows into automated pipelines is hard:
- Limited public APIs: Many users report wanting easier integrations with scheduling, telehealth, CRM, and analytics tools; most workflows live behind the web app and exports.
- Structured templates and locking: Notes are highly structured and often “locked” post-signature; compliant edits must preserve audit trails and signatures.
- Separate e-prescribing flows: Med management can run through external vendors (e.g., DrFirst), creating cross-system dependencies and authentication constraints.
- Billing interfaces and batching: Practices generate encounter data and batch claims (837P/CMS-1500) via configured clearinghouses, with timing windows and file formats to respect.
- Reporting and data export limitations: Users frequently ask for more flexible reporting/exports (treatment goals, outcomes, productivity) to feed BI tooling.
- Strong enterprise security: MFA/SSO, role-based entitlements, and network controls complicate headless automation.
How Supergood Creates ICANotes 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, appointment, note, diagnosis, and treatment plan objects so you can integrate once
- Aligns with customer entitlements and licensing constraints to ensure compliant access
- Bridges batch exports and clearinghouse submissions with signed URL retrieval and delivery where applicable
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your ICANotes product mix, licensing, and authentication model.
- Supergood Builds and Validates Your API
We deliver a hardened ICANotes adapter tailored to your workflows and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as ICANotes 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 client/patient profiles with demographics, insurance, and key identifiers. Use filters to target onboarding, updates, or analytics.
Appointments
/appointmentsCreate or update an appointment with clinician, location, service coding, and telehealth flags. Sync schedules between ICANotes and external systems.
Clinical Notes
/clinical-notesCreate or update a structured clinical note (progress, intake, med management) with diagnoses, interventions, mental status, goals addressed, and signature status. Supports compliant locks and edit reason codes.
Treatment Plans
/treatment-plansRetrieve treatment plans with problems, goals, objectives, target dates, and progress. Use this to track outcomes and update plans programmatically.
Use Cases
Intake and Patient Onboarding
- Push new clients from your intake funnel or CRM into ICANotes - Attach signed consents and intake forms, mapping custom fields to ICANotes templates - Maintain a single source of truth for demographics, insurance, and emergency contacts
Scheduling and Telehealth Integration
- Synchronize appointments between your scheduling or telehealth platform and ICANotes - Create session records with CPT codes and telehealth flags for downstream billing - Keep providers’ calendars and patient reminders up to date
Clinical Documentation and Outcomes
- Generate progress notes from telehealth session metadata and clinician prompts - Update treatment plans (goals/objectives) and log outcomes (PHQ-9/GAD-7) over time - Lock notes with signature, track edits with reason codes, and export full audit trails
Billing and Revenue Cycle
- Assemble encounter data into claims (837P) using documented CPT codes and modifiers - Route submissions to the configured clearinghouse; reconcile statuses and remittances - Drive productivity dashboards with session counts, code mix, and reimbursement metrics
Analytics and Compliance
- Export machine-readable note packets and treatment plan details for quality programs - Monitor diagnosis trends and outcomes across cohorts - Prove documentation completeness and note lock signatures during audits
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, appointments, notes, and treatment plans
Security
Encrypted transport, scoped tokens, and audit logging; respects ICANotes entitlements and compliance requirements
Webhooks
Optional asynchronous delivery for appointment changes, note locking, and claim exports
Latency
Sub-second responses for list/detail queries under normal load
Throughput
Designed for high-volume documentation and scheduling 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 ICANotes areas, subject to your licensing and entitlements. We typically cover patients, appointments, diagnoses, treatment plans, clinical notes (including lock/signature handling), and billing exports. E-prescribing flows can be bridged where permitted through the configured partner.
We support username/password + MFA (SMS, email, TOTP) and can operate behind SSO/OAuth when enabled. For e-prescribing managed via third-party vendors (e.g., DrFirst), we integrate within the constraints of your configuration, preserving audit trails and consent requirements.
Yes. You can assemble 837P lines from documented encounters (CPT/HCPCS, modifiers, units) and route submissions via your configured clearinghouse. We return statuses and artifacts for reconciliation alongside encounter data.