Closed-loop data processing method, apparatus, and electronic device

Abstract

The application provides a closed loop data processing method and device and electronic equipment. The method comprises: obtaining input patient information; the patient information comprises at least one of the following: patient ID, medical ID and medical order ID; based on preset closed loop node configuration data and patient information, finding corresponding closed loop data of the patient information from a database; based on node array configuration information in the closed loop node configuration data, detecting node data in the closed loop data to obtain a closed loop data detection result; the closed loop data detection result comprises closed loop node information and debugging information, or further comprises quality information and overdue information; and the closed loop data detection result is displayed on a page. The application can detect the node of the closed loop data of the patient, display the detection result such as debugging information, quality information or overdue information, and enable the user to more conveniently understand the closed loop data of the patient.

Description

Technical Field

[0001] This application relates to the field of medical technology, and in particular to a closed-loop data processing method, apparatus, and electronic device. Background Technology

[0002] In medical order processing systems, existing closed-loop processing methods typically involve querying the business database for known nodes and displaying the query results, which usually include the operation time, operator, and node information. This closed-loop business display method is relatively simple. When closed-loop nodes are configured but data is not displayed, users often cannot troubleshoot on their own and must contact the development team. Summary of the Invention

[0003] The purpose of this application is to provide a closed-loop data processing method, device, and electronic device that can perform node detection on the patient's closed-loop data and display the detection results, such as closed-loop node information, debugging information, quality information, or overdue information, so that users can more easily understand the patient's closed-loop data status.

[0004] In a first aspect, this application provides a closed-loop data processing method, the method comprising: acquiring input patient information; the patient information including at least one of the following: patient ID, visit ID, and medical order ID; searching for closed-loop data corresponding to the patient information in a database based on preset closed-loop node configuration data and the patient information; detecting the node data in the closed-loop data based on the node array configuration information in the closed-loop node configuration data to obtain closed-loop data detection results; the closed-loop data detection results including: closed-loop node information, debugging information, or further including: quality information and overdue information; and displaying the closed-loop data detection results on a page.

[0005] Furthermore, before the above-mentioned step of obtaining the input patient information, the following steps are also included: verifying the configuration data of the closed-loop node; if the verification result is qualified, continue to execute the step of obtaining the input patient information; if the verification result is unqualified, return a prompt message indicating that the configuration is incorrect.

[0006] Furthermore, the above steps for validating the closed-loop node configuration data include: validating the closed-loop node configuration data in at least one of the following aspects: determining whether the closed-loop node configuration data is in a specified format; determining whether the closed-loop node configuration data simultaneously contains the closed-loop title, the closed-loop main table, query condition configuration information, and database connection information; determining whether the length of the node array of the closed-loop node configuration data is greater than 1; determining whether the node array includes: node ID, node name, node corresponding table, node corresponding field, node query configuration, database connection information, overdue configuration information, and quality configuration information; determining whether the node corresponding field and node query configuration meet preset conditions; checking whether the quality configuration information meets a preset format; determining whether each node ID is unique; checking whether the node start ID and node end ID in the node connection are included in the node array; if any of the above at least one aspect of the validation fails, the closed-loop node configuration data is deemed unqualified.

[0007] Furthermore, the above-mentioned step of searching for closed-loop data corresponding to patient information from the database based on preset closed-loop node configuration data and patient information includes: searching for the closed-loop master table and query condition configuration from the closed-loop node configuration data; assembling and generating a first database query statement based on the closed-loop master table, query condition configuration, and patient information; and searching for the closed-loop data corresponding to patient information from the database based on the first database query statement.

[0008] Furthermore, the aforementioned node array configuration information includes: multiple query condition configurations corresponding to each closed loop node; the steps of detecting node data in the closed loop data based on the node array configuration information in the closed loop node configuration data to obtain the closed loop data detection results include: for each closed loop node in the closed loop node configuration data, the following steps are performed: based on the multiple query condition configurations corresponding to the closed loop node, node fields are matched one by one in the closed loop data to obtain multiple node query conditions corresponding to the closed loop node; the multiple node query conditions, the node correspondence table of the closed loop node, and the node correspondence fields are combined to form a second database query statement; the corresponding data is queried in the database using the second database query statement; if the query result is empty, the second database query statement and the corresponding node name are saved to the debug queue, and the prompt message indicating that the node has no data is saved to the quality queue; if the query result is not empty, the node correspondence fields of each node and the node field values ​​queried based on the node correspondence fields are concatenated to obtain the node data corresponding to the closed loop node.

