Report query method, apparatus and device, and storage medium

Abstract

The embodiment of the invention provides a report query method and device, equipment and a storage medium. The method comprises the following steps: determining a corresponding key query parameter according to query input content oriented to any patient and a report contrast relationship defined for the patient; according to the key query parameters, a target report query result of the patient is determined from an electronic medical record library, and medical record report data of each patient is synchronously stored in the electronic medical record library. According to the embodiment of the invention, any patient item report can be timely and effectively queried, and the problem of hysteresis of query of the patient item report is avoided. Moreover, in combination with a report contrast relationship defined for any patient, key query parameters involved in the query can be determined more comprehensively and accurately, so that the high efficiency and accuracy of patient project report query are ensured, a more efficient, convenient and reliable diagnosis and treatment decision reference is provided for doctors, and the scientization and standardization of the diagnosis and treatment process of the patient are promoted.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing technology, and specifically to a report query method, device, equipment and storage medium. Background Art

[0002] With the rapid development of medical technology and the improvement of patients' health awareness, clinical examinations and tests have become an indispensable part of disease diagnosis, treatment monitoring and prognosis evaluation. After completing various examinations and tests, patients usually need to log in to the hospital system or use the hospital's dedicated self-service machine to query the various examination and test reports.

[0003] However, since there are many patients in the hospital and almost every patient will undergo at least one examination and test, there are too many historical examination and test reports in the hospital system, which makes it difficult to effectively manage the historical examination and test reports. Therefore, when querying the examination and test reports of any patient, it is impossible to guarantee the timely and effective query of the examination and test reports, and there may be a certain query lag problem, which affects the diagnosis and treatment efficiency of patients. Summary of the invention

[0004] The embodiments of the present application provide a report query method, apparatus, device and storage medium to realize timely and effective query of any patient project report, ensure the high efficiency and accuracy of patient project report query, and improve the patient's diagnosis and treatment efficiency.

[0005] In a first aspect, an embodiment of the present application provides a report query method, the method comprising:

[0006] Determine corresponding key query parameters according to query input content for any patient and report comparison relationship defined for the patient;

[0007] According to the key query parameters, the target report query result of the patient is determined from the electronic medical record library, and the electronic medical record library synchronously stores the medical report data of each patient.

[0008] In a second aspect, an embodiment of the present application provides a report query device, the device comprising:

[0009] A query parameter determination module, used to determine corresponding key query parameters according to query input content for any patient and a report comparison relationship defined for the patient;

[0010] The report query module is used to determine the target report query result of the patient from the electronic medical record library according to the key query parameters, and the electronic medical record library synchronously stores the medical report data of each patient.

[0011] In a third aspect, an embodiment of the present application provides an electronic device, the electronic device comprising:

[0012] A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the report query method provided in the first aspect of the present application.

[0013] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium for storing a computer program, wherein the computer program enables a computer to execute the report query method provided in the first aspect of the present application.

[0014] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the report query method provided in the first aspect of the present application.

[0015] The embodiments of the present application provide a report query method, device, equipment and storage medium, which can support the attending physician to input personalized query content for any patient to describe the specific query requirements for the diagnosis and treatment of the patient's condition. Then, based on the query input content for any patient, combined with the report control relationship defined for the patient, the corresponding key query parameters can be determined, so as to determine the target report query results of the patient from the electronic medical record library, thereby realizing timely and effective query of any patient project report and avoiding the problem of lag in patient project report query. Moreover, combined with the report control relationship defined for any patient, the key query parameters involved in this query can be determined more comprehensively and accurately to ensure the efficiency and accuracy of the patient project report query, provide doctors with more efficient, convenient and reliable diagnosis and treatment decision references, improve the diagnosis and treatment efficiency of patients, and promote the scientific and standardized diagnosis and treatment process of patients. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0017] Figure 1 A flowchart of a report query method shown in an embodiment of the present application;

[0018] Figure 2 A flowchart of another report query method shown in an embodiment of the present application;

[0019] Figure 3 A functional block diagram of a report query device shown in an embodiment of the present application;

