Packaging system of intelligent operation kit

Abstract

The invention provides a packaging system of an intelligent operation kit. The packaging system comprises an operating room management terminal cluster, a packaging robot cluster and a surgical instrument database. The operating room management terminal cluster comprises a main control terminal node and a standby terminal node. The master control terminal node receives a surgical instrument configuration instruction, generates an instrument configuration log file and copies the instrument configuration log file to the standby terminal node. And the standby terminal node monitors the operation state of the main control terminal, and if the main control terminal is abnormal, the cached instrument configuration log file is sent to the corresponding packaging robot node. And the packaging robot node generates an instrument packaging instruction based on the instrument configuration log file, performs processing in batches, and updates the surgical instrument database. According to the system, automatic and intelligent packaging of the surgical instruments can be achieved, the packaging efficiency and accuracy are improved, the reliability and stability of the system are enhanced, instrument omission or errors caused by manual misoperation are reduced, and the efficiency and safety of surgical preparation are improved.

Description

Technical Field

[0001] This application relates to the field of medical surgical instrument management technology, and more specifically, to a packaging system for an intelligent surgical kit. Background Technology

[0002] In existing surgical instrument packing procedures, the configuration of surgical packs mainly relies on manual verification of the instrument list. This traditional operating mode has the following technical drawbacks: First, due to the dynamic changes in instrument configuration requirements for different surgical types, manual verification is prone to mismatches in instrument type or quantity. Second, the instrument packing process requires strict adherence to aseptic techniques and a specific placement order, which is difficult to guarantee through manual operation. Third, when the main control system malfunctions, the existing backup system lacks the ability to proactively trigger packing instructions, leading to surgical delays.

[0003] While existing solutions attempt to match surgical types using a static instrument database, they still cannot effectively address configuration errors caused by real-time fluctuations in instrument inventory and sudden changes in surgical plans. Particularly in scenarios such as instrument sterilization or intraoperative instrument additions, the system struggles to adjust packaging plans in a timely manner. Furthermore, traditional systems suffer from response delays in backup node switching and command synchronization, failing to meet the stringent requirements of operating rooms for timely instrument package delivery.

[0004] To address the aforementioned issues, existing technologies urgently need improvement. Summary of the Invention

[0005] The purpose of this application is to provide a smart surgical pack packaging system and its control method, which has the advantages of improving the accuracy of instrument configuration, ensuring system fault tolerance, and realizing dynamic packing scheduling.

[0006] This application provides a packaging system for intelligent surgical kits, with the following technical solution: The packaging system for intelligent surgical kits includes: various operating room management terminal clusters, a packaging robot cluster, and a surgical instrument database. The packaging robot cluster includes various packaging robot nodes, and each packaging robot node corresponds to one operating room management terminal cluster within the various operating room management terminal clusters. The operating room management terminal cluster includes a master control terminal node and backup terminal nodes. For each operating room management terminal cluster, the operating room management terminal cluster is configured as follows: the master control terminal node is configured to perform the following replication steps: receiving preset surgical instrument configuration instructions and generating an instrument configuration log file corresponding to the surgical instrument configuration instructions; and... The instrument configuration log file is copied to the backup terminal nodes included in the operating room management terminal cluster. The backup terminal nodes are configured to perform the following synchronization steps: store the instrument configuration log file copied from the master terminal node to a preset cache stack; monitor the operating status of the master terminal node to obtain terminal status monitoring information; in response to determining that the terminal status monitoring information indicates an abnormal operation of the master terminal, send the instrument configuration log file at the top of the preset cache stack to the packaging robot node in the packaging robot cluster corresponding to the operating room management terminal cluster; the packaging robot node is configured to perform the following batch packaging process: generate individual instrument packaging instructions based on the instrument configuration log file sent by the backup terminal node; and execute each instrument packaging instruction in batches to update the surgical instrument database.

[0007] Furthermore, this application proposes that the master control terminal node is further configured to receive preset surgical instrument configuration instructions and generate an instrument configuration log file corresponding to the surgical instrument configuration instructions through the following steps: receiving surgical instrument list data and surgical type codes from the surgical scheduling system as surgical instrument configuration instructions within a preset time period; converting the surgical instrument configuration instructions into various instrument configuration data units, wherein each instrument configuration data unit corresponds to one data point in each surgical instrument list data and each surgical type code; storing each instrument configuration data unit in a preset log file; and determining the preset log file storing each instrument configuration data unit as the instrument configuration log file corresponding to the surgical instrument configuration instructions.

[0008] Furthermore, this application also proposes that the master control terminal node is further configured to copy the instrument configuration log file to the backup terminal nodes included in the operating room management terminal cluster through the following steps: transmitting the instrument configuration log file to the backup terminal nodes included in the operating room management terminal cluster in real time through a pre-configured dual-machine hot standby synchronization mechanism.

[0009] Furthermore, this application proposes that the backup terminal node is further configured to monitor the operating status of the master terminal node through the following steps to obtain terminal status monitoring information, including: receiving a heartbeat detection signal sent by the master terminal node; and in response to not receiving a heartbeat detection signal three times consecutively, determining the information indicating abnormal operation of the master terminal as terminal status monitoring information.

[0010] Furthermore, this application proposes that the packaging robot node be further configured to generate various device packaging instructions based on the device configuration log file sent by the backup terminal node through the following steps: determining each device configuration data unit included in the device configuration log file as a configuration unit to be processed, wherein each configuration unit in the configuration unit to be processed includes a device type code, a device quantity parameter, and a surgery type code; for each configuration unit in the configuration unit to be processed, performing the following conversion steps: determining the device type code included in the configuration unit as an index code; querying the packaging instruction template corresponding to the index code from the preset device packaging rule base to obtain the target packaging template; writing the device quantity parameter and surgery type code included in the configuration unit into the corresponding fields of the target packaging template; and marking the updated target packaging template as a device packaging instruction.

