What is the eHealth doctrine?
A corner stone of the roadmap for digital health, the Doctrine sets out the levers pulled by the State to regulate the eHealth ecosystem.
It defines the technical and urbanisation frameworks all eHealth professionals must conform with by 2025.
The Doctrine was created to support the unity of health structures and to stimulate innovation.
The eHealth Doctrine: a short introduction
Discover the eHealth Doctrine, its role in accelerating the digital transition and all the structuring services it integrates. We are here to guide you through them.
The doctrine is part of a co-building and collective work process to nurture a close bond between the ANS and you.
The eHealth roadmap
The eHealth doctrine in numbers
575 Participants in the 2021 webinar sessions
Themes of evaluation and referencing
Several key referential texts, as well as procedures of evaluation and certification, help you measure the conformity level of your digital solutions. They are opposable by ministerial ruling and their guidelines must be followed by all players in the eHealth ecosystem.
Conform to regulation and boost the development of your solutions on Convergence
You may use the Convergence platform to:
- submit your applications for referencing procedures with the ANS (the Health Ségur, My Health Space referencing, certification of digital medical devices);
- check maturity average ratings, evaluate the maturity of your solutions, promote your level of maturity with your clients and prospects;
- guide you through the different processes;
- create a roadmap to reach the conformity goals set out in the Doctrine;
- access a library of questionnaires on maturity and the requirements set out in the referentials.
The Convergence platform in numbers
444 registered members
693 products created
1350 users of Convergence
3 Steps to evaluate your solution on Convergence
Add a product or select a product you have already created, and link it to the evaluation and projection module.
Evaluate your product based on the eHealth Doctrine themes: you answer questionnaires about interoperability, security and urbanisation.
Make the projection of your product to define a roadmap. You anticipate deadlines for your development to reach the level recommended by the eHealth Doctrine.
The ANS provides you with all the documentation you need to use Convergence
FAQ on self-evaluation
The ANS answers your most frequent questions about self-evaluation.
To initiate the process, click on Add a product. A product identification and a product qualification questionnaire invite you to register:
- the name of the product, its versions, its identification number (NIL number, issued by the CNDA), its description and its certifications;
- technical or functional specificities;
- the referencing process you wish to apply for when you finish creating the product.
The qualification questionnaire specifies technical and functional features and customises the maturity questionnaires you will have to fill in later during the application process.
When you submit the identification and qualification questionnaires, the product is created. The platform will then ask you to select the evaluation module you wish to register the product in. You may also add a product into a module from the product page or from the module’s presentation page.
The accountability referential defines the means useable for:
- tracing the actions done on a health IS;
- guarantee the value of each registered action;
- control the use of this health IS.
The eHealth doctrine identifies several data directories, each with a specific target:
- the extended RPPS (or RPPS+) to identify each physical person in their role as a health professional (all types of professionals or assistants in the sector);
- the revised FINESS(or FINESS+) to identify each moral person in the health sector (all establishments or judicial entities in the sector);
- the ROR to describe the extend of the health offer within a facility or establishment (specialties, capacity, etc.).
To start completing the platform, it is necessary in the first place to identify a “pilot” person who will be responsible for the completion operations. The pilot will list the products, which need to integrate the entry perimeter and the list of resources needed - they can be product owners, technical experts, functional experts...
Although the questions have been contextualised, some knowledge of health IS interoperability, security and the main goals of the eHealth doctrine is a prerequisite.
Some time may be allocated to organise group questionnaire readings. From the completion of a first product, the questionnaire reading will be useful to identify topics that are under control and topics that need to be addressed.
Then, the pilot can organise punctual meetings in order to follow the project’s completion progress, make sure the answers are coherent and share experts’ feedback.
There are two types of profile :
- Administrator (“Responsable”) : this profile is either for the company’s social representative, or for the person authorised by the social representative. They are authorised to add new contributors, create products, and grant rights to contributors from their company;
- Contributor (“Contributeur”) : authorised to create accounts for other users, to create products and to answer questionnaires, within the limit of the permissions they are granted.
Access permissions are granted to contributors in order to access questionnaires for products that have already been created on the platform and the questionnaire relating to the global strategy.
Contributors without rights to validate questionnaires may only register draft answers for the questionnaires they have access to.