Book a demoGet started
TheraPro Clinical · Integrations

If it has an API, TheraPro connects to it.

Any REST API. Any database. Most rehab EMRs. Data in, data out, in real time. And if we integrate it, we support it. 100%.

Request an integrationSee what we connect

REST and JSONFHIR R4HL7 v2SQL and NoSQLSigned webhooksCSV

  • Any REST API.If it speaks HTTPS and JSON, TheraPro connects to it. API keys, OAuth 2.0 and signed requests are all supported.
  • Any database.PostgreSQL, MySQL, SQL Server, Oracle, Snowflake, MongoDB, or a plain export file from a system you've retired.
  • Most rehab EMRs.Cliniko and Juvonno you connect yourself. WebPT, Raintree, Prompt, Net Health and Clinicient we set up for you, with FHIR R4 and HL7 v2 for hospital systems.
  • 100% supported.If we build it, we monitor it, fix it and keep it current when the other system changes. For as long as you're with us.
Built in. Not a roadmap.

Your EMR, your data and your tools, managed from one screen.

Integrations live in Settings, inside every TheraPro Clinical account. Connect an EMR, choose what syncs in which direction, import patients and send real-time events to any system.

  • Cliniko and Juvonno, connected with your own key in minutes
  • Five more rehab EMRs set up by TheraPro
  • Two-way sync controls for each type of data
  • CSV import with a full preview. Nothing is added until you confirm.
  • 11 real-time events, signed and delivered to any HTTPS address
  • A log of every sync, import and export
TheraPro Clinical Settings, Integrations: WebPT connected, other EMRs ready to connect
The directory

The systems your clinic runs on. Connected.

If it isn't on this list and it has an API, a database or an export, we can connect it.

Every system your clinic runs on

EMRs, databases, billing, scheduling, CRM and automation, in one place.

Live todayIn the catalogComing soonEverything else is built on request

Product names and logos are trademarks of their owners and are shown to describe compatibility. A listing does not mean a partnership or endorsement. Integrations built on request are scoped for each clinic and depend on the other vendor providing access.

Import and export

Data in. Data out. Nothing lost.

Bring records in from any source, clean them on the way, and send them anywhere your team needs them.

  • EMR feed
  • Database
  • REST API
  • CSV file
TheraPro
  1. Map fields
  2. Validate
  3. Match duplicates
  4. Encrypt and log
  • EMR write-back
  • Webhooks
  • Data warehouse
  • CSV export
Import

From anywhere

  • CSV export from any EMR or spreadsheet
  • HL7 v2 patient and scheduling feeds
  • FHIR R4 Patient and Appointment resources
  • Direct database reads, SQL and NoSQL
  • REST API pulls on a schedule you choose
  • One-time migration from a retired system
TheraPro import and export settings with signed webhooks
Export

To everything

  • Visit summaries written back to your EMR
  • Home program assignments and progress
  • Signed real-time webhooks for 11 events
  • CSV downloads of patients and appointments
  • REST endpoints for your BI and data team
  • Scheduled extracts to your data warehouse
Under the hood

Built by integration engineers. Down to the field.

Healthcare data is messy. Names arrive in pieces, dates in four formats, providers by number. This is the work we do so your team never has to.

WebPT ADT feedTheraPro Clinical
Source fieldTransformTheraPro field
PID-3 Patient identifierTrim, keep as match keypatient.mrn
PID-5 DOE^JANESplit family and given namepatient.lastName, firstName
PID-7 19860214YYYYMMDD to ISO 8601patient.dob 1986-02-14
PID-13 (843) 555-0142Normalize to E.164patient.phone +18435550142
SCH-11 202610061430Convert to clinic time zoneappointment.start
PV1-7 Attending providerMatch therapist by NPIappointment.therapistId

Validated before import. Missing or malformed fields are held back with a plain reason, and possible duplicates are flagged for review instead of merged.

  • HL7 v2.x
  • FHIR R4
  • REST and JSON
  • OAuth 2.0
  • HMAC-SHA256
  • SQL and NoSQL
  • CSV
  • X12 270/271
The numbers

Faster to connect. Cheaper to run.

Integration projects in healthcare are known for running for months. Ours are measured in days and weeks.

Time to go live

Typical timelines by connection type

  • CSV import and exportSame day
  • Signed webhooksSame day
  • Custom REST API1–3 weeks
  • Catalog rehab EMR2–8 weeks
  • Typical custom EMR interface project3–9 months

Catalog EMR timelines are mostly the EMR vendor's approval. The industry figure is a typical range for custom-built interfaces.

Stop re-typing patients

What double entry costs your front desk

1,000staff hours back per year
$24,000in front-desk time not spent re-typing