[0011] Furthermore, this application proposes that the packaging robot node be further configured to perform batch execution processing of various instrument packaging instructions through the following steps to update the surgical instrument database: for each instrument packaging instruction, classify it according to the instruction type label, wherein the instruction type label is one of the following: instrument replenishment instruction, instrument replacement instruction, and instrument withdrawal instruction; determine the various instrument packaging instructions into a packaging instruction set; determine the various instrument packaging instructions in the packaging instruction set with the instruction type label of instrument replenishment instruction as the first execution batch; determine the various instrument packaging instructions in the packaging instruction set with the instruction type label of instrument replacement instruction as the second execution batch; determine the various instrument packaging instructions in the packaging instruction set with the instruction type label of instrument withdrawal instruction as the third execution batch; and perform batch instrument packaging operations based on the first execution batch, the second execution batch, and the third execution batch, and update the surgical instrument database.

[0012] Furthermore, this application proposes that the master control terminal node is further configured to receive surgical instrument list data and surgical type codes from the surgical scheduling system within a preset time period through the following steps: reading the electronic tag data of the surgical instrument storage cabinet through an RFID scanning device; obtaining the standard configuration parameters of the corresponding instruments from the surgical instrument database based on the electronic tag data; matching the standard configuration parameters with a preset surgical rule base to generate surgical instrument list data; receiving surgical type codes sent by the doctor's terminal; and integrating the surgical instrument list data and surgical type codes into surgical instrument configuration instructions.

[0013] Furthermore, this application also proposes that the packaging robot node be further configured to perform a verification operation before writing the device quantity parameters included in the configuration unit into the target packaging template through the following steps: performing verification based on a preset device quantity verification rule, which is defined as follows: if the actual device quantity is greater than or equal to the standard minimum configuration quantity, the verification passes; if the actual device quantity is less than the standard minimum configuration quantity, the verification fails; in response to successful verification, the parameter writing operation is performed; in response to failed verification, a device shortage alarm is triggered and the current instruction generation is stopped.

[0014] Furthermore, this application also proposes that the packaging robot node is further configured to query the packaging instruction template from the preset instrument packaging rule library through the following steps: calculating the instrument packaging priority based on the surgical urgency coefficient, wherein the priority calculation rule is: the instrument packaging priority is equal to the surgical grade weight value multiplied by the emergency surgery coefficient; and selecting the corresponding level of packaging instruction template from the preset instrument packaging rule library according to the calculated instrument packaging priority.

[0015] Furthermore, this application proposes that the packaging robot node be further configured to perform batch instrument packaging operations through the following steps: for each instrument packaging instruction in the first execution batch, control the robotic arm to perform an instrument picking operation and update the inventory record in the surgical instrument database; for each instrument packaging instruction in the second execution batch, perform an instrument replacement operation and update the instrument status flag in the surgical instrument database; for each instrument packaging instruction in the third execution batch, perform an instrument retrieval operation and update the instrument traceability log in the surgical instrument database; generate a surgical package integrity report and send the surgical package integrity report to the nurse station terminal.

[0016] As can be seen from the above, the intelligent surgical pack packaging system and its control method provided in this application effectively solve the problems of manual verification error and system fault tolerance delay through the collaborative configuration of the main control terminal and the backup terminal, the real-time synchronization of the instrument configuration log, and the automatic instruction switching under abnormal conditions. It has the advantages of improving the accuracy of instrument configuration, ensuring the fault tolerance of the system, and realizing dynamic packing scheduling. Attached Figure Description

[0017] The above and other objects, features, and advantages of exemplary embodiments of the present invention will become readily apparent from the following detailed description taken in conjunction with the accompanying drawings. Several embodiments of the invention are illustrated in the drawings by way of example and not limitation, wherein: Figure 1 This is a schematic diagram of the packaging system for an intelligent surgical pack provided in an embodiment of the present invention. Detailed Implementation

