WO2014172761A2

WO2014172761A2 - Method and system for communication between users, in particular between doctors/dentists and patients

Info

Publication number: WO2014172761A2
Application number: PCT/BG2014/000018
Authority: WO
Inventors: Peter Grigorov VELEV
Original assignee: Credoweb Ltd.
Priority date: 2013-04-22
Filing date: 2014-04-22
Publication date: 2014-10-30
Also published as: EP2989577A2; WO2014172761A3; CA2909525A1

Abstract

The present invention refers to a method and system for communication between users, in particular between doctors/dentists and patients, which may be used in the field of healthcare. The method involves: receiving a request for access to information and/or search for a doctor/dentist via the Internet from the user's device; checking and identifying the type of the request and the type of the user and processing the request according to its type and the user's access level and providing the user with comprehensive, selected and reliable information that appears on the appropriate user's device. The system for communication between users, in particular between doctors/dentists and patients, allows for direct communication between the users. The system consists of two server, and the first server (1) hosts the SQL database (1.1 ) serving the "Open ID" client-server technology, whereas the second server (2) hosts the user database (2.1 ) with two-way connected dedicated module (2.2) for management and provision of information to users. The dedicated module for management and provision of information to users (2.2) is implemented in two variants.

Description

METHOD AND SYSTEM FOR COMMUNICATION BETWEEN USERS, IN PARTICULAR BETWEEN DOCTORS/DENTISTS AND PATIENTS

TECHNICAL FIELD

The present invention refers to a method and a system for communication between users, in particular between doctors/dentists and patients, which may be used in the field of healthcare.

TECHNICAL BACKGROUND ART

The technical background shows methods and systems for communication of internet network users, in particular social systems arranged in one of the following two ways: as users in a peer-to-peer network or in a server based network. More widespread is the server based network that consists of one or more main computers, called server(s), servicing the network. The server stores information and resources organized in a user database, processed by the respective server- based software. These data are available to customers through their PCs connected to the network. There are server-built databases such as SQL databases and servicing server-based software that provides a secure single connection between a particular client to the server, isolated from the other clients.

In a of client-server network, the clients included in the network are users and in this case the user- client - usually but not always- is a computer and may also be another device, such as a cell phone, computer - notebook, terminal, etc. In general, the client works as a network device that sends a request to one or more servers to use a resource in the network. The server, in turn, provides the requested resources (data, software, printers, etc.) to the other computers in the network and is mainly used for centralized management of network services, where each computer in the network can work both as a client, and as a server. It is known from the technical background that the client may also be a program. When operating, it connects to another computer - server, acting as the so-called client program, a familiar example of which is the e-mail software, connecting with the mail-server in order to receive or send users' emails. Network servers can have thousands of users. They are more expensive than equal access networks, but are the best solution for large companies or where there is a need for keeping big volumes of data. The administration of client-server networks is simpler, especially for networks comprising many computers and shared resources. The shared files are stored on the server, so that they can be easily archived and searched. The management of this type of networks is carried out by a system administrator controlling all network operations and resources. The security of these systems is higher than that of the equal access networks. To enter the network each user must have a username and a password created on the server. The network administrator can assign different access rights to a specific resource to different users, and the individual users can combine in groups and then the individual user groups are assigned different rights.

The current state of the art, in particular the publication of CN202602673 (U) of 12/12.2012 [1] provides information about the "Doctor-Patient Communication System". This system contains a patient terminal, a server for transmission and collection of information and a doctor terminal, where the server is connected to the doctor and patient terminals by cable or wirelessly to the network for communication and transmission of data in real time. The doctor and patient terminals are mobile devices or fixed terminals. Each user can connect and log in after registering as a registered user through the input interface and exchange information in real time with a professional doctor. The wireless connection between the server for transmitting and collecting information is a third generation telecommunication (3G) network or fourth generation telecommunication (4G) mobile communications network (internetwork). By adopting internetworking the limitations of Internet can be overcome so that the doctor can be connected with the patient at anytime and anywhere. The server for collecting, storing and transmitting information is connected with a social security system via the network to provide data exchange. The security system can update the status according to data of the doctor-patient communication system and thereby make updating and completion of the medical insurance and the entire status in the security system. The server is also connected with the family monitoring system over the network so that the doctor can observe and monitor the health status of all family members in real time. The doctor-patient communication system referred to in [1] does not provide for communication between multiple users, but between many doctors and patients, doctors and doctors as well as between these groups and health or patient organizations, institutions, companies, medical staff, etc., and does not provide opportunities to search for information for different purposes and depending on the user's query and the relative user's access level.

The publication US 6757898 B1 of 29/06/2004, [2] provides information about the "Electronic provider— patient interface system". The communication takes place between at least one provider and a number of users connected to the provider, where the communications occur through the provider/patient interface. The system includes a central server containing at least one server or one logical device of a number of servers; provider's service computer; a number of user PCs; and a communication network that allows for communication between the central server, the provider's service computer and the user PCs. The preferred system users are patients, and the preferred provider is the patient's GP or a person providing health care such as the patient's practitioner. The system provides an automated mechanism for generating personalized space (patient page) for each user in the web site of a doctor or a group of doctors within the system and for presenting provider-based information content in standardized formats, such as the standard administrative or legal codes and formats. Thus, the system provides for automated patient care through which the patients' access to their own doctor is provided over the Internet excluding any additional work for the doctor's office. For the system referred to in [2], the information provider and generator is the doctor who provides information to the registered patients under his/her cares.

The technical background, in particular BG 1652 U1 [3], shows a system for providing Internet access. The well-known system is designed to provide free and secure user access to the global network - Internet, and includes a component for recognition and receiving user's requests to connect to the global network, and a component for providing access. According to BG 1652 U1 , the user request receiving component is connected to component providing access to an affiliated website, where the recognition component includes a module providing access to the global network - Internet. According to the preferred implementation of the familiar system, the component recognizing the user as a new user or as an already known user on the network is dd-wrt software, whereas the component for providing access to an affiliated website is a http server and user, where dd-wrt software also provides for the user's access to the global network. The request for access to the global network enters the request receiving component and then it is forwarded to dd-wrt software that defines the user as a new user or as an already known user. The user defined as an already known user is forwarded to http server that returns to the user the request with the requested and/or added content, such as an advertisement. In general, no direct access to the network is provided for the user, but the specific user is given the choice to review the information and/or the advertisement sent, or to continue to the global network. If the user chooses to review the information and/or the advertisement first, in order to continue to the global network, they must re-apply for access. In case the user is recognized by dd-wrt software as an already known user, the user is provided access to the global network through a virtual access tunnel, protecting the user from the intervention of third parties. The well-known internet access system does not provide an opportunity for direct communication between users, in particular between doctors and patients, and does not provide selected information according to the user's request and the specific user's access level.

TECHNICAL DISCLOSURE OF THE INVENTION

The present invention aims to provide a method and a system allowing for direct communication between users, in particular between doctors/dentists and patients, involving exchange of selected and reliable information depending on the user's request and in accordance with the determined user's access level. The invention also aims to provide an opportunity for exchange of information through communication between different groups of users in the field of healthcare.

The method of communication between users, in particular between doctors/dentists and patients, involves the following operations: receiving a request for access to information and/or search for a doctor/dentist via the Internet from the user device; implementation of a check to identify the type of request and determine the type of user; processing of request depending on its type and the user's access level. From the user database it is possible to retrieve the relevant information on the search for a doctor/dentist and/or the work calendar of the doctor/dentist and/or to record an appointment with the doctor/dentist. It is also possible to retrieve information on articles for patients or doctors/dentists, or information on useful links, or an event calendar, or inquiries carried out, or forums, e-mails. The information is displayed on the relevant user device in accordance with the function and type of request. For a new user - patient or doctor/dentist, upon processing the request in accordance with its type and the user's access level, the system carries out the operation of determining an identification code and user registration in the SQL database servicing the "Open ID" server-client technology, followed by determining the access level and then the so made registration of the user is saved in the user array on the user database. When the request is filed by a registered user - patient, this request is forwarded to the user database to retrieve and provide the relevant information. For a request filed by a doctor/dentist, the system checks for the user's access level and certifies the doctor's competence. Upon confirmation of the access level, the request is forwarded for processing and provision of relevant information. For requests for access to work calendar and/or recording an appointment with the respective doctor/dentist, there is a two-way communication via the Internet between users, in particular between doctors/dentists and patients, in order to specify the date and time of the appointment. For a request by a user to a banner, the system sends information about the user type and access level. In accordance with the user's access level, an advertising banner is sent to be displayed on the user device, where parameters such as size, duration, time of displaying each advertising banner and sequence of displaying the banners of the relevant advertising campaign are predetermined and set in the banner system.

In case of a request to search for a doctor/dentist, the system generates dropdown menus for selecting parameters where the user may select and/or input the parameters known such as region, town, medical facility of the doctor/dentist searched, doctor/dentist's specialty, name and/or surname, and type of appointments. These parameters are sent to the user database and based on them the system retrieves and filters the information contained in the array of doctors/dentists' data. The filtered data is sorted according to the rating of doctors/dentists and their unoccupied time for appointments if the request is for a date and/or time of appointment, and then this information is sent to the user.

The doctors/dentists' rating is determined after each appointment by generating and sending to the user a message containing questions that are recorded automatically at the time of answering. The resulting data are processed and stored.

In the event of a request sent by a user for appointment, consultation and/or examination of a patient at the doctor/dentist's, the system generates an appointment calendar of the selected doctor/dentist with the specified period of time - daily, weekly, monthly calendar of the current year with colour-coded unoccupied times of appointment, then the user-patient marks the date and time of appointment on the doctor/dentist's calendar with a "pending confirmation" status. In accordance with the response of the doctor/dentist, the system generates a confirmation and/or cancellation and/or marking of a new date and time of appointment, which is then recorded on the calendar. In this way the time of appointment is determined following the doctor/dentist-patient communication. For a user-doctor/dentist, the system activates calendars corresponding to each of the doctor/dentist's offices. The calendar contains optional interfaces of respective daily, weekly, monthly calendar, list of patients, determination, confirmation and/or amendment of appointment for consultation or examination and/or archiving completed consultations or examinations and events. In case of appointing a new consultation or a new examination, the system enters a patient's name from the list of recorded patients or the name of a new unregistered patient, or a personal appointment of the doctor/dentist. When the date and time of the appointment are determined, the system sets the deadline for confirmation of the appointment by the patient. For a user- nursing staff, the system verifies the authorization of the person to perform the above described actions.

