International telemedicine: deploying an on-premise solution for a ministry of health

Deploying international telemedicine for a ministry of health has nothing in common with equipping a physician's office in France. The constraints are radically different: absent or intermittent connectivity, data sovereignty requirements, multilingual interfaces, patient volumes exceeding a hundred a day, and often no existing IT infrastructure at all.

This guide draws on real deployments in New Caledonia, Côte d'Ivoire, Saudi Arabia, and Switzerland to explain how MedConnect adapts to each international context.

The 3 challenges of an international deployment

1. Connectivity

In many countries, internet connectivity is neither stable nor fast. In rural West Africa, the network may be limited to intermittent 3G. On Pacific islands, satellite links add latency. And in high-volume public health settings (pilgrimages, screening campaigns), the bandwidth available per station may be insufficient for real-time video.

MedConnect solves this with its asynchronous mode: the nurse performs the full exam with the connected devices, the data is stored locally, then synchronized when a connection is available. The physician reviews the data later. In Côte d'Ivoire, this model made it possible to screen 150 patients a day as part of a diabetes screening program (Dignité Sociale medical center, funded by Bpifrance).

2. Data sovereignty

Ministries of health often require health data to stay on national soil. Not in a cloud abroad — on servers physically located in the country, under local jurisdiction.

MedConnect offers a complete on-premise deployment: local servers, zero cloud dependency, locally managed encryption keys. Saudi Arabia's Ministry of Hajj chose this model for its deployment of 15 systems for pilgrim medical screening — all data stays within the local infrastructure.

3. Languages

A platform that only speaks French or English is unusable in an Arabic- or Italian-speaking context. MedConnect natively supports 4 interface languages: French, English, Arabic, and Italian. The AI scribe transcribes and generates reports in all 4 languages.

On-premise vs. cloud: why ministries choose local hosting

Most telemedicine platforms are cloud-only. That creates three problems for a country-scale telemedicine deployment:

• Data transits abroad — incompatible with local regulations
• If the internet goes down, the platform is unreachable — unacceptable for a public health service
• Operational control (updates, access, backups) sits with the vendor, not the ministry

MedConnect's on-premise deployment solves all three. The system runs on a local network with no internet connection. Updates are delivered as OTA (over-the-air) packages that the local IT team applies at its discretion. The platform runs on Linux servers with Docker containerization — standard infrastructure that a local IT team can maintain.

Asynchronous mode: 150 patients a day without a permanent connection

MedConnect's asynchronous mode is designed for low-connectivity environments. Here is how it works in practice:

1. The nurse receives the patient and creates (or retrieves) their record locally
2. They perform the exam: vital signs, blood glucose, blood pressure, and any other relevant test
3. The data is stored on the local MedConnect Hub (in development)
4. When a connection is available (even briefly), the data syncs with the central server
5. The physician reviews the data and gives their opinion

In Côte d'Ivoire, under the Dignité Sociale program, nurses use this model to screen for diabetes across 5 health districts. Blood pressure and blood glucose data are collected on site, then sent to the physician for evaluation. Volume reaches 150 patients a day.

Island deployment: 1,500 teleconsultations in New Caledonia

New Caledonia's Northern Province is an archipelago where patient transfers between islands (and to the mainland) are costly and logistically complex. MedConnect was deployed there with a full diagnostic suite, including the portable ultrasound.

The result: more than 1,500 teleconsultations performed, and a significant reduction in inter-island transfers that previously required medical air evacuations. Specialist care (cardiology, dermatology, geriatrics) is now accessible without the patient having to travel.

National health project: 60 mass-screening kits

Saudi Arabia's Ministry of Hajj ordered 15 systems for the medical screening of pilgrims during Hajj 2025. The project combines fixed modular clinics (18 m²) with mobile backpack kits for field teams.

Each kit includes: ultrasound, 12-lead ECG, vital signs monitor, bioanalyzer, connected stethoscope, otoscope, dermatoscope, thermometer, and glucometer. The software is deployed on-premise with an Arabic interface and AI-driven triage.

This deployment shows how international telemedicine can operate at scale in a demanding context: high volume, multiple languages, data sovereignty, and tough field conditions.

Training and support: how to train clinical staff locally

MedConnect training is the same regardless of the deployment country:

• Duration: one day for clinical staff (nurses, operators)
• Content: handling each connected device, using the platform, the complete consultation workflow
• Language: training is delivered in the interface language (FR, EN, AR, IT)
• Support: via Freshdesk, with service levels matched to the contract (standard or 24/7)

For large-scale projects, MedConnect offers a "train-the-trainer" program: a local team is trained in depth and becomes self-sufficient in training the rest of the staff.

MedConnect Hub: why a compact bridge changes everything

In environments with limited IT infrastructure, the MedConnect Hub is the cornerstone. It is a compact unit (under 15 cm × 15 cm × 5 cm, VESA-mountable) that:

• Connects all medical devices via 5 USB ports and Bluetooth 5.0
• Provides Gigabit Ethernet and Wi-Fi 5 connectivity
• Runs a hardened Linux with Docker containerization
• Receives OTA updates without on-site IT intervention

The Hub removes the need for a Windows PC, reduces technical complexity for on-site staff, and provides a reliable, maintained computing platform in environments where IT infrastructure is minimal. It is what makes international deployments viable without a permanent IT team.

For organizations interested in distributing MedConnect in their country, see the distributor program.

FAQ

Can MedConnect work without an internet connection?

Yes. The on-premise deployment runs on a local network. Asynchronous mode stores data locally and syncs when a connection is available. The 150 patients a day in Côte d'Ivoire are screened in this mode.

Which languages are supported?

The interface is available in French, English, Arabic, and Italian. The AI scribe transcribes and generates reports in all 4 languages.

How long does an international deployment take?

2 to 4 weeks for a standard site (configuration, hardware delivery, training). Multi-site projects (such as the Hajj, with 15 systems) follow a timeline adapted to the logistics.

Who handles on-site maintenance?

MedConnect provides remote support via Freshdesk. For large-scale projects, local distributors provide on-the-ground support. The MedConnect Hub receives OTA updates without local IT intervention.