[0018] The technical solutions 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 the embodiments. The components of this application described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, 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 represents selected embodiments of this application. 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. It should be noted that similar reference numerals and letters in the following drawings indicate similar items; therefore, once an item is defined in one drawing, it does not need to be further defined and explained in subsequent drawings. Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0019] In existing technologies, traditional surgical instrument packaging processes rely on manual checklist verification, which suffers from insufficient dynamic adaptability, lack of operational standardization, and weak emergency error tolerance mechanisms. Manual operation struggles to adapt in real-time to changes in instrument configuration due to differences in surgical types; for example, the types and quantities of instruments required for cardiac surgery differ significantly from those required for orthopedic surgery. When the main control terminal malfunctions, the backup system cannot proactively trigger packaging instructions, leading to delays in surgical package delivery. To address the aforementioned issues, the inventors discovered that existing systems lack a data synchronization mechanism between primary and backup nodes, hindering rapid switching of the operating entity in case of failure. By analyzing the dynamic characteristics of surgical instrument configuration, a log-driven instruction generation system needs to be established to ensure data consistency between primary and backup nodes. Furthermore, considering the timing requirements of instrument packaging operations, instruction batch processing logic needs to be designed to match the database update rhythm. Therefore, this application proposes a packaging system for intelligent surgical kits, including an operating room management terminal cluster 101, a packaging robot cluster 102, and a surgical instrument database 103. The operating room management terminal cluster comprises a master control terminal node and backup terminal nodes, with each packaging robot node corresponding to one operating room management terminal cluster. The master control terminal node receives surgical instrument configuration instructions and generates an instrument configuration log file, which is then copied to the backup terminal node. The backup terminal node stores the log file in a preset cache stack, monitors the master control terminal's operating status, and sends the top log file to the corresponding packaging robot node in case of an anomaly. The packaging robot node generates instrument packaging instructions based on the log file, performs batch processing, and updates the surgical instrument database. The operating room management terminal cluster refers to a collaborative control system composed of a main control terminal and backup terminals, which can be implemented using a dual-server architecture to ensure continuous instruction processing. The packaging robot cluster refers to an execution unit consisting of multiple independently operating automated packaging devices, which can be implemented using a robotic arm and conveyor belt integrated device, used for physically performing instrument sorting and packaging operations. The instrument configuration log file is a structured data file recording the type, quantity, and corresponding surgical code of surgical instruments, which can be implemented using JSON or XML format, used for standardized transmission of configuration parameters. The preset cache stack is a temporary storage area for storing log files according to a last-in-first-out principle, which can be implemented using an in-memory database, used to prioritize the processing of the latest configuration data. Terminal status monitoring information refers to detection signals reflecting the operating status of the main control terminal, which can be implemented using a heartbeat mechanism to trigger fault switching logic. Specifically, after receiving surgical instrument configuration instructions, the master control terminal node converts them into a structured log file and synchronizes it to the backup terminal node via a dual-machine hot standby mechanism. The backup terminal node continuously monitors the master control terminal's heartbeat signal. When it detects three consecutive signal loss, it determines that the master control terminal is abnormal and immediately retrieves the latest log file from the cache stack. The packaging robot node parses the received log file, matches it to a preset packaging rule template according to the instrument type code, and generates executable instructions containing quantity parameters and surgical codes. After classifying the instructions into replenishment, replacement, and withdrawal types, the robot arm is controlled in batches to perform instrument picking, replacement, and retrieval operations, synchronously updating the database inventory status and instrument traceability information. Compared to existing technologies, traditional systems rely on a single control terminal to process commands and lack a fault response mechanism. This solution constructs a redundant architecture through a primary and backup terminal cluster, combined with a cache stack storage and status monitoring mechanism, to achieve a 10-second fault switching response. Existing technologies use static configuration templates, which cannot adapt to dynamic surgical requirements. This solution dynamically generates commands through log files, combined with batch processing logic, to ensure precise matching between instrument configuration and surgical type. Through the above technical solution, this application automatically switches to a backup node and sends the latest configuration instructions when the main control terminal fails, eliminating surgical delays caused by system interruptions. Standardized log files drive instruction generation, avoiding instrument mismatch and quantity errors caused by manual operation. A batch processing mechanism for instructions ensures strict synchronization between database updates and physical packaging operations, maintaining the real-time accuracy of instrument inventory data.

[0020] This application further proposes that the master control terminal node receives preset surgical instrument configuration instructions and generates corresponding instrument configuration log files through the following steps: receiving various surgical instrument list data and various surgical type codes from the surgical scheduling system as surgical instrument configuration instructions within a preset time period; converting the surgical instrument configuration instructions into various instrument configuration data units, wherein each instrument configuration data unit corresponds to a surgical instrument list data or surgical type code; storing each instrument configuration data unit to a preset log file; and determining the preset log file storing the data units as the instrument configuration log file. The preset time period refers to the data reception window set by the system. This can be implemented using a timed data synchronization interface between the surgical scheduling system and the main control terminal to ensure the timeliness of surgical instrument configuration instructions. The instrument configuration data unit refers to a structured data record unit, which can be implemented by encapsulating a single surgical instrument list data entry and its corresponding surgical type code in JSON format to eliminate mixed data parsing errors. The preset log file refers to a data container with a fixed storage format, which can be implemented using a timestamp-named binary file combined with a circular buffer mechanism to build a traceable configuration record chain. Specifically, after receiving the raw configuration instructions from the surgical scheduling system, the master control terminal node first uses a data parsing module to break down the mixed instructions, which contain multiple instrument entries and surgical type codes, into independent data units. Each data unit carries a single instrument type code, quantity parameters, and its associated surgical type identifier, forming a discrete configuration record. These discrete units are sequentially written to independent storage blocks of a pre-defined log file, and an index table in the file header establishes a mapping relationship between data units and physical storage locations. This forms a structured log file, providing a configuration data source accurate to individual instruments for the subsequent packaging robot. Compared to existing technologies, traditional methods, which rely on manual input or batch import to process instrument configuration data, are prone to errors in matching instrument types and quantities due to mixed data formats. For example, existing patent CN112489XXXA directly stores the entire batch of instruments into the database, failing to distinguish configuration differences for different surgical types. This solution establishes a discretized data unit conversion mechanism, giving each instrument configuration item an independent data structure and associated identifier, fundamentally avoiding data cross-contamination. Through the above technical solution, this application achieves precise parsing and storage of surgical instrument configuration instructions, ensuring a strict binding relationship between each instrument type code and its corresponding quantity parameters and surgical type code. In scenarios where cardiac surgery requires a high-frequency electrosurgical unit while orthopedic surgery requires a bone drill, it can accurately distinguish the instrument configuration requirements for different surgical types, avoiding instrument mismatch issues caused by data mixing. Simultaneously, by constructing structured log files, it provides a verifiable configuration data source for the instrument packaging process, reducing the operational risks of manual verification.

