Hospital quality control data preprocessing and heterogeneous data integration method and system

Abstract

The invention discloses a hospital quality control data preprocessing and heterogeneous data integration method and system, and relates to the field of data processing, and the method comprises the steps: reading a hospital quality control index set from a database, and displaying the hospital quality control index set in a calculation caliber maintenance interface; receiving a quality control index identifier selected in the hospital quality control index set, displaying an operation component library corresponding to the quality control index identifier on a calculation aperture editing interface, responding to drag-drop operation and connection operation of the component, generating a data processing flow, and storing the data processing flow in the calculation aperture editing interface; the data processing flow comprises configuration information of each component and a data flow relationship between the components; in response to the storage instruction, converting the data processing flow into a script code; executing the script code according to a set time interval; and recording an execution log and a calculation result of the script code, and establishing a corresponding relationship between the execution log, the calculation result and the quality control index identifier for storage. By implementing the method, the processing efficiency of the hospital quality control index data can be improved.

Description

Technical Field

[0001] The present application relates to the field of data processing, and in particular to a method and system for preprocessing hospital quality control data and integrating heterogeneous data. Background Art

[0002] With the rapid development of medical information technology, hospital quality control is receiving increasing attention. As an important basis for measuring medical quality, the calculation and management requirements of hospital quality control indicators are constantly increasing, placing higher demands on the accuracy, timeliness, and standardization of data processing.

[0003] In related technologies, hospital quality control indicators can be calculated through database SQL queries combined with program code or data analysis tools. During this process, technicians first need to obtain raw data through database connection tools, then write SQL statements to extract and perform preliminary statistics. Finally, they use programming languages ​​or professional data analysis software to further calculate and process the data, ultimately obtaining the indicator results.

[0004] However, since the calculation process involves multiple independent tools and platforms, the data processing process is relatively fragmented and there is a lack of effective connection between the various links. This decentralized processing method not only increases the data flow links, but also makes it difficult to uniformly monitor and track the entire calculation process, reducing the efficiency of data processing. Summary of the Invention

[0005] The present application provides a method and system for preprocessing hospital quality control data and integrating heterogeneous data, which are used to improve the processing efficiency of hospital quality control indicator data.

[0006] In the first aspect, the present application provides a hospital quality control data preprocessing and heterogeneous data integration method, which is applied to a hospital quality control data preprocessing and heterogeneous data integration system. The method includes: reading a hospital quality control indicator set from a database, and displaying the hospital quality control indicator set in a calculation caliber maintenance interface; receiving a quality control indicator identifier selected in the hospital quality control indicator set, and displaying an operation component library corresponding to the quality control indicator identifier on a calculation caliber editing interface, wherein the operation component library includes a data source connection component, a data processing component, and a calculation formula component; in response to the drag-and-drop operation and the connection operation of the component, generating a data processing flow, the data processing flow includes the configuration information of each component and the data flow relationship between each component; in response to a save instruction, converting the data processing flow into a script code; executing the script code at a set time interval; recording the execution log and calculation results of the script code, and establishing a corresponding relationship between the execution log, the calculation results and the quality control indicator identifier for storage.

[0007] By adopting the above technical solution, the quality control indicator set is first read from the database and displayed on the calculation caliber maintenance interface. Then, the operation component library is presented according to the selected indicator identifier. The user uses drag-and-drop and connection operations to build the data processing flow, which enables the components to be combined as needed and clarifies the data flow path. The process is then converted into script code and executed at a scheduled time. Relevant information is recorded and a corresponding relationship is established for storage. This realizes the standardization and automation of the data processing flow, improves data processing efficiency, ensures the accuracy and traceability of data processing, and effectively promotes the effective implementation of hospital quality control work.

[0008] In combination with some embodiments of the first aspect, in some embodiments, the data processing flow is generated in response to the drag-and-drop operation and the connection operation of the components. The data processing flow includes the configuration information of each component and the steps of the data flow relationship between each component, specifically including: receiving the user's drag-and-drop operation on the components in the operation component library, and displaying the dragged and dropped components on the calculation caliber editing interface; in response to the user's connection operation, displaying the connection relationship between the components on the calculation caliber editing interface, and recording the data flow direction between adjacent components; detecting whether the configuration parameters of each component are complete, and the configuration parameters include the input parameters, processing parameters and output parameters of the component; if the configuration parameters are complete, generating a data processing flow including the business processing flow according to the connection relationship between the components and the configuration parameters of each component.

[0009] By adopting this technical solution, the rationality and reliability of data processing workflow construction are ensured. After the user drags and drops components, the system responds to the connection operation, determines the component connection relationship and data flow, and checks the component configuration parameters. When the configuration parameters are complete, a data processing flow containing the business process flow is generated based on the connection relationship and parameters. This effectively prevents data processing issues caused by missing or incorrect configurations and improves the success rate of process construction.

[0010] In combination with some embodiments of the first aspect, in some embodiments, the step of converting the data processing flow into script code in response to a save instruction specifically includes: in response to a save instruction, converting the data processing flow information into a calculation caliber file in a dynamic script language format, which contains script codes for data processing timing, processing duration, processing logic, query detail data, and calculation index data; and compiling the calculation caliber file through a parser to generate script code.

[0011] By employing this technical solution, we achieve precise conversion of data processing flows into script code. Upon responding to a save command, the process information is first converted into a computational caliber file in a dynamic scripting language format, including key script code such as processing timing. This is then compiled into script code using a parser. This conversion method accurately transforms the graphically designed flow into executable code, ensuring the precise implementation of the processing logic.

[0012] In combination with some embodiments of the first aspect, in some embodiments, after the step of detecting whether the configuration parameters of each component are complete, the configuration parameters include the input parameters, processing parameters and output parameters of the component, the method also includes: if the configuration parameters are incomplete, sending parameter supplement prompt information to the target client.

[0013] By adopting this technical solution, the accuracy of data processing flow configuration is improved. When detecting component configuration parameters, if any incompleteness is found, a prompt message will be sent, helping users quickly identify the problem and supplement the parameters in a timely manner, avoiding data processing errors caused by configuration errors and ensuring that each component can operate with the correct configuration.

[0014] In combination with some embodiments of the first aspect, in some embodiments, after the step of compiling the calculation caliber file through the parser to generate script code, the method also includes: if the compilation is successful, storing the generated script code in the database; if the compilation fails, returning an error message to the target client.