[0009] Furthermore, the above node array configuration information also includes: quality configuration information; the quality configuration information includes: quality detection field, function index value, comparison type, and comparison value; after obtaining the node data corresponding to the closed node, it also includes: searching for the data corresponding to the quality detection field from the node data corresponding to the closed node; obtaining the corresponding preset verification function according to the function index value; inputting the data corresponding to the quality detection field, comparison type, and comparison value into the preset verification function for verification; if the verification result indicates that there is a quality problem, concatenating the node name of the closed node, the quality configuration information, and the verification result value into a string and inserting it into the quality queue.

[0010] Furthermore, the above node array configuration information also includes: overdue configuration information and node connection data; the overdue configuration information includes: overdue verification formula; after obtaining the node data corresponding to the closed node, it also includes: obtaining the operation time of the closed node and the operation time of the previous node; calculating the time difference between the operation time of the closed node and the operation time of the previous node; finding the corresponding connection in the node connection data according to the ID of the closed node and the previous node, and updating the label of this connection with the time difference; matching the time difference with the overdue verification formula, and if the condition is not met, inserting the node name, operation time and overdue prompt information into the overdue queue.

[0011] Furthermore, the steps for displaying the closed-loop data detection results on a page include: displaying the closed-loop data detection results in a graphical interface; wherein, the closed-loop node information is displayed in the form of a flowchart, where each process node represents a step, and the lines between process nodes represent the execution order of the process; each process node displays the node name, operator, and operation time; debugging information is displayed in the sidebar or pop-up window of the interface, providing detailed debugging information, including query statements, to help users troubleshoot problems and optimize configurations; quality information is displayed in the form of a list or chart, listing the nodes that do not meet the quality inspection standards and their corresponding information.

[0012] Secondly, this application also provides a closed-loop data processing device, comprising: an information acquisition module for acquiring input patient information; the patient information includes at least one of the following: patient ID, visit ID, and medical order ID; a data search module for searching for closed-loop data corresponding to the patient information from a database based on preset closed-loop node configuration data and the patient information; a node detection module for detecting node data in the closed-loop data based on node array configuration information in the closed-loop node configuration data, and obtaining closed-loop data detection results; the closed-loop data detection results include: closed-loop node information, debugging information, or may also include: quality information and overdue information; and a result display module for displaying the closed-loop data detection results on a page.

[0013] Thirdly, this application also provides an electronic device, including a processor and a memory, wherein the memory stores computer-executable instructions that can be executed by the processor, and the processor executes the computer-executable instructions to implement the method described in the first aspect above.

[0014] Fourthly, this application also provides a computer-readable storage medium storing computer-executable instructions, which, when invoked and executed by a processor, cause the processor to implement the method described in the first aspect above.

[0015] The closed-loop data processing method, apparatus, and electronic device provided in this application first acquire input patient information; the patient information includes at least one of the following: patient ID, visit ID, or medical order ID; based on preset closed-loop node configuration data and the patient information, the closed-loop data corresponding to the patient information is retrieved from the database; based on the node array configuration information in the closed-loop node configuration data, the node data in the closed-loop data is detected to obtain the closed-loop data detection result; the closed-loop data detection result includes: closed-loop node information, debugging information, and may also include: quality information and overdue information; the closed-loop data detection result is displayed on a page. This application can perform node detection on the patient's closed-loop data and display the detection results, such as debugging information, quality information, or overdue information, so that users can more easily understand the patient's closed-loop data status. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the specific embodiments of this application or the prior art, the drawings used in the description of the specific embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0017] Figure 1 A flowchart illustrating a closed-loop data processing method provided in this application embodiment;

[0018] Figure 2 A closed-loop display effect diagram provided for an embodiment of this application;

[0019] Figure 3 A schematic diagram illustrating data debugging as provided in an embodiment of this application;

[0020] Figure 4 A structural block diagram of a closed-loop data processing device provided in an embodiment of this application;

[0021] Figure 5 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0022] The technical solutions of this application will be clearly and completely described below with reference to the embodiments. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0023] Existing technologies offer relatively simple closed-loop business display methods, often lacking configuration options and support for displaying closed-loop information. Furthermore, when closed-loop steps are configured but data is not displayed, users are often unable to troubleshoot on their own and must contact the R&D personnel.

[0024] Based on this, embodiments of this application provide a closed-loop data processing method, apparatus, and electronic device that can perform node detection on the patient's closed-loop data and display the detection results, such as debugging information, quality information, or overdue information, so that users can more easily understand the patient's closed-loop data status.

[0025] To facilitate understanding of this embodiment, a closed-loop data processing method disclosed in this application embodiment will first be described in detail.

[0026] Figure 1 A flowchart of a closed-loop data processing method provided in this application embodiment is shown. The method specifically includes the following steps:

[0027] Step S102: Obtain the input patient information; the patient information includes at least one of the following: patient ID, visit ID, or doctor's order ID;

