A multi-sensory coordination-based operating room behavior compliance monitoring and alarm system

Abstract

The application discloses a kind of operating room behavior compliance monitoring alarm systems based on multi-sensory coordination, it is related to medical alarm technical field, including, door access module, collection door before multi-source state, and door before multi-source state is respectively with hand washing compliance token and hand washing node exception mark is admitted to verify, when there is hand washing compliance token and door before multi-source state meets access condition, output normal passage conclusion, when there is hand washing node exception mark, output hand washing exception passage conclusion, when door before multi-source state does not meet access condition and does not trigger hand washing node exception mark, output door before blocking passage conclusion;The application generates door before state set and carries out access verification to door before state set with hand washing compliance token, hand washing node exception mark, realizes that medical staff enters the token validity confirmation before operating room, door before state access judgment and hand washing exception block.

Description

Technical Field

[0001] This invention relates to the field of medical alarm technology, and in particular to an operating room behavior compliance monitoring alarm system based on multi-sensory collaboration. Background Technology

[0002] With the development of clean operating rooms, intelligent access control, RFID tracking, video surveillance and environmental safety monitoring technologies, operating room management is gradually shifting from manual verification to multi-source sensing and automated linkage. Medical staff identification, preoperative preparation, handwashing behavior, door access and alarm handling can all be recorded and managed through information technology equipment.

[0003] Existing operating room behavior management technologies mostly focus on single-point identification, single-item recording, or single alarm, making it difficult to form a continuous access chain from changing room preparation, handwashing verification, door status, and abnormal handling. This results in problems such as improper handwashing, identity mismatch, and abnormal door status being difficult to be attributed in a timely manner and trigger accurate alarms. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a multi-sensory collaborative operating room behavior compliance monitoring and alarm system to solve the problem of lack of continuous verification and accurate alarm linkage for preoperative access behavior in the operating room.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution: This invention provides a multi-sensory collaborative operating room behavior compliance monitoring and alarm system, comprising: an access modeling module, which constructs a temporal state machine based on basic access information, configures state transition conditions for access behavior nodes, forms a compliance access rule set, collects preoperative preparation perception information based on the compliance access rule set, and verifies the consistency between personnel identity and preparation status to form a preoperative preparation status certificate; a handwashing verification module, which verifies the identity of medical personnel corresponding to the preoperative preparation status certificate in the handwashing area, collects handwashing behavior perception information, and forms a handwashing behavior credential; verifies the handwashing duration and identity consistency based on the handwashing behavior credential, converts verified handwashing behavior into a handwashing compliance token, and converts unverified handwashing behavior into a handwashing node anomaly marker; and an entrance access module, which collects multi-source status at the entrance and converts the multi-source status at the entrance into a multi-source status. The source status is verified against the handwashing compliance token and the handwashing node anomaly marker for access. When a handwashing compliance token exists and the multi-source status at the door meets the access conditions, a normal access conclusion is output. When a handwashing node anomaly marker exists, an abnormal handwashing access conclusion is output. When the multi-source status at the door does not meet the access conditions and the handwashing node anomaly marker is not triggered, an access block conclusion is output. The breakpoint handling module performs compliance playback on the normal access conclusion, performs process breakpoint analysis on the abnormal handwashing access conclusion and the access block conclusion, locates the specific source of the anomaly among changing room anomalies, handwashing anomalies, access control anomalies, and security anomalies, and forms an anomaly breakpoint description. According to the anomaly breakpoint description, an access handling instruction is generated, and the access handling instruction is executed to perform voice alarm, display prompt, video marking, and sensor door linkage locking, forming a behavior compliance monitoring alarm file.

[0007] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system described in this invention, the steps for forming the compliance access rule set are as follows: The basic access information includes surgical scheduling information, medical staff authorization information, target operating room information, controlled area access information, access time window, and access process number; Establish a common access instance based on the basic access information, map the basic access information to the same access time window, and form an access instance index; Configure the access behavior nodes of the sequential state machine according to the access instance index, and set identity authentication, RFID hand sanitizer binding, locker status confirmation, effective handwashing sink sensing and sensor door access as sequential state nodes to form an access state machine instance. Configure the state transition conditions between adjacent access behavior nodes based on the access state machine instance, and write the personnel identity consistency, RFID scrub garment binding status, locker completion status, handwashing basin validity status, target operating room permissions, and access time window into the corresponding transition edges to form a compliant access rule set.

[0008] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system of the present invention, the steps for generating the preoperative preparation status certificate are as follows: The preoperative preparation sensing information includes medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, locker opening events, locker closing events, and locker occupancy status information; Preoperative preparation awareness information is collected based on the compliance access rule set, and time is merged according to the access instance index to form a preoperative preparation event sequence. Verify the consistency of medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, and cabinet occupancy information based on the preoperative preparation event sequence, and encapsulate the verified preoperative preparation event sequence into a preoperative preparation status certificate.

[0009] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system of the present invention, the steps for generating handwashing behavior credentials are as follows: Based on the preoperative preparation status certificate, a handwashing verification task is generated, and the handwashing verification task is limited to being triggered by the corresponding medical staff in the designated handwashing area and within the access time window, forming the basis for identity verification in the handwashing area; Based on the identity verification criteria in the handwashing area, the preoperative preparation status certificate is mapped to a certificate shadow, and the real-time collected medical staff identity information, RFID scrub suit tracking information, handwashing area location information, and entry time in the handwashing area are mapped to a real-time handwashing shadow. The certificate shadow and the real-time handwashing shadow are matched accordingly. When the access instance, personnel identity, RFID scrub suit, handwashing area, and entry time all meet the corresponding relationship, the certificate shadow matching score is calculated based on the corresponding relationship of access instance, personnel identity, RFID scrub suit, handwashing area, and entry time. When the certificate shadow matching score reaches the preset matching threshold, a handwashing session is established. When the certificate shadow matching score does not reach the preset matching threshold, the handwashing session is terminated and identity verification abnormal information is generated. Based on the handwashing session, the handwashing behavior perception information is collected, and the handwashing sink trigger state, handwashing continuous state and handwashing interruption state are merged into the same handwashing session to form handwashing behavior credentials.

[0010] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system described in this invention, the step of converting the handwashing node into an abnormal marker is as follows: The system continuously and collaboratively verifies the handwashing behavior credentials. When the handwashing behavior credentials meet the preset handwashing duration under the same medical staff identity information and the same RFID hand sanitizer tracking information, and the handwashing interruption status does not meet the preset interruption judgment conditions, a valid handwashing verification conclusion is formed. Based on the verification results of effective handwashing, the handwashing behavior credentials are tokenized, and the access instance index, medical staff identity information, RFID scrub suit tracking information, handwashing completion time, target operating room, and token validity time window are written into the same handwashing compliance token. When identity verification error information exists, the corresponding handwashing verification task will be directly converted into a handwashing node error marker. When the handwashing behavior credentials fail to pass the continuous collaborative verification of actions, the corresponding handwashing session will be converted into a handwashing node error marker.

[0011] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system described in this invention, the multi-source status in front of the door includes access control identification information, sensor door passage events, door operation status, target operating room information, and the safety status of the target operating room door and the controlled area.

[0012] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system of the present invention, the steps for outputting the conclusion of blocking passage in front of the door are as follows: Receive handwashing compliance tokens and handwashing node anomaly flags. Establish multiple trigger levels around the access instance index according to the access sequence of token availability verification, identity consistency verification, target operating room consistency verification, door security verification, controlled area security verification, and handwashing anomaly blocking. Write the corresponding door-front status quantity, triggering condition, pre-enabling condition, output content, and blocking feedback content into each trigger level to form door-front access verification rules. Based on the door access verification rules, the multi-source status at the door is collected, and combined with the handwashing compliance token, the handwashing node abnormality mark and the multi-source status at the door, the token availability status, identity consistency status, operating room matching status, door security status, area security status and handwashing abnormal status are converted to form a set of door status; The access trigger interaction is performed on the set of states in front of the door. When the token availability state meets the token availability condition, the identity consistency condition is activated. When the identity consistency state meets the identity consistency condition, the target operating room consistency condition is activated. When the operating room matching state meets the target operating room consistency condition, the door security condition and the controlled area security condition are activated. When the handwashing abnormal state meets the handwashing abnormal blocking condition, the token availability condition, the target operating room consistency condition, the door security condition, and the controlled area security condition are simultaneously set to the locked state, forming the access interaction state in front of the door. Based on the access control interaction status, when the token availability condition, identity consistency condition, target operating room consistency condition, door security condition, and controlled area security condition are all in an active and passable state, and the handwashing anomaly blocking condition is not triggered, the handwashing compliance token is marked as consumed and a normal passage conclusion is output. When the handwashing anomaly blocking condition is triggered, the consumption of the handwashing compliance token is prohibited and a handwashing anomaly passage conclusion is output. When any one of the following conditions is not met, and the handwashing anomaly blocking condition is not triggered, a door-front blocking passage conclusion is output.

