A disease data management system

Abstract

The application provides a disease data management system, which comprises a health record module, a doctor-patient relationship establishing module, a medical guidance and tracking module, and a case sharing module. The health record module is used for generating health records of patients and forming a health record library. The doctor-patient relationship establishing module is used for determining a target health record from the health record library, wherein the target health record corresponds to a target patient who is an object of follow-up guidance and treatment by a target doctor. The medical guidance and tracking module is used for tracking and recording process data of the target doctor in the guidance and treatment of the target patient. The same-disease patient analysis module is used for analyzing and counting process data generated by the treatment of different patients and the health records of the different patients, so as to generate case data of various types of diseases. The case sharing module is used for sharing guidance articles created by doctors based on the case data. The disease data management system provided by the application can realize the tracking management of disease data of patients and provide a learning platform for communication and exchange for doctors.

Description

Technical Field

[0001] This application relates to the field of data management technology, and more specifically, to a disease data management system. Background Technology

[0002] Currently, patients seeking treatment for their illnesses must visit hospitals, undergoing cumbersome procedures and lengthy waiting times to receive guidance on their specific conditions. Even after receiving treatment, the lack of a unified platform for managing patients' diagnostic records and past health data hinders doctors' research on different diseases. This makes it difficult to formulate opinions that can be shared with other doctors or provide guidance to patients. Therefore, how to achieve the tracking and management of patient disease data and establish a learning platform for doctors to communicate and exchange ideas is a pressing technical problem that needs to be solved. Summary of the Invention

[0003] The embodiments of this application provide a disease data management system that enables doctors to proactively discover and guide the treatment of patients' diseases, tracks and manages patients' disease data and health status data, and provides a learning platform for doctors to communicate and exchange information.

[0004] Specifically, the technical solution of this application is as follows:

[0005] This application provides a disease data management system, comprising: a health record module for collecting and processing patients' health status data and daily routine data to generate a health record database, the health record database consisting of health records of different patients; a doctor-patient relationship establishment module for identifying target health records from the health record database, the target patient corresponding to the target health record being the subject of follow-up guidance and treatment by the target doctor; a medical guidance and tracking module for tracking and recording the process data of the target doctor guiding the target patient; a similar patient analysis module for analyzing and statistically analyzing the process data generated by the guided treatment of different patients and the health records of different patients to generate case data for various types of diseases; and a case sharing module for sharing guidance articles created by doctors based on the case data.

[0006] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: a health data acquisition module for collecting patients' health status data; a rest and activity statistics module for collecting and statistically analyzing patients' rest and activity times to obtain patients' rest and activity data; a disease tagging module for determining the patient's disease tag based on the patient's health status data; and a data processing module for generating the patient's health record based on the health status data, the rest and activity data, and the disease tag.

[0007] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: a focus area report recommendation module, used to recommend health records to the target doctor based on the medical fields of focus of the target doctor; a health record sorting module, used to sort the health records based on the occupancy score of each health record, wherein the occupancy score is used to characterize the degree of attention of the disease tag corresponding to the health record; a search query module, used to search and query health records; and a health record selection module, used to determine the target health record through the focus area report recommendation module, the health record sorting module, and the search query module.

[0008] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: a doctor-patient communication module, which is used for online communication between the target doctor and the target patient.

[0009] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: the doctor-patient communication module is also used to invite other doctors to jointly follow up and guide the treatment of the target patient.

[0010] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: a case data editing module for generating guidance articles created by doctors based on the case data; a case data tagging module for tagging the guidance articles with corresponding article tags; and an intelligent data push module for pushing matching guidance articles to doctors or patients based on the article tags.

[0011] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: a data storage module, which is used to store the health record database, case data of the various types of diseases, and the guidance articles.

[0012] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: the data storage module is also used to manage the viewing permissions of doctors or patients to the health record database and the case data of the various types of diseases.

[0013] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: a calling interface set in the data storage module, the calling interface being connected to the doctor-patient relationship establishment module and the case sharing module respectively.

[0014] In some embodiments of this application, based on the foregoing scheme, the disease data management system further includes: the system further includes a login module, which is used to provide doctors or patients with an entry point to the disease data management system.