[0020] Figure 4 A schematic block diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0021] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0022] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or server that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0023] In order to solve the problem of certain query lag when querying any patient project report, the embodiment of the present application designs a new report query solution. This solution can be based on the query input content for any patient, combined with the report comparison relationship defined for the patient, to more comprehensively and accurately determine the key query parameters involved in this query, so as to determine the target report query result of the patient from the electronic medical record library, thereby realizing timely and effective query of any patient project report and avoiding the problem of lag in patient project report query.

[0024] Figure 1 This is a flow chart of a report query method shown in an embodiment of the present application. Figure 1 , the method may include the following steps:

[0025] S110, determining corresponding key query parameters according to the query input content for any patient and the report comparison relationship defined for the patient.

[0026] In the medical field, any patient usually needs to undergo various medical examinations and diagnosis and treatment with the assistance of a doctor during the entire medical consultation process, so as to generate the patient's complete medical record data. It is understandable that any patient can choose a doctor in a suitable department to see a doctor, and undergo various examinations and tests under the doctor's advice, and the doctor will diagnose and analyze the various medical examination results recorded in the patient's various examination and test reports to preliminarily diagnose the patient's specific condition.

[0027] It can be seen that for any patient, each inspection and test report obtained after completing various inspections and tests will be handed over to the patient's attending physician to assist in diagnosing the patient's specific condition. Then, in order to ensure that the attending physician can quickly and conveniently view the inspection and test report of any patient, this application can develop an intelligent query assistant for the doctor (referred to as Copilot) to support any attending physician to accurately describe the specific query needs of the patient's condition diagnosis and treatment through personalized input of relevant query content for a certain patient, thereby timely and effectively querying the relevant inspection and test reports of the patient.

[0028] Specifically, the intelligent query assistant Copilot can provide doctors with a corresponding query interaction interface to support doctors to input personalized query content for any patient, and display the target report query results after querying the patient.

[0029] In this application, the query interaction interface provided by the intelligent query assistant Copilot can adopt a simple and clear interface layout, placing key functions in a prominent position on the interface to ensure that the doctor can quickly and conveniently perform key function operations. Moreover, by processing the query interaction interface with details such as color matching, icon design, and font selection, the intuitiveness, usability, and readability of the query interaction interface can be improved, thereby reducing the visual fatigue of the doctor.

[0030] Moreover, the query interaction interface can provide customizable interface options, allowing different doctors to set the view mode, data display method, etc. according to their personal preferences to meet the working habits and needs of different doctors. In addition, clear interactive guidance can be set in the key function operation links in the query interaction interface, such as floating prompts, step instructions, etc., to help doctors quickly perform key function operations and reduce misoperation.

[0031] In some possible implementations, a corresponding query input box can be set in the above-mentioned query interaction interface to support the attending doctor to input relevant query content for a patient according to the specific query requirements of the patient's condition and treatment, so as to trigger the query of the patient's corresponding condition and treatment information.

[0032] Alternatively, a patient-centered comprehensive dialogue interaction box can be set up in the above query interaction interface, and a smooth dialogue between the doctor and the intelligent query assistant Copilot can be achieved through natural language processing and speech synthesis technology. That is, the doctor can initiate a dialogue by inputting simple voice instructions or query text for a certain patient in the comprehensive dialogue interaction box, and process the above input information through natural language processing or speech synthesis technology to obtain the query input content for the patient, so as to feed back the specific query results of the patient to the doctor as a dialogue reply, thereby achieving a smooth dialogue between the doctor and the intelligent query assistant Copilot.

[0033] This application does not limit the specific form in which the attending physician inputs the corresponding query content for any patient in the query interaction interface provided by the intelligent query assistant Copilot.

[0034] Therefore, when any attending doctor has a corresponding query demand for the diagnosis and treatment of a patient's relevant condition, the attending doctor can log in to the above-mentioned intelligent query assistant Copilot to display the corresponding query interaction interface to the attending doctor. Then, by real-time detection of the query input operation performed by the attending doctor on any patient in the query interaction interface, the personalized query content input by the attending doctor for the patient is obtained as the query input content in this application to describe the specific query demand of the attending doctor on the diagnosis and treatment of the patient's condition.

[0035] It can be understood that the query input content for any patient in the present application can be a single query question input by the attending physician, or it can be multiple rounds of conversations and contextual content between the attending physician and the intelligent query assistant Copilot regarding the patient's condition and treatment.

