Hospital instant test result reliable publishing control method and system based on quality element atlas

Abstract

This application relates to the field of information processing technology, and in particular to a method and system for reliable release control of hospital point-of-care test results based on a quality element map. The method constructs a point-of-care test quality element map by organizing multi-source quality data scattered throughout the hospital's point-of-care testing process according to quality elements and their relationships. A corresponding task-level quality sub-map is formed when a specific testing task is triggered. The testing access status is determined based on the task-level quality sub-map, and the task-level quality sub-map is dynamically updated after testing is completed, incorporating newly generated quality events. This further determines the reliability of the test results and generates corresponding report release control strategies, thereby improving the accuracy, reliability, and security of hospital point-of-care test result release.

Description

Technical Field

[0001] This application relates to the field of information processing technology, and in particular to a method and system for reliable release control of real-time test results in hospitals based on quality element maps. Background Technology

[0002] Point-of-care testing (POCT) has been widely adopted in emergency departments, ICUs, respiratory departments, endocrinology departments, oncology departments, cardiology departments, nephrology departments, obstetrics and gynecology departments, primary healthcare institutions, and large hospitals with multiple campuses due to its advantages such as fast testing speed, proximity to patients, and ability to assist in rapid clinical decision-making. Unlike traditional central laboratory testing, POCT testing equipment is typically distributed across multiple clinical departments, and the operators come from diverse backgrounds, including laboratory personnel, doctors, nurses, and trained clinical staff. Furthermore, there are significant differences in equipment brands, models, testing principles, test items, reagent batch numbers, quality control batch numbers, reporting procedures, and departmental usage habits. Therefore, while POCT improves clinical testing efficiency, existing hospital POCT management suffers from high information bias. This bias does not affect the automatic review and publication strategies for subsequent tests performed on the same equipment, resulting in lower reliability. Summary of the Invention

[0003] Therefore, it is necessary to provide a reliable release control method and system for real-time hospital test results based on quality element maps to address the above-mentioned technical problems.

[0004] In a first aspect, this application provides a method for controlling the reliable release of hospital real-time test results based on quality element maps, the method comprising: Acquire multi-source quality data during the hospital's point-of-care testing process, and construct a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between the quality elements. In response to the triggering of the target immediate inspection task, quality elements related to the target immediate inspection task are extracted from the immediate inspection quality element map to form a task-level quality sub-map, and the detection access status of the target immediate inspection task is determined according to the status of each quality element in the task-level quality sub-map. The execution of the target real-time inspection task and the detection results after the execution of the target real-time inspection task are controlled according to the detection admission status. After obtaining the detection results, the task-level quality subgraph is updated according to the quality events corresponding to the target instant inspection task, and the result credibility of the detection results is determined according to the updated task-level quality subgraph. A report release control strategy is then generated based on the result credibility.

[0005] In one example, the acquisition of multi-source quality data during the hospital's point-of-care testing process, and the construction of a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlations between these quality elements, includes: The multi-source quality data is obtained from multiple data sources related to the hospital's point-of-care testing process, and the multi-source quality data is standardized to obtain point-of-care testing events that characterize changes in the state of quality elements. Based on the quality objects associated with each of the immediate inspection events, the corresponding quality elements are determined, and based on the business associations and quality dependencies of different quality objects in the immediate inspection process, the association relationships between the quality elements are determined. The real-time inspection quality element map is constructed based on each of the quality elements, the state of each of the quality elements, and the correlation between each of the quality elements.

[0006] In one example, in response to the triggering of a target immediate inspection task, quality elements related to the target immediate inspection task are extracted from the immediate inspection quality element map to form a task-level quality sub-map. Based on the state of each quality element in the task-level quality sub-map, the detection admission status of the target immediate inspection task is determined, including: Based on the task attributes of the target real-time inspection task, determine the target quality objects participating in the target real-time inspection task; Extract the target quality element nodes corresponding to each of the target quality objects from the real-time inspection quality element graph, and the target quality association edges connecting each of the target quality element nodes to form the task-level quality subgraph; Based on the fusion result of the state of each target quality element node and the association weight of each target quality associated edge in the task-level quality subgraph, the detection execution conditions of the target real-time inspection task are evaluated to obtain the detection admission evaluation result. The detection access status of the target real-time inspection task is determined based on the detection access evaluation results.

[0007] In one example, controlling the execution of the target immediate verification task and the detection result after executing the target immediate verification task based on the detection admission state includes: Generate a corresponding access control identifier based on the detected access status; The access control identifier is sent to the data interface connected to the instant inspection device or report processing system; Based on the access control identifier, the target instant verification task is controlled to enter the allowed execution state, conditional execution state, or restricted execution state; When the target real-time inspection task enters the allowed execution state or the conditional execution state, the detection result obtained by executing the target real-time inspection task is acquired; when the target real-time inspection task enters the restricted execution state and the detection result has been generated, the detection result is restricted from entering the formal report processing flow.

[0008] In one example, updating the task-level quality subgraph based on the quality events corresponding to the target real-time inspection task, and determining the result confidence of the detection result based on the updated task-level quality subgraph, includes: Based on the task identifier and quality context corresponding to the detection result, obtain the associated quality events generated during and after the execution of the target instant inspection task from the instant inspection quality element map; Determine the quality elements corresponding to each of the associated quality events, and establish the correlation between the detection results and the corresponding quality elements; Update the state of the corresponding quality element in the task-level quality subgraph based on the quality state changes represented by each of the associated quality events. Based on the updated status of each quality element and its correlation with the test results, the quality impact of each quality element on the test results is determined. Then, in conjunction with the test access status of the target real-time inspection task, the quality impacts are fused to obtain the result reliability of the test results.

[0009] In one example, a report release control strategy is generated based on the credibility of the results, including: The credibility of the results is matched with preset release conditions to determine the report release level corresponding to the detection results; Based on the report release level, determine the target flow status of the test results in the report processing flow, and generate a report release control instruction corresponding to the target flow status; The report release control command is sent to the interface gateway connected to the target reporting system, so that the interface gateway writes the detection result into the data processing path corresponding to the target flow status according to the report release control command; Record the result credibility, target flow status, and execution status of the report release control instructions corresponding to the detection results to form the report release control record of the detection results.

[0010] In one example, the method further includes: The target data processing path corresponding to the detection result is determined according to the report release control strategy, and the detection result is controlled to enter the target data processing path through the interface gateway. The policy execution status returned by the interface gateway in response to the detection result is obtained, and the policy execution status is associated with and stored with the detection result, so as to determine the actual flow status of the detection result in the report processing flow based on the policy execution status.