Assumes 3 minutes of duplicate entry per visit, 50 working weeks and $24/hour front-desk cost.

Real-time events

Delivered to your systems as they happen

  • Visit completedsession.completed184 ms
  • Appointment bookedappointment.booked201 ms
  • Patient addedpatient.added176 ms
  • Form submittedform.submitted193 ms
  • No-showsession.no_show168 ms
  • Home program createdprogram.created210 ms
  • Visit rescheduledsession.rescheduled187 ms
  • Video visit scheduledtelehealth.scheduled199 ms

Example deliveries. Every event is signed and logged in Settings.

How it works

From request to live, without the usual project.

You name the system. We do the integration work.

  • YouName the systemTell us what you use and what should move. One form, no spec required.
  • TheraProWe scope itWe confirm the method (API, FHIR, HL7, database or file), the fields and the direction.
  • TheraProWe build and testBuilt and tested against a sandbox or test data before any patient record moves.
  • TogetherGo liveYou choose the switch-on date. Every sync is logged in Settings from the first record.
  • TheraProSupported for goodWe monitor it, fix it and update it when the other system changes. Included in the monthly price.
The TheraPro guarantee

If we integrate it, we support it. 100%.

No handoff to a third party. No "unsupported configuration". Every connection we build stays our responsibility for as long as you're a TheraPro customer.

Request an integration
Monitored
Failed syncs and webhook deliveries are flagged and retried automatically.
Fixed by us
If a connection we built breaks, we fix it. You never open a ticket with three vendors.
Kept current
When the other system changes its API or interface, updating the connection is on us.
One accountable team
One owner for the whole connection, from the first field map to the last record.
Secure by design

Connected doesn't mean exposed.

Every integration runs inside your clinic's isolated TheraPro environment, under the same HIPAA safeguards as the rest of the platform.

HMAC-SHA256signed events
AES-256encryption at rest
BAAon every plan
Read the security FAQ
  • Signed webhooksEvery delivery is signed with HMAC-SHA256 and a timestamp, so your server can reject anything forged or replayed.
  • Minimum necessaryWebhook messages carry record IDs only, never names or clinical notes.
  • Every sync loggedImports, exports, deliveries and settings changes are recorded with who and when.
  • Encrypted end to endTLS in transit and AES-256 at rest, on AWS infrastructure in the United States.
  • Owner-approvedOnly the clinic owner can add a paid integration. Only clinic admins can import patients or change what syncs.
  • Signed BAAEvery integration runs under the business associate agreement you already have with us.
Questions

Integration questions, answered.

The things teams ask us most before they switch.

Still deciding?Talk to someone who knows the product. We'll walk you through it with your workflow in mind.
Book a demoContact us

  • Cliniko and Juvonno you connect yourself with your own API key. WebPT, Raintree, Prompt Health, Net Health and Clinicient TheraPro sets up with the vendor for you. For hospital and multi-specialty systems such as Epic, Oracle Health, athenahealth, eClinicalWorks and NextGen we connect through FHIR R4, HL7 v2 or the vendor's API. If your EMR isn't listed, ask: most can be connected.

  • CSV import and export and webhooks are included in every plan. Standard EMR connectors (Cliniko, Juvonno) are $299 to set up and $29 a month. Advanced EMR integrations (WebPT, Raintree, Prompt Health, Net Health, Clinicient) are $599 to set up and $49 a month, and the monthly price starts only when your connection goes live. Custom API, multi-location and data migration work is quoted for you. The full list is on the pricing page.

  • The clinic owner adds paid integrations in the clinic app, under Settings, Integrations. Other admins see the price and can ask the owner with one click. Once it's paid, the connection options appear straight away.

  • Almost always. We can read a database directly, pick up scheduled export files, receive an HL7 feed, or start with CSV import and export, which works with any system today.

  • Yes. We map your old export or database to TheraPro, show you a preview before anything is added, match duplicates, and log every row that comes in.

  • We do. If we integrate it, we support it: monitoring, fixes and updates when the other vendor changes something are all on TheraPro.

  • You choose per data type. Patients and appointments usually flow into TheraPro, and visit summaries and Home programs flow back to your EMR. Each direction can be switched on or off in Settings.

  • CSV import and webhooks work the same day. Cliniko and Juvonno take about 5 minutes once they're on your plan. Advanced EMR connections usually take 2 to 8 weeks, mostly waiting on the EMR vendor's approval. Custom API work is scoped up front, so you know the timeline before we start.

Name the system. We'll connect it.

Tell us what your clinic runs on. We'll come back with the method, the timeline and what syncs, before any work starts.

Request an integrationExplore TheraPro Clinical