Influenza medical service data reporting method and device, server and medium

The integration of a task scheduling and conversion execution engine automates influenza medical service data reporting, enhancing efficiency and reducing labor costs by automating data extraction and reporting processes.

CN119069064APending Publication Date: 2024-12-03WINNING HEALTH TECHNOLOGY GROUP CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411079653.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-07
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Current influenza medical service data reporting methods are labor-intensive and lack automation, requiring manual execution of data extraction scripts and file placement, which is inefficient and costly.

Method used

Integrate a task scheduling engine and conversion execution engine to automate the extraction, conversion, and reporting of influenza medical service data by determining target tasks based on scheduling configuration information, executing data extraction from medical databases, and uploading files to a monitoring system when updates are detected.

Benefits of technology

Improves automation and conversion efficiency while reducing labor costs by enabling automatic extraction, conversion, and reporting of influenza medical service data, ensuring timely and efficient data reporting to national monitoring systems.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119069064A_ABST
    Figure CN119069064A_ABST
Patent Text Reader

Abstract

The invention provides an influenza medical service data reporting method and device, a server and a medium, and relates to the technical field of big data. The method comprises the following steps: determining a target conversion task to be executed from a plurality of conversion tasks by adopting a task scheduling engine according to a plurality of pieces of pre-arranged conversion task scheduling configuration information; executing the target conversion task by adopting a conversion execution engine so as to extract target data from a medical business database corresponding to the target conversion task and generate a target medical service table file corresponding to the target conversion task, and storing the target medical service table file into a preset file directory; monitoring the preset file directory by adopting a front program of the influenza medical service monitoring system; and if the preposed program monitors that file updating exists in the preset file directory, the preposed program uploads the updated file to a second server of the influenza medical service monitoring system. Therefore, the labor cost is saved, and the conversion efficiency is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of big data technology, and in particular to a method, device, server and medium for reporting influenza medical service data. Background Art

[0002] With the deepening of globalization and the increase in population mobility, the spread of influenza viruses is getting faster and faster, and new strains are constantly emerging, making influenza medical service monitoring more complex and urgent. In the current monitoring of influenza medical services, for influenza patients visiting medical institutions, the data that needs to be reported include outpatient (emergency) influenza cases, in-hospital (hospitalized but not discharged) influenza cases, and discharged influenza cases. The uploaded content needs to obtain data from three systems: HIS, doctor station, and medical technology, and the reporting frequency is daily.

[0003] The reporting method is to deploy the front-end program specified by the influenza medical service monitoring system, monitor the update date of the csv file in a specific directory, and automatically push any changes to the influenza medical service monitoring system server. The file can also be uploaded directly through the influenza medical service monitoring system webpage.

[0004] In the existing technology, the HIS, doctor station, and medical technology systems provide data extraction scripts, and then write programs to export data as csv files, and then manually place the csv files in a specific directory, and the front-end completes the data reporting. The disadvantages of the existing technology are: the degree of automation is low, and the export script needs to be manually executed every day and then placed in a specific directory. Summary of the invention

[0005] The purpose of the present invention is to provide a method, device, server and medium for reporting influenza medical service data in view of the deficiencies in the above-mentioned prior art, so as to improve the automation of influenza medical service data reporting, save labor costs and improve conversion efficiency.

[0006] To achieve the above purpose, the technical solution adopted in the embodiment of the present application is as follows:

[0007] In a first aspect, an embodiment of the present application provides a method for reporting influenza medical service data, which is applied to a first server of an integrated task scheduling management platform and an influenza medical service monitoring system, wherein the task scheduling management platform integrates a task scheduling engine and a conversion execution engine, and the method includes: using the task scheduling engine to determine a target conversion task to be executed from the multiple conversion tasks according to a plurality of pre-arranged conversion task scheduling configuration information; using the conversion execution engine to execute the target conversion task to extract target data from a medical business database corresponding to the target conversion task and generate a target medical service table file corresponding to the target conversion task, and store the target medical service table file in a preset file directory; different conversion tasks are used to generate medical service table files of different reporting types; using the front-end program of the influenza medical service monitoring system to monitor the preset file directory; if the front-end program detects that there is a file update in the preset file directory, the front-end program uploads the updated file to the second server of the influenza medical service monitoring system.

[0008] In one embodiment, the task scheduling engine is used to determine the target conversion task to be executed from the multiple conversion tasks according to the pre-arranged multiple conversion task scheduling configuration information, including: using the task scheduling engine to obtain the scheduling configuration information of the multiple conversion tasks from the task information table of the multiple conversion tasks, the scheduling configuration information of each conversion task including: task name, scheduling expression and execution time information; using the task scheduling engine to determine whether the multiple conversion tasks meet the preset execution trigger conditions according to the scheduling expressions and execution time information of the multiple conversion tasks; if the target conversion task meets the preset execution trigger conditions, using the task scheduling engine to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task, wherein the target conversion information includes: the reporting type of the target medical service form file and the storage path of the preset file directory.

[0009] In one embodiment, the use of the conversion execution engine to execute the target conversion task includes: using the conversion execution engine to call the execution file of the target conversion task among the execution files of the multiple conversion tasks according to the target conversion information to execute the target conversion task.

