I'm a medical centre
Want to connect external software to your GipoNext practice management system? This page explains how it works, what to expect, and your role in the process.
Existing integrations
Before starting a new project, check whether an integration already exists for your use case.
- MioDottore — GipoNext is natively integrated with MioDottore (DocPlanner). If you use MioDottore for online booking, agenda and appointment sync is already active without extra development.
- RIS/PACS — GipoNext integrates with RIS/PACS systems for order management and diagnostic report reception.
- Vendors already integrated — several software vendors have integrated with GipoNext via the APIs documented here. Ready-made solutions may cover your needs.
💡 Ask your Customer Success
Your Customer Success contact knows the integration ecosystem.
Contact them to check for existing integrations compatible with your use case before involving an external integrator.
What are APIs, in simple terms
APIs are a "bridge" that lets two systems exchange data automatically and securely.
In practice: a trusted integrator uses this bridge to connect their software with GipoNext, without you manually copying data between systems.
💡 Concrete example
A lab can send reports directly into GipoNext, or a booking portal can create appointments in your clinic's agenda, all automatically.
What you can and cannot do
The APIs cover a specific set of operations: patients, agendas, appointments, reports, invoices, and more. Not everything in the GipoNext UI is available via API.
This is an advantage: you and your integrator know from the start what is feasible, with no surprises once the project is underway.
⚠️ Important
Custom API features cannot be requested. Always verify at the outset that project requirements fall within what is documented.
Your role: what you need to do
The integration project is managed by your integrator. Your role is coordination and activation:
- Introduce the integrator to GipoNext — communicate who they are and that they want to integrate.
- Request developer account activation — GipoNext will activate a technical account for your integrator (not access to your data; it only registers the software).
- Provide data access if needed — when the integrator is ready to work with real data, you can request a dedicated temporary user account.
💡 No technical work required
All technical work (development, configuration, testing) is the integrator's responsibility. You define objectives and authorize access.
Two distinct things: software and person
For data security, the system requires two separate checks:
| What | Purpose | Who activates |
|---|---|---|
| Developer account | Lets the integrator register their software | You request it; GipoNext activates it |
| Access user account | Lets a person access your clinic's data | You request it via ticket |
These are independent: the developer account does not grant access to patient data. Data access always requires a user account with the right permissions.
Development and testing without touching your data
Your integrator can develop and test using a sandbox environment with fictitious data. Real clinic data is not needed until final validation.
This means:
- your real data stays protected throughout development;
- production error risk is reduced;
- you do not share health data with third parties during testing.
Next step
Share project objectives with your integrator and ask them to read Getting started: they will find everything needed to begin.