[0028] For example, on the closed-loop data processing page, users can enter the Patient ID, Visit ID, and Order No.

[0029] Step S104: Based on the preset closed-loop configuration data and patient information, search the database for the closed-loop data corresponding to the patient information.

[0030] The aforementioned closed-loop node configuration data can be pre-configured by the user or automatically generated by the system. This includes closed-loop configuration information and node array configuration information. The closed-loop configuration information includes: closed-loop title, closed-loop main table, query condition configuration information, and database connection information. The node array configuration information includes: node style data, node configuration data, and node connection data. Node style data characterizes the node's style, such as whether it's rectangular or circular, background color, etc. Node configuration data includes: quality configuration information and expired configuration information. Node connection data refers to the connection data between closed-loop nodes. Quality configuration information is used to check whether the node data quality is acceptable, and expired configuration information is used to check whether the time information corresponding to the node data is acceptable.

[0031] The aforementioned database pre-stores medical treatment information for each patient. Based on the preset closed-loop node configuration data and patient information, a first database query statement can be generated. This query statement can then be used to retrieve the closed-loop data corresponding to the patient's information from the database. The retrieved closed-loop data includes data from multiple nodes. For example, it might include three nodes: medical orders, tests, and viewings. The closed-loop data would contain the data corresponding to each of these three nodes. The data for each node could include the operator, operation time, and specific operation details.

[0032] Step S106: Based on the node array configuration information in the closed-loop node configuration data, the node data in the closed-loop data is detected to obtain the closed-loop data detection result; the closed-loop data detection result includes: closed-loop node information, debugging information, or may also include: quality information and overdue information.

[0033] The aforementioned closed-loop node information includes node data for each node, such as the operator, operation time, and specific operation content for each node. Debugging information includes common query conditions, such as node name, table name, time field, doctor field, and query conditions. Debugging information also includes query conditions and other data stored in the debugging queue; displaying this information facilitates troubleshooting and configuration optimization. Quality information includes quality issue data for nodes that fail to meet quality standards, stored in the quality queue; for example, a field exceeding its length standard. Expiration information includes timeout data for nodes with non-compliant operation times, stored in the expiration queue; for example, information indicating that a node's operation time has expired.

[0034] Step S108: Display the closed-loop data detection results on the page.

[0035] Finally, the aforementioned closed-loop information, debugging information, quality information, and overdue information will be displayed on the system page. Various methods can be used for display, such as flowcharts or small icons, etc. No specific limitation is made here.

[0036] The closed-loop data processing method provided in this application improves the user experience and makes the closed-loop display clearer by optimizing some aspects of the closed-loop display process, including supporting quality and overdue configurations, and presenting debugging and quality information while displaying closed-loop step information.

[0037] This application also provides another closed-loop data processing method, which is implemented based on the above embodiments. This embodiment focuses on describing the detection process of closed-loop node configuration data, the closed-loop data query process, the node data detection process, and the result display method.

[0038] In one implementation, before the step of obtaining the input patient information (i.e., step S102), a data verification process may be included, specifically including: verifying the configuration data of the closed-loop node; if the verification result is qualified, continuing to execute the step of obtaining the input patient information; if the verification result is unqualified, returning a prompt message indicating that the configuration is incorrect.

[0039] Specifically, the steps for verifying the configuration data of the closed loop point mentioned above include:

[0040] The following aspects of the closed-loop configuration data are verified sequentially:

[0041] (1) Determine whether the configuration data of the closed loop point is in the specified format;

[0042] (2) Determine whether the closed loop configuration data contains the closed loop title, closed loop main table, query condition configuration information and database connection information at the same time.

[0043] (3) Determine whether the length of the node array of the closed-loop node configuration data is greater than 1;

[0044] (4) Determine whether the node array includes: node ID, node name, node corresponding table, node corresponding field, node query configuration, database connection information, overdue configuration information, and quality configuration information;

[0045] (5) Determine whether the corresponding fields of the node and the node query configuration meet the preset conditions;

[0046] (6) Check whether the quality configuration information meets the preset format;

[0047] (7) Determine if each node ID is unique;

[0048] (8) Check whether the start ID and end ID of the node in the node connection are included in the node array;

[0049] If any of the above multi-faceted verifications fails, the closed-loop node configuration data verification is deemed unqualified.

[0050] For example, determining whether the configuration information of the closing node is in the specified format;

[0051] If not, return an incorrectly formatted message;

[0052] If so, further determine whether the closed loop configuration information includes the closed loop title, the closed loop main table, query condition configuration information (such as key-value pairs, {“PatientID”:“PatientID”,“VISITID”:“VISITID”,“OrderNo”:“OrderNo”}) and database connection information;

[0053] If not, return a message indicating insufficient closed-loop configuration data and requesting you to check.