[0021] This application further proposes that the master control terminal node transmits the instrument configuration log file to the backup terminal nodes included in the operating room management terminal cluster in real time through a pre-configured dual-machine hot standby synchronization mechanism. The dual-machine hot standby synchronization mechanism refers to the real-time data synchronization channel established between the master control terminal node and the standby terminal node. Specifically, it can be implemented using real-time data replication technology based on the TCP / IP protocol. This mechanism continuously monitors the data update status of the master control terminal node to ensure that the log file is transmitted immediately after its generation. Pre-configuration means that the parameters and communication paths of the dual-machine hot standby synchronization mechanism are deployed before the system runs. Specifically, it can use XML configuration files to define the synchronization frequency, data verification rules, and fault switching thresholds. For example, setting the transmission delay threshold to no more than 50 milliseconds ensures that the data transmission channel between the master and standby nodes is immediately available. Specifically, when the master terminal node generates the device configuration log file, the dual-machine hot standby synchronization mechanism uses memory mirroring technology to map the file content to the cache area of ​​the standby terminal node in real time. During this process, the data writing operations of the master terminal node and the data receiving operations of the standby terminal node remain synchronized, ensuring that the standby terminal node's cache stack always stores the latest version of the log file. Furthermore, the log file transmission process adopts an incremental synchronization mode, transmitting only newly added or modified data units, thereby reducing network bandwidth consumption. When the master terminal node experiences a malfunction, the standby terminal node can directly access the synchronized complete log file in its cache stack without waiting for data retransmission or manually triggering a recovery process. Compared to existing technologies, traditional backup systems typically employ timed batch synchronization or manually triggered synchronization mechanisms, such as performing data backups every 15 minutes. This results in outdated versions of log files stored on the backup nodes. This solution, however, eliminates the data synchronization time lag through a real-time transmission mechanism. This ensures that when the primary control terminal node fails, the backup node can immediately obtain the latest configuration data, avoiding delays in generating packaging instructions due to data loss. Through the above technical solution, this application ensures that the backup terminal node can directly obtain the real-time updated instrument configuration log file when the main control terminal node is abnormal, thereby quickly generating accurate packaging instructions. Furthermore, through the pre-configured stable transmission channel, the risk of transmission interruption caused by the temporary establishment of communication links in traditional solutions is effectively avoided, ensuring that the surgical instrument packaging process can still be executed continuously in the event of a main control system failure, ultimately achieving on-time delivery of surgical packages.

[0022] This application further proposes that the backup terminal node is configured to monitor the operational status of the master terminal node through the following steps: receiving a heartbeat detection signal sent by the master terminal node; and in response to three consecutive failures to receive a heartbeat detection signal, determining information indicating abnormal operation of the master terminal as terminal status monitoring information. The heartbeat detection signal refers to the status acknowledgment signal periodically sent by the master control terminal node. This can be implemented using the TCP protocol's heartbeat packet mechanism, sending data packets at fixed time intervals to maintain the communication link's activity, thereby establishing a real-time status monitoring channel between the master control terminal and the backup terminal. Three consecutive missed receptions mean that the backup terminal node fails to capture the heartbeat detection signal within three preset consecutive detection periods. This can be implemented using a sliding window counting algorithm, accumulating the number of signal losses to determine if the master control terminal has experienced a persistent fault. This mechanism avoids misjudgments caused by momentary network jitter by setting a three-consecutive-detection threshold. Specifically, the backup terminal node continuously monitors the operating status of the master terminal node by receiving heartbeat detection signals from it. When the master terminal node experiences a heartbeat signal interruption due to hardware failure or software crash, the backup terminal node starts a sliding window counter to accumulate the number of signal loss attempts. If no heartbeat signal is received within three consecutive detection cycles, the master terminal is deemed to be malfunctioning. This judgment logic ensures the accuracy of status monitoring by eliminating intermittent communication interference. Upon confirming the master terminal's malfunction, the backup terminal node immediately triggers a system switchover process, sending the cached instrument configuration log file to the packaging robot node, thereby ensuring the continuity of the surgical instrument packaging process. Compared to existing technologies, which typically trigger alarms upon a single lost heartbeat signal, this approach is prone to erroneous handover operations due to network fluctuations. Our solution, however, uses a three-consecutive-signal-loss-criteria approach to effectively filter out momentary communication anomalies and reduce the probability of false alarms. Furthermore, existing technologies lack proactive monitoring mechanisms for backup terminals, requiring manual intervention for handover after a primary terminal failure. Our solution, through automated status monitoring and judgment mechanisms, reduces system handover response time to the second level. Through the above technical solution, this application achieves real-time and reliable monitoring of the main control terminal's operating status, and quickly triggers backup node switching when the main control terminal experiences a continuous failure, avoiding system downtime caused by delays due to manual intervention. This mechanism balances response speed and system stability through a three-consecutive-signal-loss judgment condition, ensuring that the surgical instrument packaging process can still be executed according to the preset configuration even when the main control terminal malfunctions.

[0023] This application further proposes a method for a packaging robot node to generate various device packaging instructions based on a device configuration log file sent by a backup terminal node, including: determining each device configuration data unit included in the device configuration log file as a configuration unit to be processed, wherein each configuration unit includes a device type code, a device quantity parameter, and a surgery type code; for each configuration unit, determining the device type code as an index code; querying the packaging instruction template corresponding to the index code from a preset device packaging rule base to obtain a target packaging template; writing the device quantity parameter and surgery type code into the corresponding fields of the target packaging template; and marking the updated target packaging template as a device packaging instruction. The device configuration data unit refers to a data structure extracted from the device configuration log file that contains complete parameters for a single device type. This can be implemented using JSON objects, with each object containing device type code, quantity parameters, and surgical type code fields to ensure that configuration parameters for each device type are processed independently. The index code is a unique identifier for the device type used to match the preset rule base. This can be implemented using a 12-digit numeric code defined by the International Medical Device Coding System (IMDS), allowing for quick location of the corresponding packaging rule. The preset device packaging rule base is a database storing the association between device types and packaging operations. This can be implemented using a relational database table structure, with each table entry containing device type code, packaging order rules, and aseptic processing requirements fields, used to standardize the generation of instruction templates. The corresponding field in the target packaging template refers to the parameter filling positions reserved in the template. This can be implemented using placeholder tags in an XML template, dynamically generating executable instructions by replacing the tag content. Specifically, the instrument configuration log file is split into multiple independent configuration units, each carrying the code, quantity, and surgical type information for a specific instrument type. By using the instrument type code as an index, the corresponding packaging template is retrieved from the rule base. For example, the template for orthopedic surgical drills includes independent packaging requirements and shockproof packaging steps. When the quantity parameter is written to the quantity field of the template, the required number of packaging layers can be automatically calculated; when the surgical type code is written to the priority field, the packaging order can be adjusted to meet the needs of emergency surgeries. The updated template is converted into machine-readable instructions, such as robotic arm grasping path codes or packaging machine temperature parameters, ensuring that each step is executed according to preset rules. Compared to existing technologies, current methods rely on manual searching of instrument parameters and packaging rules in multiple systems based on paper lists, which is prone to coding errors or rule matching omissions. This solution eliminates manual operations by automatically associating structured data units with a rule base. For example, surgical type codes and packaging priorities are directly associated in the configuration unit, avoiding errors in instrument packaging order caused by human judgment. Through the above technical solutions, this application achieves automated generation of instrument packaging instructions, ensuring that the packaging steps for each instrument type strictly adhere to aseptic techniques and placement order requirements. In dynamically configured scenarios, automatic matching of instrument quantity parameters with template fields avoids mismatches in instrument quantity caused by manual calculation errors. When dealing with different surgical types, automatic association between surgical type codes and packaging priorities ensures that emergency surgical instruments are packaged first, reducing surgical preparation delays.