[0015] This application provides a disease data management system. By setting up a health record module, it enables the acquisition of patients' historical health status and daily routine data, thereby creating corresponding health records for different patients. This allows for unified analysis and management of patients' disease data. The system also includes a doctor-patient relationship establishment module, enabling doctors to proactively identify target health records from the health record database, thus establishing a doctor-patient relationship for proactive guidance and treatment. Furthermore, the system includes a medical guidance and tracking module, which tracks and records the process data of doctors guiding and treating patients, providing data support for doctors' disease research. A similar patient analysis module automatically generates case data for various types of diseases, providing doctors with rich case data to aid in in-depth research. Finally, a case sharing module allows the system to recommend guidance articles based on case data to different doctors or patients, providing doctors with a communication and learning platform. Attached Figure Description

[0016] Figure 1 A schematic diagram of the architecture of a disease data management system according to an embodiment of this application is shown.

[0017] Figure 2 A schematic diagram of the architecture of a health record module according to an embodiment of this application is shown.

[0018] Figure 3 A schematic diagram of the architecture of a doctor-patient relationship establishment module according to an embodiment of this application is shown.

[0019] Figure 4 A schematic diagram of the architecture of a case sharing module according to an embodiment of this application is shown.

[0020] The annotations in the attached figures are explained as follows:

[0021] 100—Health Record Module, 110—Health Data Collection Module

[0022] 120—Day and Night Schedule Statistics Module, 130—Disease Tagging Module

[0023] 140—Data Processing Module

[0024] 200—Module for establishing doctor-patient relationships; 210—Module for recommending reports on areas of focus.

[0025] 220—Health record sorting module; 230—Search query module.

[0026] 240—Health Record Selection Module

[0027] 300—Doctor-Patient Communication Module

[0028] 400—Medical guidance and tracking module,

[0029] 500—Similar Patient Analysis Module

[0030] 600—Case Sharing Module, 610—Case Data Editing Module

[0031] 620—Case Data Tagging Module, 630—Intelligent Data Push Module

[0032] 700—Data storage module,

[0033] 800 — Login module. Detailed Implementation

[0034] Typical embodiments embodying the features and advantages of this application will be described in detail in the following description. It should be understood that this application can have various variations in different embodiments, all of which do not depart from the scope of this application, and the descriptions and illustrations therein are for illustrative purposes only and not intended to limit this application.

[0035] In the description of this application, it should be noted that the terms "vertical", "up", "down", "horizontal", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the system or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0036] In the description of this application, it should also be noted that, unless otherwise expressly specified and limited, the terms "set," "install," "connect," and "link" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; and they can refer to the internal connection of two components. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0037] It should be noted that in this application, all employees of the company can be considered as patients, or users with diseases can be considered as patients.

[0038] This application provides a disease data management system. To enable those skilled in the art to better understand the disease data management system proposed in this solution, the following will be combined with... Figures 1 to 4 Please provide a detailed explanation.

[0039] See Figure 1 The diagram shows a simplified schematic representation of the structure of a disease data management system according to an embodiment of this application.

[0040] like Figure 1 As shown, a possible disease data management system according to this application is illustrated, including a health record module 100, a doctor-patient relationship establishment module 200, a doctor-patient communication module 300, a medical guidance and tracking module 400, a similar patient analysis module 500, a case sharing module 600, a data storage module 700, and a login module 800.

[0041] The health record module 100 is used to collect and process patients' health status data and daily routine data to generate a health record library, which consists of health records of different patients.

[0042] It should be noted that in the health record module 100, the health status data of different patients will be analyzed and modeled using daily routine data to form health records (i.e., health profiles) for different patients. The health records are equivalent to the patient's health database, which can reflect the patient's current and historical health status.

[0043] In some embodiments, the health record module 100 is as follows: Figure 2 The modules shown are composed of...

[0044] For details, see Figure 2 The diagram shows an architectural schematic of a health record module according to one embodiment of this application.

[0045] The health record module 100 includes a health data acquisition module 110, which is used to collect the patient's health status data.

[0046] In some implementations, the health status data can reflect the patient's current and past health status, including but not limited to the patient's basic information (such as blood type, age, height, etc.), past medical history, allergy history, history of adverse drug reactions, medical records, medication records, examination records (such as blood test data), etc. Specifically, the type of health status data collected can be designed according to the specific application scenario, and this application does not limit it here.

[0047] In some implementations, the health data acquisition module 110 can obtain the patient's health status data by importing the patient's medical examination reports from previous years.

[0048] In some implementations, the health data acquisition module 110 can also input the patient's health status data through an input editing process, such as inputting the collected patient's health status data into the disease data management system through the health acquisition module.

[0049] In some implementations, the health data acquisition module 110 can also collect the patient's health status data via a smart wearable device. For example, it can acquire the patient's electrocardiogram (ECG) data through a wearable ECG monitoring device.