[0015] By adopting the above technical solution, after compilation, if successful, the code is stored to provide a unified management space. If it fails, an error message is returned, and comprehensive error details are collected, formatted, and sent to the client, which is converted into an intuitive prompt to help users quickly locate and solve the problem.

[0016] In combination with some embodiments of the first aspect, in some embodiments, after the step of recording the execution log and calculation results of the script code, and establishing a corresponding relationship and storing the execution log, calculation results and the quality control indicator identifier, the method also includes: extracting a calculation rule template from the data processing flow, the calculation rule template including the combination method of the components, the connection relationship between the components and the configuration parameters; in response to a request for a new quality control indicator, obtaining the calculation elements of the new quality control indicator, and performing a matching calculation on the calculation elements and the elements in the calculation rule template; when the matching degree exceeds a preset matching degree threshold, applying the calculation rule template to the new quality control indicator, and generating a corresponding data processing flow to be displayed in the calculation caliber editing interface.

[0017] By adopting the above technical solution, after recording the execution related information, the system extracts the calculation rule template, which covers key elements such as component combination. When there is a new quality control indicator request, its calculation elements are obtained and matched with the template. If the match is high enough, the template is applied to generate a new process display, avoiding repeated process construction, ensuring the logical standardization of new indicator processing, and improving processing efficiency.

[0018] In combination with some embodiments of the first aspect, in some embodiments, after the step of recording the execution log and calculation results of the script code, and establishing a corresponding relationship and storing the execution log, calculation results and the quality control indicator identifier, the method also includes: running the script code according to a preset fixed execution cycle, and turning on the incremental update mode, the incremental update mode is to calculate the new data later than the last execution timestamp in each incremental update cycle; performing data sampling and analysis on the calculation results generated in each incremental update cycle to obtain the change range of the statistical indicator; when the change range of a key statistical indicator exceeds a preset change threshold, tracing the position of the key statistical indicator to obtain an abnormal data item; marking the abnormal data item in the calculation caliber maintenance interface.

[0019] By employing this technical solution, the script code runs according to a preset cycle and enables incremental updates. New data is filtered and calculated based on timestamps, ensuring timely and targeted data processing. Incremental results are sampled and analyzed, and different strategies are used to obtain samples and calculate the magnitude of change, effectively monitoring data fluctuations. When key indicators exceed thresholds, a multi-step tracing process is used to identify the source of the abnormal data, store it in a table, and annotate it within the interface. This allows for the timely detection and resolution of abnormal data, preventing it from impacting results and improving data processing accuracy.

[0020] In the second aspect, an embodiment of the present application provides a hospital quality control data preprocessing and heterogeneous data integration system, which includes: one or more processors and a memory; the memory is coupled to the one or more processors, and the memory is used to store computer program code, and the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the hospital quality control data preprocessing and heterogeneous data integration system to execute the method described in the first aspect and any possible implementation method of the first aspect.

[0021] In a third aspect, an embodiment of the present application provides a computer program product comprising instructions. When the above-mentioned computer program product runs on a hospital quality control data preprocessing and heterogeneous data integration system, the above-mentioned hospital quality control data preprocessing and heterogeneous data integration system executes the method described in the first aspect and any possible implementation method of the first aspect.

[0022] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium comprising instructions. When the instructions are run on a hospital quality control data preprocessing and heterogeneous data integration system, the hospital quality control data preprocessing and heterogeneous data integration system executes the method described in the first aspect and any possible implementation method of the first aspect.

[0023] It is understandable that the hospital quality control data preprocessing and heterogeneous data integration system provided in the second aspect, the computer program product provided in the third aspect, and the computer storage medium provided in the fourth aspect are all used to execute the methods provided in the embodiments of this application. Therefore, the beneficial effects that can be achieved can be referenced to the beneficial effects of the corresponding methods and will not be repeated here.

[0024] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages: 1. This application first reads the quality control indicator set from the database and displays it in the calculation caliber maintenance interface, then presents the operation component library according to the selected indicator identifier, and the user uses drag and drop and connection operations to build the data processing process, which enables the components to be combined as needed and clarifies the data flow path. The process is then converted into script code and executed at a scheduled time, relevant information is recorded and a corresponding relationship is established for storage, thereby achieving standardization and automation of the data processing process, improving data processing efficiency, ensuring the accuracy and traceability of data processing, and effectively promoting the effective implementation of hospital quality control work.

[0025] 2. This application ensures the rationality and reliability of data processing flow construction. After the user drags and drops components, the system responds to the connection operation to determine the component connection relationship and data flow, and detects the component configuration parameters. When the configuration parameters are complete, a data processing flow containing the business processing flow is generated based on the connection relationship and parameters, effectively preventing data processing problems caused by missing or incorrect configuration, and improving the success rate of process construction.

[0026] 3. After recording the execution-related information, the system extracts the calculation rule template, which covers key elements such as component combination. When there is a request for a new quality control indicator, its calculation elements are matched with the template. If the match is high enough, the template is applied to generate a new process display, avoiding repeated process construction, ensuring the logical standardization of new indicator processing, and improving processing efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 This is a flow chart of the method for preprocessing hospital quality control data and integrating heterogeneous data in an embodiment of the present application; Figure 2 This is another flow chart of the method for preprocessing hospital quality control data and integrating heterogeneous data in an embodiment of the present application; Figure 3 This is another flow chart of the method for preprocessing hospital quality control data and integrating heterogeneous data in an embodiment of the present application; Figure 4 This is a schematic diagram of the physical device structure of the hospital quality control data preprocessing and heterogeneous data integration system in the embodiment of the present application. DETAILED DESCRIPTION

[0028] The terms used in the following examples of the present application are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification of the present application, the singular expressions "a", "an", "above", "the", and "this" are intended to include plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used in the present application refers to any or all possible combinations of one or more of the listed items.

[0029] In the following, the terms "first" and "second" are used for descriptive purposes only and should not be understood to imply or suggest relative importance or implicitly indicate the number of the technical features indicated. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of this application, unless otherwise specified, "plurality" means two or more.

[0030] For ease of understanding, the following describes the process of the method provided by this implementation. Figure 1 , which is a flow chart of the hospital quality control data preprocessing and heterogeneous data integration method in the embodiment of this application.