[0054] If so, further check if the length of the node array is greater than 1;

[0055] If not, return a message indicating that the number of closed loop points is less than 2 and you should check.

[0056] If so, check whether the node array includes: node ID, node name, node corresponding table, node corresponding field, node query configuration, database connection information, overdue configuration information, and quality configuration information;

[0057] If not, the returned message indicates insufficient data in the node field; please check.

[0058] If so, check whether the corresponding fields of the node and the node query condition type meet the preset conditions (whether they are key-value pairs, and whether the relevant fields include the operation time).

[0059] If not, the returned message indicates that the field corresponding to the node or the query condition does not meet the rules, and you should check it.

[0060] If so, check if the quality configuration information meets the preset format; the quality configuration information is an expression, where the rules are of the type "field|rule|size|value" (operator|length|greater than|5), and each rule is separated by a comma.

[0061] If not, a message will be returned indicating that the quality configuration information does not conform to the rules and request you to check.

[0062] If so, check whether the overdue configuration information meets the preset requirements; the overdue configuration information is a judgment expression (such as n>30 or n>0&&n<20).

[0063] If not, the returned message will indicate that the expired configuration information does not meet the requirements and you should check it.

[0064] If so, check if each node ID is unique;

[0065] If not, the returned message indicates that the node ID is not unique and you should check.

[0066] If so, check if the start ID and end ID of the node in the node connection are included in the node array;

[0067] If not, return the message "Target object for node connection is out of range, please check";

[0068] If so, the verification result is qualified.

[0069] In one possible implementation, the step of searching for closed-loop data corresponding to patient information from the database based on preset closed-loop point configuration data and patient information includes:

[0070] The system retrieves the closed-loop master table and query condition configuration from the closed-loop node configuration data; it then assembles and generates a first database query statement based on the closed-loop master table, query condition configuration, and patient information; finally, it retrieves the closed-loop data corresponding to the patient information from the database based on the first database query statement.

[0071] In practice, the closed-loop master table and query condition configuration are first obtained, and a connection is established with the database. Next, the key-value pairs of the query condition configuration are matched against the data entered by the user. If no match is found, an "error parameter" is returned. If a match is successful, the table and query conditions are assembled, and the data is retrieved through the database connection. If the query result is empty, an "no closed-loop data found, please check" message is returned; if data is found, the result is saved to the closed-loop master data.

[0072] For example, the obtained closed-loop master table is Table 1; the obtained query condition configuration includes: "Gender = #{SEX}" (this is just an example; it can also include name, age, and other query condition configurations). By matching it with the user-input data, we get "Gender = Female"; that is, a successful match. At this point, we can generate the first database query statement: "select * from table1 where gender = female". Using this query statement to query the database data, we can obtain the closed-loop data corresponding to the patient.

[0073] Furthermore, the aforementioned node array configuration information includes: node query conditions; the steps of detecting node data in the closed-loop data based on the node array configuration information in the closed-loop node configuration data to obtain the closed-loop data detection results include:

[0074] For each closed-loop node in the configuration data, the following steps are performed: Based on the multiple query conditions configured for the closed-loop node, the node fields are matched one by one in the closed-loop data to obtain multiple node query conditions corresponding to the closed-loop node; the multiple node query conditions, the node-to-node table of the closed-loop node, and the corresponding fields of the nodes are combined to form a second database query statement; the corresponding data is queried in the database using the second database query statement; if the query result is empty, the second database query statement and the corresponding node name are saved to the debug queue, and the prompt message indicating that the node has no data is saved to the quality queue; if the query result is not empty, the corresponding fields of each node and the node field values ​​retrieved based on the corresponding fields are concatenated to obtain the node data corresponding to the closed-loop node.

[0075] In practice, the debugging queue, quality queue, overdue queue, and node time queue can be initialized first. Node query configurations are then processed, and field matching is performed in the closed-loop master data based on each node query configuration. If a relevant field is found, the relevant result is returned; otherwise, "The query condition field configuration is incorrect, please check." For example, a closed-loop node may have two node query configurations: Name = name, Gender = sex; after field matching in the closed-loop master data, multiple node query conditions are obtained: Name = Zhang San, Gender = Female.

[0076] After determining all the above node query conditions, combine multiple node query conditions, node corresponding tables, and node corresponding fields to form a query statement. For example, the node corresponding table is Table 1, and the node corresponding fields are executor and execution time. Combining the two node query conditions mentioned above: Name = Zhang San, Gender = Female, the generated second database query statement is "select executor, execution time from table1 where query conditions <name = Zhang San, gender = female>". Then, use this query statement to query data in the database. If the query result is empty, save the query statement from the previous step along with the node name to the debug queue, and save the "No data for node name" message to the quality information. If data is returned, concatenate the node corresponding fields and the values ​​returned by the query (e.g., Operator: Zhang San, Operation Time: 2024-03-19 10:47). Store the operation time and node ID in the node time queue, and update the node name after concatenation.