[0010] In one embodiment, before the conversion execution engine is used to call the execution file of the target conversion task among the execution files of the multiple conversion tasks according to the target conversion information to execute the target conversion task, the method further includes: encapsulating the conversion description information, conversion execution logic, connection configuration information of the medical business database to be extracted, and output file configuration information of each conversion task into the execution file of each conversion task.

[0011] In one embodiment, the task scheduling engine is used to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task, including: using the task scheduling engine to query the conversion information table bound to the target conversion task from a preset database according to the task name of the target conversion task; using the task scheduling engine to determine the target conversion information from the conversion information table.

[0012] In one embodiment, the method further includes: using the task scheduling engine to obtain the data upload log returned by the second server from the front-end; and using the task scheduling engine to write the data upload log into a preset database.

[0013] In one embodiment, the method further includes: if the data upload log indicates that the file upload failed, using the task scheduling engine to obtain information of the monitoring personnel corresponding to the target conversion task; and issuing an upload failure notification message of the target conversion task to the monitoring personnel.

[0014] In the second aspect, an embodiment of the present application also provides an influenza medical service data reporting device, the device comprising: a determination module, configured to use the task scheduling engine, and determine a target conversion task to be executed from the multiple conversion tasks according to a plurality of pre-arranged conversion task scheduling configuration information; an execution module, configured to use the conversion execution engine to execute the target conversion task, so as to extract target data from the medical business database corresponding to the target conversion task and generate a target medical service table file corresponding to the target conversion task, and store the target medical service table file in a preset file directory; different conversion tasks are used to generate medical service table files of different reporting types; a monitoring module, configured to use the front-end program of the influenza medical service monitoring system to monitor the preset file directory; a reporting module, configured to upload the updated file to the second server of the influenza medical service monitoring system by the front-end program if the front-end program detects that there is a file update in the preset file directory.

[0015] In one embodiment, the determination module is configured to: use the task scheduling engine to obtain the scheduling configuration information of the multiple conversion tasks from the task information table of the multiple conversion tasks, the scheduling configuration information of each conversion task including: task name, scheduling expression and execution time information; use the task scheduling engine to determine whether the multiple conversion tasks meet the preset execution trigger conditions based on the scheduling expressions and execution time information of the multiple conversion tasks; if the target conversion task meets the preset execution trigger conditions, use the task scheduling engine to determine the target conversion information bound to the target conversion task based on the task name of the target conversion task, wherein the target conversion information includes: the reporting type of the target medical service form file and the storage path of the preset file directory.

[0016] In one implementation, the execution module is configured to: use the conversion execution engine to call the execution file of the target conversion task among the execution files of the multiple conversion tasks according to the target conversion information, so as to execute the target conversion task.

[0017] In one embodiment, the influenza medical service data reporting device also includes a packaging module, which is configured to: package the conversion description information, conversion execution logic, connection configuration information of the medical business database to be extracted, and output file configuration information of each conversion task into an execution file of each conversion task.

[0018] In one embodiment, the determination module is configured to: use the task scheduling engine to query the conversion information table bound to the target conversion task from a preset database according to the task name of the target conversion task; use the task scheduling engine to determine the target conversion information from the conversion information table.

[0019] In one embodiment, the monitoring module is configured to: use the task scheduling engine to obtain the data upload log returned by the second server from the front-end; and use the task scheduling engine to write the data upload log into a preset database.

[0020] In one embodiment, the monitoring module is configured as follows: if the data upload log indicates that the file upload failed, the task scheduling engine is used to obtain information about the monitoring personnel corresponding to the target conversion task; and an upload failure notification message of the target conversion task is issued to the monitoring personnel.

[0021] In a third aspect, an embodiment of the present application further provides a server, comprising: a processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, and when the computer device is running, the processor communicates with the storage medium through the bus, and the processor executes the program instructions to perform the steps of any one of the above methods.

[0022] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of any one of the above methods are executed.

[0023] The beneficial effects of the present application are: using a task scheduling engine, according to a plurality of pre-arranged conversion task scheduling configuration information, determining the target conversion task to be executed from a plurality of conversion tasks; using a conversion execution engine, executing the target conversion task, extracting the target data from the medical business database corresponding to the target conversion task and generating the target medical service form file corresponding to the target conversion task, and storing the target medical service form file in a preset file directory; using the front-end program of the influenza medical service monitoring system to monitor the preset file directory; if the front-end program detects that there is a file update in the preset file directory, the front-end program uploads the updated file to the second server of the influenza medical service monitoring system. By integrating the integrated task scheduling management platform and the influenza medical service monitoring system in the first server, integrating the task scheduling engine and the conversion execution engine in the task scheduling management platform, the automatic extraction, automatic conversion, monitoring and automatic reporting of influenza medical service data can be realized. In this way, the automation of influenza medical service data reporting is improved, while saving labor costs, the conversion efficiency is improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0025] Figure 1 A flowchart of a method for reporting influenza medical service data provided in an embodiment of the present application;