[0031] S101. Read the hospital quality control indicator set from the database and display the hospital quality control indicator set in the calculation caliber maintenance interface.

[0032] The hospital quality control indicator set represents the set of indicators used by medical institutions to evaluate the quality of medical services, encompassing multiple specific quality control assessment indicators. The calculation caliber maintenance interface is a graphical user interface used to configure and manage quality control indicator calculation rules, displaying and editing indicator definitions. The database represents a structured data storage system for quality control indicator data, including tables such as the indicator definition table and the calculation rule table.

[0033] This step is executed upon system startup or when a user enters the Quality Control Indicator Management module. Specifically, the system first connects to the designated database instance and retrieves all valid quality control indicator records from the quality control indicator definition table using SQL queries. The query results are then converted into the data structure required for interface display, including information such as indicator ID, indicator name, indicator category, and calculation period. Finally, an indicator display area is constructed within the calculation scope maintenance interface, presenting indicator data to the user in a list or tree format.

[0034] In some embodiments, the reading and display of indicator data can be achieved in a variety of ways: Optionally, the system uses database connection pool technology to establish a long connection with the database, executes parameterized queries to obtain indicator data, converts the result set into a list of Java objects, transmits it to the front end through the Spring MVC framework, and uses the Vue.js component library to build a dynamic table to display indicator information, supporting paging, sorting and search functions; Optionally, the system uses an ORM framework such as MyBatis to map database tables to entity classes, defines query methods through annotations, and after the query results are processed by the data conversion service, they are pushed to the front end using WebSocket technology, and the React component library is used to implement tree display, supporting interactive functions such as expansion / collapse, drag and drop sorting, etc. It is understandable that other database access and interface display technologies can also be used to achieve the reading and display of indicator data, which is not limited here.

[0035] S102. Receive the quality control indicator identifier selected in the hospital quality control indicator set, and display the operation component library corresponding to the quality control indicator identifier on the calculation caliber editing interface. The operation component library includes a data source connection component, a data processing component, and a calculation formula component.

[0036] The "quality control indicator identifier" refers to a code or ID used to uniquely identify a specific quality control indicator. The "operation component library" represents a collection of predefined data processing modules. The "data source connection component" refers to modules used to establish connections to data sources, including database connections and file reading. The "data processing component" represents modules used for operations such as data cleaning, conversion, and filtering. The "calculation formula component" refers to modules used to perform mathematical calculations and statistical analysis. The "calculation caliber editing interface" provides a workspace for designing data processing workflows.

[0037] This step is triggered when a user selects a specific indicator from the quality control indicator list. Specifically, the system receives the user's selection event and obtains the identification information of the selected indicator. Based on the indicator identification, the system queries the available component types for that indicator and selects the relevant processing components from the component library. The selected components are grouped by category and displayed in the component panel of the calculation caliber editing interface. Drag-and-drop support is provided for each component, allowing users to construct data processing workflows through drag-and-drop operations.

[0038] In some embodiments, the display and management of the component library can be achieved in a variety of ways: optionally, the system uses a component registration center to uniformly manage all processing components, defines the properties and behaviors of the components through component description files, uses a factory pattern to create component instances, uses classification tags to manage component categories, implements the drag and drop function of the components through drag event handlers, and uses a connection manager to handle the connection relationship between components; optionally, the system uses a plug-in architecture to design the component library, defines component specifications through plug-in interfaces, uses a reflection mechanism to dynamically load component classes, describes the input, output and configuration items of the components through metadata, uses SVG technology to draw component graphics, and realizes the visual display and interactive operation of the components. It is understandable that other component management and interface interaction technologies can also be used to realize the display and operation functions of the component library, which are not limited here.

[0039] S103 : In response to the drag-and-drop operation and the connection operation of the components, a data processing flow is generated, where the data processing flow includes the configuration information of each component and the data flow relationship between each component.

[0040] Drag-and-drop operations refer to interactions in which users drag components to designated locations using a mouse. Wiring operations involve drawing connections between components. A data processing flow represents a complete processing chain consisting of multiple processing components in a specific order and relationship. Configuration information refers to the parameter settings required for each component to operate, including input parameters, processing rules, and output formats. Data flow relationships represent the data transfer method and path between processing components, defining the data flow and conversion rules.

[0041] This step is performed when users design data processing flows through a graphical interface. Specifically, the system monitors component drag-and-drop events and line drawing events on the interface. When a drag-and-drop operation is detected, a component instance is created at the target location and the component's default configuration is initialized. When a line drawing operation is detected, the validity of the connection is verified, including data type matching and circular dependency checks, establishing the connection relationship between components. The system updates the internal representation model of the flow in real time, recording information such as component location, parameter configuration, and connection relationships, and presents a real-time visualization of the flow on the interface.

[0042] In some embodiments, the construction of the data processing flow can be implemented in a variety of ways: optionally, the system uses an event bus to manage user interaction events, creates component instances through a component factory, uses a state manager to maintain process configuration, uses a graph layout algorithm to optimize component positions, checks data compatibility through a connection validator, and uses a command pattern to implement undo / redo operations; optionally, the system uses a responsive programming model to handle interaction events, manages component definitions through a component registry, uses an observer pattern to implement inter-component communication, uses a constraint solver to ensure the legitimacy of connections, saves process configurations through a serialization service, and uses a snapshot mechanism to support process version management. It is understandable that other event processing and process management technologies can also be used to implement the data processing flow construction function, which is not limited here.

[0043] S104: In response to the save instruction, convert the data processing flow into script code.

[0044] The "save" instruction represents a user-triggered control command for a save operation. Script code refers to program code automatically generated by the system for executing data processing tasks, supporting multiple programming languages ​​such as SQL and Python. Conversion refers to the process of converting a visual process definition into executable code.

[0045] This step is executed when the user completes the process design and triggers the save operation. Specifically, the system first verifies the integrity and validity of the process, checking for unconfigured components or invalid connections. It then topologically sorts the process based on the dependencies between components to determine the order of code generation. The system processes each component one by one, generating corresponding code snippets based on the component type and configuration parameters. This includes data source connection code, data processing logic, calculation expressions, and more. Finally, all code snippets are assembled in the execution order to generate the complete script code, and the necessary error handling and logging code are added.