[0013] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system of the present invention, the steps for forming abnormal breakpoints are as follows: Based on the normal passage conclusion, abnormal handwashing passage conclusion, and door-to-door blocking passage conclusion, the access instance index is used as the replay primary key. The preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node abnormal marker, door-to-door status set, and door-to-door access interaction status are merged according to the occurrence time to form an access replay event chain. Based on the access replay event chain, the preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node anomaly marker, door-front status set, and door-front access interaction status are mapped to changing node, handwashing node, access control node, and security node to generate the actual access trajectory. A standard access trajectory is generated based on the compliance access rule set. The actual access trajectory is aligned with the standard access trajectory in terms of node order, time window, and passage status. Synchronous passage, node missing, order offset, time limit exceeded, and reverse blocking status are marked to form an access deviation alignment sequence. Breakpoint attribution is performed based on the access deviation alignment sequence. If no deviation node exists, a compliance playback description is generated. If a deviation node exists, the earliest deviation node that cannot be explained by the preceding deviation is located as the corresponding source of the abnormality among changing room abnormality, handwashing abnormality, access control abnormality, and security abnormality, and an abnormal breakpoint description is generated.

[0014] As a preferred embodiment of the multi-sensory collaborative operating room behavior compliance monitoring and alarm system of the present invention, the step of generating access control instructions according to the abnormal breakpoint description is as follows: Receive the abnormal breakpoint description, establish an alarm handling transaction with the admission instance index as the handling primary key, and write the specific abnormal source and the breakpoint occurrence stage into the alarm handling transaction draft; According to the draft alarm handling procedures, the alarm script, display content, video range and door control actions corresponding to the specific source of the anomaly are matched, and passage handling instructions are generated according to the handling priority.

[0015] As a preferred embodiment of the operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration described in this invention, the steps for forming the behavior compliance monitoring and alarm file are as follows: According to the passage handling instructions, the system will execute video marking, sensor door linkage locking, voice alarm and display prompts, and receive alarm linkage execution receipts returned by each execution object; Based on the execution completion status of the access control instruction verified by the alarm linkage execution receipt, the description content corresponding to the current access instance in the abnormal breakpoint description is extracted, and the description content, access control instruction and alarm linkage execution receipt are packaged into a behavior compliance monitoring alarm file.

[0016] The beneficial effects of this invention are as follows: By generating a set of door-front states and verifying the set of door-front states with handwashing compliance tokens and abnormal handwashing node markers, the invention enables the confirmation of token validity, door-front state access judgment, and handwashing abnormality blocking before medical staff enter the operating room. This allows for the differentiation and output of normal passage conclusions, abnormal handwashing passage conclusions, and door-front blocking conclusions. It also provides accurate basis for process breakpoint analysis, passage handling instruction generation, voice alarms, display prompts, video marking, and sensor door linkage locking, thereby improving the real-time performance, accuracy, and traceability of the operating room behavior compliance monitoring and alarm process. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the following description of the embodiments will be briefly introduced. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of an operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration.

[0019] Figure 2 A flowchart for identity verification and handwashing node conversion in handwashing areas.

[0020] Figure 3 This is a flowchart for determining the interaction triggered by the set of states in front of the gate.

[0021] Figure 4 The flowchart for access playback breakpoint attribution and alarm linkage.

[0022] Figure 5 This is a confusion matrix data diagram of the three types of common conclusions.

[0023] Figure 6 This is a chart showing the comparison of point and line data for key indicators. Detailed Implementation

[0024] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0025] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0026] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0027] Reference Figures 1-6 This is one embodiment of the present invention, which provides a multi-sensory collaborative operating room behavior compliance monitoring and alarm system, including the following steps: The access modeling module constructs a temporal state machine based on basic access information and configures the state transition conditions for access behavior nodes to form a set of compliant access rules. Based on the set of compliant access rules, it collects preoperative preparation perception information and verifies the consistency between personnel identity and preparation status to form a preoperative preparation status certificate.

[0028] Basic access information includes surgical scheduling information, medical staff authorization information, target operating room information, controlled area access information, access time window, and access process number; It should be noted that the surgical scheduling information comes from the hospital's surgical scheduling management data and is used to determine the surgical tasks, surgical times, and entry process starting points for medical staff. The authorization information for medical staff comes from the hospital's personnel access management data and is used to confirm whether medical staff are qualified to enter the target operating room and perform the corresponding surgical tasks. The target operating room information comes from the operating room resource management data and is used to identify the specific operating room and the person to be verified at the entrance for medical staff during this access period. The controlled area access information is derived from the surgical department's restricted area management data and is used to limit the permitted access range for medical staff between the changing area, handwashing area, and operating room entrance. The access time window is derived from the surgical scheduling time and the time limit configuration of the preoperative preparation process, and is used to constrain the effective time for identity verification, changing clothes, hand washing and access to the door. The access process number is derived from the operating room behavior compliance process configuration data and is used to identify the sequence of state nodes and state transition rules applicable to this access.

[0029] Establish a common access instance based on the basic access information, map the basic access information to the same access time window, and form an access instance index; Specifically, the system verifies whether the surgical schedule information includes the identity of medical staff, the surgical time, and the target operating room; whether the authorization information of medical staff contains the identity of medical staff and surgical task permissions consistent with the surgical schedule information; whether the target operating room information falls within the scope of the controlled area access information; whether the access time window covers the time range required for identity authentication, changing clothes, handwashing, and sensor door access; and whether the access process number corresponds to the sequence of identity authentication, RFID scrub garment binding, locker status confirmation, effective handwashing sink sensing, and sensor door access. After all verifications are passed, the basic access information is mapped to the same access time window to form the same access instance. Based on the correspondence between the medical staff authorization information, the target operating room information, the access time window, and the access process number, the same access instance is uniquely identified to form an access instance index.

[0030] Configure the access behavior nodes of the sequential state machine according to the access instance index, and set identity authentication, RFID hand sanitizer binding, locker status confirmation, effective handwashing sink sensing and sensor door access as sequential state nodes to form an access state machine instance. Specifically, based on the access instance index, the basic access information within the same access instance is retrieved. Identity authentication is set as the access start node to receive authorization information from medical staff. RFID scrub gown binding, locker status confirmation, effective handwashing sink sensing, and sensor door access are sequentially set as sequential state nodes according to the access process number. Surgical shoe requisition information is used as an auxiliary verification item in locker status confirmation, ensuring that locker status confirmation simultaneously covers locker opening events, locker closing events, locker occupancy status information, and surgical shoe requisition information. Each sequential state node is associated with the access instance index, target operating room information, and access time window, ensuring that each sequential state node occurs within the same access instance. Adjacent sequential state nodes are connected according to the order of identity authentication, RFID scrub gown binding, locker status confirmation, effective handwashing sink sensing, and sensor door access, forming an access state machine instance that represents the execution order of this access process.

[0031] Configure the state transition conditions between adjacent access behavior nodes based on the access state machine instance, and write the personnel identity consistency, RFID scrub garment binding status, locker completion status, handwashing basin validity status, target operating room permissions, and access time window into the corresponding transition edges to form a compliant access rule set.

[0032] Specifically, based on the access state machine instance, adjacent access behavior nodes between identity authentication, RFID scrubber binding, locker status confirmation, effective handwashing sink sensing, and sensor door access are determined. Personnel identity consistency is written into the migration edge from identity authentication to RFID scrubber binding, the RFID scrubber binding status is written into the migration edge from RFID scrubber binding to locker status confirmation, and the locker completion status is written into the migration edge from locker status confirmation to effective handwashing sink sensing. The locker completion status is jointly verified and determined by locker opening events, locker closing events, locker occupancy status information, and surgical shoe requisition information. The effective handwashing sink status, target operating room permissions, and access time window are written into the migration edge from effective handwashing sink sensing to sensor door access. Each migration edge is saved in correspondence with the access instance index to form a compliant access rule set.