After specifying the date and time of appointment, the "pending confirmation" status in the calendar is changed into "confirmed". A message is generated for the agreed appointment that is sent both to the patient and the doctor/dentist.

The system for communication between users, in particular between doctors/dentists and patients, includes two servers, where the first server hosts the SQL database servicing the "Open ID" server-client technology, and the second server hosts the user database with two-way connected dedicated module for management and provision of information to users depending on the request and the type of user. Through the dedicated modules for management and provision of information depending on the request and the type of users, the second server is connected via the Internet to the first server to n user devices and to the administrator's work device.

The second server also includes a module Banner system, a module for electronic communications and a module Forums, and these modules are two-way connected to the user database and to the dedicated module for management and provision of information to users. The module Banner system is connected through the dedicated module for management and provision of information to users via the Internet and to the administrator's work device and to the respective user's device. In addition, the module Forums is connected through the dedicated module for management and provision of information to users depending on the request and the type of users via the Internet to the respective user's device. The module for electronic communications is connected to the Internet.

The dedicated module for management and provision of information to users includes a module for registration and a module for doctor/dentist's authentication, and both modules are two-way connected with one another, whereas each of them has one input and one output, which are inputs and outputs of the dedicated module for management and provision of information to users depending on the request and the type of user intended for connection with the user database on the second server. The module for registration is connected to the output of the second access verifying component and connected to the input and output of the dedicated module for management and provision of information to users for two way connection via the Internet to the first server and to the appropriate user's device. The second access verifying component also has inputs and outputs that are respective inputs and outputs of the dedicated module for management and provision of information to users for connection respectively to the user database on the second server and via the Internet to the respective user's device. The dedicated module for management and provision of information to users depending on the request and the type of user also contains a module for search for a doctor/dentist, a module Working calendar, a module Articles for doctors/dentists, a module Articles for patients, a module Medical audit, a module Lawyer's blog, a module Useful links, a module Event calendar, a module Forums control, an module Inquiries and a module Videos. The inputs of these modules are connected to the output of the second access verifying module. Moreover, each of these modules has an input and output of the dedicated module for management and provision of information to users depending on the request and the type of user intended for connection to the user database on the second server and via the Internet to the appropriate user's device, the display of which shows boxes corresponding to the functions of the modules.

The input and output of the module Forums control and of the module Advertising space located in the dedicated module for management and provision of information are inputs and outputs of the dedicated module for management and provision of information to users, where these inputs and outputs are intended for connection respectively to the standard module Forums and to the module Banner system which are standard modules connected through their inputs and outputs to the dedicated module for management and provision of information to users for connection with the module for administration. The module for administration has inputs and outputs representing the respective inputs and outputs of the dedicated module for management and provision of information to users for connection via the Internet to the administrator's work device and to the user database on the second server. The module for administration is connected to the output of the first access verifying component, which has inputs and outputs, which are inputs and outputs of the dedicated module for management and provision of information to users for connection via the Internet respectively to the administrator's work device and to the user database. The input of the module for administration is connected to the output of the first access verifying component which is connected to a terminal of the dedicated module for management and provision of information to users for two-way connection to the user database of the second server and via the Internet - to the administrator's work device. The second variant of the dedicated module for management and provision of information to users includes a module for administration and a module for doctor/dentist's authentication, and both modules are two-way connected with each other. The module for doctor/dentist's authentication is two-way connected to the first access verifying component, which has one of its outputs connected to the module for administration. The output of the module for administration is the output of the dedicated module for management and provision of information to users intended for connection to the inputs of the module Forums, module Banner system and the module for electronic communication respectively. The first access verifying component, the module for administration and the module for doctor/dentist's authentication each have inputs and outputs that are an input and an output of the dedicated module for management and provision of information to users intended for two-way connection via the Internet to the administrator's work device and respectively inputs and outputs that are an input and an output of the dedicated module for management and provision of information to users intended for two-way connection to the user database. The module for administration is connected to the second access verifying component to which two-way connected are the module Work calendar, the module for search, the module Publications, the module for users' profiles, the module Forums control, the module Useful links, the module Event calendar, the module for internal communications and the module Advertising space. The module for search is composed of a sub-module for search for a doctor/dentist, a sub-module for search for another user and a sub-module for search by a keyword. This module is one-way connected via its sub-module fo search for a doctor/dentist to the module for users' profiles. Through its sub- module for search by a keyword the module for search is connected to the input of the module Publications, to the input of the module for users' profiles and to the input of the module Forums control, whereas through its sub-module for search for another user it is connected to the input of the module for users' profiles. The module for users' profiles is two-way connected to the module Work calendar. The module Forums control has an input and an output that are an input and an output of the dedicated module for management and provision of information to users intended for two-way connection to the module Forum of the second server. The module for internal communications has an input that is an input to the dedicated module for management and provision of information to users intended for connection to the output of the module for administration. Each of the module for registration, the module Work calendar, the module for search for information, the module Publications, the module for users' profiles, the module Forums control, the module Useful links, the module Event calendar, the module for internal communications, the module Advertising space, and the second access verifying module has inputs and outputs that are inputs and outputs of the dedicated module for management and provision of information to users intended respectively for two-way connection to the user database and for two-way connection via the Internet to the appropriate user device. The display of the user device visualizes the boxes with corresponding functions, namely: box Registration form, box Users' login forms, box Work calendar, box for Search, box Publications, box Useful links, box Event calendar, box Users' profiles, box Forums and box Internal communications and box Advertising space. The user database on the second server contains separate arrays of information about the users' identity data - doctors/dentists, patients, medical staff - connected with the working places array, with the sub-arrays for working time and medical facilities. In addition it contains an array of medical specialties and specializations of doctors/dentists, an array of business contacts and an array of medical events calendar. It also includes an array of data about other users working in the field of healthcare, and an array of offered products and/or services related to health care.

The above described method and system provide for reliable direct communication between doctors/dentists, patients and other users that can be carried out in real time and in interactive mode, while at the same time the type and volume of the information provided to users depends on the particular user - doctor/dentist, patient, medical facilities, medical staff, companies and individuals operating in the fields of healthcare, patient organizations, government and public health institutions and/or patients.

BRIEF DESCRIPTION OF THE FIGURES

The method and system for communication between users, in particular between doctors and patients, are illustrated in the following figures:

Fig. 1 is a diagram showing in summary the method of communication between users, in particular between doctors/dentists and patients;

Fig. 2 - diagram of handling a request for registration of a doctor/dentist;

Fig. 3 - diagram of handling a request for registration of a patient;

Fig. 4 - diagram of processing a request for search for a doctor/dentist;

Fig. 5 - diagram of processing a request for appointment with a doctor/dentist;

Fig. 6 - block view of the system that implements the method;

Fig. 7 - functional diagram of the system according to this invention;

Fig. 8 - functional diagram of the system variant according to this invention.

DESCRIPTION OF THE EMBODIMENTS OF THE INVENTION

The method and system for communication between users, in particular between doctor/dentist and patient, can be explained by an exemplary implementation shown in Figures 1 to 8.

According to Fig. 1 , when a user device sends a request for access to information via the Internet, prior to processing the request of a new user - patient or doctor/dentist - the system carries out a user registration procedure and then determines the access level and the so performed user registration is saved in the user array. When the user skips registration, he/she is limited to using a demonstration (demo) version of the communication method. When the request is filed by a registered user - patient, this request is forwarded for processing and the system retrieves and provides the relevant information. Upon receiving a request by a doctor/dentist, the system checks for the access level and authentication of the doctor/dentist's competence, then upon confirming the access level, the system forwards the request for processing and provision of relevant information. The request may concern searching for a doctor/dentist, making an appointment with a doctor/dentist and/or doctor/dentist's work calendar, articles for patients or doctors/dentists, information about useful links, event calendar, inquiries conducted or forums. The information is retrieved and sent to the appropriate user device.

Upon receiving a request for registration of a doctor/dentist (Fig. 2), the system requires successive entering of identity and personal data, namely: user type, unique identification number or personal professional code, password, password confirmation, e-mail address, scientific or academic degree, name and surname, primary specialty, additional specialty, contact telephone numbers, region and place of the doctor/dentist's office. Other data can also be entered (year of birth, unique identification code of friend(s), etc.). The personal data are selected from the generated drop-down menus.

The system checks the correctness of the data entered for registration, where the first check is for the availability of registered user with the same data, then the check proceeds with the other data. The optional data as such as unique identification number of friend(s) is only checked for availability of a doctor/dentist with the same unique identification number/ personal professional code registered with the database. Only data of already registered doctors/dentists are accepted. Error messages are generated for any ascertained errors or omissions in the data input.

The correct entries are saved in the user database and in the SQL database. Messages about the registration are generated and sent to the doctor/dentist, the authentication person and to the doctors/dentists-friends whose UIN/PPC has been entered. The registered doctor/dentist can log in to create a profile or to enter the menu of registered doctors/dentists.

For a request for registration of a patient, as shown in Fig. 3, the system carries out the same steps as those required for the registration of a doctor/dentist in Fig. 2. The patient is required to enter the following data: username, password, password confirmation, e-mail address, name and surname, telephone numbers. A message about the registration is generated and sent to the registered patient. After the registration, the patient can log in to create a profile or to enter the menu of registered patients.

Upon receiving a request for search for a doctor/dentist (Fig. 4), the system generates drop-down menus to select parameters such as region, town, medical facility of the doctor/dentist searched, doctor/dentist's specialty, and the user enters sequentially the parameters known. The next step concerns entering data about the doctor/dentist's name and/or surname and the type of the appointments. The parameters are sent to the user database and based on them the system retrieves and filters the information contained in the array of doctors/dentists data. The filtered data is saved according to the rating of doctors/dentists and their unoccupied time for appointments if the request is for a date and/or time of appointment, then this information is sent to the user. Depending on the search result, the user can make a new search or to proceed respectively to review the doctor/dentist's calendar to make an appointment for a particular date and time, to proceed to review the doctor/dentist's rating, to proceed to review the doctor/dentist's profile or to exit the system.

Doctors/dentists' rating is determined after each appointment by generating and sending to the user a message containing questions that are recorded automatically at the time of answering. The obtained data are processed and saved.