[0024] This application further proposes classifying each instrument packaging instruction within each instrument packaging instruction according to an instruction type label, wherein the instruction type label is one of the following: instrument replenishment instruction, instrument replacement instruction, and instrument withdrawal instruction; determining each instrument packaging instruction into a packaging instruction set; determining each instrument packaging instruction in the packaging instruction set with the instruction type label of instrument replenishment instruction as the first execution batch; determining each instrument packaging instruction in the packaging instruction set with the instruction type label of instrument replacement instruction as the second execution batch; determining each instrument packaging instruction in the packaging instruction set with the instruction type label of instrument withdrawal instruction as the third execution batch; and performing batch-wise instrument packaging operations based on the first execution batch, the second execution batch, and the third execution batch, and updating the surgical instrument database.

[0025] The instruction type label is an identifier used to distinguish the type of instrument operation. This can be implemented using a preset field code, which maps to the instrument operation type, automatically marking operation attributes during the instruction generation phase. The packaged instruction set is an aggregate unit of instructions to be executed, which can be implemented using a dynamic linked list structure to store the categorized instruction data. Batch-based instrument packaging operations refer to executing different categories of instrument operations in a preset order. This can be implemented using a multi-threaded task queue mechanism, controlling the execution order by setting batch priorities.

[0026] Specifically, after the instrument packing instruction is generated, it is automatically categorized according to the operation type attribute. Replenishment instructions, which involve replenishing instrument inventory and directly affect the start of surgery, are therefore assigned to the first execution batch for priority processing. Replacement instructions involve updating instrument status, and withdrawal instructions involve the instrument retrieval process; both have a relatively low impact on the surgical progress and are assigned to subsequent execution batches. By dividing the instruction set into three independent batches, different types of instructions are assigned to independent execution queues, avoiding resource conflicts when concurrently executing the same instrument access operations. During execution, the robotic arm operation and database update adopt a transaction synchronization mechanism. After each batch is completed, a batch update of database records is automatically triggered to ensure that the inventory status and physical operations remain consistent in real time.

[0027] Compared to existing technologies, traditional packaging systems do not differentiate between instruction types, leading to mixed execution of replenishment, replacement, and withdrawal operations. This can easily cause conflicts in device access and delays in database updates. For example, in existing technologies, when replenishment and withdrawal instructions operate on the same device simultaneously, incorrect execution order may result in abnormal inventory data. This solution uses instruction classification and batch segmentation mechanisms to isolate different operation types, optimize the robotic arm's movement path and database transaction processing order, and reduce resource contention and operational conflicts.

[0028] Through the above technical solution, this application effectively solves the problem of low processing efficiency caused by conflicting execution sequences of packaging instructions for different medical devices, and achieves priority execution of critical operations through a classification and batch processing mechanism. Simultaneously, the transaction synchronization mechanism between database updates and physical operations avoids data inconsistencies caused by overlapping instruction execution, ensuring the real-time accuracy of medical device inventory status.