[0026] Figure 2 A flowchart of a method for reporting influenza medical service data provided in an embodiment of the present application;

[0027] Figure 3 A flowchart of a method for reporting influenza medical service data provided in an embodiment of the present application;

[0028] Figure 4 A flowchart of a method for reporting influenza medical service data provided in an embodiment of the present application;

[0029] Figure 5 A flowchart of a method for reporting influenza medical service data provided in an embodiment of the present application;

[0030] Figure 6 A schematic diagram of the structure of a flu medical service data reporting device provided in an embodiment of the present application;

[0031] Figure 7 A schematic diagram of the structure of a computer device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments.

[0033] Therefore, the following detailed description of the embodiments of the present application provided in the accompanying drawings is not intended to limit the scope of the present application for which protection is sought, but merely represents selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0034] In the description of the present application, it should be noted that if the terms "upper", "lower", etc. appear, the orientation or position relationship indicated is based on the orientation or position relationship shown in the drawings, or is the orientation or position relationship in which the product of the application is usually placed when used. It is only for the convenience of describing the present application and simplifying the description, and does not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present application.

[0035] In addition, the terms "first", "second", etc. in the specification and claims of the present invention 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 interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0036] It should be noted that, in the absence of conflict, the features in the embodiments of the present application may be combined with each other.

[0037] Figure 1 A flowchart of a method for reporting influenza medical service data provided in an embodiment of the present application; Figure 1 As shown, it is applied to the first server of the integrated task scheduling management platform and the influenza medical service monitoring system, wherein the task scheduling management platform integrates the task scheduling engine and the conversion execution engine, and the method includes:

[0038] Step 110: Using a task scheduling engine, according to a plurality of pre-arranged conversion task scheduling configuration information, determine a target conversion task to be executed from a plurality of conversion tasks.

[0039] The task scheduling engine can be a Quartz.Net task scheduling framework integrated on the task scheduling management platform. Quartz.Net allows developers to create, schedule and manage scheduled tasks, and supports multiple triggering strategies, such as simple triggering, Cron triggering, etc., which can meet various complex scheduling requirements. In actual operation, the Quartz.Net task scheduling framework can be encapsulated through C# code.

[0040] Multiple conversion tasks are generally multiple different conversion tasks, such as: data in the HIS database is converted into outpatient and inpatient cases, data in the doctor station database is converted into death records and discharge summaries, and data in the medical technology database is converted into test records and discharged influenza cases. There are three databases and five conversion tasks.

[0041] The scheduling configuration information is used to indicate the scheduling-related information of the conversion task, such as: scheduling expression, execution time information, etc.; wherein, the scheduling expression is used to define the task execution time, and is usually used for the scheduling of scheduled tasks. Here, the scheduling expression can be a Cron standard expression. Specifically, the Cron standard expression consists of 5 fields, representing minutes, hours, date, month, and day of the week. Each field is separated by a space, and the value of each field has its specific meaning and allowed range. The format of the Cron expression is very flexible, and the execution time, execution frequency, and execution interval of the task can be defined by combining numbers, "*", "-", commas, and " / ". Further, the minute field (0-59): This field indicates which minute of each hour the task will be triggered; for example: if it is set to "* / 15", the task will be executed every 15 minutes. The hour field (0-23): This field specifies which hour of the day the task will be executed; for example: "0*" means that the task will be executed at midnight every day. Day field (1-31): This field is used to specify the day of the month when the task will be triggered; for example, "10" means that the task will be executed on the tenth day of each month. Month field (1-12): This field defines the month of the year when the task will be executed; for example, "JAN" or "1" means that the task will be executed in January. Day of the week field (0-7, where 0 and 7 both represent Sunday, or SUN-SAT represents Sunday to Saturday): This field is used to specify the day of the week when the task will be executed; for example, "MON" means that the task will be executed every Monday.

[0042] Quartz.Net can run in a local or remote node, and the node can be an ASP.NET Core application. In actual operation, the task scheduling management platform (for example, also an ASP.NET Core application) can be used to manage the start and stop of the conversion task execution node. Furthermore, it can also be responsible for monitoring the conversion task. Furthermore, the task scheduling management platform can also output the execution log data of the conversion task; further, the execution status of the conversion task can be determined based on the execution log, and in the case of failure of the conversion task execution, the corresponding responsible person can be notified by email, SMS, etc. Here, the responsible person can be an employee of the hospital information department, and there is no limitation here.

[0043] The task scheduling management platform can integrate the task scheduling engine and the conversion execution engine to realize automatic scheduling and automatic conversion of conversion tasks. Furthermore, the task scheduling management platform can also provide functions such as data verification, message push, and subordinate data query, which are not limited here.

[0044] The influenza medical service monitoring system can be understood as a national monitoring system that requires the Medical Administration and Management Bureau of the National Health Commission to report data on influenza patients visiting medical institutions at or above the second level, including outpatient (emergency) influenza cases, inpatient (hospitalized but not discharged) influenza cases, and discharged influenza cases.

[0045] The first server can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), as well as big data and artificial intelligence platforms.