[0046] In some embodiments, the conversion of process to code can be achieved in a variety of ways: optionally, the system uses a code generation engine to parse the process definition, generates a code framework through a template engine, assembles the code structure using a syntax tree builder, uses a code optimizer to improve code quality, creates test cases through a unit test generator, and uses a code formatting tool to beautify the final code; optionally, the system uses a semantic analyzer to extract process logic, creates transition code through an intermediate code generator, uses a target language converter to generate specific language code, uses dependency injection to handle the relationship between components, ensures code correctness through a code validator, and uses a version control system to manage code history. It is understandable that other code generation and conversion technologies can also be used to achieve the conversion function of process to script code, which is not limited here.

[0047] S105: Execute the script code at a set time interval.

[0048] The set interval represents the periodic execution of the preconfigured script, which can be in units of minutes, hours, days, or other time units. Executing the script code means running the program code converted from the data processing flow to complete the data processing and computation tasks. The interval represents the time difference between two executions and is used to control the frequency and timing of script execution.

[0049] This step continues after the system initializes the scheduled task. Specifically, the system first reads the script's execution configuration and obtains the set execution interval. It then creates the scheduled execution task and sets the task's triggering rules, including the initial execution time, repetition interval, and number of executions. At each interval, the system prepares the execution environment, including initializing runtime parameters, establishing database connections, and loading dependent resources. The system then starts the script executor, runs the script code, and monitors the execution status, including resource usage, execution progress, and error handling.

[0050] In some embodiments, the scheduled execution of scripts can be achieved in a variety of ways: optionally, the system uses a task scheduling framework such as Quartz to create scheduled tasks, ensures that tasks are not lost after system restart through task persistence, uses a thread pool to manage execution threads, uses a monitoring module to track task status, handles execution exceptions through a failure retry mechanism, and uses a resource limiter to control task resource usage; optionally, the system uses a distributed scheduling platform such as XXL-Job to manage task execution, implements task distribution through a master-slave architecture, uses distributed locks to ensure unique task execution, uses a task queue to schedule execution order, monitors execution nodes through a heartbeat mechanism, and uses an alarm service to handle abnormal situations. It is understandable that other task scheduling and execution management technologies can also be used to achieve the scheduled execution function of scripts, which are not limited here.

[0051] S106: Record the execution log and calculation result of the script code, and establish a corresponding relationship between the execution log, calculation result and the quality control indicator identifier for storage.

[0052] The execution log is a text record of status information, error messages, and key events during the script execution process. The calculation result is the data processing output generated after the script is executed. The correspondence relationship represents the mapping between the execution log and calculation results and specific quality control indicators. Storage refers to the process of persisting data to a storage system. The quality control indicator identifier is the unique identifier for a specific quality control indicator.

[0053] This step is performed immediately after the script completes. Specifically, the system collects all log information generated during script execution, including execution time, execution status, error messages, and performance metrics. It also obtains the script's calculation output, including calculated values, statistical data, and analysis reports. The system generates unique identifiers for logs and results, establishing relationships with quality control indicators. The data is then written to persistent storage, including log tables, result tables, and relationship tables, and necessary indexes are established to support fast queries.

[0054] In some embodiments, the storage management of execution records can be implemented in a variety of ways: optionally, the system uses a relational database to store structured data, aggregates execution logs through a log collector, uses a data access layer to handle data persistence, uses an index optimizer to improve query performance, reduces storage space through data compression, and uses a data cleanup strategy to manage historical data; optionally, the system uses a distributed storage architecture to manage data, processes log data through a log aggregation service, uses a time series database to store calculation results, uses a graph database to manage associations, improves access performance through a cache service, and uses data backup to ensure data security. It is understandable that other data storage and management technologies can also be used to implement the storage function of execution records, which are not limited here.

[0055] The following is a more detailed description of the process of the method provided by this implementation. Figure 2 , is another flow chart of the hospital quality control data preprocessing and heterogeneous data integration method in the embodiment of this application.

[0056] S201. Read the hospital quality control indicator set from the database and display the hospital quality control indicator set in the calculation caliber maintenance interface.

[0057] The hospital quality control indicator set is a collection of standardized metrics used by medical institutions to evaluate and monitor medical quality. These metrics include specific indicators such as surgical complication rates, inpatient mortality rates, and average length of stay. In this context, the term "database" specifically refers to the relational database that stores these quality control indicator data, such as MySQL or Oracle. The calculation caliber maintenance interface is a graphical user interface used to display and manage the calculation rules and methods for quality control indicators.

[0058] During implementation, the system first retrieves complete indicator data from the database's quality control indicator table using SQL queries, including fields such as indicator code, indicator name, indicator category, and calculation frequency. After acquiring the data, the system renders it into the calculation caliber maintenance interface in a predefined display format (such as a tree structure or list). For example, indicators can be displayed by department or grouped by indicator type, allowing users to clearly view and select the quality control indicators they need to operate on.

[0059] S202. Receive the quality control indicator identifier selected in the hospital quality control indicator set, and display the operation component library corresponding to the quality control indicator identifier on the calculation caliber editing interface. The operation component library includes a data source connection component, a data processing component, and a calculation formula component.

[0060] The quality control indicator identifier is a unique identifier for each quality control indicator, typically consisting of a combination of letters and numbers. The operation component library is a collection of components that contain various data manipulation tools. The data source connection component is used to configure data sources and connection parameters; the data processing component includes functions such as data cleaning, conversion, and filtering; and the calculation formula component provides various mathematical calculations and statistical analysis functions.

[0061] When a user selects a specific quality control indicator in the calculation caliber maintenance interface, the system reads the corresponding operation component configuration information based on the indicator's identifier and displays the available operation components in the toolbar area of ​​the calculation caliber editing interface. These components are displayed as icons or text and are grouped by categories such as data source connection, data processing, and calculation formula, making it easy for users to quickly find the required functional components.

[0062] S203: Receive a user's drag-and-drop operation on a component in the operation component library, and display the dragged-and-dropped component on the calculation caliber editing interface.

[0063] Drag-and-drop operation is a commonly used human-computer interaction method in graphical interfaces. Users select and move interface elements through input devices such as the mouse.