[0029] This application further proposes that the master control terminal node be further configured to receive surgical instrument list data and surgical type codes from the surgical scheduling system within a preset time period through the following steps: reading the electronic tag data of the surgical instrument storage cabinet through an RFID scanning device; obtaining the standard configuration parameters of the corresponding instruments from the surgical instrument database based on the electronic tag data; matching the standard configuration parameters with a preset surgical rule base to generate surgical instrument list data; receiving surgical type codes sent by the doctor's terminal; and integrating the surgical instrument list data and surgical type codes into surgical instrument configuration instructions. The RFID scanning device refers to a device that automatically collects instrument information through radio frequency identification technology. Specifically, it can be implemented using a UHF band RFID reader / writer, used to read the electronic tag data of instruments in the storage cabinet in real time, replacing manual recording. Electronic tag data refers to the encoded information of the RFID tags stored in the instrument storage cabinet, specifically implemented using the EPCC1G2 standard format, containing a unique instrument identifier and storage location code, used to accurately identify currently stocked instruments. Standard configuration parameters refer to the quantity and specifications of instruments in a sterilized state. Specifically, it can retrieve preset minimum configuration quantities and sterilization expiration dates from the surgical instrument database to verify whether the instruments meet the surgical use conditions. The preset surgical rule base is a database storing the instrument configuration requirements corresponding to different surgical types. Specifically, it can use a relational database to establish a mapping relationship between surgical type codes and instrument types and quantities, used to dynamically generate an instrument list suitable for specific surgeries. The surgical type code is a unique code identifying the surgical category, specifically implemented using the ICD-10 coding system, transmitted directly from the doctor's terminal to the main control terminal to avoid information transmission errors. Specifically, this technical solution automatically collects electronic tag data of instruments in the storage cabinet using an RFID scanning device, eliminating errors in instrument type or quantity that may occur with manual recording. Based on the electronic tag data, it retrieves the standard configuration parameters of the corresponding instruments from the surgical instrument database, ensuring that the instruments are within their sterilization period and that their quantity meets the minimum configuration requirements. The standard configuration parameters are then matched with surgical type-instrument mapping rules stored in a preset surgical rule base to dynamically generate a surgical instrument list that includes instrument type, quantity, and placement order. Simultaneously, it receives surgical type codes directly sent from the doctor's terminal, avoiding coding errors caused by manual translation. Finally, the instrument list data and surgical type codes are integrated to generate executable configuration instructions, forming a closed-loop processing flow from data acquisition to instruction generation. Compared to existing technologies, which rely on manual verification of paper lists against physical instruments, this solution addresses the risk of instrument mismatch. It utilizes RFID automatic data collection and database validation to achieve real-time verification of instrument configuration parameters; intelligent matching based on a surgical rule base dynamically generates an instrument list that meets specific surgical needs; and it directly transmits surgical type codes through the doctor's terminal, ensuring consistency between surgical classification information and clinical decisions. Through the above technical solutions, this application solves the problem of instrument configuration errors caused by the lack of dynamic adaptation, and achieves accurate matching between instrument list data and actual surgical needs. Automated data collection and intelligent rule matching eliminate instrument type mismatches and quantity errors caused by manual operation; a closed-loop data verification mechanism ensures that configuration instructions comply with sterilization specifications and surgical type requirements; and surgical codes are directly obtained from the clinical end, avoiding coding distortion during information transmission.

[0030] This application further proposes that the packaging robot node performs a verification operation before writing the device quantity parameters included in the configuration unit into the target packaging template: the verification is performed based on a preset device quantity verification rule, which is defined as follows: if the actual device quantity is greater than or equal to the standard minimum configuration quantity, the verification passes; if the actual device quantity is less than the standard minimum configuration quantity, the verification fails; in response to the verification passing, the parameter writing operation is performed; in response to the verification failing, a device shortage alarm is triggered and the current instruction generation is stopped. The instrument quantity verification rules refer to pre-defined logical conditions used to determine whether the actual inventory meets the minimum surgical requirements. These rules can be implemented using database queries and numerical comparison algorithms, ensuring instrument availability by comparing inventory data with configuration requirements in real time. The actual instrument quantity refers to the current available inventory of clean and sterile instruments, which can be obtained in real time through RFID scanning devices or a warehouse management system to dynamically reflect the instrument supply status. The standard minimum configuration quantity refers to the minimum quantity requirement for specific instruments for different types of surgeries, which can be extracted from the surgical rule base to ensure that packaging operations comply with clinical safety standards. The instrument shortage alarm is a warning signal triggered when an insufficient quantity of instruments is detected. This can be implemented using audible and visual alarm devices or system message push notifications to notify operators to replenish instruments promptly. Specifically, when the packaging robot node receives the instrument configuration data unit, it first retrieves the current actual inventory quantity from the warehouse management system. Simultaneously, based on the surgical type code, it extracts the minimum configuration standard for the corresponding instrument from a preset rule base. A real-time verification is performed through a numerical comparison module. If the actual inventory meets or exceeds the minimum standard, the instrument quantity parameter is written into the packaging template field. If the inventory is below the standard threshold, the instruction generation process is immediately terminated, and a shortage notification is sent to the nurse station. This verification process is embedded at the front end of the instruction generation stage, forming a mandatory verification mechanism to ensure that each packaging instruction undergoes inventory sufficiency verification before generation. Compared to existing technologies, traditional packaging systems generate instructions based solely on configuration requirements, failing to establish a dynamic link between inventory status and instruction generation, which easily leads to packaging failures or surgical interruptions. This solution, by introducing real-time inventory verification and a dual-path processing mechanism, proactively intercepts invalid requests during the instruction generation phase and simultaneously triggers an emergency response process, thus resolving the chain reaction of packaging errors caused by instrument shortages. Through the above technical solutions, this application effectively prevents invalid packaging operations caused by insufficient actual inventory, reduces the error rate of surgical pack configuration through a pre-verification mechanism, and enables rapid response to abnormal situations by using shortage alarms, thus ensuring the reliability and timeliness of the surgical instrument packaging process.

