CN114974530A - Post-diagnosis follow-up method, system and storage medium - Google Patents

Post-diagnosis follow-up method, system and storage medium Download PDF

Info

Publication number
CN114974530A
CN114974530A CN202210503319.0A CN202210503319A CN114974530A CN 114974530 A CN114974530 A CN 114974530A CN 202210503319 A CN202210503319 A CN 202210503319A CN 114974530 A CN114974530 A CN 114974530A
Authority
CN
China
Prior art keywords
follow
patient
doctor
visit
label
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
Application number
CN202210503319.0A
Other languages
Chinese (zh)
Inventor
吴俊宏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhejiang Yuantu Technology Co ltd
Original Assignee
Zhejiang Yuantu Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Zhejiang Yuantu Technology Co ltd filed Critical Zhejiang Yuantu Technology Co ltd
Priority to CN202210503319.0A priority Critical patent/CN114974530A/en
Publication of CN114974530A publication Critical patent/CN114974530A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Biomedical Technology (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

The application relates to the technical field of follow-up systems, in particular to a method, a system and a storage medium for follow-up after diagnosis, which comprises the following steps: the patient registers at the patient end according to the visit information to obtain a corresponding patient account; the platform side acquires and stores a patient account, adds an illness state label to the patient account according to the treatment information corresponding to the patient account, connects the patient side to a corresponding doctor side according to the treatment information and the illness state label, and generates a corresponding follow-up visit task according to a preset follow-up visit template, wherein the illness state label is characterized by the illness type of the patient; and the doctor end carries out follow-up visit according to the follow-up visit task to obtain a follow-up visit result and sends the follow-up visit result to the platform end. The application has the effect of improving the working efficiency of follow-up visits after the diagnosis.

Description

Post-diagnosis follow-up method, system and storage medium
Technical Field
The present application relates to the field of follow-up system technology, and in particular, to a method, a system, and a storage medium for follow-up after diagnosis.
Background
The follow-up visit after the diagnosis refers to a medical rehabilitation observation behavior that the patient changes of the patient are tracked and known regularly by the hospital through various modes, and the patient are matched to complete the follow-up visit task to perform professional rehabilitation guidance on the patient.
In the medical field, a long process is needed for treating and recovering many diseases such as some chronic diseases, and as the average time of hospitalization is shorter and shorter nowadays, the later-stage rehabilitation time of more and more patients at home is longer and longer, which means that the requirements of the patients on the aspects of later-stage nursing, disease observation, health care and the like are higher and higher, and for the return visit work of the patients after the visit, the requirements of the patients on the rehabilitation treatment outside the hospital can be met, and the improvement of the medical treatment and service work of the hospitals can be approached.
At present, when a patient is discharged and recovered outside a hospital, when the patient needs to consult the self recovery problem, a network searching or hospital-visiting consultation method is generally used, and when the patient needs to know the physical condition of the patient, the patient is also contacted with the patient by using contact ways such as a telephone and the like to carry out follow-up work, so that the follow-up mode of the hospital and the patient is low in efficiency, and no method is available for achieving information synchronism and richness.
Disclosure of Invention
In order to improve the working efficiency of the follow-up visit after the diagnosis, the application provides a follow-up visit after the diagnosis method, a follow-up visit after the diagnosis system and a storage medium.
In a first aspect, the following technical scheme is adopted in the post-diagnosis follow-up method provided by the application:
a method of follow-up after a visit, comprising the steps of:
the patient registers at the patient end according to the visit information to obtain a corresponding patient account;
the method comprises the steps that a platform side obtains and stores a patient account, the platform side adds an illness state label to the patient account according to treatment information corresponding to the patient account, the platform side connects the patient side to a corresponding doctor side according to the treatment information and the illness state label and generates a corresponding follow-up task according to a preset follow-up template, and the illness state label is characterized by the illness type of a patient;
and the doctor end carries out follow-up visit according to the follow-up visit task to obtain a follow-up visit result and sends the follow-up visit result to the platform end.
In some embodiments, the adding, by the platform terminal, an illness label to the patient account according to the visit information corresponding to the patient account includes:
acquiring the treatment etiology of the patient according to the injection treatment etiology information, creating an illness state label according to the treatment etiology, and defining the illness state label as a first illness state label;
inputting the treatment etiology into a historical etiology database, and judging whether high-risk complication information associated with the treatment etiology exists in the historical etiology database, wherein the historical etiology database comprises various types of disease information and associated high-risk complication information;
and if so, creating a disease label according to the high-risk complication information associated with the treatment etiology, and defining the disease label as a second disease label.
In some of these embodiments, creating a condition label from the high risk complication information associated with the visit etiology and defining as a second condition label, further comprises:
acquiring key inspection item values in the high-risk complication information associated with the diagnosis etiology, and comparing the inspection item values in the diagnosis information with the key inspection item values to judge whether at least two inspection item values are abnormal, wherein the key inspection item values in the high-risk complication information associated with the diagnosis etiology are characterized as limit theoretical values when the patient suffers from the disease;
if the values of at least two examination items in the information of seeing a doctor are abnormal, setting the second illness state label as an explicit label;
and if the number of the examination items in the information about the doctor is less than two, setting the second illness state label as a recessive label.
In some embodiments, the platform end connects the patient end to a corresponding physician end according to the visit information and the disease label, and generates a corresponding follow-up task according to a preset follow-up template, including:
the platform end stores a follow-up template preset corresponding to various diseases, and the follow-up template at least comprises a patient name, treatment information, a patient contact way, a follow-up date, a follow-up log, a rehabilitation plan, a doctor name and a doctor contact way;
the platform end acquires a corresponding follow-up template according to the disease label;
the platform end automatically carries out initial filling on information in the follow-up visit template according to the visit information and generates a corresponding follow-up visit task, wherein the follow-up visit task comprises a plurality of follow-up visit nodes, and the follow-up visit nodes correspond to a follow-up visit time.
In some embodiments, the follow-up visit by the physician end according to the follow-up visit task to obtain a follow-up visit result includes:
the doctor end receives a follow-up task, connects with the patient end for follow-up according to a follow-up node of the follow-up task, and updates and fills a follow-up template corresponding to the follow-up node in the follow-up task according to the follow-up process;
after the follow-up visit is completed, the doctor end stores the updated and filled follow-up visit template to the platform end to obtain a follow-up visit result, and the patient obtains and checks the follow-up visit result through the patient end.
In some embodiments, the physician end includes a doctor seeing end, a doctor interfacing end and a doctor on duty end, the platform end connects the patient end to the corresponding physician end according to the doctor seeing information, and the patient uses the patient end to perform a disease inquiry, including the following steps:
the platform end comprises a consultation question-answer library and is used for judging whether the patient condition inquiry of the patient is contained in the consultation question-answer library;
if yes, the docking physician end obtains a reply right, and obtains a reply dialect matched with the disease inquiry through consulting a question-answering library to reply;
if not, the end-to-end doctor transmits the reply content and the reply authority to the end-to-be-treated doctor for authority examination and approval after replying, if the end-to-be-treated doctor passes the authority examination and approval, the reply content is sent to the patient end, and if the end-to-be-treated doctor does not pass the authority examination and approval, the reply content is cleared and the reply authority is moved to the end-to-be-treated doctor;
if the reply time to the doctor end exceeds the preset time, the reply authority is moved to the on-duty doctor end, and the on-duty doctor end judges whether the disease inquiry is contained in the consultation question-answer library for reply.
In some embodiments, the platform end pushes the propaganda and education content into the patient account according to the disease label corresponding to the patient account, and specifically includes the following steps:
if the patient account only contains a first disease label, pushing corresponding first order propaganda and education content according to the first disease label;
if the patient account number comprises a first illness state label and a second illness state label, pushing corresponding first order propaganda and education contents according to the first illness state label and pushing corresponding second order propaganda and education contents according to the second illness state label, wherein the pushing priority of the first order propaganda and education contents is higher than that of the second order propaganda and education contents.
In some of these embodiments, a scoring method is also included, comprising the steps of:
after the doctor end carries out interactive updating actions based on the operation of the patient end, the platform end carries out intelligent scoring on the doctor end based on a preset first scoring rule to obtain a first score, the patient end carries out manual scoring on the doctor end based on a preset second scoring rule to obtain a second score, and the platform end receives the first score and the second score, calculates a final score according to the preset scoring rule and associates the final score with an account number of the doctor end for displaying.
In a second aspect, the present application provides a follow-up system after a diagnosis, which adopts the following technical scheme:
a post-visit system comprising a patient end, a platform end, and a physician end, wherein:
the patient side is used for registering the patient at the patient side according to the visit information to obtain a corresponding patient account, and the patient uses the patient side to check the follow-up result;
the platform end comprises a storage module, a follow-up module and a label module, the platform end acquires a patient account and connects the patient end to a corresponding doctor end according to the visit information, the storage module stores the patient account, the label module is used for adding an illness state label to the patient account according to the visit information corresponding to the patient account, and the follow-up module is used for generating a corresponding follow-up task according to a preset follow-up template;
and the doctor end is used for the doctor to follow up the patient at the patient end according to the follow-up task so as to obtain a follow-up result.
In a third aspect, the present application provides a computer storage medium, which adopts the following technical solutions:
a computer storage medium having stored thereon a computer program which, when executed by a processor, implements any of the above-described post-visit methods.
To sum up, the application comprises the following beneficial technical effects:
1. the patient registers at the patient end according to the information of seeing a doctor, obtains a corresponding patient account, obtains a corresponding illness state label according to the information of seeing a doctor and displays the illness state label, is connected to a corresponding doctor end according to doctor information filled in the information of seeing a doctor, realizes online connection between the patient end and the doctor end, can obtain a corresponding follow-up visit task through the illness state label displayed at the patient end, is connected with the patient end to carry out online follow-up visit, and sends a follow-up visit result to a platform end for the patient to check, realizes quick establishment of the follow-up visit task, conveniently carries out follow-up visit work in an online mode, does not need the patient to repeatedly go to a hospital and carry out follow-up review under the line with the doctor during rehabilitation, and improves follow-up visit efficiency.
Drawings
FIG. 1 is a schematic overall flow diagram of an embodiment of the present application;
FIG. 2 is a logic diagram illustrating the setting of a disease flag in an embodiment of the present application;
FIG. 3 is a schematic flow chart of a follow-up procedure performed in an embodiment of the present application;
FIG. 4 is a logic diagram illustrating the response to a query in an embodiment of the present application;
FIG. 5 is a logic diagram illustrating the determination of whether the reply time is exceeded when a query reply is performed in the embodiment of the present application;
fig. 6 is a schematic flowchart of the evaluation performed by the physician side in the embodiment of the present application.
Detailed Description
For a clearer understanding of the objects, aspects and advantages of the present application, reference is made to the following description and accompanying drawings. However, it will be apparent to one of ordinary skill in the art that the present application may be practiced without these specific details. In some instances, well known methods, procedures, systems, components, and/or circuits have been described at a higher level without undue detail in order to avoid obscuring aspects of the application with unnecessary detail. It will be apparent to those of ordinary skill in the art that various changes can be made to the embodiments disclosed herein, and that the general principles defined herein may be applied to other embodiments and applications without departing from the principles and scope of the present application. Thus, the present application is not limited to the embodiments shown, but is to be accorded the widest scope consistent with the scope of the present application as claimed.
Unless defined otherwise, technical or scientific terms referred to herein shall have the same general meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in this application, the terms "a," "an," "the," and the like do not denote a limitation of quantity, but rather are used in the singular or the plural. The terms "comprises," "comprising," "has," "having," and any variations thereof, as referred to in this application, are intended to cover non-exclusive inclusions; for example, a process, method, and system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or modules, but may include other steps or modules (elements) not listed or inherent to such process, method, article, or apparatus.
Reference to "a plurality" in this application means two or more. In general, the character "/" indicates a relationship in which the objects associated before and after are an "or". The terms "first," "second," "third," and the like in this application are used for distinguishing between similar items and not necessarily for describing a particular sequential or chronological order.
The terms "system," "engine," "unit," "module," and/or "block" referred to herein is a method for distinguishing, by level, different components, elements, parts, components, assemblies, or functions of different levels. These terms may be replaced with other expressions capable of achieving the same purpose. In general, reference herein to a "module," "unit," or "block" refers to a collection of logic or software instructions embodied in hardware or firmware. The "modules," "units," or "blocks" described herein may be implemented as software and/or hardware, and in the case of implementation as software, they may be stored in any type of non-volatile computer-readable storage medium or storage device.
In some embodiments, software modules/units/blocks may be compiled and linked into an executable program. It will be appreciated that software modules may be invokable from other modules/units/blocks or from themselves, and/or may be invoked in response to detected events or interrupts. The software modules/units/blocks configured for execution on the computing device may be provided on a computer readable storage medium, such as a compact disk, digital video disk, flash drive, magnetic disk, or any other tangible medium, or downloaded as digital (and may be initially stored in a compressed or installable format that requires installation, decompression, or decryption prior to execution). Such software code may be stored partially or wholly on a storage device of the executing computing device and applied in the operation of the computing device. The software instructions may be embedded in firmware, such as an EPROM. It will also be appreciated that the hardware modules/units/blocks may be included in connected logic components, such as gates and flip-flops, and/or may be included in programmable units, such as programmable gate arrays or processors. The modules/units/blocks or computing device functions described herein may be implemented as software modules/units/blocks, and may also be represented in hardware or firmware. Generally, the modules/units/blocks described herein may be combined with other modules/units/blocks or, although they are physically organized or stored, may be divided into sub-modules/sub-units/sub-blocks. The description may apply to the system, the engine, or a portion thereof.
It will be understood that when an element, engine, module or block is referred to as being "on," "connected to" or "coupled to" another element, engine, module or block, it can be directly on, connected or coupled to or in communication with the other element, engine, module or block, or intervening elements, engines, modules or blocks may be present, unless the context clearly dictates otherwise. In this application, the term "and/or" may include any one or more of the associated listed items or combinations thereof.
The present application is described in further detail below with reference to figures 1-6.
The embodiment of the application discloses a follow-up method after diagnosis.
As shown in fig. 1, one method of follow-up after diagnosis includes:
and S100, the patient registers at the patient end according to the visit information to obtain a corresponding patient account.
The information of seeing a doctor includes the name, sex, contact way, ID card number, doctor's end of seeing a doctor, registration information, inspection numerical value, inspection result, information of getting it filled in by way of filling in manually, and registration information, inspection numerical value, inspection result, information of getting it filled in by way of taking pictures, after the patient registers, can get the patient's corresponding and unique account number of patient, this account number is used for the record object information of the whole process of this patient's physiotherapy of representation.
When a subsequent patient wants to log in the account again, only the login information preset during registration needs to be input, such as an identification number, a mobile phone number and the like.
S200, the platform side acquires and stores the patient account, adds the illness state label to the patient account through the treatment information corresponding to the patient account, connects the patient side to the corresponding doctor side according to the treatment information and the illness state label, and generates a corresponding follow-up visit task according to a preset follow-up visit template.
Wherein the disease signature is indicative of the type of illness of the patient. If the internal display of the medical information of the patient a indicates that the systolic pressure of the patient a is 170mmHg and the diastolic pressure of the patient a is 101mmHg, which are greater than the systolic pressure of 120-.
As shown in fig. 2, S210, a medical treatment cause of the patient is obtained according to the medical treatment information, and a medical condition label is created according to the medical treatment cause and defined as a first medical condition label.
When a patient visits a doctor in a hospital, a patient condition examination result and a disease cause are often obtained after examination, after an operation and the like, for example, in case of a disease, besides an examination numerical value and an operation log, the type of the disease, such as fracture, cancer, coronary heart disease and the like, is written, at the moment, the platform end can obtain the disease type, namely the disease cause, in the disease information through picture recognition and a neural algorithm according to the disease information uploaded by the patient at the patient end, such as medical record pictures and the like, and the disease type, namely the disease cause, is created according to the disease cause, is an explicit label, namely, is displayed on a patient account of the patient, and is defined as a first disease label.
For example, before the patient a is admitted, the patient a is admitted with a hospitalization diagnosis of cerebral infarction and when the patient is discharged after treatment, cerebral infarction and hyperhomocysteinemia are diagnosed at the time of discharge, which may be a case where a related disease occurs due to cerebral infarction during hospitalization, and at this time, depending on the time end of uploading the visit information by the patient, "cerebral infarction" is used as the first disease condition label if the patient uploads the visit information during the examination without admission, and the first disease condition label is updated to "cerebral infarction" and "hyperhomocysteinemia" if the patient uploads the visit information again at the time of discharge. It should be noted that, during the procedure of patient admission for treatment, the physician may also manually update the first disease label of the patient by updating the medical log.
S211, inputting the diagnosis cause into a historical cause database, and judging whether high-risk complication information related to the diagnosis cause exists in the historical cause database.
When the platform end acquires the treatment etiology of the patient, the platform end can deduce whether the patient possibly has high-risk complications associated with the treatment etiology according to the treatment etiology. And a historical etiology library is arranged in the platform end, diseases obtained by all patients in the historical diagnosis process and high-risk complication conditions occurring in the treatment and treatment process are stored in the historical etiology library, and the incidence relations of various original diseases and complications are integrated and connected to obtain a disease extraction library formed by a plurality of groups of incidence disease strings, wherein the incidence disease strings can be one-to-one or one-to-many, for example, when hypertension is used as an original disease, the existing high-risk complications are stroke, cerebral infarction, cerebral thrombosis, glomerular arteriosclerosis, kidney damage and renal failure, and the high-risk complications of shoulder fracture are arthritis.
If the mild cold is mild in symptoms, high-risk complications cannot appear in most cases, and whether the mild cold is aggravated or not can be further judged according to clinical results, and whether corresponding high-risk complications exist or not can be further judged.
Wherein, the historical etiology base of a plurality of networked hospitals can be shared.
And S212, if the disease condition label exists, creating a disease condition label according to the high-risk complication information related to the treatment etiology, and defining the disease condition label as a second disease condition label.
If the patient treats pneumonia, after the patient uploads the diagnosis information, the platform end obtains the diagnosis etiology of the patient as pneumonia according to the diagnosis information, and outputs the pneumonia into the historical etiology library, and the high-risk complications associated with the pneumonia in the historical etiology library are sepsis, viral myocarditis and respiratory failure, and at the moment, the platform end defines the three high-risk complications as a second disease label.
By the method, when the disease label of the patient is defined, the diagnosed disease condition can be marked, and the high-risk complication possibly occurring in the patient can be marked, so that the patient and a doctor can mark and early warn the diseased disease and the disease possibly complicated in the future in advance and prepare for prevention in advance. If a doctor sees that a patient suffers from pneumonia, the doctor can synchronously check physical examination indexes of possible high-risk complications while treating the pneumonia, and the possibility that sudden complications cannot be timely treated is reduced.
Further, since a large number of high-risk complications are associated with diseases related to blood vessels, heart, organs, etc., and the second disease label is added to the large number of high-risk complications, not only too many disease labels are displayed on the patient account, but also anxiety of the patient is increased, and much stress is added to the work of the doctor, the method further includes the following steps in order to perform certain management classification on the second disease label in S212:
s213, key examination item values in the high-risk complication information associated with the treatment etiology are obtained, and the examination item values in the treatment information are compared with the key examination item values to judge whether at least two examination item values are abnormal.
The important examination item value associated with the diagnosis etiology is characterized as the limit theoretical value when the patient suffers from the disease, and when a certain value is higher or lower than the limit theoretical value, the examination item value is determined to be abnormal, and if the value is higher or lower than the limit theoretical value, the examination item value is specified by clinical medical rules.
If patient a suffers from pneumonia, and the high-risk complications are "sepsis", "viral myocarditis", and "respiratory failure", we take "sepsis" as an example, the key examination items of sepsis are leukocytes, c-reactive protein, plasma procalcitonin, creatinine, blood coagulation function, platelets, plasma total bilirubin, blood lactic acid, and the like, these indexes are key examination items for judging whether sepsis occurs, and the examination item values in the diagnosis information are compared with the key examination item values to judge whether there is abnormality in the values.
S214, if the values of at least two examination items in the visit information are abnormal, setting the second illness state label as an explicit label.
Also in the above-mentioned "sepsis" as an example, when the number of leukocytes is more than 12 × 10 to 9 th power per liter or less than 4 × 10 to nine th power per liter, the examination item value of leukocytes is abnormal, when c-reactive protein exceeds two times the standard deviation of the normal value or more, the examination item value of c-reactive protein is abnormal, when plasma procalcitonin exceeds two times the standard deviation of the normal value or more, the examination item value of plasma procalcitonin is abnormal, when creatinine is increased more than 44.2 micromolar per liter, the examination item value of creatinine is abnormal, when the activated partial thromboplastin time aptt is more than 60 seconds, the examination item value of blood coagulation function is abnormal, when platelets is less than 100 × 10 to nine times per liter, the examination item value of platelets is abnormal, and when blood lactate is more than 1 millimolar, the examination item value of blood lactate is abnormal.
Then, after comparing the values of the plurality of examination items in the information of the diagnosis with the values of the key examination items, the results show that the values of the leukocytes, the c-reactive protein, the creatinine and the platelets of the patient A fall outside the limit theoretical values of the key examination items, which indicates that the four examination items are abnormal, and the number of the abnormal examination items is more than two, so that the patient is considered to be most likely to suffer from pneumonia and also suffer from sepsis, which is a high-risk complication of pneumonia, and the "sepsis" is taken as a dominant second disease label and displayed on the account of the patient, so as to remind the patient and the doctor of paying attention to the possibility of the occurrence of the complication.
By analogy, as shown in fig. 2, the examination item values in the patient visit information are compared with the key examination item values of the high-risk complications, and the complications at higher risk are screened out and displayed as an explicit label.
S215, if the number of the examination items in the information about the doctor is less than two, the second disease label is set as a recessive label.
Taking the above-mentioned "sepsis blood" as an example, when the examination item value in the visit information is compared with the key examination item value, it is found that only the data of the white blood cells is abnormal, and then it is considered that the patient a has a high probability of not suffering from the high-risk complication of sepsis blood yet, the second condition label is set as a recessive label, and the recessive second condition label is not displayed on the account of the patient but is hidden, so that the psychological burden on the patient is reduced, and the working pressure of a doctor is also reduced. When the result of the examination item in the follow-up visit information is updated, if the numerical value of the result of the examination item changes and results in an abnormality of more than two examination item results, the recessive second disease label is updated to be the dominant second disease label.
By the method, the classified labels are set for the high-risk complications possibly caused by the diagnosis etiology, the patient and the doctor can be reminded of the possibility of the complications possibly existing in the patient and the doctor by setting the explicit second disease label, the patient can conveniently prepare in advance and the doctor can conveniently perform subsequent follow-up treatment, the implicit second disease label can be used for counting the complications with lower current disease probability in advance, the condition of causing the complications by the doctor is not required to be considered all the time, and the working pressure of the doctor is reduced.
Further, in order to improve the intuitiveness of the prompt of the disease condition label, the platform end can distinguish colors of the disease condition label, the distinguishing rule can be modified by daily use of accumulated opinions, for example, the first disease condition label with serious disease conditions uses a red label, the first disease condition label with lighter disease conditions uses a green label, the second disease condition label uses a yellow label, acute diseases uses an orange label, chronic diseases uses yellow labels and the like, and because the patient possibly does not know the rarely used diseases and complications, the patient possibly has serious diseases but does not pay attention to the patient, or the patient with lighter disease conditions excessively worrys, the disease condition labels are distinguished by setting the labels with different colors, and the patient can roughly know the degree of urgency of the self diseases through the colors of the labels.
Furthermore, in order to reduce the misjudgment of the second disease label, when the patient end sees that a certain second disease label representing a complication is displayed on the patient account of the patient end, the patient end can manually cancel or hide the second disease label when the second disease label displayed on the second disease label does not exist after communicating with a doctor, and then the second disease label can be manually displayed after the complication symptom appears or the complication is determined to be suffered.
The patient side is a mobile networking device used in daily life, such as a mobile phone, a tablet personal computer, a notebook computer, a desktop computer and the like, and also can be a mobile electronic watch or a patient rehabilitation bracelet customized by a hospital, and because the patient most often uses the mobile phone or the portable watch or bracelet to check the patient account number of the patient, after the patient is ill, a plurality of second disease condition labels representing complications may be provided, the labels may not be displayed on the mobile phone together, and at the same time, the interface is too bulky even if the labels can be displayed together, in another embodiment, one patient side interface only displays one first disease condition label and one second disease condition label beside the patient account number, and the second disease condition label is screened out by the platform side through an algorithm, and can also be manually adjusted by the patient, the remaining second illness state labels are displayed on the second illness state labels in a quantity corner mark mode, if one patient has four second illness state labels, only one second illness state label A is displayed, the remaining three second illness state labels display a '3' at the upper right part of the A, the three remaining second illness state labels which are not displayed are compressed, and a user can click on the uniquely displayed second illness state label to check all the second illness state labels. The same applies to the subsequent physician.
As shown in fig. 3, the platform end connects the patient end to the corresponding physician end according to the visit information and the disease label, and generates the corresponding follow-up task according to the preset follow-up template, including the following steps:
and S220, the platform end acquires a corresponding follow-up template according to the disease condition label.
The platform end is internally pre-stored with follow-up templates corresponding to various diseases, and the follow-up templates at least comprise patient names, treatment information, patient contact ways, follow-up dates, follow-up logs, rehabilitation plans, doctor names, doctor contact ways and the like.
The follow-up template has some details, and different diseases are slightly different, for example, the follow-up date, the follow-up log, the rehabilitation plan template and the like in the follow-up template are different according to the treatment time such as acute diseases, chronic diseases and the like.
And the platform end searches for a corresponding follow-up visit template according to the content in the disease label, and if the first disease label of the patient A is diabetes, the platform end selects the follow-up visit template corresponding to the diabetes from the stored preset follow-up visit templates. By the method, the contents in the follow-up template can be conveniently filled and updated by a doctor, because if all diseases use one follow-up template together, the condition that the follow-up template cannot be matched with the follow-up process in the follow-up process may occur, and a plurality of follow-up templates are classified according to diseases, so that the correspondence and the efficiency can be improved.
To take a more extreme example, if the patient a has cancer and the patient B has bacterial enteritis, the platform end acquires the corresponding follow-up template through the first disease label of the "cancer" of the patient a, and simultaneously acquires the corresponding follow-up template through the first disease label of the "bacterial enteritis" of the patient B, while the disease condition of the patient a is obviously more serious than that of the patient B, and the treatment time, treatment period and treatment method of the cancer are completely different from those of the bacterial enteritis, so that the follow-up period, follow-up date, rehabilitation plan and the like in the follow-up template of the patient a are necessarily completely different from those of the patient B. Therefore, the follow-up templates of different diseases are classified and managed, and the follow-up work is facilitated to be carried out quickly.
It should be noted that the generation of the follow-up template only aims at the first disease label, and does not consider the second disease label in the automatic generation stage, because the second disease label represents a complication, and the complication is likely not to occur, in this case, if the generation of the follow-up template according to the second disease label increases the workload of the doctor, and the generation of the follow-up template aiming at the second disease label can wait for the further treatment, for example, when the diagnosis of the complication in the second disease label occurs, the doctor manually generates the follow-up template by the doctor.
And S221, the platform end automatically performs initial filling on the information in the follow-up visit template according to the visit information, and generates a corresponding follow-up visit task.
The platform terminal automatically fills in basic information in the follow-up template according to the visit information, such as the name, sex, contact way, doctor name, disease type, examination item data and the like of the patient, generates a corresponding follow-up task after filling in, and sends the follow-up task to a corresponding doctor terminal. When the platform end is filled with the data, the name of the doctor associated with the patient can be obtained according to the doctor information, and the corresponding follow-up task can be sent to the corresponding doctor end according to the doctor information.
The follow-up task comprises a plurality of follow-up nodes, and the plurality of follow-up nodes correspond to one follow-up time.
And S300, the doctor end performs follow-up visit according to the follow-up visit task to obtain a follow-up visit result, and sends the follow-up visit result to the platform end.
And S310, receiving the follow-up task by the doctor end, performing follow-up visit with the patient end according to the follow-up node of the follow-up task, and updating and filling the follow-up template corresponding to the follow-up node in the follow-up task according to the follow-up process.
And S320, after the follow-up visit is completed, the doctor end stores the updated and filled follow-up visit template in the platform end to obtain a follow-up visit result, and the patient obtains and checks the follow-up visit result through the patient end.
If the patient A needs to follow up once a week, the follow-up time is 5 pm weekly, then in this follow-up time, the doctor needs to connect with the patient end to perform the follow-up task under the node, and update and fill the contents in the follow-up template according to the follow-up process, such as the overall condition, medication condition, follow-up judgment, next hospital arrival check time, and the like of the current patient. After the follow-up task of the node is completed, the doctor sends the updated and filled follow-up result to the platform end, and the patient end can check the follow-up result.
In order to remind the doctor of the follow-up node of each follow-up task, a reminding function can be set at a preset time at the front end of the follow-up time corresponding to each follow-up node, and the doctor is reminded through the doctor end in modes of ringing and the like.
Sometimes, a doctor forgets to perform follow-up tasks due to more work, so that a patient end has a filling authority for a blank follow-up template on a certain follow-up node within a preset time at one end, it needs to be noted that the filling authority of the patient end can only be used for the blank follow-up template, because a non-blank follow-up template is necessarily filled after the doctor end performs follow-up, the patient may unintentionally modify the content on the follow-up template, which may affect subsequent treatment, and a user may modify the follow-up template on the corresponding node at the time point only when the doctor does not perform follow-up at a preset time, the modified authority may be limited to only the contents of follow-up logs, the overall condition of the patient, the condition of medication and the like, so that the patient may record some states of the patient first when the doctor cannot perform follow-up, and after seeing the contents of the follow-up template updated by the patient through the doctor end, the follow-up doctor updates and modifies the follow-up template so as to ensure the continuity of the follow-up task.
As shown in fig. 4 and 5, besides receiving a follow-up visit, a patient may have some questions to ask a doctor in the course of daily treatment or rehabilitation, and at this time, the patient may be inconvenient to go to a hospital, and at this time, the patient may go to the internet for inquiry, and the network often has many wrong information, which may have a negative effect on the rehabilitation of the patient, and at this time, how to ensure the smooth on-line communication between the patient side and the doctor side is very important.
In another embodiment, the physician side includes a doctor visit side, a physician docking side, and a physician on duty side. The doctor end is an attending doctor responsible for examination and treatment work of the patient when the doctor end is in the process of seeing a doctor, the doctor end is a docking doctor related to the doctor, can be other doctors in the same department or doctors managed by the docking doctor, and the like, and is mainly responsible for docking and communicating with the patient when the doctor is busy. While the doctor on duty is responsible for dealing with some emergency doctors when neither the doctor on duty nor the clinician on duty is online, the doctor on duty generally remains online for 24 hours.
After the platform end connects the patient to the corresponding doctor end according to the visit information, the patient uses the patient end to inquire the disease condition, and the method comprises the following steps:
s400, judging whether the patient' S disease inquiry is contained in the consulting question-answering library.
And S410, if the answer is included, obtaining the answer authority to the doctor end, and obtaining an answer word matched with the disease inquiry by consulting the question-answer library to answer.
And S420, if the answer is not contained, the answer content and the answer authority are transferred to the doctor seeing a doctor end for authority examination and approval after the answer is sent to the patient seeing a doctor, if the doctor seeing a doctor passes the authority examination and approval, the answer content is sent to the patient, and if the doctor seeing a doctor does not pass the authority examination and approval, the answer content is cleared and the answer authority is moved to the doctor seeing a doctor.
The consultation question-answer library comprises a platform end, a large number of common questions of patients, such as the dosage of a certain medicament, the questions possibly brought by the change of the body of the patient, the time for appointment registration, the time for the doctor to go out of the doctor, the questions of the numerical values of the examination items and the like, are stored in the consultation question-answer library, and corresponding answer phony is set for each question, such as the using method of the A medicament, the A medicament is eaten twice a day, 3 pills are taken each time, the time for the doctor A to go out of the doctor A is from eight early to five late of Monday to Thursday, and the like.
When the patient asks questions through the patient end, the doctor at the end of the butt-joint doctor sees the questions, searches whether the corresponding answer words exist in the consultation question-answer library, and if yes, the answer words in the consultation question-answer library are directly used for replying. The query method may use a common keyword extraction method, such as a drug name, a doctor name, and the like, each keyword may correspond to a plurality of questions, and the plurality of questions correspond to a plurality of answer words, for example, when a doctor searches for a drug a, a plurality of questions may occur, such as a use method of the drug a, a use taboo of the drug a, a price of the drug a, a side effect of the drug a, and the doctor may select a corresponding answer word to reply.
Nowadays, a method for automatically identifying keywords by a platform end and automatically searching for a reply word operation through the keywords is used in many fields, but in the application, because of the fact that in the medical field, the method has relatively clear attention to the problems of a patient, if the condition of a reply error occurs through automatic intelligent reply, a great safety accident can occur when the patient eats the wrong medicine, so in the embodiment, the method for manually inquiring the keywords and manually selecting the corresponding reply word operation by a doctor is used, and the problem that the health of the patient is influenced due to the occurrence of the wrong reply is avoided.
Some questions have certain pertinence and cannot be found in the consulting question-answering library, and the docking physicians can manually answer the questions. When a patient sees a doctor, an attending doctor can make a set of rehabilitation plan and follow-up visit plan according to the illness state of the patient, and when the patient asks some problems of rehabilitation contents or follow-up visit contents, the butt-joint doctor may have the situation of wrong response due to the fact that the butt-joint doctor does not know the rehabilitation plan and the follow-up visit plan, and in order to avoid the situation, after the butt-joint doctor manually responds to the problems, the butt-joint doctor needs to pass through the authority examination and approval of the end of the doctor seeing a doctor.
At the moment, the reply content and the reply authority are sent to the doctor end, after the doctor receives the reply content, the doctor checks the reply content to judge whether the permission examination and approval is passed, if the doctor considers that the reply content has no problem, the doctor passes the permission examination and approval, and the reply content is directly sent to the patient end; if the doctor feels that the reply content conflicts with the rehabilitation plan and the follow-up plan set by the doctor, the doctor does not pass the authority examination and approval, the reply content of the end-to-end doctor is automatically deleted, and the end-to-end doctor needs to reply the question and send the reply content to the patient end through the reply authority.
The method has the advantages that after the end-to-end doctor answers, the doctor-seeing end only needs to check whether the content meets the requirement, if yes, the doctor-seeing end does not need to answer, the workload of the main doctor is reduced, the answering content can be guaranteed to have a correct rehabilitation effect on the patient, and when the requirement is not met, the main doctor can answer by himself, so that the accuracy of the answering content is guaranteed while the workload is reduced.
S430, if the reply time of the end to the doctor exceeds the preset time, the reply authority is moved to the end on duty, and the end on duty judges whether the disease is queried semi-soundly in the inquiry and answer library to reply.
Sometimes, the problem that the butting doctor cannot answer the problem in time due to work needs occurs, so that a preset time is set, which can be 3 minutes or 5 minutes, when the preset time is exceeded, the authority for answering the problem is moved to a 24-hour online doctor on duty end, and the doctor on duty can answer the problem. When the on-duty doctor replies, the logic is the same as that of the reply to the doctor end, if the questions are contained in the consultation question-answer library, the questions are replied through the reply operation in the library, if the questions do not exist, the questions are manually replied and the authority of the doctor end needs to be passed.
Therefore, the communication timeliness of the patient end and the doctor end can be ensured, so that the problems of the patient can be answered as soon as possible, and long-time waiting is not needed.
The platform end can also push propaganda and education content to the patient account according to the state of illness label that the patient account corresponds, specifically includes:
and S500, if the patient account only contains the first disease condition label, pushing corresponding first order propaganda and education content according to the first disease condition label.
And S510, if the patient account number comprises a first disease condition label and a second disease condition label, pushing a corresponding first order propaganda and education content according to the first disease condition label, and pushing a corresponding second order propaganda and education content according to the second disease condition label, wherein the pushing priority of the first order propaganda and education content is higher than that of the second order propaganda and education content.
The propaganda and education means propaganda and education, and a doctor end can upload a large number of videos, articles, thesis and other contents of various diseases about treatment, rehabilitation, prevention and other topics to a platform end and classify the diseases according to different disease types.
And the platform end carries out directional pushing on the announced contents according to the disease label in the diseased account.
When the first disease condition label is a diagnosis cause and the second disease condition label is a complication, the priority level of pushing is required to be set when the content is pushed, and as the patient can feel tired after watching a plurality of propaganda and education contents, if the propaganda and education contents corresponding to the two labels are pushed together, the patient can possibly not see the content corresponding to the first disease condition label after seeing the content corresponding to the second disease condition label, so that the priority level of pushing the first antecedent propaganda and education contents is higher than that of pushing the second antecedent and education contents.
As shown in fig. 6, in order to prompt the physician to perform follow-up and answering work on the patient in time, the scoring method includes the following steps:
s600, after the doctor end carries out interactive updating action based on the operation of the patient end, the platform end carries out intelligent scoring on the doctor end based on a preset first scoring rule to obtain a first score, the patient end carries out manual scoring on the doctor end based on a preset second scoring rule to obtain a second score, the platform end calculates a final score according to a preset scoring rule after receiving the first score and the second score, and the final score is related to an account number of the doctor end to be displayed
Performing an interactive update action refers to: follow-up visits between the patient side and the doctor side, responses to questions from the patient side by the doctor side, updates of rehabilitation plans from the patient side by the doctor side, and the like.
Wherein the first scoring rule is: scoring according to the corresponding time of interaction at the doctor end, solving within a specified time, if a problem issued by the patient end is recovered within the specified time or a follow-up task is performed within the specified time, giving 5 points (in this example, 5 points are full points), and making a proper amount of deduction according to the time length exceeding the specified time, if the response is performed within 10 minutes, if the response exceeds ten minutes, 1 point is deducted every 5 minutes, and the like, and calculating the final score.
The second scoring rule is: scoring based on the overall experience of the patient using the patient side, such as the length of time the response is received, the physician's level of care during the follow-up, the satisfaction with the follow-up results, the satisfaction with the announcements being pushed, etc., may optionally be given a score of 0-5 (in this example, a score of 5 is full). Meanwhile, in order to know the opinions of the patients, the patients can fill out the deduction reason and the opinions while scoring so as to prompt corresponding doctors to correct the comments.
When the platform receives the first score and the second score, the calculation may be performed by taking an average value or weighting. The average value is simple, if the first score is 5 points and the second score is 4 points, the calculated average value is 4.5 points, and finally 4.5 points are used as the final score and are related to the account number of the doctor end for displaying. The weighting mode is used because the intelligent scoring of the platform end intelligently responds according to the time of the interactive reply, and the scoring of the patient represents the real experience of the patient, so the scoring of the patient represents the service quality of the doctor end in a larger sense, so the first scoring can occupy 30% of weight coefficient, the second scoring occupies 70% of weight coefficient, and if the first scoring is 5 points and the second scoring is 3 points, the scoring is 3.6 points after the calculation of (5 0.3+3 x 0.7).
In actual application, the scoring rules can be modified according to problems occurring in the specific implementation process.
In another embodiment, a post-visit system is also disclosed, comprising a patient end, a platform end, and a physician end.
The patient side is used for registering the patient at the patient side according to the visit information to obtain a corresponding patient account, and the patient uses the patient side to check the follow-up result;
the platform end comprises a storage module, a follow-up module and a tag module, the platform end acquires a patient account and connects the patient end to a corresponding doctor end according to the visit information, the storage module stores the patient account, the tag module is used for adding an illness state tag to the patient account according to the visit information corresponding to the patient account, and the follow-up module is used for generating a corresponding follow-up task according to a preset follow-up template;
the doctor end is used for the doctor to follow up the visit to the patient of patient end according to the follow-up task to obtain the follow-up result.
Further, the platform end also comprises a historical etiology library, a consulting question-answering library, a reply module, an authority module, a propaganda module, a scoring module and the like.
A follow-up system after a visit can also be used for functions such as appointment registration, patient complaints, satisfaction survey and the like.
Another embodiment discloses a computer storage medium having a computer program stored thereon, the computer program when executed by a processor implementing the method of post-visit described above.
The above are preferred embodiments of the present application, and the scope of protection of the present application is not limited thereto, so: all equivalent changes made according to the structure, shape and principle of the present application shall be covered by the protection scope of the present application.

Claims (10)

1. A method of follow-up after a diagnosis, comprising the steps of:
the patient registers at the patient end according to the visit information to obtain a corresponding patient account;
the platform end acquires and stores a patient account, adds an illness state label to the patient account according to the patient information corresponding to the patient account, connects the patient end to a corresponding doctor end according to the patient information and the illness state label, and generates a corresponding follow-up visit task according to a preset follow-up visit template, wherein the illness state label is characterized by the illness type of the patient;
and the doctor end carries out follow-up visit according to the follow-up visit task to obtain a follow-up visit result and sends the follow-up visit result to the platform end.
2. The method of claim 1, wherein the platform adds an illness label to the patient account according to the visit information corresponding to the patient account, and the method comprises:
acquiring the treatment etiology of the patient according to the injection treatment etiology information, creating an illness state label according to the treatment etiology, and defining the illness state label as a first illness state label;
inputting the treatment etiology into a historical etiology database, and judging whether high-risk complication information associated with the treatment etiology exists in the historical etiology database, wherein the historical etiology database comprises various types of disease information and associated high-risk complication information;
and if so, creating a disease label according to the high-risk complication information associated with the treatment etiology, and defining the disease label as a second disease label.
3. A method of follow-up after diagnosis as claimed in claim 2, wherein: creating a condition label according to the high-risk complication information associated with the visit etiology, and defining the condition label as a second condition label, further comprising:
acquiring key inspection item values in the high-risk complication information associated with the diagnosis etiology, and comparing the inspection item values in the diagnosis information with the key inspection item values to judge whether at least two inspection item values are abnormal, wherein the key inspection item values in the high-risk complication information associated with the diagnosis etiology are characterized as limit theoretical values when the patient suffers from the disease;
if the number of at least two examination items in the information about the doctor is abnormal, setting the second disease label as an explicit label;
and if the number of the examination items in the information about the doctor is less than two, setting the second illness state label as a recessive label.
4. A method of follow-up after diagnosis as claimed in claim 1, wherein: the platform end connects the patient end to the corresponding doctor end according to the visit information and the illness state label and generates a corresponding follow-up task according to a preset follow-up template, and the follow-up task comprises the following steps:
the platform end stores a follow-up visit template preset corresponding to each disease, wherein the follow-up visit template at least comprises a patient name, treatment information, a patient contact way, a follow-up visit date, a follow-up visit log, a rehabilitation plan, a doctor name and a doctor contact way;
the platform end acquires a corresponding follow-up template according to the disease label;
the platform end automatically carries out initial filling on information in the follow-up visit template according to the visit information and generates a corresponding follow-up visit task, wherein the follow-up visit task comprises a plurality of follow-up visit nodes, and the follow-up visit nodes correspond to a follow-up visit time.
5. A method of follow-up after diagnosis as claimed in claim 4, wherein: the doctor end carries out follow-up visit according to the follow-up visit task to obtain a follow-up visit result, and the follow-up visit result comprises the following steps:
the doctor end receives a follow-up task, connects with the patient end for follow-up according to a follow-up node of the follow-up task, and updates and fills a follow-up template corresponding to the follow-up node in the follow-up task according to the follow-up process;
after the follow-up visit is completed, the doctor end stores the updated and filled follow-up visit template to the platform end to obtain a follow-up visit result, and the patient obtains and checks the follow-up visit result through the patient end.
6. A method of follow-up after diagnosis as claimed in claim 1, wherein: the doctor end comprises a doctor seeing-in end, a doctor butting end and a doctor on duty, the platform end connects the patient end to the corresponding doctor end according to the doctor seeing-in information, and the patient uses the patient end to inquire the condition of an illness, wherein the doctor seeing-in end comprises the following steps:
the platform end comprises a consultation question-answer library and is used for judging whether the patient condition inquiry of the patient is contained in the consultation question-answer library;
if yes, the docking physician end obtains a reply right, and obtains a reply dialect matched with the disease inquiry through consulting a question-answering library to reply;
if the answer is not contained, the answer content and the answer authority are transferred to the doctor seeing-in department for authority examination and approval after the answer is sent to the doctor seeing-in end, if the doctor seeing-in end passes the authority examination and approval, the answer content is sent to the patient end, if the doctor seeing-in end does not pass the authority examination and approval, the answer content is cleared, and the answer authority is moved to the doctor seeing-in end;
if the reply time to the doctor end exceeds the preset time, the reply authority is moved to the on-duty doctor end, and the on-duty doctor end judges whether the disease inquiry is contained in the consultation question-answer library for reply.
7. The method of claim 3, wherein the platform end pushes announcements into the patient account according to the disease label corresponding to the patient account, and the method specifically comprises the following steps:
if the patient account only contains a first illness state label, pushing corresponding first cis-position propaganda and education content according to the first illness state label;
if the patient account number comprises a first illness state label and a second illness state label, pushing corresponding first order propaganda and education contents according to the first illness state label and pushing corresponding second order propaganda and education contents according to the second illness state label, wherein the pushing priority of the first order propaganda and education contents is higher than that of the second order propaganda and education contents.
8. A method of follow-up after diagnosis according to claim 6 or 7, wherein: the method also comprises a scoring method, and comprises the following steps:
after the doctor end carries out interactive updating actions based on the operation of the patient end, the platform end carries out intelligent scoring on the doctor end based on a preset first scoring rule to obtain a first score, the patient end carries out manual scoring on the doctor end based on a preset second scoring rule to obtain a second score, and the platform end receives the first score and the second score, calculates a final score according to the preset scoring rule and associates the final score with an account number of the doctor end for displaying.
9. A post-visit system comprising a patient side, a platform side, and a physician side, wherein:
the patient side is used for registering the patient at the patient side according to the visit information to obtain a corresponding patient account, and the patient uses the patient side to check the follow-up result;
the platform end comprises a storage module, a follow-up module and a label module, the platform end acquires a patient account and connects the patient end to a corresponding doctor end according to the visit information, the storage module stores the patient account, the label module is used for adding an illness state label to the patient account according to the visit information corresponding to the patient account, and the follow-up module is used for generating a corresponding follow-up task according to a preset follow-up template;
and the doctor end is used for the doctor to follow up the patient of the patient end according to the follow-up task so as to obtain a follow-up result.
10. A computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the post-visit method of any of claims 1 to 8.
CN202210503319.0A 2022-05-10 2022-05-10 Post-diagnosis follow-up method, system and storage medium Pending CN114974530A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210503319.0A CN114974530A (en) 2022-05-10 2022-05-10 Post-diagnosis follow-up method, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210503319.0A CN114974530A (en) 2022-05-10 2022-05-10 Post-diagnosis follow-up method, system and storage medium

Publications (1)

Publication Number Publication Date
CN114974530A true CN114974530A (en) 2022-08-30

Family

ID=82981001

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210503319.0A Pending CN114974530A (en) 2022-05-10 2022-05-10 Post-diagnosis follow-up method, system and storage medium

Country Status (1)

Country Link
CN (1) CN114974530A (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116364233A (en) * 2023-03-06 2023-06-30 广东名阳信息科技有限公司 Prompting method and device after diagnosis
CN116779190A (en) * 2023-06-25 2023-09-19 急尼优医药科技(上海)有限公司 Medical platform user follow-up management system and method based on Internet of things

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116364233A (en) * 2023-03-06 2023-06-30 广东名阳信息科技有限公司 Prompting method and device after diagnosis
CN116779190A (en) * 2023-06-25 2023-09-19 急尼优医药科技(上海)有限公司 Medical platform user follow-up management system and method based on Internet of things
CN116779190B (en) * 2023-06-25 2024-02-13 急尼优医药科技(上海)有限公司 Medical platform user follow-up management system and method based on Internet of things

Similar Documents

Publication Publication Date Title
Damarell et al. General practitioner strategies for managing patients with multimorbidity: a systematic review and thematic synthesis of qualitative research
US20220383998A1 (en) Artificial-intelligence-based facilitation of healthcare delivery
US20190131004A1 (en) System and method of applying state of being to health care delivery
US20200221990A1 (en) Systems and methods for assessing and evaluating renal health diagnosis, staging, and therapy recommendation
US20180137247A1 (en) Preventive and predictive health platform
US7056289B2 (en) Method and system for outpatient monitoring
TWI557679B (en) System and method for generating real-time health care alerts
Samal et al. Health information technology to improve care for people with multiple chronic conditions
US20150213194A1 (en) Methods, Devices, And Systems For Multi-Format Data Aggregation
CN105792731A (en) Patient care surveillance system and method
CN111128333A (en) One-stop intelligent diagnosis and intelligent medical management system
CN114974530A (en) Post-diagnosis follow-up method, system and storage medium
US20190333614A1 (en) Individualized health platforms
US11393589B2 (en) Methods and systems for an artificial intelligence support network for vibrant constitutional guidance
CN112639988A (en) Perioperative education and appointment for surgical patients
CN112735610A (en) Post-hospital follow-up system and follow-up method
US20210334462A1 (en) System and Method for Processing Negation Expressions in Natural Language Processing
CN111627516A (en) Drug treatment management system and method for patients with chronic obstructive pulmonary disease
CN112102956A (en) Method and system for improving compliance of diabetic patient
CN114067940A (en) Health management method and storage medium
Mesbahi et al. The effect of teach-back training on self-care and readmission of patients with heart failure
US10674910B1 (en) ICU telemedicine system for varied EMR systems
US20210375429A1 (en) Automation of medical nutrition therapy
CN112466423A (en) Intelligent chronic disease health management method and system
Lacey et al. A problem-based nutrition care model that is diagnostic driven and allows for monitoring and managing outcomes

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