[0064] In practice, users can select the target component in the component library by clicking it, hold down the left mouse button, drag it to the designated location in the calculation caliber editing interface, and release it. The system will create a graphical instance of the component at the release location, including visual elements such as the component icon, name, input and output ports, etc. These component instances will maintain their relative position on the interface and support subsequent parameter configuration and wiring operations. Each dragged and dropped component has a unique instance identifier, which can be distinguished and referenced in subsequent data flow configuration.

[0065] S204. In response to the user's connection operation, the connection relationship between the components is displayed on the calculation caliber editing interface, and the data flow direction between adjacent components is recorded.

[0066] A connection operation is the act of drawing a line between two components' ports on a graphical interface using a device such as a mouse. Connections represent the coordination and order between components during data processing, typically represented by directed lines. The data flow direction defines the path along which data flows between adjacent components, including information about the source component (data provider) and the target component (data receiver).

[0067] During implementation, when a user connects a line in the calculation caliber editing interface, the system first captures the mouse click event on the output port of the starting component, then tracks the mouse movement and draws a preview of the connection line in real time. When the user releases the mouse on the input port of the target component, the system creates a permanent connection line object, which contains the connection line's style attributes (such as color, thickness, type, etc.) as well as the source and target port information of the connection. At the same time, the system records this connection relationship in an internal data structure, recording information such as the source component ID, target component ID, and connection line ID for subsequent data flow generation and execution.

[0068] S205: Check whether the configuration parameters of each component are complete, where the configuration parameters include the input parameters, processing parameters, and output parameters of the component.

[0069] Configuration parameters are the various settings required for a component to function properly. Input parameters define the format and requirements for data received by the component, such as data types and field names. Processing parameters are the configuration items required for a component to perform specific functions, such as filtering conditions and calculation formulas. Output parameters specify the format and structure of the data output by the component after processing.

[0070] The configuration parameter integrity check process includes the following steps: First, the system obtains the type information for each component instance and loads its parameter template definition based on the component type. Next, the system sequentially checks the settings of the component instance's input, processing, and output parameters. For input parameters, the system verifies that the data source and field mappings are specified. For processing parameters, the system verifies that required configuration items are set and conform to formatting requirements. For output parameters, the system confirms that the output field definitions are complete. The system records the results of each parameter check in a verification result set, which serves as a basis for subsequent process decisions.

[0071] S206: If the configuration parameters are complete, generate a data processing flow including a business processing flow according to the connection relationship between the components and the configuration parameters of each component.

[0072] A business process is a collection of data processing steps required to achieve a specific business goal. A data processing flow is a computerized representation of the business process, encompassing the specific execution logic and data processing details. The connections between components and their configuration parameters together form a complete process definition.

[0073] When generating a data processing flow, the system first constructs a directed acyclic graph (DAG) data structure, in which nodes represent components and edges represent the connection relationships between components. The system topologically sorts the graph to determine the execution order of the components. For each component, the system collects its complete configuration information, including: connected data source information, data processing logic, calculation rules, output format definition, etc. This information is organized into a standardized process description document and stored in JSON or XML format. The document contains basic information about the process (such as creation time, version number, etc.), a component list (containing the complete configuration of each component), a connection relationship definition (recording the data flow path between components), and other content. This processing flow document will serve as the basis for subsequent script generation and execution.

[0074] S207: If the configuration parameters are incomplete, a parameter supplement prompt message is sent to the target client.

[0075] Parameter supplementary prompts are system-generated text messages used to guide users through parameter configuration. They include descriptions of missing parameters, component information, and supplementary suggestions. The target client is the user's current operating terminal, which can be a web browser, desktop application, or mobile application. Sending the prompts involves transmitting the prompts over the network to the user interface for display.

[0076] In specific implementations, the system first generates structured prompt information based on the parameter validation results. This information contains the following fields: component ID, component name, parameter type (input / processing / output), parameter name, missing description, and filling instructions. The system then encapsulates this information into a JSON-formatted message and sends it to the target client via a WebSocket or HTTP request. After receiving the prompt information, the client selects an appropriate display method based on the message type and severity, such as a pop-up window, an inline prompt, or a status bar prompt. The user is then provided with a quick shortcut to jump directly to the corresponding parameter configuration interface.

[0077] S208. In response to the save instruction, the data processing flow information is converted into a calculation caliber file in a dynamic script language format, which contains the script code of data processing timing, processing time, processing logic, query detail data and calculation index data.

[0078] Dynamic scripting languages, such as Python and JavaScript, are programming languages ​​that can be dynamically interpreted and executed at runtime. A calculation scope file is a text file that describes the data processing flow, organizing and storing the processing logic in a specific format. The data processing timing specifies the script's execution trigger conditions, while the processing duration defines the execution timeout. The processing logic includes specific data manipulation steps, while querying detailed data and calculating indicator data specifically capture and calculate the data.

[0079] When executing the conversion process, the system first deconstructs the data processing flow into basic operation units. For each operation unit, the system generates a corresponding script code snippet. This includes: generating database connection and query code, setting query parameters and conditions; generating data processing code, including operations such as data cleansing, conversion, and calculation; and generating result storage code, defining the output format and storage location. These code snippets are organized according to the processing flow sequence, and necessary error handling and logging code are added. Finally, the system saves the generated code as a calculation caliber file, which contains the complete execution configuration and processing logic.

[0080] S209: compile the calculation caliber file through a parser to generate script code.

[0081] A parser is a program module that converts high-level programming languages ​​into executable code. It analyzes the grammatical structure of the source code and generates target code. Compilation is the process of converting source code into executable code, including lexical analysis, syntax analysis, semantic analysis, and code generation. Script code is the program code that can ultimately be directly interpreted and executed by the execution engine.

[0082] During the compilation process, the system first initializes the language parser, loading the necessary grammar rules and standard libraries. The parser reads the contents of the computational scope file and performs lexical analysis, breaking the source code into a sequence of tokens. It then performs syntactic analysis, constructing an abstract syntax tree (AST) to verify the correctness of the code structure. Semantic analysis then checks constraints such as variable declarations and type matching. Finally, based on the analysis results, the system generates optimized target code, including variable declarations, function definitions, and control flow statements. The generated script code uses a standardized format to ensure correct execution in the target execution environment.

[0083] S210: If the compilation is successful, the generated script code is stored in the database.

