SimplePractice at a glance
| Vendor | SimplePractice, LLC |
|---|---|
| Deployment segment | Behavioral Health, Ambulatory |
| Integration method | Proprietary API and FHIR R4 |
| Authentication | OAuth 2.0 via SimplePractice developer portal; webhook signing secret for event callbacks. |
| Data sync cadence | Real-time via SimplePractice webhooks (appointments, billing events); near-real-time API polling (60 seconds) for uncovered resources. |
| Typical go-live | 1–3 weeks typical for solo-to-small-group practices. |
How QuickIntell connects to SimplePractice
QuickIntell connects to SimplePractice over Proprietary API and FHIR R4. Authentication: OAuth 2.0 via SimplePractice developer portal; webhook signing secret for event callbacks. The integration is bidirectional — QuickIntell reads patient, encounter, order, coverage, and documentation resources from SimplePractice, and writes back claim statuses, prior-authorization decisions, coding suggestions, and payment-posting events. Data exchange is encrypted in transit (TLS 1.2+), encrypted at rest (AES-256), and covered by a signed Business Associate Agreement per HIPAA.
See the full platform flow on how QuickIntell works, compare adjacent connectors in the EHR integration overview, or review encryption, BAA, and access controls on the security page.
QuickIntell modules validated on SimplePractice
The 5 modules below are production-validated against SimplePractice. Every module uses the same Proprietary API and FHIR R4 surface described above — no separate integration is required per module.
| Module | What it does on SimplePractice |
|---|---|
| QuickRCM | End-to-end revenue cycle orchestration from SimplePractice encounter data — eligibility, claim scrubbing, submission, denials. |
| QuickAuth | Prior-authorization automation using SimplePractice clinical data to build, submit, and track payer auth requests. |
| QuickCode | AI-assisted ICD-10 / CPT / HCPCS coding against SimplePractice clinical documentation with modifier guidance. |
| QuickERA | Automated 835 / EOB posting and underpayment detection reconciled against SimplePractice patient accounts. |
| QuickScribe | Ambient clinical documentation that writes structured notes back into the SimplePractice chart. |
Go deeper on the modules above — QuickRCM for end-to-end revenue cycle and QuickAuth for prior-authorization automation. Browse adjacent connectors on the integrations index, or review encryption, BAA, and access controls on the security page.
SimplePractice integration setup steps
- 1Register for SimplePractice API partner access; obtain OAuth client credentials.
- 2Configure webhook subscriptions for appointments, notes, and claim events.
- 3Map SimplePractice service codes and fee schedule to QuickIntell's coding rules.
- 4Validate in a SimplePractice sandbox; run a one-week parallel billing cycle.
- 5Promote to production; confirm first-month ERA posting reconciles against SimplePractice reports.
Data sync cadence
Real-time via SimplePractice webhooks (appointments, billing events); near-real-time API polling (60 seconds) for uncovered resources. QuickIntell retries transient interface failures with exponential backoff and logs every message delivery so reconciliation is auditable end-to-end. Operational exceptions (rejected messages, schema drift, credential expiry) route to the customer's QuickIntell console for triage. For day-2 operations on SimplePractice, the same console exposes the Health dashboard (circuit state, weekly uptime, recent errors), the Sync log with correlation IDs for end-to-end traceability across FHIR R4 and HL7 v2 acknowledgements, and the Conflict workspace for picking a winner when QuickIntell and SimplePractice disagree on the same field — described in the section below.
Operational resilience on SimplePractice
Every QuickIntell EHR connector ships with the same day-2 control surface — so when something drifts on the SimplePracticeside, your team has the tools to see it, fix it, and prove what happened. The four controls below are part of the platform; they are not SimplePractice-specific add-ons.
- Health dashboard
One screen for the SimplePractice connector — circuit state (CLOSED / HALF_OPEN / OPEN), last successful inbound and outbound sync, conflicts pending, and three rolling numbers: weekly uptime (target 99.5%+), syncs in the last 24 hours, and recent errors.
- Sync log + correlation IDs
Every sync attempt against SimplePractice is recorded with a timestamp, direction, source, status, plain-language errorReason, and a unique correlation ID — so any payload can be traced end-to-end across QuickIntell, the interface engine, and the SimplePractice acknowledgement without guesswork.
- Conflict workspace
When QuickIntell and SimplePractice disagree on the same field, the row lands in the Conflict workspace with both values, the source of each, and a full audit trail. Pick a winner, apply, and the next sync converges — no silent overwrites, no "which system is right" guessing.
- Backfill mode
After an outage, credential reset, or a fresh go-live, Run Backfill catches SimplePractice up over a chosen date range — out-of-band so it never blocks the standard poll cadence, scoped to a resource set, and tagged source =
BACKFILLin the Sync log so progress is auditable.
Recovery & SLA
- Health check cadence
- 1 minute
- Drift MTTD
- <60 seconds
- Breaker cooldown
- 1 hour to HALF_OPEN
- Backfill throughput
- ≤ 24 hours per million records
- Polling cadence
- 1 minute (configurable to 15 min default)
Go-live timeline
1–3 weeks typical for solo-to-small-group practices. The timeline spans the five steps above, concluding with a pilot department or practice running end-to-end before broader rollout. Multi-site or multi-tenant deployments add calendar time for each additional SimplePractice instance.
Behavioral health on SimplePractice
- Group therapy 90853 + per-member attribution
Group psychotherapy sessions billed under CPT 90853 are split per attending member with their own claim, eligibility snapshot, and authorization unit count — so the SimplePracticegroup note maps cleanly to each payer's one-claim-per-member rule without manual rework.
- Telehealth modifiers 95/GT + POS 02/10
Telehealth sessions auto-attach modifier 95 or GT and place-of-service 02 (non-home) or 10 (patient home) per payer policy, with audit trails on every claim — keeping behavioral-health telehealth visits payer-compliant as post-PHE rules continue to shift.
- Psychotherapy-note privacy (45 CFR §164.508)
Psychotherapy notes get heightened protection under 45 CFR §164.508 — QuickIntell honors SimplePractice's no-export flag on restricted notes and never pulls them into coding, claim, or denial workflows, so PHI stays scoped to what payers are actually entitled to see.
SimplePractice teams usually start with prior auth automation, AI coding, ERA posting, and QuickRCM for the revenue-cycle worklist, with the broader behavioral-health solution available for group practices, IOP, PHP, and SUD programs.
Insurance Discovery for self-pay accounts
Self-pay book? QuickIntell's weekly Insurance Discovery sweep finds active commercial coverage for ~20% of self-pay accounts — 25 credits per search, 30-day dedupe window. See the Insurance Discovery module.
Pipeline orchestration confidence
Every Automation Point ships in NOTIFY_ONLY mode. Move to SEMI_AUTOMATIC after 1–2 weeks of clean observation, then AUTOMATIC at >95% approval. AP-2 (Prior Auth), AP-12 (Appeals), and AP-17 (EHR write-back) can stay on SEMI_AUTOMATIC permanently if your compliance posture requires a human signature.
Known limitations
Every SimplePractice deployment has environment-specific edges. The boundaries below apply to the QuickIntell integration itself — they are not deficiencies of SimplePractice.
- SimplePractice's FHIR surface is narrower than larger EHRs; QuickIntell uses the proprietary API for most billing and scheduling writes.
- QuickVoice is not currently bundled in the SimplePractice integration; ambient documentation can be added via a manual paste-back workflow.
Frequently asked questions — SimplePractice integration
How does QuickIntell connect to SimplePractice?
QuickIntell connects to SimplePractice via Proprietary API and FHIR R4. Authentication is handled through OAuth 2.0 via SimplePractice developer portal; webhook signing secret for event callbacks. The integration exchanges patient demographics, encounters, orders, coverage, clinical documentation, and billing data bidirectionally, with all traffic encrypted in transit (TLS 1.2+) and at rest (AES-256).
How long does an integration with SimplePractice take?
1–3 weeks typical for solo-to-small-group practices. The timeline covers partner-program enablement, credential provisioning, data mapping, sandbox validation, and a single-department or single-practice pilot before broader rollout. Multi-site deployments add calendar time per additional SimplePractice instance.
Which QuickIntell modules work with SimplePractice?
The following QuickIntell modules are production-validated on SimplePractice: QuickRCM, QuickAuth, QuickCode, QuickERA, QuickScribe. Each module uses the same Proprietary API and FHIR R4 surface — customers do not need to run a separate integration per module.
How often does data sync between SimplePractice and QuickIntell?
Real-time via SimplePractice webhooks (appointments, billing events); near-real-time API polling (60 seconds) for uncovered resources. Transient interface failures are retried with exponential backoff, and every message delivery is logged for audit. Operational exceptions (rejected messages, schema drift, credential expiry) surface in the QuickIntell console for triage.
Is QuickIntell certified or listed in the SimplePractice partner program?
QuickIntell participates in the SimplePractice, LLC partner ecosystem and is available via direct integration today. Marketplace listing status varies by vendor; contact the QuickIntell team for the current certification and listing state against your SimplePractice tenant.
What are the known limitations of the QuickIntell–SimplePractice integration?
SimplePractice's FHIR surface is narrower than larger EHRs; QuickIntell uses the proprietary API for most billing and scheduling writes. QuickVoice is not currently bundled in the SimplePractice integration; ambient documentation can be added via a manual paste-back workflow. These boundaries apply to the integration itself and are not deficiencies of SimplePractice.
Does QuickIntell submit therapy claims on my behalf or do I still use SimplePractice?
SimplePractice remains the system of record and the place your team reviews the encounter. QuickIntell reads appointment, coverage, service-code, and claim metadata, scrubs and enriches the claim workflow, then writes back statuses or posting context where the SimplePractice API permits it.
How does QuickIntell handle group therapy 90853 billing?
QuickIntell follows the Specialty Billing manual pattern for group sessions: switch the session into group mode, attach each attending patient, bill CPT 90853 per attendee, and keep each member's eligibility, authorization units, claim, and ERA outcome separate.
Does QuickIntell read my psychotherapy notes?
No. QuickIntell does not read psychotherapy notes or no-export restricted note content from SimplePractice. It uses appointment, service, payer, claim, and documentation metadata needed for billing and compliance workflows.
Can I run QuickIntell as a solo therapist or only as a group?
Both. SimplePractice solo clinicians can run QuickRCM, QuickAuth, QuickCode, QuickERA, and QuickScribe in the same 1–3 week implementation path, while groups add provider, location, fee-schedule, and group-session mappings during onboarding.
How does QuickIntell handle telehealth POS and modifier 95/GT?
QuickIntell applies the Specialty Billing manual's telehealth pattern to SimplePractice sessions: POS 02 for telehealth outside the patient's home, POS 10 for telehealth in the patient's home, modifier 95 or GT where payer policy requires it, and modifier 93 for audio-only sessions when applicable.
What happens if SimplePractice's note-write API rate-limits us?
QuickIntell queues note writebacks, applies exponential backoff, surfaces the delay in the Sync log, and keeps the approved note draft available for manual paste-back if the rate limit persists. Billing-side workflows continue from the last confirmed SimplePractice sync.
Is patient data secure during the SimplePractice integration?
Yes. All data exchanged between QuickIntell and SimplePractice is encrypted in transit using TLS 1.2+ and at rest using AES-256. QuickIntell is HIPAA-compliant, provides a signed Business Associate Agreement, and maintains SOC 2 Type II controls. Role-based access and audit logging cover every read and write against SimplePractice data.
Connect QuickIntell to your SimplePractice tenant
Get a personalized integration plan. The QuickIntell team maps your SimplePractice workflows to QuickRCM, QuickAuth, QuickCode, QuickERA, and QuickScribe — typical go-live is 1–3 weeks typical for solo-to-small-group practices..
Disclaimer
This page describes the QuickIntell integration with SimplePractice and is provided for operational reference. SimplePractice is a trademark of SimplePractice, LLC; QuickIntell is not affiliated with or endorsed by SimplePractice, LLC except as noted above. Integration capabilities evolve as vendor APIs change — contact the QuickIntell integrations team for the current scope on your tenant.