Blog

Actualités

Summary
Actualités

Ségur Digital Health Wave 2: what hospitals must do (2026-2027)

Ségur Digital Health Wave 2 for hospitals: DPI and PFI devices, the 2026-2027 calendar, funding, and how to get your EHR ready.

The essentials in 30 seconds

QuestionShort answerWhat to remember
What is Ségur Wave 2?The national program that funds hospital software to reach a new interoperability and security bar.It is about circulating data, not filling forms.
Who is concerned?Hospitals and their software vendors, through the DPI and the PFI.Two devices in the Hospital corridor.
Key deadline?Complete proof of compliance closes 31 March 2026; referencing until 30 June 2026.Miss the window, miss that funding cycle.
Who pays?Under the SONS model the State funds the referenced version through the vendor.The facility does not pay directly for that scope.
Main goal?Feed and consult the DMP from the EHR, generalise MSSanté, secure the INS.The patient at the centre via Mon espace santé.
How to prepare?Confirm your vendor is referenced and map the INS, MSSanté and identity prerequisites.Compliance only pays off if teams use it.

Introduction

Hospital data still gets re-entered, faxed, or lost between software that does not talk to each other. Wave 2 of the Ségur du numérique en santé exists to end that, by funding hospitals so their tools finally exchange information securely and with the patient.

Galeon has built an AI-native EHR (DPI) hand in hand with caregivers since 2016. It is used in 19 hospitals including 2 university hospitals (CHU), covering more than 3 million patient records and over 10 000 caregivers, which gives a concrete read on what Wave 2 demands in real wards.

One thing to remember: Ségur Wave 2 is not a compliance formality, it is the moment hospital data becomes genuinely shareable.

What exactly is Ségur Wave 2?

It is the second stage of the Ségur du numérique en santé, steered by the Agence du Numérique en Santé (ANS). After Wave 1 connected the foundations, Wave 2 raises the bar on real use, richer feeding of the DMP, and stronger identity and security. Funding follows the SONS model (Systèmes Ouverts et Non Sélectifs): the State pays the vendor for a referenced version, so the facility does not carry that upgrade cost directly.

What changes for hospitals: DPI and PFI?

The Hospital corridor rests on two devices. The DPI (the electronic health record) must let professionals consult Mon espace santé, feed the DMP with the right documents, use the national health identity (INS), and exchange through MSSanté. The PFI (Interoperability Platform) is the layer that routes and standardises those exchanges across the facility. A modern EHR treats interoperability as native rather than as an add-on.

What is the 2026-2027 calendar?

The regulatory calendar was updated by decree. For the Hospital corridor the main milestones are: end of the complete proof-of-compliance submission on 31 March 2026, referencing procedure open until 30 June 2026, funding and advance requests until 23 September 2026, end of the Ségur service delivery on 22 June 2027, and final balance requests until 28 September 2027. The ANS has already adjusted these dates once, so always check the current official version.

How do you prepare your EHR for Wave 2?

Confirm your vendor is engaged in the Wave 2 referencing and can deliver the referenced version within the calendar. Map your prerequisites: INS qualification, MSSanté, professional identity, and DMP access from the software. Then plan adoption, because a compliant version only creates value once clinicians actually use the new flows in daily care.

CriterionLegacy compliance approachInteroperability-native EHR (Galeon)
DMP consultationSeparate portal, extra loginConsulted inside the care workflow
DMP feedingManual, document by documentFrom the record, structured
National identity (INS)Added late, often patchyBuilt into the patient flow
MSSanté messagingBolt-on moduleIntegrated exchange
Data structuringFree text, hard to reuseStructured, validated by caregivers
HostingVaries by contractHDS certified, ISO 27001:2022 aligned
Upgrade pathHeavy version migrationsContinuous, cloud-based updates

Limits and challenges to be aware of

  • Referencing is not adoption: funding rewards a compliant version, but value depends on clinicians using the new flows.
  • Deadlines are firm: a missed submission window can push funding out of reach for that cycle.
  • Prerequisites stack up: INS, MSSanté and identity building blocks must be in place for DMP access to work end to end.
  • Dates evolve: the ANS has already adjusted the calendar, so the official version is the only reliable reference.

FAQ

Is Ségur Wave 2 mandatory?
The referencing and funding are voluntary for the facility, but the underlying obligations such as INS, DMP feeding and MSSanté are part of the national framework and increasingly expected.

Who actually pays for the software upgrade?
Under the SONS model the State funds the referenced software version through the vendor, so the facility does not pay directly for that defined scope.

What is the difference with Wave 1?
Wave 1 connected the foundations. Wave 2 focuses on real use, richer document feeding of the DMP, and stronger identity and security.

What if my vendor is not referenced in time?
You may miss the funding window for that cycle, which is why confirming your vendor roadmap early matters.

Does Wave 2 cover access to the DMP?
Yes, consulting Mon espace santé and feeding the DMP from the EHR are central objectives of the Hospital corridor.

In summary

Ségur Wave 2 is less about paperwork than about making hospital data circulate securely, with the patient at the centre through Mon espace santé. Galeon is an AI-native EHR (DPI) built with caregivers since 2016, HDS certified and aligned with ISO 27001:2022, and designed around interoperability, which is exactly the posture Wave 2 rewards. Facilities that treat Wave 2 as a care-quality project rather than a compliance box will get the most out of it.

Want to know more about our smart EHR ?

Book a demo
Read next: smart EHR vs traditional EHR, why hospitals are switching to AI.

Sources

 

Ils nous font confiance

Logo du Centre Hospitalier Intercommunal Toulon La Seyne-sur-MerLogo du Centre Hospitalier Sud Francilien (CHSF)Logo blanc du GHNE (Groupement Hospitalier Nord Essonne) sur fond transparentLogo du CHU de RouenLogo du CHU Caen Normandie