[0084] Successful compilation means that no errors were found during all compilation phases of the script code, including syntax checking and semantic analysis. Script code is a set of instructions written according to the grammatical rules of a specific programming language, used to perform data processing tasks. In this context, the database serves as a code repository, centrally managing and maintaining all verified script code.

[0085] The stored procedure specifically includes the following steps: First, the system creates a unique identifier for the generated script code, typically consisting of a timestamp and a random string. The system then converts the script code into BASE64 encoding or another format suitable for database storage to ensure that special characters are correctly preserved. The system creates a script code table in the database, containing fields such as the script ID, the associated quality control indicator ID, the script content, the creation time, the last modification time, and the version number. The encoded script content and its metadata are written to the database using SQL INSERT or UPDATE statements, and an association with the quality control indicator is established. The system also maintains the script's version history to facilitate tracking modification records and version rollbacks.

[0086] S211. If the compilation fails, an error message is returned to the target client.

[0087] Compilation failures occur when syntax errors, semantic errors, or other anomalies are detected during the code compilation process. Error messages provide a textual description of the specific cause of the compilation failure, including the error type, location, and suggested solutions. The target client, the user's terminal device, is responsible for displaying error messages and enabling users to correct them.

[0088] When compilation fails, the system first collects all error and warning information generated during the compilation process. For each error, the system records its detailed information, including: error code, error description, error location (line number, column number), involved code snippet, suggested repair method, etc. The system formats this information into a structured error report organized in JSON format. The error report is sent to the target client via HTTP response or WebSocket message. After the client receives the error information, it converts it into a user-friendly prompt form, such as an error prompt dialog box or embedded error mark, and provides navigation function to quickly locate the error location.

[0089] S212: Execute the script code at a set time interval.

[0090] An interval is a fixed time period between script executions, and can be measured in units of minutes, hours, days, or other time units. Script execution refers to the process by which the interpreter processes instructions according to the logical sequence of the code, completing data operations. The interval is typically determined based on business needs and system resource availability.

[0091] The specific implementation of the execution process includes: the system first creates a scheduled task scheduler and uses cron expressions to define the execution plan, such as "0 0 * / 1 * * ?", which means execution once every hour. When the execution time point is reached, the scheduler activates the script execution engine and loads the corresponding script code from the database. The execution engine initializes the running environment, including setting the execution timeout, allocating memory space, preparing database connections, etc. The execution engine then interprets and executes the script instructions one by one, during which the execution status, performance indicators, and key node logs are recorded. After execution is completed, the system updates the task execution record, including information such as the start time, end time, and execution results. If an exception occurs during the execution process, the system will trigger the error handling mechanism to ensure data consistency and record detailed error information.

[0092] S213: Record the execution log and calculation result of the script code, and establish a corresponding relationship between the execution log, calculation result and the quality control indicator identifier and store them.

[0093] Execution logs record detailed information about the script's execution process, including execution time, steps, resource usage, and exception information. Calculation results are the data processing output generated after script execution, such as statistics and analysis reports. Corresponding relationship storage organizes data by linking execution logs and calculation results with quality control indicators, facilitating subsequent query and tracking.

[0094] During the specific implementation process, the system first creates a logger and uses a structured log format (such as JSON) to record the execution process information. The log content includes: execution timestamp, script ID, quality control indicator ID, execution steps, SQL statements, data processing volume, execution time, resource usage (CPU, memory), etc. For the calculation results, the system creates a special result table with fields including: result ID, quality control indicator ID, calculation time, indicator value, data dimension, statistical period, etc. The system associates the execution log table and the calculation result table with the quality control indicator table through a foreign key relationship to establish a corresponding relationship between the three. In addition, the system also establishes indexes to optimize query performance and implements log hierarchical storage and archiving strategies.

[0095] The following is a more detailed description of the process of the method provided by this implementation. Figure 2 , is another flow chart of the hospital quality control data preprocessing and heterogeneous data integration method in the embodiment of this application.

[0096] S301: extracting a calculation rule template from the data processing flow, where the calculation rule template includes a combination mode of the components, a connection relationship between the components, and the configuration parameters.

[0097] A calculation rule template is a standardized data processing specification used to guide data processing in similar business scenarios. The combination of components describes the arrangement and organization of processing units. The connections between components define the data flow path. Configuration parameters include specific settings for each processing unit.

[0098] When extracting calculation rule templates, the system first analyzes the structural characteristics of the data processing flow. It abstracts the component combination, identifying the core processing units and their organizational modes, such as serial processing, parallel processing, or hybrid modes. The system extracts the connection relationships between components, including data flow, dependencies, and control flows. For configuration parameters, the system identifies key parameters and variable parameters, using fixed parameter values ​​as template defaults and defining variable parameters as template variables. This information is organized into a standard template description document, stored in XML or JSON format, containing the template ID, applicable scenarios, component definitions, connection relationships, parameter configurations, and other content.

[0099] S302: In response to a request for adding a new quality control indicator, obtain calculation elements of the new quality control indicator, and perform matching calculation between the calculation elements and elements in the calculation rule template.

[0100] Calculation elements are the basic data items and processing rules required to calculate quality control indicators. New quality control indicators are new medical quality assessment indicators that need to be added to the system. Match calculation is a quantitative process that evaluates the degree of similarity between new indicators and existing templates.

[0101] During the matching process, the system first analyzes the definition of the newly added quality control indicator and extracts its calculation elements, including data source type, input fields, calculation rules, time dimension, and statistical granularity. The system then loads the existing calculation rule template library and performs a similarity assessment on each template. This similarity calculation utilizes a multi-dimensional scoring mechanism, including data source matching (assessing the similarity of data sources), field matching (comparing the correspondence between input and output fields), calculation logic matching (analyzing the similarity of processing rules), and constraint matching (comparing filter conditions and restriction rules). The system assigns weights to each dimension, calculates a comprehensive matching score, and sorts the matching results in descending order by score.

[0102] S303. When the matching degree exceeds the preset matching degree threshold, the calculation rule template is applied to the newly added quality control indicator, and the corresponding data processing flow is generated and displayed in the calculation caliber editing interface.

[0103] The preset match threshold is a system-defined minimum match standard used to determine whether a template is suitable for a new indicator. Match is a numerical indicator that measures the degree of similarity between the template and the new indicator. Applying a template is the process of adapting an existing processing rule template to a new indicator, including parameter replacement and rule adjustments.