[0050] See also Figure 2 The health record module 100 also includes a daily routine statistics module 120, which is used to collect and statistically analyze the patient's daily routine to obtain the patient's daily routine data.

[0051] In some implementations, the daily routine data includes, but is not limited to, the patient's nighttime sleep duration, afternoon nap duration, work hours, etc. It is understood that the daily routine statistics module 120 can convert the collected patient's daily routine time into patient routine data through statistical calculations. For example, the daily routine statistics module 120 can collect the patient's wake-up time and sleep time, and determine the patient's sleep duration routine data through statistical calculations.

[0052] In some implementations, if all employees of the company are considered as patients, the work and rest statistics module 120 can be connected to the company's attendance system to obtain the patients' daily attendance records and the patients' work and rest times collected in the attendance system, so as to obtain the patients' work and rest data.

[0053] In some implementations, the daily routine statistics module 120 can also collect patients' daily routine data by editing input, such as entering the collected patients' daily routine time into the disease data management system through the daily routine statistics module 120.

[0054] In some implementations, the daily routine statistics module 120 can also collect the patient's daily routine data through a smart wearable device, such as a health and fitness bracelet.

[0055] Continuing with reference to 2, the health record module 100 further includes a disease labeling module 130, which is used to determine the patient's disease label based on the patient's health status data.

[0056] It should be noted that the disease data management system provided in this application stores various disease tags. These disease tags can be determined based on the International Classification of Diseases, the classification of diseases by various medical institutions, or keywords extracted from diseases based on doctors' suggestions. Specifically, chronic diseases, heart disease, genetic diseases, etc., can all be used as disease tags.

[0057] In some implementations, the disease tag module 130 can also perform operations such as modification, addition, and deletion on the stored disease tags according to the actual situation.

[0058] It is understood that the disease tagging module 130 analyzes the health status data collected by the health data acquisition module 110, and then, based on the analysis results, tags one or more disease tags onto the patient's health status data. It is understood that if a patient suffers from multiple types of diseases, they will be tagged with multiple disease tags.

[0059] See also Figure 2 The health record module 100 further includes a data processing module 140, which is used to generate a patient's health record based on the health status data, the daily routine data, and the disease tags.

[0060] It should be noted that each health record will have one or more corresponding disease tags, so that doctors can quickly locate the health record they need to query in the health record database.

[0061] It is understood that the data processing module 140 can model the patient based on the patient's health status data, daily routine data, and disease tags to form a patient's health record. In addition to recording the patient's health status data, the health record can also record the results of statistical analysis of the patient's health status data, such as the patient's weight change trend, number of illnesses, number of medical visits, duration of use of a certain medication, etc.

[0062] In some implementations, the data processing module 140 can also aggregate the health records of all patients to form a health record database. Furthermore, the data processing module 140 can perform statistical analysis on the health record database, such as counting the number of times each disease label is marked, and calculating the age or gender of all patients corresponding to a certain disease label, etc., to help doctors view the evolution trends of various types of diseases and the comprehensive influencing factors associated with each type of disease, thus providing doctors with substantial data support for their medical research.

[0063] See also Figure 1The disease data management system further includes a doctor-patient relationship establishment module 200, which is used to determine the target health record from the health record database. The target patient corresponding to the target health record is the object of the target doctor's follow-up guidance and treatment.

[0064] In some implementations, the doctor-patient relationship establishment module 200 is as follows: Figure 3 The modules shown are composed of...

[0065] For details, see Figure 3 The diagram illustrates the architecture of a doctor-patient relationship establishment module according to an embodiment of this application.

[0066] The doctor-patient relationship establishment module 200 includes a focus area report recommendation module 210, which is used to recommend health records to the target doctor based on the medical fields of interest of the target doctor.

[0067] In some implementations, the medical areas of interest to doctors can be obtained when they register and log in to the disease data management system.

[0068] In some implementations, the medical areas of interest of doctors can also be determined by the search records of doctors in the disease data management system.

[0069] Specifically, this application does not limit the method for determining the medical areas of interest to doctors.

[0070] It is understood that each health record in the health database is marked with a matching disease tag, and each disease tag exists in its corresponding medical field. Therefore, when a doctor enters the disease data management system, the field of interest report recommendation module 210 will match the disease tags of the health records in the health record database with the medical fields of interest of the doctor, and then recommend the matched health records to the doctor.