[0011] Secondly, the present invention also provides a reliable release control system for real-time hospital test results based on quality element maps, the system comprising: The map construction module is used to acquire multi-source quality data in the hospital's point-of-care testing process, and construct a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between the quality elements. The detection access status determination module is used to extract quality elements related to the target immediate inspection task from the immediate inspection quality element map in response to the triggering of the target immediate inspection task, form a task-level quality sub-map, and determine the detection access status of the target immediate inspection task according to the status of each quality element in the task-level quality sub-map. The detection result determination module is used to control the execution of the target real-time inspection task and the detection result after executing the target real-time inspection task according to the detection admission status; The release control module is used to update the task-level quality subgraph according to the quality event corresponding to the target instant inspection task after obtaining the detection result, determine the result credibility of the detection result according to the updated task-level quality subgraph, and generate a report release control strategy according to the result credibility.

[0012] Thirdly, this application provides a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method provided in the first aspect of this application.

[0013] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method provided in the first aspect of this application.

[0014] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the method provided in the first aspect of this application.

[0015] The aforementioned method and system for reliable release control of hospital point-of-care test results based on quality element mapping constructs a quality element map of point-of-care testing according to quality elements and their relationships, based on the multi-source quality data scattered during the hospital's point-of-care testing process. When a specific testing task is triggered, a corresponding task-level quality sub-map is generated, enabling the correlation and evaluation of personnel, equipment, reagents, consumables, quality control status, and other relevant quality conditions around a single testing task. Based on this, the testing access status is determined according to the task-level quality sub-map, allowing for pre-control of the execution of testing tasks and the flow of test results. After testing, the task-level quality sub-map is dynamically updated based on newly generated quality events, further determining the reliability of the test results and generating corresponding report release control strategies. Thus, previously scattered quality information used only for post-event statistics or anomaly alerts is transformed into a continuous control basis throughout the pre-test access, testing process status updates, and post-test report release. This ensures that quality deviations such as equipment quality control anomalies, personnel or reagent status anomalies can promptly affect the review and release of corresponding test results, preventing test results that do not meet quality requirements from being directly included in the formal reporting process, thereby improving the accuracy, reliability, and security of hospital point-of-care test result release. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating the steps of a hospital real-time test result reliability control method based on quality element map in one embodiment. Figure 2 This is a block diagram of a hospital real-time test result reliable release control system based on quality element map in one embodiment. Detailed Implementation

[0017] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the specific embodiments of this application are described in detail below with reference to the accompanying drawings. Many specific details are set forth in the following description to provide a thorough understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar modifications without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.

[0018] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0019] In this application, unless otherwise expressly specified and limited, the terms "connected" and "linked" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms in this application based on the specific circumstances.

[0020] It should be noted that when one element is considered to be "connected" to another element, it can be directly connected to the other element or connected to the other element through an intermediary element. Furthermore, in the following embodiments, "connection" should be understood as "electrical connection," "communication connection," etc., if there is transmission of electrical signals or data between the connected objects.

[0021] Point-of-care testing (POCT) has been widely adopted in emergency departments, ICUs, respiratory departments, endocrinology departments, oncology departments, cardiology departments, nephrology departments, obstetrics and gynecology departments, primary healthcare institutions, and large hospitals with multiple campuses due to its advantages such as rapid testing speed, proximity to patients, and ability to support rapid clinical decision-making. Unlike traditional central laboratory testing, POCT testing equipment is typically distributed across multiple clinical departments, and the operators come from diverse backgrounds, including laboratory personnel, doctors, nurses, and trained clinical staff. Furthermore, there are significant differences in equipment brands, models, testing principles, test items, reagent batch numbers, quality control batch numbers, reporting procedures, and departmental usage habits. Therefore, while POCT improves clinical testing efficiency, it also introduces considerable complexity to hospital quality management.

[0022] Because POCT devices are typically distributed across multiple departments, the same test may be performed by devices of different brands, models, and based on different testing principles, and operated by personnel with varying professional backgrounds and training. Therefore, the quality of a single point-of-care testing task cannot be determined solely by the test result itself. For example, even if a blood glucose test result is within the normal range, if it is performed by an authorized person using an expired calibration device and test strips with batch drift risk, the result may still be unsuitable for direct inclusion in the formal reporting process. Furthermore, there is a persistent information bias that does not immediately affect the automatic review and publication strategy for subsequent tests performed on the same device.

[0023] It should be noted that "point-of-care testing" in this application refers to the process of performing tests on patient samples and obtaining test results using point-of-care testing equipment outside of a central laboratory or close to the patient's treatment location. The testing location for point-of-care testing can be the emergency department, intensive care unit, endocrinology department, cardiology department, operating room, ward, outpatient department, primary care facility, or other testing sites within a hospital.

[0024] This application's embodiments relate to a method for controlling the reliable release of hospital real-time test results based on quality element maps, such as... Figure 1 As shown, the method includes the following steps S102 to S108. Wherein: S102. Obtain multi-source quality data from the hospital's point-of-care testing process, and construct a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between each quality element.

[0025] Multi-source quality data refers to data generated by different business systems, testing equipment, or management processes, which can be used to evaluate whether point-of-care testing tasks meet the quality requirements for testing and report issuance. Multi-source quality data includes not only test values, but also information such as the personnel involved in generating the test values, equipment serial number, reagent batch, quality control batch, standard operating procedure version, sample status, testing time, department, equipment calibration status, equipment maintenance status, quality control status, intra-hospital comparison status, inter-laboratory quality assessment status, historical anomaly status, and report interface status.

[0026] Quality elements refer to objects or states that can affect the execution conditions of point-of-care testing tasks, the accuracy of test results, or the reliability of test result publication. Quality elements can be entities such as personnel, equipment, reagents and consumables, testing items, standard operating procedures, samples, quality control activities, intra-institutional comparison activities, inter-laboratory quality assessment activities, test results, reporting interfaces, and anomaly handling tasks, or the authorization status, validity status, adaptation status, risk status, or circulation status corresponding to the above entities.

[0027] The relationships between various quality elements refer to the business connections that exist between different quality elements. Examples include the authorized operation relationship between personnel and testing items, the compatibility relationship between equipment and reagents, the attribution relationship between calibration activities and corresponding equipment, the binding relationship between quality control activities and corresponding testing items, the attribution relationship between test results and corresponding testing tasks, and the flow relationship between reporting interfaces and corresponding testing items. When constructing a quality element map for point-of-care testing, each quality element is mapped to a node in the map, and the relationships between different quality elements are mapped to edges connecting the corresponding nodes. Weights can be assigned to each edge based on the degree of impact of the relationship on testing quality, ultimately resulting in a complete quality element map covering the entire process of all point-of-care testing services in the hospital.

[0028] S104. In response to the triggering of the target immediate inspection task, extract the quality elements related to the target immediate inspection task from the immediate inspection quality element map to form a task-level quality sub-map, and determine the inspection access status of the target immediate inspection task based on the status of each quality element in the task-level quality sub-map.

