Skip to content

Partner program

What partners get today.

Built with partners close to clinics.

Technical access first. The commercial terms are being defined with our first partners.

Three things you can use now

The parts of the platform a partner works with from the first week.

  1. APIs

    Documented APIs and API tokens

    Partners integrate through the FHIR R4 REST API and the documented REST and streaming APIs. Machine-to-machine API tokens let a partner service call the platform on its own, without a person signed in, and role-based access control sets what each token may read or change. FHIR R4 is an open standard, so the data you exchange with Dudoxx follows a model that other clinical software already understands.

  2. Sandbox

    A tenant of your own to test in

    The tenant provisioner sets up a clinic as its own tenant, and each clinic's data is isolated. For a partner, that means a place of your own to build and test against the platform before any real clinic is involved. Your test tenant and a live clinic stay apart. When an integration is ready, the same provisioning brings a real clinic onto the platform as a tenant of its own.

  3. Branding

    Per-tenant branding

    Per-tenant branding lets each clinic carry its own name, colours and logo inside Dudoxx. For a partner who serves several clinics, every clinic keeps its own look while the platform underneath stays one and the same. Branding is a setting of the tenant, so a clinic that changes its look does not need a different version of the software, and a partner does not maintain one copy per customer.

Want technical access?

Apply, and tell us what you plan to build.