[0071] See also Figure 3 The doctor-patient relationship establishment module 200 further includes a health record sorting module 220, which sorts the health records based on their respective occupancy scores. The occupancy scores represent the degree of attention given to the disease tags corresponding to the health records.

[0072] In some implementations, each health record can be assigned a score based on the statistical results of the number of times disease tags are marked by the data processing module 140. For example, if the data processing module 140 counts 10 times for the heart disease tag, 8 times for the hypertension tag, and 2 times for the diabetes tag, then the health record corresponding to the heart disease tag can be assigned a score of 0.5, the health record corresponding to the hypertension tag a score of 0.4, and the health record corresponding to the diabetes tag a score of 0.1. It can be understood that, correspondingly, the health record corresponding to the heart disease tag is ranked first in the health record sorting module 220.

[0073] In some implementations, a score can be assigned to each health record based on the doctor's search history in the disease data management system. For example, if the search history shows that the doctor searched for heart disease 5 times, hypertension 2 times, and diabetes 3 times in the disease data management system, then the health record corresponding to the heart disease tag can be assigned a score of 0.5, the health record corresponding to the hypertension tag a score of 0.2, and the health record corresponding to the diabetes tag a score of 0.3. It can be understood that, correspondingly, the health record corresponding to the heart disease tag will be ranked first in the health record sorting module 220.

[0074] In some implementations, the data processing module 140 can also assign a occupancy score to each health record based on the statistical results of the number of times the disease tag is marked, and the doctor's search records in the disease data management system. For example, combining the above example of determining the occupancy score, if the diabetes disease tag is determined to have a total of 15 occurrences based on the statistics of the data processing module 140 and the doctor's search records, the hypertension disease tag is determined to have a total of 10 occurrences based on the statistics of the data processing module 140 and the doctor's search records, and the diabetes disease tag is determined to have a total of 5 occurrences based on the statistics of the data processing module 140 and the doctor's search records, then the occupancy score for the health record corresponding to the heart disease tag can be determined to be 0.5, the occupancy score for the health record corresponding to the hypertension disease tag is 0.33, and the occupancy score for the health record corresponding to the diabetes disease tag is 0.17.

[0075] In this embodiment, the health record sorting module 220 can determine the sorting method for health records based on specific actual conditions, and this application does not limit this method. The health record sorting module 220 can recommend health records with high interest to doctors, which can save doctors time searching for health records to a certain extent, thereby improving work efficiency.

[0076] See also Figure 3The doctor-patient relationship establishment module 200 further includes a health record selection module 240, which is used to determine the target health record through the interest area report recommendation module 210, the health record sorting module 220, and the search query module 230.

[0077] It is understood that when a doctor enters the disease data management system of this application, they can determine the health records of interest through the area of ​​interest report recommendation module 210, the health record sorting module 220, or by searching in the search query module 230. Furthermore, if a doctor selects a health record of interest, it means that the doctor can view all the data information included in the selected health record, thereby enabling them to monitor and track the patients corresponding to the selected health record and guide the treatment of the patients' diseases.

[0078] It should be noted that a single doctor can establish doctor-patient relationships with multiple patients. Conversely, if a patient suffers from multiple illnesses, the same patient can also establish doctor-patient relationships with multiple doctors.

[0079] In this embodiment, through the doctor-patient relationship establishment module 200, the target doctor uses the person he has selected for guidance and treatment as the target patient. It can be seen that the patient does not need to go to the hospital to passively select a doctor to receive guidance and treatment for his or her disease. Instead, the doctor actively selects and guides the patient's treatment, so that the patient's disease can be actively treated and the efficiency of the patient's medical treatment can be improved.

[0080] See also Figure 1 The disease data management system provided in this application also includes a doctor-patient communication module 300, which is used for online communication between the target doctor and the target patient.

[0081] It should be noted that when the target doctor identifies a target patient through the doctor-patient relationship establishment module 200, the target patient can be introduced into the doctor-patient communication module 300. The target doctor can then use the doctor-patient communication module 300 to inquire about and annotate the target patient, thereby providing better guidance for treatment. Of course, the communication methods between the target doctor and the target patient include, but are not limited to, text, video, and voice.

[0082] In some implementations, the doctor-patient communication module 300 is also used to invite other doctors to jointly follow up and guide the treatment of the target patient.

[0083] It is understandable that if the target doctor encounters a complex disease, they can form a cross-doctor team through the doctor-patient communication module 300 to better guide the treatment of the target patient.

