Medistory relies on a technical ecosystem that connects user accounts, the EtherEgo platform, and the synchronization of medical data. Understanding how these components work together allows for time savings during the initial login and enables users to fully utilize the software’s features on a daily basis.
Technical prerequisites for connecting to Medistory without issues
The majority of connection difficulties reported by practitioners do not stem from the software itself, but from a poorly prepared environment. Before even creating an EtherEgo account, three conditions must be met.
You may also like : How to choose between a thumb lock and a key lock for your security?
- A recent and up-to-date browser: Safari, Chrome, or Firefox in their latest version. Older versions of Safari on unupdated macOS cause SSL certificate errors when accessing the EtherEgo platform.
- An active mobile phone associated with the account: SMS validation is mandatory during registration. Without a valid mobile number, the process halts at the security step.
- A stable internet connection at the time of initial synchronization: Medistory then works offline for consulting records, but the first synchronization requires a reliable network access.
A rarely documented point concerns the office’s firewall. Some professional routers block the ports used by EtherEgo for synchronization. Checking the network filtering rules before the first attempt avoids considerable time loss.
For a deeper understanding of the identification process, a detailed guide is available on Medistory and your account on Guide Seniors, which describes each step of the registration form.
See also : How to Easily Access Reliable and Up-to-Date Financial Information Online
EtherEgo account and Medistory access: what truly connects them
EtherEgo is not just a simple login portal. It is the identity layer that authenticates the user across the entire Medistory suite. A single EtherEgo identifier provides access to all modules: patient records, calendar, billing, secure messaging.
The EtherEgo registration form is broken down into several successive steps: title, profession, office address, creation of login credentials, and then validation via SMS code. Each step must be fully completed before moving on to the next.
Difference between EtherEgo identifier and local Medistory session
The EtherEgo identifier is used for cloud synchronization and access to community tools. The local session on the Medistory application remains active even without an internet connection. This architecture allows for the consultation and modification of patient records while on the go or during home visits.
However, any changes made offline will only synchronize upon reconnecting. The data remains on the device until synchronization is completed, raising the question of backup in case of device loss or failure.
Medistory features available from the first connection
Once the EtherEgo account is activated and the initial synchronization is complete, the software provides access to a set of modules without additional configuration. The table below summarizes the features available immediately and those that require setup.
| Feature | Available upon connection | Configuration needed |
|---|---|---|
| Consultation of patient records | Yes | No |
| Calendar and appointment management | Yes | Customization of time slots |
| Billing (ExpressVitale) | No | Configuration of Vital card reader |
| Prescriptions (LAP Claude Bernard Bank) | Yes | No |
| EtherEgo community tools | Yes | Selection of prevention programs |
| Secure messaging between peers | Yes | Adding contacts |
| Voice AI Loquii | No | Specific activation |
The patient record is the central module. It displays a synthesized profile of the patient upon opening: history, ongoing treatment with dosages, biometrics. Abnormal values are visually highlighted, speeding up reading during a quick consultation.
Customization of consultation templates
Medistory allows for the creation of forms and prescription templates tailored to each specialty. A dermatologist does not use the same fields as a psychiatrist or a general practitioner. This customization is done once and replicates across all devices synchronized via EtherEgo.
The integrated medical glossaries and dictionaries (notably the Claude Bernard database for medications) work offline once downloaded during the initial synchronization.
European regulatory obligations and their impact on your Medistory account
Practitioners using medical software that handles health data are directly affected by several regulatory frameworks currently in force. The GDPR remains the foundation, but the European AI Act adds progressive obligations between 2025 and 2027.
Since February 2025, prohibitions on certain AI practices deemed to pose unacceptable risks are in effect. The obligations for AI literacy, which require providers and professional users to understand how the systems they deploy work, also apply.
For decision support modules integrated into software like Medistory (for example, the voice AI Loquii), substantive obligations will become fully applicable starting in 2026-2027: AI risk management, data governance, transparency, human oversight, and technical robustness. These requirements are cumulative with the Medical Devices Regulation (MDR).
What this changes for the user on a daily basis
In practical terms, medical software publishers will need to upgrade their technical documentation, logging mechanisms, and user information procedures. For the doctor connected to Medistory, this will translate into updates to terms of use and potentially new validation steps when activating modules that utilize artificial intelligence.
The management of patient records and medical data remains subject to the same principles of minimization and security imposed by the GDPR, but the AI Act adds an additional layer of traceability for any automated processing.
The Medistory account via EtherEgo remains the single entry point to all these features. Properly configuring the technical environment from the start, understanding the distinction between local session and cloud synchronization, and keeping up with European regulatory developments are the three key areas that determine effective long-term use of the software.