EP2989577A2 - Procédé et système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients - Google Patents

Procédé et système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients

Info

Publication number
EP2989577A2
EP2989577A2 EP14734716.5A EP14734716A EP2989577A2 EP 2989577 A2 EP2989577 A2 EP 2989577A2 EP 14734716 A EP14734716 A EP 14734716A EP 2989577 A2 EP2989577 A2 EP 2989577A2
Authority
EP
European Patent Office
Prior art keywords
module
user
users
information
doctor
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
EP14734716.5A
Other languages
German (de)
English (en)
Inventor
Peter Grigorov VELEV
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Credoweb Ltd
Original Assignee
Credoweb Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from BG111542A external-priority patent/BG66817B1/bg
Application filed by Credoweb Ltd filed Critical Credoweb Ltd
Publication of EP2989577A2 publication Critical patent/EP2989577A2/fr
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H80/00—ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms

Definitions

  • 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.
  • 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.
  • 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.
  • 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 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.
  • 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).
  • 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.
  • 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.
  • the information provider and generator is the doctor who provides information to the registered patients under his/her cares.
  • BG 1652 U1 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.
  • 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.
  • the component recognizing the user as a new user or as an already known user on the network is dd-wrt software
  • the component for providing access to an affiliated website is a http server and user
  • 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.
  • 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.
  • 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 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.
  • 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.
  • the request is filed by a registered user - patient, this request is forwarded to the user database to retrieve and provide the relevant information.
  • the system checks for the user's access level and certifies the doctor's competence.
  • the request is forwarded for processing and provision of relevant information.
  • 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.
  • the system sends information about the user type and 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.
  • the 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 parameters such as region, town, medical facility of the doctor/dentist searched, doctor/dentist's specialty, name and/or surname, and type of appointments.
  • 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.
  • the system 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.
  • 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.
  • 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.
  • the system sets the deadline for confirmation of the appointment by the patient.
  • the system verifies the authorization of the person to perform the above described actions.
  • the system for communication between users 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • a user device 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.
  • the user skips registration he/she is limited to using a demonstration (demo) version of the communication method.
  • this request is filed by a registered user - patient, this request is forwarded for processing and the system retrieves and provides the relevant information.
  • the system 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.
  • the system 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.
  • the system 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.
  • the patient can log in to create a profile or to enter the menu of registered patients.
  • the system 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.
  • 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.
  • the system 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.
  • the system 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.
  • Additional data are entered relating to the request for making an appointment, such as symptoms, test data, past medical history
  • 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.
  • 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.
  • the system also sets the deadline for confirmation of the appointment by the patient.
  • the appointment is recorded in the user database with status "appointment pending confirmation by the patient".
  • 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.
  • the system 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.
  • the 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).
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the submission of the requested information to users is filtered by type depending on the type of the particular user.
  • the system can be used for communication between doctors, between doctors and medical facilities, as well as between medical facilities, institutions and patients.
  • the system operates by using modules and database saved on disk drives.
  • 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).
  • http hyper-terminal protocol requests
  • 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.
  • server 2 returns one of the four user input forms:
  • the following operation of the system is determined by the algorithm of actions and the request selected by the user.
  • the user connects from the user's device to the servers via the Internet.
  • 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.
  • 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.
  • the system 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.
  • 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.
  • the displayed image contains an error message and form to correct it.
  • server 1 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.
  • 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.
  • 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.
  • 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.
  • ID system identifier
  • the dedicated module for management and provision of information to users 2.2 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.
  • 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.
  • 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 uses 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 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.
  • 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.
  • the system 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.
  • the module for registration 2.2.4 prepares and sends an electronic notification letter to the person requested the registration.
  • the dedicated module for management and provision of information to users 2.2 in server 2 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.
  • 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.
  • 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.
  • 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 uses 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 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.
  • 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.
  • 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.
  • the second access verifying component 2.2.5 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.
  • 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.
  • 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.
  • the browser of the user's device 3.i displays the relevant desktop elements and boxes.
  • 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.
  • the dedicated module for management and provision of information to users 2.2 in server 2, which activates the respective module in the RAM.
  • 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 user's device receives a page with fields where the patients are allowed to fill in their username and password for access.
  • the user's device 3.i 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
  • 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.
  • 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.
  • the system 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.
  • 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).
  • Event waiting - steady state in which the system waits for an action to be undertaken by the user
  • the header is common to all pages of the system and includes the system logo, banner, links and navigation bar.
  • 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).
  • 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.
  • 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:
  • 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
  • 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;
  • 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.
  • the system saves the current ID parameters in case of changes made by the user in the calendar fields or boxes.
  • 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.
  • This block determines what branch of the algorithm to be used for loading the page Loading the "Topic" field.
  • 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
  • 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 box_2 The system calls and loads 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 according to the user's ID parameters and the user's personal data;
  • Event waiting - steady state in which the system waits for an action to be undertaken by the user.
  • the header is common to all pages of the system and includes the system logo, banner, links and navigation bar.
  • 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.
  • Event List 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.
  • 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.
  • Loading box_2 The system calls and loads 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 according to the user's ID parameters and the user's personal data;
  • 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.
  • 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.
  • the system loads the box Inquiries 3.L12 in the position specified by the customization or by the administrator.
  • the system loads a customized mini inquiry from the database.
  • the box Inquiries 3.L12 displays a text and a link to "Active Page" where the inquiry opens.
  • the header is common to all pages of the system and includes the system logo, banner, links and navigation bar;
  • 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 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
  • 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
  • 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;
  • Event waiting - steady state in which the system waits for an action to be undertaken by the user.
  • 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;
  • 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 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;
  • 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
  • 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;
  • 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.
  • 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:
  • 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.
  • the user's device 3.i 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.
  • 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.
  • 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 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.
  • the system 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.
  • 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.
  • the home page of the users with rights to upload publications displays an additional uploading bar containing an "Upload 1 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.
  • 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.
  • 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.
  • the user activates the line containing the link to the selected publication.
  • 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.
  • 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.
  • 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.
  • 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.
  • the box Publications 3. ⁇ .16 displays additional fields for parameters of the publication.
  • 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.
  • the module Publications 2.2.19 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.
  • 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 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.
  • the module for administration 2.2.2 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.
  • 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.
  • 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.
  • 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.
  • the administrator 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.
  • the administrator 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.
  • buttons for entering additional information about the particular type of user 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.