[0033] Preoperative preparation sensing information includes medical staff identification information, RFID scrub gown tracking information, surgical shoe requisition information, locker opening events, locker closing events, and locker occupancy status information; It should be noted that the medical staff's identity information comes from the hospital's personnel identity management data or access control identity recognition data, and is used to confirm whether the medical staff participating in the access process are the same as the authorized personnel in the access instance index; The tracking information for RFID scrub suits comes from the data read from the RFID tags on the scrub suits. This information is used to confirm whether the scrub suits have been linked to the corresponding medical staff and serves as a basis for verifying the preoperative preparation status. Surgical shoe requisition information comes from shoe dispensing equipment, smart shoe cabinets, or surgical shoe RFID reading data, and is used to confirm whether medical staff have completed the surgical shoe requisition operation that matches the operating room access process; The locker opening event is derived from the locker door opening and closing detection data, which is used to indicate that medical staff have entered the changing operation stage and triggered the preoperative preparation status record; The locker closing event originates from locker door closing detection data, which is used to characterize the end of the changing operation phase and provide a time point for judging whether the changing process is complete. The locker occupancy status information comes from the locker occupancy detection data, which is used to confirm whether the status of clothes being taken out or put in the locker has changed and to determine whether the changing operation has been completed.

[0034] Preoperative preparation awareness information is collected based on the compliance access rule set, and time is merged according to the access instance index to form a preoperative preparation event sequence. Specifically, based on the compliance access rule set, the sequential status nodes corresponding to the access instance index for identity authentication, RFID scrub gown binding, and locker status confirmation are read. Medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, locker opening events, locker closing events, and locker occupancy status information are collected according to these sequential status nodes. Preoperative preparation perception information is associated with each item in the access instance index. Using the access time window as the time range, preoperative preparation perception information under the same access instance index is sorted and merged according to the occurrence time. This ensures that medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, locker opening events, locker closing events, and locker occupancy status information correspond to the same access process, forming a preoperative preparation event sequence.

[0035] Verify the consistency of medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, and cabinet occupancy information based on the preoperative preparation event sequence, and encapsulate the verified preoperative preparation event sequence into a preoperative preparation status certificate.

[0036] Specifically, the system retrieves the medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, and cabinet occupancy status information within the same access instance according to the access instance index. It verifies whether the medical staff identity information belongs to authorized personnel defined by the compliant access rule set, whether the RFID scrub gown tracking information is bound to the same medical staff identity information, whether the surgical shoe requisition information corresponds to the same medical staff identity information, and whether the cabinet occupancy status information indicates that the changing operation has been completed. When all verified content meets the compliant access rule set, and the medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, and cabinet occupancy status information all belong to the same access instance index, the preoperative preparation event sequence verification is deemed successful. The access instance index, medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, cabinet occupancy status information, and verification success status are then encapsulated as a preoperative preparation status certificate.

[0037] The handwashing verification module verifies the identity of medical staff corresponding to the preoperative preparation status certificate in the handwashing area and collects handwashing behavior perception information to form a handwashing behavior credential. Based on the handwashing behavior credential verification, the module verifies the handwashing time and identity consistency, converts the verified handwashing behavior into a handwashing compliance token, and converts the unverified handwashing behavior into a handwashing node anomaly mark.

[0038] Based on the preoperative preparation status certificate, a handwashing verification task is generated, and the handwashing verification task is limited to being triggered by the corresponding medical staff in the designated handwashing area and within the access time window, forming the basis for identity verification in the handwashing area; Specifically, the system reads the access instance index, medical staff identity information, RFID scrub tracker information, target operating room, and access time window from the preoperative preparation status certificate. It establishes a binding relationship between the access instance index and the medical staff identity information, uses the RFID scrub tracker information as a supplementary identity verification basis, associates the target operating room with the designated handwashing area, and uses the access time window as the effective triggering period for the handwashing verification task. The system limits the triggering subject with the medical staff identity information, the triggering location with the designated handwashing area, and the triggering period with the access time window, so that the handwashing verification task can only be triggered by the corresponding medical staff in the designated handwashing area and within the access time window, forming the basis for identity verification in the handwashing area.

[0039] Based on the identity verification criteria in the handwashing area, the preoperative preparation status certificate is mapped to a certificate shadow, and the real-time collected medical staff identity information, RFID scrub suit tracking information, handwashing area location information, and entry time in the handwashing area are mapped to a real-time handwashing shadow. The certificate shadow and the real-time handwashing shadow are matched accordingly. When the access instance, personnel identity, RFID scrub suit, handwashing area, and entry time all meet the corresponding relationship, the certificate shadow matching score is calculated based on the corresponding relationship of access instance, personnel identity, RFID scrub suit, handwashing area, and entry time. When the certificate shadow matching score reaches the preset matching threshold, a handwashing session is established. When the certificate shadow matching score does not reach the preset matching threshold, the handwashing session is terminated and identity verification abnormal information is generated. Specifically, the system reads the access instance index, medical staff identity information, RFID scrub tracker information, designated handwashing area, and access time window from the pre-operative preparation status certificate. These are then written into the certificate shadow according to a preset field order. The generation time and matching status of the certificate shadow are recorded, ensuring it remains unalterable during the handwashing area identity verification process. Once the medical staff enters the handwashing area, the real-time medical staff identity information, RFID scrub tracker information, handwashing area location information, and entry time are written into the real-time handwashing shadow according to the same field order. The real-time handwashing shadow is then bound to the access instance index, ensuring it is only used for the current matching of the corresponding certificate shadow. The credential shadow and real-time handwashing shadow are verified item by item. When the access instance, personnel identity, RFID hand sanitizer, and handwashing area all match and the entry time falls within the access time window, the credential shadow matching score is calculated. When the credential shadow matching score reaches the preset matching threshold, a handwashing session is established. When the credential shadow matching score does not reach the preset matching threshold, the handwashing session is terminated and an identity verification anomaly is generated. When any of the access instance, personnel identity, RFID hand sanitizer, or handwashing area does not match, or the entry time does not fall within the access time window, the credential shadow matching score calculation is stopped, a handwashing session is not established, an identity verification anomaly is generated directly, and the corresponding handwashing verification task is converted into a handwashing node anomaly marker.

[0040] It should be noted that the preset field order refers to encapsulating the corresponding content in the preoperative preparation status certificate according to the fixed arrangement order of the admission instance index, medical staff identity information, RFID scrub suit tracking information, designated handwashing area and admission time window, so that the certificate shadow and the real-time handwashing shadow can be matched item by item according to the same field position.

[0041] The preset matching threshold is set based on the accuracy of medical staff identity information recognition, the stability of RFID scrub suit tracking information reading, the error of handwashing area location information, and the allowable deviation between entry time and admission time window. The example value range is 0.80 to 0.95. The value is based on the concentrated distribution of credential shadow matching scores in historical normal handwashing verification samples and the distinction boundary between identity mismatch, clothing mismatch, cross-regional triggering, and timeout triggering samples.

[0042] The expression for calculating the voucher shadow matching score is: ; in, Scoring based on shadow matching of credentials; The flag corresponding to the admission instance is set to one if the admission instance index is the same and zero if they are different. The identifier is used to match the identity of medical staff; if the identity information of medical staff matches, the value is 1, and if they do not match, the value is 0. The corresponding tag for the RFID hand sanitizer is set as follows: if the RFID hand sanitizer tracking information matches, the value is 1; if they do not match, the value is 0. The location information of the handwashing area is marked with a value of 1 if it belongs to the designated handwashing area and 0 if it does not belong to the designated handwashing area. For entry time; The center time of the admission time window; This is half the width of the admission time window.

[0043] It should be noted that the value range of the credential shadow matching score is 0 to 1. The closer the value is to 1, the higher the degree of correspondence between the real-time handwashing shadow and the credential shadow. When any corresponding marker is 0, the credential shadow matching score is 0, indicating that a handwashing session cannot be established.

[0044] Based on the handwashing session, the handwashing behavior perception information is collected, and the handwashing sink trigger state, handwashing continuous state and handwashing interruption state are merged into the same handwashing session to form handwashing behavior credentials.

