Does Medaris hold patient data?

No. Medaris holds zero patient data by design: no patient records, admissions, appointments or patient billing. The scope is the equipment estate, works, supply chain, capacity, stock and the evidence around them.

Is Medaris a cloud service?

No. Medaris runs on a single server inside the hospital's own walls, and its AI features run entirely inside the hospital network with no external calls. Cloud is opt-in for ministries that prefer it, but the default is sovereign on-premises.

Why one platform instead of stitching several?

Because hospital estate teams already work across equipment manuals, paper logs and multiple spreadsheets. Medaris keeps the scope focused on operations, maintenance, reporting and audit.

Is Medaris GDPR / RGPD compliant?

Medaris is built RGPD-aligned: deployment stays inside the host country, and the product holds no patient data at all, so the hardest data-protection questions never arise. For OHADA countries, Medaris follows OHADA-compatible practice.

How is the backup handled without cloud?

The architecture can include a local backup machine, documented recovery procedures and cold-copy rotation. The exact recovery model is agreed with the integrator and ministry.

Sovereignty

On-prem AI by default.
In ministry colours.

On-premises deployment is the default. Core operations and AI-assisted workflows run on a hospital server, with local backup options, ministry branding, and exportable data. Cloud hosting is available only when requested.

Sovereignty

On-prem AI by default.
Cloud only if requested.

Medaris is configured to run inside the facility, with documented backup and restart procedures. Operational data and every AI-assisted workflow stay under local control without routine outbound connectivity - and no patient data ever enters the system.

On-premises server

Hospital-controlled deployment

No routine outbound connection

Core workflows run locally

Restart procedure

Documented recovery steps

Local backup option

Second room or agreed backup site

Ministry branding

Crest, colours and partner logos

Equipment import

OEM CSV during handover

Staff handover

Train-the-trainer sessions

Hospital technician using a tablet connected to a local on-premises workflow. — No outbound internet

Hospital server

Backup room

Ward tablets

Quarterly pack

What Medaris talks to

Designed to integrate carefully.
Open records, bounded scope.

Imaging systems - Year-2 interface planning can cover worklists and report references for MRI, CT, X-ray and ultrasound.
Other hospital software - Medaris provides CSV and XLSX exports of the operational registers for downstream systems; clinical integrations are separate programme decisions.
National health reporting - Year-2 planning can include aggregate indicators for the national health information system.
Plain exports - Excel-friendly files for your ministry analysts, your way.

Deployed with the equipment packageOn-prem AI supportOn-premises by defaultWhite-label per siteZero patient dataRGPD-alignedOHADA-compatibleSource-code escrow availableExport-credit report templatesDeployed with the equipment packageOn-prem AI supportOn-premises by defaultWhite-label per siteZero patient dataRGPD-alignedOHADA-compatibleSource-code escrow availableExport-credit report templates

If you build hospitals

Request a Medaris demo.

A focused walkthrough covers programme scope, handover timing, on-prem AI boundaries, reporting evidence and buyer roles.

Request a demo

Or write to contact@medaris.fr

Medaris · Paris, France

On-prem AI by default. In ministry colours.

On-prem AI by default. Cloud only if requested.

Designed to integrate carefully. Open records, bounded scope.

Request a Medaris demo.

On-prem AI by default.
In ministry colours.

On-prem AI by default.
Cloud only if requested.

Designed to integrate carefully.
Open records, bounded scope.