[0046] Step 120: Use the conversion execution engine to execute the target conversion task to extract target data from the medical business database corresponding to the target conversion task and generate a target medical service table file corresponding to the target conversion task, and store the target medical service table file in a preset file directory.

[0047] Among them, different conversion tasks are used to generate medical service form files of different reporting types.

[0048] The transformation execution engine can be a Kettle transformation execution engine integrated on the task scheduling management platform. Kettle (also known as Pentaho Data Integration (PDI for short)) is an open source ETL (Extract-Transform-Load) tool for data integration and data processing. Kettle provides a visual graphical interface that enables users to design and configure ETL processes by dragging and dropping and connecting components. It supports a variety of data sources and targets, including relational databases, files, APIs, Hadoop, etc. Kettle provides rich transformation and cleaning functions, which can perform operations such as format conversion, data filtering, data merging, and data calculation on data. It also supports functions such as data quality checking, error handling, and data verification.

[0049] The medical business database is used to record and save influenza-related case data, including three databases: HIS, doctor station, and medical technology.

[0050] In actual operation, the format of the target medical service form file is generally csv format.

[0051] The preset file directory may be a pre-established designated directory for storing target medical service form files.

[0052] Reporting type refers to the type of medical service form document, which generally includes five types, namely, outpatient and emergency influenza cases, inpatient influenza cases, discharge summaries, death records, laboratory records, and discharged influenza cases.

[0053] Step 130: Use the pre-program of the influenza medical service monitoring system to monitor the preset file directory.

[0054] The pre-program of the influenza medical service monitoring system in this step is consistent with the pre-program of the influenza medical service monitoring system in the related art, and is used to monitor the target medical service form file under the above-mentioned preset file directory.

[0055] Step 140: If the front-end program detects that there is a file update in the preset file directory, the front-end program uploads the updated file to the second server of the influenza medical service monitoring system.

[0056] The file update may be an update of the file content or an update of the file date, which is not limited here.

[0057] The second server is used to store the updated target medical service table file in the preset file directory. The second server can be the same as the first server or different from the first server, which is not limited here.

[0058] The influenza medical service data reporting method provided by the embodiment of the present application adopts a task scheduling engine, and according to a plurality of pre-arranged conversion task scheduling configuration information, determines the target conversion task to be executed from a plurality of conversion tasks; adopts a conversion execution engine, executes the target conversion task, extracts the target data from the medical business database corresponding to the target conversion task and generates a target medical service form file corresponding to the target conversion task, and stores the target medical service form file in a preset file directory; adopts the front-end program of the influenza medical service monitoring system to monitor the preset file directory; if the front-end program detects that there is a file update in the preset file directory, the front-end program uploads the updated file to the second server of the influenza medical service monitoring system. By integrating the integrated task scheduling management platform and the influenza medical service monitoring system in the first server, integrating the task scheduling engine and the conversion execution engine in the task scheduling management platform, the automatic extraction, automatic conversion, monitoring and automatic reporting of influenza medical service data can be realized. In this way, the automation of influenza medical service data reporting is improved, while saving labor costs, the conversion efficiency is improved.

[0059] The following is a further explanation of the process of determining a target conversion task to be executed from a plurality of conversion tasks in the above embodiment with reference to examples. Figure 2 This is a flow chart of the method for reporting influenza medical service data provided in the embodiment of the present application. Figure 2As shown, the above step 110 may further include the following steps 210 to 230:

[0060] Step 210: Using a task scheduling engine, obtain scheduling configuration information of multiple conversion tasks from a task information table of multiple conversion tasks.

[0061] The scheduling configuration information of each conversion task includes: task name, scheduling expression and execution time information.

[0062] The task information table is used to record information related to the conversion task, such as: as shown in Table 1, code, task code, task name, whether to run in a loop, Cron expression, task status, task start time, task end time, task last execution time, task next start time, etc.; if whether to run in a loop is set to no, the task will only be executed once after it is started; if whether to run in a loop is set to yes, the task will execute the call expression after it is started until the task end time arrives. The code can be used to identify the task information table, and the task code can be used to identify the task.

[0063] Field Name Field meaning Field Type ID coding uniqueidentifier TRANS_ID Task ID uniqueidentifier NAME Task Name Varchar(64) ISRUNLOOP Whether to run in a loop bit CRON_EXPRESSION Cron Expressions Varchar(32) STATUS Task Status Varchar(64) START_DATE Task start time datetime END_DATE Task end time datetime LAST_RUNTIME The last time the task was executed datetime NEXT_RUNTIME Next task start time datetime

[0064] Table 1

[0065] The scheduling configuration information is part of the information in the task information table, which is used to indicate the scheduling-related information of the conversion task, including the task name, the scheduling expression and the execution time information; wherein the execution time information may include the task start time and / or the task end time; for example: the task name is: connecting to the HIS database to generate the conversion of outpatient and emergency and in-hospital influenza cases; the task name is: connecting to the doctor station database to generate the conversion of death records and discharge summaries; the task name is: connecting to the medical technology database to generate the conversion of test records and discharged influenza cases; the scheduling expression is [0017**?], then the task start time is 17:00, the task end time can be determined according to the setting, or the task end time may not be set. In the case of setting the task end time, the task end time can be determined according to the execution time of the conversion task. Generally, the task end time is later than the sum of the task start time and the maximum task execution time; for example: the task start time is 17:00, the maximum task execution time is 20 minutes, and the task end time is later than 17:20.