Abstract

La présente invention se rapporte à un procédé et à un système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients, pouvant être utilisés dans le domaine des soins de santé. Le procédé consiste à : recevoir une demande d'accès à des informations et/ou de recherche d'un médecin/dentiste par Internet depuis le dispositif d'utilisateur ; vérifier et identifier le type de la demande et le type de l'utilisateur et traiter la demande en fonction de son type et du niveau d'accès de l'utilisateur et fournir à l'utilisateur des informations complètes, sélectionnées et fiables apparaissant sur le dispositif d'utilisateur approprié. Le système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients, permet une communication directe entre les utilisateurs. Le système se compose de deux serveurs, le premier serveur (1) hébergeant la base de données SQL (1.1) au service de la technologie client-serveur "Open ID", tandis que le second serveur (2) héberge la base de données d'utilisateur (2.1) avec un module dédié à connexion bidirectionnelle (2.2) pour la gestion et la fourniture d'informations à des utilisateurs. Le module dédié pour la gestion et la fourniture d'informations à des utilisateurs (2.2) est mis en œuvre dans deux variantes.
EP14734716.5A 2013-04-22 2014-04-22 Procédé et système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients Ceased EP2989577A2 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
BG239613 2013-04-22
BG111542A BG66817B1 (bg) 2013-07-25 2013-07-25 Метод и система за комуникация между потребители, по-специално между лекари/стоматолози и пациенти
PCT/BG2014/000018 WO2014172761A2 (fr) 2013-04-22 2014-04-22 Procédé et système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients

Publications (1)

Publication Number Publication Date
EP2989577A2 true EP2989577A2 (fr) 2016-03-02

Family

ID=51062579

Family Applications (1)