[0045] Specifically, the system uses the access instance index corresponding to the handwashing session, the medical staff's identity information, and the RFID scrub suit tracking information as the basis for association. It continuously collects the handwashing sink sensing signals and generates handwashing sink trigger status, handwashing continuous status, and handwashing interruption status according to the triggering, holding, and interruption of the handwashing sink sensing signals. The handwashing sink trigger status, handwashing continuous status, and handwashing interruption status are merged into the same handwashing session according to the occurrence time, so that the handwashing behavior perception information corresponds with the same medical staff's identity information, the same RFID scrub suit tracking information, and the same access instance index, forming handwashing behavior credentials.

[0046] The system continuously and collaboratively verifies the handwashing behavior credentials. When the handwashing behavior credentials meet the preset handwashing duration under the same medical staff identity information and the same RFID hand sanitizer tracking information, and the handwashing interruption status does not meet the preset interruption judgment conditions, a valid handwashing verification conclusion is formed. Specifically, the system reads the healthcare worker's identity information, RFID scrub suit tracking information, handwashing basin trigger status, handwashing duration, and handwashing interruption status from the handwashing behavior credentials for the same handwashing session. It also verifies whether the healthcare worker's identity information is consistent with the information used when the handwashing session was established, and whether the RFID scrub suit tracking information is consistent with the information used when the handwashing session was established. Based on the consistency of the healthcare worker's identity information and the consistency of the RFID scrub suit tracking information, the system determines the start of handwashing based on the handwashing basin trigger status, accumulates the handwashing duration based on the handwashing duration, and determines whether the handwashing process has been effectively interrupted based on the handwashing interruption status. When the handwashing duration meets the preset handwashing duration and the handwashing interruption status does not meet the preset interruption judgment conditions, the handwashing behavior credentials are determined to be validly verified through continuous collaborative action verification, forming a conclusion of effective handwashing verification.

[0047] It should be noted that the handwashing time is set based on the operating room handwashing operation guidelines, handwashing product instructions, and hospital infection control requirements. The example value ranges from 2 minutes to 6 minutes. The basis for this value is that surgical hand disinfection is usually performed according to the product instructions and the commonly recommended time is in the range of 2 minutes to 6 minutes. The interruption determination criteria are set based on the handwashing sink trigger state, handwashing continuous state, handwashing interruption state, and handwashing action continuity requirements. The example value range is that a single interruption exceeding 3 to 10 seconds is considered a valid interruption. The value is based on the short-term jitter tolerance range of the handwashing sink sensor signal, the recognition delay of personnel leaving the handwashing area, and the hospital process calibration sample.

[0048] Based on the verification results of effective handwashing, the handwashing behavior credentials are tokenized, and the access instance index, medical staff identity information, RFID scrub suit tracking information, handwashing completion time, target operating room, and token validity time window are written into the same handwashing compliance token. Specifically, the access instance index, medical staff identity information, and RFID scrub suit tracking information corresponding to the handwashing behavior credential are confirmed to be consistent with the handwashing validity verification conclusion. The end time of the handwashing duration status in the handwashing behavior credential is read as the handwashing completion time, and the target operating room and access time window are associated based on the access instance index. The access instance index, medical staff identity information, RFID scrub suit tracking information, handwashing completion time, target operating room, and token validity time window are written into the same credential carrier in a fixed field order, wherein the token validity time window is calculated from the handwashing completion time and is limited to the access time window. The credential carrier is marked as a handwashing compliance token that can be used for front-door access verification, so that the handwashing compliance token can be verified in accordance with the multi-source status at the entrance of the target operating room.

[0049] It should be noted that the valid time window for the token is jointly determined by the handwashing completion time, the access time window, infection control requirements, surgical scheduling access requirements, and operating room access rules. The valid time window for the token starts from the handwashing completion time and ends no later than the end time of the access time window. When the surgical scheduling access requirements impose restrictions on the waiting time, the duration of the valid time window for the token is determined according to the corresponding restrictions. For example, the duration of the valid time window for the token is 5 to 20 minutes, and the value is based on the regular passage time for medical staff to complete the door access verification at the entrance of the target operating room after completing handwashing, the time requirements of infection control for waiting to enter the operating room after handwashing, and the queuing time allowed in the operating room access control process.

[0050] When identity verification error information exists, the corresponding handwashing verification task will be directly converted into a handwashing node error marker. When the handwashing behavior credentials fail to pass the continuous collaborative verification of actions, the corresponding handwashing session will be converted into a handwashing node error marker.

[0051] Specifically, when identity verification anomalies exist, the handwashing verification task is located based on the access instance index associated with the identity verification anomaly. The medical staff's identity information, RFID scrub suit tracking information, designated handwashing area, and anomaly occurrence time from the identity verification anomaly are written into the handwashing verification task, and the processing status of the handwashing verification task is changed to an anomaly status. The access instance index, medical staff's identity information, RFID scrub suit tracking information, and identity verification anomaly are encapsulated into a handwashing node anomaly marker. When the handwashing behavior credential fails the continuous collaborative verification of actions, the handwashing session is located based on the access instance index associated with the handwashing behavior credential. The handwashing sink trigger status, handwashing continuity status, handwashing interruption status, and reason for failure of continuous collaborative verification of actions from the handwashing behavior credential are written into the handwashing session, and the processing status of the handwashing session is changed to an anomaly status. The access instance index, medical staff's identity information, RFID scrub suit tracking information, and reason for failure of continuous collaborative verification of actions are encapsulated into a handwashing node anomaly marker.

[0052] The gate access module collects the multi-source status at the gate and verifies the multi-source status with the handwashing compliance token and the handwashing node anomaly flag. When a handwashing compliance token exists and the multi-source status at the gate meets the access conditions, a normal passage conclusion is output. When a handwashing node anomaly flag exists, a handwashing abnormal passage conclusion is output. When the multi-source status at the gate does not meet the access conditions and the handwashing node anomaly flag is not triggered, a gate blocked passage conclusion is output.

[0053] The multi-source status at the door includes access control identification information, sensor door access events, door operation status, target operating room information, and the security status of the target operating room door and the controlled area.

[0054] It should be noted that the access control identification information comes from the access control identification device at the entrance of the target operating room, and is used to confirm whether the identity of the medical staff entering the area in front of the door is consistent with the identity of the medical staff corresponding to the handwashing compliance token; The automatic door access event originates from the opening, closing, and access trigger records of the automatic door at the entrance of the target operating room, and is used to determine whether medical staff have initiated the access behavior to enter the target operating room; The door's operating status is determined by the door magnet, door controller, or operating feedback signal of the target operating room's sensor door, and is used to confirm whether the sensor door is in an openable, closed, abnormally opened, or locked state. The target operating room information comes from surgical scheduling information and operating room resource management data, and is used to confirm whether the specific operating room corresponding to the current door access verification is consistent with the handwashing compliance token. The safety status of the target operating room door and the controlled area is derived from door safety detection data and controlled area safety monitoring data, and is used to determine whether the target operating room entrance and associated controlled area meet the access release conditions.

[0055] Receive handwashing compliance tokens and handwashing node anomaly flags. Establish multiple trigger levels around the access instance index according to the access sequence of token availability verification, identity consistency verification, target operating room consistency verification, door security verification, controlled area security verification, and handwashing anomaly blocking. Write the corresponding door-front status quantity, triggering condition, pre-enabling condition, output content, and blocking feedback content into each trigger level to form door-front access verification rules. Specifically, the system receives handwashing compliance tokens and handwashing node anomaly flags, reads the access instance index from the handwashing compliance token, and merges handwashing node anomaly flags according to the same access instance index. Multiple trigger levels are established according to the access sequence of token availability verification, identity consistency verification, target operating room consistency verification, door security verification, controlled area security verification, and handwashing anomaly blocking. Each trigger level is written with corresponding door-front state variables, trigger conditions, pre-activation conditions, pass output content, and blocking feedback content. Specifically, the pass output content of token availability verification serves as the pre-activation condition for identity consistency verification; the pass output content of identity consistency verification serves as the pre-activation condition for target operating room consistency verification; the pass output content of target operating room consistency verification serves as the pre-activation condition for door security verification and controlled area security verification; and the blocking feedback content of handwashing anomaly blocking is used to disable token availability verification, target operating room consistency verification, door security verification, and controlled area security verification, thus forming the door-front access verification rules.

