To make sure your software complies with the guidelines required to implement INS into software, several documents are available:

Health professionals are encouraged to use MOS and NOS for three main reasons :

• enhance the interoperability of information systems by harmonising names, attributes, codes and nomenclatures;
• share the same understanding of the information, regardless of which directory or reference document it is taken from;
• facilitate the specification, analysis and conception of a project. 

The ANS offers training on MOS-NOS and the elaboration method for exchanges’ functional specs (see our Documentation section).

The illustration below gives you examples of the types of professionals using the MOS-NOS: 

Our partner, the GIE Sesam-Vitale, is here to provide you with support and answer your questions about your software project, how to integrate INSi, or solve any potential technical setbacks. 

The helpdesk is available by phone at +33 (0)2 43 57 42 88, from 9am to 12noon, and from 2pm to 6pm, Monday to Friday. You may also send an email to centre-de-service@sesam-vitale.fr.

In order to make the check lists more transparent and reduce the risk of seeing your Ségur application denied, we have published a document listing common mistakes, which is available below:

Your level of access to the ROR data depends on the nature of the data you wish to use (public/restricted) and the perimeter you wish to cover (one ROR or several ROR directories).

The ROR data in public access:

• is available as opendata since mid-2022;
• will be available directly on the national ROR with no specific procedure in early 2023.

The ROR data in restricted access (professional access):

• for one regional ROR, you must complete a request form to join the regional circle of trust and send it to the region’s GRADeS;
• for several ROR directories, you must complete a request form to join the national circle of trust and send it to the ROR program team.

The MOS is a collection of concepts described homogeneously and neutrally in terms of technologies. It offers a common description of the information processed and exchanged in the information systems to make digital communication easier.

The overall consistency of the MOS is founded on the definition and description of its UML (Unified Modelling Language) concepts.

Some MOS concepts can be coded. They are associated with the nomenclatures of health objects (NOS), i.e. lists of codes/labels.

You are encouraged to use MOS and NOS to :

• optimise and coordinate efforts when you analyse or conceive a system (or an application) by re-using the same semantic components;
• make sure there is consistency in your internal developments and with external systems, for the best possible interoperability.

The European Commission’s studies have determined there is a need for a base vocabulary, such as MOS and NOS, which can be used as a starting point for:

• develop and evolve information systems (IS) to formalise the conceptual and logical data they utilise (for instance, the MOS is a reference for the modelling of the RPPS);
• share information between ISs to create specific models of data they can use (thus, the MOS is underlying the ROR exposure model);
• combine and synthetise elements originating from different sources;
• publish data in a common format, such as a directory or catalogue of service (for example, the Annuaire Santé / Health Pro Directory).

Upgrading your products allows you to offer your customers a solution that complies with current regulations. Failure to meet this requirement will have several impacts: 

• Your customers will not incorporate the INS into their software, which will entail possible penalties with regard to several systems (Ségur Wave 1, HOPEN, portal listing in Mon Espace Santé, etc.) ; 

• Your customers will not be in compliance with the law. They will therefore be responsible for any errors in the identification of their patients and users ; 

• Sharing health data by your customers will be more time consuming ; 

• The identity used by your customers may not be the right one, for instance if a patient uses their married name or if the patient is a child registered under their parent’s social security number.

Yes, the applications close before the end of the first Ségur wave to allow enough time for the solutions implementation.

PLATINES is a platform dedicated to interoperability tests for eHealth. It stimulates a ROR (version 2.4) and gives you the opportunity to use “test” data via several professional cases (a total of 94 test scenarios are available). These test scenarios are valid for the current ROR as well as the national ROR.

You must contact the ROR program team to request access to PLATINES.