[0066] Step 220: Using a task scheduling engine, determine whether the multiple conversion tasks meet preset execution trigger conditions according to the scheduling expressions and execution time information of the multiple conversion tasks.

[0067] Among them, the scheduling expressions, execution time information and current actual time of multiple conversion tasks can be combined to determine whether the multiple conversion tasks meet the preset execution trigger conditions; generally, when the execution time information of multiple conversion tasks is determined to be consistent with the current actual time through the scheduling expression and execution time information, the preset execution trigger conditions are met, otherwise, the preset execution trigger conditions are not met. Among them, the execution time of multiple conversion tasks can be determined by the scheduling expression, the execution time of multiple conversion tasks can be determined by the execution time information, and the execution time of multiple conversion tasks can be determined by the scheduling expression and the execution time information, which is not limited here.

[0068] Step 230: If the target conversion task meets the preset execution triggering condition, the task scheduling engine is used to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task.

[0069] The target conversion information includes: the reporting type of the target medical service form file and the storage path of the preset file directory.

[0070] The conversion information may be stored in a table format. In addition to including the reporting type of the medical service form file and the storage path of the preset file directory, the conversion information may also include information such as the code, the task name, and whether it is disabled.

[0071] The target conversion information is conversion information of a target conversion task to be executed among the multiple conversion tasks.

[0072] The influenza medical service data reporting method provided in the embodiment of the present application adopts a task scheduling engine to obtain the scheduling configuration information of multiple conversion tasks from the task information table of multiple conversion tasks; adopts the task scheduling engine to determine whether the multiple conversion tasks meet the preset execution trigger conditions according to the scheduling expressions and execution time information of the multiple conversion tasks; if the target conversion task meets the preset execution trigger conditions, adopts the task scheduling engine to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task. Determine the scheduling configuration information through the task information table, determine whether to trigger the target conversion task according to the scheduling configuration information, and determine the target conversion information according to the task name in the scheduling configuration information when the target conversion task is triggered. In this way, the target conversion information can be accurately determined so as to accurately execute the target conversion task later.

[0073] The following is an example of the process of the conversion execution engine executing the target conversion task in the above embodiment. The above step 120 may further include the following steps:

[0074] A conversion execution engine is used to call the execution file of the target conversion task among the execution files of multiple conversion tasks according to the target conversion information, so as to execute the target conversion task.

[0075] The format of the execution file is generally ktr format. In actual operation, each conversion task can be encapsulated into a ktr format file, including connecting to the HIS database to generate conversions of outpatient and emergency and in-hospital influenza cases; connecting to the doctor station database to generate conversions of death records and discharge summaries; connecting to the medical technology database to generate conversions of test records and discharged influenza cases; these five ktr format execution files can be used as inputs of the conversion execution engine.

[0076] Specifically, before the above steps, the following steps are also included:

[0077] The conversion description information, conversion execution logic, connection configuration information of the medical business database to be extracted, and output file configuration information of each conversion task are encapsulated into an execution file for each conversion task.

[0078] The conversion description information is used to describe relevant information of information conversion, such as: converting data in a medical business database into a medical service form file.

[0079] The conversion execution logic, that is, how to perform the conversion specifically; for example: converting the data in the HIS database into medical service form files for outpatient and emergency departments and in-hospital influenza cases; converting the data in the doctor's station database into medical service form files for death records and discharge summaries; converting the data in the medical technology database into medical service form files for test records and discharged influenza cases.

[0080] The connection configuration information of the medical business database to be extracted, that is, the connection configuration information of the HIS database, the doctor station database, and the medical technology database. To realize the automatic extraction of data from the database, it is necessary to connect the HIS database, the doctor station database, and the medical technology database to the task scheduling management platform.

[0081] Output file configuration information, that is, setting the format of the output file, the storage path of the output file (that is, the storage path of the preset file directory), etc.

[0082] The influenza medical service data reporting method provided in the embodiment of the present application encapsulates the conversion description information, conversion execution logic, connection configuration information of the medical business database to be extracted, and output file configuration information of each conversion task into an execution file for each conversion task; a conversion execution engine is used to call the execution file of the target conversion task in the execution files of multiple conversion tasks according to the target conversion information to execute the target conversion task. By encapsulating the conversion-related information into an execution file and inputting it into the conversion execution engine, so that the conversion execution engine executes the conversion task according to the execution file, the automation of the conversion task is realized, which saves labor costs and improves conversion efficiency.

[0083] The following is a further explanation of the process of using the task scheduling engine in the above embodiment to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task, with reference to the examples. Figure 3 This is a flow chart of the method for reporting influenza medical service data provided in the embodiment of the present application. Figure 3 As shown, the above step 230 may further include the following steps 310 and 320:

[0084] Step 310: Using the task scheduling engine, according to the task name of the target conversion task, query the conversion information table bound to the target conversion task from the preset database.

