Clarity Connect integration
Stripe eClinicalWorks Integration
When patients pay through Stripe, get each payment onto the right eClinicalWorks account and each Stripe payout reconciled, while visit details stay out of Stripe.
What moves between Stripe and eClinicalWorks
Stripe takes the card or bank payment and pays it out to the practice in batches. eClinicalWorks holds the patient's balance and the billing team's posting. The integration carries payment facts from Stripe toward eClinicalWorks: amount, date, Stripe ID and a reference to the account. Clinical details never travel the other way into Stripe.
Stripe
Where the payment is taken and paid out
- Payments
- Refunds
- Disputes
- Payouts and fees
eClinicalWorks
Where the patient's balance is kept
- Patient account
- Payment posting
- Refunds and adjustments
- Billing reports
Stripe to eClinicalWorks record mapping
Stripe names are its API objects. eClinicalWorks doesn't publish its billing objects, so that side is described in plain terms. Discovery settles the posting route with your eClinicalWorks setup.
| Stripe | eClinicalWorks | Direction |
|---|---|---|
| PaymentIntent (succeeded) and its charge | Patient payment on the account | Stripe to eClinicalWorks |
| Metadata reference (no PHI) | Patient account it belongs to | Set when the payment is created |
| Refund | Refund or adjustment on the account | Stripe to eClinicalWorks |
| Dispute | Flag for the billing team | Stripe to eClinicalWorks |
| Payout and its balance transactions | Deposit reconciliation report | Stripe to billing and accounting |
How the payment sync works
First, check you need Stripe here
eClinicalWorks sells its own payment service, healow Payment Services, which posts payments into the practice management system automatically and offers text-to-pay through healow Pay. A practice already using it may not need Stripe for patient balances. Stripe fits when payments start somewhere eClinicalWorks doesn't reach, such as an online store, a membership or a self-pay portal.
Payments matched to the patient account
When a Stripe payment succeeds, a payment_intent.succeeded event tells Connect. Connect matches it to the account using a reference stored on the payment. It then passes the amount, date and Stripe ID to eClinicalWorks through whatever financial integration eClinicalWorks enables for the practice. Where none is enabled, Connect can produce a posting list for the billing team instead.
Payouts reconciled to the bank
Stripe pays out in batches, net of refunds, disputes and fees. For automatic payouts Stripe lists every transaction inside each payout, so each bank deposit can be matched to the payments posted in eClinicalWorks and to the practice's accounting system.
PHI stays out of Stripe
Stripe doesn't publish a business associate agreement for its payments products. Keep diagnoses, procedures and visit details out of Stripe descriptions, metadata and invoice line items. Stripe also says never to put card or bank details in metadata. The reference on each payment should mean nothing outside the practice's own systems.
See Clarity Connect move an order
Watch an online order travel into the ERP and its status come back in our Clarity Connect demo, or book a live walkthrough on your own systems.
HIPAA, BAAs and card data
HIPAA itself carves out payment processing. Section 1179 of the Social Security Act (42 U.S.C. 1320d-8) says HIPAA's administrative-simplification rules don't apply to a financial institution, or anyone acting for one, when it processes payments for health care by card, check or electronic transfer. The carve-out covers the payment, not visit details. Stripe's own terms point the same way: its Services Agreement bars sending Stripe PHI as part of data shared from other service providers, and Stripe Identity can't be used by a HIPAA-covered entity to process PHI. Have the practice's compliance counsel confirm the setup.
Card data stays with Stripe, in its tokenized vault, as described on Clarity's Stripe gateway page; what Connect handles is payment records, not card numbers. Clarity's Payment Hub for healthcare works the same way and is designed to stay out of PHI scope, posting to the practice's financial system rather than the EHR.
What eClinicalWorks documents
The free APIs eClinicalWorks publishes are its ONC-certified FHIR APIs, which cover the clinical record. It lists integrations "with systems requiring claims or financial data" as a separate type but publishes no terms or specifications for them. Before a project starts, the practice should ask eClinicalWorks which route it will enable for posting outside payments.
How Clarity Connect runs it
Clarity Connect is Clarity's integration platform. For this pair it can listen for Stripe events and run a daily payout check, with matching, refunds and reconciliation as separate tasks so one failure doesn't hold up the rest. Jobs bound for a system that is down are parked in a retry queue and tried again every 30 minutes, up to 10 times. You can watch Connect at work in our video playlist.
Discovery
A Clarity business analyst documents the data fields and workflows each system can share and which ones you need.
Tasks and mapping
Each flow becomes a Connect task, such as orders to the ERP or stock to the store, set to run in real time or on a schedule.
Testing
Orders and updates are run end to end, including the return trip of statuses back to the customer-facing system.
Live, with a dashboard
Queues and scheduled tasks show in Connect's Hangfire dashboard. A job whose target is offline is retried 10 times, every 30 minutes, and can be re-queued once the cause is fixed.
Clarity Connect is sold as a SaaS subscription at $599 a month or as a one-time license at $15,000 with no ongoing fees, and larger projects are priced to scope. See pricing.
Questions
Does the integration store card numbers?
No. Stripe takes and stores the card data. Connect works with Stripe's payment records: amount, date, Stripe IDs and the account reference.
Will Stripe sign a BAA?
Stripe doesn't publish one for its payments products. Plan the integration so no PHI goes to Stripe, and confirm your arrangement with Stripe and your compliance counsel.
We already use healow Payment Services. Do we need this?
Probably not for patient balances, since healow Payment Services already posts into eClinicalWorks. This integration is for payments taken in Stripe, such as on a store or self-pay portal, that still need to reach the patient's account.
How is Clarity Connect priced?
Clarity Connect costs $599 a month as SaaS, or $15,000 for a one-time license with nothing ongoing. Larger scopes are priced individually. See pricing.
Related resources
Connect Stripe and eClinicalWorks
Tell us where patients pay through Stripe and how your billing team posts those payments today. A Clarity business analyst will map the posting route, the account reference and the reconciliation with you before anything is built.
Book a demo