[0077] Furthermore, the above node array configuration information also includes: quality configuration information; the quality configuration information includes: quality detection field, function index value, comparison type, and comparison value; after obtaining the node data corresponding to the closed node, it also includes:

[0078] From the node data corresponding to the closed-loop node, find the data corresponding to the quality inspection field; obtain the corresponding preset verification function according to the function index value; input the data corresponding to the quality inspection field, the comparison type, and the comparison value into the preset verification function for verification; if the verification result indicates that there is a quality problem, concatenate the node name of the closed-loop node, the quality configuration information, and the inspection result value into a string and insert it into the quality queue.

[0079] In practice, the content of the quality configuration node of the current closed node in the node array (e.g., "Operator|Length|Greater than|5, Operation Time|Time Format|Yes|Yes") is obtained and separated by commas into a quality inspection array. Elements of the quality inspection array are separated by a vertical bar "|". The first field is the quality inspection field, which matches the corresponding field of the node to obtain the inspection value. The second field is the function index value, indicating the preset function to be called. The third field is the comparison type, supporting judgments such as "greater than, less than, not equal to, not empty, yes / no". The fourth field is the comparison value. The corresponding preset function is found based on the function index value (e.g., if the index value is "length", the method for judging length is found; if the index value is "time format", the method for judging time format is found). For example, if the string length is used to determine the string length, the function is called, passing in the inspection value, comparison type, and comparison value. If the function returns true, the node name, quality inspection field, comparison value, and result value are concatenated into a string and inserted into the quality queue.

[0080] Furthermore, the above node array configuration information also includes: overdue configuration information and node connection data; the overdue configuration information includes: overdue verification formula; after obtaining the node data of the closed node, it also includes: obtaining the operation time of the closed node and the operation time of the previous closed node; calculating the time difference between the operation time of the closed node and the operation time of the previous closed node; finding the corresponding connection in the node connection data according to the ID of the closed node and the previous closed node, and updating the label of this connection with the time difference; matching the time difference with the overdue verification formula, and if the condition is not met, inserting the node name, operation time and overdue prompt information into the overdue queue.

[0081] In practice, the content of the overdue configuration nodes of the current closed node in the node array is obtained (e.g., "n>0 && n<20"). The overdue status of the current closed node is checked by comparing the data of the current closed node and the previous node. First, the operation time of the current closed node and the operation time of the previous closed node are obtained. This is done by retrieving the ID of the previous closed node and querying the corresponding operation time in the node time queue according to the closed node ID. Then, the time difference (in minutes) is calculated by subtracting the time of the previous closed node from the current closed node time. Next, based on the IDs of the current and previous closed nodes, the corresponding line is found in the node connection data, and the time difference is updated to the label of this line. The time difference is then matched against the overdue check equation. If the condition is not met, the node name, operation time, and "overdue" information are inserted into the overdue queue.

[0082] Current methods for judging the quality of closed-loop points are relatively simple. This embodiment optimizes the methods for judging quality and overdue status, using logic such as greater than and less than to make quick judgments, and supports judgments for various quality scenarios and flexible overdue status.

[0083] Furthermore, the steps for displaying the closed-loop data detection results on a page include: displaying the closed-loop data detection results in a graphical interface; wherein, the closed-loop node information is displayed in the form of a flowchart, where each process node represents a step, and the lines between process nodes represent the execution order of the process; each process node displays the node name, operator, and operation time; debugging information is displayed in the sidebar or pop-up window of the interface, providing detailed debugging information, including query statements to help users troubleshoot problems and optimize configurations; quality information is displayed in the form of a list or chart, listing the nodes that do not meet the quality inspection standards and their corresponding information.

[0084] In one implementation, closed-loop information, quality information, and debugging information can be displayed through a graphical interface. For example... Figure 2 As shown, the closed-loop node information is displayed in the form of a flowchart, with each node representing a step, and the lines connecting the nodes indicating the execution order. Each node can display relevant information such as node name, operator, and operation time. Quality information can be displayed in the form of a list or chart, listing nodes that do not meet quality inspection standards and their corresponding information, so that users can quickly identify and handle them. Debugging information can be displayed in the sidebar of the interface or in a pop-up window (such as...). Figure 3 As shown, it provides detailed debugging information, such as query statements, to help users troubleshoot problems and optimize configurations.