[0056] Based on the door access verification rules, the multi-source status at the door is collected, and combined with the handwashing compliance token, the handwashing node abnormality mark and the multi-source status at the door, the token availability status, identity consistency status, operating room matching status, door security status, area security status and handwashing abnormal status are converted to form a set of door status; Specifically, based on the access control verification rules, the system collects multi-source status data at the entrance. It searches the access instance index to determine if a handwashing compliance token has been generated under the same access instance. If a handwashing compliance token exists, it reads the handwashing completion time, the token's valid time window, and the consumption flag. It then compares the occurrence time of the sensor-activated door access event with the token's valid time window. If the occurrence time of the sensor-activated door access event falls within the token's valid time window and the consumption flag does not indicate consumption, the system is converted to a token-available state. The system also compares the medical staff identity information in the access control identification information with the medical staff identity information in the handwashing compliance token. If they match, the system is converted to an identity-matched state. Finally, it compares the target operating room information in the multi-source status at the entrance with the target operating room information in the handwashing compliance token. A consistency comparison is performed, and if they match, the system is converted to the operating room matching state. The system determines whether the sensor door is in a controllable opening, normal closing, and fault-free state based on the door's operating status. If the door's operating requirements are met, the system is converted to the door safety state. The system determines whether the target operating room entrance and the controlled area are in an allowed access state based on the safety status of the target operating room door and the controlled area. If the allowed access state is met, the system is converted to the area safety state. The system searches for abnormal handwashing node markers under the same access instance according to the access instance index. If an abnormal handwashing node marker is found, the system is converted to the handwashing abnormal state. The system then merges the token availability state, identity consistency state, operating room matching state, door safety state, area safety state, and handwashing abnormal state to form a door front state set.

[0057] It should be noted that the token availability status refers to the state in which the handwashing compliance token exists, is within the token's validity period window, and has not been consumed. This status is used to determine whether medical staff have the necessary handwashing access credentials to enter the target operating room. The identity consistency status refers to the consistency between the medical staff identity information in the access control identification information and the medical staff identity information in the handwashing compliance token. It is used to determine whether the person passing through the door is the same medical staff who has completed the handwashing verification. Operating room matching status refers to the state in which the target operating room information in the multi-source status at the door is consistent with the target operating room in the handwashing compliance token, which is used to determine whether the handwashing compliance token has been used for access to the corresponding target operating room. The door safety status refers to the door's operating status, which indicates that the sensor door is in a state of controllable opening, normal closing, and no malfunction. It is used to determine whether the sensor door at the entrance of the target operating room meets the access conditions. The area security status refers to the security status of the target operating room door and the controlled area, which indicates that the entrance of the target operating room and the controlled area are in a state of permitted access, and is used to determine whether the passage environment in front of the door meets the security access conditions. The abnormal handwashing status refers to the state where there is an abnormal handwashing node under the same access instance index. It is used to trigger abnormal handwashing blocking and output an abnormal handwashing passage conclusion.

[0058] The access trigger interaction is performed on the set of states in front of the door. When the token availability state meets the token availability condition, the identity consistency condition is activated. When the identity consistency state meets the identity consistency condition, the target operating room consistency condition is activated. When the operating room matching state meets the target operating room consistency condition, the door security condition and the controlled area security condition are activated. When the handwashing abnormal state meets the handwashing abnormal blocking condition, the token availability condition, the target operating room consistency condition, the door security condition, and the controlled area security condition are simultaneously set to the locked state, forming the access interaction state in front of the door. Specifically, when performing access triggering interaction on the door-front state set, the system reads the token availability status, identity consistency status, operating room matching status, door security status, area security status, and handwashing abnormal status according to the door-front access verification rules, and uses the token availability condition as the first-level access triggering condition; when the token availability status meets the token availability condition, the output content of the token availability condition is written into the pre-enabling condition of the identity consistency condition, making the identity consistency condition verifiable; when the identity consistency status meets the identity consistency condition, the output content of the identity consistency condition is written into the pre-enabling condition of the target operating room consistency condition, making the target operating room consistency condition verifiable; when the operating room matching status meets the target operating room consistency condition... When the target operating room's consistency condition is met, the output content is written into the pre-activation conditions of the door security condition and the controlled area security condition, respectively, so that the door security condition and the controlled area security condition enter the verifiable state. When the door security state meets the door security condition and the area security state meets the controlled area security condition, the activation pass status of each trigger level is recorded. When the handwashing abnormality state meets the handwashing abnormality blocking condition, the blocking feedback content of the handwashing abnormality blocking condition is synchronously written into the token availability condition, the target operating room consistency condition, the door security condition, and the controlled area security condition, and the token availability condition, the target operating room consistency condition, the door security condition, and the controlled area security condition are synchronously set to the locked state, forming the door access interaction state.

[0059] It should be noted that the token availability condition refers to the access judgment condition that the handwashing compliance token has been generated, is within the token's valid time window, and has not been marked as consumed. This condition is used to determine whether medical staff have the handwashing access qualification before entering the target operating room. The target operating room consistency condition refers to the access judgment condition that the target operating room information in the multi-source state at the door is consistent with the target operating room written with the handwashing compliance token. This is used to prevent the handwashing compliance token from being used to pass through non-corresponding operating rooms. Door safety conditions refer to the access judgment conditions that characterize the sensor door to be in a controllable opening, normal closing and without door malfunction, and are used to confirm that the entrance to the target operating room has a safe basis for passage. The safety conditions of the controlled area refer to the judgment conditions that indicate the target operating room entrance and associated controlled area are in an accessible state, and are used to confirm that the environment in front of the door meets the access requirements.

[0060] Based on the access control interaction status, when the token availability condition, identity consistency condition, target operating room consistency condition, door security condition, and controlled area security condition are all in an active and passable state, and the handwashing anomaly blocking condition is not triggered, the handwashing compliance token is marked as consumed and a normal passage conclusion is output. When the handwashing anomaly blocking condition is triggered, the consumption of the handwashing compliance token is prohibited and a handwashing anomaly passage conclusion is output. When any one of the following conditions is not met, and the handwashing anomaly blocking condition is not triggered, a door-front blocking passage conclusion is output.

[0061] Specifically, the passage decision is made based on the access control interaction status at the entrance. This involves reading the current status of token availability, identity consistency, target operating room consistency, door security, controlled area security, and handwashing anomaly blocking conditions, prioritizing the handwashing anomaly blocking condition. When the handwashing anomaly blocking condition is triggered, handwashing compliance token consumption is immediately stopped, the token remains unconsumed, and the handwashing anomaly status, access instance index, and entrance status set are recorded to form a handwashing anomaly passage decision. Conversely, if the handwashing anomaly blocking condition is not triggered, and the token availability, identity consistency, and target operating room consistency are all considered, the passage decision is made based on the current status of the access control interaction status. When the operating room consistency condition, door security condition, and controlled area security condition are all in an active and passable state, the consumption mark of the handwashing compliance token is rewritten to consumed, and the access instance index, door-front state set, and access permission status are recorded to form a normal passage conclusion. When the handwashing abnormal blocking condition is not triggered, and at least one of the token availability condition, identity consistency condition, target operating room consistency condition, door security condition, and controlled area security condition is not in an active and passable state, the door-front state quantity and reason for failure corresponding to the failure condition are retained, and the access instance index and access prohibition status are recorded to form a door-front blocked passage conclusion.

[0062] It should be noted that an unused handwashing compliance token means that the handwashing compliance token has been generated from the handwashing behavior credentials, but has not yet been verified at the entrance of the target operating room. It can still be used for one entrance access judgment. A used handwashing compliance token means that the handwashing compliance token has been used and marked when the normal access conclusion is generated. It cannot be used again for the same medical staff to enter the target operating room. This is to prevent the same handwashing compliance token from being reused, used across doors, or borrowed by others.