[0104] During the implementation process, the system first compares the calculated degree of match with a preset threshold. If the degree of match exceeds the threshold, the system begins the template application process: first, the selected calculation rule template is cloned to create a new processing flow instance; then, the specific parameters of the newly added quality control indicators are replaced with the variables in the template, including data source configuration, field mapping, calculation formula, etc.; then, based on the replaced configuration information, the system rebuilds the component layout on the calculation caliber editing interface, including component position, connection lines, parameter settings, etc.; finally, the system automatically fills in the component configuration parameters and highlights the configuration items requiring user confirmation on the interface. The entire process forms a complete visual data processing flow.

[0105] S304: Run the script code according to a preset fixed execution cycle and start the incremental update mode. The incremental update mode calculates the new data that is later than the last execution timestamp in each incremental update cycle.

[0106] The default fixed execution cycle is the system-defined interval at which the script runs periodically. Incremental update mode is a data processing strategy that only processes newly added data records. The execution timestamp is the time point at which each script runs. New data refers to data records generated between two execution timestamps.

[0107] To implement the operational mechanism, the system first configures a scheduled task scheduler and creates an execution plan based on a preset execution period (such as hourly or daily). During each execution, the system records the current execution timestamp and compares it with the previous execution timestamp to determine the time range of the data to be processed. The system then modifies the original SQL query statement, adding a timestamp filter to ensure that only newly added data is queried. For incremental data retrieved, the system performs calculations according to the processing logic defined in the script and appends the results to the result table. The system also maintains an execution timestamp record table, storing the time point information for each execution, which serves as the basis for the next incremental update.

[0108] S305: Perform data sampling analysis on the calculation results generated in each incremental update cycle to obtain the variation range of the statistical indicators.

[0109] The incremental update cycle is the time interval between two incremental data processing cycles. Data sampling analysis is the process of sampling and checking calculation results. The magnitude of change in a statistical indicator indicates the degree of change in the indicator value relative to historical data.

[0110] During the analysis process, the system first extracts data samples from the calculation results within the incremental update cycle. Sampling strategies include sampling by time interval, sampling by data volume ratio, or stratified random sampling. Statistical analysis is performed on the sampled data, calculating key indicators such as mean, standard deviation, maximum, and minimum values. The system compares the statistical values ​​of the current cycle with historical data and calculates the magnitude of change, including absolute change, relative rate of change, and month-on-month rate of change. These statistical results are recorded in a dedicated analysis results table with fields such as analysis time, sample size, statistical value, and rate of change, for subsequent quality monitoring and trend analysis.

[0111] S306: When the change range of a key statistical indicator exceeds a preset change threshold, the key statistical indicator is traced to obtain an abnormal data item.

[0112] Key statistical indicators are core metrics that significantly impact data quality and business performance. Preset change thresholds are the system's predefined tolerances for indicator fluctuations. Location tracing is an analytical method that traces back to locate the source of abnormal data. Abnormal data items are specific data records that cause unusual fluctuations in indicators.

[0113] During the anomaly tracing process, the system first identifies key statistical indicators whose changes exceed a threshold. For each anomaly indicator, the system initiates a multi-level tracing analysis: First, the time period in which the anomaly occurred is determined to narrow the scope of investigation; then, the calculation process is broken down, examining the results of each intermediate step; statistical analysis of the input data for each step is performed, including data distribution and outlier detection; and the specific anomaly record is located, including record ID, data value, and time of occurrence. The system stores the traced anomaly data records in an anomaly data table, with fields including anomaly ID, indicator ID, data ID, anomaly type, anomaly severity, and discovery time. The complete tracing path is also recorded to facilitate subsequent analysis and processing.

[0114] S307. Mark the abnormal data item in the calculation caliber maintenance interface.

[0115] Abnormal data item annotation is a visual process that highlights abnormal data in a special way on the interface. The calculation caliber maintenance interface is a user interaction interface for configuring and managing data processing processes.

[0116] When implementing the annotation function, the system first locates the processing nodes involved in the abnormal data on the data flow diagram of the calculation caliber maintenance interface. For each abnormal data item, the system uses a variety of visual annotation methods: adding warning icons to the relevant components, distinguishing the severity of the abnormality by color (such as red for serious abnormalities, yellow for minor abnormalities); marking the flow of abnormal data on the component connection line, using different line types or thicknesses to represent the abnormal propagation path; creating an abnormal data details panel to display the specific information of the abnormal record, including data value, abnormal cause, impact range, etc.; providing abnormal data filtering and navigation functions, supporting rapid positioning and switching of different abnormal items. The system also provides an operation entry for exception handling on the interface, including data correction, rule adjustment, ignoring exceptions and other functions, and records logs of all processing operations.

[0117] The following describes the hospital quality control data preprocessing and heterogeneous data integration system in the embodiment of the present invention from the perspective of hardware processing. Figure 4 , which is a schematic diagram of the physical device structure of the hospital quality control data preprocessing and heterogeneous data integration system in the embodiment of the present application.

[0118] It should be noted that Figure 4 The structure of the hospital quality control data preprocessing and heterogeneous data integration system shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0119] like Figure 4 As shown, the hospital quality control data preprocessing and heterogeneous data integration system includes a central processing unit (CPU) 401, which can perform various appropriate actions and processes based on programs stored in a read-only memory (ROM) 402 or programs loaded from a storage unit 408 into a random access memory (RAM) 403, such as executing the methods described in the above embodiments. RAM 403 also stores various programs and data required for system operation. CPU 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to bus 404.

[0120] The following components are connected to the I / O interface 405: an input section 406 including an audio input device, push button switches, and the like; an output section 407 including a liquid crystal display (LCD), an audio output device, indicator lights, and the like; a storage section 408 including a hard disk and the like; and a communication section 409 including a network interface card such as a LAN (Local Area Network) card or a modem. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to the I / O interface 405 as needed. Removable media 411, such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory, is installed in the drive 410 as needed, so that computer programs read from the removable media can be installed in the storage section 408 as needed.

[0121] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for executing the methods illustrated in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 409 and / or installed from removable media 411. When executed by central processing unit (CPU) 401, the computer program performs the various functions defined in the present invention.

[0122] It should be noted that specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In the present invention, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0123] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present invention. Each box in the flowchart or block diagram can represent a module, program segment, or part of the code, and the above-mentioned module, program segment, or part of the code contains one or more executable instructions for implementing the specified logical functions. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings.

