The connection to a.netsoins.com involves several technical layers that most startup guides overlook: TLS certificate management on the browser side, internal DNS resolution, and caching policy on shared tablets. Optimizing this access is not just a matter of comfort; it is a condition for the DUI to remain reliable in real-time across all workstations in the establishment.
DNS Resolution and TLS Certificate: The Blind Spots of the Netsoins Connection in EHPAD
A connection failure to a.netsoins.com almost never originates from the remote server. In most cases, the problem lies between the client workstation and the network gateway of the establishment.
The first point to check is the local DNS resolution. Many EHPADs use an internal DNS server provided by the operator’s box or a dedicated firewall. If this server caches an expired response or redirects to a captive portal (common after a network restart), the browser displays a certificate error or a timeout without an explicit message.
Configuring a reliable secondary DNS on each workstation and tablet (for example, via the DHCP of the local network) reduces this type of incident. On Android tablets used in care carts, the DNS may be locked by the MDM (Mobile Device Management): intervention is then required at the level of the MDM’s network configuration policy, not on the tablet itself.
The second blind spot concerns the TLS certificate of the platform. Netsoins operates over HTTPS with a periodically renewed certificate. On workstations where the root certificate store is not up to date (outdated Windows machines, old tablets), the renewal of the server-side certificate triggers a security alert. The reflex to “override” the warning compromises the chain of trust and violates HDS hosting requirements.
Properly configuring the connection to a.netsoins.com for ehpad therefore requires keeping the operating system of each terminal up to date, including the tablets at the end of the hallway that no one thinks to update.
Cache Policy and Shared Sessions on Care Tablets
In EHPADs, the same tablet passes between several caregivers during a shift. This operation raises a concrete issue: session persistence in the browser.
Netsoins manages authenticated sessions server-side with a session token stored in a cookie. If the browser retains this cookie after a user logs out, the next caregiver can access the resident’s file under the previous user’s identity. Beyond the GDPR risk, this distorts the traceability of actions in the DUI.
- Enable automatic cookie deletion upon browser closure, or configure a default “private browsing” profile on shared tablets.
- Ensure that the session timeout on the Netsoins side aligns with the actual duration of a care round (usually configurable in the administration interface).
- For tablets managed by MDM, deploy a browser cache cleaning policy at each screen lock.
These settings fall under the responsibility of the network administrator or IT service provider, not the caregiving teams. Documenting the procedure in the establishment’s information system security protocol ensures its sustainability during changes in technical staff.
National Health Identity and DUI Netsoins: What the Connection Must Allow to Verify
Accessing Netsoins is not limited to displaying the care plan. The National Identity Vigilance Reference Framework (RNIV), whose “Common Principles” version dates from December 2024, requires establishments to verify the quality of each resident’s digital identity in the DUI.
In practice, each resident file must be referenced with the National Health Identity (INS). When a caregiver logs in and opens a file, the software must allow verification of the INS status (qualified, provisional, erroneous). A degraded connection (slowness, timeout, partial synchronization) can mask an identity vigilance alert and allow un-reconciled identities to coexist.
This point is even more critical as the ESMS Digital program pushes establishments towards interoperability with Mon espace santé and MSSanté. Checking the status of INS exchanges after each update of Netsoins should be included in the maintenance checklist, alongside data backup.
Identity Discrepancies: A Network Symptom Often Ignored
A discrepancy between the locally stored INS and that returned by the INSi remote service may stem from a synchronization issue related to an unstable connection. Before manually correcting the identity in the file, it is essential to ensure that the last synchronization was successful. The exchange log (accessible in the Netsoins administration interface) allows for this verification.
Netsoins-Omnidoc Integration: Ensuring Tele-expertise Without Double Entry
The integration between Netsoins and Omnidoc aims to eliminate double entry during tele-expertise requests. The principle: the data from the resident’s file is transmitted directly from the DUI to the Omnidoc platform, without manual re-entry by the coordinating physician.
For this flow to work, the connection to a.netsoins.com must allow outgoing API calls to the Omnidoc servers. However, some EHPAD firewalls block unreferenced outgoing connections by default. The result: the “tele-expertise” button in Netsoins returns a silent error, and the physician ends up re-entering the data in Omnidoc, negating the benefit of the integration.
- Request from the publisher the list of domains and ports to allow in the firewall for the Omnidoc integration.
- Test the API connection from a care workstation (not just from the administrative workstation, which may have different network rules).
- After each firewall or network firmware update, restart an end-to-end test on tele-expertise.
The actual use of this feature deserves regular monitoring. Checking how many tele-expertise requests actually go through the integrated flow, and how many are manually re-entered, provides a concrete measure of the quality of the connection and network configuration.
The connection to Netsoins is not a fixed asset after the initial deployment. Each software update, each change in network hardware, each certificate renewal can jeopardize access stability. Integrating a functional connection test (access to the DUI, INS synchronization, Omnidoc flow) into the periodic maintenance of the establishment remains the most reliable way to avoid silent regressions.