Application Number Title Priority Date Filing Date
EP14734716.5A Ceased EP2989577A2 (fr) 2013-04-22 2014-04-22 Procédé et système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients

Country Status (3)

Country Link
EP (1) EP2989577A2 (fr)
CA (1) CA2909525A1 (fr)
WO (1) WO2014172761A2 (fr)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104599212A (zh) * 2015-02-24 2015-05-06 王学庆 一种腹膜透析网络客户端智能协助管理系统及方法
JP6747868B2 (ja) * 2015-05-22 2020-08-26 メディア株式会社 歯科予約装置、及び同システム並びに同プログラム、記憶媒体
CN113593721A (zh) * 2021-06-30 2021-11-02 广州市健齿生物科技有限公司 一种医工交互方法、装置及设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6141010A (en) * 1998-07-17 2000-10-31 B. E. Technology, Llc Computer interface method and apparatus with targeted advertising
US6757898B1 (en) 2000-01-18 2004-06-29 Mckesson Information Solutions, Inc. Electronic provider—patient interface system
GB2466022A (en) * 2008-12-08 2010-06-09 Self Refer Ltd Selecting service providers and secure information exchange for medical appointments.
CN202602673U (zh) 2012-05-18 2012-12-12 北京华录亿动科技发展有限公司 医患信息交流系统
BG1652U1 (bg) 2012-06-12 2013-01-31 "Fri Ouay Fay.Bg" Ood " ООД"ФРИ УАЙ ФАЙ.Б Система за предоставяне на интернет достъп

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
None *
See also references of WO2014172761A2 *

Also Published As

Publication number Publication date
WO2014172761A3 (fr) 2015-03-05
WO2014172761A2 (fr) 2014-10-30
CA2909525A1 (fr) 2014-10-30

Similar Documents

Publication Publication Date Title
US20220138689A1 (en) Generation and Data Management of a Medical Study Using Instruments in an Integrated Media and Medical System
US7438228B2 (en) Systems and methods for managing electronic prescriptions
US7286997B2 (en) Internet-based, customizable clinical information system
US10468130B1 (en) System and method for automatically generating a prescription refill order via a reply electronic message
US8131560B2 (en) Systems and methods for managing regulatory information
EP1174816A2 (fr) Méthode et système de traitement en ligne de maladie chronique et de bien-être
US20090216562A1 (en) Method and apparatus for accommodating diverse healthcare record centers
US20140058753A1 (en) Professional networking platform with ranked patient information delivery
US20110131059A1 (en) Pharmacy benefits management method and apparatus
US20090112627A1 (en) Method and System for Creating, Assembling, Managing, Utilizing, and Securely Storing Portable Personal Medical Records
US20160098542A1 (en) Medical diagnosis and treatment support apparatus, system, and method
US20060259331A1 (en) Medical records website and related methods
US20190096019A1 (en) System and method for implementing a diagnostic software tool
US20080103371A1 (en) Interactive method for facilitating patient compliance during a healthcare protocol
US20030061073A1 (en) Method and system for displaying patient information
US20210103939A1 (en) Computerised system and method for matching a user to a caregiver or a caregiving facility
CA3007791A1 (fr) Acces mobile coordonne a des dossiers medicaux electroniques
US7464043B1 (en) Computerized method and system for obtaining, storing and accessing medical records
US20160335400A1 (en) Systems and methods for managing patient-centric data
WO2014172761A2 (fr) Procédé et système de communication entre utilisateurs, en particulier entre des médecins/dentistes et des patients
US10572630B1 (en) Refill prescription by calendar reminder
US20110213622A1 (en) Healthcare information management and communications system and method
US11322230B2 (en) System and method for generating and implementing a stateless patient history module
WO2013126735A1 (fr) Procédé et système de fourniture de contenu spécifique au patient
US20130238354A1 (en) Contemporaneous, multi-physician, online consultation system

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20151028

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

DAX Request for extension of the european patent (deleted)
17Q First examination report despatched

Effective date: 20170607

REG Reference to a national code

Ref country code: DE

Ref legal event code: R003

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN REFUSED

18R Application refused

Effective date: 20180904