[0036] On the other hand, in order to achieve accurate query of patient project reports, the present application can support the intelligent query assistant Copilot to communicate with various data storage systems in the medical institution system for storing relevant disease diagnosis and treatment data of each patient during the medical treatment process. Data storage systems may include but are not limited to laboratory information systems (Laboratory Information System, referred to as LIS), picture archiving and communication systems (Picture Archiving and Communication Systems, referred to as PACS), etc. Among them, the LIS system can be responsible for the management and storage of laboratory test data, such as blood tests, urine analysis and other results. The PACS system can be responsible for the storage, retrieval, transmission and processing of medical images, including X-rays, computed tomography (Computed Tomography, referred to as CT), magnetic resonance imaging (Magnetic Resonance Imaging, referred to as MRI) and other image data.

[0037] In order to achieve timely and effective query of any patient project report, this application can establish a stable data synchronization mechanism between the intelligent query assistant Copilot and each of the above data storage systems through database triggers or timed tasks. Therefore, every time a new copy of relevant patient diagnosis and treatment data is generated on any data storage system, such newly generated data can be automatically or on demand synchronized to the above intelligent query assistant Copilot.

[0038] Considering that the relevant patient diagnosis and treatment data synchronized from various data storage systems usually have information in their own data formats, different patient diagnosis and treatment data may contain redundant, erroneous or inconsistent information. Then, in order to ensure the query accuracy of the patient project report, this application can perform corresponding data cleaning on the patient diagnosis and treatment data synchronized each time.

[0039] Specifically, the data cleaning operations for patient diagnosis and treatment data may include but are not limited to the following operations:

[0040] 1) Data deduplication: Compare and check the synchronized patient diagnosis and treatment data with the existing patient diagnosis and treatment data, and delete duplicate data, such as redundant master tables such as redun_lab_record, to ensure the uniqueness of patient diagnosis and treatment data.

[0041] 2) Unified format: In order to ensure the convenience of data processing from different sources, this application can unify the data format of patient diagnosis and treatment data from different sources, such as date and time format, unit conversion, etc.

[0042] 3) Error correction: Determine whether there are obvious data errors in the patient diagnosis and treatment data synchronized each time, such as logical errors or parameter range errors, and correct them to ensure the accuracy of the patient diagnosis and treatment data.

[0043] 4) Missing value processing: Determine whether there is missing key information in the patient diagnosis and treatment data synchronized each time, so that it can be automatically filled or marked as missing according to business rules.

[0044] For the cleaned patient diagnosis and treatment data, this application can set up an electronic medical record (EMR) library in the intelligent query assistant Copilot to store the cleaned patient diagnosis and treatment data from different sources to ensure timely and effective query of patient project reports.

[0045] Specifically, the electronic medical record database, as the core system used by medical institutions to store patient diagnosis and treatment data, can store all diagnosis and treatment records of each patient, which may include but is not limited to the result data of the patient after completing any examination and testing items, so as to realize accurate query of any patient project report.

[0046] Moreover, the present application can divide the patient diagnosis and treatment data from different sources into unstructured data and structured data, and store them in partitions in the electronic medical record library. Among them, unstructured data may include but are not limited to examination reports, test reports or examination pictures, etc., which are usually stored in the form of files, and corresponding indexes or links are established for them in the electronic medical record library for rapid retrieval and display. Structured data may include but are not limited to various test indicators in the redundant main table of test data, etc., which can be directly stored in the database table and funny query and analysis can be performed through query languages ​​such as Structured Query Language (SQL).

[0047] In some achievable methods, since the electronic medical record library stores a large number of relevant diagnosis and treatment data of patients, it may include different result data after a patient completes the same inspection and testing item at different times, and may also include various result data after a patient completes multiple inspection and testing items in the same period of time, etc. Then, in order to ensure efficient query of any patient project report, the intelligent query assistant Copilot developed in this application can analyze all the inspection and testing items done by each patient during the entire medical treatment process, as well as the completion time point of each inspection and testing item, and mark and arrange the various inspection and testing items completed by the patient with corresponding multiple timestamps. Among them, the multiple timestamps marked by each inspection and testing item can identify the multiple time points when the patient completes the inspection and testing item. Thus, with the patient identification of each patient as the key field, a report control relationship can be pre-defined for the patient according to the multiple timestamps corresponding to the various inspection and testing items completed by each patient during the entire medical treatment process and the results of the sequential arrangement, and the report control relationship can represent the execution order association relationship between the various inspection and testing items completed by the patient during the entire medical treatment process and the time association relationship when the same inspection and testing item is executed.