[0085] The preset database is a pre-established database used to store conversion information tables of multiple conversion tasks.

[0086] The conversion information table records the conversion information related to the conversion task, as shown in Table 2, including the code, the task name of the conversion task, whether it is disabled, the reporting type of the medical service form file, the storage path of the preset file directory, etc. Generally, the conversion information at least includes the reporting type of the medical service form file and the storage path of the preset file directory.

[0087] Field Name Field meaning Field Type ID coding uniqueidentifier TRANS_NAME Task Name Varchar(64) TYPE Report Type Varchar(64) TRANS_PATH Convert storage path Varchar(64) IS_DEL Disable bit

[0088] Table 2

[0089] Step 320: Using the task scheduling engine, determine the target conversion information from the conversion information table.

[0090] The target conversion information includes: the reporting type of the target medical service form file and the storage path of the preset file directory.

[0091] The target conversion information is conversion information of a target conversion task to be executed among the multiple conversion tasks.

[0092] The influenza medical service data reporting method provided in the embodiment of the present application adopts a task scheduling engine, and queries the conversion information table bound to the target conversion task from the preset database according to the task name of the target conversion task; the task scheduling engine is adopted to determine the target conversion information from the conversion information table. The conversion information table is obtained by querying the task name in the scheduling configuration information, and the conversion information is determined from the conversion information. In this way, unified management of data is achieved, and the query efficiency of data is improved, thereby saving overall time and improving overall efficiency.

[0093] In some embodiments, in order to achieve traceability of influenza medical service data reporting, data upload logs can be stored. Figure 4 This is a flow chart of the method for reporting influenza medical service data provided in the embodiment of the present application. Figure 4 As shown, the influenza medical service data reporting method provided in the embodiment of the present application further includes the following steps 410 and 420:

[0094] Step 410: Use the task scheduling engine to obtain the data upload log returned by the second server from the front-end.

[0095] The front-end processor is consistent with the front-end program or front-end processor of the influenza medical service monitoring system in the related art, and is used to monitor whether the target medical service form file under the above-mentioned preset file directory is updated, and return the data upload log.

[0096] The data upload log, that is, the data upload result log, can be used to know the data upload result; for example, the data upload log can record the data upload status, specifically, it can record the success or failure of the data upload.

[0097] Step 420: Using the task scheduling engine, write the data upload log into a preset database.

[0098] The preset database is a pre-established database used to store data upload logs.

[0099] The influenza medical service data reporting method provided in the embodiment of the present application adopts a task scheduling engine to obtain the data upload log returned by the second server from the front-end; and adopts the task scheduling engine to write the data upload log into a preset database. The data upload log is obtained through the front-end and saved. In this way, it is conducive to the staff to review the reporting of influenza medical service data, so that the reporting of influenza medical service data can be checked and traced.

[0100] In actual operation, the task execution results and data upload logs can be summarized into a table for storage to facilitate query and tracing; for example, as shown in Table 3, it includes code, task code, task scheduling execution node, log content, execution success flag, creation time, etc.

[0101] Field Name Field meaning Field Type ID coding int SCHEDULEID Task Coding uniqueidentifier NODE Task scheduling execution node Varchar(64) MESSAGE Log content Varchar(max) RESULT Successful execution sign int CREATETIME Creation time datetime

[0102] Table 3

[0103] In some embodiments, in order to improve the success rate of influenza medical service data reporting, relevant staff can be notified when data upload fails. Figure 5 This is a flow chart of the method for reporting influenza medical service data provided in the embodiment of the present application. Figure 5 As shown, the influenza medical service data reporting method provided in the embodiment of the present application further includes the following steps 510 and 520:

[0104] Step 510: If the data upload log indicates that the file upload fails, the scheduling execution engine is used to obtain the information of the monitoring personnel corresponding to the target conversion task.

[0105] The monitoring personnel can also be understood as the person responsible for data reporting; specifically, the person responsible may be an employee of the hospital information department, which is not limited here.

[0106] In actual operation, the correspondence table between the target conversion task and the corresponding monitoring personnel can be stored in the above-mentioned preset database. When the data upload log indicates that the target medical service form file upload fails, the corresponding monitoring personnel information can be obtained according to the target conversion task through the correspondence table between the target conversion task and the corresponding monitoring personnel. In actual operation, the correspondence table between the target conversion task and the corresponding monitoring personnel (user) can be stored in the preset database in the form of a table, for example: as shown in Table 4, the task code and the monitoring personnel code are stored in a table to form a correspondence table, which can specifically include the code, task code, user code, whether to disable, etc.

[0107] Field Name Field meaning Field Type ID coding int SCHEDULEID Task Coding uniqueidentifier USERID User Code int IS_DEL Disable bit

[0108] Table 4

[0109] The monitoring personnel's information includes the monitoring personnel's real name, user name, password, email address, phone number, creation time, last login time, whether disabled, etc., so that the monitoring personnel can be contacted through the contact information even if an abnormal situation occurs. In actual operation, the monitoring personnel (user) information can also be stored in a preset database in the form of a table, for example: as shown in Table 5.

