A short list, on purpose.
Every EMR advertises two hundred integrations. Most are a Zapier trigger nobody has tested, and you find out which on the afternoon you need it. Ours are built and supported by us. Fewer connections, all of them load-bearing.
Aminova
INV-2481 · $525.00Marcus WebbOpenQuickBooks Online
Peak Vitality LLCOne-way · Aminova → booksWaitingDepth beats a long list
A logo grid is easy to print and hard to rely on. We would rather connect to five systems in a way you can trust on a Friday afternoon than list fifty that technically pass a field over. If something is on this page, it is built, tested and supported.
Each clinic connects its own accounts
Every integration is authorised per clinic, under that clinic’s own account, with credentials stored per tenant — never a shared platform key. A multi-location group can run different processors and different books per site without the connections bleeding into each other.
You can always leave
Disconnect any integration yourself, and export your data at any time without asking us. An integration that becomes a hostage situation is worse than no integration, which is why nothing essential depends on one staying connected.
Where the money moves.
Your clinic banks with one card processor, and medication is deliberately kept off that rail. Both sides of that are set up here.
- ✓Stripe — cards, memberships and recurring billing
- ✓Square — cards, memberships and in-person terminal
- ✓One or the other, never both at once, by design
- ✓Corepay — the high-risk rail medication routes to, connected in a minute
Payments
Medication charges route to Corepay automatically. How the partnership works →
Your books, without the re-keying.
Revenue, payments and refunds flow to the ledger your accountant already works in, so month-end stops being an export-and-retype exercise.
- ✓QuickBooks — connect your own company file
- ✓Xero — same, for clinics who run on it
- ✓Gusto — payroll, connected per clinic
- ✓Or export and hand your accountant a file, if you prefer
Back Office
Nothing here is required — export works without any of it.
The networks prescribing actually runs on.
Prescribing and dispensary aren’t nice-to-have connections for a clinic like yours — they’re the workflow. These are wired in rather than bolted on.
- ✓A national e-prescribing network reaching compounding and retail pharmacies
- ✓In-house supplement dispensing, with your own catalog and margin
- ✓Lab result ingest from your existing lab partner
- ✓Clearinghouse connection for clinics that bill insurance
Clinical Network
Tell us your pharmacies and lab during onboarding and we confirm each.
The honest half of an integrations page.
Things clinics ask about that we either don’t do, or do in a limited way. You will find this out eventually — better here than in month two.
- ✓No generic Zapier-style marketplace with hundreds of shallow connectors
- ✓Patient financing is a hand-off today — a full API integration is in the works
- ✓Wearables and device data are in the works, not shipped
- ✓Ordering integrations depend on which network your lab sits on
Straight Answers
If a connection matters to your clinic, ask before you sign.
How it works
Three moves, one platform.
Authorise from Settings with your own account — no keys pasted into a chat, no credentials handed to us.
Each connection is per clinic, so a multi-location group is never sharing one set of credentials.
Revoke it yourself, whenever. Nothing about your data depends on a connection staying live.
What connects today.
Your brand, one login, no stitched-together stack.
Questions
Why so few integrations?
Because we would rather five work than fifty exist. A long logo grid usually means shallow connectors nobody maintains, and you find out which on the afternoon you need one. Everything on this page is built, tested and supported by us.
Do you have an API?
Ask us. There’s no public self-serve API today, and pretending otherwise would waste your developer’s week. If you have a specific integration your clinic depends on, tell us during onboarding rather than after — sometimes the answer is yes.
Who owns the connection?
You do. Every integration is authorised under your clinic’s own account, stored per clinic, and revocable by you at any time. We never ask you to send us keys, and we don’t hold a shared platform credential on your behalf.
What if we run multiple locations?
Each clinic connects its own accounts. A group can run different processors, different books and different pharmacies per site without those connections seeing each other.
Do you integrate with wearables?
It’s in the works rather than shipped, so we haven’t put it on the list above as though it were live. Tell us which devices matter to your clinic and it shapes what we build first.
What happens if we disconnect something?
It stops syncing and nothing else breaks. Your data stays yours, export keeps working, and the clinic keeps running. No integration here is load-bearing for your ability to see patients.
See it in action.
A 30-minute walkthrough, configured for how your clinic runs.