[0048] That is, the report comparison relationship defined for each patient may include the longitudinal comparison relationship between the report data of the same item completed by the patient at different time points and the transverse comparison relationship between the report data of different items completed by the patient in the same period of time.

[0049] Thus, through the defined report comparison relationship for each patient, an index can be established for each patient ID in the electronic medical record library to ensure rapid query of the patient's diagnosis and treatment data based on the patient ID in the electronic medical record library. Moreover, through the defined report comparison relationship for each patient, SQL query statements or database views can be used to associate the patient ID with the relevant patient diagnosis and treatment data in the electronic medical record library to form a complete inspection and testing record chain for the patient. According to the above two methods, the complete diagnosis and treatment data of each patient in the electronic medical record library during the entire medical treatment process can be deeply mined to accurately analyze the patient's potential health problems, disease trends or treatment effects, etc., thereby realizing timely and effective query of any patient project report.

[0050] In this application, when any attending physician has a corresponding query demand for the diagnosis and treatment of a patient's relevant condition, the query input content of the attending physician for the patient can be obtained by real-time detection of the query input operation performed by the attending physician for any patient in the query interaction interface. The patient identifier of the patient can also be used to determine the report control relationship defined for the patient.

[0051] Then, for any patient, the specific query requirements of the doctor for the patient are determined by performing corresponding semantic analysis on the query input content for the patient. Then, by analyzing the time and sequence of the various examination and test items completed by the patient during the entire consultation process represented by the report control relationship defined for the patient, it is determined whether each examination and test item meets the specific query requirements of the doctor for the patient, thereby determining the corresponding key query parameters.

[0052] Among them, the key query parameters can be the name, specific indicators, parameter range, etc. of a certain inspection and testing item specified for this query.

[0053] In some implementable methods, in order to ensure accurate query of any patient project report, the present application can determine the corresponding key query parameters in the following manner: determine the corresponding query segmentation based on the query input content for any patient; based on the query segmentation, determine the corresponding key query parameters from the report comparison relationship defined for the patient.

[0054] Specifically, after obtaining the query input content for any patient, the application will first perform corresponding word segmentation processing on the query input content to obtain the corresponding query word segmentation. At this time, each query word segmentation can comprehensively describe the specific query needs of the attending doctor for the diagnosis and treatment of the patient's condition.

[0055] Then, by analyzing the correlation between the time and sequence of various examination and test items completed by the patient during the entire medical treatment process, as represented by the report control relationship defined for the patient, and comparing them with the specific query requirements comprehensively described by each query segmentation, multiple key query parameters related to the query segmentation set in the report object relationship can be determined more comprehensively and accurately, so as to further improve the comprehensiveness and accuracy of any patient project report query.

[0056] S120, determining the target report query result of the patient from the electronic medical record library according to the key query parameters, and the electronic medical record library synchronously stores the medical report data of each patient.

[0057] From the above content, it can be seen that the electronic medical record library in this application can synchronously store the relevant diagnosis and treatment data of each patient, which serves as the medical record report data of the patient in this application.

[0058] In order to accurately obtain the patient diagnosis and treatment data corresponding to each key query parameter, this application can construct a corresponding data interface in the electronic medical record library, and by calling the constructed data interface, the relevant patient diagnosis and treatment data represented by each key query parameter can be quickly obtained from the medical record report data of all patients stored in the electronic medical record library. Furthermore, by comprehensively processing the acquired relevant patient diagnosis and treatment data, the target report query result of the patient can be generated, and the target report query result can be displayed to the attending physician, so as to provide the attending physician with a more efficient, convenient and reliable diagnosis and treatment decision reference, improve the diagnosis and treatment efficiency of the patient, and promote the scientific and standardized diagnosis and treatment process of the patient.

[0059] It can be understood that the target report query result of any patient in the present application can be the examination and test results obtained by the patient after completing any examination and test items, or it can be the data change trend of the patient's relevant disease diagnosis and treatment indicators over a period of time, so as to analyze the patient's specific condition.

