When a nursing assistant enters a care procedure in NETSoins at 7 AM and the attending physician checks the same information on Mon Espace Santé at 9 AM, traceability works. In many DomusVi residences, we are not there yet. The feeding of the DMP from the care software remains partial, identities are not all qualified, and the 2026 deadline of Ségur wave 2 is approaching with stricter requirements than often thought.
Qualified INS in NETSoins: the technical lock that teams underestimate
Before discussing the DMP, we hit a prerequisite that silently blocks the chain: the national health identity. Each resident must have a qualified INS via the INSi tele-service, and not just a number copied from an old paper file.
On the ground, feedback varies on this point. Some DomusVi residences have qualified all their residents in a few weeks, while others have been stuck with provisional identities for months. The issue is not NETSoins itself (the module exists), it’s the upstream organization: who initiates the INSi request, who checks the match with the identity document, who corrects the anomalies.
A concrete process that works: the IDEC identifies residents without a qualified INS via a NETSoins export, the medical secretariat initiates batch requests, and the nurse validates the match at the next consultation. If this circuit is not formalized, identities remain in “retrieved” status without ever moving to “qualified,” and no document can be sent to the DMP.
Useful resources can be found to structure this step, notably through the Netsoins DomusVi training on Senior News which details the verification points on the configuration side.
Feeding the DMP from NETSoins: what Ségur wave 2 really imposes
The Ségur wave 2 texts for medico-social DUI no longer just encourage feeding the DMP. They make it a condition of compliance, with technical audits planned for publishers and establishments. Specifically, NETSoins must be able to automatically send several types of structured documents to Mon Espace Santé:
- The resident’s medical summary, updated with each significant change in the care plan
- Hospitalization or specialized consultation reports, when they are entered or digitized in the DUI
- The list of current medications, synchronized with the active care plan in NETSoins
The common trap: the team thinks they are feeding the DMP because they check a box in NETSoins, but the document sent is an unstructured PDF that the attending physician cannot read or use in their own software. Ségur compliance requires structured flows in CDA format, not just simple attachments.
To verify if your configuration is operational, you can ask the IT referent to test sending a summary document to the DMP of a consenting resident, then check on Mon Espace Santé that the document displays correctly and that the data is readable by section.
NETSoins traceability and HAS evaluation: the link that IDECs must anticipate
The HAS evaluation reform for ESSMS has changed the game for IDECs and directors. We are no longer talking about a one-time audit every five years with a binder of protocols. HAS now expects a structured annual traceability of improvement actions, with evidence in the resident file, validated protocols, and documented clinical indicators.
NETSoins already contains the raw material: targeted transmissions, care plans, prescription history, fall and pressure ulcer tracking. The problem is that this data often remains siloed in tabs that no one cross-references.
A telling example: if a resident falls three times in two months, NETSoins records each event. But if no one documents in the software the reassessment of risk, the modification of the care plan, and the report from the multidisciplinary meeting, the HAS evaluator will not find evidence of an improvement circuit. Traceability only matters if it tells a coherent clinical story, not a series of isolated incidents.
For the DMP link to work in this context, the summary document sent to the attending physician must reflect these adjustments. A community doctor who opens Mon Espace Santé and finds a summary document dating from admission, with no updates despite three falls, is exactly the signal that HAS seeks to eliminate.
Timeline and concrete checkpoints before the end of 2026
There is a tendency to postpone this type of project because it seems technical. In practice, three actions are enough to unblock the situation in most DomusVi residences:
- Audit the rate of qualified INS in NETSoins and address identities that remain in provisional status, prioritizing residents with frequent hospitalizations
- Test the actual sending of a structured summary document to Mon Espace Santé, check its readability on the recipient’s side, and correct the configuration if the document is sent as a raw PDF
- Formalize in NETSoins the update circuit for the summary document (who writes, who validates, how often), in connection with the HAS evaluation schedule of the establishment
Ségur wave 2 leaves no room for interpretation regarding the automatic feeding capability of the DMP. Establishments that have not validated these structured flows risk losing their compliance and, with it, access to funding related to digital health.
Traceability with NETSoins and the DMP is not an IT project to delegate to a provider. It is an organizational circuit that involves the IDEC, the coordinating physician, the secretariat, and management. DomusVi residences that are making progress are those where someone has taken ownership of the subject, tested the flows, and corrected what was not working before an auditor did it for them.