[0029] Among them, a target point-of-care testing task refers to a task that performs a target test on a target patient or target sample. The task attributes of a target point-of-care testing task may include task identifier, patient identifier, sample identifier, test item, target equipment, target operator, department, reagent batch number to be used, planned execution time, and clinical urgency.

[0030] After obtaining the target immediate inspection task, the target quality objects participating in the target immediate inspection task are determined according to the task attributes. Then, the quality element nodes corresponding to the target quality objects are used as the starting nodes. The associated nodes and edges are extracted in the immediate inspection quality element graph according to the preset association level to form a task-level quality subgraph. This eliminates the need to traverse all quality elements, effectively reducing the amount of data in a single calculation and improving processing efficiency.

[0031] S106. Control the execution of the immediate inspection task of the target based on the detection access status and the detection results after the execution of the immediate inspection task of the target.

[0032] Among them, an access control identifier is generated based on the testing access status. The access control identifier can correspond one-to-one with the testing access status, or it can further carry the reason for restriction, applicable equipment, applicable testing items, validity period, and result flow requirements on the basis of the testing access status.

[0033] When the access status is set to "permitted," a permissive access control flag can be generated. Upon receiving the permissive access control flag, the on-the-spot inspection equipment or report processing system allows the target on-the-spot inspection task to execute normally and allows the inspection results to enter the subsequent reliability evaluation process.

[0034] S108. After obtaining the test results, update the task-level quality subgraph according to the quality events corresponding to the target instant inspection task, determine the result credibility of the test results according to the updated task-level quality subgraph, and generate a report and release control strategy based on the result credibility.

[0035] A quality event is a data event that can lead to the establishment, alteration, confirmation, or invalidation of the status of one or more quality elements. For example, personnel passing the assessment for a testing item can form an authorization effective event; personnel authorization exceeding the validity period can form an authorization expired event; equipment completing calibration can form a calibration completed event; equipment failure can form an equipment failure event; quality control results exceeding control limits can form a quality control anomaly event; and the generation of new internal comparison results can form a comparison status update event.

[0036] Report release control strategies refer to control information determined based on the credibility of the results, used to control how test results flow in the report processing workflow. The report processing workflow may include processing paths such as formal release, release after adding risk labels, manual review, delayed release, entry into the isolation zone, and restriction of writing to the formal reporting system.

[0037] Specifically, the test results may include information such as the test value, testing unit, reference range, test time, equipment number, operator number, reagent batch number, quality control batch number, sample number, and result label. After the test results are generated, they can be associated with personnel nodes, equipment nodes, reagent and consumable nodes, test item nodes, sample nodes, and quality control nodes in the task-level quality subgraph based on the corresponding task identifier and quality context.

[0038] Quality events corresponding to the target real-time testing task include events that occur during task execution and after task completion. For example, equipment malfunction events during testing, quality control events after testing, reagent batch status change events, sample anomaly events, new intra-hospital comparison events, and report interface anomaly events.

[0039] Update the status of the corresponding node in the task-level quality subgraph based on quality events. If a new quality control event indicates a trend deviation in the equipment, update the risk of the equipment node and the quality control node; if a new intra-hospital comparison event indicates a unidirectional deviation of the same reagent batch on multiple devices, update the risk of the reagent and consumables node; if a sample status event indicates that the sampling to testing time exceeds the allowable range, update the status of the sample node.

[0040] Result reliability does not represent the statistical probability of a test value, nor is it directly equivalent to whether a test result exceeds the reference range. Rather, it characterizes the comprehensive reliability of a test result in meeting publication criteria within the current quality context, including personnel, equipment, reagents, standard operating procedures, quality control, intra-institutional comparisons, inter-laboratory quality assessments, sample data, and historical anomalies. Result reliability reflects both the quality conditions before the testing task begins and the dynamic quality changes during and after the testing process, avoiding decisions on publication solely based on whether a test value exceeds the reference range.

[0041] The aforementioned method for reliable release control of hospital point-of-care test results based on quality element mapping constructs a quality element map of point-of-care testing by organizing multi-source quality data scattered throughout the hospital's point-of-care testing process according to quality elements and their relationships. When a specific testing task is triggered, a corresponding task-level quality sub-map is generated, enabling the correlation and evaluation of personnel, equipment, reagents, consumables, quality control status, and other relevant quality conditions around a single testing task. Based on this, the testing access status is determined according to the task-level quality sub-map, allowing for pre-control of the execution of testing tasks and the flow of test results. After testing, the task-level quality sub-map is dynamically updated based on newly generated quality events, further determining the reliability of the test results and generating corresponding report release control strategies. This transforms previously scattered quality information, used only for post-event statistics or anomaly alerts, into a continuous control basis throughout the pre-test access, testing process status updates, and post-test report release. This ensures that quality deviations such as equipment quality control anomalies, personnel or reagent status anomalies, can promptly affect the review and release of corresponding test results, preventing test results that do not meet quality requirements from being directly included in the formal reporting process, thereby improving the accuracy, reliability, and security of hospital point-of-care test result release.

[0042] In one exemplary embodiment, multi-source quality data from the hospital's point-of-care testing process is acquired, and a point-of-care testing quality element map is constructed based on the quality elements represented by the multi-source quality data and the relationships between the quality elements. This includes: acquiring multi-source quality data from multiple data sources related to the hospital's point-of-care testing process, standardizing the multi-source quality data to obtain point-of-care testing events that characterize changes in the state of quality elements; determining the corresponding quality elements based on the quality objects associated with each point-of-care testing event, and determining the relationships between the quality elements based on the business associations and quality dependencies of different quality objects in the point-of-care testing process; and constructing a point-of-care testing quality element map based on each quality element, the state of each quality element, and the relationships between the quality elements.

[0043] Specifically, at least two data sources can be accessed through a unified interface gateway, including point-of-care testing equipment, laboratory information systems, hospital information systems, electronic medical record systems, personnel management systems, equipment management systems, reagent and consumable management systems, standard operating procedure management systems, internal quality control systems, intra-hospital comparison systems, inter-laboratory quality assessment systems, and report publishing systems.

[0044] Data fields, object numbers, time formats, data units, and status codes may differ across different data sources. For example, the same device might be identified by its device serial number in the data uploaded from a point-of-care testing device, but by its hospital asset number in the device management system; similarly, a person might be identified by their employee ID in a personnel management system, but by their operation card number in a device. Therefore, it is necessary to establish an object identifier mapping relationship to map data from different data sources pointing to the same quality object to a unified quality object identifier.

[0045] Standardizing multi-source quality data can include at least field standardization, code standardization, unit standardization, time standardization, and object association standardization.