[0085] The closed-loop data processing method provided in this application first parses and verifies the input closed-loop node configuration data; then, it obtains the patient ID, visit ID, and medical order ID input by the user, parses the closed-loop configuration data, establishes a database connection, and queries the closed-loop data; for each closed-loop node in the node array, it processes the corresponding node query configuration, updates the corresponding fields of the node, and performs quality checks and overdue checks; finally, it assembles the closed-loop node data, debugging information, quality information, and overdue information, and displays them through a graphical interface. This method realizes the functions of parsing, querying, processing, and displaying closed-loop node configuration information to provide an intuitive and clear closed-loop business display effect.

[0086] Based on the above method embodiments, this application also provides a closed-loop data processing device, see [link to relevant documentation]. Figure 4 As shown, the device includes: an information acquisition module 42, used to acquire input patient information; the patient information includes at least one of the following: patient ID, visit ID, or medical order ID; a data search module 44, used to search for closed-loop data corresponding to the patient information from the database based on preset closed-loop node configuration data and the patient information; a node detection module 46, used to detect the node data in the closed-loop data based on the node array configuration information in the closed-loop node configuration data, and obtain the closed-loop data detection result; the closed-loop data detection result includes: closed-loop node information, debugging information, or may also include: quality information and overdue information; and a result display module 48, used to display the closed-loop data detection result on a page.

[0087] Furthermore, the above-mentioned device also includes: a configuration verification module, used to verify the configuration data of the closed-loop point before the step of obtaining the input patient information; if the verification result is qualified, the step of obtaining the input patient information continues; if the verification result is unqualified, a prompt message indicating that the configuration is incorrect is returned.

[0088] Furthermore, the aforementioned configuration verification module is used to sequentially verify the following aspects of the closed-loop node configuration data: determining whether the closed-loop node configuration data conforms to the specified format; determining whether the closed-loop node configuration data simultaneously contains the closed-loop title, closed-loop main table, query condition configuration information, and database connection information; determining whether the length of the node array in the closed-loop node configuration data is greater than 1; determining whether the node array includes: node ID, node name, node corresponding table, node corresponding field, node query configuration, database connection information, overdue configuration information, and quality configuration information; determining whether the node corresponding field and node query configuration meet preset conditions; checking whether the quality configuration information meets the preset format; determining whether each node ID is unique; checking whether the node start ID and node end ID in the node connection are included in the node array; if any of the above verifications fails, the closed-loop node configuration data is deemed unqualified.

[0089] Furthermore, the aforementioned data lookup module 44 is used to look up the closed-loop master table and query condition configuration information from the closed-loop node configuration data; assemble and generate a first database query statement based on the closed-loop master table, query condition configuration information, and patient information; and look up the closed-loop data corresponding to the patient information from the database based on the first database query statement.

[0090] Furthermore, the above-mentioned node array configuration information includes: multiple query condition configurations corresponding to each closed loop node; the node detection module 46 is used to perform the following steps for each closed loop node in the closed loop node configuration data: based on the multiple query condition configurations corresponding to the closed loop node, perform node field matching one by one in the closed loop data to obtain multiple node query conditions corresponding to the closed loop node; combine the multiple node query conditions, the node correspondence table of the closed loop node, and the node corresponding fields to form a second database query statement; query the corresponding data in the database through the second database query statement; if the query result is empty, save the second database query statement and the corresponding node name to the debug queue, and save the prompt message indicating that the node has no data to the quality queue; if the query result is not empty, concatenate each node corresponding field and the node field value queried based on the node corresponding field to obtain the node data corresponding to the closed loop node.

[0091] Furthermore, the above node array configuration information also includes: quality configuration information; the quality configuration information includes: quality detection field, function index value, comparison type, and comparison value; the node detection module 46 is used to find the data corresponding to the quality detection field from the node data corresponding to the closed node; obtain the corresponding preset verification function according to the function index value; input the data corresponding to the quality detection field, comparison type, and comparison value into the preset verification function for verification; if the verification result is that there is a quality problem, the node name of the closed node, the quality configuration information, and the inspection result value are concatenated into a string and inserted into the quality queue.

[0092] Furthermore, the above node array configuration information also includes: overdue configuration information and node connection data; the overdue configuration information includes: overdue verification formula; the node detection module 46 is used to obtain the operation time of the closed node and the operation time of the previous closed node; calculate the time difference between the operation time of the closed node and the operation time of the previous closed node; find the corresponding connection in the node connection data according to the ID of the closed node and the previous closed node, and update the label of this connection with the time difference; match the time difference with the overdue verification formula, and if the condition is not met, insert the node name, operation time and overdue prompt information into the overdue queue.