[0063] Figure 5The diagram shows the confusion matrix for the three types of access conclusions. The horizontal axis represents the output access conclusions, and the vertical axis represents the true access conclusions. The darker the color, the more samples there are in the corresponding category. As can be seen from the figure, the main samples of the normal access conclusion, the abnormal handwashing access conclusion, and the door blocking access conclusion are concentrated on the diagonal. Among them, 1403 groups of normal access conclusions were correctly identified, 593 groups of abnormal handwashing access conclusions were correctly identified, and 858 groups of door blocking access conclusions were correctly identified. This shows that the present invention can distinguish and output the three types of access conclusions relatively stably. At the same time, the number of misjudgments on the off-diagonal line is relatively small, indicating that after the door state set is combined with the handwashing compliance token and the abnormal handwashing node marker for joint access verification, it has a good ability to distinguish between abnormal handwashing and door blocking scenarios.

[0064] The breakpoint handling module performs compliance playback on normal passage conclusions, analyzes process breakpoints on abnormal handwashing passage conclusions and door-blocking passage conclusions, identifies the specific sources of abnormalities in changing room abnormalities, handwashing abnormalities, access control abnormalities, and security abnormalities, and generates abnormal breakpoint descriptions; generates passage handling instructions based on abnormal breakpoint descriptions, and executes voice alarms, display prompts, video markings, and sensor door linkage locking according to the passage handling instructions, forming a behavior compliance monitoring alarm file.

[0065] Based on the normal passage conclusion, abnormal handwashing passage conclusion, and door-to-door blocking passage conclusion, the access instance index is used as the replay primary key. The preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node abnormal marker, door-to-door status set, and door-to-door access interaction status are merged according to the occurrence time to form an access replay event chain. Specifically, the access instance index associated with each access conclusion is read, and the access instance index is used as the replay primary key for the same access process. The preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node anomaly marker, door-to-door status set, and door-to-door access interaction status that have been formed under the same access instance index are retrieved respectively. The generation time of the preoperative preparation status certificate, the formation time of the handwashing behavior certificate, the generation time and consumption time of the handwashing compliance token, the formation time of the handwashing node anomaly marker, the collection time of the door-to-door status set, and the formation time of the door-to-door access interaction status are extracted and sorted in chronological order of occurrence. After sorting, the contents under the same access instance index are sequentially concatenated into an access replay event chain that can reflect the process of preoperative preparation, handwashing verification, door-to-door access, and access conclusion formation.

[0066] Based on the access replay event chain, the preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node anomaly marker, door-front status set, and door-front access interaction status are mapped to changing node, handwashing node, access control node, and security node to generate the actual access trajectory. A standard access trajectory is generated based on the compliance access rule set. The actual access trajectory is aligned with the standard access trajectory in terms of node order, time window, and passage status. Synchronous passage, node missing, order offset, time limit exceeded, and reverse blocking status are marked to form an access deviation alignment sequence. Specifically, the system reads the preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node anomaly marker, door-front status set, and door-front access interaction status according to the occurrence time. It categorizes the access behavior nodes corresponding to each item: the preoperative preparation status certificate is categorized into the changing room node; the handwashing behavior certificate, handwashing compliance token, and handwashing node anomaly marker are categorized into the handwashing node; content related to access control identification information, sensor door access events, and target operating room information in the door-front status set is categorized into the access control node; and content related to door operation status, target operating room door, and controlled area security status in the door-front status set is categorized into the security node. These are then arranged according to the occurrence time to form the actual access trajectory. Identity authentication and RFID hand sanitizer are then centrally processed according to the compliance access rules. The system generates a standard access trajectory by considering the status transition conditions for binding, locker status confirmation, effective handwashing sink sensing, and sensor door access, as well as the access time window and node passage conditions. The actual access trajectory is then compared node by node with the standard access trajectory. Nodes with the same name, the same order of occurrence, and the occurrence time falling within the access time window, and meeting the node passage conditions, are marked as synchronously passed. Nodes missing from the standard access trajectory but lacking a corresponding node in the actual access trajectory are marked as node missing. Nodes in the actual access trajectory not occurring in the standard access trajectory are marked as having an order deviation. Nodes in the actual access trajectory occurring outside the access time window are marked as exceeding the time limit. A locked state is present in the door access interaction state, marking it as reverse blocking. This forms an access deviation alignment sequence.

[0067] Breakpoint attribution is performed based on the access deviation alignment sequence. If no deviation node exists, a compliance playback description is generated. If a deviation node exists, the earliest deviation node that cannot be explained by the preceding deviation is located as the corresponding source of the abnormality among changing room abnormality, handwashing abnormality, access control abnormality, and security abnormality, and an abnormal breakpoint description is generated.

[0068] Specifically, the system reads the synchronization status (passed, node missing, sequence offset, time limit exceeded, and reverse blocking) according to the occurrence time, and determines whether there is a deviation node in the access deviation alignment sequence. If there is no deviation node in the access deviation alignment sequence, the verification content that the actual access trajectory is consistent with the standard access trajectory is written into the compliance playback description. If there is a deviation node in the access deviation alignment sequence, the earliest deviation node is determined according to the occurrence time, and the earliest deviation node is determined by combining the order of access behavior nodes to determine whether it can be explained by the preceding deviation node. The earliest deviation node that cannot be explained by the preceding deviation node is taken as the specific source of the anomaly. When the specific source of the anomaly is located at the changing node, it is located as a changing anomaly; when the specific source of the anomaly is located at the handwashing node, it is located as a handwashing anomaly; when the specific source of the anomaly is located at the access control node, it is located as an access control anomaly; when the specific source of the anomaly is located at the security node, it is located as a security anomaly. The specific source of the anomaly, the breakpoint occurrence stage, the deviation status, and the corresponding access instance index are written into the anomaly breakpoint description.

[0069] It should be noted that "cannot be explained by preceding deviations" means: when subsequent deviation nodes can be naturally caused by earlier deviation nodes, the subsequent deviation nodes are not considered as specific sources of anomalies; when the preceding changing node has missing nodes, sequence offsets, time limits exceeded, or the cabinet occupancy status does not indicate changing completion, and this leads to the subsequent missing handwashing node or failure to establish a handwashing session, the earliest deviation node is identified as a changing anomaly; when the preceding handwashing node has identity verification failure, insufficient handwashing time, handwashing interruption status reaching the preset interruption judgment condition, or a handwashing node anomaly marker, and this leads to subsequent access control blocking, the earliest deviation node is identified as a handwashing anomaly; when neither the changing nor handwashing nodes have deviation nodes, but the access control identification information, identity consistency status, or operating room matching status has deviation nodes, the earliest deviation node is identified as an access control anomaly; when none of the changing, handwashing, and access control nodes have deviation nodes, but the door security status or area security status has deviation nodes, the earliest deviation node is identified as a security anomaly.

[0070] It should be noted that abnormal changing of clothes refers to anomalies in the changing of clothes nodes corresponding to the preoperative preparation status certificate, such as missing nodes, sequence deviation, time exceeding the limit, or cabinet occupancy status not indicating completion of changing of clothes. This is used to locate the specific source of non-compliance in the preoperative preparation stage of medical staff. Handwashing anomalies refer to anomalies in handwashing nodes corresponding to handwashing behavior credentials, handwashing compliance tokens, or handwashing node anomaly markers, such as identity verification failure, insufficient handwashing time, or handwashing interruption reaching preset interruption judgment conditions. These anomalies are used to locate the specific source of non-compliance in the handwashing verification stage. Access control anomalies refer to anomalies in the access control nodes corresponding to the door state set, such as failure to pass identity consistency status, failure to pass operating room matching status, or failure of sensor door access events to meet access triggering interaction requirements. These anomalies are used to locate the specific non-compliance sources in the access stage of the target operating room entrance. Security anomalies refer to anomalies in the security nodes corresponding to the door status set, where the door security status or the area security status fails to pass. These anomalies are used to locate the specific non-compliance sources that prevent access due to the security status of the target operating room door and the controlled area.

[0071] Receive the abnormal breakpoint description, establish an alarm handling transaction with the admission instance index as the handling primary key, and write the specific abnormal source and the breakpoint occurrence stage into the alarm handling transaction draft; Specifically, the access instance index in the exception breakpoint description is read, and the access instance index is used as the primary key for handling. The specific exception source and breakpoint occurrence stage associated with the same access instance index are extracted. The handling category of the alarm handling transaction is determined according to the specific exception source, and the handling position and order of the alarm handling transaction are determined according to the breakpoint occurrence stage. The access instance index, specific exception source, breakpoint occurrence stage and handling category are written into the same alarm handling transaction. The alarm handling transaction is marked as pending execution, forming a draft alarm handling transaction for generating the pass handling instruction.