[0124] Specifically, the hospital quality control data preprocessing and heterogeneous data integration system of this embodiment includes a processor and a memory, and a computer program is stored in the memory. When the computer program is executed by the processor, the hospital quality control data preprocessing and heterogeneous data integration method provided in the above embodiment is implemented.

[0125] As another aspect, the present invention further provides a computer-readable storage medium, which may be included in the hospital quality control data preprocessing and heterogeneous data integration system described in the above embodiments, or may exist independently and not be incorporated into the hospital quality control data preprocessing and heterogeneous data integration system. The above storage medium carries one or more computer programs, which, when executed by a processor of the hospital quality control data preprocessing and heterogeneous data integration system, enable the hospital quality control data preprocessing and heterogeneous data integration system to implement the hospital quality control data preprocessing and heterogeneous data integration method provided in the above embodiments.

[0126] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

[0127] As used in the above embodiments, the term “when” may be interpreted to mean “if” or “after” or “in response to determining that” or “in response to detecting that”, depending on the context. Similarly, the phrases “upon determining that” or “if (stated condition or event) is detected” may be interpreted to mean “if determining that” or “in response to determining that” or “upon detecting (stated condition or event)” or “in response to detecting (stated condition or event)”, depending on the context.

[0128] Those skilled in the art will appreciate that all or part of the process steps in the above-described method embodiments can be implemented by a computer program instructing the relevant hardware. The program can be stored in a computer-readable storage medium, and when executed, the program can include the process steps in the above-described method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A method for preprocessing hospital quality control data and integrating heterogeneous data, characterized in that: Applied to hospital quality control data preprocessing and heterogeneous data integration system, the method includes: Read a hospital quality control indicator set from a database, and display the hospital quality control indicator set in a calculation caliber maintenance interface; Receiving a quality control indicator identifier selected in the hospital quality control indicator set, and displaying an operation component library corresponding to the quality control indicator identifier on a calculation caliber editing interface, wherein the operation component library includes a data source connection component, a data processing component, and a calculation formula component; In response to the drag-and-drop operation and the connection operation of the components, a data processing flow is generated, wherein the data processing flow includes the configuration information of each component and the data flow relationship between each component; In response to a save instruction, converting the data processing flow into script code; Execute the script code at a set time interval; The execution log and calculation result of the script code are recorded, and the execution log, calculation result and the quality control indicator identifier are stored in a corresponding relationship.

2. The method according to claim 1, characterized in that In response to the drag-and-drop operation and the connection operation of the components, a data processing flow is generated, and the data processing flow includes the configuration information of each component and the steps of the data flow relationship between each component, specifically including: Receiving a user's drag-and-drop operation on a component in the operation component library, and displaying the dragged and dropped component on a calculation caliber editing interface; In response to the user's connection operation, the connection relationship between components is displayed on the calculation caliber editing interface, and the data flow direction between adjacent components is recorded; Detecting whether the configuration parameters of each of the components are complete, the configuration parameters including input parameters, processing parameters and output parameters of the component; If the configuration parameters are complete, a data processing flow including a business processing flow is generated according to the connection relationship between the components and the configuration parameters of each component.

3. The method according to claim 1, characterized in that The step of converting the data processing flow into script code in response to the save instruction specifically includes: In response to the save instruction, the data processing flow information is converted into a calculation caliber file in a dynamic script language format, which contains the script code of data processing timing, processing duration, processing logic, query detail data and calculation index data; The calculation caliber file is compiled by a parser to generate script code.

4. The method according to claim 2, characterized in that: After the step of detecting whether the configuration parameters of each component are complete, wherein the configuration parameters include input parameters, processing parameters and output parameters of the component, the method further comprises: If the configuration parameters are incomplete, a parameter supplement prompt message is sent to the target client.

5. The method according to claim 3, characterized in that: After the step of compiling the calculation caliber file by a parser to generate script code, the method further includes: If the compilation is successful, the generated script code is stored in the database; If the compilation fails, an error message is returned to the target client.

6. The method according to claim 1, characterized in that After the step of recording the execution log and calculation result of the script code, and storing the execution log, calculation result and the quality control indicator identifier in a corresponding relationship, the method further includes: Extracting a calculation rule template from the data processing flow, wherein the calculation rule template includes a combination mode of the components, a connection relationship between the components, and the configuration parameters; In response to a request for adding a new quality control indicator, obtaining a calculation element of the new quality control indicator, and performing a matching degree calculation between the calculation element and an element in the calculation rule template; When the matching degree exceeds a preset matching degree threshold, the calculation rule template is applied to the newly added quality control indicator, and the corresponding data processing flow is generated and displayed in the calculation caliber editing interface.

7. The method according to claim 1, characterized in that After the step of recording the execution log and calculation result of the script code, and storing the execution log, calculation result and the quality control indicator identifier in a corresponding relationship, the method further includes: Run the script code according to a preset fixed execution cycle and start the incremental update mode, wherein the incremental update mode calculates the newly added data later than the last execution timestamp in each incremental update cycle; Performing data sampling and analysis on the calculation results generated in each incremental update cycle to obtain a variation range of the statistical indicator; When the change range of a key statistical indicator exceeds a preset change threshold, the key statistical indicator is traced back to obtain an abnormal data item; The abnormal data item is marked in the calculation caliber maintenance interface.

8. A hospital quality control data preprocessing and heterogeneous data integration system, characterized in that: The hospital quality control data preprocessing and heterogeneous data integration system includes: one or more processors and a memory; the memory is coupled to the one or more processors, the memory is used to store computer program code, the computer program code includes computer instructions, and the one or more processors call the computer instructions to enable the hospital quality control data preprocessing and heterogeneous data integration system to execute the method described in any one of claims 1-7.

9. A computer-readable storage medium comprising instructions, characterized in that: When the instruction is executed on the hospital quality control data preprocessing and heterogeneous data integration system, the hospital quality control data preprocessing and heterogeneous data integration system executes the method as described in any one of claims 1-7.

10. A computer program product, characterized in that When the computer program product runs on a hospital quality control data preprocessing and heterogeneous data integration system, the hospital quality control data preprocessing and heterogeneous data integration system executes the method as described in any one of claims 1-7.

Images