Developer docs Security & compliance Live demo
Try the demo

Partners

The half of the conversation you currently decline

If you host and support OpenEMR, your customers already ask you for online booking, reminders that behave, and referral tracking. Today the answer is a custom quote or a polite no.

The programme

What a partner gets

Your name on it

Brand resolved by hostname, so your clinics see your product name and your support address — on the sign-in page, before anybody has logged in.

Deliberately a fixed set of brand fields rather than free CSS. A reseller able to inject styling into a page showing patient records could inject rather more than styling, and every clinic on that host would be exposed to it.

Wholesale rates

Per plan, negotiated. Where you have no agreed price for a plan, list applies — a plan is never free by omission because somebody forgot to price it.

One invoice a month

Every clinic you sell, on one document, numbered without gaps. Suspended workspaces are not billed to you; a clinic on no plan is left off with a note rather than billed at zero.

A console of your own

Your clinics, their plans, what you owe. Commercial facts only — a partner session never points at a clinic's database, so there is nothing inside a practice for it to reach.

The constraint

What a partner does not get

Access to any patient record, in any clinic, ever. This is structural rather than a permission we grant carefully: signing in as a partner establishes no clinic context at all, so there is no database connection for a query to run against.

That is a constraint on you, and it is also the sentence that makes your customers comfortable buying it through you.

Structural, not procedural

  • A partner session establishes no clinic context
  • There is no database connection for a query to use
  • Nothing to misconfigure, and nothing to switch on by accident

The fit

How it fits what you already sell

You keep hosting the EMR. You keep the help desk, the forms work and the migrations. This adds a recurring line to accounts you already have, and the setup is one API credential — not a change to any installation you maintain.

For the clinic, one supplier and one bill. For you, the answer to the question you are already being asked.

You keep selling

  • Managed hosting and the uptime promise
  • Patching and the help desk
  • Custom encounter forms and templates
  • Migrations off legacy systems
  • Training

We add one recurring line, and touch none of it.

Talk to us

Bring your hardest customer

We would rather have ten partners who understand the limits than a hundred who discover them. Bring your hardest customer and we will tell you honestly whether this helps them.