[0072] It should be noted that the handling categories are divided into changing room correction handling, handwashing correction handling, access control authority handling, and security blocking handling according to the specific source of the abnormality. Among them, changing room correction handling is used to correct the preoperative preparation status corresponding to changing room abnormalities; handwashing correction handling is used to remind people to wash their hands again and restrict access to sensor doors corresponding to handwashing abnormalities; access control authority handling is used to trigger access control alarms and video markings corresponding to access control abnormalities; and security blocking handling is used to control doors, provide remote prompts, and block access corresponding to security abnormalities.

[0073] According to the draft alarm handling procedures, the alarm script, display content, video range and door control actions corresponding to the specific source of the anomaly are matched, and passage handling instructions are generated according to the handling priority.

[0074] Specifically, the system reads the access instance index, the specific source of the anomaly, and the breakpoint occurrence stage, and determines the handling category based on the specific source of the anomaly. When the specific source of the anomaly is a changing room anomaly, it matches the alarm script, display content, video range, and door suspension control action corresponding to the changing room correction handling. When the specific source of the anomaly is a handwashing anomaly, it matches the alarm script, display content, video range, and sensor door linkage locking action corresponding to the handwashing correction handling. When the specific source of the anomaly is an access control anomaly, it matches the alarm script, display content, video range, and current sensor door locking action corresponding to the access control permission handling. When the specific source of the anomaly is a security anomaly, it matches the alarm script, display content, video range, and sensor door linkage locking action corresponding to the security blocking handling. The system determines the timing of alarm script playback, the display position of display content, the video range capture interval, and the target of door control action execution based on the breakpoint occurrence stage, and arranges them according to the handling priority of sensor door linkage locking, video marking, voice alarm, and display prompts to form access handling instructions.

[0075] It should be noted that the handling priorities for different specific sources of anomalies are as follows: The handling priorities are determined based on the specific source of the anomaly, the stage at which the interruption occurred, and the degree of access risk; when the specific source of the anomaly is a changing room anomaly, the handling priorities are, in order, temporarily suspending the door control action, issuing a voice alarm, displaying a prompt, and marking a video, to prompt medical staff to return to the changing room to complete the preoperative preparation status correction; when the specific source of the anomaly is a handwashing anomaly, the handling priorities are, in order, the sensor door locking, issuing a voice alarm, displaying a prompt, and marking a video, to prevent medical staff from continuing to enter the target operating room and prompting them to complete the handwashing verification again; when the specific source of the anomaly is an access control anomaly, the handling priorities are, in order, the current sensor door locking action, marking a video, issuing a voice alarm, and displaying a prompt, to prioritize blocking access behavior with mismatched identities or inconsistent permissions and to preserve evidence in front of the door; when the specific source of the anomaly is a security anomaly, the handling priorities are, in order, the sensor door locking, displaying a prompt, issuing a voice alarm, and marking a video, to prioritize ensuring the security status of the target operating room entrance and controlled areas.

[0076] According to the passage handling instructions, the system will execute video marking, sensor door linkage locking, voice alarm and display prompts, and receive alarm linkage execution receipts returned by each execution object; Specifically, the system reads the access instance index, alarm script, display content, video range, and door control actions from the access control instructions. Based on the video range, it marks the start and end of the video segment in front of the door associated with the access instance index, forming a video marking receipt. Based on the door control actions, it issues a linkage locking command to the sensor door and forms a sensor door linkage locking receipt based on the locking completion status returned by the sensor door. After the sensor door linkage locking receipt is formed, it plays a voice alarm based on the alarm script and records the voice alarm playback completion status, forming a voice alarm receipt. At the same time, it displays the source of the abnormality, the direction of handling, and the access status on the display screen based on the display content and records the display completion status, forming a display prompt receipt. The video marking receipt, sensor door linkage locking receipt, voice alarm receipt, and display prompt receipt are merged according to the access instance index to form an alarm linkage execution receipt.

[0077] Based on the execution completion status of the access control instruction verified by the alarm linkage execution receipt, the description content corresponding to the current access instance in the abnormal breakpoint description is extracted, and the description content, access control instruction and alarm linkage execution receipt are packaged into a behavior compliance monitoring alarm file.

[0078] Specifically, the system reads video tag receipts, sensor door linkage locking receipts, voice alarm receipts, and display prompt receipts according to the access instance index. It then verifies whether the video tag receipt contains the video tag index, whether the sensor door linkage locking receipt indicates locking completion, whether the voice alarm receipt indicates alarm playback completion, and whether the display prompt receipt indicates prompt display completion. If all receipts meet the execution requirements of the access control instruction, the access control instruction is determined to be in a completed state. The system also extracts the specific anomaly source, breakpoint occurrence stage, and deviation node content corresponding to the current access instance from the anomaly breakpoint description. Finally, the description content, access control instruction, and alarm linkage execution receipt are associated and encapsulated according to their occurrence time to form a behavior compliance monitoring alarm file.

[0079] It should be noted that the execution requirements refer to the pre-determined completion criteria for each alarm linkage action in the access control instruction. Specifically, these include: the video tag receipt should contain the video tag index and video range corresponding to the access instance index; the sensor door linkage locking receipt should indicate that the corresponding sensor door has entered the locked state; the voice alarm receipt should indicate that the alarm message has been played; and the display prompt receipt should indicate that the displayed content has been displayed. When all of the above receipts are consistent with the video range, door control action, alarm message, and display content in the access control instruction, the access control instruction is deemed to meet the execution requirements.

[0080] Figure 6The diagram shows a point-and-line comparison of key indicators between the conventional solution and the solution of this invention. Hollow dots represent the conventional solution, solid dots represent the solution of this invention, and connecting lines represent the differences between the two solutions for the same indicator. As can be seen from the figure, the overall accuracy of the solution of this invention increased from 74.1% to 95.1%, the abnormal handwashing recognition rate increased from 12.3% to 98.8%, the door blocking recognition rate increased from 77.2% to 95.3%, the false release rate of abnormal samples decreased from 47.6% to 1.0%, the alarm receipt completeness rate increased from 68.9% to 97.1%, and the alarm file generation rate increased from 65.3% to 95.9%. The conventional solution refers to a solution that relies solely on access control identification information, sensor door access events, door operating status, and simplified handwashing stay duration for access judgment. The solution of this invention refers to a continuous verification solution that sequentially generates handwashing behavior credentials, handwashing compliance tokens, handwashing node abnormality markers, door front status sets, door front access interaction status, access handling instructions, alarm linkage execution receipts, and behavior compliance monitoring alarm files.

[0081] In summary, this invention generates a set of door-front states and verifies these states against handwashing compliance tokens and abnormal handwashing node markers. This enables the confirmation of token validity, door-front state access judgment, and handwashing anomaly blocking of medical personnel before they enter the operating room. It allows for the differentiation and output of normal passage conclusions, abnormal handwashing passage conclusions, and door-front blocking conclusions. Furthermore, it provides accurate data for process breakpoint analysis, passage handling instruction generation, voice alarms, display prompts, video marking, and sensor door linkage locking, thereby improving the real-time performance, accuracy, and traceability of the operating room behavior compliance monitoring and alarm process.