[0084] In some implementations, the doctor-patient communication module 300 can also group different patients with the same disease into the same communication group, enabling doctors to guide the treatment of multiple patients at the same time and improve the efficiency of diagnosis and treatment.

[0085] See also Figure 1 The disease data management system further includes a medical guidance and tracking module 400, which is used to track and record the process data of the target doctor guiding the treatment of the target patient.

[0086] In some implementations, the process data refers to data recording the period from when the patient was noticed by the target doctor until the disease was cured or controlled. Specifically, this includes, but is not limited to, communication record data recorded in the doctor-patient communication module 300, doctor's offline diagnosis and treatment record data, patient's examination results data in the hospital, medication record data, etc.

[0087] See also Figure 1 The disease data management system further includes a similar patient analysis module 500, which is used to analyze and statistically process data generated by the guided treatment of different patients and the health records of different patients to generate case data for various types of diseases.

[0088] It is understandable that different patients generate related process data after receiving treatment under the guidance of doctors, and each patient has their own health record. Therefore, the similar patient analysis module 500 can perform analysis and statistics based on the process data and the data included in the health records. For example, it can analyze and statistically analyze indicators such as the patient's physical examination data, disease treatment plan, disease treatment cycle, and disease manifestations, thereby forming case data corresponding to various types of diseases.

[0089] See also Figure 1 The disease data management system further includes a case sharing module 600, which is used to share guidance articles created by doctors based on the case data.

[0090] In some implementations, the case sharing module 600 includes, for example: Figure 4 The modules shown are composed of...

[0091] For details, see Figure 4 The diagram illustrates the architecture of a case sharing module according to one embodiment of this application.

[0092] The case sharing module 600 includes a case data editing module 610, which is used to generate guidance articles created by doctors based on the case data.

[0093] In some implementations, doctors can use the case data editing module 610 to combine the case data, clinical medical experience, medical paper knowledge, and medical report data to create more accessible and understandable guidance articles. Examples include health advice articles for a certain type of disease, or analyses of the evolution of a certain type of disease.

[0094] See also Figure 4 The case sharing module 600 further includes a case data tag module 620, which is used to tag the guidance article with corresponding article tags.

[0095] In some implementations, the guidance articles can be tagged as patient articles and doctor articles based on the intended audience. It is understood that the guidance articles created by doctors based on the case data may be suitable for doctors or patients; therefore, the guidance articles can be tagged based on the audience viewing them.

[0096] In some implementations, the guidance articles can also be tagged with corresponding article tags based on the content they contain.

[0097] See also Figure 4 The case sharing module 600 further includes an intelligent data push module 630, which is used to push matching guidance articles to doctors or patients based on the article tags.

[0098] In some implementations, the intelligent data push module 630 can use an internal recommendation algorithm based on the patient's health record disease tags, the article tags of the guidance articles, the medical fields that the doctor is interested in, or the doctor's search query records, to recommend matching guidance articles to the doctor or patient.

[0099] In this embodiment, the intelligent data push module 630 can recommend matching guidance articles to doctors, thus providing doctors with a learning platform for communication and exchange.

[0100] See also Figure 1 In some embodiments, the disease data management system further includes a data storage module 700, which stores the health record database, case data of the various types of diseases, and the guidance articles.

[0101] It is understood that the data storage module 700 can store the data generated by the entire disease data management system, thereby ensuring the stability of the system and the security of the data.

[0102] In some implementations, the data storage module 700 is also used to manage the viewing permissions of doctors or patients for the health record database and case data of the various types of diseases.

[0103] It is understandable that if a doctor enters the disease data management system, they can query all patients' relevant information, while if a patient enters the disease data management system, they can only query information related to themselves. This achieves relative sharing of system data and relative isolation of patient information, ensuring the security of system data.

[0104] In some implementations, the data storage module 700 is provided with a calling interface, which is connected to the doctor-patient relationship establishment module 200 and the case sharing module 600 respectively.

[0105] It is understood that after the health record module 100 generates the health record database, it will transmit the data information contained in the health record database to the data storage module 700. At the same time, the doctor-patient relationship establishment module 200 can call the health record database stored in the data storage module 700 through the calling interface, so as to determine the target health record from the health record database.

[0106] In addition, after the case data tagging module 620 in the case sharing module 600 tags the guidance article with the corresponding article tag, it will transmit the guidance article to the data storage module 700. At the same time, the intelligent data push module 630 in the case sharing module 600 can call the guidance article stored in the data storage module 700 through the calling interface, so as to recommend matching guidance articles to doctors or patients.