[0060] The technical solution provided by the embodiment of the present application can support the attending physician to input personalized relevant query content for any patient to describe the specific query requirements for the diagnosis and treatment of the patient's condition. Then, based on the query input content for any patient, combined with the report comparison relationship defined for the patient, the corresponding key query parameters can be determined, so as to determine the target report query results of the patient from the electronic medical record library, thereby realizing timely and effective query of any patient project report and avoiding the problem of lag in patient project report query. Moreover, combined with the report comparison relationship defined for any patient, the key query parameters involved in this query can be determined more comprehensively and accurately to ensure the efficiency and accuracy of the patient project report query, provide doctors with more efficient, convenient and reliable diagnosis and treatment decision references, improve the diagnosis and treatment efficiency of patients, and promote the scientific and standardized diagnosis and treatment process of patients.

[0061] As an optional implementation scheme in the present application, in order to ensure timely and effective query of any patient's project report, the present application can also set corresponding interactive operations between any patient's examination and test data and the attending physician, so as to provide doctors with more efficient, convenient and reliable diagnosis and treatment decision-making references, and improve the patient's diagnosis and treatment efficiency.

[0062] Figure 2 FIG. 1 is a flow chart of another report query method shown in an embodiment of the present application. Figure 2 As shown, the method may include the following steps:

[0063] S210: Determine corresponding query segmentation words according to the query input content for any patient.

[0064] S220, according to the query segmentation, determine the corresponding key query parameters from the report comparison relationship defined for the patient.

[0065] S230: Determine a corresponding query category according to the query segmentation.

[0066] Considering that the examination and test items completed by the patient can be divided into two categories: examination category and test category. Then, the relevant diagnosis and treatment data of the patient in the entire medical treatment process can be divided into two categories: patient diagnosis and treatment data under the examination category and patient diagnosis and treatment data under the test category.

[0067] In order to ensure efficient storage of patient medical data in the electronic medical record library, the present application can partition and store the patient's related medical data under different categories in the electronic medical record library to facilitate subsequent convenient and efficient queries.

[0068] To this end, after determining the corresponding query segmentation based on the query input content for any patient, the present application can also perform semantic segmentation on each query segmentation to determine whether each query segmentation represents information about examination or test items to determine the corresponding query classification.

[0069] In some implementations, the present application can use a large number of relevant historical diagnosis and treatment data of patients in different categories to train a classification model. Then, after determining the query segmentation corresponding to the query input content for any patient, the present application can input each query segmentation into the trained classification model, and the classification model performs corresponding data analysis on each query segmentation to determine the corresponding query classification.

[0070] S240, according to the key query parameters, determine the target report query result of the patient from the medical record sub-library corresponding to the query category in the electronic medical record library.

[0071] In order to accurately obtain the patient diagnosis and treatment data corresponding to each key query parameter, the present application can construct a data interface that matches the query classification in the electronic medical record library according to the above query classification, such as an inspection interface or a test interface. Then, by calling the constructed data interface, it is possible to directly locate the medical record sub-library corresponding to the query classification in the electronic medical record library. Then, from the medical record report data of all patients stored in the medical record sub-library, the relevant patient diagnosis and treatment data represented by each key query parameter can be quickly obtained. Furthermore, by comprehensively processing the acquired relevant patient diagnosis and treatment data, the target report query result of the patient can be generated, and the target report query result can be displayed to the attending physician to provide the attending physician with a more efficient, convenient and reliable reference for diagnosis and treatment decisions.

[0072] S250, determining a corresponding query presentation style according to the report type of the target report query result to present the target report query result.

[0073] Taking into account that different target report query results may contain data in different forms, the most suitable styles for different target report query results are also different. Therefore, after determining the target report query result of any patient, this application can also perform corresponding visual analysis on the various diagnosis and treatment data in the target report query result to determine the report type of the target report query result. Then, based on the report type of the target report query result, the data display format that best matches the various diagnosis and treatment data in the target report query result is determined to determine the query presentation style of the target report query result.

[0074] Exemplarily, if the target report query result includes relevant diagnosis and treatment data in the form of charts, then it can be determined that the query presentation style of the target report query result can include charts.