[0046] Field standardization refers to converting data from different data sources that have the same meaning but different field names into a unified field. For example, "equipment serial number," "instrument number," and "asset number" can be uniformly mapped to the equipment identifier field.

[0047] Coding standardization refers to converting the status codes of different systems into a unified state. For example, if different systems use "0", "normal", and "OK" to represent a device being normal, they can be uniformly mapped to the normal device state.

[0048] Unit standardization refers to converting test values ​​or quality control values ​​that use different units of measurement. For example, it involves uniformly converting the units of mass concentration to the platform's preset units to avoid erroneous judgments due to inconsistent units for the same test item.

[0049] Time standardization refers to converting the device's local time, server time, and system recorded time to a unified time base, and determining the actual occurrence time of the event and the platform's receiving time based on the upload delay.

[0050] Object association standardization refers to establishing cross-system object mappings using equipment serial numbers, asset numbers, employee numbers, operation card numbers, reagent batch numbers, quality control batch numbers, and sample numbers.

[0051] Through the above standardization process, data from different sources can be written into the graph with a unified event structure, and information of the same quality object in different data sources can be aggregated to the same quality element node, avoiding duplicate nodes or incorrect associations in the graph due to inconsistent object identification.

[0052] Each standardized data point can be represented as an immediate verification event:

[0053] in, Indicates the first An event identifier for an instant verification event; Indicates the event type; Represents the quality object associated with the event; Indicates the time when the event occurred or the time when the data was generated; Indicate the source of the event; Indicates the event value or event status; Indicates the event context; Indicates the credibility of an event.

[0054] Event context can include information such as department, test item, equipment number, operator number, reagent batch number, quality control batch number, sample number, test time, and network status. By preserving event context, it is possible to avoid treating equipment status, personnel status, or quality control status as static data unrelated to the specific testing task.

[0055] The credibility of an event can be represented as follows:

[0056] in, Indicates the authority of the data source; Indicates the timeliness of the data; Indicates the completeness of the field; Indicates the degree of standardization; Indicates the degree of consistency with other data sources; to For the corresponding weights, the following condition must be met:

[0057] For example, the online status of the device uploaded in real time through the device's direct connection interface has high timeliness; the calibration records in the device management system have high authority; and the credibility of manually entered data may be reduced due to possible entry delays or missing fields.

[0058] When different data sources provide inconsistent statuses for the same quality object, a primary status can be selected based on the event's credibility, and a data conflict event can be generated simultaneously. For example, if the device interface shows the device is available, but the device management system shows the device calibration validity period has expired, the online status of the device cannot simply replace the calibration status. Instead, the device status should be determined as "conflict exists" or "pending confirmation," and this conflicting status should be included in subsequent testing access evaluations.

[0059] The quality element diagram of immediate inspection can be represented as follows:

[0060] in, Represents the set of quality element nodes; Represents the set of quality-related edges; This represents the set of association weights corresponding to quality-related edges; This represents the set of status information for each quality element node.

[0061] Quality element nodes can include personnel nodes, equipment nodes, reagent and consumable nodes, testing item nodes, standard operating procedure nodes, sample nodes, quality control nodes, intra-institutional comparison nodes, inter-laboratory quality assessment nodes, test result nodes, report nodes, interface nodes, and anomaly handling task nodes.

[0062] Quality-related edges are used to characterize the quality dependencies between different quality elements. For example, an equipment operation authorization edge can be established between personnel nodes and equipment nodes; a project authorization edge can be established between personnel nodes and testing project nodes; a project adaptation edge can be established between equipment nodes and testing project nodes; a reagent adaptation edge can be established between equipment nodes and reagent / consumable nodes; a procedure application edge can be established between testing project nodes and standard operating procedure nodes; a result flow edge can be established between testing result nodes and report nodes; and a report writing edge can be established between report nodes and interface nodes.

[0063] Association weights can be represented as follows:

[0064] in, Represents quality element nodes With quality element nodes The correlation weight between them; Indicates the strength of institutional constraints corresponding to quality relationships; Indicates the degree of reliance in the immediate inspection process; Indicates the degree of correlation in historical anomalies; Indicates the timeliness of the corresponding relationship; to These are the weight parameters.

[0065] The state of each quality element node can be represented as:

[0066] in, Indicates the node status category, such as normal, abnormal, expired, conflicted, pending confirmation, or disabled; Indicates the node risk value; Indicates the node status update time; This indicates the reliability of the node's state.

[0067] The real-time inspection quality element map constructed in the above manner not only records the quality objects, but also the real-time status of the quality objects and the influence relationship between different quality objects, thus providing a data foundation for extracting task-level quality sub-maps according to the target real-time inspection task.

[0068] In an exemplary embodiment, in response to the triggering of a target immediate inspection task, quality elements related to the target immediate inspection task are extracted from the immediate inspection quality element graph to form a task-level quality subgraph. Based on the state of each quality element in the task-level quality subgraph, the detection admission status of the target immediate inspection task is determined. This includes: determining the target quality objects participating in the target immediate inspection task based on the task attributes of the target immediate inspection task; extracting target quality element nodes corresponding to each target quality object and target quality association edges connecting each target quality element node from the immediate inspection quality element graph to form a task-level quality subgraph; evaluating the detection execution conditions of the target immediate inspection task based on the fusion result of the state of each target quality element node and the association weight of each target quality association edge in the task-level quality subgraph to obtain a detection admission evaluation result; and determining the detection admission status of the target immediate inspection task based on the detection admission evaluation result.

[0069] The task attributes of the target point-of-care testing task may include task identifier, patient identifier, sample identifier, test item, target equipment, target operator, department, reagent batch number to be used, planned execution time, and clinical urgency.

[0070] Task attributes are used to determine which quality objects are involved in the target point-of-care testing task. Task attributes can include at least the testing items, equipment, operator, department, and task time; when the relevant data is available, they can also include reagent batch number, quality control batch number, sample type, and reporting interface.

[0071] After obtaining the target immediate inspection task, the target quality objects participating in the target immediate inspection task are determined according to the task attributes. Then, taking the quality element node corresponding to the target quality object as the starting node, the associated nodes and edges are extracted in the immediate inspection quality element graph according to the preset association hierarchy to form a task-level quality subgraph:

[0072] in, This indicates that the target needs to be verified immediately. This represents the set of quality element nodes related to the task. This represents the set of quality-related edges connecting the nodes of each relevant quality element.

[0073] For example, for the task of nurse A using blood glucose meter D1 and test strip batch number R1 to perform blood glucose testing on patient sample S1, the task-level quality subgraph can include the personnel node corresponding to nurse A, the equipment node corresponding to blood glucose meter D1, the reagent node corresponding to test strip batch number R1, the blood glucose item node, the applicable standard operating procedure node, the most recent quality control node, the most recent intra-hospital comparison node, the inter-laboratory quality assessment node, the sample node corresponding to sample S1, and the target report interface node.

[0074] Inspection access status indicates whether a target immediate inspection task meets the execution requirements under current quality conditions. Inspection access status can be determined based on personnel authorization, equipment availability, reagent and consumable validity, standard operating procedure validity, recent quality control status, data consistency status, and unresolved historical anomalies.

[0075] The pre-test quality threshold can be represented as follows:

[0076]

[0077] in, This indicates the pre-test quality threshold for the target immediate inspection task; This represents the overall admission score obtained by combining various quality evaluation items and penalty items. Represents the Sigmoid function; Indicates the score for personnel authorization; Indicates the equipment availability score; Indicates the score for reagents and consumables; Indicates the score for a valid standard operating procedure; This indicates the most recent effective score for quality control. Indicates the data consistency score; This indicates that the abnormal penalty has not been turned off; Indicates historical risk penalties; to These are the model parameters.

[0078] in:

[0079] Personnel authorization scores can be determined based on whether the personnel have valid authorization, whether they have authority over the target detection project, whether they have authority to operate the target equipment, their most recent assessment results, and the timeliness of their training. For example:

[0080] in, Indicates whether the overall authorization of personnel is valid; Indicates whether the user has permission to perform target detection tasks; Indicates whether the user has permission to operate the target device; Indicates recent performance evaluation results; This indicates a perfect score on the assessment; Indicates the time since the most recent training or assessment; Indicates the effective period of training or assessment; A balance coefficient representing the balance between performance and timeliness.

[0081] Equipment availability score can be determined based on whether the equipment is online, within its calibration validity period, maintained as scheduled, and whether there are any unshutdown faults:

[0082] in, Indicates the device's online status; Indicates that the calibration is valid; This indicates that there is no fault that is not closed; Indicates whether the planned maintenance has been completed; Indicates the time since the last maintenance; Indicates the maintenance cycle.

[0083] The score for reagents and consumables can be determined based on whether the reagent is within its expiration date, whether it is suitable for the target project and equipment, whether the reagent batch number is registered, whether it is still within its usage period after opening, and whether the inventory meets the requirements.

[0084] The effective score of the standard operating procedure can be determined based on whether the standard operating procedure version is valid, whether it is suitable for the target detection item, whether it is suitable for the current departmental scenario, and whether it has been reviewed and released.

[0085] The recent quality control effective score can be determined based on whether there is a recent effective quality control, the result of the most recent quality control, the time since the most recent qualified quality control, and the prescribed quality control cycle:

[0086] in, Indicate whether there is a recent quality control record; This indicates the risk level in the most recent quality control test. Indicates the time since the last qualified quality control; This indicates the effective period for quality control.

[0087] Based on the pre-test quality threshold, the test acceptance status can be determined:

[0088] in, This indicates the allowed execution threshold; This indicates a threshold for limiting execution, and .

[0089] By constructing a task-level quality subgraph, and extracting only the quality elements relevant to the target immediate testing task for admission evaluation, we can avoid the erroneous impact of abnormal states of irrelevant departments, equipment, or reagent batches on the current task.

[0090] In an exemplary embodiment, controlling the execution of a target instant inspection task and the detection result after executing the target instant inspection task according to the detection access status includes: generating a corresponding access control identifier according to the detection access status; sending the access control identifier to a data interface connected to the instant inspection device or report processing system; controlling the target instant inspection task to enter an allowed execution state, a conditional execution state, or a restricted execution state according to the access control identifier; obtaining the detection result obtained from executing the target instant inspection task when the target instant inspection task enters the allowed execution state or the conditional execution state; and restricting the detection result from entering the formal report processing flow when the target instant inspection task enters the restricted execution state and a detection result has been generated.

[0091] In this embodiment, the test result refers to the structured result data generated after the point-of-care testing device performs the target point-of-care testing task. The structured result data includes the test item, test value, test unit, reference range, test time and result status, and is associated with at least one of the following: result identifier, patient identifier or sample identifier, device identifier, operator identifier, department, reagent batch number and quality control batch number.

[0092] Among them, an access control identifier is generated based on the testing access status. The access control identifier can correspond one-to-one with the testing access status, or it can further carry the reason for restriction, applicable equipment, applicable testing items, validity period, and result flow requirements on the basis of the testing access status.

[0093] When the access status is set to "permitted," a permissive access control flag can be generated. Upon receiving the permissive access control flag, the on-the-spot inspection equipment or report processing system allows the target on-the-spot inspection task to execute normally and allows the inspection results to enter the subsequent reliability evaluation process.

[0094] When the testing access status is in a conditional execution state, an early warning access control identifier can be generated. Point-of-care testing equipment can perform tests, but the test results cannot directly enter the formal report release path; instead, they first enter the evaluation cache or the data area awaiting review. The conditional execution state is applicable when the current task has a certain quality risk, but has not yet reached the point where testing must be stopped. For example, equipment maintenance time is approaching its deadline, personnel training is about to expire, quality control time is approaching its cycle limit, or reagent batches show a slight deviation trend.

[0095] When the access control status is restricted, a blocking access control flag can be generated. Depending on whether the real-time inspection device supports pre-inspection control, the device can be prevented from starting inspection. For devices that cannot be directly prevented from inspection by the platform, the device can be allowed to generate raw inspection data, but this inspection data can be written to an isolated buffer through the data interface of the report processing system, preventing it from entering the formal reporting process.

[0096] To avoid patients not receiving timely testing information due to quality control issues in emergency clinical scenarios, restrictions can be determined based on the clinical urgency of the target point-of-care testing task. For example, in emergency or critical care scenarios, test results can be allowed for temporary clinical viewing with risk marking when a certain level of risk exists, while a mandatory review task is generated; however, the result still cannot be released as a risk-free formal report without completing the corresponding review.

[0097] Access control identifiers can be represented as:

[0098] in, Indicates the control identifier type; This indicates the quality reason that triggered the control flag; Indicates the scope of equipment, items, personnel, or reagents to which the control label applies; Indicates the validity period of the control label; This indicates the initial data processing path for the detection results.

[0099] By converting the inspection access status into an access control identifier that can be recognized by the interface of the real-time inspection equipment or the report processing system, the inspection access evaluation can no longer remain a mere interface reminder, but can actually affect the execution of inspection tasks and the flow of inspection results.

[0100] The data interface can be the device interface of the point-of-care testing equipment, or it can be the interface gateway located between the point-of-care testing equipment and the laboratory information system or hospital information system.

[0101] When the data interface is connected to the real-time testing equipment, the access control identifier can control equipment login, project selection, test initiation, or result upload.

[0102] When the data interface is connected to the report processing system, the access control identifier can control the entry of the test results into the formal result table, the pending result table, or the isolation result table without interfering with the physical detection action of the equipment.

[0103] Therefore, "permitted execution state, conditional execution state, or restricted execution state" can simultaneously correspond to the state at the task execution level and the state at the detection result flow level. Specifically, in the permitted execution state or conditional execution state, the target real-time verification device executes the target real-time verification task and obtains the detection result; in the restricted execution state, the execution of the target real-time verification task is prevented, or the already generated detection results are restricted to an isolated data path.

[0104] In an exemplary embodiment, updating the task-level quality subgraph based on the quality events corresponding to the target instant inspection task, and determining the result credibility of the detection result based on the updated task-level quality subgraph, includes: obtaining associated quality events generated during and after the execution of the target instant inspection task from the instant inspection quality element map based on the task identifier and quality context corresponding to the detection result; determining the quality elements corresponding to each associated quality event and establishing the association between the detection result and the corresponding quality elements; updating the state of the corresponding quality elements in the task-level quality subgraph based on the quality state changes represented by each associated quality event; determining the quality impact of each quality element on the detection result based on the updated state of each quality element and its association with the detection result, and fusing the quality impacts in conjunction with the detection admission status of the target instant inspection task to obtain the result credibility of the detection result.

[0105] The task identifier corresponding to the test result is generated when the target point-of-care testing task is established. It is used to uniquely or relatively uniquely identify the target point-of-care testing task and is written into the task-level quality sub-graph, access control identifier, and test result data. When the test result does not directly carry a task identifier, the corresponding task identifier is determined by combining and matching the sample identifier, test item, equipment identifier, and test time in the test result. The quality context is determined based on the task attributes of the target point-of-care testing task, the associated information carried by the test result, and the status of quality elements related to the task identifier in the point-of-care testing quality element map. It is used to characterize the personnel, equipment, reagents and consumables, samples, quality control, intra-institutional comparison, inter-laboratory quality assessment, and report circulation conditions at the time the test result is generated, so as to screen associated quality events that have actual quality impact on the test result based on the task identifier and quality context.

[0106] The test results are associated with personnel nodes, equipment nodes, reagent and consumable nodes, test item nodes, sample nodes, and quality control nodes in the task-level quality subgraph.

[0107] Quality events corresponding to the target real-time testing task include events that occur during task execution and after task completion. For example, equipment malfunction events during testing, quality control events after testing, reagent batch status change events, sample anomaly events, new intra-hospital comparison events, and report interface anomaly events.

[0108] The platform updates the status of corresponding nodes in the task-level quality subgraph based on quality events. If a new quality control event indicates a trend deviation in the equipment, the risk of the equipment node and the quality control node is updated; if a new intra-hospital comparison event indicates a unidirectional deviation of the same reagent batch on multiple devices, the risk of the reagent and consumables node is updated; if a sample status event indicates that the sampling to testing time exceeds the allowable range, the status of the sample node is updated.

[0109] To adapt to real-time testing environments involving multiple devices, departments, and batches, quality control events can be dynamically grouped using the following grouping keys:

[0110]

[0111]

[0112] in, The first grouping subkey represents the dimensions of project, equipment, and department. The second grouping sub-bond represents the combination of batch, concentration level, and time dimension; Indicates the items to be tested; Indicates the device type; Indicates the equipment number; Indicates department; Indicates the reagent batch number; Indicates the batch number of the quality control product; Indicates the quality control concentration level; Indicates a time window.

[0113] When the number of quality control data in the finest-grained group is less than the preset minimum sample size, grouping dimensions such as equipment number, department, reagent batch number, or quality control batch number can be gradually reduced to form the upper-level grouping. The platform prioritizes the finest-grained grouping where the sample size meets the requirements and the intra-group differences do not exceed the preset range.

[0114] Group heterogeneity can be represented by, for example:

[0115] in, Indicates the number of subgroups within a group; Indicates the first The number of data points in each subgroup; Indicates the first The mean of each subgroup; This represents the overall mean of the group. Indicates the overall variance of the group; To prevent extremely small positive numbers with a denominator of zero.

[0116] For the first in the effective quality control group Quality control value Standardized deviation can be calculated:

[0117] in, This indicates the target value or stable mean of the quality control group; This represents the standard deviation of the quality control group.

[0118] Slow drift can be identified using the exponentially weighted moving average statistic:

[0119] in, Indicates the first The exponentially weighted moving average statistic at time points; This represents the smoothing coefficient.

[0120] Persistent biases can be identified using cumulative sum statistics:

[0121]

[0122] in, Indicates positive cumulative deviation; Indicates negative cumulative deviation; This indicates the allowed offset parameter.

[0123] Dynamic quality control risk can be represented as:

[0124]

[0125]

[0126] in, This represents the statistical risk component consisting of rule judgment, trend drift, and cumulative bias. This represents the execution risk components consisting of missing quality control, expired quality control, and data conflicts. This indicates the risk of quality control rules derived from rules such as single-point over-limit, continuous unidirectional over-limit, continuous unilateral over-limit, and continuous changing trend. This indicates the risk of trend drift; Indicates cumulative deviation risk; This indicates a risk of inadequate quality control; This indicates a risk of quality control exceeding the deadline; This indicates a risk of conflicting quality control data. to For the corresponding weights.

[0127] The risk of missing quality control measures can be determined based on the number of times quality control should have been performed but was not:

[0128] in, This indicates the number of quality control measures that should have been performed but were not. This represents the missing tolerance coefficient.

[0129] The risk of quality control exceeding the deadline can be represented as:

[0130] in, Indicates the time since the last qualified quality control; This indicates the specified quality control cycle.

[0131] For the same test item, the set of intra-hospital comparison results generated under different equipment, different departments, different reagent batches, or different concentration levels:

[0132] The robust central value can be determined using the median:

[0133] Robust dispersion is determined using the median absolute deviation:

[0134] No. The robust standardized bias of the intra-hospital comparison results can be expressed as:

[0135] For the Unit or the first For each department, relative bias can be determined based on the difference between its comparison mean and robust central value:

[0136] in, This indicates the total allowable error for the test item.

[0137] The comparison coverage risk can be expressed as:

[0138] in, and These represent the actual number of participating departments and the number of departments that should participate, respectively. and These represent the actual number of participating devices and the number of devices that should participate, respectively. and These represent the actual number of concentration levels covered and the number of concentration levels that should be covered, respectively. .

[0139] Intra-hospital consistency risk can be represented as:

[0140] in, This represents outlier risk determined based on robust standardized bias. Indicates relative bias risk; This indicates the risk of anchoring deviation from the central laboratory or reference equipment.

[0141] When multiple devices simultaneously exhibit deviations in the same direction relative to the central laboratory, it can be identified as a test item-level systematic deviation; when a single device deviates from other devices, it can be identified as an equipment-level deviation; when multiple devices in the same department deviate from other departments, it can be identified as a departmental operation or environmental deviation; when multiple devices using the same reagent batch number exhibit deviations in the same direction, it can be identified as a reagent batch number deviation.

[0142] The reliability of the results can be determined based on pre-test quality access values, dynamic quality control risks, intra-institutional consistency risks, inter-laboratory quality assessment status, equipment status, personnel status, reagent and consumable status, standard operating procedure status, sample status, historical anomaly status, and data conflict status.

[0143] For example, the confidence level of the result can be expressed as:

[0144]

[0145]

[0146]

[0147]

[0148] in, Indicates the test results The reliability of the results; This indicates the overall credibility score; This represents the pre-test admission score component; Represents the positive score components for each quality state; This indicates the risk component comprised of each risk and penalty item; This indicates the quality threshold value before testing; This indicates dynamic quality control risks; This indicates a risk of inconsistency within the hospital; This indicates the inter-laboratory quality assessment score; This indicates the device status score; Indicates the score of the personnel's status; The score indicates the status of reagents and consumables; Indicates the standard operating procedure status score; Indicates the sample state score; Indicates punishment for historical anomalies; Indicates penalties for data conflicts; to These are the model parameters.

[0149] The interlaboratory quality assessment score can be determined based on the existence of a valid interlaboratory quality assessment record, the time since the most recent qualified interlaboratory quality assessment, and the deviation of the most recent interlaboratory quality assessment:

[0150] in, This indicates whether there are valid interlaboratory quality assessment records; Indicates the time since the most recent qualified interlaboratory quality assessment; Indicates the effective period of interlaboratory quality assessment; This indicates the risk of deviation in interlaboratory quality assessment.

[0151] The sample status score can be determined based on the sample identity matching status, whether the sampling and testing time meets the requirements, whether the sample type is suitable for the testing items, whether the sample volume is sufficient, and whether the sample has hemolysis, coagulation, contamination or other abnormalities.

[0152] Through the above calculations, the reliability of the results can simultaneously reflect the quality conditions before the detection task begins, as well as the dynamic quality changes during and after the detection process, avoiding the decision to publish solely based on whether the detection value exceeds the reference range.

[0153] In an exemplary embodiment, generating a report release control strategy based on result credibility includes: matching the result credibility with preset release conditions to determine the report release level corresponding to the detection result; determining the target flow state of the detection result in the report processing flow based on the report release level, and generating a report release control instruction corresponding to the target flow state; sending the report release control instruction to the interface gateway connected to the target reporting system, so that the interface gateway writes the detection result into the data processing path corresponding to the target flow state according to the report release control instruction; and recording the result credibility, target flow state, and execution state of the report release control instruction corresponding to the detection result to form a report release control record for the detection result.

[0154] The report's publication level can be determined based on the preset confidence level range to which the results belong:

[0155] in, ; It can automatically publish levels; It can correspond to the release level marked with risk; It can correspond to manual review or delayed release levels; You can restrict the level of release accordingly.

[0156] The target flow status refers to the state that the test result needs to enter in the report processing flow. Report release control instructions may include test result identifier, target flow status, policy generation reason, interface target, execution priority, validity period, and review requirements.

[0157] After receiving the report publishing control command, the interface gateway can perform the following operations: When the target workflow status is officially released, the test results will be written to the official report data area and pushed to the clinical end. When the target flow status is in the risk mark release status, the test results and quality risk mark are written into the formal report data area at the same time, and the test results are added to the random inspection and review queue. When the target's status is pending review, the test results are written to the pending review data area, and no formal report is generated for the clinical end at this time. When the target is in the isolated state, the detection results are written to the isolated data area to prevent it from entering the formal report data area. When a test result has been published but subsequent quality incidents reduce its credibility, a report withdrawal prompt or report correction prompt can be generated.

[0158] Report release control records can be represented as follows:

[0159] in, Indicates the test result identifier; This indicates the report release control strategy; Indicate the reason for control; This indicates control over execution time; Indicates the target data processing path; Indicates the execution status.

[0160] This control log can be used to trace why a detection result was not automatically published, what data processing path it entered, and whether the interface gateway actually executed the control policy.

[0161] In an exemplary embodiment, the method further includes: determining the target data processing path corresponding to the detection result according to the report release control policy, and controlling the detection result to enter the target data processing path through the interface gateway; obtaining the policy execution status returned by the interface gateway for the detection result, and storing the policy execution status in association with the detection result, so as to determine the actual flow status of the detection result in the report processing flow according to the policy execution status.

[0162] The strategy execution status can include execution success, execution failure, partial execution, waiting for execution, and execution timeout.

[0163] Specifically, the target data processing path refers to the flow path of detection results corresponding to the report release control strategy, which may include the formal release path, risk marking path, pending review path, delayed release path, and isolation path. After receiving the report release control strategy, the interface gateway writes the detection results into the corresponding data area according to the release level and target flow status of the detection results. For example, detection results that meet the automatic release conditions enter the formal report path; detection results that require manual review enter the pending review path; and detection results that do not meet the release conditions enter the isolation path, thereby preventing them from directly entering the formal report system.

[0164] After completing the corresponding processing, the interface gateway returns the policy execution status to the platform. The policy execution status can include successful execution, pending execution, execution failure, partial execution, or execution timeout. The platform associates and saves the policy execution status with the corresponding detection result, and determines its actual flow status in the report processing workflow by combining the actual data processing path the detection result enters. If the actual flow status matches the target status required by the report release control policy, the policy execution is confirmed to be complete; if they do not match, an interface execution exception message is generated, triggering compensatory processing such as resending control instructions, manual verification, or report withdrawal. This ensures that the report release control policy is not only generated but also actually executed by the interface gateway, improving the reliability and traceability of detection result release control.

[0165] Therefore, the policy execution status is not simply log information, but is used to verify whether the report release control policy is actually effective, and to trigger compensation control when the policy is not effective.

[0166] For example, if the report release control policy requires the test results to enter the pending review data area, but the interface gateway returns an execution failure, and the test results have already entered the formal report data area, then the actual flow status of the test results is inconsistent with the target flow status. In this case, the platform can generate an interface exception event, update the interface node risk, and perform result interception, report withdrawal prompts, or manual verification.

[0167] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0168] Based on the same inventive concept, this application also provides a quality element graph-based reliable release control system for hospital real-time test results, used to implement the aforementioned method for reliable release control of hospital real-time test results based on quality element graphs. The solution provided by this system is similar to the implementation scheme described in the above method. Therefore, the specific limitations of one or more cloud-based embodiments of the reliable release control system for hospital real-time test results based on quality element graphs provided below can be found in the limitations of the method for reliable release control of hospital real-time test results based on quality element graphs described above, and will not be repeated here.

