Hospital Telemedicine Software in France: 2026 Comparison and Selection Criteria

Which telemedicine software should a hospital choose? There is no single best hospital telemedicine software in 2026: the right choice depends on the clinical act the hospital wants to structure first. For hospital-to-community tele-expertise (asynchronous specialist opinions) and virtual tumor boards, platforms such as Rofim, Omnidoc, M-Covalia or Enovacom (formerly Nomadeec) are built for the job. For nurse-assisted teleconsultation with a real physical exam (12-lead ECG, auscultation, vital signs) from a ward, a satellite site or a partner nursing home, you need software paired with connected medical devices, such as Parsys or MedConnect. Either way, the selection criteria for a hospital stay the same: certified health-data hosting, EHR and patient-administration interoperability, a hosting model your IT team approves, tele-expertise workflows, and hardware.
This comparison focuses on vendors serving French hospitals, where certified health-data hosting (HDS), the national patient identifier (INS) and the national shared record (DMP) shape every procurement. The criteria translate directly to US and international buyers: replace HDS with your own hosting and privacy requirements (for example HIPAA and a BAA), and DMP/INS with your HIE and patient-matching rules.
2026 comparison: telemedicine software for hospitals in France
The table below only reflects what each vendor states on its own public website. Where a site does not say, we write "Not stated". That does not mean the feature is missing, only that it is not published.
| Solution | Acts covered | HDS hosting | Interoperability (as stated) | Connected devices / assisted teleconsultation | Hosting / on-premise | Published price |
|---|---|---|---|---|---|---|
| Rofim | Tele-expertise, virtual tumor boards (e-RCP), teleconsultation, assisted teleconsultation, remote surgical assistance, messaging. Remote monitoring: not stated | Yes ("HDS-certified host") | 10+ hospital EHRs interfaced, patient administration, PACS, ultrasound systems; HL7/FHIR: not stated | Assisted teleconsultation compatible with "most connected devices on the market" | HDS host; on-premise: not stated | Hospitals: quote, from 5 physicians. Free individual tier; Premium from €19/month |
| Omnidoc | Tele-expertise, virtual tumor boards, teleconsultation (scheduled, on-demand, assisted). Remote monitoring: not stated | Yes ("HDS server") | Hospital systems: scheduling, EHR, patient administration; national services (RPPS, Pro Santé Connect, INS, Carte Vitale); HL7/FHIR: not stated | Not stated | "No installation or interfacing" required; on-premise: not stated | Free for individual use; organizations on quote; listed on the CAIH ELODI purchasing framework |
| M-Covalia (Docaposte Santé) | Teleconsultation, tele-expertise, remote follow-up, remote case meetings | Yes ("HDS, GDPR") | "Interoperability" included in every plan; standards: not stated | Not stated | "Sovereign" SaaS; on-premise: not stated | Quote (per user, per care pathway or per specialty network) |
| Enovacom Nomadeec (Enovacom) | Teleconsultation (including assisted), tele-expertise with built-in tumor-board module, teleradiology, emergency telemedicine and EMS dispatch | Yes ("ISO 27001 (HDS certification)") | EHRs, patient-administration interfaces, national ANS services (secure messaging/DMP, INS); HL7/FHIR: not stated for the platform | ECG, stethoscope, otoscope, dermatoscope, portable ultrasound; interfaces with multiparameter monitors | "Sovereign" environment (Orange); on-premise: not stated | Not stated |
| Parsys | Teleconsultation, tele-expertise; tumor boards listed among video use cases. Remote monitoring: not stated | Yes ("HDS cloud or on-site hosting") | "Based on open standards and technologies"; standards: not stated | 40+ integrated devices; own hardware (stations, cart, Télécardia ECG) | HDS cloud or on-premise | Not stated |
| MedConnect | Teleconsultation (including assisted), native tele-expertise (optional Omnidoc connector). No tumor-board or reimbursed remote-monitoring module claimed | Yes (HDS-certified cloud in France), ISO 27001:2022 | GDT (ECG), HL7 2.x (spirometry), FHIR R4 (vital signs monitors), REST API, DMP Connect, Carte Vitale billing; hospital-system interfaces scoped with your IT team | 12-lead ECG, stethoscope, vital signs, cameras, ultrasound and more, by configuration; carts and kits | HDS cloud, on-premise or hybrid | From $195/month per system (€150 excl. VAT in France); hardware and integrations quoted |
Facts read from each vendor's public website on October 1, 2026. Spotted an error or an update? Tell us through our contact form and we will correct it.
What each solution emphasizes
Rofim: tele-expertise, tumor boards and teleconsultation on one platform
Rofim describes itself as the telemedicine platform that "centralizes tele-expertise, teleconsultation and multidisciplinary meetings". It reports 2,000 user facilities and 100,000 healthcare professionals. Its hospital plan includes teleconsultation, tele-expertise and tumor-board licenses, EHR/patient-administration/PACS interoperability, training and project management. Rofim also offers white-label deployments.
Omnidoc: hospital-to-community tele-expertise, free for referring clinicians
Omnidoc says nearly 250 hospitals use it and stresses that the tool is free for referring professionals. For the facility, it collects the data needed to push tele-expertise acts into patient administration and the EHR. Its teleconsultation module, "designed for hospitals", handles scheduled, on-demand and assisted visits with named or floating licenses. MedConnect has an optional Omnidoc connector, so the two are not mutually exclusive.
M-Covalia: four modular components
Published by Docaposte Santé, M-Covalia bundles teleconsultation, tele-expertise, remote follow-up and remote case meetings, deployable for a single facility, a regional hospital group or an entire region. Pricing is a subscription per user, per care pathway (3,000 patients per pathway) or per specialty network.
Enovacom Nomadeec: from hospital wards to pre-hospital emergency care
Nomadeec is now part of Enovacom. The platform merges Nomadeec and Nexus: Nexus for in-hospital teleconsultation, Nomadeec for community or assisted teleconsultation with connected devices. Enovacom reports 600+ interconnected facilities, including every French university hospital and comprehensive cancer center, and a tumor-board module built into tele-expertise. For emergency care, Enovacom describes itself as the "leading emergency telemedicine platform".
Parsys: telemedicine hardware plus Parsys Cloud
Parsys combines its telemedicine stations and carts with Parsys Cloud (patient record, scheduling, e-prescribing), the MedCapture Windows app (data capture from 40+ devices, offline mode) and Parsys RTC video, hosted in an HDS cloud or on-site. Its visible use cases are mainly long-term care, emergency services, maritime and remote medicine.
Healphi, sometimes listed on this topic, describes kits and software aimed mainly at independent practitioners and primary-care networks on its site, so we left it out of the hospital table.
Selection criteria for hospital telemedicine software
- Verifiable certified hosting. In France, health data must sit with an HDS-certified host. Ask for the certificate (host and scope), the hosting region and the subcontracting policy. All six solutions in the table claim HDS hosting; the difference is in the evidence and scope. US buyers should ask the same questions about HIPAA safeguards and the BAA.
- EHR, patient administration and PACS interoperability. This drives adoption and billing: synchronized appointments, patient identity, reports filed into the EHR, acts sent to billing. Ask for the list of sites already interfaced with your EHR vendor, the standard used (HL7 v2, FHIR, proprietary feed) and the connector cost. Any vendor that claims interoperability without naming a standard should be tested in a technical workshop.
- National digital-health services. In France: the national patient identifier (INS), the DMP shared record, Pro Santé Connect and secure messaging. Check which are live and which are in progress. For tele-expertise, the French national health insurer states that the specialist's report is filed in the patient's DMP when one is open (ameli.fr).
- A hosting model your IT team signs off on. Multi-tenant SaaS, dedicated instance, on-premise or hybrid: most vendors only publish SaaS. If your security policy or an international program requires data on your own servers, raise it in the RFP. Our guide to on-premise telemedicine deployment and data sovereignty covers the prerequisites.
- Tele-expertise workflows. Request lines per department, specialty questionnaires, triage, attachments (DICOM images, ECG traces), automatic reports, billing. In France, a tele-expertise act is billable up to 4 times per year, per physician, for the same patient (ameli.fr). If the opinion relies on an exam performed remotely, check that device data reaches the request, not just free text.
- Tumor boards and remote monitoring: scope them separately. Virtual tumor boards are a discipline of their own, covered by Rofim, Omnidoc and Enovacom. Remote patient monitoring has been reimbursed under standard rules in France since July 1, 2023 (ameli.fr) and is often served by condition-specific solutions. Our guide to remote patient monitoring and teleconsultation software for hospitals goes deeper.
- Hardware and assisted teleconsultation. When a nurse or technician is with the patient (a ward without the specialist, a satellite site, an affiliated nursing home, a correctional facility), the remote physician needs a 12-lead ECG, auscultation and live vital signs. Ask for the list of devices actually integrated (brand, model, protocol) and run a demo on your own network.
- Project delivery and total cost. Compare over 3 years: licenses (named or floating), hospital-system connectors, hardware, training and support. Check whether the vendor is listed on a purchasing framework your hospital already uses (Omnidoc, for example, states it is listed on the CAIH ELODI framework). Pilot in 2 or 3 departments before rolling out.
Where MedConnect fits (and who it is not for)
The MedConnect telehealth platform is built around the remote physical exam. A clinician at the bedside uses a cart or a kit; the remote physician receives the 12-lead ECG, auscultation, vital signs and images live, and they land in the consultation record. For a hospital, that maps to a few specific uses:
- assisted teleconsultation between a ward and a specialist at another site in the hospital group;
- links with nursing homes, satellite sites or community facilities, with a telehealth cart brought to the room;
- native tele-expertise with your own specialists, plus an optional Omnidoc connector;
- projects that require hosting on the hospital's own servers or a hybrid architecture designed with IT.
Production data flows are documented by protocol: GDT for compatible ECGs, HL7 2.x for the MIR Spirobank II Smart spirometer, FHIR R4 for AIView vital signs monitors, a REST API, DMP through the DMP Connect module, and Carte Vitale billing through Stellair. HL7/FHIR interfaces with a hospital information system are scoped and quoted with your IT team; we never assume universal compatibility. INS integration is in progress. The platform is ISO 27001:2022 certified and runs on an HDS-certified cloud in France, with regional or on-premise hosting for international projects. It is HIPAA-ready, with US deployments under a BAA. Software subscriptions start at $195 per month per system; hardware, number of sites and integrations set the total price. Go-live typically takes 2 to 4 weeks.
MedConnect is not the right choice if your priority is running oncology tumor boards or national specialty networks, rolling out a large device-free tele-expertise network with community physicians, equipping EMS dispatch, or launching a reimbursed remote-monitoring program. The specialized solutions in the table are better placed for those needs. Our carts and kits ship with a Windows computer, so the web tools your hospital already uses stay available on the same station, while MedConnect adds the connected clinical exam.
Writing an RFP? Explore the MedConnect platform and its hosting options, or book a demo built around your use cases.
Frequently asked questions
Which telemedicine software should a hospital choose? Start from the priority clinical act. For hospital-to-community tele-expertise and virtual tumor boards, platforms such as Rofim, Omnidoc, M-Covalia or Enovacom are built for it. For assisted teleconsultation with live ECG, auscultation and vital signs, choose software paired with connected devices, such as Parsys or MedConnect. In both cases, require certified hosting, documented EHR interoperability and a pilot in 2 or 3 departments.
Does hospital telemedicine software need HDS hosting? In France, yes: health data hosted on behalf of a facility must be entrusted to an HDS-certified host. Ask for the certificate, its scope and the data location. All six solutions in this comparison state HDS hosting on their websites. Outside France, apply the equivalent local rules, such as HIPAA and a BAA in the US.
What is the difference between tele-expertise, virtual tumor boards and assisted teleconsultation? Tele-expertise is an opinion requested by one clinician from another, often asynchronously. A virtual tumor board (e-RCP in France) is a remote multidisciplinary case meeting, common in oncology. Assisted teleconsultation connects the patient with a remote physician while a clinician at the patient's side uses connected devices.
Can the software integrate with our EHR? Check this first. Rofim reports 10+ hospital EHRs interfaced, Omnidoc and Enovacom describe EHR and patient-administration interfaces, and MedConnect scopes and quotes HL7/FHIR interfaces with your IT team. Ask for references at hospitals running the same EHR as you.
Can the platform run on the hospital's own servers? Among the solutions compared, Parsys (for its RTC video) and MedConnect state that on-premise deployment is possible. For the others, it is not stated on their public sites, so ask the vendor directly.
How much does hospital telemedicine software cost? Most vendors quote hospitals individually (Rofim from 5 physicians; Omnidoc and M-Covalia on quote). MedConnect publishes a subscription from $195 per month per system, excluding hardware and custom integrations. Always compare 3-year total cost, including connectors and training.
Can a hospital combine several solutions? Yes, and it is common: a tele-expertise and tumor-board platform across the hospital group, plus an assisted-teleconsultation solution with hardware for sites that see patients without a specialist on hand. MedConnect, for example, offers an optional Omnidoc connector for tele-expertise.
Ready to discover MedConnect?
Request a personalized demo and see how the platform adapts to your practice.
Request a demo