[0107] In some implementations, the case sharing module 600 can also interface with an external sharing platform to periodically share guidance articles generated in the disease data management system to the external sharing platform, so that the guidance articles can be better circulated.

[0108] See also Figure 1 In some embodiments, the disease data management system further includes a login module 800, which provides doctors or patients with an entry point to the disease data management system.

[0109] It is understood that doctors or patients can register and access the disease data management system through the login module 800. Correspondingly, the login module 800 obtains the identity information of patients or doctors when they register or access the system, thereby better managing the viewing and operation permissions of logged-in users.

[0110] In some embodiments of this application, the technical solutions include a health record module 100, which allows for the acquisition of patients' historical health status and daily routine data, thereby creating corresponding health records for different patients. This demonstrates that the health record module 100 enables unified analysis and management of patients' disease data. A doctor-patient relationship establishment module 200 allows doctors to proactively identify target health records from the health record database, thus establishing a doctor-patient relationship for proactive guidance and treatment. A medical guidance and tracking module 400 tracks and records the process data of doctors guiding patients' treatment, providing data support for doctors' disease research. A similar patient analysis module 500 automatically generates case data for various types of diseases, providing doctors with rich case data to aid in in-depth research. A case sharing module 600 recommends guidance articles based on case data to different doctors or patients within the system provided in this application, providing doctors with a communication and learning platform.

[0111] Although this application has been described with reference to several typical embodiments, it should be understood that the terminology used is descriptive and exemplary, and not restrictive. Since this application can be embodied in many forms without departing from the spirit or substance of the application, it should be understood that the above embodiments are not limited to any of the foregoing details, but should be interpreted broadly within the spirit and scope defined by the appended claims. Therefore, all variations and modifications falling within the scope of the claims or their equivalents should be covered by the appended claims.

Claims

1. A disease data management system, characterized in that, The system includes: The health record module is used to collect and process patients' health status data and daily routine data to generate a health record library, which consists of health records of different patients. The doctor-patient relationship establishment module is used to determine the target health record from the health record database, and the target patient corresponding to the target health record is the object of the target doctor's follow-up guidance and treatment; The medical guidance and tracking module is used to track and record the process data of the target doctor guiding the treatment of the target patient; The similar patient analysis module is used to analyze and statistically analyze the process data generated by the guided treatment of different patients and the health records of different patients to generate case data for various types of diseases; the case data is obtained by analyzing and statistically analyzing the patient's physical examination data, disease treatment plan, disease treatment cycle, and disease manifestations. The case sharing module is used to share guidance articles created by doctors based on the case data; The doctor-patient relationship establishment module includes: The focus area report recommendation module is used to recommend health records to the target doctor based on the medical areas they are interested in. The health record sorting module is used to sort the health records based on their respective occupancy scores, whereby the occupancy scores represent the degree of attention given to the disease tags corresponding to the health records. The search query module is used to search for health records; The health record selection module is used to determine the target health record through the interest area report recommendation module, the health record sorting module, and the search query module.

2. The system according to claim 1, characterized in that, The health record module includes: The health data acquisition module is used to collect patients' health status data; The daily routine statistics module is used to collect and analyze patients' daily routines to obtain their daily routine data. The disease labeling module is used to determine the patient's disease label based on the patient's health status data. The data processing module is used to generate a patient's health record based on the health status data, the daily routine data, and the disease tags.

3. The system according to claim 1, characterized in that, The system also includes a doctor-patient communication module, which is used for online communication between the target doctor and the target patient.

4. The system according to claim 3, characterized in that, The doctor-patient communication module is also used to invite other doctors to jointly follow up and guide the treatment of the target patient.

5. The system according to claim 1, characterized in that, The case sharing module includes: The case data editing module is used to generate guidance articles created by doctors based on the case data; The case data tagging module is used to tag the guidance articles with corresponding article tags; The intelligent data push module is used to push matching guidance articles to doctors or patients based on the article tags.

6. The system according to claim 1, characterized in that, The system also includes a data storage module for storing the health record database, case data of various types of diseases, and guidance articles.

7. The system according to claim 6, characterized in that, The data storage module is also used to manage doctors' or patients' viewing permissions for the health record database and case data of various types of diseases.

8. The system according to claim 6, characterized in that, The data storage module is equipped with a calling interface, which is connected to the doctor-patient relationship establishment module and the case sharing module.

9. The system according to claim 1, characterized in that, The system also includes a login module, which provides doctors or patients with an entry point to the disease data management system.

Images