[0031] This application further proposes that the packaging robot node is configured to calculate the instrument packaging priority based on the surgical urgency coefficient. The priority calculation rule is to multiply the surgical grade weight value by the emergency surgery coefficient, and select the corresponding level of packaging instruction template from the preset instrument packaging rule library according to the calculated instrument packaging priority. Among them, the surgical urgency coefficient is a numerical parameter used to quantify the urgency of surgery. Specifically, it can be implemented using a preset urgency classification table. For example, emergency surgery, time-limited surgery, and elective surgery can be mapped to different coefficient values. This parameter can be used to dynamically adjust the response level of instrument packaging. Among them, the surgical grading weight value refers to the importance assessment index set according to the type of surgery. Specifically, it can be implemented by assigning corresponding values ​​to the surgical grading catalog issued by the National Health Commission. For example, the highest weight value is given to level 4 surgery, so that the equipment configuration for major surgeries receives higher processing priority. The emergency surgery coefficient is a dynamic variable that reflects the urgency of the surgery. It can be calculated using the reciprocal function of the remaining preparation time provided by the surgery scheduling system. The shorter the remaining time, the larger the coefficient value, ensuring that instrument packs close to the surgery time are given priority. The preset instrument packaging rule library refers to a database that stores operation templates corresponding to different priorities. Specifically, it can be implemented using a hierarchical index structure. For example, the templates can be divided into emergency mode, standard mode and delayed mode according to priority, with each mode corresponding to different robotic arm movement speed and packaging process parameters. Specifically, when the packaging robot node receives the instrument configuration log file, it first parses the surgery type code and retrieves the corresponding surgery's classification weight value by querying the surgery classification directory. Simultaneously, it obtains the estimated start time of the surgery from the surgery scheduling system and calculates an emergency surgery coefficient based on the difference between the current time and the estimated time. The classification weight value is multiplied by the emergency coefficient to obtain the instrument packaging priority value. The corresponding packaging instruction template is selected based on the threshold range of this value. For example, when the priority value exceeds the first threshold, the emergency mode template is invoked. This template increases the robotic arm's movement speed to the maximum and skips unnecessary quality inspection steps, thereby achieving rapid preparation of emergency surgical instrument packs. Compared to existing technologies, traditional methods allocate priorities based solely on surgical type or a single time parameter. For example, patent CN112489XXXA only categorizes processing order by surgical department, failing to consider the differences in urgency levels among surgeries within the same department. This solution calculates priorities using composite parameters, retaining the basic weight of surgical type while also incorporating time urgency parameters. This avoids excessive resource consumption for non-urgent level 4 surgeries due to reliance solely on surgical classification, while also preventing delays in processing low-level emergency surgeries. Through the above technical solution, this application can dynamically adjust the order of instrument packaging according to the actual urgency of the surgery, prioritize the supply of instruments for emergency and major surgeries when resources are limited, and ensure that surgeries of different priorities receive differentiated treatment procedures through graded template matching, effectively reducing delays in instrument preparation caused by unreasonable priority allocation.

[0032] This application further proposes a packaging robot node to perform batch instrument packaging operations: for each instrument packaging instruction in the first batch, the robot arm is controlled to perform an instrument picking operation and update the inventory record in the surgical instrument database; for each instrument packaging instruction in the second batch, an instrument replacement operation is performed and the instrument status flag in the surgical instrument database is updated; for each instrument packaging instruction in the third batch, an instrument retrieval operation is performed and the instrument traceability log in the surgical instrument database is updated; a surgical package integrity report is generated and sent to the nurse station terminal. The process includes several key elements: **Batch instrument packaging:** Executing instructions of different operation types in a preset order, typically using a priority queue scheduling algorithm to resolve database update conflicts. **Instrument retrieval:** Using a robotic arm to pick up designated instruments, implemented with a visual positioning and force feedback control system to ensure real-time alignment between instrument replenishment actions and inventory records. **Instrument replacement:** Removing instruments marked for replacement and replacing them with new ones, achieved using RFID technology to match instrument numbers and synchronously update instrument status markers to prevent the use of faulty instruments. **Instrument retrieval:** Transferring withdrawn instruments to a sterilization or storage area, using a path planning algorithm combined with an electronic tag scanner to record instrument flow information in the traceability log. **Surgical pack integrity report:** A verification file containing instrument configuration completion and operation timestamps, implemented using XML format to encapsulate data fields and transmit verifiable packaging results to the nursing station terminal. Specifically, when the main control terminal malfunctions, the backup terminal triggers a packing command transmitted to the corresponding packing robot node. The first batch of instrument replenishment commands uses a robotic arm to retrieve a specified number of instruments from the storage cabinet. Each retrieval operation sends an inventory deduction signal to the database, ensuring strict consistency between inventory data and physical quantity. The second batch of instrument replacement commands scans the electronic tags of the old instruments to verify their status. Once the replacement conditions are met, the usable status of the new instruments is activated, preventing the incorrect use of damaged or expired instruments. The third batch of instrument retrieval commands records the final location and operation time of the instruments during the retrieval process and writes this information to the traceability log field of the database, forming a complete instrument circulation record. After all batches of operations are completed, the system automatically generates a surgical pack integrity report containing an instrument configuration list, operation time, and execution status, which is transmitted to the nurse station terminal display interface via the hospital's internal network. Compared to existing technologies, traditional methods can only pause the packaging process when the main control terminal malfunctions, failing to differentiate the execution priorities of different operation types of instructions, resulting in the inability to synchronize inventory data, device status, and traceability information. This solution, through a batch processing mechanism, separates the replenishment, replacement, and withdrawal operations for execution, and links them to updates of inventory records, status markers, and traceability logs respectively, ensuring the accuracy and relevance of all data dimensions in the database even in emergency scenarios. Through the above technical solution, this application solves the problem of database update chaos caused by the disordered execution of instrument packing instructions when the system malfunctions, ensuring that instrument replenishment operations reflect inventory changes in real time, instrument replacement operations update status markers synchronously, and instrument withdrawal operations fully record traceability information. Simultaneously, by automatically generating and sending surgical pack integrity reports, the time delay of manual verification of packing results is eliminated, enabling medical staff to promptly confirm the surgical pack configuration status.

[0033] The above are merely embodiments of this application and are not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A packaging system for an intelligent surgical pack, characterized in that, The intelligent surgical pack packaging system includes: a cluster of management terminals for each operating room, a cluster of packing robots, and a database of surgical instruments. The packing robot cluster includes various packing robot nodes, and each packing robot node corresponds to one of the operating room management terminal clusters. The operating room management terminal cluster includes a master terminal node and a backup terminal node. For each operating room management terminal cluster in each operating room management terminal cluster, the operating room management terminal cluster is configured as follows: the master terminal node is configured to perform the following replication steps: receive preset surgical instrument configuration instructions, and generate an instrument configuration log file corresponding to the surgical instrument configuration instructions; Copy the instrument configuration log file to the backup terminal nodes included in the operating room management terminal cluster; The backup terminal node is configured to perform the following steps: Store the device configuration log file copied from the master control terminal node to the preset cache stack; Monitor the operational status of the main control terminal node to obtain terminal status monitoring information; In response to the determination that the terminal status monitoring information indicates an abnormal operation of the main control terminal, the instrument configuration log file at the top of the preset cache stack is sent to the packaging robot node in the packaging robot cluster corresponding to the operating room management terminal cluster. The packaging robot node is configured to perform the following batch packaging process: Based on the device configuration log file sent by the backup terminal node, generate packaging instructions for each device; The packaging instructions for each instrument are processed in batches to update the surgical instrument database.

