CN117253622A - Disease data management system - Google Patents
Disease data management system Download PDFInfo
- Publication number
- CN117253622A CN117253622A CN202310261119.3A CN202310261119A CN117253622A CN 117253622 A CN117253622 A CN 117253622A CN 202310261119 A CN202310261119 A CN 202310261119A CN 117253622 A CN117253622 A CN 117253622A
- Authority
- CN
- China
- Prior art keywords
- module
- health
- patient
- data
- 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.)
- Pending
Links
- 208000037265 diseases, disorders, signs and symptoms Diseases 0.000 title claims abstract description 144
- 201000010099 disease Diseases 0.000 title claims abstract description 135
- 238000013523 data management Methods 0.000 title claims abstract description 50
- 230000036541 health Effects 0.000 claims abstract description 170
- 238000004891 communication Methods 0.000 claims abstract description 29
- 238000000034 method Methods 0.000 claims abstract description 17
- 238000004458 analytical method Methods 0.000 claims abstract description 16
- 230000008569 process Effects 0.000 claims abstract description 16
- 230000003862 health status Effects 0.000 claims description 19
- 238000013500 data storage Methods 0.000 claims description 17
- 238000012545 processing Methods 0.000 claims description 16
- 239000000203 mixture Substances 0.000 claims description 7
- 238000002372 labelling Methods 0.000 claims description 2
- 238000007726 management method Methods 0.000 abstract description 4
- 238000010586 diagram Methods 0.000 description 8
- 208000019622 heart disease Diseases 0.000 description 8
- 206010012601 diabetes mellitus Diseases 0.000 description 7
- 206010020772 Hypertension Diseases 0.000 description 6
- 238000013480 data collection Methods 0.000 description 4
- 238000003745 diagnosis Methods 0.000 description 4
- 239000003814 drug Substances 0.000 description 4
- 238000011160 research Methods 0.000 description 4
- 229940079593 drug Drugs 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000004617 sleep duration Effects 0.000 description 2
- 206010067484 Adverse reaction Diseases 0.000 description 1
- 208000017667 Chronic Disease Diseases 0.000 description 1
- 206010020751 Hypersensitivity Diseases 0.000 description 1
- 208000026350 Inborn Genetic disease Diseases 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 230000006838 adverse reaction Effects 0.000 description 1
- 208000026935 allergic disease Diseases 0.000 description 1
- 230000007815 allergy Effects 0.000 description 1
- 239000008280 blood Substances 0.000 description 1
- 210000004369 blood Anatomy 0.000 description 1
- 238000009534 blood test Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000012937 correction Methods 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 208000016361 genetic disease Diseases 0.000 description 1
- 238000002955 isolation Methods 0.000 description 1
- 238000012806 monitoring device Methods 0.000 description 1
- 238000007619 statistical method Methods 0.000 description 1
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
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients
-
- 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
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/20—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
-
- 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
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/30—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for calculating health indices; for individual health risk assessment
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02A—TECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
- Y02A90/00—Technologies having an indirect contribution to adaptation to climate change
- Y02A90/10—Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation
Landscapes
- Engineering & Computer Science (AREA)
- Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Public Health (AREA)
- Data Mining & Analysis (AREA)
- Biomedical Technology (AREA)
- Databases & Information Systems (AREA)
- Pathology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Primary Health Care (AREA)
- Medical Treatment And Welfare Office Work (AREA)
Abstract
The present application provides a disease data management system, the system comprising: the health file module is used for generating health files of patients and forming a health file library; the doctor-patient relationship establishing module is used for determining a target health file from the health file library, wherein a target patient corresponding to the target health file is a target doctor to follow-up a target guiding treatment; the medical guidance and tracking module is used for tracking and recording process data of guiding treatment of the target patient by the target doctor; the similar patient analysis module is used for analyzing and counting the process data generated by the treatment of different patients and the health files of the different patients so as to generate case data of various diseases; and the case sharing module is used for sharing the instruction article which is authored by the doctor based on the case data. The disease data management system provided by the application can realize tracking management of patient disease data, and simultaneously provides a learning platform for communication and communication for doctors.
Description
Technical Field
The present application relates to the field of data management technologies, and in particular, to a disease data management system.
Background
At present, patients want to get treatment of diseases to go to hospitals, and the patients can get guidance treatment of the diseases of the patients after undergoing complicated procedures and long waiting time, even if the diseases of the patients get guidance treatment, the diagnosis records of the diseases of the patients and the past health state data of the patients are uniformly managed due to the lack of a platform, so that doctors lack data bases for researching different diseases, and the doctors are difficult to form suggestions with references to other doctors and guidance suggestions to the patients aiming at different disease types. Based on the above, how to realize the tracking management of the patient disease data and form a learning platform for doctors to communicate is a technical problem to be solved.
Disclosure of Invention
The embodiment of the application provides a disease data management system, which can realize that the disease of a patient is actively found and guided and treated by a doctor, can realize the tracking management of the disease data and the health state data of the patient, and can also obtain a learning platform for the communication and communication of the doctor.
Specifically, the technical scheme of the application is as follows:
the present application provides a disease data management system, the system comprising: the health archive module is used for collecting and processing health state data and work and rest data of patients to generate health archives, wherein the health archives are composed of health archives of different patients; the doctor-patient relationship establishing module is used for determining a target health file from the health file library, wherein a target patient corresponding to the target health file is a target doctor to follow-up a target guiding treatment; the medical guidance and tracking module is used for tracking and recording process data of guiding treatment of the target patient by the target doctor; the similar patient analysis module is used for analyzing and counting the process data generated by guiding the treatment of different patients and the health files of different patients so as to generate case data of various diseases; and the case sharing module is used for sharing the instruction article which is authored by the doctor based on the case data.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: the health data acquisition module is used for acquiring health state data of a patient; the composition statistics module is used for collecting and counting the composition time of the patient so as to obtain the composition data of the patient; a disease label module for determining a disease label for the patient based on the patient's health status data; and the data processing module is used for generating a health file of the patient based on the health state data, the work and rest data and the disease label.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: the attention field report recommending module is used for recommending a health file to the target doctor based on the medical field of attention of the target doctor; the health record sorting module is used for sorting the health records based on occupation scores of the health records, wherein the occupation scores are used for representing the attention degree of the disease label corresponding to the health records; the search query module is used for searching and querying the health files; the health record selecting module is used for determining the target health record through the attention field report recommending module, the health record sorting module and the search query module.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: and the doctor-patient communication module is used for carrying out online communication between the target doctor and the target patient.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: the doctor-patient communication module is also used for inviting other doctors to follow up together to guide the treatment of the target patient.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: the case data editing module is used for generating a guide article authored by a doctor based on the case data; the case data label module is used for labeling the corresponding article labels for the guide articles; and the intelligent data pushing module is used for pushing the matched guide articles to the doctor or the patient based on the article labels.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: and the data storage module is used for storing the health archive, the case data of various diseases and the guide article.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: the data storage module is also used for managing the viewing authority of doctors or patients to the health archive and the case data of various diseases.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: and a calling interface is arranged in the data storage module, and is respectively connected with the doctor-patient relationship establishing module and the case sharing module.
In some embodiments of the present application, based on the foregoing, the disease data management system further comprises: the system further includes a login module for providing a doctor or patient with access to the disease data management system.
According to the disease data management system, the health file module is arranged, so that historic health state data and work and rest data of patients can be obtained through the health file module, corresponding health files are formed for different patients, and the disease data of the patients can be analyzed and managed uniformly through the health file module; by setting a doctor-patient relationship establishing module in the system, a doctor can actively determine a target health file from the health archive, so that the doctor can actively establish a doctor-patient relationship with a patient to actively guide and treat the disease of the patient; the medical guidance and tracking module is arranged in the system, so that the process data of guiding and treating the disease of the patient by the doctor can be tracked and recorded, and the data support is provided for the research of the doctor on the disease; the system can automatically generate case data of various types of diseases by arranging the similar patient analysis modules, so that abundant case data are provided for doctors to help the doctors to conduct deep research on various types of diseases; by arranging the case sharing module in the system, the guidance articles obtained based on case data creation can be recommended to different doctors or patients in the system provided by the application, so that the doctors can obtain a learning platform for communication through the system.
Drawings
Fig. 1 shows a simplified schematic architecture diagram of a disease data management system according to one embodiment of the present application.
FIG. 2 illustrates an architectural diagram of a health profile module according to one embodiment of the present application.
FIG. 3 illustrates an architecture diagram of a doctor-patient relationship establishment module according to one embodiment of the application.
Fig. 4 illustrates an architecture diagram of a case sharing module according to one embodiment of the present application.
The reference numerals are explained as follows:
100-a health file module, 110-a health data acquisition module,
120-a work and rest statistics module, 130-a disease label module,
140-a data processing module, which is configured to process the data,
200-doctor-patient relationship establishing module, 210-attention field report recommending module,
220-a health record ranking module, 230-a search query module,
240-a health record selection module,
300-a doctor-patient communication module,
400-a medical guidance and tracking module,
500-a similar patient analysis module,
600-a case sharing module, 610-a case data editing module,
620-case data label module, 630-intelligent data push module,
700-a data storage module,
800-login module.
Detailed Description
Exemplary embodiments that embody features and advantages of the present application are described in detail in the following description. It will be understood that the present application is capable of various modifications in various embodiments, all without departing from the scope of the present application, and that the description and illustrations herein are intended to be by way of illustration only and not to be limiting.
In the description of the present application, it should be noted that the azimuth or positional relationship indicated by the terms "vertical", "upper", "lower", "horizontal", etc. are based on the azimuth or positional relationship shown in the drawings, and are merely for convenience of description of the present application and simplification of the description, and do not indicate or imply that the system or element referred to must have a specific azimuth, be configured and operated in a specific azimuth, and thus should not be construed as limiting the present application.
In the description of the present application, it should also be noted that, unless explicitly specified and limited otherwise, the terms "disposed," "mounted," "connected," and "connected" are to be construed broadly, and may be, for example, fixedly connected, detachably connected, or integrally connected; can be mechanically or electrically connected; can be directly connected or indirectly connected through an intermediate medium, and can be communication between two elements. The specific meaning of the terms in this application will be understood by those of ordinary skill in the art as the case may be.
In the present application, all employees of a company may be used as patients, or users suffering from a disease may be used as patients.
The present application provides a disease data management system, and in order to better understand the disease data management system according to the present embodiment, the following description will be made with reference to fig. 1 to 4.
Referring to fig. 1, a simplified schematic diagram of a disease data management system according to one embodiment of the present application is shown.
Referring to fig. 1, a possible disease data management system of the present application is shown, which includes a health archive module 100, a doctor-patient relationship establishment module 200, a doctor-patient communication module 300, a medical guidance and tracking module 400, a homogeneous patient analysis module 500, a case sharing module 600, a data storage module 700, and a login module 800.
The health archive module 100 is configured to collect and process health status data and work and rest data of patients to generate health archives, where the health archives are composed of health archives of different patients.
It should be noted that in the health profile module 100, the health status data of different patients are analyzed and modeled according to the work and rest data, so as to form health profiles (i.e. health portraits) of different patients, where the health profiles are equivalent to a health database of the patients, and can reflect the current and historical health status of the patients.
In some embodiments, the health profile module 100 is composed of modules as shown in fig. 2.
In particular, referring to FIG. 2, a schematic architecture diagram of a health archive module according to one embodiment of the present application is shown.
The health record module 100 includes a health data collection module 110, and the health data collection module 110 is configured to collect health status data of a patient.
In some embodiments, the health status data may reflect the current and past health status of the patient, including but not limited to basic patient information (e.g., blood type, age, height, etc.), past disease history, allergy history, medication adverse reaction history, medical records, medication records, examination records (e.g., blood test data), and the like. Specifically, for what health status data of the patient is collected may be designed according to a specific application scenario, which is not limited herein.
In some embodiments, the health data acquisition module 110 may obtain health status data of the patient by importing physical examination reports of the patient over the years.
In some embodiments, the health data collection module 110 may also input health status data of the patient in an edited form, such as by entering the collected health status data of the patient into the disease data management system through the health collection module.
In some embodiments, the health data acquisition module 110 may also collect health status data of the patient by way of a smart wearable device. Such as by acquiring electrocardiographic data of the patient via a wearable electrocardiographic monitoring device.
With continued reference to fig. 2, the health record module 100 further includes a work and rest statistics module 120, where the work and rest statistics module 120 is configured to collect and count a work and rest time of the patient, so as to obtain work and rest data of the patient.
In some embodiments, the work and rest data includes, but is not limited to, a night sleep duration, a noon break duration, a work duration, and the like of the patient. It can be appreciated that the rest statistics module 120 may convert the collected rest time of the patient into the rest data of the patient through statistics, for example, the rest statistics module 120 determines the rest data of the sleep duration of the patient through statistics from the collected time of getting up and sleeping of the patient.
In some embodiments, if all staff of the company are taken as the patient, the work and rest statistics module 120 may be connected to an attendance system of the company, so as to obtain daily attendance records of the patient, and work and rest time of the patient collected in the attendance system, so as to obtain work and rest data of the patient.
In some embodiments, the statistics module 120 may also collect the patient's information by editing the input, such as entering the collected information about the patient's information into the disease data management system via the statistics module 120.
In some embodiments, the rest statistics module 120 may also collect the rest data of the patient through the smart wearable device, such as obtaining the rest data of the patient through a health exercise bracelet.
With continued reference to fig. 2, the health profile module 100 further includes a disease label module 130, where the disease label module 130 is configured to determine a disease label of the patient based on the patient's health status data.
It should be noted that, in the disease data management system provided in the present application, various disease labels may be stored, and the disease labels may be determined based on international disease classification, may be determined according to classification of diseases by each medical institution, or may be keywords of diseases extracted as disease labels based on advice of doctors. In particular, chronic diseases, heart diseases, genetic diseases, etc. can be used as disease markers.
In some embodiments, the disease label module 130 may also perform operations such as correction, addition, deletion, etc. on the stored disease label according to actual situations.
It will be appreciated that the disease tagging module 130 analyzes the health status data collected by the health data collection module 110 and then tags the health status data of the patient with one or more disease tags in combination with the analysis. It will be appreciated that if a patient suffers from multiple types of disease, multiple disease signatures will be labeled.
With continued reference to fig. 2, the health profile module 100 further includes a data processing module 140, where the data processing module 140 is configured to generate a health profile of the patient based on the health status data, the work and rest data, and the disease label.
It should be noted that each health record has one or more disease labels corresponding to the health record, so that a doctor can quickly locate the health record to be queried in the health record repository.
It is understood that the data processing module 140 may model the patient based on the patient's health status data, work and rest data, and the disease label to form a patient's health profile. The health record can record data such as health state data of a patient, and also can record result data of statistical analysis on the health state data of the patient, wherein the result data can be such as weight change trend data of the patient, times of illness, times of diagnosis and treatment, time of using a certain medicine and the like.
In some embodiments, the data processing module 140 may also aggregate the health profiles of all patients into a health archive. In addition, the data processing module 140 may further perform data statistics analysis on the health archive, such as counting the number of marking times of each disease label, age statistics or gender statistics of all patients corresponding to a certain disease label, etc., so that a doctor can check the evolution trend of each type of disease, and check the comprehensive influencing factors associated with each type of disease, so that the medical study of the doctor is supported by a large amount of data.
With continued reference to fig. 1, the disease data management system further includes a doctor-patient relationship establishing module 200, where the doctor-patient relationship establishing module 200 is configured to determine a target health record from the health record repository, and a target patient corresponding to the target health record is a target doctor who follows a target doctor for guiding treatment.
In some embodiments, the doctor-patient relationship establishment module 200 is composed of modules as shown in fig. 3.
Specifically, referring to fig. 3, a schematic architecture diagram of a doctor-patient relationship establishment module according to one embodiment of the application is shown.
The doctor-patient relationship establishing module 200 includes a field of interest report recommending module 210, where the field of interest report recommending module 210 is configured to recommend a health record to the target doctor based on the medical field of interest of the target doctor.
In some embodiments, the medical field of interest to the doctor may be acquired by the doctor upon registration to log into the disease data management system.
In some embodiments, the medical field of interest to the physician may also be determined by a search record of the physician in the disease data management system.
In particular, the manner in which the medical field of interest to the doctor is determined is not limited in this application.
It will be appreciated that each health record in the health database, because each health record is labeled with a disease label matching it, and each disease label will have a medical field to which it belongs, when a doctor enters the disease data management system, the attention field report recommendation module 210 will match the acquired medical field of interest of the doctor with the disease label of the health record in the health record repository, so as to recommend the matched health record to the doctor.
With continued reference to fig. 3, the doctor-patient relationship establishing module 200 further includes a health record ranking module 220, where the health record ranking module 220 is configured to rank each health record based on an occupation score of each health record, where the occupation score is used to characterize a degree of interest of a disease label corresponding to the health record.
In some embodiments, the data processing module 140 may assign an occupation score to each health record according to the statistics of the number of times the disease label is marked, for example, if the data processing module 140 counts that the heart disease label is 10 times, the hypertension disease label is 8 times, and the diabetes disease label is 2 times, it may be determined that the occupation score to the health record corresponding to the heart disease label is 0.5, the occupation score to the health record corresponding to the hypertension disease label is 0.4, and the occupation score to the health record corresponding to the diabetes disease label is 0.1. It will be appreciated that, correspondingly, the health files corresponding to the heart disease label are arranged first in the health file sorting module 220.
In some embodiments, occupancy scores may also be assigned to individual health profiles based on a doctor's search records in the disease data management system. By way of example, if it is determined by searching the record that the doctor inquires about the heart disease 5 times, the hypertension 2 times, and the diabetes 3 times in the disease data management system, the occupation score of the health file corresponding to the heart disease label may be determined to be 0.5, the occupation score of the health file corresponding to the hypertension label may be 0.2, and the occupation score corresponding to the diabetes label may be 0.3. It will be appreciated that, correspondingly, the health files corresponding to the heart disease label are arranged first in the health file sorting module 220.
In some embodiments, the occupation scores may also be assigned to the health records based on statistics of the number of times the disease label is marked by the data processing module 140, and based on the search records of the doctor in the disease data management system. By way of example, in combination with the above example of determining the occupation score, the diabetes disease label is determined to have a total number of times of 15 by the statistics of the data processing module 140 and the search records of the doctor, the hypertension disease label is determined to have a total number of times of 10 by the statistics of the data processing module 140 and the search records of the doctor, and the diabetes disease label is determined to have a total number of times of 5 by the statistics of the data processing module 140 and the search records of the doctor, so that the occupation score of the health file corresponding to the heart disease label is determined to be 0.5, the occupation score of the health file corresponding to the hypertension disease label is determined to be 0.33, and the occupation score corresponding to the diabetes disease label is determined to be 0.17.
In this embodiment, the health record ranking module 220 may determine the manner of ranking the health records according to specific practical situations, which is not limited herein. The health files with higher attention can be recommended to doctors through the health file sorting module 220, so that the time for searching and inquiring the health files by the doctors can be saved to a certain extent, and the working efficiency is improved.
With continued reference to fig. 3, the doctor-patient relationship establishment module 200 further includes a health profile selection module 240, where the health profile selection module 240 is configured to determine the target health profile via the field of interest report recommendation module 210, the health profile ranking module 220, and the search query module 230.
It will be appreciated that when a doctor enters the disease data management system of the present application, the health record of interest of the doctor can be determined by the attention area report recommendation module 210, the health record of interest of the doctor can be determined by the health record ranking module 220, or the health record of interest of the doctor can be determined by searching and querying the search query module 230. Meanwhile, if the doctor selects the interested health file, the doctor can check all data information included in the selected health file, so that the doctor can pay attention to and track the patient corresponding to the selected health file, and guide treatment on the disease suffered by the patient.
It should be noted that the same doctor can establish a doctor-patient relationship with a plurality of patients. In contrast, if a patient suffers from multiple diseases, the same patient can also establish a doctor-patient relationship with multiple doctors.
In this embodiment, through the doctor-patient relationship establishing module 200, the target doctor uses the subject selected by the doctor to guide treatment as the target patient, so that the patient does not need to go to the hospital to undergo passive selection to determine the doctor so that the patient suffers from the disease to guide treatment, but the doctor actively selects to guide treatment, so that the disease of the patient can be actively treated, and the doctor seeing efficiency of the patient is improved.
With continued reference to fig. 1, the disease data management system provided herein further includes a doctor-patient communication module 300, where the doctor-patient communication module 300 is configured to perform online communication between the target doctor and the target patient.
It should be noted that, when the target doctor determines that the target patient is a target patient through the doctor-patient relationship establishing module 200, the target patient may be introduced into the doctor-patient communication module 300, and the target doctor may query and mark the target patient through the doctor-patient communication module 300, so that better guiding treatment can be performed on the target patient. Of course, the communication mode between the target doctor and the target patient includes but is not limited to text, video, voice, etc.
In some embodiments, the doctor-patient communication module 300 is further configured to invite other doctors to follow-up together to guide the treatment of the target patient.
It will be appreciated that if the target physician encounters a complex disease, a cross-physician team may be established through the physician-patient communication module 300 to better guide treatment of the target patient.
In some embodiments, the doctor-patient communication module 300 can also group different patients with the same disease into the same communication group, so that doctors can conduct guiding treatment on multiple patients at the same time, and diagnosis and treatment efficiency is improved.
With continued reference to fig. 1, wherein the disease data management system further includes a medical guidance and tracking module 400, the medical guidance and tracking module 400 is configured to track and record process data of the targeted patient for guiding treatment by the targeted physician.
In some embodiments, the process data is data recorded between the patient being cured or controlled from the disease of which the target doctor is interested, specifically including, but not limited to, communication record data recorded in the doctor-patient communication module 300, doctor off-line diagnosis record data, patient in-hospital examination result data, medication record data, and the like.
With continued reference to fig. 1, the disease data management system further includes a homogeneous patient analysis module 500, where the homogeneous patient analysis module 500 is configured to analyze and count process data generated by the guided treatment of the different patients and health files of the different patients to generate case data of each type of disease.
It will be appreciated that different patients will generate associated process data after guided treatment by the doctor, and that each patient will have its own health profile. The similar patient analysis module 500 may perform analysis statistics based on the process data and the data included in the health record, for example, perform analysis statistics according to the physical examination data of the patient, the disease treatment scheme, the disease treatment period, the disease appearance condition, and other indexes, so as to form case data corresponding to various types of diseases.
With continued reference to fig. 1, the disease data management system further includes a case sharing module 600, where the case sharing module 600 is configured to share a guiding article created by a doctor based on the case data.
In some embodiments, the case sharing module 600 includes a module composition as shown in fig. 4.
Specifically, referring to fig. 4, a schematic architecture diagram of a case sharing module according to one embodiment of the present application is shown.
The case sharing module 600 includes a case data editing module 610, where the case data editing module 610 is configured to generate a guiding article authored by a doctor based on the case data.
In some embodiments, the doctor may perform secondary authoring on the case data in the case data editing module 610 in combination with the case data, medical clinical experience, medical paper knowledge, medical report data, and the like, to obtain a more popular and understandable guide article. Such as health care advice articles for certain diseases, analysis articles for the evolution process of certain diseases, etc.
With continued reference to fig. 4, the case sharing module 600 further includes a case data tag module 620, where the case data tag module 620 is configured to tag the guide article with a corresponding article tag.
In some embodiments, the patient article tag and the doctor article tag may be labeled based on the object to which the guide article is appropriate. It will be appreciated that the physician composes based on the case data such that the resulting guide article may be suitable for viewing by the physician or by the patient, and thus the guide article may be tagged with the object of viewing the guide article.
In some embodiments, corresponding article tags may also be marked for the guide articles according to the content they contain.
With continued reference to fig. 4, the case sharing module 600 further includes an intelligent data pushing module 630, where the intelligent data pushing module 630 is configured to push the matched guide articles to the doctor or the patient based on the article tag.
In some embodiments, the intelligent data pushing module 630 may perform an internal recommendation algorithm according to the disease tag of the patient's health record, the article tag of the guide article, the medical field of interest to the doctor or the search query record of the doctor, so as to recommend the matched guide article for the doctor or the patient.
In this embodiment, the intelligent data pushing module 630 can recommend the matched guide articles by the doctor, so as to provide a learning platform for communication and communication for the doctor.
With continued reference to fig. 1, in some embodiments, the disease data management system further includes a data storage module 700, the data storage module 700 being configured to store the health archive, the case data for each type of disease, and the guide article.
It will be appreciated that the data storage module 700 is capable of storing data generated by the overall disease data management system, thereby ensuring system stability and data security.
In some embodiments, the data storage module 700 is further configured to manage the doctor's or patient's viewing rights to the health archive and the case data for the various types of diseases.
It can be understood that if a doctor enters the disease data management system, relevant information of all patients can be queried, if the doctor enters the disease data management system, only relevant information of the doctor can be queried, so that relative sharing of system data and relative isolation of patient information are realized, and safety of the system data is ensured.
In some embodiments, a calling interface is set in the data storage module 700, where the calling interface is connected to the doctor-patient relationship establishing module 200 and the case sharing module 600 respectively.
It will be appreciated that the data information contained in the health archive is transmitted to the data storage module 700 after the health archive is generated by the health archive module 100, and the doctor-patient relationship establishing module 200 may invoke the health archive stored in the data storage module 700 through the invoking interface so as to determine the target health archive from the health archive.
In addition, when the case data tag module 620 in the case sharing module 600 tags the corresponding article tag with the guide article, the guide article is transmitted to the data storage module 700, and at the same time, the intelligent data pushing module 630 in the case sharing module 600 may call the guide article stored in the data storage module 700 through the call interface, so as to recommend the matched guide article to the doctor or patient.
In some embodiments, the case sharing module 600 may further interface with an external sharing platform, and periodically share the guide articles generated in the disease data management system to the external sharing platform, so that the guide articles are more popular.
With continued reference to fig. 1, in some embodiments, the disease data management system further includes a login module 800, the login module 800 being used to provide a doctor or patient with access to the disease data management system.
It will be appreciated that a doctor or patient may register with the disease data management system via the login module 800, or may enter the disease data management system via the login module 800. Accordingly, the login module 800 may acquire the identity information of the patient or doctor when the patient or doctor registers or enters the system, so as to better manage the viewing authority and the operation authority of the login person.
In the technical solutions provided in some embodiments of the present application, by setting the health archive module 100, the health archive module 100 can obtain historic health status data and work and rest data of a patient, so as to form corresponding health archives for different patients, and it can be seen that unified analysis and management can be performed on disease data of the patient through the health archive module 100; by arranging the doctor-patient relationship establishing module 200 in the system, a doctor can actively determine a target health file from the health archive, so that the doctor can actively establish a doctor-patient relationship with a patient to actively guide and treat the disease of the patient; the medical guidance and tracking module 400 is arranged in the system, so that the process data of guiding and treating the disease of the patient by the doctor can be tracked and recorded, and the data support is provided for the research of the disease by the doctor; the similar patient analysis module 500 is arranged in the system, so that case data of various types of diseases can be automatically generated, and abundant case data are provided for doctors, so that the doctors can be helped to conduct deep research on the various types of diseases; by arranging the case sharing module 600 in the system, the guidance articles obtained based on case data creation can be recommended to different doctors or patients in the system provided by the application, so that the doctors can obtain a learning platform for communication through the system.
While the present application has been described with reference to several exemplary embodiments, it is understood that the terminology used is intended to be in the nature of words of description and illustration rather than of limitation. As the present application may be embodied in several forms without departing from the spirit or essential attributes thereof, it should be understood that the above-described embodiments are not limited by any of the details of the foregoing description, but rather should be construed broadly within its spirit and scope as defined in the appended claims, and therefore all changes and modifications that fall within the metes and bounds of the claims, or equivalence of such metes and bounds are therefore intended to be embraced by the appended claims.
Claims (10)
1. A disease data management system, the system comprising:
the health archive module is used for collecting and processing health state data and work and rest data of patients to generate health archives, wherein the health archives are composed of health archives of different patients;
the doctor-patient relationship establishing module is used for determining a target health file from the health file library, wherein a target patient corresponding to the target health file is a target doctor to follow-up a target guiding treatment;
the medical guidance and tracking module is used for tracking and recording process data of guiding treatment of the target patient by the target doctor;
the similar patient analysis module is used for analyzing and counting the process data generated by guiding the treatment of different patients and the health files of different patients so as to generate case data of various diseases;
and the case sharing module is used for sharing the instruction article which is authored by the doctor based on the case data.
2. The system of claim 1, wherein the health profile module comprises:
the health data acquisition module is used for acquiring health state data of a patient;
the composition statistics module is used for collecting and counting the composition time of the patient so as to obtain the composition data of the patient;
a disease label module for determining a disease label for the patient based on the patient's health status data;
and the data processing module is used for generating a health file of the patient based on the health state data, the work and rest data and the disease label.
3. The system of claim 1, wherein the doctor-patient relationship establishment module comprises:
the attention field report recommending module is used for recommending a health file to the target doctor based on the medical field of attention of the target doctor;
the health record sorting module is used for sorting the health records based on occupation scores of the health records, wherein the occupation scores are used for representing the attention degree of the disease label corresponding to the health records;
the search query module is used for searching and querying the health files;
the health record selecting module is used for determining the target health record through the attention field report recommending module, the health record sorting module and the search query module.
4. The system of claim 1, further comprising a doctor-patient communication module for online communication between the target doctor and the target patient.
5. The system of claim 4, wherein the doctor-patient communication module is further configured to invite other doctors to follow-up together to guide the treatment of the target patient.
6. The system of claim 1, wherein the case sharing module comprises:
the case data editing module is used for generating a guide article authored by a doctor based on the case data;
the case data label module is used for labeling the corresponding article labels for the guide articles;
and the intelligent data pushing module is used for pushing the matched guide articles to the doctor or the patient based on the article labels.
7. The system of claim 1, further comprising a data storage module for storing the health archive, the case data for each type of disease, and the guide article.
8. The system of claim 7, wherein the data storage module is further configured to manage viewing rights of a doctor or patient to the health archive and case data for the types of diseases.
9. The system of claim 7, wherein call interfaces are provided in the data storage module, the call interfaces being respectively connected to the doctor-patient relationship creation module and the case sharing module.
10. The system of claim 1, further comprising a login module for providing a doctor or patient with access to the disease data management system.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2023101516647 | 2023-02-10 | ||
| CN202310151664 | 2023-02-10 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117253622A true CN117253622A (en) | 2023-12-19 |
Family
ID=89135666
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310261119.3A Pending CN117253622A (en) | 2023-02-10 | 2023-03-13 | Disease data management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117253622A (en) |
-
2023
- 2023-03-13 CN CN202310261119.3A patent/CN117253622A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102558021B1 (en) | A clinical decision support ensemble system and the clinical decision support method by using the same | |
| Van Den Block et al. | Transitions between care settings at the end of life in Belgium | |
| Beuscart-Zéphir et al. | Integrating users’ activity modeling in the design and assessment of hospital electronic patient records: the example of anesthesia | |
| RU2267158C2 (en) | Method and system for detection of deviations in controlled environment | |
| Moss et al. | Improving operating room coordination: communication pattern assessment | |
| CN108281195A (en) | A kind of management method and system of medical data | |
| CN106997421B (en) | Intelligent system and method for personalized medical information acquisition and health monitoring | |
| US11715569B2 (en) | Intent-based clustering of medical information | |
| JP2006260437A (en) | Nursing service management system | |
| CN112164469A (en) | Clinical scientific research data acquisition management system | |
| CN111613291A (en) | Medicine management, classification and medical staff and patient association system | |
| Gaffney et al. | Medical documentation burden among US office-based physicians in 2019: a national study | |
| CN116504373A (en) | Comprehensive management information platform for digital intelligent ward | |
| McDonald | Quality measures and electronic medical systems | |
| CN112071412B (en) | Biological sample library management system | |
| US20200234315A1 (en) | Systems and methods for patient retention in network through referral analytics | |
| Tien | Deficits of information management associated with schizophrenia: Awareness and associated integrative cognitive functions | |
| CN117253622A (en) | Disease data management system | |
| Small | Medical Device–Associated Safety and Risk: Surveillance and Stratagems | |
| Kramer et al. | Practical improvements for medical device evaluation | |
| CN113113093A (en) | Clinical and image-based case data management system | |
| CN112259186A (en) | Novel sleep disorder diagnosis and treatment system | |
| CN111950234A (en) | Processing method based on intelligent medical text processing system | |
| CN111950235A (en) | Intelligent medical text processing system | |
| CN111667910A (en) | Pathological management system based on computer medical treatment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |