A mobile terminal-based clinical blood transfusion process closed-loop management system

Abstract

The application discloses a kind of clinical blood transfusion process closed loop management system based on mobile terminal, it is related to blood transfusion management technical field, including: management module, for presetting the operation node of blood bag and corresponding order constraint;Execution module includes the submodule for executing the corresponding task of operation node;Recording module is used to update the operation record of blood bag based on the operation task that has been completed;Verification module includes acquisition submodule, matching submodule and recording submodule;Wherein, acquisition submodule is used to obtain the unique identification of user and operation node, responds to the code scanning operation of user to blood bag, obtains the latest operation record of corresponding blood bag according to code scanning result;Matching submodule is used to match the latest operation record of blood bag with the operation node of user based on operation node and order constraint, if matching succeeds, trigger execution module and / or recording module, if matching fails, generate and push operation exception information.The application realizes the checkable closed loop management of blood bag operation.

Description

Technical Field

[0001] This application relates to the field of blood transfusion management technology, specifically to a closed-loop management system for clinical blood transfusion processes based on mobile terminals. Background Technology

[0002] Clinical blood transfusion is a commonly used medical procedure in disease treatment and patient resuscitation. Because the closed-loop blood transfusion process involves multiple departments, personnel, and operational steps, it is highly complex to manage. Furthermore, the timeliness of blood transfusions directly affects the patient's treatment outcome; therefore, extremely high standards of information accuracy and procedural standardization are required in clinical practice.

[0003] In the traditional clinical blood management model, the process mostly relies on manual operation and paper records. The execution of the process is prone to the risk of untimely or missing operation records. This risk not only affects the lag or absence of key operational information in blood transfusion, affecting the staff's mastery and scheduling efficiency of blood transfusion process, but also increases the risk of errors in blood transfusion operation. Summary of the Invention

[0004] The purpose of this invention is to solve the technical problem of untimely or incomplete recording in existing blood transfusion management, and to provide a closed-loop management system for clinical blood transfusion process based on mobile terminals.

[0005] According to a first aspect of the present invention, the present invention claims protection for a closed-loop management system for clinical blood transfusion processes based on mobile terminals, comprising:

[0006] The management module is used to preset the operation nodes of blood bags and their corresponding sequence constraints;

[0007] The execution module includes sub-modules for executing the operation tasks of the corresponding operation nodes;

[0008] The recording module is used to update the operation records of blood bags based on completed operation tasks;

[0009] The verification module includes an acquisition submodule, a matching submodule, and a recording submodule;

[0010] The acquisition submodule is used to acquire the user's unique identifier and operation node, and in response to the user's scanning operation of the blood bag, it acquires the latest operation record of the corresponding blood bag based on the scanning result. The matching submodule is used to match the user's operation node with the latest operation record of the blood bag based on the operation node and sequence constraints. If the match is successful, the execution module and / or the recording module are triggered. If the match fails, operation exception information is generated and pushed.

[0011] Preferably, the management module is also used to preset process nodes and corresponding sequence constraints. The process nodes include application nodes, and the operation nodes include blood matching nodes and inter-hospital transfer nodes. The execution module includes an application sub-module, a blood matching sub-module, and an inter-hospital transfer sub-module.

[0012] The application submodule is used to obtain blood transfusion applications submitted by users; the blood matching submodule is used to establish the association between blood transfusion applications and blood bags, and set the scheduling status of the corresponding blood bags to prohibited; the cross-hospital transfer submodule is used to generate and push transfer exception information for blood bags with a prohibited scheduling status, and generate transfer applications for blood bags with a permitted scheduling status.

[0013] Preferably, the execution module further includes a monitoring submodule; the monitoring submodule is used to monitor the remaining valid time of each blood bag, obtain the matching degree of each blood bag with each medical institution, and generate and push a recall reminder message if the matching degree of the blood bag with the storage medical institution is the smallest among all the matching degrees of the same blood bag.

[0014] Among them, the evaluation indicators of matching degree include the probability score of the corresponding blood bag being used by the corresponding medical institution within the remaining effective time.

[0015] Preferably, the system further includes: obtaining the scoring results of the corresponding blood bag and the corresponding medical institution based on all evaluation indicators; calculating the matching degree according to the product of the indicative function and the scoring results; if the remaining valid time after the corresponding blood bag is transferred to the corresponding medical institution is greater than 0, the indicative function is set to 1; if the remaining valid time after the corresponding blood bag is transferred to the corresponding medical institution is not greater than 0, the indicative function is set to 0.

[0016] Preferably, the method for calculating the probability score includes:

[0017] ;

[0018] Where B represents blood bags, H represents medical institutions, and S represents blood bags. p This represents a probability score, where position represents the sequence number of the corresponding blood bag in the usage queue of the corresponding medical institution, and N is the number of the blood bag. H This indicates the demand for the same type of blood bags by the corresponding medical institution.

[0019] Preferably, the evaluation index of matching degree also includes the scheduling cost of dispatching the corresponding blood bag from the storage medical institution to the corresponding medical institution.

[0020] Preferably, upon receiving a transfer-in request, the cross-hospital transfer-out submodule is further configured to obtain the safety threshold of the corresponding category of blood bags at the current medical institution, sort all blood bags of the same type stored at the current medical institution based on the matching degree with the current medical institution, and take the number of blood bags corresponding to the safety threshold into the safety pool in descending order of matching degree, and include the remaining blood bags of the same type into the candidate pool. The blood bags in the candidate pool serve as candidate blood bags for the initiating institution of the transfer-in request.

[0021] Preferably, the system further includes a scheduling engine, which is used to select the blood bag with a higher matching degree with the initiating organization from all candidate pools as the target scheduling blood bag based on the number of applications for the corresponding category of blood bags in the blood bag transfer application, and generate a scheduling scheme.

[0022] Preferably, the system further includes: obtaining the average consumption of blood bags of the corresponding category at the current medical institution; sorting the scheduling time from the current medical institution to all candidate institutions in descending order, and calculating the average scheduling time of the first half; and calculating the lower limit of the corresponding safety threshold based on the average scheduling time and the average consumption.

[0023] Preferably, the operation node also includes an inter-hospital transfer node, and the execution module also includes an inter-hospital transfer sub-module. The inter-hospital transfer sub-module is used to initiate a transfer application, and the monitoring sub-module is also used to monitor the quantity of blood bags of each category. If there is a category where the quantity of blood bags drops to a safe threshold, a transfer reminder message is generated and pushed.

[0024] According to a second aspect of the present invention, the present invention claims protection for a closed-loop management device for clinical blood transfusion process based on a mobile terminal, comprising a processor and a memory, the memory storing computer-readable instructions, which, when executed by the processor, run functional modules as described in the first aspect above.

[0025] This application has the following beneficial effects:

[0026] 1. By setting up management, execution, recording, and verification modules, a mandatory, sequential, and structured closed-loop management mechanism for blood bag operations is established on the mobile terminal. The management module, through preset operation nodes and sequence constraints, ensures that each blood bag operation has a clear logical sequence requirement within the system. The verification module, based on this logical sequence requirement, compares and matches the user-selected operation node with the latest operation record of the blood bag. When a match is successful, the execution module is automatically triggered to complete the corresponding operation task, and / or the recording module is automatically triggered to update the blood bag's operation record. Conversely, when a match fails, the system generates operation anomaly information. Medical personnel can use this information to promptly identify safety risks during blood bag operations, such as incorrect operation steps or inaccurate operation records. Therefore, this application achieves verifiable closed-loop management of blood bag operations, improving the timeliness, security, and completeness of blood bag operation records.

[0027] 2. After establishing a one-to-one or one-to-many association between blood transfusion requests and blood bags, the blood matching submodule sets the scheduling status of the corresponding blood bags to prohibited. The cross-hospital dispatch submodule verifies whether the scanned blood bag is in a dispatchable state. When the scheduling status of the scanned blood bag is prohibited, it generates and pushes operation exception information, thereby ensuring that the blood bags reserved by the blood matching submodule cannot be occupied or incorrectly dispatched by external dispatch processes, reducing the risk of incorrect blood bag dispatch.

[0028] 3. The monitoring submodule can identify blood bags at risk of being wasted based on their matching degree with different medical institutions, and generate a recall reminder message to reduce the risk of waste caused by blood bags being left in low-demand medical institutions.

[0029] 4. An indicator function is introduced into the matching algorithm to convert the scheduling reachability of blood bags into a hard constraint. On the one hand, binarization does not increase the additional computational load of the system; on the other hand, it reduces the risk of misscheduling due to blood bags being unusable upon arrival at the hospital, thus reducing unnecessary scheduling costs and waste. When the remaining valid duration of the blood bag is not greater than the scheduling duration, it means that the blood bag will inevitably be unusable within its remaining validity period after arriving at the corresponding medical institution. Through the correction of the indicator function, the matching degree between the blood bag and the medical institution is made to 0. When the remaining valid duration of the blood bag is greater than the scheduling duration, the indicator function takes the value of 1, indicating that the blood bag has a minimum usability guarantee.

[0030] 5. Dynamic window matching based on remaining validity period: By calculating the difference between the blood bag's usage queue number in the medical institution and the institution's demand for the same type of blood bag, the system automatically identifies the risk of blood bag waste without increasing the system load. Furthermore, this method is universal and compatible even when medical institutions use heterogeneous sorting strategies for their blood bags. When the difference is less than 0, it indicates that the system determines that the corresponding medical institution has a definite demand gap for that type of blood bag within its remaining validity period. The smaller the difference, the larger the demand gap, and the higher the probability that the corresponding blood bag will be used by the corresponding medical institution within its remaining validity period; conversely, the larger the difference, the smaller the demand gap, and the lower the probability that the corresponding blood bag will be used by the corresponding medical institution within its remaining validity period. When the difference is greater than 0, it means that the system judges that the corresponding medical institution has an over-exploitation risk of this type of blood bag within the remaining validity period of the corresponding blood bag. The smaller the difference, the smaller the over-exploitation risk, and the greater the probability that the corresponding blood bag will be used by the corresponding medical institution within the remaining validity period. The larger the difference, the greater the over-exploitation risk, and the lower the probability that the corresponding blood bag will be used by the corresponding medical institution within the remaining validity period.

[0031] 6. Scheduling costs are incorporated into the matching calculation. The system prioritizes allocation schemes with lower scheduling costs, ensuring that blood bags are used by the storing medical institution first, provided they can be consumed normally. If the probability of blood bags being used by the storing medical institution within the remaining effective time is too low, they can be allocated to other medical institutions. This allows cross-hospital allocation to balance resource utilization and operational costs.

[0032] 7. A dynamic construction mechanism for safety pools and candidate pools based on safety thresholds has been introduced. This enables medical institutions to prioritize blood bags with higher matching rates into the safety pool and blood bags with lower usage probability and higher retention risk into the candidate pool when they receive a transfer request, while ensuring that their minimum safety stock is not weakened. This achieves cross-hospital support that balances resource utilization and safety stock.

[0033] 8. By using the matching degree of blood bags in the candidate pool as input to the scheduling engine, blood bags with a higher matching degree with the initiating organization can be selected as target scheduling blood bags. This mechanism ensures the demand matching between the selected blood bags and the initiating organization of the transfer application.

[0034] 9. The lower limit of the safety threshold allows the selection of the safety threshold to reflect the time required for medical institutions to allocate blood bags to other medical institutions. This ensures that the minimum holding quantity of this type of blood bag by medical institutions can be adapted to the time required for them to apply for allocation to other surrounding medical institutions. It provides a safety stock judgment basis driven by allocation time, balancing the blood supply safety risk caused by too low a safety threshold and the blood bag retention risk caused by too high a threshold.

[0035] 10. Automated risk alerts can help reduce the risk of blood supply disruptions due to human error. Attached Figure Description

[0036] The accompanying drawings, which are incorporated in and form a part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure.

[0037] Figure 1 This is a schematic diagram of a closed-loop management system for clinical blood transfusion based on a mobile terminal, as described in an embodiment of this application.

[0038] Figure 2 This is a schematic diagram illustrating the triggering of each module in the recycling node involved in the embodiments of this application;

[0039] Figure 3 This is another structural diagram of the closed-loop management system for clinical blood transfusion based on a mobile terminal involved in the embodiments of this application;

[0040] Figure 4This is a flowchart illustrating the identification process of blood bags remaining in the monitoring submodule of the cross-hospital transfer node involved in this application embodiment;

[0041] Figure 5 The flowchart of the generation of the scheduling scheme in the cross-hospital transfer node involved in the embodiments of this application;

[0042] Figure 6 This is a schematic diagram of the electronic device structure involved in the embodiments of this application;

[0043] In the diagram, N represents the number of medical institutions. Detailed Implementation

[0044] This invention provides a closed-loop management system for clinical blood transfusion processes based on mobile terminals. To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. The components of the embodiments of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, referring to terms such as "an embodiment," "some embodiments," "implementation," "embodiment," "illustrative embodiment," "example," "specific example," or "some examples," the following detailed description of the embodiments of this application provided in the accompanying drawings is not intended to limit the scope of the claimed application, but merely indicates that the specific features, structures, or characteristics described in connection with that embodiment or example are included in at least one embodiment or example of the present invention. Moreover, the specific features, structures, or characteristics described can be combined in any suitable manner in one or more embodiments or examples. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0045] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, relational terms such as "first," "second," etc., are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0046] This invention claims protection for a closed-loop management system for clinical blood transfusion processes based on mobile terminals, as detailed in the appendix. Figure 1As shown, the system includes a management module, an execution module, a recording module, and a verification module. The management module is used to preset the operation nodes, process nodes, and corresponding sequence constraints for the blood bag. The execution module is used to execute the operation tasks of the corresponding operation nodes and process nodes. The recording module is used to update the operation records of the blood bag. The verification module is used to verify whether any operation nodes of the blood bag are missing.

[0047] It should be noted that the system's preset operation nodes include the warehousing node, blood matching node, blood dispensing and retrieval node, pre-transfusion verification node, transfusion node, in-transfusion inspection node, termination node, termination inspection node, recycling node, and destruction node, but these are not limited to these. The preset process nodes include the application node and the application approval node, but these are not limited to these.

[0048] It should be noted that the sequence constraints include both sequential relationships and time constraints between nodes. Sequential relationships between nodes include those between operational nodes, between process nodes, and between operational nodes and process nodes. These sequential relationships describe the logical dependency that the start or completion of one node requires the completion of one or more other nodes. For example, the preceding node to the blood collection node is pre-set as the blood matching node, indicating that the blood matching node should be completed before the blood collection node begins. Of course, the sequential relationships between nodes are not limited to this. Time constraints describe the time constraints of the start and / or completion intervals between nodes. For example, the time constraint may include allowing entry into the pre-transfusion verification node within a preset time after the completion of the blood collection node. This means that if the time to enter the pre-transfusion verification node exceeds the preset time, the time constraint is not met, and entry into the pre-transfusion verification node is prohibited to ensure the safety of the blood bags used by the patient.

[0049] It should be noted that the order constraint can be obtained through pre-setting.

[0050] It should be noted that whether each operation node and each process node has a sub-module that performs the corresponding operation in the execution module can be determined through pre-setting.

[0051] In the first embodiment, the preset operation nodes and process nodes in the management module can correspond to sub-modules in the execution module. The warehousing node corresponds to the warehousing sub-module in the execution module. This sub-module is used to store blood bag information, generate or obtain the unique identifier and blood bag code of the blood bag, etc., to associate the blood bag code with all the records of the blood bag; however, it is not limited to this. The blood bag code can be a barcode, a QR code, or other feasible methods. The blood matching node corresponds to the blood matching sub-module in the execution module. This sub-module is used to obtain blood bags matching the transfusion request and establish the association between the transfusion request and the blood bag, etc.; however, it is not limited to this. The blood dispensing node corresponds to the blood dispensing sub-module in the execution module. This sub-module is used to dispense the corresponding blood bag; however, it is not limited to this. The pre-transfusion verification node corresponds to the pre-transfusion verification sub-module in the execution module. This pre-transfusion verification module is used to verify the blood bag information and patient information before the transfusion operation; however, it is not limited to this. The transfusion node corresponds to a transfusion submodule in the execution module. This submodule records the patient's status characteristics during transfusion, but its scope is not limited to this. The in-transfusion monitoring node and the end-of-transfusion monitoring node correspond to a monitoring submodule in the execution module. This submodule records the patient's status characteristics 15 minutes after the start of transfusion and 4 hours after the end of transfusion, but its scope is not limited to this. The end node corresponds to an end submodule in the execution module; this submodule records the patient's status characteristics when the transfusion is completed, but its scope is not limited to this. The retrieval node corresponds to a retrieval submodule in the execution module. This submodule records the blood bag's status upon retrieval and updates the storage information in the blood bank, such as whether it is damaged, but its scope is not limited to this. The destruction node corresponds to a destruction submodule in the execution module. This submodule updates the storage information in the blood bank, but its scope is not limited to this.

[0052] It should be noted that corresponding table structures can be created for blood transfusion applications and blood bag information respectively. Then, the application identifier of the blood transfusion application can be selected as the foreign key of the blood bag information table, and / or the unique blood bag identifier of the blood bag information table can be selected as the foreign key of the blood transfusion application table, thereby establishing the association between blood transfusion applications and blood bags.

[0053] In this embodiment, the application node corresponds to an application submodule in the execution module. The application submodule is used to obtain the blood transfusion application submitted by the user, but it is not limited to this. The application approval node corresponds to an approval submodule in the execution module. The approval submodule is used to obtain the user's approval opinion on the blood transfusion application, but it is not limited to this.

[0054] In this embodiment, the recording module is used to update the operation record of the blood bag based on the completed operation tasks. The operation record includes at least the operator's unique identifier, digital signature, operation node, and operation time, but it is not limited to these.

[0055] In this embodiment, the verification module includes an acquisition submodule and a matching submodule, but it is not limited to these. The acquisition submodule includes a personnel submodule and a blood bag submodule, but it is not limited to these. The personnel submodule is used to acquire the unique identifier and operation node of the operator. The blood bag submodule responds to the user's scanning operation of the blood bag and queries the corresponding latest operation record based on the unique identifier of the blood bag. The matching submodule is used to match the user's operation node with the latest operation record of the blood bag based on the operation node and the sequence constraints preset in the management module. If the matching fails, it generates and pushes operation exception information to remind the operator and / or relevant management personnel to check whether there are any errors or omissions in the operation record of the blood bag.

[0056] In this embodiment, the recycling node is used as an example for detailed explanation. Other nodes are similar to the recycling node and will not be described in detail here. Refer to the appendix. Figure 2 As shown, before executing and / or recording the corresponding operation node, the user who wants to recycle the blood bag logs into their account. The personnel module caches the user's unique identifier, such as a user code. In response to the user completing the login operation, the personnel module pushes an operation node selection page to the user and obtains the "recycle" node selected by the user. In response to the user completing the blood bag scanning operation, the blood bag module obtains the unique identifier from the scanning result and queries the latest operation record of the blood bag based on the unique identifier. When the user-selected "recycle" node and the latest operation record of the blood bag are obtained, the matching submodule is automatically triggered. The matching submodule queries the order constraint of the "recycle" node based on the "recycle" node and the latest operation record of the blood bag, and determines whether the latest operation record of the blood bag matches the "recycle" node. If they match, the system considers the match successful, triggers the recycling submodule, completes the operation task of the recycling submodule, and then continues to trigger the recording module to update the latest operation record of the blood bag; if they do not match, the system considers the match failed, generates the operation exception information, and pushes it to the operator and / or relevant management personnel.

[0057] It should be noted that when a match is successful, both the execution module and the recording module can be triggered simultaneously, or the execution module can be triggered first, followed by the recording module after its completion, or vice versa. This embodiment does not further limit the specific triggering order of a successful match.

[0058] It should be noted that the preset operation nodes and process nodes in the management module may not correspond one-to-one with the sub-modules in the execution module. In the second embodiment, compared to the first embodiment, the execution module does not have a sub-module corresponding to the blood transfusion node. That is, when performing a blood transfusion operation, the verification module directly determines whether a blood transfusion operation should be performed, and the recording module records the operator and operation time of the blood transfusion operation, without the need to set up an additional blood transfusion sub-module in the execution module. Other nodes are similar and will not be described in detail again. The execution module also includes a monitoring sub-module, which is used to monitor the remaining valid time of each blood bag in the blood bank and the quantity of each type of blood bag. If the monitoring sub-module does not involve manual intervention by the operator, there is no need to set up corresponding storage monitoring nodes in the operation node and the process node. If the monitoring sub-module involves manual intervention by the operator, corresponding storage monitoring nodes can be set up in the operation node and the process node.

[0059] In this embodiment, if there is no submodule corresponding to the corresponding operation node in the execution module, the recording module is directly triggered when the matching submodule determines that the match is successful.

[0060] In the third embodiment, compared to the first and second embodiments, refer to the appendix. Figure 3 As shown, after establishing the association between the blood transfusion request and the blood bag, the blood matching submodule is also used to set the scheduling status of the corresponding blood bag to prohibited. The operation node also includes an inter-hospital transfer node. The inter-hospital transfer node corresponds to the inter-hospital transfer submodule in the execution module. The inter-hospital transfer submodule is used to determine the scheduling status of the corresponding blood bag. If the corresponding scheduling status is prohibited, transfer exception information is generated and pushed; if the corresponding scheduling status is permitted, a transfer request is initiated.

[0061] It should be noted that when medical staff establish a connection between a blood transfusion request and a blood bag through the blood matching submodule, it indicates that the blood bag is in an unschedulable state, and the blood matching submodule sets the scheduling status of the blood bag to prohibited. When medical staff perform an inter-hospital transfer operation for a blood bag, they select the inter-hospital transfer node in the personnel submodule. If the matching submodule determines that the match is successful, the inter-hospital transfer submodule is triggered. The inter-hospital transfer submodule determines whether the blood bag can be transferred based on its scheduling status; that is, blood bags with a prohibited scheduling status cannot be transferred, while blood bags with a permitted scheduling status can be transferred.

[0062] In this embodiment, refer to the appendix. Figure 4As shown, the monitoring submodule is also used to obtain the matching degree of each blood bag in the blood bank with each medical institution, and to determine whether the corresponding blood bank should be transferred out based on the matching degree. That is, among all the matching degrees of the same blood bag, if the matching degree of the blood bag with the storage medical institution is the smallest, it means that the blood bag is more suitable to be transferred to other medical institutions for storage, and there is a high risk of being wasted due to retention. Correspondingly, a transfer reminder message is generated and pushed to remind medical staff to initiate a transfer application.

[0063] In this embodiment, the matching degree is equal to the probability score of the corresponding blood bag being used by the corresponding medical institution within the remaining valid time. The probability score of the blood bag being used by the medical institution within the remaining valid time can be obtained by inputting it by medical staff. The higher the probability score, the greater the matching degree between the corresponding blood bag and the corresponding medical institution; the lower the probability score, the lower the matching degree between the corresponding blood bag and the corresponding medical institution.

[0064] It should be noted that the medical institution storing the blood bags is the medical institution that stores the blood bags. The monitoring module can update the matching degree of each blood bag in real time, or it can calculate the matching degree between the blood bag and the medical institution at a preset update cycle.

[0065] It should be noted that upon receiving a transfer request, medical staff at each medical institution can choose the blood bags to be transferred from the request, or the transfer can be automatically allocated based on the compatibility between the blood bags and each medical institution, or other feasible implementation methods can be used. This application does not further limit the subsequent response method for transfer requests.

[0066] In this embodiment, the method for calculating the probability score of the corresponding blood bag being used by the corresponding medical institution within the remaining effective time includes:

[0067] ;

[0068] Where B represents the input blood bag, H represents the input medical institution, and S represents the input medical institution. p This represents a probability score, where position represents the sequence number of the corresponding blood bag in the usage queue of the corresponding medical institution, and N is the number of the blood bag. H This represents the demand for the same type of blood bags by the corresponding medical institution, and e represents the base of the natural logarithm.

[0069] It should be noted that the specific operations of the usage queue and position can be pre-set according to the blood bag usage sorting strategy of the medical institution. For example, if the sorting strategy of prioritizing the use of blood bags with the shortest remaining validity period is selected as the corresponding medical institution, the position can include retrieving all blood bags of the same type after the corresponding blood bag is transferred to the corresponding medical institution, and arranging them in ascending order of remaining validity period to obtain the usage queue. Alternatively, a FIFO blood bag usage sorting strategy can be selected, and the position is sorted based on the blood bag's arrival time.

[0070] It should be noted that when calculating the probability score between blood bags and non-storage medical institutions, the queue number must take into account the scheduling time from blood bags to non-storage medical institutions. Scheduling time includes transportation time and warehousing time, but is not limited to these. For example, if the storage medical institution for blood bag B is medical institution H0, the scheduling time from medical institution H0 to medical institution H1 is 1 day, and the remaining valid time for blood bag B is 3 days, then when obtaining the corresponding usage queue number for blood bag B in medical institution H1, on the first day of blood bag B's scheduling, medical institution H1 should consider storing blood bags in its institution, but should not sort blood bag B. Only on the second and third days after the scheduling of blood bag B begins should medical institution H1 add the blood bag to the sorting queue. However, when calculating the probability score between blood bags and storage medical institutions, the queue number does not need to consider the scheduling time. For example, when obtaining the corresponding usage queue number for blood bag B in medical institution H0, the sorting of blood bag B should be considered for all three days of medical institution H0.

[0071] It should be noted that the demand for the same type of blood bags from corresponding medical institutions can be pre-set within the system, and the demand can be calculated by multiplying the average demand by the remaining effective duration of the blood bags. Alternatively, a demand prediction model can be built based on historical usage data, and the demand for the same type of blood bags from corresponding medical institutions can be obtained through the output of the demand prediction model, or other feasible implementation methods can be used. This application does not further limit the specific method of obtaining the demand.

[0072] In this embodiment, refer to the appendix. Figure 5 As shown, upon receiving a transfer request from another medical institution, the inter-hospital transfer submodule further obtains the safety threshold for the corresponding category of blood bags at the current medical institution. Based on the matching degree with the current medical institution, it sorts all blood bags of the same type stored at the current medical institution, and in descending order of matching degree with the current medical institution, it adds the number of blood bags corresponding to the safety threshold to the safety pool. The remaining blood bags of the same type are added to the candidate pool, and the blood bags in the candidate pool serve as candidate blood bags for the institution that initiated the transfer request. The inter-hospital transfer submodule sets the scheduling status of blood bags in the safety pool to prohibited and sets the scheduling status of blood bags in the candidate pool to allowed.

[0073] It should be noted that the security threshold can be obtained through pre-setting.

[0074] In this embodiment, the system further includes: obtaining the average consumption of blood bags of the corresponding category at the current medical institution; sorting the scheduling time from the current medical institution to all candidate institutions in descending order, taking the first half of the scheduling time to calculate the average time, and rounding up if the number of candidate institutions is odd to ensure that at least one is selected; calculating the lower limit of the corresponding safety threshold based on the average time and the average consumption, and when setting the safety threshold, its value is not less than the lower limit.

[0075] It should be noted that the average consumption can be obtained through a pre-set method, or by reading the historical consumption records of the current medical institution in the corresponding blood bag category from the blood bag consumption database and continuously accumulating the consumption data according to a preset period to obtain the average blood bag consumption of the medical institution in the corresponding category, so as to adapt to the changes in blood bag consumption at different times.

[0076] It should be noted that the candidate institutions are medical institutions other than the current medical institution. The system has a built-in path duration table of the scheduling network, and the path market table is used to store the scheduling duration between various medical institutions. The system retrieves the scheduling duration from the current medical institution to the corresponding candidate institution from the path duration table.

[0077] In this embodiment, the system further includes a scheduling engine. The scheduling engine sorts all blood bags in the candidate pool according to their matching degree with the initiating organization of the blood bag transfer application based on the number of applications for the corresponding category of blood bags in the blood bag transfer application. It then selects the blood bags with the highest number of applications as the target blood bags for scheduling, generating a scheduling plan. The scheduling plan includes the blood bags to be scheduled, the medical institution storing the blood bags, and the medical institution to which the blood bags are intended to be transferred.

[0078] It should be noted that if the total number of medical institutions is N, then there are a total of N-1 candidate pools. If there is a medical institution whose number of blood bags of the same type is not greater than the corresponding safety threshold, then the corresponding candidate pool is empty.

[0079] In this embodiment, the operation node further includes an inter-hospital transfer node. The inter-hospital transfer node is a sub-module corresponding to the execution module, used to initiate transfer requests. The monitoring sub-module is also used to determine whether the number of blood bags of each type exceeds the safety threshold. If the number of blood bags drops to the safety threshold, a transfer reminder message is generated and pushed to alert medical staff. Medical staff can initiate transfer requests through the inter-hospital transfer module.

[0080] In the fourth embodiment, compared to the third embodiment, the matching degree is equal to the product of the probability score and the indicative function. If the remaining valid time after the corresponding blood bag is transferred to the corresponding medical institution is greater than 0, the indicative function is set to 1; if the remaining valid time after the corresponding blood bag is transferred to the corresponding medical institution is not greater than 0, the indicative function is set to 0. The indicative function I can be expressed as:

[0081] ;

[0082] ;

[0083] Among them, T usable T represents the remaining validity period after the corresponding blood bag is transferred to the corresponding medical institution. remaining T represents the remaining effective duration of the corresponding blood bag. scheduling This indicates the scheduling time for the corresponding blood bag to be transferred to the corresponding medical institution.

[0084] In the fifth embodiment, compared to the fourth embodiment, the matching degree is equal to the product of the indicative function and the scoring result. Evaluation components are obtained based on all evaluation indicators, and the scoring result is obtained based on the linear weighting of these evaluation components. The evaluation indicators include the probability score and the scheduling cost score. The scheduling cost score describes the scheduling cost of moving the corresponding blood bag from the storage medical institution to the corresponding medical institution. A higher scheduling cost corresponds to a lower scheduling cost score and a lower matching degree; conversely, a lower scheduling cost corresponds to a higher scheduling cost score and a higher matching degree.

[0085] It should be noted that the scheduling cost can be obtained based on transportation costs, such as vehicle costs and labor costs.

[0086] In this embodiment, for ease of calculation, the unit price of vehicles and labor used for dispatching between medical institutions is preset to be the same. Therefore, the dispatching cost is mainly affected by the transportation distance; the longer the transportation distance, the higher the dispatching cost, and the lower the corresponding dispatching cost score; conversely, the shorter the transportation distance, the lower the dispatching cost, and the lower the corresponding dispatching cost score. Therefore, the dispatching cost score S... d The calculation methods include:

[0087] ;

[0088] It should be noted that D represents the transportation distance between the storage medical institution and the medical institution to which the goods are to be transferred. max This indicates the maximum transport distance between two medical institutions within the region, which can be obtained through pre-setting.

[0089] In the sixth embodiment, the scoring result is obtained based on the product of the probability score and the scheduling cost score. The method for calculating the matching degree includes:

[0090] ;

[0091] It should be noted that the evaluation indicators for the scoring results are not limited to the probability score and the scheduling cost score, but can also be obtained based on other evaluation indicators.

[0092] See attached document Figure 6 As shown, this application provides an electronic device including a processor and a memory. The processor and the memory are interconnected and communicate with each other via a communication bus and / or other forms of connection mechanism (not shown). The memory stores a computer program executable by the processor. When the computing device is running, the processor executes the computer program to perform a system in any of the optional implementations of the above embodiments.

[0093] This application provides a storage medium in which, when the computer program is executed by a processor, it performs a system according to any optional implementation of the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0094] It should be understood that the disclosed system can be implemented in other ways, as illustrated in the embodiments provided in this application. The system embodiments described above are merely illustrative. For example, the division of modules is only a logical functional division, and in actual implementation, it can be divided in other ways. Furthermore, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Additionally, the coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces; the indirect coupling or communication connection between systems or units can be electrical, mechanical, or other forms.

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

[0096] Furthermore, the functional modules in the various embodiments of this application can be integrated together to form an independent part, or each module can exist independently, or two or more modules can be integrated to form an independent part.

[0097] Flowcharts are used herein to illustrate the steps of the methods according to embodiments of this disclosure. It should be understood that the preceding or following steps are not necessarily performed in exact order. Instead, the steps can be evaluated in reverse order or simultaneously. Furthermore, other operations can be added to these processes.

[0098] Unless otherwise defined, all terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains. It should also be understood that terms such as those defined in a common dictionary should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and not as having an idealized or highly formalized meaning, unless expressly defined herein.