2. The packaging system for the intelligent surgical pack according to claim 1, characterized in that, The master control terminal node is further configured to receive preset surgical instrument configuration instructions and generate an instrument configuration log file corresponding to the surgical instrument configuration instructions through the following steps: receiving a list of surgical instruments and codes of surgical types from the surgical scheduling system within a preset time period as surgical instrument configuration instructions; The surgical instrument configuration instructions are converted into individual instrument configuration data units, where each instrument configuration data unit corresponds to one data point in each surgical instrument list and each surgical type code. Store the configuration data units of each instrument to a preset log file; The preset log file storing the configuration data of each instrument is determined as the instrument configuration log file corresponding to the surgical instrument configuration instruction.

3. The packaging system for the intelligent surgical pack according to claim 1, characterized in that, The master terminal node is further configured to copy the instrument configuration log file to the backup terminal nodes included in the operating room management terminal cluster through the following steps: transmitting the instrument configuration log file to the backup terminal nodes included in the operating room management terminal cluster in real time through a pre-configured dual-machine hot standby synchronization mechanism.

4. The packaging system for the intelligent surgical pack according to claim 1, characterized in that, The backup terminal node is further configured to monitor the operating status of the master terminal node through the following steps to obtain terminal status monitoring information, including: receiving a heartbeat detection signal sent by the master terminal node; In response to three consecutive failures to receive a heartbeat detection signal, the information indicating abnormal operation of the main control terminal is identified as terminal status monitoring information.

5. The packaging system for the intelligent surgical pack according to claim 2, characterized in that, The packaging robot node is further configured to generate individual device packaging instructions based on the device configuration log file sent by the backup terminal node through the following steps: determining each device configuration data unit included in the device configuration log file as a configuration unit to be processed, wherein each configuration unit in the configuration unit to be processed includes a device type code, a device quantity parameter and a surgery type code; For each configuration unit in the configuration units to be processed, perform the following transformation steps: determine the instrument type code included in the configuration unit as the index code; The target packaging template is obtained by querying the packaging instruction template corresponding to the index code from the preset medical device packaging rule base; Write the instrument quantity parameters and surgical type codes included in the configuration unit into the corresponding fields of the target packaging template; Mark the updated target packaging template as an instrument packaging instruction.

6. The packaging system for the intelligent surgical pack according to claim 1, characterized in that, The packaging robot node is further configured to process each instrument packaging instruction in batches through the following steps to update the surgical instrument database, including: classifying each instrument packaging instruction according to the instruction type label, wherein the instruction type label is one of the following: instrument replenishment instruction, instrument replacement instruction, and instrument withdrawal instruction; The individual instrument packaging instructions are defined as a packaging instruction set; Each device packaging instruction in the packaging instruction set with the instruction type label "Device Supplement Instruction" is identified as the first batch of execution; Each device packaging instruction in the packaging instruction set with the instruction type label "device replacement instruction" is identified as the second execution batch. Each device packaging instruction in the packaging instruction set with the instruction type label "device withdrawal instruction" is identified as the third execution batch; Based on the first, second, and third execution batches, perform batch-by-batch instrument packaging operations and update the surgical instrument database.

7. The packaging system for the intelligent surgical pack according to claim 2, characterized in that, The master control terminal node is further configured to receive the list data of each surgical instrument and the code of each surgical type from the surgical scheduling system within a preset time period through the following steps, including: reading the electronic tag data of the surgical instrument storage cabinet through an RFID scanning device; Based on electronic tag data, the standard configuration parameters of the corresponding instruments are obtained from the surgical instrument database; The standard configuration parameters are matched with the preset surgical rule base to generate a list of surgical instruments. Receive the surgical type code sent by the doctor's terminal; The surgical instrument inventory data and surgical type codes are integrated into surgical instrument configuration instructions.

8. The packaging system for the intelligent surgical pack according to claim 5, characterized in that, Before writing the device quantity parameters included in the configuration unit into the target packaging template, the packaging robot node is further configured to perform a verification operation: verification is performed based on a preset device quantity verification rule, which is defined as follows: If the actual number of instruments is greater than or equal to the standard minimum configuration number, the verification is successful; If the actual number of instruments is less than the standard minimum configuration number, the verification fails. Upon successful verification, the parameter writing operation is executed. In response to verification failure, a missing weapon alarm is triggered and the current instruction generation is aborted.

9. The packaging system for the intelligent surgical pack according to claim 5, characterized in that, The packaging robot node is further configured to query the packaging instruction template from the preset instrument packaging rule base through the following steps: calculating the instrument packaging priority based on the surgical urgency coefficient, wherein the priority calculation rule is: the instrument packaging priority is equal to the surgical grade weight value multiplied by the emergency surgery coefficient; Based on the calculated device packaging priority, select the corresponding level of packaging instruction template from the preset device packaging rule library.

10. The packaging system for the intelligent surgical pack according to claim 6, characterized in that, The packaging robot node is further configured to perform batch instrument packaging operations through the following steps: for each instrument packaging instruction in the first execution batch, control the robotic arm to perform an instrument picking operation and update the inventory record of the surgical instrument database; For each instrument packing instruction in the second execution batch, perform an instrument replacement operation and update the instrument status flag in the surgical instrument database; For each instrument packing instruction in the third execution batch, perform an instrument retrieval operation and update the instrument traceability log in the surgical instrument database; Generate a surgical pack integrity report and send it to the nurse station terminal.

Images