[0082] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A multi-sensory collaborative operating room behavior compliance monitoring and alarm system, characterized in that, include: The access modeling module constructs a temporal state machine based on basic access information and configures the state transition conditions of access behavior nodes to form a set of compliant access rules. Based on the set of compliant access rules, it collects preoperative preparation perception information and verifies the consistency between personnel identity and preparation status to form a preoperative preparation status certificate. The handwashing verification module verifies the identity of medical staff corresponding to the preoperative preparation status certificate in the handwashing area and collects handwashing behavior perception information to form a handwashing behavior credential. Based on the handwashing behavior credential verification, the module verifies the handwashing time and identity consistency, converts the verified handwashing behavior into a handwashing compliance token, and converts the unverified handwashing behavior into a handwashing node anomaly marker. The door access control module collects multi-source status data at the door, including access control identification information, sensor door access events, door operating status, target operating room information, and the security status of the target operating room door and controlled area. It then verifies these multi-source status data against handwashing compliance tokens and handwashing node anomaly markers. If a handwashing compliance token is present and the multi-source status data meets the access conditions, a normal access conclusion is output. If a handwashing node anomaly marker is present, an abnormal handwashing access conclusion is output. If the multi-source status data does not meet the access conditions and no handwashing node anomaly marker is triggered, an access block conclusion is output. The steps are as follows: Receive handwashing compliance tokens and handwashing node anomaly flags. Establish multiple trigger levels around the access instance index according to the access sequence of token availability verification, identity consistency verification, target operating room consistency verification, door security verification, controlled area security verification, and handwashing anomaly blocking. Write the corresponding door-front status quantity, triggering condition, pre-enabling condition, output content, and blocking feedback content into each trigger level to form door-front access verification rules. Based on the door access verification rules, the multi-source status at the door is collected, and combined with the handwashing compliance token, the handwashing node abnormality mark and the multi-source status at the door, the token availability status, identity consistency status, operating room matching status, door security status, area security status and handwashing abnormal status are converted to form a set of door status; The access trigger interaction is performed on the set of states in front of the door. When the token availability state meets the token availability condition, the identity consistency condition is activated. When the identity consistency state meets the identity consistency condition, the target operating room consistency condition is activated. When the operating room matching state meets the target operating room consistency condition, the door security condition and the controlled area security condition are activated. When the handwashing abnormal state meets the handwashing abnormal blocking condition, the token availability condition, the target operating room consistency condition, the door security condition, and the controlled area security condition are simultaneously set to the locked state, forming the access interaction state in front of the door. Based on the access control interaction status, when the token availability condition, identity consistency condition, target operating room consistency condition, door security condition, and controlled area security condition are all in an active and passable state, and the handwashing anomaly blocking condition is not triggered, the handwashing compliance token is marked as consumed and a normal passage conclusion is output. When the handwashing anomaly blocking condition is triggered, the consumption of the handwashing compliance token is prohibited and a handwashing anomaly passage conclusion is output. When any one of the token availability condition, identity consistency condition, target operating room consistency condition, door security condition, and controlled area security condition fails to pass, and the handwashing anomaly blocking condition is not triggered, a door-front blocking passage conclusion is output. The breakpoint handling module performs compliance playback on normal passage conclusions and process breakpoint analysis on abnormal handwashing passage conclusions and door-blocking passage conclusions. It identifies the specific sources of anomalies in changing room anomalies, handwashing anomalies, access control anomalies, and security anomalies, and generates an anomaly breakpoint description. The steps are as follows: Based on the normal passage conclusion, abnormal handwashing passage conclusion, and door-to-door blocking passage conclusion, the access instance index is used as the replay primary key. The preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node abnormal marker, door-to-door status set, and door-to-door access interaction status are merged according to the occurrence time to form an access replay event chain. Based on the access replay event chain, the preoperative preparation status certificate, handwashing behavior certificate, handwashing compliance token, handwashing node anomaly marker, door-front status set, and door-front access interaction status are mapped to changing node, handwashing node, access control node, and security node to generate the actual access trajectory. A standard access trajectory is generated based on the compliance access rule set. The actual access trajectory is aligned with the standard access trajectory in terms of node order, time window, and passage status. Synchronous passage, node missing, order offset, time limit exceeded, and reverse blocking status are marked to form an access deviation alignment sequence. Breakpoint attribution is performed based on the access deviation alignment sequence. If there are no deviation nodes, a compliance playback description is generated. If there are deviation nodes, the earliest deviation node that cannot be explained by the preceding deviation is located as the corresponding source of the abnormality among changing room abnormality, handwashing abnormality, access control abnormality, and security abnormality, and an abnormal breakpoint description is generated. Based on the abnormal breakpoint description, generate access control instructions, and execute voice alarms, display prompts, video markings, and sensor door linkage locking according to the access control instructions to form a behavior compliance monitoring alarm file.

2. The operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration as described in claim 1, characterized in that, The steps for forming the compliance access rule set are as follows: The basic access information includes surgical scheduling information, medical staff authorization information, target operating room information, controlled area access information, access time window, and access process number; Establish a common access instance based on the basic access information, map the basic access information to the same access time window, and form an access instance index; Configure the access behavior nodes of the sequential state machine according to the access instance index, and set identity authentication, RFID hand sanitizer binding, locker status confirmation, effective handwashing sink sensing and sensor door access as sequential state nodes to form an access state machine instance. Configure the state transition conditions between adjacent access behavior nodes based on the access state machine instance, and write the personnel identity consistency, RFID scrub garment binding status, locker completion status, handwashing basin validity status, target operating room permissions, and access time window into the corresponding transition edges to form a compliant access rule set.

3. The operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration as described in claim 2, characterized in that, The steps for generating the preoperative preparation status certificate are as follows: The preoperative preparation sensing information includes medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, locker opening events, locker closing events, and locker occupancy status information; Preoperative preparation awareness information is collected based on the compliance access rule set, and time is merged according to the access instance index to form a preoperative preparation event sequence. Verify the consistency of medical staff identity information, RFID scrub gown tracking information, surgical shoe requisition information, and cabinet occupancy information based on the preoperative preparation event sequence, and encapsulate the verified preoperative preparation event sequence into a preoperative preparation status certificate.

4. The operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration as described in claim 3, characterized in that, The steps to generate handwashing behavior credentials are as follows: Based on the preoperative preparation status certificate, a handwashing verification task is generated, and the handwashing verification task is limited to being triggered by the corresponding medical staff in the designated handwashing area and within the access time window, forming the basis for identity verification in the handwashing area; Based on the identity verification criteria in the handwashing area, the preoperative preparation status certificate is mapped to a certificate shadow, and the real-time collected medical staff identity information, RFID scrub suit tracking information, handwashing area location information, and entry time in the handwashing area are mapped to a real-time handwashing shadow. The certificate shadow and the real-time handwashing shadow are matched accordingly. When the access instance, personnel identity, RFID scrub suit, handwashing area, and entry time all meet the corresponding relationship, the certificate shadow matching score is calculated based on the corresponding relationship of access instance, personnel identity, RFID scrub suit, handwashing area, and entry time. When the certificate shadow matching score reaches the preset matching threshold, a handwashing session is established. When the certificate shadow matching score does not reach the preset matching threshold, the handwashing session is terminated and identity verification abnormal information is generated. Based on the handwashing session, the handwashing behavior perception information is collected, and the handwashing sink trigger state, handwashing continuous state and handwashing interruption state are merged into the same handwashing session to form handwashing behavior credentials.

5. The operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration as described in claim 4, characterized in that, The steps to convert the handwashing node into an abnormal marker are as follows: The system continuously and collaboratively verifies the handwashing behavior credentials. When the handwashing behavior credentials meet the preset handwashing duration under the same medical staff identity information and the same RFID scrub suit tracking information, and the handwashing interruption status does not meet the preset interruption judgment conditions, a valid handwashing verification conclusion is formed. Based on the verification results of effective handwashing, the handwashing behavior credentials are tokenized, and the access instance index, medical staff identity information, RFID scrub suit tracking information, handwashing completion time, target operating room, and token validity time window are written into the same handwashing compliance token. When identity verification error information exists, the corresponding handwashing verification task will be directly converted into a handwashing node error marker. When the handwashing behavior credentials fail to pass the continuous collaborative verification of actions, the corresponding handwashing session will be converted into a handwashing node error marker.

6. The operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration as described in claim 1, characterized in that, The steps for generating passage handling instructions based on the abnormal breakpoint description are as follows: Receive the abnormal breakpoint description, establish an alarm handling transaction with the admission instance index as the handling primary key, and write the specific abnormal source and the breakpoint occurrence stage into the alarm handling transaction draft; According to the draft alarm handling procedures, the alarm script, display content, video range and door control actions corresponding to the specific source of the anomaly are matched, and passage handling instructions are generated according to the handling priority.

7. The operating room behavior compliance monitoring and alarm system based on multi-sensory collaboration as described in claim 6, characterized in that, The steps for creating the behavior compliance monitoring and alarm file are as follows: According to the passage handling instructions, the system will execute video marking, sensor door linkage locking, voice alarm and display prompts, and receive alarm linkage execution receipts returned by each execution object; Based on the execution completion status of the access control instruction verified by the alarm linkage execution receipt, the description content corresponding to the current access instance in the abnormal breakpoint description is extracted, and the description content, access control instruction and alarm linkage execution receipt are packaged into a behavior compliance monitoring alarm file.

Images