[0110] Field Name Field meaning Field Type ID coding int USERNAME username Varchar(64) PASSWORD password Varchar(64) REALNAME Real name Varchar(64) PHONE Telephone Varchar(64) EMAIL Email Address Varchar(64) CREATETIME Creation time datetime LASTLOGINTIME Last login time datetime IS_DEL Disable bit

[0111] Table 5

[0112] Step 520: Sending a notification message of a failure to upload the target conversion task for the monitoring personnel.

[0113] The failure notification message may be an email, text message, etc., which is not limited here.

[0114] When the data upload log indicates that the target medical service form file upload fails, the monitoring personnel is notified through a failure notification message so that the monitoring personnel can handle the situation that the target medical service form file upload fails in a timely manner.

[0115] The influenza medical service data reporting method provided in the embodiment of the present application, if the data upload log indicates that the file upload failed, uses the scheduling execution engine to obtain the information of the monitoring personnel corresponding to the target conversion task; and sends a notification message of the upload failure of the target conversion task to the monitoring personnel. In the case of a file upload failure, a notification message of an upload failure is sent to the monitoring personnel. In this way, the monitoring personnel can be reminded to take corresponding measures in time for the failure of data upload, so that the entire influenza medical service data reporting process forms a closed loop.

[0116] After introducing the influenza medical service data reporting method according to the exemplary embodiment of the present disclosure, next, refer to Figure 6 The influenza medical service data reporting device 600 according to the exemplary embodiment of the present disclosure is described.

[0117] refer to Figure 6 As shown, the influenza medical service data reporting device 600 includes: a determination module 610, which is configured to use a task scheduling engine to determine a target conversion task to be executed from multiple conversion tasks according to a plurality of pre-arranged conversion task scheduling configuration information; an execution module 620, which is configured to use a conversion execution engine to execute the target conversion task to extract target data from a medical business database corresponding to the target conversion task and generate a target medical service table file corresponding to the target conversion task, and store the target medical service table file in a preset file directory; different conversion tasks are used to generate medical service table files of different reporting types; a monitoring module 630, which is configured to use a front-end program of an influenza medical service monitoring system to monitor the preset file directory; and a reporting module 640, which is configured to upload the updated file to a second server of the influenza medical service monitoring system by the front-end program if the front-end program detects that there is a file update in the preset file directory.

[0118] In one embodiment, the determination module 610 is configured to: use a task scheduling engine to obtain scheduling configuration information of multiple conversion tasks from a task information table of multiple conversion tasks, the scheduling configuration information of each conversion task including: task name, scheduling expression and execution time information; use the task scheduling engine to determine whether the multiple conversion tasks meet the preset execution trigger conditions based on the scheduling expressions and execution time information of the multiple conversion tasks; if the target conversion task meets the preset execution trigger conditions, use the task scheduling engine to determine the target conversion information bound to the target conversion task based on the task name of the target conversion task, wherein the target conversion information includes: the reporting type of the target medical service form file and the storage path of the preset file directory.

[0119] In one implementation, the execution module 620 is configured to: use a conversion execution engine to call an execution file of a target conversion task among the execution files of multiple conversion tasks according to the target conversion information, so as to execute the target conversion task.

[0120] In one embodiment, the influenza medical service data reporting device 600 also includes a packaging module, which is configured to: package the conversion description information, conversion execution logic, connection configuration information of the medical service database to be extracted, and output file configuration information of each conversion task into an execution file for each conversion task.

[0121] In one embodiment, the determination module 610 is configured to: use the task scheduling engine to query the conversion information table bound to the target conversion task from the preset database according to the task name of the target conversion task; use the task scheduling engine to determine the target conversion information from the conversion information table.

[0122] In one implementation, the monitoring module 630 is configured to: use a task scheduling engine to obtain the data upload log returned by the second server from the front-end; and use the task scheduling engine to write the data upload log into a preset database.

[0123] In one embodiment, the monitoring module 630 is configured to: if the data upload log indicates that the file upload fails, use the task scheduling engine to obtain the information of the monitoring personnel corresponding to the target conversion task; and issue an upload failure notification message of the target conversion task to the monitoring personnel.

[0124] The above-mentioned device is used to execute the method provided by the aforementioned embodiment, and its implementation principle and technical effect are similar, which will not be repeated here.

[0125] The above modules may be one or more integrated circuits configured to implement the above methods, such as one or more application specific integrated circuits (ASICs), or one or more microprocessors, or one or more field programmable gate arrays (FPGAs). For another example, when a module is implemented in the form of a processing element scheduling program code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processor that can call program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0126] Figure 7 A schematic diagram of a computer device provided in an embodiment of the present application. The device can be integrated into a terminal device or a chip of a terminal device. The terminal can be a computing device with data processing capabilities.

[0127] The device includes: a processor 701 , a storage medium 702 and a bus 703 .

[0128] The storage medium 702 stores program instructions executable by the processor 701. When the computer device 700 is running, the processor 701 communicates with the storage medium 702 via the bus 703, and the processor 701 executes the program instructions to perform the above method embodiment. The specific implementation method and technical effect are similar and will not be repeated here.