[0075] Then, according to the query presentation style of the target report query results, the target report query results are presented in the query interaction interface of the intelligent query assistant Copilot to ensure an intuitive display of the target report query results, so that the attending physician can easily view the long-term change trends of various report indicators of the patient through the intelligent query assistant Copilot, such as comparison of normal ranges, annotation of abnormal values, etc., so as to more accurately judge the development stage of the patient's disease and the treatment effect.

[0076] S260, determining the diagnosis and treatment recommendations associated with the patient based on the data tags of the target report query results.

[0077] After determining the target report query results of any patient, in order to further understand the patient's medical condition and treatment, the present application can also analyze the relevant patient diagnosis and treatment data in the target report query results to determine the data labels involved in the target report query results. The data labels can indicate from which aspects the target report query results describe the patient's medical condition and treatment.

[0078] Then, by deeply mining the relevant patient diagnosis and treatment data in the target report query results, the associated data labels and potential associated indicators of the data label can be further determined. Among them, the associated data labels and potential associated indicators can cover common disease diagnosis clues, and can also include other key factors that may affect the patient's condition (such as living habits, genetic background, etc.). Furthermore, by analyzing the relevant patient diagnosis and treatment data represented by such associated data labels and potential associated indicators, the diagnosis and treatment recommendation content associated with the patient can be further determined. The diagnosis and treatment recommendation content can be multiple similar contents of the query input content for this query input for the patient.

[0079] While presenting the target report query results to the attending physician, the present application can also present multiple diagnosis and treatment recommendation contents associated with the patient to the attending physician, so that the attending physician can quickly interact with any of the presented diagnosis and treatment recommendation contents through the intelligent query assistant Copilot, and further quickly and deeply understand the patient's overall diagnosis and treatment situation, providing the attending physician with a more comprehensive diagnosis and treatment basis for the patient's diagnosis and treatment decision.

[0080] S270, according to the new medical record report data synchronized in the electronic medical record library, push the corresponding report generation message to the target user.

[0081] Since the electronic medical record library will receive relevant patient diagnosis and treatment data synchronized from various data storage systems in medical institutions from time to time, and store it in the electronic medical record library as the patient's medical report data, then, in order to ensure that the attending doctor can obtain the latest examination and test results of a specific patient in real time, this application can set a report push function for the electronic medical record library through the intelligent query assistant Copilot.

[0082] In this application, by real-time detection of whether a new medical record report data is synchronized to the electronic medical record library, it can be determined whether the examination and inspection items completed by a patient generate corresponding examination and inspection results. When a new medical record report data is synchronized to the electronic medical record library, this application can determine the patient represented by the new medical record report data and use the patient's attending physician as the target user in this application.

[0083] Then, for the new medical record report data synchronized in the electronic medical record library, the present application can generate a corresponding report generation message for the new medical record report data, and the report generation message can carry the patient identification, inspection and test item identification, generation time, etc. corresponding to the new medical record report data. Thus, the report generation message corresponding to the new medical record report data can be notified to the target user through SMS or message push, so that the target user can view the new medical record report data in time.

[0084] In some implementable methods, for new medical record report data synchronized in the electronic medical record library, it can support instant notification of the report generation message corresponding to the new medical record report data to the target user, or it can simultaneously notify the target user of the report generation messages corresponding to multiple new medical record report data within the interval period at regular intervals. This application does not limit the specific notification method of the report generation message corresponding to the new medical record report data in the electronic medical record library.

[0085] It should be noted that there is no corresponding execution sequence between S270 and S210-S260 in the present application. During the execution of S210-S260, if the execution condition of S270 is met, S270 can be triggered to execute, so that S210-S260 and S270 may be executed simultaneously or in steps.

[0086] The technical solution provided by the embodiment of the present application can support the attending physician to input personalized relevant query content for any patient to describe the specific query requirements for the diagnosis and treatment of the patient's condition. Then, based on the query input content for any patient, combined with the report comparison relationship defined for the patient, the corresponding key query parameters can be determined, so as to determine the target report query results of the patient from the electronic medical record library, thereby realizing timely and effective query of any patient project report and avoiding the problem of lag in patient project report query. Moreover, combined with the report comparison relationship defined for any patient, the key query parameters involved in this query can be determined more comprehensively and accurately to ensure the efficiency and accuracy of the patient project report query, provide doctors with more efficient, convenient and reliable diagnosis and treatment decision references, improve the diagnosis and treatment efficiency of patients, and promote the scientific and standardized diagnosis and treatment process of patients.

