ICANotes API
ICANotes provides an ONC-certified EHR optimized for behavioral health clinicians, including psychiatrists, psychologists, counselors, social workers, and multidisciplinary clinic staff. This page is an independent design exercise that asks what a well-designed ICANotes API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed ICANotes API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing ICANotes product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
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)
An API for a platform like this would naturally organize around its core 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/role-based entitlements, and network controls complicate headless automation.
What a ICANotes API Could Look Like
If ICANotes exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like ICANotes: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/sessionsWould establish a session using credentials. MFA challenges (SMS, email, TOTP) would need first-class support. Would return a short-lived auth token.
Patients
/patientsWould retrieve client/patient profiles with demographics, insurance, and key identifiers. Use filters to target onboarding, updates, or analytics.
Appointments
/appointmentsWould create or update an appointment with clinician, location, service coding, and telehealth flags. Would sync schedules between ICANotes and external systems.
Clinical Notes
/clinical-notesWould create 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-plansWould retrieve 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 Requirements
Authentication
Would require username/password with MFA (SMS, email, TOTP); 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
Would need 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
Design target: sub-second responses for list/detail queries
Throughput
Design target: designed for high-volume documentation and scheduling pipelines
Reliability
Retry logic, backoff, and idempotency keys minimize duplicate actions
Versioning
Clear versioning and change management would matter as ICANotes evolves
Frequently asked questions
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual ICANotes product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.