[0129] Optionally, the present invention also provides a program product, such as a computer-readable storage medium, comprising a program, which is used to execute the above method embodiment when executed by a processor.

[0130] In the several embodiments provided by the present invention, it should be understood that the disclosed 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 units is only a logical function division. There may be other division methods in actual implementation, such as multiple units 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 units, which can be electrical, mechanical or other forms.

[0131] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0132] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0133] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (English: processor) to perform some steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (English: Read-Only Memory, abbreviated: ROM), random access memory (English: Random Access Memory, abbreviated: RAM), disk or optical disk and other media that can store program codes.

[0134] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for reporting influenza medical service data, characterized in that: The method is applied to a first server of an integrated task scheduling management platform and an influenza medical service monitoring system, wherein the task scheduling management platform integrates a task scheduling engine and a conversion execution engine, and the method comprises: Using the task scheduling engine, according to the pre-arranged multiple conversion task scheduling configuration information, determine the target conversion task to be executed from the multiple conversion tasks; The conversion execution engine is used to execute the target conversion task to extract target data from the medical service database corresponding to the target conversion task and generate a target medical service form file corresponding to the target conversion task, and store the target medical service form file in a preset file directory; different conversion tasks are used to generate medical service form files of different reporting types; The preset file directory is monitored using the front-end program of the influenza medical service monitoring system; If the front-end program detects that there is a file update in the preset file directory, the front-end program uploads the updated file to the second server of the influenza medical service monitoring system.

2. The method according to claim 1, characterized in that The task scheduling engine is used to determine a target conversion task to be executed from the multiple conversion tasks according to the pre-arranged multiple conversion task scheduling configuration information, including: Using the task scheduling engine, obtaining the scheduling configuration information of the multiple conversion tasks from the task information table of the multiple conversion tasks, the scheduling configuration information of each conversion task including: task name, scheduling expression and execution time information; Using the task scheduling engine, determining whether the multiple conversion tasks meet preset execution trigger conditions according to the scheduling expressions and execution time information of the multiple conversion tasks; If the target conversion task meets the preset execution trigger condition, the task scheduling engine is used to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task, wherein the target conversion information includes: the reporting type of the target medical service form file and the storage path of the preset file directory.

3. The method according to claim 2, characterized in that The using the conversion execution engine to execute the target conversion task includes: The conversion execution engine is used to call the execution file of the target conversion task among the execution files of the multiple conversion tasks according to the target conversion information, so as to execute the target conversion task.

4. The method according to claim 3, characterized in that Before using the conversion execution engine to call the execution file of the target conversion task among the execution files of the multiple conversion tasks according to the target conversion information to execute the target conversion task, the method further includes: The conversion description information, conversion execution logic, connection configuration information of the medical service database to be extracted, and output file configuration information of each conversion task are encapsulated into an execution file of each conversion task.

5. The method according to claim 2, characterized in that: The step of using the task scheduling engine to determine the target conversion information bound to the target conversion task according to the task name of the target conversion task includes: Using the task scheduling engine, according to the task name of the target conversion task, querying the conversion information table bound to the target conversion task from a preset database; The task scheduling engine is used to determine the target conversion information from the conversion information table.

6. The method according to claim 1, characterized in that The method further comprises: Using the task scheduling engine to obtain the data upload log returned by the second server from the front-end processor; The task scheduling engine is used to write the data upload log into a preset database.

7. The method according to claim 6, characterized in that The method further comprises: If the data upload log indicates that the file upload fails, the task scheduling engine is used to obtain information about the monitoring personnel corresponding to the target conversion task; A notification message of upload failure of the target conversion task for the monitoring personnel is issued.

8. A device for reporting influenza medical service data, characterized in that: The device is applied to a first server of an integrated task scheduling management platform and an influenza medical service monitoring system, wherein the task scheduling management platform integrates a task scheduling engine and a conversion execution engine, and the device comprises: A determination module is configured to use the task scheduling engine to determine a target conversion task to be executed from the multiple conversion tasks according to the pre-arranged multiple conversion task scheduling configuration information; an execution module, configured to use the conversion execution engine to execute the target conversion task, so as to extract target data from the medical service database corresponding to the target conversion task and generate a target medical service form file corresponding to the target conversion task, and store the target medical service form file in a preset file directory; different conversion tasks are used to generate medical service form files of different reporting types; A monitoring module configured to monitor the preset file directory using a pre-program of the influenza medical service monitoring system; The reporting module is configured to upload the updated file to the second server of the influenza medical service monitoring system by the front-end program if the front-end program detects that there is a file update in the preset file directory.

9. A server, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, and when the computer device is running, the processor and the storage medium communicate through the bus, and the processor executes the program instructions to perform the steps of the influenza medical service data reporting method according to any one of claims 1 to 7.

10. A computer device, characterized in that: include: A processor, a storage medium and a bus, wherein the storage medium stores program instructions executable by the processor, and when the computer device is running, the processor and the storage medium communicate through the bus, and the processor executes the program instructions to perform the steps of the influenza medical service data reporting method according to any one of claims 1 to 7.