[0093] Furthermore, the aforementioned result display module 48 is used to display the closed-loop data detection results in a graphical interface. The closed-loop node information is displayed in the form of a flowchart, where each node represents a step, and the lines connecting the nodes indicate the execution order. Each node displays its name, operator, and operation time. Debugging information is displayed in the sidebar or pop-up window of the interface, providing detailed debugging information, including query statements, to help users troubleshoot problems and optimize configurations. Quality information is displayed in the form of a list or chart, listing nodes that do not meet quality inspection standards and their corresponding information.

[0094] The device provided in this application embodiment has the same implementation principle and technical effect as the aforementioned method embodiment. For the sake of brevity, any parts of the device embodiment not mentioned can be referred to the corresponding content in the aforementioned method embodiment.

[0095] This application also provides an electronic device, such as... Figure 5 The diagram shows the structure of the electronic device, which includes a processor 51 and a memory 50. The memory 50 stores computer-executable instructions that can be executed by the processor 51, and the processor 51 executes the computer-executable instructions to implement the above-described method.

[0096] exist Figure 5 In the illustrated embodiment, the electronic device further includes a bus 52 and a communication interface 53, wherein the processor 51, the communication interface 53, and the memory 50 are connected via the bus 52.

[0097] The memory 50 may include high-speed random access memory (RAM) or non-volatile memory, such as at least one disk storage device. Communication between this system network element and at least one other network element is achieved through at least one communication interface 53 (which can be wired or wireless), such as the Internet, wide area network, local area network, metropolitan area network, etc. The bus 52 may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus 52 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 The symbol is represented by a single double-headed arrow, but this does not mean that there is only one bus or one type of bus.

[0098] The processor 51 may be an integrated circuit chip with signal processing capabilities. In implementation, each step of the above method can be completed by the integrated logic circuitry in the hardware of the processor 51 or by instructions in software form. The processor 51 may be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc.; it may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The general-purpose processor may be a microprocessor or any conventional processor. The steps of the method disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules may reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in the memory, and the processor 51 reads the information in the memory and, in conjunction with its hardware, completes the steps of the method described in the foregoing embodiment.

[0099] This application also provides a computer-readable storage medium storing computer-executable instructions. When the computer-executable instructions are called and executed by a processor, the computer-executable instructions cause the processor to implement the above-described method. For specific implementation details, please refer to the foregoing method embodiments, which will not be repeated here.

[0100] The computer program products of the methods, apparatus, and electronic devices provided in the embodiments of this application include a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the methods described in the preceding method embodiments. For specific implementations, please refer to the method embodiments, which will not be repeated here.

[0101] Unless otherwise specifically stated, the relative steps, numerical expressions, and values ​​of the components and steps described in these embodiments do not limit the scope of this application.

[0102] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0103] In the description of this application, it should be noted that the terms "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0104] Finally, it should be noted that the above-described embodiments are merely specific implementations of this application, used to illustrate the technical solutions of this application, and not to limit them. The protection scope of this application is not limited thereto. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the technical scope disclosed in this application. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be covered within the protection scope of this application. Therefore, the protection scope of this application should be determined by the protection scope of the claims.

Claims

1. A closed-loop data processing method, characterized in that, The method includes: Obtain the input patient information; the patient information includes at least one of the following: patient ID, visit ID, or medical order ID; Based on preset closed-loop node configuration data and the patient information, the closed-loop data corresponding to the patient information is retrieved from the database, including: retrieving the closed-loop master table and query condition configuration from the closed-loop node configuration data; assembling and generating a first database query statement based on the closed-loop master table, the query condition configuration, and the patient information; and retrieving the closed-loop data corresponding to the patient information from the database based on the first database query statement. Based on the node array configuration information in the closed-loop node configuration data, the node data in the closed-loop data is detected to obtain the closed-loop data detection result; the closed-loop data detection result includes: closed-loop node information, debugging information, or may also include: quality information and overdue information; The closed-loop data detection results are displayed on the page. The node array configuration information includes: multiple query condition configurations corresponding to each closed loop node; the step of detecting node data in the closed loop data based on the node array configuration information in the closed loop node configuration data to obtain the closed loop data detection result includes: for each closed loop node in the closed loop node configuration data, performing the following steps: based on the multiple query condition configurations corresponding to the closed loop node, matching node fields one by one in the closed loop data to obtain multiple node query conditions corresponding to the closed loop node; combining the multiple node query conditions, the node correspondence table of the closed loop node, and the node correspondence fields to form a second database query statement; querying the corresponding data in the database using the second database query statement; if the query result is empty, saving the second database query statement and the corresponding node name to the debug queue, and saving the prompt message indicating that the node has no data to the quality queue; if the query result is not empty, concatenating each node correspondence field and the node field value queried based on the node correspondence field to obtain the node data corresponding to the closed loop node.