[0087] Figure 3 This is a functional block diagram of a report query device shown in an embodiment of the present application. Figure 3 As shown, the device 300 may include:

[0088] A query parameter determination module 310, for determining corresponding key query parameters according to query input content for any patient and a report comparison relationship defined for the patient;

[0089] The report query module 320 is used to determine the target report query result of the patient from the electronic medical record library according to the key query parameters, and the electronic medical record library synchronously stores the medical report data of each patient.

[0090] In some implementations, the query parameter determination module 310 may be specifically configured to:

[0091] Determine corresponding query segmentation words according to query input content for any patient;

[0092] According to the query segmentation, corresponding key query parameters are determined from the report comparison relationships defined for the patient.

[0093] In some implementations, the report query device 300 may further include a query classification module. The query classification module may be used to:

[0094] According to the query segmentation, a corresponding query category is determined.

[0095] Accordingly, the report query module 320 can be specifically used for:

[0096] According to the key query parameters, the target report query result of the patient is determined from the medical record sub-library corresponding to the query classification in the electronic medical record library.

[0097] In some implementations, the report comparison relationship includes a longitudinal comparison relationship between report data of the same item completed by the patient at different time points and a transverse comparison relationship between report data of different items completed by the patient within the same period of time.

[0098] In some implementations, the report query device 300 may further include a query result presentation module. The query result presentation module may be used to:

[0099] According to the report type of the target report query result, a corresponding query presentation style is determined to present the target report query result.

[0100] In some implementations, the report query device 300 may further include a related content recommendation module. The related content recommendation module may be used to:

[0101] According to the data tags of the target report query results, the diagnosis and treatment recommendation content associated with the patient is determined.

[0102] In some implementations, the report query device 300 may further include a message push module. The message push module may be used to:

[0103] According to the new medical record report data synchronized in the electronic medical record library, a corresponding report generation message is pushed to the target user.

[0104] In an embodiment of the present application, it is possible to support the attending physician to input personalized relevant query content for any patient to describe the specific query requirements for the diagnosis and treatment of the patient's condition. Then, based on the query input content for any patient, combined with the report control relationship defined for the patient, the corresponding key query parameters can be determined, so as to determine the target report query results of the patient from the electronic medical record library, thereby realizing timely and effective query of any patient project report and avoiding the problem of lag in patient project report query. Moreover, combined with the report control relationship defined for any patient, the key query parameters involved in this query can be determined more comprehensively and accurately to ensure the efficiency and accuracy of the patient project report query, provide doctors with more efficient, convenient and reliable diagnosis and treatment decision references, improve the diagnosis and treatment efficiency of patients, and promote the scientific and standardized diagnosis and treatment process of patients.

[0105] It should be understood that the device embodiment and the method embodiment may correspond to each other, and similar descriptions may refer to the method embodiment. To avoid repetition, they will not be described here. Specifically, Figure 3 The device 300 shown can execute any method embodiment in the present application, and the aforementioned and other operations and / or functions of each module in the device 300 are respectively for implementing the corresponding processes in each method in the embodiment of the present application. For the sake of brevity, they will not be repeated here.

[0106] The above describes the device 300 of the embodiment of the present application from the perspective of the functional module in conjunction with the accompanying drawings. It should be understood that the functional module can be implemented in hardware form, can be implemented by instructions in software form, and can also be implemented by a combination of hardware and software modules. Specifically, the steps of the method embodiment in the embodiment of the present application can be completed by the hardware integrated logic circuit and / or software form instructions in the processor, and the steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware decoding processor to perform, or a combination of hardware and software modules in the decoding processor to perform. Optionally, the software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory, and completes the steps in the above method embodiment in conjunction with its hardware.

[0107] Figure 4 A schematic block diagram of an electronic device according to an embodiment of the present application.

[0108] like Figure 4 As shown, the electronic device 400 may include:

[0109] The memory 410 and the processor 420, the memory 410 is used to store the computer program and transmit the program code to the processor 420. In other words, the processor 420 can call and run the computer program from the memory 410 to implement the method in the embodiment of the present application.

[0110] For example, the processor 420 may be configured to execute the above method embodiments according to instructions in the computer program.

[0111] In some embodiments of the present application, the processor 420 may include but is not limited to:

[0112] General-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, etc.

[0113] In some embodiments of the present application, the memory 410 includes but is not limited to:

[0114] Volatile memory and / or non-volatile memory. Among them, the non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM) or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link DRAM (SLDRAM), and direct RAM bus random access memory (DR RAM).

[0115] In some embodiments of the present application, the computer program may be divided into one or more modules, which are stored in the memory 410 and executed by the processor 420 to complete the method provided by the present application. The one or more modules may be a series of computer program instruction segments capable of completing specific functions, and the instruction segments are used to describe the execution process of the computer program in the electronic device.

[0116] like Figure 4 As shown, the electronic device may also include:

[0117] The transceiver 430 may be connected to the processor 420 or the memory 410 .

[0118] The processor 420 may control the transceiver 430 to communicate with other devices, specifically, to send information or data to other devices, or to receive information or data sent by other devices. The transceiver 430 may include a transmitter and a receiver. The transceiver 430 may further include an antenna, and the number of antennas may be one or more.

[0119] It should be understood that the various components in the electronic device are connected via a bus system, wherein the bus system includes not only a data bus but also a power bus, a control bus and a status signal bus.

[0120] The present application also provides a computer storage medium on which a computer program is stored, and when the computer program is executed by a computer, the computer can perform the method of the above method embodiment. In other words, the present application embodiment also provides a computer program product containing instructions, and when the instructions are executed by a computer, the computer can perform the method of the above method embodiment.

[0121] When software is used for implementation, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function according to the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a solid state drive (solid state disk, SSD)), etc.

[0122] Those of ordinary skill in the art will appreciate that the modules and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

[0123] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the module is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.

[0124] The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. For example, each functional module in each embodiment of the present application may be integrated into a processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0125] The above are only specific implementations of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A report query method, characterized in that: include: Determine corresponding key query parameters according to query input content for any patient and report comparison relationship defined for the patient; According to the key query parameters, the target report query result of the patient is determined from the electronic medical record library, and the electronic medical record library synchronously stores the medical report data of each patient.

2. The method according to claim 1, characterized in that Determining corresponding key query parameters according to the query input content for any patient and the report comparison relationship defined for the patient includes: Determine corresponding query segmentation words according to query input content for any patient; According to the query segmentation, corresponding key query parameters are determined from the report comparison relationships defined for the patient.

3. The method according to claim 2, characterized in that The method further comprises: Determine a corresponding query classification according to the query segmentation; Accordingly, determining the target report query result of the patient from the electronic medical record library according to the key query parameter includes: According to the key query parameters, the target report query result of the patient is determined from the medical record sub-library corresponding to the query classification in the electronic medical record library.

4. The method according to claim 1, characterized in that: The report comparison relationship includes the longitudinal comparison relationship between the report data of the same item completed by the patient at different time points and the transverse comparison relationship between the report data of different items completed by the patient in the same period of time.

5. The method according to claim 1, characterized in that After determining the target report query result of the patient from the electronic medical record library according to the key query parameter, the method further includes: According to the report type of the target report query result, a corresponding query presentation style is determined to present the target report query result.

6. The method according to claim 1, characterized in that The method further comprises: According to the data tags of the target report query results, the diagnosis and treatment recommendation content associated with the patient is determined.

7. The method according to claim 1, characterized in that The method further comprises: According to the new medical record report data synchronized in the electronic medical record library, a corresponding report generation message is pushed to the target user.

8. A report query device, characterized in that: include: A query parameter determination module, used to determine corresponding key query parameters according to query input content for any patient and a report comparison relationship defined for the patient; The report query module is used to determine the target report query result of the patient from the electronic medical record library according to the key query parameters, and the electronic medical record library synchronously stores the medical report data of each patient.

9. An electronic device, characterized in that: include: A processor and a memory, wherein the memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to execute the report query method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Used to store a computer program, wherein the computer program enables a computer to execute the report query method according to any one of claims 1 to 7.

Images