[0169] In one exemplary embodiment, such as Figure 2 As shown, this application also provides a hospital real-time test result reliable release control system 500 based on quality element map, the system comprising: The map construction module 100 is used to acquire multi-source quality data in the hospital's point-of-care testing process, and construct a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between each quality element. The detection access status determination module 200 is used to extract quality elements related to the target immediate inspection task from the immediate inspection quality element map in response to the triggering of the target immediate inspection task, form a task-level quality sub-map, and determine the detection access status of the target immediate inspection task according to the status of each quality element in the task-level quality sub-map. The detection result determination module 300 is used to control the execution of the target real-time inspection task and the detection result after the execution of the target real-time inspection task based on the detection access status. The release control module 400 is used to update the task-level quality subgraph according to the quality events corresponding to the target real-time inspection task after obtaining the detection results, determine the result credibility of the detection results according to the updated task-level quality subgraph, and generate a report release control strategy based on the result credibility.

[0170] In one embodiment, a computer device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps of the method described above.

[0171] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described above.

[0172] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps of the method described above.

[0173] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0174] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0175] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for controlling the reliable release of hospital real-time test results based on quality element maps, characterized in that, The method includes: Acquire multi-source quality data during the hospital's point-of-care testing process, and construct a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between the quality elements. In response to the triggering of the target immediate inspection task, quality elements related to the target immediate inspection task are extracted from the immediate inspection quality element map to form a task-level quality sub-map, and the detection access status of the target immediate inspection task is determined according to the status of each quality element in the task-level quality sub-map. The execution of the target real-time inspection task and the detection results after the execution of the target real-time inspection task are controlled according to the detection admission status. After obtaining the detection results, the task-level quality subgraph is updated according to the quality events corresponding to the target instant inspection task, and the result credibility of the detection results is determined according to the updated task-level quality subgraph. A report release control strategy is then generated based on the result credibility.

2. The method according to claim 1, characterized in that, The process of acquiring multi-source quality data during hospital point-of-care testing, and constructing a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between the quality elements, includes: The multi-source quality data is obtained from multiple data sources related to the hospital's point-of-care testing process, and the multi-source quality data is standardized to obtain point-of-care testing events that characterize changes in the state of quality elements. Based on the quality objects associated with each of the immediate inspection events, the corresponding quality elements are determined, and based on the business associations and quality dependencies of different quality objects in the immediate inspection process, the association relationships between the quality elements are determined. Based on each of the quality elements, the state of each of the quality elements, and the relationships between the quality elements, the real-time inspection quality element map is constructed.

3. The method according to claim 1, characterized in that, In response to the triggering of a target immediate inspection task, the process involves extracting quality elements related to the target immediate inspection task from the immediate inspection quality element map to form a task-level quality sub-map, and determining the detection access status of the target immediate inspection task based on the status of each quality element in the task-level quality sub-map, including: Based on the task attributes of the target real-time inspection task, determine the target quality objects participating in the target real-time inspection task; Extract the target quality element nodes corresponding to each of the target quality objects from the real-time inspection quality element graph, and the target quality association edges connecting each of the target quality element nodes to form the task-level quality subgraph; Based on the fusion result of the state of each target quality element node and the association weight of each target quality associated edge in the task-level quality subgraph, the detection execution conditions of the target real-time inspection task are evaluated to obtain the detection admission evaluation result. The detection access status of the target real-time inspection task is determined based on the detection access evaluation results.

4. The method according to claim 1, characterized in that, The step of controlling the execution of the target real-time inspection task based on the detection admission status and the detection results after executing the target real-time inspection task includes: Generate a corresponding access control identifier based on the detected access status; The access control identifier is sent to the data interface connected to the instant inspection device or report processing system; Based on the access control identifier, the target instant verification task is controlled to enter the allowed execution state, conditional execution state, or restricted execution state; When the target real-time inspection task enters the allowed execution state or the conditional execution state, the detection result obtained by executing the target real-time inspection task is acquired; when the target real-time inspection task enters the restricted execution state and the detection result has been generated, the detection result is restricted from entering the formal report processing flow.

5. The method according to claim 1, characterized in that, The step of updating the task-level quality subgraph based on the quality events corresponding to the target real-time inspection task, and determining the result reliability of the detection result based on the updated task-level quality subgraph, includes: Based on the task identifier and quality context corresponding to the detection result, obtain the associated quality events generated during and after the execution of the target instant inspection task from the instant inspection quality element map; Determine the quality elements corresponding to each of the associated quality events, and establish the correlation between the detection results and the corresponding quality elements; Update the state of the corresponding quality element in the task-level quality subgraph based on the quality state changes represented by each of the associated quality events. Based on the updated status of each quality element and its correlation with the test results, the quality impact of each quality element on the test results is determined. Then, in conjunction with the test access status of the target real-time inspection task, the quality impacts are fused to obtain the result reliability of the test results.

6. The method according to claim 5, characterized in that, Based on the credibility of the results, a report release control strategy is generated, including: The credibility of the results is matched with preset release conditions to determine the report release level corresponding to the detection results; Based on the report release level, determine the target flow status of the test results in the report processing flow, and generate a report release control instruction corresponding to the target flow status; The report release control command is sent to the interface gateway connected to the target reporting system, so that the interface gateway writes the detection result into the data processing path corresponding to the target flow status according to the report release control command; Record the result credibility, target flow status, and execution status of the report release control instructions corresponding to the detection results to form the report release control record of the detection results.

7. The method according to claim 6, characterized in that, The method further includes: The target data processing path corresponding to the detection result is determined according to the report release control strategy, and the detection result is controlled to enter the target data processing path through the interface gateway. The policy execution status returned by the interface gateway in response to the detection result is obtained, and the policy execution status is associated with and stored with the detection result, so as to determine the actual flow status of the detection result in the report processing flow based on the policy execution status.

8. A reliable control system for real-time hospital test results based on quality element maps, characterized in that, The system includes: The map construction module is used to acquire multi-source quality data in the hospital's point-of-care testing process, and construct a point-of-care testing quality element map based on the quality elements represented by the multi-source quality data and the correlation between the quality elements. The detection access status determination module is used to extract quality elements related to the target immediate inspection task from the immediate inspection quality element map in response to the triggering of the target immediate inspection task, form a task-level quality sub-map, and determine the detection access status of the target immediate inspection task according to the status of each quality element in the task-level quality sub-map. The detection result determination module is used to control the execution of the target real-time inspection task and the detection result after executing the target real-time inspection task according to the detection admission status; The release control module is used to update the task-level quality subgraph according to the quality event corresponding to the target instant inspection task after obtaining the detection result, determine the result credibility of the detection result according to the updated task-level quality subgraph, and generate a report release control strategy according to the result credibility.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images