2. The method according to claim 1, characterized in that, Before the step of obtaining the input patient information, the following steps are also included: The configuration data of the closed loop point is verified; If the verification result is satisfactory, continue to the step of obtaining the input patient information; If the verification result is unqualified, a message indicating a configuration error will be returned.

3. The method according to claim 2, characterized in that, The steps for verifying the closed-loop node configuration data include: The closed-loop configuration data shall be validated in at least one of the following aspects: Determine whether the closed-loop configuration data is in the specified format. Determine whether the closed loop configuration data simultaneously contains the closed loop title, the closed loop main table, query condition configuration information, and database connection information. Determine whether the length of the node array of the closed-loop node configuration data is greater than 1; Determine whether the node array includes: node ID, node name, node corresponding table, node corresponding field, node query configuration, database connection information, overdue configuration information, and quality configuration information; Determine whether the fields corresponding to the node and the node query configuration meet preset conditions; Check whether the quality configuration information meets the preset format; Determine whether each node ID is unique; Check if the start ID and end ID of the nodes in the node connection are included in the node array; If any one of the above verifications fails, the closed-loop node configuration data verification is deemed unqualified.

4. The method according to claim 1, characterized in that, The node array configuration information also includes: quality configuration information; the quality configuration information includes: quality detection field, function index value, comparison type, and comparison value; after obtaining the node data corresponding to the closed node, the method further includes: From the node data corresponding to the closed node, find the data corresponding to the quality detection field; obtain the corresponding preset verification function according to the function index value; input the data corresponding to the quality detection field, the comparison type, and the comparison value into the preset verification function for verification; if the verification result indicates that there is a quality problem, concatenate the node name of the closed node, the quality configuration information, and the inspection result value into a string and insert it into the quality queue.

5. The method according to claim 1, characterized in that, The node array configuration information also includes: overdue configuration information and node connection data; the overdue configuration information includes: overdue verification formula; after obtaining the node data corresponding to the closed node, the method further includes: Obtain the operation time of the closed node and the operation time of the previous closed node; Calculate the time difference between the operation time of the closed node and the operation time of the previous closed node; Based on the IDs of the closed node and the previous closed node, find the corresponding connection in the node connection data and update the time difference to the label of this connection. The time difference is matched with the overdue verification formula. If the condition is not met, the node name, operation time and overdue prompt information are inserted into the overdue queue.

6. The method according to claim 1, characterized in that, The steps for displaying the closed-loop data detection results on a webpage include: The closed-loop data detection results are displayed in a graphical interface; the closed-loop node information is displayed in the form of a flowchart, where each process node represents a step, and the lines between process nodes represent the execution order of the process; each process node displays the node name, operator, and operation time. The debugging information is displayed in the sidebar or pop-up window of the interface, providing detailed debugging information, including query statements, to help users troubleshoot problems and optimize configurations; The quality information is displayed in the form of a list or chart, listing the nodes that do not meet the quality inspection standards and their corresponding information.

7. A closed-loop data processing device, characterized in that, The device includes: The information acquisition module is used to acquire input patient information; the patient information includes at least one of the following: patient ID, visit ID, and medical order ID; The data lookup module is used to search for closed-loop data corresponding to the patient information in the database based on preset closed-loop node configuration data and the patient information. The module includes: searching for a closed-loop master table and query condition configuration from the closed-loop node configuration data; assembling and generating a first database query statement based on the closed-loop master table, the query condition configuration, and the patient information; and searching for the closed-loop data corresponding to the patient information in the database based on the first database query statement. The node detection module is used to detect the node data in the closed-loop data based on the node array configuration information in the closed-loop node configuration data, and obtain the closed-loop data detection result; the closed-loop data detection result includes: closed-loop node information, debugging information, or may also include: quality information and overdue information; The results display module is used to display the closed-loop data detection results on a webpage. The node array configuration information includes: multiple query condition configurations corresponding to each closed loop node; the node detection module is further configured to perform the following steps for each closed loop node in the closed loop node configuration data: based on the multiple query condition configurations corresponding to the closed loop node, perform node field matching one by one in the closed loop data to obtain multiple node query conditions corresponding to the closed loop node; combine the multiple node query conditions, the node correspondence table of the closed loop node, and the node corresponding fields to form a second database query statement; query the corresponding data in the database using the second database query statement; if the query result is empty, save the second database query statement and the corresponding node name to the debug queue, and save the prompt message indicating that the node has no data to the quality queue; if the query result is not empty, concatenate each node corresponding field and the node field value queried based on the node corresponding field to obtain the node data corresponding to the closed loop node.

8. An electronic device, characterized in that, The method includes a processor and a memory, the memory storing computer-executable instructions executable by the processor, the processor executing the computer-executable instructions to implement the method of any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when invoked and executed by a processor, cause the processor to perform the method according to any one of claims 1 to 6.

Images