Upon receiving a request for making an appointment with a doctor/dentist, as shown in Fig. 5, the system generates a calendar with the schedule of all offices of the selected doctor/dentist. The doctor/dentist may have more than one office in one or more different towns and medical facilities, and the system provides information about the location of the office where the respective doctor/dentist examines patients, the specialty/ies and the available times of appointment. The calendar for each office contains optional interfaces - daily, weekly and monthly calendar for a year period where the unoccupied appointment times are colour- coded.

When the user is a patient, he/she chooses and marks the corresponding unoccupied date and time of appointment and then the system generates a message containing data of the appointment. Additional data are entered relating to the request for making an appointment, such as symptoms, test data, past medical history, etc. These data are checked for correctness, and in case of ascertaining errors, the system generates a message with the respective appointment data with indications of errors. If the data are correct, the appointment is recorded in the user database with status "appointment pending confirmation by the doctor/dentist". The system automatically generates and sends messages with the reserved date and time of the appointment both to the patient and to the doctor/dentist, and in case of a specific request for the respective medical office and medical facility - to the medical administration. After reserving the date and time of appointment, the patient is allowed to access the patient menu for reviewing the personal calendar or profile, or to exit the system.

For the user doctor/dentist, the system generates calendars corresponding to each of the doctor/dentist's offices. The calendar contains optional interfaces of respective daily, weekly, monthly calendar for one-year period, a list of patients, determination, confirmation and/or amendment of appointment for consultation or examination and/or archiving implemented consultations or examinations and events. In case the doctor/dentist makes a new appointment or new examination in the calendar associated with the respective medical office, the system enters a patient's name from the list of recorded patients or the name of a new unregistered patient, or a personal appointment of the doctor/dentist. When a date and time of appointment are determined, the system also sets the deadline for confirmation of the appointment by the patient. After the system checks the data input, the appointment is recorded in the user database with status "appointment pending confirmation by the patient". When the user is nursing staff, the system will also verify the authorization of the person to perform the above described actions. Messages are automatically generated and sent to all involved persons.

For a request by a user to a banner, the system sends information about the user type and the access level. The system sends an advertising banner corresponding to the user's access level to be displayed on the user's device, where parameters such as size, duration, time of displaying each advertising banner and the sequence of displaying the banners of the relevant advertising campaign are predetermined and set in the banner system.

After processing the request for appointment and recording the reserved date and time of appointment in the user database with status "pending confirmation" by users - patients or doctor/dentist/medical staff or administration respectively, the system carries out steps similar to those described in the procedure of processing the request for appointment (Fig. 5).

Figure 6 shows the block view of the system for communication between users, in particular between doctors/dentists and patients according to the invention. The system is implemented as a client-server network through the Internet (server- based network) consisting of two servers - first server 1 and second server 2. Both servers 1 and 2 are connected to each other via the global network - the Internet. The first server 1 serves the OpenID technology and it hosts under Linux operating system the SQL database 1.1 and the modules OpenID Server 1.2 and OpenID client 1.3. It is used to manage and store usernames and passwords of the system users and administrators, since this standard allows the users to enter into various websites without having to log in for each of them separately. A single address is required to be entered - the user's OpenID - and the communication is performed by selecting to log in. The user registration under this standard is the basis for regulating the user access to information.

On the second server 2, Linux operating system creates and maintains user database 2.1 for handling relational databases. The user database 2.1 on server 2 includes an array of users' data - data of doctors/dentists, patients or medical staff - connected with the work places array with sub-arrays for working time, medical facilities and business contacts as well as medical and/or pharmaceutical enterprises. Moreover, the users' data array is connected to the array of the users' specialties, to the arrays of the calendar of medical events and medical audit respectively.

Server 2 also hosts the dedicated module for management and provision of information to users 2.2, processing requests for two way communication between doctors and patients, which are also connected to the user database 2.1 and has input and output that are input and output of the server 2 for connection via the Internet.

The second server 2 also hosts the standard control modules adapted to the functions of the electronic communication system according to the invention, namely: a module Forums 2.3 intended to service Internet forums, a module Banner system 2.4 intended to control image advertising campaigns and a module for electronic communications 2.5- a module for Internet e-mail campaigns.

The installed modules use peripherals, processors, disk space and memory, that are set up according to the specific requirements of the system.

User devices 3 can be all kinds of devices, such as computers, laptops, tablets, provided that they support Internet browsers.

The second server 2 through its interface is directly connected to the user devices 3.i, 3.2, 3.3, (3.i) ... 3n via the Internet using "http" and "https" protocols.

Fig. 7 shows a functional diagram of the components, modules and the links between them, providing an example of the operation of the communication system, in particular doctor/dentist-patients, in accordance with this invention. The first server 1 is connected via the Internet to server 2. The second server 2 is connected to the administrator's work device 4 and to one exemplary user's device - the computer 3.i. The display of the user's device 3.i shows exemplary boxes that are displayed during the operation of the system, namely: box Registration form 3.Ϊ.1 , box User login forms 3.i.2, box Work calendar 3.i.3, box for search for doctor/dentist 3.Ϊ.4, box Lawyer's blog 3.i.5, box Medical audit 3.i.6, box Useful links 3.Ϊ.7, box Event calendar 3.i.8, box Articles for doctors/dentists 3.i.9, box Articles for patients 3.Ϊ.10, box Forums 3.L11 , box Inquiries 3.L12 box Videos 3.Ί.13 and box Advertising space 3.Ί.14.

The second server 2 hosts the dedicated module for management and provision of information to users 2.2 and the user database 2.1 and the standard control modules respectively for forums 2.3, Banner system 2.4 and module for electronic communications 2.5. The dedicated module for management and provision of information to users 2.2 includes components, modules and links for processing requests and for ensuring the communication between doctors/dentists and patients, namely: a module for registration 2.2.4, which has inputs and outputs that are inputs and outputs of the dedicated module for management and provision of information to users 2.2, respectively connected to the user database 2.1 , and via the Internet to the respective the user's device 3.i and to the first server 1. The module for registration 2.2.4 is two-way connected to the module for doctor/dentist's authentication 2.2.3, which in turn is two-way connected to the user database 2.1 , to the first access verifying component 2.2.1 , and directly via the Internet- to the administrator's work device 4. The first access verifying component 2.2.1 is connected through its output to the module for administration 2.2.2 and has an input and an output that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to the user database 2.1. The module for administration 2.2.2 on its part has an input and an output that are respectively inputs and outputs of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to the user database 2.1 and via the Internet - to the administrator's work device 4. The output of the module for administration 2.2.2 is an output of the dedicated module for management and provision of information to users 2.2, which is connected to the module Banner system 2.4 and to the module for electronic communication 2.5. One of the inputs of the module for registration 2.2.4 is connected to an output of the second access verifying component 2.2.5, which has inputs and outputs that are inputs and outputs of the dedicated module for management and provision of information to users 2.2 intended for two-way connection respectively to the user database 2.1 and via the Internet - to the respective the user's device 3.i. The second outputs of the second access verifying component 2.2.5 are connected to each of the modules - module Work calendar 2.2.6, module for search for a doctor 2.2.7, module Lawyer's blog 2.2.8, module Medical audit 2.2.9, module Useful links 2.2.10, module Event calendar 2.2.11 , module Articles for doctors 2.2.12, module Articles for patients 2.2.13, module Forums control 2.2.14, module Inquiries 2.2.15, module Videos 2.2.16, and module Advertising space 2.2.17, which in turn have inputs and outputs that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to the user database 2.1.

The module Work calendar 2.2.6 is two-way connected to the module for search for a doctor 2.2.7 and module Lawyer's blog 2.2.8, module Medical audit 2.2.9, module Useful links 2.2.10, module Event calendar 2.2.11 , module Articles for doctors 2.2.12, module Articles for patients 2.2.13, module Forums control 2.2.14, module Inquiries 2.2.15, module Videos 2.2.16, and module Advertising space 2.2.17 are also two-way connected to the input and the output of the dedicated module for management and provision of information to users 2.2 intended for connection to the user database 2.1. Each of these modules of the dedicated module for management and provision of information to users 2.2 is connected via the Internet to its functionally corresponding box on the display of the user's device 3.i, namely: box Registration form 3.1.1 , box User login forms 3.Ί.2, box Work calendar 3.L3, box for search for doctor/dentist 3.Ϊ.4, box Lawyer's blog 3.L5, box Medical audit 3.i.6, box Useful links 3.i.7, box Event calendar 3.Ϊ.8, box Articles for doctors/dentists 3.Ϊ.9, box Articles for patients 3.Ϊ.10, box Forums 3.1.11 , box Inquiries 3.Ϊ.12, box Videos 3.Ϊ.13 and box Advertising space 3.1.14.

The module Advertising space 2.2.17 and the module Forums control 2.2.14 have inputs and outputs that are inputs and outputs of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to are connected to the standard modules - module Banner system 2.4 and module Forums 2.3 respectively, adapted to the system's functions according to the invention. The standard module for electronic communication 2.5, designed to send messages to users, is directly and one-way connected via the Internet to user's e-mail. The module Banner system 2.4 and the module for electronic communication 2.5 are connected to the output of the module for administration 2.2.2.

Fig. 8 shows a functional diagram of the components, modules and connections between them of the second variant of the system for communication between users according to the invention, in particular covering the dedicated module for management and provision of information to users 2.2.

In this variant, as in the first variant, the dedicated module for management and provision of information to users 2.2 includes the first access verifying component 2.2.1 two-way connected to the module for doctor/dentist's authentication 2.2.3. An output of the first access verifying component 2.2.1 is connected to the module for administration 2.2.2. The module for administration 2.2.2 is connected to an output of the dedicated module for management and provision of information to users 2.2 intended for connection to the module Forums 2.3, to the module Banner system 2.4 and to the module for electronic communication 2.5. The module for doctor/dentist's authentication 2.2.3 is two-way connected to the module for registration 2.2.4. The module for registration 2.2.4 is also connected via the Internet to the server 1. An output of the second access verifying component 2.2.5 is connected to the input of the module for registration 2.2.4. The dedicated module for management and provision of information to users 2.2 also includes a module Work calendar 2.2.6, module Useful links 2.2.10, module Event calendar 2.2.11 , module Forums control 2.2.14, and module Advertising space 2.2.17, which are identical to those of the first variant of the dedicated module for management and provision of information to users 2.2, as shown on Fig. 7. The module Forums control 2.2.14 has an input and an output that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to the module Forums 2.3. The module Advertising space 2.2.17 has an input and an output that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to the module Banner system 2.4.