[0099] The above provides a detailed description of a mobile terminal-based closed-loop management system for clinical blood transfusion processes. Specific examples have been used to illustrate the principles and implementation methods of this application. The descriptions of these embodiments are merely examples of this application and are intended to help understand the mobile terminal-based closed-loop management system for clinical blood transfusion processes. They are not intended to limit the scope of protection of this application. Furthermore, various modifications and variations can be made to this application by those skilled in the art. Any modifications or equivalent substitutions made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A mobile terminal based clinical blood transfusion process closed loop management system, characterized in that, The system comprises: a management module configured to preset operation nodes of blood bags and corresponding sequence constraints; an execution module comprising sub-modules configured to execute operation tasks of the corresponding operation nodes; a record module configured to update operation records of the blood bags based on the completed operation tasks; a verification module comprising an acquisition sub-module, a matching sub-module, and a record sub-module; wherein the acquisition sub-module is configured to acquire a unique identifier of a user and an operation node, and in response to a code scanning operation of the user on a blood bag, to acquire the latest operation record of the corresponding blood bag according to the code scanning result; the matching sub-module is configured to match the operation node of the user with the latest operation record of the blood bag based on the operation node and the sequence constraint, and if the matching is successful, to trigger the execution module and / or the record module, and if the matching fails, to generate and push operation exception information; the execution module further comprises a monitoring sub-module; the monitoring sub-module is configured to monitor the remaining valid time length of each blood bag, and to acquire the matching degree of each blood bag with each medical institution respectively; in all matching degrees of the same blood bag, if the matching degree of the blood bag with the storage medical institution is the smallest, to generate and push a call-out reminder information; the storage medical institution is a medical institution that saves the blood bag; wherein the evaluation index of the matching degree comprises a probability score of the corresponding blood bag being used by the corresponding medical institution within the remaining valid time length; the calculation method of the probability score comprises: ； Wherein, B represents blood bags, H represents medical institutions, S p represents the probability score, position represents the sequence number of obtaining the corresponding blood bag in the corresponding use queue of the corresponding medical institution, N H represents the demand of the corresponding medical institution for blood bags of the same category, e represents the base of natural logarithm.

2. The mobile terminal based clinical transfusion process closed loop management system of claim 1, wherein, the management module is further configured to preset process nodes and corresponding sequence constraints; the process nodes comprise an application node; the operation nodes comprise a blood allocation node and a cross-institution call-out node; the execution module comprises an application sub-module, a blood allocation sub-module, and a cross-institution call-out sub-module; the application sub-module is configured to acquire a blood transfusion application submitted by a user; the blood allocation sub-module is configured to establish an association between the blood transfusion application and the blood bag, and to set the scheduling state of the corresponding blood bag to prohibited; the cross-institution call-out sub-module is configured to generate and push a call-out exception information for the blood bag with the scheduling state of prohibited, and to generate a call-out application for the blood bag with the scheduling state of allowed.

3. The mobile terminal based clinical transfusion process closed loop management system of claim 2, wherein, The system further comprises: obtaining a score result of the corresponding blood bag and the corresponding medical institution based on all evaluation indexes; calculating the matching degree according to the product of the indicative function and the score result; if the remaining valid time length of the corresponding blood bag after being transferred into the corresponding medical institution is greater than 0, the indicative function takes the value of 1, and if the remaining valid time length of the corresponding blood bag after being transferred into the corresponding medical institution is not greater than 0, the indicative function takes the value of 0.

4. The mobile terminal based clinical transfusion process closed loop management system of claim 3, wherein, The evaluation index of the matching degree further comprises a scheduling cost of the corresponding blood bag being scheduled from the storage medical institution to the corresponding medical institution. 5.The mobile terminal based clinical transfusion process closed loop management system of claim 3, wherein, Upon receiving the call-in application, the cross-institution call-out sub-module is further configured to acquire a safety threshold of the current medical institution for the corresponding category of blood bags, to sort all blood bags of the same category stored in the current medical institution based on the matching degree with the current medical institution, to take the blood bags corresponding to the safety threshold in number into a safety pool in the order from large to small of the matching degree, to take the remaining blood bags of the same category into a candidate pool, and to take the blood bags in the candidate pool as candidate blood bags of the initiating institution of the call-in application.

6. The mobile terminal based clinical transfusion process closed loop management system of claim 5, wherein, The system further comprises a scheduling engine configured to take the blood bags with higher matching degrees with the initiating institution from all candidate pools as target scheduling blood bags according to the application quantity of the corresponding category of blood bags in the call-in application, and to generate a scheduling scheme. 7.The mobile terminal based clinical transfusion process closed loop management system of claim 5, wherein, The system further comprises: obtaining a consumption average of the current medical institution for the blood bags of the corresponding category; sorting the scheduling time lengths of the current medical institution to all candidate institutions from small to large, and taking the first half of the scheduling time lengths to calculate a time length average; and calculating a lower limit of the value of the corresponding safety threshold according to the time length average and the consumption average.

8. The mobile terminal based clinical transfusion process closed loop management system of claim 7, wherein, The operation node further comprises a cross-hospital transfer-in node, and the execution module further comprises a cross-hospital transfer-in submodule. The cross-hospital transfer-in submodule is configured to initiate a transfer-in application. The monitoring submodule is further configured to monitor the quantity of blood bags of each category. If there is a category in which the quantity of blood bags decreases to the safety threshold, a transfer-in reminder information is generated and pushed.

Images