Unlike the first variant of exemplary implementation of the dedicated module for management and provision of information to users 2.2, this variant includes a module for search 2.2.18 which enables search not only for doctors/dentists, but also for other users, as well as to search by a keyword. The category of other users includes medical professionals, medical institutions, companies operating in the field of healthcare, pharmacists, pharmacies and pharmacy chains, health institutions and organizations, patient organizations and other entities in the field of healthcare. The module for search 2.2.18 has sub-module for search for a doctor/dentist 2.2.18.1 , a sub-module for search for another user 2.2.18.2 and a sub-module for search by a keyword 2.2.18.3. The module for search 2.2.18 is one-way connected through the sub-module for search for a doctor/dentist 2.2.18.1 and through the sub-module for search for another user 2.2.18.2 to the module for users' profiles 2.2.20. Through the sub-module for search by a keyword 2.2.18.3, the module for search 2.2.18 is connected to the input of the module Publications 2.2.19, to an input of the module for users' profiles 2.2.20, and to an input of the module Forums control 2.2.14.

Characteristic of this exemplary variant is the separation of the module Publications 2.2.19 as a single module combining and performing the functions of the following modules provided for in the first variant (Fig. 7): module Lawyer's blog 2.2.8, module Medical audit 2.2.9, module Articles for doctors 2.2.12, module Articles for patients 2.2.13, module Inquiries 2.2.15, and module Videos 2.2.16. The above described variant also provides for the module for users' profiles 2.2.20. The input of the module for users' profiles 2.2.20 is connected to the output of the module for search for a doctor/dentist 2.2.18.

This variant of the dedicated module for management and provision of information to users 2.2 also includes the module for internal communications 2.2.21 enabling the internal communication between all users of the system. An input of the first access verifying component 2.2.1 is connected to the module for administration 2.2.2.

The second access verifying component 2.2.5 is two-way connected to the module Work calendar 2.2.6, the module for search 2.2.18, the module Publications 2.2.19, the module Useful links 2.2.10, the module Event calendar 2.2.11 , the module for users' profiles 2.2.20, the module Forums control 2.2.14, the module for internal communications 2.2.21 , and the module Advertising space 2.2.17.

The module for administration 2.2.2, the module for doctor/dentist's authentication 2.2.3 and the first access verifying component 2.2.1 each have respectively an input and an output that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection via the Internet to the administrator's work device 4.

Each of the respective module for registration 2.2.4, module Work calendar 2.2.6, module for search 2.2.18, module Publications 2.2.19, module Useful links 2.2.10, module Events calendar 2.2.11 , module for users' profiles 2.2.20, module Forums control 2.2.14, module for internal communications 2.2.21 , module Advertising space 2.2.17, as well as the second access verifying component 2.2.5 has an input and an output that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection via the Internet to the respective the user's device 3.i.

Each of the respective modules for administration 2.2.2, for doctor/dentist's authentication 2.2.3, for registration 2.2.4, Work calendar 2.2.6, for search 2.2.18, Publications 2.2.19, Useful links 2.2.10, Events calendar 2.2.11 , for users' profiles 2.2.20, Forums control 2.2.14, for internal communications 2.2.21 , Advertising space 2.2.17, as well as the first access verifying component 2.2.1 and the second access verifying component 2.2.5 has a respective input and output that are an input and an output of the dedicated module for management and provision of information to users 2.2 intended for two-way communication with the user database 2.1 of the server 2.

The output of the dedicated module for management and provision of information to users 2.2 intended for two-way connection to the Internet is connected to the network adaptor of the second server 2.

Each of the modules of the dedicated module for management and provision of information to users 2.2 is connected via the Internet to its functionally corresponding box on the display of the user's device 3.i, namely: box Registration form 3.Ϊ.1 , box User login forms 3.i.2, box Work calendar 3.i.3, box for search for information 3.Ϊ.15, box Publications 3.Ϊ.16, box Useful links 3.Ϊ.7, box Event calendar 3.Ϊ.8, box Users' profiles 3.Ϊ.17, box Forums 3-i.11 , box Internal communications 3.Ϊ.18, and box Advertising space 3.Ϊ.14. The box for search for information 3.Ϊ.15 from each the user's device 3.i, functionally corresponding to the module for search 2.2.18, has predetermined fields for searching for a doctor/dentist, another user and by a keyword, respectively. The box Publications 3.Ϊ.16 of the user's device 3.i, functionally corresponding to the module Publications 2.2.19, has predetermined fields for input or display of information, such as lawyer's blog, medical audit, articles for doctors/dentists, articles for patients, inquiries and video boxes for entering the respective publications. The box Users' profiles 3.Ϊ.17, functionally corresponding to the module for users' profiles 2.2.20, has boxes for entering information about the profile of the medical office, the profile of the medical facility, the company's profile, the company's officer's profile, the patient's profile, the medical professional's profile, the doctor/dentist's profile and profiles of other entities operating in the field of healthcare. The box Internal communications 3.Ϊ.18, functionally corresponding to the module for internal communications 2.2.21 , has predetermined boxes displaying notification icon, list of conversations and address book.

The above described system is a medical communications system which allows for reliable direct communication between all its users, whether grouped, or individually. This communication complements a missing element in the organization of healthcare, namely: the exchange of scientific, public and personal health-related information or in general - public information that is not directly related to the doctor-patient relationship in a specific medical treatment process. At the same time the submission of the requested information to users is filtered by type depending on the type of the particular user. Moreover, the system can be used for communication between doctors, between doctors and medical facilities, as well as between medical facilities, institutions and patients.

OPERATION AND APPLICABILITY

The system operates by using modules and database saved on disk drives. In the process of operation, the modules and data necessary for the system are loaded on the memory of the respective server 1 or 2 where processing takes place. The process of loading is performed according to the user requests and depends on what is processed and what should be processed at that time. Data processing is performed by two four-core processors. Data exchange at server level is performed through the network interface, disk drives or directly through the memory. Data exchange between the user and the server is performed through internet protocol connectivity using client-server standard hyper-terminal protocol requests (http). The steps of system operation are performed in the following sequence:

The user fills in the web address into the browser of the user's device 3.i. The browser of the user's device 3.i produces a series of standard Internet requests to establish a connection to the Internet (IP) address of server 2. These steps result in establishing Internet connectivity between the two devices (the user's device 3.i and server 2) which ensures the data exchange between them. Upon establishing the connection, server 2 reads the homepage from its hard disk and returns it to the user's device 3.i for loading. It contains fields with key commands whose purpose is to determine the further behaviour of the system and which subsequent entry form must be returned to the user. The user selects one of the options and then based on it the user's device 3.i generates a new request to server 2 specifying the next form. Based on the submitted request, server 2 returns one of the four user input forms:

• registration of a doctor

• registration of a patient

• use of the system by a registered doctor

• use of the system by a registered patient

According to the user's selection, the following operation of the system is determined by the algorithm of actions and the request selected by the user.

A more detailed description of the operation of the system for communication of users, in particular doctor/dentist-patient, is given below.

The user connects from the user's device to the servers via the Internet. In turn, the two servers are also connected to each other via the Internet. The entire process of use is a cycle that takes place in the following sequence:

The browser of each user submits to server 2 a request for displaying the whole or part of a display page. (In the description, the parts of the displayed pages are called buttons, forms, fields, and boxes. The boxes may in turn contain one or more fields shaped as forms. Each field in turn contains some logic for arranging the data concerned. The buttons and some of the fields contain a link that generates a request for starting a procedure of data processing or loading the next field or form.)

The requests are generated as a result of a user action in the field of the displayed Explorer page and/or recording data in a field.

The second server 2 receives the request and processes it. Server 2 returns to the client browser the processed image for visualization on the display.

When sending a request for checking the access rights to the system (initial login) of the user's device 3.i the system displays a login page containing e fields for entering username and password.

Following steps:

• server 2 sends a request for data check to the first server 1.

• server 1 receives the request and processes it.

• server 1 returns a result to server 2 containing information whether or not to allow access.

• server 2 returns to the client browser the image to be displayed, processed according to the authorizing response of server 1.

• In case of error in the username and/or the password, the displayed image contains an error message and form to correct it.

• The process continues from the beginning. The cycle is repeated between these points until correct data is entered, a new user registration form is selected or logging out.

When correct data is entered, server 1 , based on the parameters of the already authorized user, prepares the home page and sends it to the user's device 3.i for loading. System operation when receiving a request for registration of a doctor/dentist:

According to the user's selection, the user's device 3.i sends a request for a doctor's registration form.

The second server 2 reads the appropriate form from the hard disk and returns it to the user's device 3.i for loading. The form sent contains fields where the doctor/dentist is required to fill in data on their universal identification number, title, name, surname, specialty, password for access, telephone, etc., hereinafter referred to as user parameters. Apart from the parameters already entered in the registration form, there are parameters automatically added by the system - open ID, ID - a unique system identifier, date/time of the last login, etc.

After completing the form, the user must continue the process by pressing "Register" button, after which the data from the registration form are sent as another request from the user's device 3„i to server 2. This request activates in the memory of server 2 module for registration 2.2.4 that takes the request and checks its data correctness.

If there are incorrect data, the system returns the registration form to the user's device 3.i for data correcting together with the corresponding error messages. The process continues until all data are correctly entered or the user exits the system. If the received request contains correct data, the module for registration 2.2.4 records the user's parameters in the user database 2.1 and sends the request to the first server 1 for opening an OpenID account. Server 1 opens the account and records the required parameters in its database. The connecting parameter of the account in the two servers is the shared unique for the system identifier (ID). After recording the account in the databases, the module for registration 2.2.4 prepares and sends an electronic notification letter to the authorized person (notary) for physical verification and confirmation of the registration and an electronic notification letter to the person who has requested the registration. After sending the letters, the dedicated module for management and provision of information to users 2.2 generates a code with the corresponding components regarding the form of the system desktop, and that code is returned to the user's device 3.i to be loaded. The user's parameters are used for the generation of the form. In the absence of data for some parameters, the system uses typical parameters preset by the administrator. The user's device 3.i displays on its screen the received form according to the describing code. According to the code, the system displays the relevant elements and boxes on the desktop.

In places where information display is required, the received form code contains commands for the browser of the user's device 3.i, which can be sent in the form of requests to the server 2. When such a request is sent, it is received by the dedicated module for management and provision of information to users 2.2, which activates the respective module in the RAM of server 2.

The activated module, using the parameters of the user corresponding to the user's ID, makes a request to the user^'s database to retrieve relevant information. Each system module handles different specific information. The processed data are returned to the user's device 3.i as a response to the request. The user's device 3.i receives the data and displays them on the place where the command is activated or the relevant new form

The process continues until the complete implementation of the code on the desktop page.

The displayed desktop page contains commands and personal user information filtered according to the appropriate parameters. The state of the user's device 3.i remains unchanged until the user activates any of the commands of the page.

System operation when receiving a request for registration of a patient:

According to the user's selection, the user's device 3.i sends a request for a patient's registration form. Server 2 reads the appropriate form from the hard disk and returns it to the user's device 3.i for loading. The form contains fields where the patients are required to fill in data about their name, surname, password for access, telephone, year of birth, and another user^'s parameters.

After completing the form, the user must continue the process by pressing "Register" button, after which the data from the registration form are sent as another request from the user's device 3.i to server 2. This request activates in the memory of server 2 the module for registration 2.2.4 that takes the request and checks its data correctness.

If there are incorrect data, the system returns the registration form to the user's device 3.i for data correcting together with the corresponding error messages. The process continues until all data are correctly entered or the user exits the system. If the received request contains correct data, the module for registration 2.2.4 records the user's parameters in the database and sends the request to the first server 1 for opening an OpenID account. Server 1 opens the account and records the required user^'s parameters in its database. The connecting parameter of the account in the two servers is the shared and unique for the system ID.

After recording the account, the module for registration 2.2.4 prepares and sends an electronic notification letter to the person requested the registration. After sending the letter, the dedicated module for management and provision of information to users 2.2 in server 2 generates a code with the corresponding components regarding the form of the system desktop, which code is returned to the user's device 3.i to be loaded. The user's parameters are used for the generation of the form. In the absence of data for some parameters, the system uses the system uses automatically generated by the system and predefined by the administrator. The user's device 3.i displays on its screen the received form according to its describing code. According to the code, the system displays the relevant elements and boxes on the desktop.

In places where information display is required, the received form code contains commands for the browser of the user's device 3.i, which are sent in the form of requests to the server 2. When such a request is sent, it is received by the dedicated module for management and provision of information to users 2.2, which activates the respective module in the RAM of server 2.

The activated module, using the parameters of the user corresponding to the user's ID, makes a request to the user database 2.1 to retrieve the relevant information. Each system module handles different specific information. The processed data are returned to the user's device 3.i as a response to the request. The user's device 3.i receives the data and displays them on the place where the command has been activated or in the relevant new form

The process continues until the complete implementation of the code of the desktop page.

System operation when receiving a request for access sent by a registered doctor/dentist:

In the case of this request, after starting the process, the user's device 3.i receives a page with fields where the doctors/dentist are allowed to fill in their unique identification number (username) respectively personal professional code and a password for access.

After the identification fields are filled in, the user's device 3.i sends a request for verifying the access to server 2. Server 2 receives the data and activates the second access verifying component 2.2.5 in its memory, which sends a request to the user database 2.1 to check the availability of a user with the same unique ID (username) and password.

If there is no match, the second access verifying component 2.2.5 generates a new adjustment registration form along with error messages and sends them to the user's device 3.i. The process continues until the entry of correct data. Provided that the request contains correct data, the second access verifying component 2.2.5 reads the parameters of the doctor/dentist from the database stored in the memory. These parameters contain user's personal information - specialty, title, name, selected user modules, etc. Based on these parameters, the dedicated module for management and provision of information to users 2.2 in server 2 generates a code with the relevant components of the doctor's desktop form, which code is returned to the user's device 3.i for loading. The doctor/dentist's parameters are used for the generation of the form. In the absence of data for some parameters, the system uses automatically generated by the system and predefined by the administrator. The user's device 3.i displays on its screen the received form according to the code by which it is described. According to the code, the browser of the user's device 3.i displays the relevant desktop elements and boxes. In places where information display is required, the received form code contains commands for the browser of the user's device 3.i, which after performing them generates requests to server 2. Upon sending such a request, it is received by the dedicated module for management and provision of information to users 2.2 in server 2, which activates the respective module in the RAM. The module activated in the memory, using the doctor's parameters corresponding to the doctor's ID, makes a request to the user database 2.1 to retrieve the relevant information. Each system module handles different specific information.

The processed data are returned to the user's device 3.i as a response to the request. The user's device 3.i receives the data and displays them on the place where the command is activated.

The process continues until the complete implementation of the code of the doctor/dentist's desktop page. System operation when receiving a request for access sent by a registered patient:

In the case of this request, after starting the process, the user's device receives a page with fields where the patients are allowed to fill in their username and password for access.

After filling in the identification fields, the user's device 3.i sends a request for verifying the access to server 2. Server 2 receives the request and the operation continues in a manner analogous to the algorithm described above for the system operation in case of a request for access to the system, sent by a registered doctor/dentist

System operation when receiving a request for making an appointment

This algorithm starts from the moment the user's device receives a command page that leads to a specific date on the doctor/dentist's calendar and the patient has activated the command. As a result of the activation, the user's device 3.i generates a request to server 2. Server 2 receives the request and activates the module Work calendar 2.2.6 in the memory, which reads in the database a dataset filtered according to the ID parameters of the doctor, doctor^'s office and the patient's parameters. The data read are encoded with the required commands from the module Work calendar 2.2.6 and returned as an image of the corresponding page to the user's device 3.i. The page displayed on the user's device 3.i contains box Work calendar 3.Ϊ.3 showing image of the calendar with of the working time of the doctor/dentist's daily schedule.

Each field represents the start time and the duration of the appointment with the doctor/dentist. Besides, colour coding is used to indicate the occupied and vacant segments of the appointment schedule. Then the user proceeds to select one of them. Following the selection of a specific field, in box Work calendar 3.Ϊ.3 a request is generated to module Work calendar 2.2.6, which in turn checks the user's access rights using the second access verifying component 2.2.5, generates the appropriate form and sends it back to the user's device 3.i. The so generated form contains fields for entering additional parameters of the appointment. After completing the parameters, the user activates the "Save" button, resulting in generating a request from the box Work calendar 3.L3 to module Work calendar 2.2.6 for making a record of the appointment. The module Work calendar 2.2.6 in turn again checks the user's access rights and the authenticity of the additionally entered parameters by using the second access verifying component 2.2.5. Upon finding incorrectly set parameters, the module Work calendar 2.2.6 generates an error message and via the Internet connection returns it to be displayed on the user's device 3.i in the appropriate fields of the box Work calendar 3.Ϊ.3. These operations are repeated until entering correct additional parameters and then the request is sent to be recorded in the user database 2.1.

Description of the system operation when receiving a request for a search for a doctor

In order to load the "Search for a Doctor" function, the system uses user's ID parameters and the "Search for a Doctor" form, loaded in "Active Page". At this point, the algorithm can be called from:

• from the box for search for doctor/dentist 3.i.4

• from a direct link via the Internet

• from links in other modules

The following actions are performed:

• loading the page header which is common to all pages of the system and includes the system logo, banner, links and navigation bar;

• Starting a timer that reloads the page intended for the search for a doctor after a certain time determined by the administrator, and a timer that reloads the advertising space after a certain time determined by the administrator; • Loading the advertisement on the page - starting point of the advertisement loading steps;

• Loading personal information from "Advertising Space" - the user's ID parameters are sent to "Advertising Space" for loading advertising images. The received images are loaded into the allocated space on the screen of the user's device 3.i;

• Displaying filter fields "Search for a Doctor" where the following search fields are displayed:

o Region

o Town

o Speciality

o Medical Facility

o Doctor's Name - Surname

o Type of Appointment

o Required Date of Examination.

If the page is called from the box for search for doctor/dentist 3.Ϊ.4, the fields "Region", "Town" and "Doctor's Name - Surname" are loaded according to the information contained in the box.

Upon any change of the values of the filter, the system generates a request to module for search for a doctor 2.2.7 which is processing it and is sending it to the user database 2.1. Follows:

• Loading information from the user database 2.1 as a filtered list of doctors, downloaded from the database;

• Loading the "Results" field - the list from the user browser is displayed;

• Loading box 1 with content preset by the System Administrator (box 1 and box 2 are positions fixed in the user's device 3.i that are dynamically loaded with information or content of some of the module-related boxes. The positions are displayed in all pages and are set for each of them through the module for administration 2.2.2). • Loading personal information from the user database 2.1. The system loads the respective box containing information according to the user's ID parameters and the user's personal data;

• Loading the "Medical Facility" box, by calling and loading box 2, set up by the system administrator;

• Loading personal information from the user database 2.1. The system loads the respective box containing information about the profile of the medical institution specified in the filter;

• Saving the current ID parameters in the user database 2.1. The system saves the current ID parameters (view, timers, etc.)

• Event waiting - steady state in which the system waits for an action to be undertaken by the user;

• Saving the current ID parameters in the user database 2.1. The current ID parameters are recorded if there are changes in the data made by the user in the filter fields or boxes;

• Saving the current ID parameters in the user database 2.1. The system saves the customizations of some boxes or the "Calendar" field;

• Saving the current ID parameters in the user database 2.1. The current parameters of the ID profile are saved when moving from "Search for a Doctor" page to:

o Desktop

o Work Calendar

o Forum, or

o Exit.

• Exit - It is the point for exiting the system or loading any of the forms listed in the block.

System operation when receiving a request for a work calendar and making an appointment for a particular date and time Input parameters. For loading "Working Calendar", the system uses the user's ID parameters and the "Calendar" field loaded on the "Working Calendar" page. At this point, the algorithm can be called from:

• the navigation bar on the header

• the search engine for doctors

• from the box Work calendar

The following steps are performed:

Loading the page header. The header is common to all pages of the system and includes the system logo, banner, links and navigation bar.

Staring a timer that reloads the calendar page after a certain time set by the administrator.

Staring a timer that reloads the advertising space after a certain time set by the administrator.

Loading advertising for "Working Calendar" which is the starting point of the advertisement loading steps.

Loading personal information from "Advertising Space". The user's ID parameters are sent to "Advertising Space" for loading advertising images. The received images are loaded into the allocated space on the screen of the user's device 3.i. Loading the "Calendar" field. Loading the "Calendar" box with a view corresponding to the view of the last use of the module, (daily, weekly or monthly). Loading personal information from the user database 2.1. The list of the doctor's appointments is downloaded from the database. The downloaded list of appointments is loaded in the field according to the selected view in the block. When another owner's calendar is displayed, the fields are completed according to the current user's parameters imposed on those of the owner of the respective calendar. As a result, the user sees only the records concerning the user's rights. All other records of the other owner's calendar are displayed colour-coded and with an icon according to their status parameter:

• Busy time • Free time

Loading box_1 , set up by the system administrator;

Loading personal information from the user database 2.1. The system loads the respective box containing information according to the user's ID parameters and the user's personal data;

Loading box_2. The system calls and loads box 2, set up by the system administrator

Saving current ID parameters in the user database 2.1. Saving current ID parameters (view, timers, etc.)

Event waiting - steady state in which the system waits for an action to be undertaken by the user.

Saving the current ID parameters in the user database 2.1. The system saves the current ID parameters in case of changes made by the user in the calendar fields or boxes.

Saving the current ID parameters in the user database 2.1. The system saves the customizations of some boxes or the "Calendar" field

Saving the current ID parameters in the user database 2.1. The current parameters of the ID profile are saved when moving from "Working Calendar" page to:

• Desktop

• Work Calendar

• Forums or

• Exit.

Exit - It is the point for exiting the system or loading any of the forms listed in the block. Operation of "Lawyer's Blog" and "Medical Audit" modules

Input parameters. For loading "Lawyer's Blog" or "Medical Audit", the system uses the user's ID parameters and the form "Lawyer's Blog" or "Medical Audit", loaded on "Active Page". At this point, the algorithm can be called from:

• box Lawyer's blog 3.Ϊ.5 or box Medical audit 3.i.6

• a direct link via the Internet

• links in other modules

Loading the page header - The header is common to all pages of the system and includes the system logo, banner, links and navigation bar;

Timer - the system starts a timer that reloads the page after a certain time, set up by the administrator.

Timer - the system starts a timer that reloads the advertising space after a certain time, set up by the administrator.

Loading the advertisement on the page - starting point of the advertisement loading steps;

Loading personal information from "Advertising Space". The user's ID parameters are sent to "Advertising Space" for loading advertising images. The received images are loaded into the allocated space on the screen of the user's device 3.i. Evaluation parameter "Page Type" - This page can load two types of content:

• List of topic of blogs

• Topic of a blog.

This block determines what branch of the algorithm to be used for loading the page Loading the "Topic" field.

Request for the content of the topic from the user database 2.1. The system downloads the content, vote and comments on the topic from the database.

Verification of changes - In case of changes (adding a comment or vote), the data should be verified (vote calculation). A modal form can be called from this block. Saving current parameters in the user database 2.1 - The validated changes are recorded in the database

Loading the "List of Topics" field.

Request for customized list of the user database 2.1. The system downloads the customized list of topics from the database.

Loading box_1 - The system calls and loads box 1 , set up by the system administrator

Loading personal information from the user database 2.1. - The system loads the respective box containing information according to the user's ID parameters and the user's personal data.

Loading box_2 - The system calls and loads box 2, set up by the system administrator

Saving the current ID parameters in the user database 2.1. The system saves the current ID parameters in case of changes made by the user in the page field.

Saving the current ID parameters in the user database 2.1. The system saves the current ID parameters in case of changes made by the user when exiting the page. Exit - This is the point for exiting this page.

Operation of "Medical Event Calendar" module

Input parameters. For loading "Event Calendar", the system uses the user's ID parameters and the form "Medical Event Calendar", loaded on "Active Page". At this point, the algorithm can be called from:

• from Box Event calendar 3.i.8.

• from a direct link via the Internet • from links in other modules

Timer - the system sets up a timer that reloads the page after a certain time, determined by the administrator.

Timer - the system sets up a timer that reloads the advertising space after a certain time, determined by the administrator.

Loading the advertisement on the page - Starting point of the advertisement loading steps.

Loading personal information from "Advertising Space" - The user's ID parameters are sent to "Advertising Space" for loading advertising images. The received images are loaded into the allocated space on the screen of the user's device 3.i.

Displaying "Event List" field - The system displays "Event List" field in case of selected event link and calls a modular form with the event website.

Loading personal information from the user database 2.1. - The system loads the field with an event list filtered according to the user's ID parameters.

Loading box Event calendar 3.i.8 - The system calls and loads the box Event calendar 3.L8, set up by the system administrator.

Loading personal information from the user database 2.1. The system sets up the box calendar with information according to the user's ID parameters and the user's personal data; upon selection of a date, the system reloads the field containing the event list.

Event waiting - steady state in which the system waits for an action to be undertaken by the user. Saving the current ID parameters in the user database 2.1. The system saves the current ID parameters in case of changes made by the user when exiting the page. Exit - This is the point for exiting this page.

Operation of the "Inquiry" module

Input parameters. For loading "Inquiries", the system uses the user's ID parameters and the form for the box Inquiries 3.L12 of the module Inquiries 2.2.15. At this point, the algorithm can be called from the page where the box Inquiries 3.Ϊ.12 is displayed.

Loading the box - The system loads the box Inquiries 3.L12 in the position specified by the customization or by the administrator.

Loading personal information from the user database 2.1.

The system loads a customized mini inquiry from the database. In the event that a wider inquiry is required to be displayed, the box Inquiries 3.L12 displays a text and a link to "Active Page" where the inquiry opens.

Loading personal information from "Advertising Space" - The user's ID parameters are sent to "Advertising Space" for loading advertising images. The received images are loaded into the allocated space on the screen of the user's device 3.i. Displaying the "Inquiry" field.

Loading personal information from the user database 2.1. The system loads the inquiry according to the user's ID parameters and the user's personal data; Data validation - Validation of the individual answers

Inquiry validation - Validation of the inquiry integrity

Saving the data input in the user database 2.1.

Saving current ID parameters in the user database 2.1 - The system saves the current ID parameters in case of changes in the user data upon exiting the page Exit - This is the point for exiting this page.

Operation of the "Useful Links" module

Input parameters. For loading "Useful Links", the system uses the user's ID parameters and the form for the box Useful links 3.Ϊ.7 of the module Useful links 2.2.10. At this point, the algorithm can be called from the page where the box is displayed.

Loading the box - The system loads the box in the position specified by the customization or by the administrator.

Loading personal information from the user database 2.1. The system loads a list of useful links. At the end of the list the system loads a personal contacts list. Loading the page header - The header is common to all pages of the system and includes the system logo, banner, links and navigation bar;

Loading personal information from "Advertising Space" - The user's ID parameters are sent to "Advertising Space" for loading advertising images. The received images are loaded into the allocated space on the screen of the user's device 3.i. Displaying the "Useful Links" field

Loading personal information from the user database 2.1. The system loads the list according to the user's ID parameters and the user's personal data;

Data validation - Validation of the values of the input personal "Useful Links" Saving the input data in the user database 2.1.

The operation of the system, as described in the second variant and shown on Fig. 8, is as follows:

System operation when receiving a request for search for another system user, other than a doctor/dentist

This point of operation can be reached from:

• navigation bar on each page

• direct link via the Internet

• links in other modules

To load a page to search for another user, the system uses the user's ID parameters and the form "Search for another user" loaded in the "Active Page", where the operations are carried out in the following sequence:

In the case of user-activated search for another user, the box for search for information 3.Ϊ.15 of the user's device 3.i displays fields to specify the search - county, city, specialty, medical facility related to the searched user. Upon each change of parameters in the fields in the box for search for information 3.Ϊ.15, the user's device 3.i generates a request through the Internet connection to the module for search 2.2.18 that complements the request with parameters derived from the second access verifying component 2.2.5 and transmits it through the sub-module for search for another user 2.2.18.2 to the user database 2.1. In response to the request, the systems provides a list of users' data which is transmitted for visualization via the sub-module for search for another user 2.2.18.2 to the module for users' profiles 2.2.20, which in turn sends the data to the user's device 3.i for visualization in the relevant fields of the box for search for information 3.Ϊ.15. The visualization takes place in the form of a separate line for each result from the user database 2.1 matching the search criteria. The line contains basic user information (name, address, etc.), link to the user profile. If the system fails to find information about any of the fields of the box for search for information 3.Ϊ.15, the module for users' profiles 2.2.20 displays a service message indicating the lack of information on these criteria. The profile of any of the displayed results can be reviewed in detail. This is carried out by the user selection of one of the displayed lines in a field of the box for search for information 3.1.15, resulting in the generation of a request via the Internet connection to the module for users' profiles 2.2.20, which using the second access verifying component 2.2.5 checks the access level of the user who has submitted the request, prepares the relevant request for data and submits it to the user database 2.1. The data obtained through the Internet connection are returned to the user's device 3.i where they are displayed in the box Users' profiles 3.Ϊ.17.

System operation when receiving a request for search by a keyword

For the "Search by a Keyword", the system uses a field of the box for search for information 3.1.15, located in the navigation bar of the site, chronologically carrying out the following steps:

The user types the keyword or text in the field. After the input, the system generates a request from the box for search for information 3.Ϊ.15 of the user's device 3.i via the Internet connection to the module for search 2.2.18. The module for search 2.2.18 complements the request with parameters received from the second access verifying component 2.2.5 and submits it to the search sub- modules - sub-module for search for another user 2.2.18.2 and sub-module for search by a keyword 2.2.18.3, which in turn generate and send search requests to the user database 2.1. In response to these requests, the systems provides lists of users' data, publications and forum topics, which are transmitted for visualization via the sub-module for search for another user 2.2.18.2 to the respective module Publications 2.2.19, module for users' profiles 2.2.20, module Forums control 2.2.14, which in turn send the data to the user's device 3.i for visualization in the relevant fields of the box for search for information 3.Ϊ.15. The visualization takes place in the form of a separate line for each result found in the user database 2.1. The line contains basic information about the publication, user or forum topic, as well as a link indicating the location of the complete information in the user database 2.1. If the system fails to find information about any of the fields of the box for search for information 3.Ϊ.15, the module for search 2.2.18 displays a service message indicating the lack of information on the searched word or string.

System operation upon uploading publications

The home page of the users with rights to upload publications displays an additional uploading bar containing an "Upload¹ button that activates the box Publications 3.Ϊ.16 in the mode of editing new articles. The home page of the users also contains a "Publications" button that activates the box Publications 3.Ϊ.16 in the mode of viewing a list of previously uploaded publications. The activated box Publications 3.L16 prepares a request for a list of publications. The request is transmitted via the Internet connection to the module Publications 2.2.19, which in turn complements the request with parameters received from the second access verifying component 2.2.5 and submits it to the user database 2.1. In response to these requests, the systems provides lists of publication data, which are transmitted via the module Publications 2.2.19 to the user's device 3.i for visualization in the respective fields of the box Publications 3.Ϊ.16. The visualization takes place in the form of a separate line for each result found in the user database 2.1. The line contains basic information about the publication and a link indicating the location of the complete information in the user database 2.1. Moreover, the system displays a link for editing for publications created by the user. From that moment on the user can use the system in three ways - to view a publication from the list, to edit one of his/her already uploaded publications, or to create a new one. In order to view a publication, the user activates the line containing the link to the selected publication. As a result, the box Publications 3.Ϊ.16 sends a request via the Internet to the module Publications 2.2.19, which in turn using the second access verifying component 2.2.5 re-checks the access rights and then transmits it to the user database 2.1. In response to this request, the user database 2.1 provides the full content of the publication which through the module Publications 2.2.19 is transmitted for visualization to the user's device 3.i in the relevant fields of the box Publications 3.L16.

In order to edit a publication, the user activates the line containing the link to the selected publication. As a result, the box Publications 3.Ϊ.16 sends a request via the Internet to the module Publications 2.2.19, which in turn using the second access verifying component 2.2.5 re-checks the access rights and then transmits it to the user database 2.1. In response to this request, the user database 2.1 provides the full content of the publication which through the module Publications 2.2.19 is transmitted for visualization to the user's device 3.i in the relevant fields of the box Publications 3.Ϊ.16. Unlike the methods of review of a publication, the box Publications 3.Ϊ.16 displays additional fields for parameters of the publication. In this state of the system all parameters and text content of the publication are located in the memory of the user's device 3.i. The user can make the required corrections and the upload it again. This is done by activating the "Upload" button located in the box Publications 3.L16, and then the box Publications 3.Ϊ.16 sends the request containing the relevant data via the Internet to the module Publications 2.2.19 which in turn using the second access verifying component 2.2.5 re-checks the access rights and the correctness of the entry of additional parameters. Upon detecting incorrect parameters, the module Publications 2.2.19 generates an error message and via the Internet connection returns it to be displayed by the user's device 3.i in the relevant fields of the box Publications 3.Ϊ.16. These steps are repeated until the correct entry of the additional parameters and then the request is submitted to be recorded in the user database 2.1. In order to create a new publication, the user activates the "Upload" button located in the publications bar. As a result, the box Publications 3.Ϊ.16 sends a request via the Internet to the module Publications 2.2.19, which in turn using the second access verifying component 2.2.5 re-checks the access rights and then returns for visualization to the user database3.i in the box Publications 3.i.16 the respective fields with buttons for selection of the type of publication (article/blog, gallery and video). In the next step the user selects the type of publication. As a result, the box Publications 3.Ϊ.16 sends a request via the Internet to the module Publications 2.2.19, which in turn using the second access verifying component 2.2.5 re-checks the access rights and then returns for visualization to the user database3.i in the box Publications 3.Ϊ.16 the respective fields for entering the content and parameters of the publication. The next step includes loading of content by the user and uploading the publication by activating the "Upload" button located in the box Publications 3.Ϊ.16, and then the box Publications 3.Ϊ.16 sends a recording request containing the relevant data via the Internet to the module Publications 2.2.19 which in turn using the second access verifying component 2.2.5 re-checks the access rights and the correctness of the entry of additional parameters. Upon detecting incorrect parameters, the module Publications 2.2.19 generates an error message and via the Internet connection returns it to be displayed by the user's device 3.i in the relevant fields of the box Publications 3.L16. These steps are repeated until the correct entry of the additional parameters and then the request is submitted to be recorded in the user database 2.1.

Operation for entering of profiles of other system users

The category of other users includes medical professionals, medical institutions, companies operating in the field of healthcare, pharmacists, pharmacies and pharmacy chains, health institutions and organizations, patient organizations and other individuals or legal entities involved in healthcare. The entry of data about doctors, patients, nurses, medical staff servicing the registry and other individuals is similar to that described in the first variant of the system shown in Fig. 7.

The entry of information about medical facilities, companies, patient organizations and other individuals or legal entities involved in healthcare is carried out as follows:

The administrator's work device 4 generates a request for a form for entering a name and administrator of the other relevant system user. The request is transmitted via the Internet connection to the module for administration 2.2.2. The module for administration 2.2.2 checks the access level using the first access verifying component 2.2.1 and returns a form containing the relevant fields of the name of "other user" type object, address, administrator's name, password, etc. The returned form is displayed on the administrator's work device 4. This is followed by completing the data and activating the "Upload" button located in the form, and then the administrator's work device 4 sends the recording request containing the relevant data via the Internet to the module for administration 2.2.2 which in turn using the first access verifying component 2.2.1 re-checks the access rights and the correctness of the data entered. Upon detecting incorrect or missing data, the module for administration 2.2.2 generates an error message and via the Internet connection returns it to be displayed and corrected on the administrator's work device 4. These steps are repeated until the correct entry of the data and then the request is submitted to be recorded in the user database 2.1. As a result, the system now has a registered user of the "other user" category and an account of that user's administrator. The full information for that user (e.g. medical facility, pharmaceutical company, etc.) is completed by the respective administrator who is required to log in through that administrator's the user's device 3.i with the officially assigned username and password and using the box for search for information 3.1.15, where the administrator completes all the fields allocated for the relevant user whose administrator he/she is. The box for search for information 3.Ϊ.15 of the user's device 3.i generates via the Internet connection a request to the module for search 2.2.18. The module for search 2.2.18 complements the request with parameters received from the second access verifying component 2.2.5 and submits it through the sub-module for search for another user 2.2.18.2 to the user database 2.1. In response to the request, the systems provides data about the searched other user which is transmitted for visualization via the sub-module for search for another user 2.2.18.2 to the respective module for users' profiles 2.2.20, which in turn sends the data to the user's device 3.i for visualization in the relevant fields of the box for search for information 3.Ϊ.15. The visualization takes place in the form of a single line matching the search criteria. The line contains basic user information about the object (name, address, etc.) and a link to the respective profile. The administrator is required to activate the link from the box for search for information 3.Ϊ.15, as a result of which the box for search for information 3.L15 generates via the Internet connection a request to the module for users' profiles 2.2.20, which using the second access verifying component 2.2.5 checks the access level of the user who has submitted the request, prepares the relevant request for data and submits it to the user database 2.1. The data obtained through the Internet connection are returned to the user's device 3.i where they are displayed in the box Users' profiles 3.Ϊ.17. The visualization is in the "Data Review" mode and only shows information available in the user database 2.1. For administrators, this form also contains an "Edit" button. In order to edit or supplement the information visualized, the administrator is required to activate it. This activation results in generating of a request by the box Users' profiles 3.Ϊ.17 of the user's device 3.i via the Internet to the module for users' profiles 2.2.20. With the receipt of this request, the module for users' profiles 2.2.20 re-checks the access rights using the second access verifying component 2.2.5 and then transmits it to the user database 2.1. In response to this request the user database 2.1 provides the full content of the data and their parameters to the edited profile. The information completed in the above manner is returned via the Internet connection to the box Users' profiles 3.Ϊ.17 of the user's device 3.i for editing. After completing the editing, the administrator is required to activate the "Record" button and then the box Users' profiles 3.Ϊ.17 of the user's device 3.i sends a recording request containing the relevant data via the Internet to the module for users' profiles 2.2.20 which in turn using the second access verifying component 2.2.5 re- checks the access rights and the correctness of the data entered. Upon detecting incorrect data, the module for users' profiles 2.2.20 generates an error message and via the Internet connection returns it to be displayed by the user's device 3.i in the relevant fields of the box Users' profiles 3.1.17. These steps are repeated until the correct entry of the data and then the request is submitted to be recorded in the user database 2.1. In edit mode the box Users' profiles 3.Ϊ.17 also contains buttons for entering additional information about the particular type of user. These buttons generate the relevant forms and requests for visualization and completion in a manner analogous to the above-described, check the correctness of the data entered and store them in the user database 2.1.

The other requests are implemented by the modules of the dedicated module for management and provision of information to users 2.2, identical to the corresponding modules of the first variant of the exemplary implementation (Fig. 7) and labelled with identical numbers in a similar way.

References:

[1] CN202602673 (U)

[2] US 6757898 B1

[3] BG 1652 U1

Claims

PATENT CLAIMS

1. A method of communication between users, in particular between doctors/dentists and patients, characterized by the implementation of the following operations:

- receiving a request for access to information and/or search for a doctor/dentist via the Internet from the user's device;

- performing a verification check to identify the type of request and determine the type of the user, where: a) in case of a new user - patient or doctor/dentist - the system generates an identification code of the user, registers the code with the SQL database that services the "Open ID" server-client technology and determines the access level; then this user's registration is recorded in the user array of the user database; b) in case of a request by a registered user - a patient - the request is forwarded to the user database; c) in case of a request by a doctor/dentist, the system checks the compliance with the specifications for the doctor/dentist's access level and competence, then the request is forwarded to the user database;

- processing the request depending on its type and the user's access level by retrieving relevant information from the user database associated with the search for a doctor/dentist, and/or a doctor/dentist/s work calendar, and/or making an appointment with the doctor/dentist, or articles for patients or doctors, or information about useful links, or a calendar of events, or conducting inquiries or forums, whereas the information is displayed on the appropriate user's device and if access is requested to a work calendar and/or making an appointment with the respective doctor/dentist, the two- way communication between the users is carried out via the Internet, in particular between patients and doctors/dentists in order to specify the appointment date and time;

- in case of a request by a user - a patient and/or a doctor/dentist - the information on the type of request and the type of the user-assigned access is sent to

1 the banner system, and the relevant user's device receives and displays an advertising banner corresponding to the user's access level, where the parameters such as size, duration, time of displaying each advertising banner and the sequence of displaying the banners of the relevant advertising campaign are predetermined and preset in the banner system.

2. The method according to Claim 1 , characterized in that upon receiving a request for search for a doctor/dentist, the system generates drop-down menus where the user is allowed to select and/or fill in sequentially parameters such as region, town, medical facility, specialty and/or name and/or surname of the doctor/dentist and the type of appointment; then this information is forwarded to the user database, where the system derives information from the doctor/dentist data arrays; the obtained information is filtered and sorted according to the rating of doctors/dentists and their unreserved appointment times, after which the information is displayed to the user.

3. The method according to Claim 2, characterized in that the doctors/dentists' rating is determined after each appointment by generating and sending to the user a message containing questions that are recorded automatically at the time of answering and the data received are processed accordingly.

4. The method according to Claim 1 characterized in that upon receiving a request for making an appointment with a particular doctor/dentist for a consultation and/or an examination of a patient, the system generates a calendar including the schedule of each medical offices with interfaces covering respectively the daily, weekly, monthly calendar within the year and colour-coded unreserved and reserved appointment times; and then:

- the display at the patient working station allows the user to mark an appointment date and time on the doctor/dentist's calendar with a "pending confirmation" status; then the doctor/dentist confirms and/or rejects and/or marks a new appointment date and time which is automatically recorded to be notified to the patient and the actual appointment time is then reserved;

- at the doctor/dentist's display the system generates a calendar which contains a list of patients, confirmation and/or amendment of appointments for consultation or

2 examination and/or archiving the implemented consultations or examinations or events; whereas in case of a request for making an appointment for a new consultation or examination, the doctor/dentist can select or enter a patient's name taken from the list of registered patients, or the name of a new unregistered patient, or a personal commitment of the doctor/dentist; whereas upon determining a specific date and time of appointment the system starts a feature assigning to the reserved appointment a "deadline for confirmation" by the patient;

- after the appointment is agreed, the "pending confirmation" status changes to "confirmed" and the system generates a message stating the agreed appointment that is sent to the patient and the doctor/dentist.

5. The system for communication between users, in particular between a doctors/dentists and patients, employing at least one server, characterized in that it comprises two servers (1 ) and (2), where the first server (1 ) hosts a SQL database (1.1 ) operating the "Open ID" server-client technology; while the second server (2) hosts the user database (2.1 ) with two-way connected dedicated module for management and provision of information to users (2.2), and the second server (2) through the dedicated module for management and provision of information to users (2.2) is connected via the internet to "n" user's devices (3), to the administrator's work device (4) and to the first server (1 ).

6. The system as claimed in Claim 5, characterized in that the second server (2) includes module Banner system (2.4), module for electronic communication (2.5) and a module Forums (2.3), each connected bidirectionally to the user database (2.1 ) and to the dedicated module for management and provision of information to users (2.2), through which the module Banner system (2.4) and the module for electronic communication (2.5) are connected via the Internet to the administrator's work device (4); the module Banner system (2.4) and the module Forums (2.3) are connected through the dedicated module for management and provision of information to users (2.2) and via the Internet to the appropriate user's device (3.i); while the module for electronic communication (2.5) is connected directly to the Internet.

3

7. The system, as claimed in Claim 5, is characterized in that the dedicated module for management and provision of information to users (2.2) contains a module for registration (2.2.4) and a module for doctor/dentist's authentication (2.2.3), and both modules (2.2.4 and 2.2.3) are two-way connected to each other, while each of them has a respective input and output that are the input and output of the dedicated module for management and provision of information to users (2.2) for a two-way connection to the user database (2.1 ), whereas the module for doctor/dentist's authentication (2.2.3) is two-way connected to the first access verifying component (2.2.1 ) and has an output that is the output of the dedicated module for management and provision of information to users (2.2) for a two-way connection to the Internet, and the module for registration (2.2.4) is connected to the second access verifying component (2.2.5) with an input and output that are the inputs and outputs of the dedicated module for management and provision of information to users (2.2) for connection via the Internet to the appropriate user's device (3.i) and to the user database (2.1), whereas the first access verifying component (2.2.1 ) has shared inputs and outputs with the dedicated module for management and provision of information to users (2.2) intended for connection respectively to the user database (2.1 ) and via the Internet to the administrator's work device (4), while one of its outputs is connected to the module for administration (2.2.2), which has shared inputs and outputs with the dedicated module for management and provision of information to users (2.2) intended for connection respectively to the user database (2.1 ) and via the Internet to the administrator's work device (4), and one of the outputs of the module for administration (2.2.2) is an output of the dedicated module for management and provision of information to users (2.2) intended for connection respectively to the inputs of the module Banner system (2.4) and to the module for electronic communications (2.5); whereas the module for registration (2.2.4) is two-way connected via the Internet to the relevant user's device (3.i) and has an input and an output intended for connection to the first server (1 ), and the dedicated module for management and provision of information to users (2.2) also contains a module for search for a doctor/dentist (2.2.7), two-way connected with the module Work calendar (2.2.6), the module Lawyer's blog (2.2.8), the module Medical audit (2.2.9), the module Articles for doctors (2.2.12), the module Useful links (2.2.10), the module Event

4 calendar (2.2.1 1 ), the module Forums control (2.2.14), the module Inquiries (2.2.15), the module Videos (2.2.16), and the module Advertising space (2.2.17), and each of the aforementioned modules has an input and an output for connection to the user database (2.1), and the inputs of these modules are connected to the output of the second access verifying component (2.2.5) and two-way connected via the Internet to the corresponding user's device (3.i), which displays the module-related functionally corresponding boxes, namely: box Registration form (3.i.1 ), box User login forms (3.i.2), box Work calendar (313), box for search for a doctor/dentist (3.i.4), box Lawyer's blog (3.Ϊ.5), box Medical audit (316), box Useful links (3.i.7), box Event calendar (3.i.8), box Articles for doctors (3.i.9), box Articles for patients (3.Ϊ.10), box Forums (311 1), box Inquiries (3112), box Videos (3.i.13), and box Advertising space (3114) and the module Forums control (2.2.14) has shared input and output with the dedicated module for management and provision of information to users (2.2) intended for connection to the standard module Forums (2.3), the module Advertising space (2.2.17) is connected to the module for administration (2.2.2) and has shared input and output with the dedicated module for management and provision of information to users (2.2) intended for connection to the module Banner system (2.4).

8. The system as claimed in Claim 5 characterized in that the dedicated module for management and provision of information to the users (2.2) includes a module for registration (2.2.4) and a module for doctor/dentist's authentication (2.2.3), which are two-way connected with one another, and the module for doctor/dentist's authentication (2.2.3) is two-way connected to the first access verifying component

(2.2.1) , whereas one of its outputs is connected to the module for administration

(2.2.2) , which has a shared output with the dedicated module for management and provision of information to users (2.2) intended for connection respectively to the module Forums (2.3), the module Banner system (2.4) and to the module for electronic communication (2.5), where the first access verifying component (2.2.1 ), the module for administration (2.2.2) and the module for doctor/dentist's authentication (2.2.3) have inputs and outputs respectively that are an input and an output of the dedicated module for management and provision of information to users (2.2) for two-way

5 connection via Internet to the administrator's work device (4), and inputs and outputs respectively that are an input and an output of the dedicated module for management and provision of information to users (2.2) intended for two-way connection to the user database (2.1 ), and the module for registration (2.2.4) is connected to the second access verifying component (2.2.5), to which the module Work calendar (2.2.6), the module for search (2.2.18), module Publications (2.2.19), module for users' profiles

(2.2.20) , module Forums control (2.2.14), module Useful links (2.2.10), module Event calendar (2.2.1 1 ), module for internal communication (2.2.21 ), and module Advertising space (2.2.17) are two-way connected, where the module for search (2.2.18) includes a sub-module for search for a doctor/dentist (2.2.18.1 ), a sub-module for search for another user (2.2.18.2), and a sub-module for search by a keyword (2.2.18.3), and is one-way connected via the sub-module for search for a doctor/dentist (2.2.18.1) to the module for users' profiles (2.2.20), and via the sub-module for search by a keyword (2.2.18.3) - to the input of the module Publications (2.2.19), to the input of the module for users' profiles (2.2.20) and to the input of the module Forums control (2.2.14), and via the sub-module for search for another user (2.2.18.2) it is connected to the input of the module for users' profile (2.2.20), and the module for users' profiles (2.2.20) is two- way connected to the module Work calendar (2.2.6), where the module Forums control (2.2.14) has an input and an output which are an input and an output of the dedicated module for management and provision of information to users (2.2) intended for two- way connection to the module Forums (2.3), the module for internal communications

(2.2.21 ) has an input which is the input of the dedicated module for management and provision of information to users (2.2) intended for connection to the output of the module for administration (2.2.2), and each of the modules for registration (2.2.4), Work calendar (2.2.6), for search (2.2.18), Publications (2.2.19), for users' profiles (2.2.20), Forums control (2.2.14), Useful links (2.2.10), Event calendar (2.2.11), for internal communications (2.2.21 ), Advertising space (2.2.17), and the second access verifying component (2.2.5) has shared inputs and outputs with the dedicated module for management and provision of information to users (2.2) respectively for two-way

6 connection to the user database (2.1 ) and for two-way connection via the Internet to the relevant user device (3.i), displaying the boxes corresponding to the function of the modules, namely: the box Registration form (3.i.1 ), box User login forms (3.L2), box Work calendar (3.i.3), box Useful links (3.i.7), box Event calendar (3.L8), box Forums (3.1.1 1 ), box Advertising space (3114), box for search for information (3.i.15), box Publications (3116), box Users' profiles (3117), and box Internal communication (3118).

9. The system as claimed in Claim 5, characterised in that the user database (2.1) on the second server (2) contains separate arrays of user identification data - of doctors/dentists, patients, health care professionals, array of workplaces with sub- array of working time and array of medical specialties and specializations of doctors/dentists, array of work contacts and array of the calendar of medical events.

10. The system as claimed in Claim 9, characterized in that the user database includes an array of users other than doctors/dentists and an array of products and/or services offered by users.

7