Medical device adaptive control based on clinician interaction

Abstract

A method and system are disclosed that identify user interactions with one or more medical devices, determine a compliance score associated with a first user based on the one or more interactions and a predetermined set of rules, reduce a level of access of the user to at least one of the one or more medical devices in response to the compliance score not satisfying a threshold compliance score, and generate a training program associated with the at least one medical device and the one or more interactions, and automatically send a training package associated with the training program to the user without user engagement and notify the user to complete the training program using the training package. The system and method also generate a new shift schedule for a clinician in response to the first shift schedule not satisfying a standard and the clinician not satisfying a corresponding performance score.

Description

[0001] Cross-references to related applications

[0002] This application claims priority to U.S. Application Serial No. 62 / 897,199, filed September 6, 2019, entitled “ADAPTIVE CONTROL OF MEDICALDEVICES BASED ON CLINICIAN INTERACTIONS”, and to U.S. Application Serial No. 62 / 865,906, filed June 24, 2019, entitled “SYSTEMS AND METHODS FOR INDENTIFYING NON-COMPLIANCE PATTERNS OF INTERACTONS WITH A MEDICAL DEVICE”, the entire contents of each of which are incorporated herein by reference. Technical Field

[0003] This application generally relates to controlling medical devices based on clinician assessments and their corresponding interactions with medical devices within a healthcare facility. Background Technology

[0004] Medical devices (such as infusion devices) offer numerous conveniences and simplify medication administration for patients by clinicians (such as nurses) in healthcare facilities. Healthcare facilities and medical device manufacturers can establish various protocols and / or safeguards to ensure the safe and consistent administration of fluids or medications by clinicians with varying levels of experience and training. However, due to differing experience and training levels, some clinicians may act outside the scope of healthcare facility protocols, jeopardizing patient safety and the operation of the healthcare facility. Furthermore, healthcare facilities utilize different systems from different vendors and clinicians with varying levels of proficiency in these systems to assist in patient care. Therefore, a key concern for healthcare facilities is identifying and mitigating operational risks while improving operational efficiency. However, existing healthcare systems often fail to adequately identify clinicians with lower proficiency levels in one or more of the systems used, thus increasing the risk of patient injury and / or reducing operational efficiency for healthcare facilities. Summary of the Invention

[0005] Clinician interactions with different medical devices and systems can increase operational risk for healthcare facilities. For example, a clinician may not follow one or more protocols when administering medication to a patient. Existing systems are not adequately configured to track and monitor non-compliant clinician interactions across multiple medical devices. Healthcare facilities may also face operational risks from ad-hoc or traveling clinicians with varying levels of training and expertise in using the facility's different medical devices and systems. Existing systems also fail to automatically assist such clinicians in successfully performing their tasks in accordance with best practices and / or protocol standards, or to effectively identify resource centers with trained ad-hoc clinicians to mitigate operational risk. Furthermore, existing systems and methods do not allow healthcare facilities to effectively specify scheduling criteria and, based on these criteria, schedule clinicians for shifts within the facility. Additionally, operational risk for healthcare facilities may increase due to inappropriate and / or inefficient scheduling of clinicians for different shifts within the facility.

[0006] Therefore, there is a need for systems and methods that can track individual clinician interactions, identify non-compliant interactions, and generate training programs to address and / or correct these non-compliant interactions, thereby reducing the risks posed by non-compliant clinicians to patients and / or healthcare facilities. There is also a need for systems and methods that can identify clinicians who do not adhere to the institution's best practices and / or protocols, regulate the operation of in-structure devices to assist them in meeting best practice and / or protocol standards, identify resource centers to seek additional trained clinicians, and allow the institution's scheduling system to dynamically and efficiently schedule clinicians based on specified scheduling standards to reduce operational risk. The systems and methods disclosed herein effectively identify non-compliant interactions by clinicians and address these non-compliant interactions via training programs generated for these clinicians, thereby reducing operational risk by increasing the safety of medical devices and systems used in patient care.

[0007] According to various embodiments, a method includes: identifying one or more interactions between a first user and one or more medical devices; determining a compliance score associated with the first user based on the one or more interactions and a predetermined set of rules; in response to the compliance score not meeting a threshold compliance score, reducing the first user's access level to at least one of the one or more medical devices, and generating a training program associated with the at least one medical device and the one or more interactions, wherein reducing the access level includes reducing a certain number of corresponding features of the at least one medical device available to the first user; and automatically sending a training package associated with the training program to the first user without user participation, and notifying the first user to complete the training program using the training package.

[0008] According to some embodiments, a method includes tracking one or more interactions of a first user with one or more medical devices; determining a compliance score based on a stored set of rules and the one or more interactions; determining whether the compliance score meets a threshold compliance score; in response to determining that the compliance score meets the threshold compliance score, generating a training plan for the first user based on the one or more interactions; and adjusting one or more features of the one or more medical devices available to the first user at the one or more medical devices based on the training plan.

[0009] According to some embodiments, a method includes identifying interactions between a plurality of clinicians and one or more medical devices, and generating a performance score for each of the plurality of clinicians associated with the interactions based on a stored set of rules and one or more interactions of each user among the plurality of clinicians. The method includes receiving a first shift schedule associated with the plurality of clinicians and determining whether the first shift schedule meets one or more scheduling criteria associated with a healthcare institution. In response to determining that the first shift schedule does not meet the one or more scheduling criteria and that a first performance score of a first clinician does not meet a first assessment threshold of the one or more scheduling criteria: (1) generating a training plan for that clinician, or a new second shift schedule for the plurality of clinicians, the second shift schedule being based on a second performance score of a second clinician, replacing a first clinician scheduled in a first time period with a second clinician who is not currently scheduled in that time period, and (2) electronically preventing the first clinician from using at least one of the plurality of medical devices in the first time period. The method includes causing the new shift schedule or training plan to be displayed on a display device associated with a clinician scheduling system.

[0010] Other aspects include corresponding systems, equipment, and computer program products for implementing the aforementioned methods.

[0011] According to some embodiments, a system includes a memory storing instructions and one or more processors coupled to the memory and configured to execute the instructions such that the system identifies interactions between a plurality of clinicians and one or more medical devices, generates a performance score for each of the plurality of clinicians based on a stored set of rules and one or more interactions between each of the plurality of clinicians, and receives a first shift schedule associated with the plurality of clinicians. The one or more processors are configured to execute the instructions such that the system determines whether the first shift schedule meets one or more scheduling criteria associated with a healthcare institution, and when the first shift schedule does not meet the one or more scheduling criteria and a first performance score of a first clinician does not meet a first assessment threshold of the one or more scheduling criteria, (1) generates a new second shift schedule for the plurality of clinicians, the second shift schedule being based on a second performance score of a second clinician, replacing a first clinician scheduled in a first time period with a second clinician currently not scheduled in that time period, and (2) electronically prevents the first clinician from using at least one of the plurality of medical devices in the first time period. The one or more processors are configured to execute instructions that cause the system to display a new shift schedule on a display device associated with a clinician scheduling system. Other aspects include corresponding systems, devices, and computer program products for implementing the system.

[0012] According to some embodiments, a device management server includes one or more processors and a memory storing one or more programs configured to be executed by the one or more processors. The one or more programs include instructions for performing operations of any of the methods described in this application. According to some embodiments, a non-transitory computer-readable storage medium stores instructions that, when executed by a server system, cause the server system to perform operations of any of the methods described in this application. Attached Figure Description

[0013] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings. Throughout the drawings and description, the same reference numerals denote corresponding parts.

[0014] Figure 1A This is a block diagram of an example network architecture for identifying a clinician's non-compliance pattern, according to an illustrative embodiment.

[0015] Figure 1B This is a block diagram of an example device management server that communicates with a computing system of a medical device and a healthcare institution according to an illustrative embodiment.

[0016] Figure 2 This is a block diagram of an example server system based on the architecture of FIG1 according to an illustrative embodiment.

[0017] Figure 3 This is a block diagram of an exemplary client device based on the architecture of FIG1 according to an illustrative embodiment.

[0018] Figure 4 It is an example medical device that can be interacted with by clinicians within a medical institution.

[0019] Figure 5 yes Figure 4 A close-up view of a portion of the medical device shown.

[0020] Figure 6 This is a flowchart illustrating an example process of registering a clinician with a medical device and consenting to or refusing access to the medical device, according to an illustrative embodiment.

[0021] Figure 7 This is a flowchart illustrating an example process for determining performance scores for one or more clinicians in a healthcare facility, according to an illustrative embodiment.

[0022] Figure 8 This is a flowchart illustrating an exemplary process, according to an illustrative embodiment, of warning a drug system and / or a pharmacy technician that they are ignoring drug administration parameters and determining whether one or more drug administration parameters can be adjusted based on clinician interaction.

[0023] Figure 9 This is a flowchart illustrating an example process for rating and identifying one or more high-performing external clinician staffing resource centers, according to an illustrative embodiment.

[0024] Figure 10 This is a flowchart of an example process for verifying and / or optimizing a schedule for clinicians, based on an illustrative embodiment.

[0025] Figure 11 This is a flowchart illustrating an example process for identifying workflows according to an illustrative embodiment and generating warnings and / or reminders for subsequent activities of clinicians with low performance scores.

[0026] Figure 12 This is a flowchart of an example process for determining a clinician's non-compliance patterns according to an illustrative embodiment.

[0027] In one or more embodiments, not all components shown in each figure may be required, and one or more embodiments may include additional components not shown in the figures. Variations in the arrangement and type of components may be made without departing from the scope of this disclosure. Within the scope of this disclosure, additional components, different components, or fewer components may be utilized. Detailed Implementation

[0028] The detailed description set forth below is intended to describe various configurations of this disclosure and is not intended to represent the only configuration in which this disclosure may be practiced. The accompanying drawings are incorporated herein and form part of the detailed description. Specific details are included in the detailed description for the purpose of providing a thorough understanding of this disclosure. However, it will be apparent to those skilled in the art that this disclosure may be practiced without these specific details. In some cases, structures and components are shown in block diagram form to avoid obscuring the concepts of this disclosure. For ease of understanding, similar components are labeled with the same element numbers.

[0029] The terminology used in describing the various embodiments described herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or,” as used herein, describes and covers any and all possible combinations of one or more of the associated listed items. It should also be understood that although the terms “first” and “second” are used herein to describe different elements, these elements should not be limited by these terms. These terms are used only to distinguish one element from another. It will be further understood that, when used in this specification, the terms “include,” “including,” “comprise,” and / or “comprising” indicate the presence of the stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. Clinicians may include licensed or unlicensed individuals who operate, maintain, service, deliver, or otherwise interact with medical devices within, by, or used in a healthcare facility. Examples of healthcare facilities, as used herein, include hospitals, long-term care facilities, nursing homes, outpatient treatment centers, retail pharmacies, community clinics, non-acute care facilities, acute care facilities, etc.

[0030] Depending on the specifics, this subject matter provides a means for identifying users by individual or role, enabling clinical actions and other actions to be associated with the user. In this regard, medical devices may be configured with radio frequency identification (RFID) tag readers to wirelessly receive data associated with the identification information of a clinician stored in RFID tags, such as a clinician's badge or identification card. The medical device may be configured to consent to or deny access to one or more protected functions of a medical device and / or computing system associated with a healthcare facility based on the received clinician identification information, a set of passwords associated with one or more permissions, and / or one or more clinician badges associated with one or more permissions. Protected functions may include, but are not limited to, unlocking the medical device, specific clinical functions or workflows of the medical device (e.g., infusion of restricted and / or classified medications), access to biomedical service features (e.g., cleaning modes and / or features of the medical device, maintenance modes and / or features of the medical device, etc.), and other similar functions of the medical device.

[0031] According to various embodiments, the disclosed medical device can identify new users associated with a healthcare institution without prior registration at a central computing system, node, and / or server. For example, in response to a clinician attempting to access protected functions of the medical device (e.g., unlocking the device), attempting to access restricted functions, etc., the medical device can display a prompt on a display device associated with the medical device to provide clinician identification information, such as by scanning their badge. The medical device can be configured to determine whether the received clinician identification information exists in one or more data storage units associated with the medical device. If the medical device determines that the clinician identification information does not exist, it can display a prompt on a display device associated with the medical device to enter the clinician's password. In response to determining that the entered password is valid, the medical device can identify the permissions associated with the password, and based on the associated permissions, the medical device can grant and / or deny the clinician's access to the function. In some embodiments, the use of a password allows a clinician to access one or more functions of the medical device without scanning a badge and / or if the clinician does not have a badge.

[0032] Medical devices can send messages to a device management server to identify badge information and associated permissions received from clinicians. The device management server can be configured to automatically store and / or update a master list of clinician badges and associated permissions in one or more data storage units associated with the device management server. The device management server can automatically transmit new badge information and associated permissions to other medical devices within the healthcare facility.

[0033] This subject matter technology may also include a device management server configured to identify and track interactions between clinicians (e.g., nurses) and medical devices in a healthcare facility (e.g., a hospital), and based on these interactions, the device management server can determine the number of times a drug is administered outside of predetermined drug administration parameter values ​​(e.g., dosage). If this number meets a threshold, the device management server can add the drug to a set of drugs administered outside of the predetermined drug administration parameter values. In some embodiments, the device management server may be configured to provide one or more alerts to users (e.g., pharmacists, pharmacy technicians, etc.) indicating the set of drugs administered outside of predetermined drug administration parameter values. In this regard, in some embodiments, the device management server may provide and / or indicate corresponding entries for drug sets in the drug library of a healthcare facility's drug management system. In some embodiments, the device management server may be configured to determine changes to corresponding entries in the drug set based on data related to a clinician's drug administration (e.g., the dosage of the administered drug).

[0034] In some embodiments, a device management server may generate scores for one or more clinicians based on their interactions with medical devices, and schedule clinicians into different shifts based on their scores. In some embodiments, the device management server may be configured to schedule clinician shifts to include a predetermined percentage or ratio of high-scoring and low-scoring clinicians. In some embodiments, for one or more low-scoring clinicians scheduled in a shift, the device management server may schedule a clinician assigned as a mentor for the low-scoring clinician in that shift. In some embodiments, a healthcare facility may temporarily staff one or more clinicians from various clinician staffing agencies, and based on the clinicians' scores, the device management server may be configured to request clinicians from clinician staffing agencies associated with a majority of high-scoring clinicians. In some embodiments, the device management server may generate and / or update scores for clinicians based on their interactions with different medical devices.

[0035] In some embodiments, for clinicians with low scores, the device management server can be configured to provide the clinician with subsequent steps or one or more reminders that should be performed next. Examples of such steps may include, but are not limited to, checking device settings, checking vital signs, etc. In some embodiments, when a clinician is using a medical device to perform a procedure (e.g., a drug administration procedure), the device management server may display one or more steps related to the procedure on a display device associated with the medical device. (Refer to Figure 1-) Figure 12 Additional details about the technology in this topic are described.

[0036] Figure 1A This is a block diagram of a network architecture 100 according to some embodiments of the present subject matter.

[0037] Network architecture 100 includes one or more medical devices 104-1, 104-2, ..., 104-n, collectively referred to herein as medical device 104. The one or more medical devices 104 can be communicatively coupled to a device management server 108 and / or one or more computing systems 110-1, 110-2, ..., 110-m of healthcare institutions, collectively referred to herein as computing system 110, via one or more communication networks 106. Examples of the one or more communication networks include, but are not limited to, intranets, the Internet, cellular telephone networks, mobile data networks, wide area networks, local area networks, metropolitan area networks, etc. In some embodiments, the one or more communication networks 106 include public communication networks (e.g., the Internet and / or cellular data networks), private communication networks (e.g., private LANs or leased lines), or combinations of such communication networks. Device management server 108 can be configured to communicate with medical device 104 and / or computing system 110.

[0038] The device management server 108 can be configured to receive clinician-related data from the medical device 104 and / or the computing system 110 and / or transmit clinician-related data to the medical device 104 and / or the computing system 110. Examples of clinician-related data include, but are not limited to, clinician identifiers, clinician resume information, and information related to clinician training programs.

[0039] In some embodiments, the device management server 108 may be a single computing device (such as a computer server), while in other embodiments, the device management server 108 may be implemented by multiple computing devices working together to perform the actions of a server system (e.g., cloud computing). References Figure 2 Additional details about the device management server 108 are described.

[0040] Medical device 104 may include one or more input devices (such as...) Figure 3 As shown, these input devices are configured to receive input to the medical device 104. Clinicians (e.g., users 102-1, 102-2, ..., 102-n, collectively referred to herein as user 102) can interact with the one or more medical devices 104 via said input devices. User 102 can utilize the medical device 104 to access the device management server 108 and / or the computing system 110 to participate in relevant services provided by the device management server 108 and / or the computing system 110.

[0041] Now go to Figure 1B A block diagram of a device management server 108 communicating with a medical device 104 and a computing system 110 is shown. As previously described, the device management server 108 can communicate with the medical device 104 via a network architecture 100. In some embodiments, such as Figure 4 As shown, the medical device 104 may include a programming module 60 configured to connect to one or more functional modules.

[0042] Device management server 108 can be configured to receive data from computing system 110 related to one or more badges and / or passwords of clinicians, and permissions for one or more functions of one or more medical devices 104 associated with said badges and / or passwords, such as... Figure 1B As shown. In some embodiments, during the introduction of clinicians into one or more management systems (e.g., employee databases, etc.) of a healthcare institution, data related to clinicians' badges and / or passwords and associated permissions can be collected via the healthcare institution's computing system 110. Device management server 108 can be configured to receive configuration data and / or firmware for communication coupling with one or more medical devices 104, such as... Figure 1B As shown. The configuration data and / or firmware may be received from one or more other computing systems 110 within a healthcare facility.

[0043] Device management server 108 can be configured to transmit configuration data and / or firmware, data related to the one or more badges and / or passwords, and associated permissions to the one or more medical devices 104 communicatively coupled to device management server 108, such as... Figure 1B As shown. Data associated with the one or more badges may be linked to the clinician identification information of the one or more clinicians. In some embodiments, the clinician identification information may be a unique identifier associated with and / or configured to identify a clinician, such as an employee identifier, badge identifier, identifier associated with a clinician in another management system of the health institution (e.g., an EMR system), etc.

[0044] The one or more medical devices 104 can be configured to determine the validity of clinician identification information provided to the medical device (e.g., scanning of a badge by a clinician using the medical device's RFID reader) and / or a password received from a user of the medical device, based on received data associated with the one or more badges and / or passwords. The medical device 104 can be configured to grant or deny access to one or more functions of the medical device (e.g., unlocking the medical device, accessing restricted functions of the medical device, etc.) based on received data related to permissions associated with the one or more badges and / or passwords. For any clinician identification information not found in the received data, the medical device 104 can be configured to register the associated clinician and transmit the new clinician identification information to the device management server 108. The device management server 108 can transmit the clinician identification information and its associated permissions to other medical devices 104 within the healthcare facility. (References: This document refers to...) Figure 6 It describes additional details on determining the validity of a clinician’s identification information, consent to access one or more functions of a medical device, and registering a clinician via medical device 104.

[0045] The medical device 104 can be configured to associate the interaction between the clinician and the medical device with received clinician identification information (e.g., received badge information), and to transmit data related to the interaction to the device management server 108, such as... Figure 1B As shown. Device management server 108 can be configured to determine the clinician's performance score based on interactive data received from medical device 104, and device management server 108 can be configured to transmit data related to the performance score and corresponding clinician identification information (e.g., clinician's badge information, clinician's password, clinician's user identifier) ​​to the healthcare institution's computing system 110, allowing computing system 110 and / or users of computing system 110 to generate reports, such as reports related to clinician performance at the healthcare institution, such as... Figure 1B As shown. Device management server 108 can be configured to disable and / or lock one or more functions of a medical device based on a determined performance score. (References provided in this document) Figures 7-11 Additional details are described regarding the generation of performance scores for clinicians and the disabling and / or locking of one or more functions of medical devices.

[0046] Now go to Figure 2The diagram illustrates a block diagram depicting a device management server 108 according to some embodiments. The device management server 108 typically includes one or more processing units (processors or cores) 202, one or more network or other communication interfaces 204, memory 206, and one or more communication buses 208 for interconnecting these components. The communication buses 208 may optionally include circuitry (sometimes referred to as chipsets) for interconnecting and controlling communication between system components. In some embodiments, the device management server 108 may include a display device 212. In some embodiments, the device management server 108 may include input devices such as a keyboard, mouse, touchpad, and / or input buttons. In some embodiments, the display device 212 may include a touch-sensitive surface, in which case the display is a touch-sensitive display.

[0047] Memory 206 may be a high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, and / or other non-volatile solid-state memory devices. In some embodiments, memory 206 includes one or more storage devices located remotely from processor 202. Memory 206 (or alternatively, the non-volatile memory devices within memory 206) includes non-transitory computer-readable storage media. In some embodiments, memory 206 or the computer-readable storage media of memory 206 stores programs, modules, and / or data structures that can be used to perform one or more operations of device management server 108. For example, memory 206 may include programs, modules, and / or data structures for operating system 226, network communication module 228, clinician information module 230, clinician tracking module 232, clinician scoring module 234, clinician training program module 235, security module 236, and access device module 238.

[0048] In some embodiments, the operating system 226 module may include programs for handling various basic system services and for performing hardware-related tasks. The network communication module 228 may be configured to connect the device management server 108 to other computing devices via one or more communication network interfaces 204 (wired or wireless) and one or more communication networks 106. The clinician information module 230 may be configured to store data related to clinicians, including but not limited to clinician identifiers, clinician resume information, and clinician current compliance scores. The clinician tracking module 232 may be configured to track information related to clinicians' interactions with the medical device 104. The clinician tracking module 232 may be configured to track clinicians' interactions throughout their careers. The clinician tracking module 232 may be configured to group and / or categorize clinician interactions into one or more groups and / or categories. (References to this document) Figure 6 Additional details are described regarding the grouping and / or categorization of interactions.

[0049] The clinician scoring module 234 can be configured to generate scores for clinicians based on determining whether one or more interactions are compliant. In some embodiments, the clinician scoring module 234 can increase the score if the one or more interactions are compliant, and decrease the score if the one or more interactions are non-compliant. In some embodiments, the clinician scoring module 234 can be configured to generate and / or maintain scores for each group and / or each type of interaction. The access module 238 can be configured to grant, deny, and / or modify access to the device management server 108 and / or one or more other computing systems or devices communicatively coupled to the device management server 108.

[0050] The Clinician Training Program Module 235 can be configured to determine whether one or more interactions are compliant, and to generate and / or update compliance scores based on the compliance status of said one or more interactions. In some embodiments, the Clinician Training Program Module 235 can increase the compliance score if said one or more interactions are compliant, and decrease the compliance score if said one or more interactions are non-compliant. The Clinician Training Program Module 235 can be configured to generate training programs based on compliance scores. In some embodiments, the Clinician Training Program Module 235 can be configured to generate and / or maintain compliance scores for each group and / or each category of interactions, and can generate training programs for groups and / or categories of interactions with compliance scores that meet a threshold training program compliance score. The Access Module 238 can be configured to grant, deny, and / or modify access to the Server System 108 and / or one or more other computing systems or devices communicatively coupled to the Server System 108.

[0051] Now go to Figure 3 The diagram illustrates a block diagram depicting a medical device 104. The medical device 104 may include one or more processors 302, one or more network or communication interfaces 304, a memory 306, one or more communication buses 308, a user interface unit 310, a transmitter device 322, and a sensor device 323. The one or more processors 302, the one or more network or communication interfaces 304, the memory 306, and the user interface unit 310 may be configured to communicate with each other via the one or more communication buses 308. In some embodiments, the communication bus 308 may include circuitry (sometimes referred to as a chipset) that interconnects and controls communication between components of the medical device 104. In some embodiments, the medical device 104 may include an image / video capture device 324, such as a camera.

[0052] The user interface unit 310 may include a display 312, one or more input devices 316 (such as a keyboard or mouse), one or more audio output devices 318, and / or one or more audio input devices 320. In some embodiments, the display 312 may include a touch-sensitive display or surface 314 configured to receive input from the user 102. The one or more audio output devices 318 may include, but are not limited to, speakers, interfaces configured to transmit audio-related data to devices configured to transmit audio. The one or more input devices 320 may include, but are not limited to, microphones, interfaces configured to receive audio-related data transmissions from devices configured to receive audio.

[0053] Memory 306 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices; and may include non-volatile memory, such as one or more disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. In some embodiments, memory 306 includes one or more storage devices located remotely from processor 302. Memory 306 (or alternatively, the non-volatile memory devices within memory 306) includes non-transitory computer-readable storage media. In some embodiments, memory 306 or the computer-readable storage media of memory 306 stores programs, modules, and data structures that can be used to perform operations on medical device 104 and to implement the techniques described herein for identifying non-compliant patterns of interaction with medical device 104. Memory 306 may include operating system 326, network communication module 328, image / video capture module 330, audio input / output module 332, clinician information module 334, etc.

[0054] Operating system 326 can be configured to implement the execution of various system services of medical device 104, including but not limited to hardware and software-related tasks. Network communication module 328 can be configured to execute instructions to connect medical device 104 to one or more other computing devices, such as device management server 108, computing system 110, etc., via one or more communication interfaces 304 and a communication network (e.g., communication network 106). Image / video capture module 330 can be configured to execute instructions to capture images or continuous image streams. Audio input module 332 can be configured to process received input data and transmit instructions and / or related data to one or more other components of medical device 104. Access module 338 can be configured to grant, deny, and / or modify access to medical device 104. For example, access module 338 can be configured to grant or deny access to medical device 104 based on received login credentials for medical device 104.

[0055] The modules and applications identified above may correspond to a set of executable instructions for performing one or more functions of the methods described above and / or in this application (e.g., computer-implemented methods and other information processing methods described herein). One or more modules may be implemented as a specific hardware device with appropriate input and output signal paths. In different embodiments, modules may be combined or otherwise rearranged. In some embodiments, memory 206 and / or memory 306 stores a subset of the data structures and modules identified above. In some embodiments, memory 206 and / or memory 306 stores additional modules and data structures not described above. In some embodiments, processor 302 may be configured to execute the modules identified above to implement one or more of the functions and / or techniques described above. Figure 4 It is an example medical device that clinicians in medical institutions can interact with. Figure 4 The illustrated medical device 104 may include a programming module 60 configured to connect to one or more functional modules, such as four fluid infusion pumps 22, 24, 26, and 28, each operatively engaged with a corresponding fluid application kit 30, 32, 34, and 36. Fluid supply sources 38, 40, 42, and 44 (which may take various forms, but are shown as bottles in this case) are inverted and suspended above the pumps. The fluid supply sources may also take the form of bags or other types of containers. The medical device 104 and the fluid supply sources 38, 40, 42, and 44 are all mounted to a roller or rod 46. A specific fluid supply source within the care area, along with its orientation (e.g., mounting location, mounting height, mounting type, etc.), can generate one or more interaction records. For example, an interaction record for the kit can be partially generated by detecting a scannable code associated with the kit prior to use. Once scanned, the interaction record can be recorded for use as described herein.

[0056] like Figure 4 As illustrated in the example embodiment, each application kit 30, 32, 34, and 36 is connected between the corresponding fluid supply sources 38, 40, 42, and 44 and the same patient 48, allowing the patient to receive fluid from all fluid sources. Application kits can be actively identified, for example, by a clinician's scan, or passively identified, for example, by wireless or optical detection of the application kit. Similar to the fluid supply sources, once identified, an interaction log can be generated to identify one or more of the application kit, as well as the clinician, the programming module, the pump, and the application kit's location (e.g., application location (e.g., left forearm, right upper arm, etc.)).

[0057] Individual infusion pumps 22, 24, 26, and 28 can be used to infuse each fluid from a fluid supply source into the patient. The infusion pump is a flow control device that acts on the corresponding tubing or fluid conduit of the fluid administration kit to move fluid from the fluid supply source through the conduit to the patient 48. Because independent pumps are used, each pump can be independently set with pumping or operating parameters required to infuse a specific medical fluid into the patient from the corresponding fluid supply source at a specific rate prescribed by the clinician for that fluid. Activities performed by the pumps or the clinician to infuse a specific medical fluid can be associated with one or more interactions, which can be recorded and processed as described.

[0058] Typically, medical fluid application kits have more parts than Figure 4 The figures show many features, including check valves, drip chambers, valved ports, connectors, and other devices well known to those skilled in the art. These other devices are not included in the figures to maintain clarity.

[0059] Figure 5 yes Figure 4 A close-up view of a portion of the medical device shown. Figure 5 Two fluid infusion pumps are shown mounted on either side of a programming module, along with a display and control keys for each pump, wherein the programming module is capable of programming both infusion pumps. Pump 22 includes a door 50 and a handle 52, which is operated to lock the door in a closed position for operation, and to unlock and open the door to access the internal pumping and sensing mechanisms and to load the application kit for the pump. When the door 50 is open, tubing can be connected to pump 22. When the door 50 is closed, the tubing is operationally engaged with the pumping mechanisms, upstream and downstream pressure sensors, and other equipment of the pump. In some embodiments, a display 54 (e.g., an LED display) may be located in a plan view on the door and may be used to visually convey various information related to pump 22, such as warning indications (e.g., alarm messages). Control keys 56 are used to program and control the operation of the infusion pumps as needed. In some embodiments, the control keys may be omitted and presented as interactive elements on display 54 (e.g., a touchscreen display). Infusion pump 24 also includes an audio alarm device in the form of a speaker (not shown).

[0060] exist Figure 4 In the example shown, program module 60 is attached to the left side of infusion pump 24. Other devices or modules (including another infusion pump) may be attached to the right side of infusion pump 24, such as... Figure 4As shown. In such a system, each attached pump represents the pump channel of the entire medical device 20. In some embodiments, the programming module is used to provide an interface between the infusion pump 24 and external devices, as well as to provide most of the operator interface for the infusion pump 24. Attention turns to U.S. Patent No. 5,713,856, entitled “Modular Patient Care System” by Eggers et al., which is incorporated herein by reference, in which the programming module is described as a high-level interface unit.

[0061] Back Figure 5 The programming module 60 includes a display 62 for visually conveying various information, such as operating parameters of pump 24, as well as warning indications and alarm messages. The programming module 60 may also include a speaker to provide audible alarms. The programming module 60 may also include one or more input devices, such as control keys 64 or a barcode scanner (not shown), for scanning information related to infusion, patient, clinician, or other relevant information. In some embodiments, the display 62 may be implemented as a touchscreen display (e.g., display 312). In such embodiments, the number of control keys 64 may be omitted or reduced by providing appropriate interactive elements through a graphical user interface presented via the display 62. The programming module 60 may include a communication system (not shown) that can be used to communicate with external equipment (such as a medical facility server or other computer) and portable processors (such as handheld communication devices or laptop computers), or other information devices that a clinician may need to use to transmit information and download drug catalogs to the programming module 60 or the pump. The communication module can be used to transmit access and interaction information to clinicians encountering the programming module or devices coupled thereto (e.g., pump 22 or barcode scanner). The communication system may include one or more radio frequency (RF) systems, such as RFID systems, optical systems (e.g., infrared), Bluetooth systems, or other wired or wireless systems. The barcode scanner and communication system may alternatively be integrated with the infusion pump 24, for example, without using the programming module, or in addition to having the programming module 60. Furthermore, the information input device does not require hardwiring to the medical instrument, and information can also be transmitted wirelessly.

[0062] Figure 5 The example shown includes a second pump module 26 connected to the programming module 60. (As...) Figure 4As shown, more pump modules can be connected. Additionally, other types of modules can be connected to pump modules or programming modules, such as infusion pump modules, pulse oximeter readers, and patient-controlled analgesia modules. Each module can generate interaction logs of one or more interaction types. Interaction logs can include identifiers of the modules or devices with which they interact. Identifiers can include device type identifiers, model or series identifiers, or unique identifiers for a specific device.

[0063] Now go to Figure 6 The diagram illustrates the process of registering a clinician with a medical device and granting or denying access to the device. For a clearer example, refer to [reference needed]. Figure 1A The components and references of the network architecture 100 shown and described Figure 1B Components shown and described, references Figure 2 The components of the device management server 108 shown and described, and references Figure 3 , Figure 4 and Figure 5 The components of the medical device 104 shown and described can be used to describe the process of registering a clinician with the medical device and consenting to or refusing access to the medical device.

[0064] Method 600 includes transmitting data associated with clinician identification information and / or passwords of one or more clinicians to medical device 104 via processor 202 of device management server 108 (box 601). As described above, examples of clinician identification information may include, but are not limited to, badge identifiers, passwords, identifiers from different health and / or management systems (e.g., EMR systems), and similar information associated with clinicians. As described above, device management server 108 may store clinician identification information and / or passwords of one or more clinicians authorized to one or more functions of the medical device. Device management server 108 may transmit password-associated authorization data to medical device 104. Medical device 104 displays a prompt on a display device for the user to provide clinician identification information (box 602). For example, processor 302 of medical device 104 may display a prompt on a display device (e.g., display 62) associated with medical device 104 for the user to scan their badge near the RFID reader of the medical device. Medical device 104 receives the clinician identification information (box 603). The processor 302 of the medical device 104 can receive clinician identification information from RFID tags (e.g., clinician badges or identification cards) via the RFID reader of the medical device 104.

[0065] Medical device 104 can be configured to determine whether received clinician identification information exists (block 604). In some embodiments, medical device 104 can determine whether received clinician identification information exists by providing the clinician identification information to device management server 108, and receiving confirmation of whether the clinician associated with the identification information is valid, active, and / or in good condition (e.g., the clinician is not suspended). As described above, for example, refer to Figure 1B The device management server 108 can receive data related to the clinician identification information of each clinician, such as data related to the clinician's badge identifier ("badge identifier data"), password ("password data"), clinician identifiers in different management and / or health systems (e.g., EMR system), and permissions associated with the clinician identification information used for different clinicians.

[0066] For example, medical device 104 can receive a clinician's badge identifier as clinician identification information, and can determine whether the received badge identifier exists by providing the badge identifier to device management server 108 (or medical device 104). Device management server 108 can search for the badge identifier in badge identifier data stored in one or more data storage units associated with device management server 108, and provide a confirmation message to medical device 104 based on the search results, indicating whether the badge identifier is valid, active, and / or in good condition.

[0067] In some embodiments, in response to determining that clinician identification information received from medical device 104 is valid, active, and / or in a good state, device management server 108 may be configured to identify the associated permissions and transmit the permissions to medical device 104 to ensure that medical device 104 contains up-to-date permission data. Medical device 104 may be configured to update stored permission data for clinicians using permission data recently received from device management server 108.

[0068] If medical device 104 determines that the received clinician identification information exists ("Yes" at box 604), method 600 proceeds to box 605. Medical device 104 applies one or more permissions associated with the clinician identification information and sends a message to device management server 108 indicating whether it agrees to allow the clinician access to medical device 104 (box 605). As described above, in some embodiments, the permissions associated with the clinician identification information may indicate whether the clinician has permission to unlock the device, whether the permission to unlock the device changes based on the clinician's low performance score, whether the clinician requests a second clinician to also provide their clinician identification information to agree to access the device, whether the clinician has permission to access certain restricted functions, etc. If medical device 104 determines that the received clinician identification information does not exist ("No" at box 604), method 600 proceeds to box 606.

[0069] The processor 302 of medical device 104 displays a prompt for a clinician to enter a password on a display device associated with medical device 104 (box 606). Processor 302 may receive a password provided by the clinician and determine whether the password is valid (box 607). Processor 302 may be configured to determine the validity of a password based on whether the password is found in a password list received from device management server 108. For example, if processor 302 cannot find the password in the received password list, processor 302 determines the password is invalid. If processor 302 determines the password is invalid, method 600 proceeds to box 608. Processor 302 electronically prevents the clinician from using the medical device (box 608). Processor 302 may be configured to electronically prevent the clinician from using medical device 104 by preventing the clinician from logging into medical device 104, denying the clinician access to medical device 104 and / or the functionality of modules connected to medical device 104, electronically locking medical device 104, and / or electronically disabling medical device 104. In some embodiments, processor 302 may disable the functionality of any module connected to medical device 104. For example, after medical device 104 is electronically locked and / or electronically disabled, processor 302 may stop or prevent the infusion of any medication to the patient via a pump module connected to medical device 104.

[0070] Processor 302 may place medical device 104 in an electronically locked and / or disabled state until medical device 104 receives clinician identification information associated with permissions for one or more functions of medical device 104. For example, processor 302 may place medical device 104 in an electronically locked and / or disabled state until processor 302 receives badge information and / or password of a clinician authorized to unlock medical device 104 or granted electronic access to use medical device 104. Returning to box 607, if processor 302 determines that the password is valid (e.g., by identifying the password in a list of received passwords), method 600 proceeds to box 609. Processor 302 applies the permissions associated with the password (box 609). Based on the permissions associated with the password, processor 302 grants access to medical device 104. Processor 302 can associate the password and associated permissions with the clinician identification information (e.g., clinician badge identifier) ​​received in block 604, and transmit the clinician identification information, associated password, and associated permissions to device management server 108 (block 610). Processor 202 of device management server 108 transmits new clinician identification information and associated passwords and permissions to other medical devices 104 (block 611). In some embodiments, processor 202 can transmit new clinician identification information and associated passwords and permissions to other medical devices 104 in multiple healthcare facilities within a medical institution. Processor 202 can store the new clinician identification information associated with the associated password and permissions in one or more data storage units associated with device management server 108.

[0071] As the device management server 108 transmits new clinician identification information and associated permissions to other medical devices 104 within a healthcare facility and / or organization, it ensures that the medical devices 104 are updated with the latest clinician identification information and associated permissions. Therefore, a clinician registered with one medical device 104 can be recognized at other medical devices 104 without having to register at those devices. Permissions granted and / or updated to the clinician are also applied to other medical devices 104, thus providing the clinician with similar access and / or functionality. For example, if a clinician registered with the first medical device 104 provides his / her clinician identification information to the second medical device 104, such as by scanning his / her badge at the second medical device 104, the second medical device 104 can determine, based on the corresponding clinician identification information received from the device management server 108, whether that clinician identification information exists, is valid, active, and / or in good condition, and apply the permissions associated with that clinician identification information based on the corresponding permission data received from the device management server 108. The second medical device 104 can be configured to use the techniques described in reference boxes 604 and 605 above to determine whether clinician identification information exists, is valid, active, and / or in good condition, and to apply the associated permissions.

[0072] In some embodiments, operating parameters and / or preferences may be associated with one or more clinicians (e.g., with corresponding clinician identification information). Examples of operating parameters and / or preferences may include, but are not limited to, modifications made by clinicians to user interfaces and / or workflows associated with one or more medications frequently administered by the clinician. In such embodiments, device management server 108 may provide operating parameters associated with clinicians to medical device 104, and processor 302 of medical device 104 may be configured to update the display device associated with medical device 104 based on the associated operating parameters. For example, for medications identified as frequently administered, processor 302 may modify the associated user interface based on one or more operating parameters and / or preferences indicating modifications made by the clinician to the user interface when administering the medication.

[0073] As described above, in some embodiments, medical device 104 may be configured to receive a clinician's identifier from a patient-related system (e.g., an EMR system) of a healthcare institution. Processor 302 may be configured to determine whether a clinician's identifier (e.g., a clinician's identifier in the EMR) exists in one or more data storage units associated with medical device 104. If the identifier exists, processor 302 may apply the permissions associated with medical device 104. If processor 302 determines that the identifier does not exist, processor 302 may prompt the clinician for other clinician identification information (e.g., scanning the clinician's badge) and / or the clinician's password to determine whether to grant access to medical device 104. If processor 302 determines that valid clinician identification information and / or a password are provided, processor 302 may apply the associated permissions and transmit information related to the clinician's identifier in the patient-related system to device management server 108, and device management server 108 may use the clinician's identifier in the patient-related system and associated permissions, password, and / or other clinician identification information to automatically update other medical devices 104.

[0074] As other medical devices 104 receive the clinician's identifier and associated permissions from the patient-related system, the clinician can now be recognized by the other medical devices 104. Therefore, the permissions associated with the clinician's identifier in the patient-related system at one medical device 104 can be applied by another medical device 104 that receives the clinician's identifier in the patient-related system. For example, if a patient associated with a second medical device 104 is under the care of a clinician, and the second medical device 104 receives the clinician's identifier in the corresponding EMR system, the second medical device 104 can be configured to apply the permissions associated with that clinician's identifier without registering the clinician's identifier in the EMR system at the second medical device 104.

[0075] Now go to Figure 7 The diagram illustrates a process for determining performance scores for one or more clinicians in a healthcare facility. For a clearer example, see [reference needed]. Figure 1A The components and references of the network architecture 100 shown and described Figure 1B Components shown and described, references Figure 2 The components of the device management server 108 shown and described, and references Figure 3 , Figure 4 and Figure 5 The components of the medical device 104 shown and described can be used to describe a process by which one or more clinicians in a healthcare facility determine performance scores.

[0076] Method 700 includes receiving information associated with a clinician's identifier at medical device 104 by a processor 202 of device management server 108 (box 701). As described above, processor 202 may receive information associated with the clinician's identifier in response to a clinician attempting to access medical device 104 (e.g., by scanning his or her identification card at medical device 104). Processor 202 also receives information associated with one or more interactions between the clinician and the medical device (box 702). As described above, examples of information related to the interaction between the clinician and medical device 104 include, but are not limited to, the simultaneous administration of two or more drugs, drug-drug interactions between the simultaneously administered drugs, the volume of drugs administered, the dosage of drugs administered, the area of ​​care in which the clinician interacts with the medical device, the type of drug administered, the type of patient receiving the drug, the response time to one or more alarms generated by the medical device, the medical route of drug administration (e.g., intravenous, subcutaneous, intra-arterial, epidural, etc.), the type of administration kit used for the fluid or drug (e.g., tubing, syringe, or connector), the duration of use of the administration kit, the type of tubing and connector used during infusion, tubing replacements (e.g., tubing replaced within 72 hours, 96 hours, etc.), the specific drug administered to the patient, the volumetric rate of drug administration (e.g., administration at a rate of 75 ml per hour), and other similar information. Interactions can also be associated with sequences to determine which interactions occurred and the order or timing of these interactions.

[0077] Processor 202 generates and / or updates a clinician's performance score based on one or more interactions between the clinician and the medical device (box 703). Device management server 108 may be configured to store clinician performance scores associated with the clinician (e.g., associated with the clinician's identifier) ​​in one or more data storage systems associated with device management server 108. In some embodiments, processor 202 may be configured to determine whether a clinician can obtain a performance score by searching one or more data storage systems associated with device management server 108. If processor 202 retrieves a performance score associated with the clinician, processor 202 updates the performance score based on information received related to one or more interactions with the clinician. If no performance score is retrieved, processor 202 generates a performance score based on information received related to one or more interactions with the clinician and stores the performance score associated with the clinician in one or more data storage systems associated with device management server 108.

[0078] Processor 202 can be configured to generate and / or update performance scores based on whether the interaction between the clinician and the medical device satisfies a set of rules associated with one or more procedures for treating a patient. Examples of the one or more procedures for treating a patient include, but are not limited to, administering medication to a patient using a medical device, responding to alarms generated by a medical device connected to the patient, patient follow-up after administration of certain medications, patient monitoring, etc. Examples of the set of rules associated with the procedures may be specifying predetermined volumetric rates, pressure rates, doses, volumes, etc., for one or more medications. In some embodiments, the set of rules may also specify a group or more groups of medications that can be administered simultaneously or sequentially. In some embodiments, the set of rules may specify different volumetric rates, pressure rates, dose rates, etc., for different types of patients (e.g., patients with heart disease, obese patients, patients with one or more allergies, etc.). In some embodiments, the set of rules may further specify different medical routes of administration of the medication (e.g., intravenous, epidural, subcutaneous, other parenteral routes, etc.), through which the medication can be administered.

[0079] Processor 202 can determine whether an interaction between a clinician and a medical device in the process of treating a patient satisfies a corresponding set of rules by comparing received information related to one or more interactions with corresponding values ​​and / or interactions specified by the rule set. For example, if a clinician administers two medications simultaneously, and the rule set specifies one or more sets and / or groups of medications that can be administered simultaneously, processor 202 can verify whether both medications are listed as part of a set or group of medications that can be administered simultaneously. If processor 202 determines that neither medication is part of a set or group of medications that can be administered simultaneously, processor 202 can determine that the clinician's interaction does not satisfy the rule set for the medication administration process and generate and / or adjust (e.g., reduce) the clinician's performance score to reflect the interaction. If processor 202 determines that both medications are part of a set or group of medications that can be administered simultaneously, processor 202 can determine that the clinician's interaction satisfies the rule set and generate and / or adjust (e.g., increase) the clinician's performance score to reflect the interaction.

[0080] In some embodiments, a performance score can be determined by identifying rules applicable to the interaction within a selected time period. This time period can be provided as input. In some embodiments, the time period can be provided as input via a user interface. In some embodiments, the time period can be listed in configuration parameters of the device management server 108. The processor 202 can obtain the object's interactions within the time period. The processor 202 can then obtain applicable rules from a set of rules used for the program. This filtering can reduce the amount of resources required to generate a performance score for the object. Once the applicable rules are obtained, the processor 202 can then evaluate the interaction by comparing it to the applicable rules. The interaction record can include an interaction type. For example, the interaction type can be used as a key for identifying relevant compliance rules by matching an identifier for the interaction type with a value specified in or by a rule used for the process. The interaction record can also include interaction data that identifies, for example, volume set by the program, rate set by the program, or other clinician behaviors used for the interaction. Each rule can contribute a value to the overall performance score.

[0081] Processor 202 can be configured to update performance scores by a predetermined adjustment amount. In some embodiments, processor 202 can be configured to determine the amount based on the frequency with which clinician interactions meet corresponding rules within a predetermined time period. For example, if a clinician administers medication at an incorrect dosage several times within a 30-day period, processor 202 can reduce the performance score by a larger amount for each subsequent occurrence.

[0082] Processor 202 can update and / or maintain a clinician's performance score throughout their career by associating the performance score with the clinician's identifier. In some embodiments, a clinician's performance score can be a cross-product performance score, reflecting the clinician's performance score across different medical device products. For example, processor 202 can update and / or maintain a clinician's device-specific performance score, wherein each device-specific performance score can be associated with a different medical device product, and the device-specific performance score can be based on one or more interactions between the clinician and the medical device product. In such embodiments, processor 202 can generate, maintain, and / or update a aggregated performance score based on one or more device-specific performance scores.

[0083] Processor 202 determines whether the clinician's performance score meets a low performance score threshold (box 704). A low performance score threshold can be a predetermined performance score indicating that the clinician requires additional guidance and support to satisfactorily complete one or more patient treatment procedures. If processor 202 determines that the performance score does not meet the low performance score threshold (e.g., the performance score is greater than the low performance score threshold) ("Yes" at box 704), method 700 proceeds to box 707. Processor 202 then determines that the performance score meets a high performance score threshold (box 707).

[0084] If processor 202 determines that the performance score does not meet the high performance score threshold (e.g., less than the high performance score threshold) (No at box 707), method 700 proceeds to box 701. If processor 202 determines that the performance score meets the high performance score threshold (e.g., equal to or greater than the high performance score threshold) (Yes at box 707), method 700 proceeds to box 708. Processor 202 adds the clinician to the list of mentor clinicians (box 708). In some embodiments, each clinician in the list of mentor clinicians may be associated with a performance score that meets the high performance score threshold. Processor 202 may store the list of mentor clinicians in a data structure in one or more data storage systems associated with device management server 108. In some embodiments, processor 202 may add a clinician to the list of mentor clinicians by adding the clinician's identifier to the data structure containing the list of mentor clinicians.

[0085] At box 704, if processor 202 determines that the performance score meets a threshold low performance score (e.g., the performance score is equal to or less than the threshold low performance score) ("Yes" at box 704), then method 700 proceeds to box 705. Processor 202 identifies the clinician's mentor clinician (box 705). In some embodiments, processor 202 identifies the mentor clinician associated with the least number of clinicians. Processor 202 associates the mentor clinician with the clinician (box 706). Processor 202 stores the mentor clinician-clinician association in a data storage system associated with device management server 108.

[0086] Device management server 108 can be configured to leverage clinician performance scores to improve the efficiency and performance of other systems in a healthcare organization that are communicatively coupled to device management server 108. For example, in some scenarios, a healthcare organization may utilize external clinician staffing resource centers to access temporary or traveling clinicians who can assist the healthcare organization, and device management server 108 can be configured to identify one or more high-performing external clinician staffing resource centers based on the performance scores of its clinicians.

[0087] This article references Figure 9 Additional details are described regarding the identification of one or more high-performing external clinicians equipped with resource centers. In another example, the device management server 108 can be configured to optimize clinician scheduling based on clinician performance scores and / or scheduling criteria. (References provided) Figure 10 Additional details regarding optimizing clinician scheduling are described. In yet another example, the device management server 108 can identify clinicians with low performance scores and generate warnings and / or reminders for subsequent activities these clinicians need to complete. References Figure 11 Additional details are described regarding the generation of warnings and / or reminders for subsequent activities of clinicians with low performance scores.

[0088] In some embodiments, processor 202 may be configured to identify a set of clinicians with performance scores that meet a high threshold performance score over a threshold time period (e.g., several weeks, consecutive months, etc.) as highly valued clinicians, and associate titles (e.g., “Hall of Fame,” “MVP,” etc.) and / or graphic icons (e.g., a graphical crown, etc.) with these clinicians, and may transmit the association of titles and / or graphic icons with clinicians to medical device 104. For example, processor 202 may be configured to identify a set of clinicians with performance scores that meet a high threshold performance score over five consecutive months as “Hall of Fame” clinicians, and associate the “Hall of Fame” title and graphical crown icon with the corresponding clinician identification information of the clinicians. In some embodiments, processor 302 of medical device 104 may be configured to determine whether a clinician requesting access to medical device 104 is associated with any specific title (e.g., “Hall of Fame,” “MVP,” etc.) and / or graphic icon, and display the associated title and / or graphic icon (e.g., near the clinician’s name) on a display device associated with medical device 104.

[0089] In some embodiments, processor 202 may be configured to identify one or more high-performing care areas (e.g., intensive care units, emergency rooms, wards, etc.) and / or one or more low-performing care areas within a healthcare facility based on the performance scores of clinicians associated with care areas. In some embodiments, processor 202 may be configured to display the one or more high-performing care areas on one or more display devices located on one or more floors of the healthcare facility. In some embodiments, processor 202 may be configured to generate messages and transmit messages to clinicians associated with low-performing care areas, indicating that their associated care area is a low-performing care area. In some embodiments, processor 202 may be configured to identify a set of clinicians with low performance scores within a threshold time period and / or low-performing care areas, and associate the set of clinicians and / or the care areas with a group name (e.g., a "regret wall" group name, etc.).

[0090] In some embodiments, device management server 108 may be configured to transmit instructions to medical device 104 to electronically lock medical device 104 and / or deny access to one or more features of medical device 104 to clinicians whose performance scores meet a low performance threshold score. In response to receiving the instruction, medical device 104 may be configured not to grant clinicians access to any function of the medical device (e.g., unlocking medical device 104). In some embodiments, device management server 108 may be configured to associate a clinician with a performance score meeting a low performance threshold score with a second clinician (e.g., a mentor clinician) and require the second clinician to also provide their clinician identification information so that medical device 104 agrees to access by the clinician with the low performance score. In some embodiments, device management server 108 may be configured to compile training packages to address clinicians' low performance scores. In some embodiments, device management server 108 may be configured to determine the effectiveness of the training packages based on changes in the clinician's performance score. In some embodiments, the device management server 108 may be configured to display additional safety warnings on a display device associated with the medical device and / or modify workflows within the medical device to mitigate any safety risks when a clinician with a low performance score is interacting with the medical device. In some embodiments, the processor 202 may cause a clinician with a low performance score to be electronically locked out of the medical device 104 and / or denied access to one or more features of functional modules (e.g., an infusion pump connected to the medical device 104) to prevent the clinician from initiating and / or interfering with drug administration. Additional details regarding electronically locking the clinician out of the medical device and / or denying access to one or more features of the medical device, generating and / or assembling training packages, evaluating the effectiveness of training, and / or requiring a second clinician to authorize access to the medical device and / or one or more functions of the medical device are described in U.S. Provisional Patent Application No. 62 / 865,906, which is incorporated herein by reference.

[0091] Now go to Figure 8 The diagram illustrates a process for alerting healthcare facility pharmacy systems and / or pharmacy technicians to clinicians who may be neglecting medication administration parameters, and for determining whether one or more medication administration parameters can be adjusted based on one or more interactions between the clinician and the medical device used to administer the medication. For a clearer example, see [link to documentation]. Figure 1A The components and references of the network architecture 100 shown and described Figure 1B Components shown and described, references Figure 2 The components of the device management server 108 shown and described, and references Figure 3 , Figure 4 and Figure 5 The components of the medical device 104 shown and described can be used to describe the operational parameters for warning healthcare institutions’ drug systems and / or pharmacy technicians and clinicians to neglect drug administration, and to determine whether one or more drug administration parameters can be adjusted based on one or more interactions between the clinician and the medical device used to administer the drug.

[0092] Method 800 includes receiving information associated with a clinician's identifier at medical device 104 by a processor 202 of device management server 108 (block 801). In response to a clinician attempting to access medical device 104, processor 202 may receive information associated with the clinician's identifier. In some embodiments, a clinician may attempt to access medical device 104 by providing his or her access credentials (e.g., scanning his or her identification card at medical device 104). The clinician's access credentials may be associated with and / or include the clinician's unique identifier, and medical device 104 may be configured to transmit the unique identifier associated with the clinician to device management server 108 in response to successfully granting access to the clinician. Examples of a clinician's unique identifier include, but are not limited to, user identifiers, employee identifiers, etc.

[0093] Processor 202 identifies a predetermined care area within a healthcare facility based on the location information of the medical device (box 802). The location of the medical device can be determined by a GPS locator system within the medical device, or by the medical device transmitting or connecting to a specific WiFi transceiver at a known location. Examples of care areas include, but are not limited to, intensive care units (ICUs), patient rooms, etc. Processor 202 receives information related to one or more interactions between a clinician and the medical device (box 803). Examples of information related to interactions between a clinician and medical device 104 include, but are not limited to, administering a certain medication to a patient, the volumetric rate of medication administration (e.g., administering medication at a rate of 105 ml per hour), etc. In some embodiments, processor 202 can group the clinician's medical device interactions into groups associated with the predetermined care area where the medical device is located. For example, processor 202 can group interactions between a clinician and a medical device located in an ICU into a group associated with the ICU, and can group interactions between a clinician and different medical devices located in a patient room into a group associated with the patient room.

[0094] Processor 202 identifies a medication being administered to a patient using a medication device (block 804). In some embodiments, processor 202 may identify the medication based on one or more interactions between a clinician and a medical device. For example, the interaction between the clinician and the medical device may be the use of the medical device to schedule the administration of a medication to a patient, and information associated with the interaction may indicate the name and / or identifier of the medication, and processor 202 may determine the medication being administered to the patient based on the name and / or identifier of the medication indicated by the information associated with the interaction. In some embodiments, processor 202 may identify the medication being administered based on patient records in an EMR system communicatively coupled to device management server 108.

[0095] Processor 202 determines whether the drug is administered outside of predetermined values ​​for drug administration parameters (box 805). Examples of drug administration parameters may include, but are not limited to, drug dosage, volumetric rate of drug administration, simultaneous administration of two or more drugs, drug-drug interactions of simultaneously administered drugs, volume of drug administered, a list of drugs that can be administered simultaneously with the drug, and the volume of drug administered. Predetermined values ​​for drug administration parameters may be stored in association with the drug in a data storage system associated with a drug management system. Predetermined values ​​for drug administration parameters may be provided to the drug management system as input by a user of the drug management system (e.g., a pharmacy technician). Device management server 108 may be communicatively coupled to the drug management system. In some embodiments, processor 202 may receive predetermined values ​​for one or more drug administration parameters from a medical device and / or the drug management system. In some embodiments, processor 202 may be configured to query the drug management system for predetermined values ​​for one or more drug administration parameters.

[0096] Processor 202 can determine one or more administration values ​​for a drug by the clinician based on received information related to one or more interactions between the clinician and the medical device. For example, the received information may instruct the clinician to administer the drug at a volume rate of 100 ml per hour. Processor 202 can determine whether the drug is administered outside of a predetermined administration parameter value based on a comparison of the administration value with a predetermined value for the corresponding administration parameter. For example, if the clinician administers the drug at a volume rate greater than or less than a predetermined volume rate for that drug, processor 202 can determine that the drug is administered outside of a predetermined administration parameter value.

[0097] If processor 202 determines that the medication was not administered outside of a predetermined administration parameter value (No at box 805), method 800 proceeds to box 801. If processor 202 determines that the medication was administered outside of a predetermined administration parameter value (Yes at box 805), the method proceeds to box 806. Processor 202 updates a counter (box 806). The counter may be associated with the medication and / or the medication's administration parameter. The counter may be associated with a predetermined care area. For example, processor 202 may maintain multiple counters for a single medication and / or an administration parameter for the medication, wherein each counter may be associated with a different predetermined care area of ​​a healthcare facility. Processor 202 may update the counter by incrementing it by a predetermined value (e.g., incrementing the value by one) to indicate that the medication was again administered outside of the predetermined administration parameter value.

[0098] Processor 202 determines whether the number of times the medication was administered outside of predetermined values ​​of the administration parameters meets a threshold (box 807). Processor 202 may determine whether the threshold is met based on the value of a counter. If the threshold is not met (“No” at box 807), method 800 proceeds to box 801. In some embodiments, processor 202 may update (e.g., reduce) the score associated with the clinician to indicate that the clinician has not satisfactorily followed the expected medication administration procedure. If processor 202 determines that the threshold is met (“Yes” at box 807), method 800 proceeds to box 808. In some embodiments, if processor 202 determines that the threshold is met, processor 202 may not negatively adjust the clinician's performance score.

[0099] Processor 202 transmits one or more drug warnings (box 808) to the user of the drug management system. Processor 202 may indicate the corresponding entry for the drug in the drug management system and / or other information related to drug administration in the warning. For example, processor 202 may include information related to the drug's identifier in the drug management system and the clinician in the designated care area who administered the drug outside of predetermined values. In some embodiments, processor 202 may add the drug to a list of drugs that have been administered a threshold number of times outside of one or more corresponding predetermined values ​​of their administration parameters. Processor 202 may transmit instructions to the drug management system to display graphical icons on a display device associated with the drug management system, wherein the graphical icons identify the drug list and indicate that these drugs are most frequently administered outside of predetermined values. In some embodiments, processor 202 may sort the drug list based on the number of times the drug was administered outside of predetermined values ​​(e.g., the top 10 drug violators) and include the sorted list in the warning. In some embodiments, if a threshold number of times is not met, the processor 202 may sort a list of clinicians who most frequently administer drugs outside of predetermined parameters and include that list in a warning so that the list is displayed on a display device associated with the drug system.

[0100] In some embodiments, processor 202 may determine a new value as a predetermined value for the administration parameter of a drug in a list. Processor 202 may determine the new value of the administration parameter based on the administration parameter value of the drug administration. For example, if a threshold number of drug administrations are performed at a volume rate exceeding a predetermined volume rate value (e.g., 100 ml / hour), processor 202 may calculate an average of the administration volume rates (e.g., 105 ml / hour) and determine the new value of the drug's volume rate as the average of the administration volume rates (e.g., 105 ml / hour), and / or may cause the new value of the volume rate to be displayed via an editor of the drug system. In some embodiments, processor 202 may determine a new value only for predetermined care areas where the drug is administered outside the predetermined value of the administration parameter. For example, if a threshold number of drug administrations are performed in an ICU at a volume rate exceeding a predetermined volume rate value, processor 202 may calculate an average of the volume rates at which the drug is administered in that ICU and may determine the new value of the drug's volume rate in that ICU as the average of the administration volume rates in that ICU.

[0101] The processor 202 may transmit the determined new value to the user of the drug management system in a message indicating that the new value is a suggested update to a predetermined value. In some embodiments, the processor 202 may indicate in the message that the new value is for a predetermined care area. In some embodiments, the processor 202 may display the determined new value in an editor user interface for various drugs stored in a data storage system associated with the drug management system.

[0102] Now go to Figure 9 A flowchart is shown illustrating the process of evaluating and identifying one or more high-performing external clinician staffing resource centers. For a clearer example, refer to [link to relevant documentation]. Figure 1A The components and references of the network architecture 100 shown and described Figure 1B Components shown and described, references Figure 2 The components of the device management server 108 shown and described, and references Figure 3 , Figure 4 and Figure 5 The components of the medical device 104 shown and described can be used to describe the process of evaluating and identifying one or more high-performance external clinician personnel resource centers.

[0103] Method 900 includes identifying one or more clinicians associated with external clinician staffing resource centers by a processor 202 of device management server 108 (block 901). Device management server 108 may receive clinician information from a healthcare facility's clinician staffing system, and this clinician information may list external clinician staffing resource centers for clinicians on temporary assignment and / or traveling. Processor 202 may store clinicians (e.g., clinician identifiers) in association with their respective external clinician staffing resource centers in a data storage system associated with device management server 108. Processor 202 may identify clinicians based on their association with external clinician staffing resource centers.

[0104] Processor 202 determines a set of clinicians from one or more clinicians who meet a threshold performance score (box 902). As described above, processor 202 stores clinician performance scores associated with clinicians (e.g., clinician identifiers) in a data storage system. Processor 202 can identify the performance score of each of the one or more clinicians and determine whether the performance score meets a threshold performance score (e.g., the performance score is equal to or greater than a threshold performance score). The threshold performance score can be a predetermined performance score defined by a healthcare institution. If a clinician's performance score meets the threshold performance score, processor 202 can add that clinician to the set of clinicians.

[0105] Processor 202 identifies one or more external clinician staffing resource centers as high-performance clinician resource centers based on a set of clinicians (box 903). Processor 202 can identify one or more external clinician staffing resource centers for clinicians having a threshold number of clinicians in the determined set, and identify them as said one or more external clinician staffing resource centers. For example, the threshold number can be predetermined as 3, and processor 202 can group clinicians in the set based on their associated external clinician staffing resource centers, and identify external clinician staffing resource centers with at least 3 clinicians. In some embodiments, processor 202 can be configured to identify one or more clinicians with the highest performance scores and identify their associated external clinician staffing resource centers as high-performance external clinician staffing resource centers. In some embodiments, processor 202 can be configured to generate an evaluation result for each of the one or more external clinician staffing resource centers based on the number of clinicians with performance scores that meet the threshold performance score and are associated with the resource center.

[0106] Processor 202 may transmit a message to a healthcare organization's staffing system, thereby informing the healthcare organization's staffing system of the one or more high-performance external clinician staffing resource centers (block 904). In some embodiments, in response to transmitting the message to the staffing system, processor 202 may cause the staffing system to request clinicians from the one or more high-performance external clinician staffing resource centers.

[0107] Now go to Figure 10 A flowchart illustrating the process of validating and / or optimizing shift schedules for clinicians is shown. For a clearer example, refer to [link / reference]. Figure 1A The components and references of the network architecture 100 shown and described Figure 1BComponents shown and described, references Figure 2 The components of the device management server 108 shown and described, and references Figure 3 , Figure 4 and Figure 5 The components of the medical device 104 shown and described can be used to describe the process of optimizing clinician scheduling.

[0108] Method 1000 includes receiving shift schedules for clinicians at a healthcare facility by a processor 202 of a device management server 108 (block 1001). In some embodiments, clinician performance scores in the shift schedules may be received. The processor 202 determines whether the received shift schedules meet one or more scheduling criteria associated with the healthcare facility (block 1002). The device management server 108 may be configured to receive one or more scheduling criteria for the healthcare facility, and the processor 202 may store the received scheduling criteria in association with the healthcare facility. The processor 202 may be configured to validate and / or optimize the received shift schedules based on the scheduling criteria associated with the healthcare facility. In some embodiments, the scheduling criteria may describe the ratio of clinicians with not low performance scores to clinicians with low performance scores. For example, the scheduling criteria may indicate that for every two clinicians with low performance scores scheduled, three clinicians with not low performance scores should be scheduled.

[0109] In some embodiments, processor 202 can be configured to apply scheduling criteria based on shift times. For example, processor 202 can be configured to apply a scheduling criterion of two clinicians with good performance scores for every two clinicians with low performance scores scheduled for night shifts, and a scheduling criterion of four clinicians with good performance scores for every two clinicians with low performance scores scheduled for afternoon shifts. Processor 202 can identify the performance scores of clinicians included in the received shift schedule and, based on the clinicians' performance scores, determine whether the ratio of clinicians with good performance scores to clinicians with low performance scores included in the shift schedule meets the indicated ratio of the scheduling criterion. If the ratio is met, processor 202 can determine that the received shift schedule meets the scheduling criterion.

[0110] In some embodiments, a scheduling criterion indicates a threshold average performance score for a shift, based on the performance scores of clinicians scheduled to a shift. Processor 202 can calculate an average performance score based on the performance scores associated with clinicians included in the received shift schedule and can determine that such a scheduling criterion is met if the calculated average performance score meets the indicated threshold average performance score. Processor 202 can then determine that the received shift schedule meets such a scheduling criterion. In some embodiments, the scheduling criterion can indicate a threshold deviation between the performance scores of clinicians included in the shift schedule to achieve a uniform distribution of performance scores across different shifts in a healthcare facility. Processor 202 can be configured to determine whether a shift schedule meets the scheduling criterion based on whether the differences between the performance scores of clinicians included in the shift schedule meet a threshold deviation.

[0111] If processor 202 determines that the received shift schedule does not meet one or more scheduling criteria associated with the healthcare institution (No at box 1002), method 1000 proceeds to box 1003. Processor 202 adjusts the received shift schedule (box 1003). Processor 202 can be configured to adjust the received shift schedule by replacing one or more clinicians included in the shift schedule with one or more other clinicians who are not currently scheduled for that shift and / or are on shifts during the same time period as the shift associated with the received shift schedule. For example, processor 202 can adjust the received shift schedule and / or generate a new shift schedule based on the performance score of a second clinician who meets a specified threshold performance score by replacing a first clinician whose performance score does not meet the threshold performance score specified in the scheduling criteria of the received shift schedule with a second clinician who is not scheduled for the same time period as the shift in the received shift schedule. In some embodiments, processor 202 may electronically prevent the first clinician from using one or more medical devices during the shift period of the received shift schedule.

[0112] In some embodiments, processor 202 may be configured to swap one or more clinicians scheduled to different shifts. In some embodiments, processor 202 may swap one or more clinicians scheduled to shifts that have not yet started. Processor 202 may be configured to continue swapping one or more clinicians between different shifts until the schedule for each shift meets one or more scheduling criteria associated with the healthcare institution. Processor 202 may be configured to store one or more adjusted schedules in a data storage system associated with device management server 108. Processor 202 sends a message to the clinician scheduling system indicating one or more adjusted schedules (block 1004). Processor 202 may include instructions in the message to cause the clinician scheduling system to update the corresponding schedules in the adjusted schedules in the clinician scheduling system.

[0113] Returning to box 1002, if processor 202 determines that the received shift schedule meets one or more scheduling criteria associated with the healthcare institution ("Yes" at box 1002), method 1000 proceeds to box 1005. Processor 202 sends a message to the clinician scheduling system indicating that the shift schedule successfully meets one or more scheduling criteria associated with the healthcare institution (box 1005).

[0114] In some embodiments, processor 202 may be configured to display clinicians' schedules on a display device of medical device 104. For example, processor 202 may identify patients associated with each clinician and medical devices 104 associated with patients based on validated and / or optimized schedules. Processor 202 may transmit information related to clinicians' schedules (e.g., information related to when clinicians' shifts begin and end) to medical device 104 so that clinicians' shift schedules are displayed on a display device of medical device 104. In some embodiments, processor 202 may be configured to transmit validated and / or optimized schedules to be displayed on a display device associated with a clinician scheduling system.

[0115] Now go to Figure 11 A flowchart is shown illustrating the process of identifying workflows for clinicians with low performance scores and generating warnings and / or reminders for subsequent activities. For a clearer example, refer to [link to documentation]. Figure 1A The components and references of the network architecture 100 shown and described Figure 1B Components shown and described, references Figure 2 The components of the device management server 108 shown and described, and references Figure 3 , Figure 4 and Figure 5The components of the medical device 104 shown and described can be used to generate warnings and / or reminders for subsequent activities of clinicians with low performance scores.

[0116] Method 1100 includes receiving a clinician's identifier from a medical device by a processor 202 of a device management server 108 (block 1101). As described above, in some embodiments, the processor 202 may receive the clinician's identifier after consent has been given to the clinician to access the medical device. The processor 202 identifies a performance score associated with the clinician (block 1102). As described above, the clinician's performance score may be stored in association with the clinician (e.g., the clinician's identifier) ​​in a data storage system associated with the device management server 108, and the processor 202 identifies the performance score based on information associated with the clinician and / or the received clinician's identifier.

[0117] Processor 202 receives information related to one or more interactions between the clinician and the medical device (box 1103). Processor 202 determines whether the clinician's performance score meets a low performance score threshold (box 1104). If processor 202 determines that the clinician's performance score does not meet the low performance score threshold ("No" in box 1104), method 1100 terminates. If processor 202 determines that the clinician's performance score meets the low performance score threshold ("Yes" in box 1104), method 1100 proceeds to box 1105.

[0118] Processor 202 identifies one or more next steps for the clinician (box 1105). Processor 202 can be configured to identify one or more next steps for the clinician based on a stored set of rules that specifies one or more next steps in different workflows configured for the medical device. In some embodiments, processor 202 can be configured to identify the appropriate next step in a workflow based on the last completed step and / or the current step in the workflow. In some embodiments, processor 202 can identify the last completed step and / or the current step in the workflow based on received information related to one or more interactions between the clinician and the medical device. For example, if received information related to one or more interactions indicates that the last step completed by the clinician was the selection of a drug infusion, processor 202 can identify the next step as checking settings in the medical device based on one or more next steps specified by a stored set of rules for infusion workflows for the medical device.

[0119] Processor 202 causes one or more identified next steps to be displayed on a display device associated with the medical device (box 1106). In some embodiments, processor 202 may transmit to the medical device the identified one or more next steps and instructions to display the transmitted one or more next steps, causing the medical device to display the one or more next steps on a display device associated with the medical device. In some embodiments, the medical device may be configured to display graphical items (e.g., warning boxes, message boxes, etc.) associated with steps in a workflow configured by the medical device, and processor 202 may transmit messages and / or instructions indicating an identifier associated with the identified next step, causing the processor of the medical device (e.g., processor 302) to identify the next steps in the stored steps for the workflow and display them on a display device associated with the medical device using the associated graphical items.

[0120] Processor 202 determines one or more follow-up activities for the clinician (box 1107). Examples of follow-up activities include, but are not limited to, checking one or more settings and / or configuration data for the medical device, checking for operational errors of the medical device, checking for patient vital signs, etc. Processor 202 may determine one or more follow-up activities based on the identified next step. For example, if the identified next step is to provide input to start a drug infusion, processor 202 may determine a follow-up activity to confirm the operational status of the pump module connected to the medical device after a predetermined amount of time. In some embodiments, processor 202 may determine one or more follow-up activities based on information associated with one or more interactions between the clinician and the medical device. For example, if information associated with one or more interactions between the clinician and the medical device indicates that a patient associated with the medical device has been disconnected, processor 202 may determine a follow-up activity to confirm that the patient record in the EMR system accurately reflects the time when the clinician was disconnected from the medical device.

[0121] Processor 202 generates one or more warnings and / or alerts indicating one or more identified follow-up activities and transmits them to clinicians and / or other computing systems (block 1108) of a healthcare facility communicatively coupled to device management server 108. In some embodiments, processor 202 may be configured to transmit warnings and / or alerts for identified follow-up activities based on whether the identified follow-up activities involve performing one or more tasks in the computing system of the healthcare facility. If processor 202 determines that the follow-up activities involve performing one or more tasks in the computing system, processor 202 may transmit warnings and / or alerts to the computing system such that the warnings and / or alerts are displayed on a display device of the computing system. For example, if the follow-up activity involves updating patient records in the healthcare facility's EMR system, processor 202 may transmit warnings and / or alerts for the follow-up activities to the EMR and display the warnings and / or alerts in response to a clinician accessing the EMR. In some embodiments, processor 202 may transmit one or more warnings and / or alerts to a computing device associated with the clinician (e.g., the clinician's mobile device) to provide the clinician with the one or more warnings and / or alerts. In some embodiments, processor 202 may be configured to lock the clinician out of medical device 104 if the clinician does complete one or more tasks of a subsequent activity within a predetermined time threshold associated with the subsequent activity (e.g., within 3 hours).

[0122] Now go to Figure 12 A flowchart illustrating the process of determining compliance scores and generating training plans for clinicians is shown. For a clearer example, refer to Figure 1 for the components of the network architecture 100 shown and described, and refer to... Figure 2 The components of the device management server 108 shown and described, and references Figure 3 The components of the medical device 104 shown and described can be used to describe the process by which clinicians determine compliance scores and generate training plans.

[0123] Method 400 includes receiving information associated with a clinician's identifier at medical device 104 by a processor 202 of device management server 108 (block 401). In response to a clinician attempting to access medical device 104, processor 202 may receive information associated with the clinician's identifier. In some embodiments, a clinician may attempt to access medical device 104 by providing his or her access credentials (e.g., scanning his or her identification card at medical device 104). The clinician's access credentials may be associated with and / or include the clinician's unique identifier, and medical device 104 may be configured to transmit the unique identifier associated with the clinician to device management server 108 in response to receiving the clinician's access credentials and / or unique identifier. Examples of a clinician's unique identifier include, but are not limited to, user identifiers, employee identifiers, etc. In some embodiments, processor 202 may determine whether to grant access to medical device 104 to the clinician based on whether secondary authorization for the clinician is required.

[0124] Processor 202 receives information related to one or more interactions between a clinician and the medical device (box 402). Examples of information related to interactions between a clinician and the medical device 104 include, but are not limited to, administration of a certain drug to a patient, the volumetric rate of drug administration (e.g., administration at a rate of 5 ml per hour), simultaneous administration of two or more drugs, drug-drug interactions of the simultaneously administered drugs, the volume of drug administered, the dosage of the drug administered, the area of ​​care in which the clinician interacts with the medical device, the type of drug administered, the type of patient receiving the drug, the response time to one or more alarms generated by the medical device, the medical route of drug administration (e.g., intravenous, subcutaneous, intra-arterial, epidural, etc.), the type of kit used for the administration of fluids or drugs (e.g., tubing, syringe, or connector), the duration of use of the administration kit, the type of tubing and connector used during infusion, tubing replacement parameters (e.g., tubing replaced within 72 hours, 96 hours, etc.), and other similar information. Interactions may also be associated with sequences to determine which interactions occurred and the order or timing of these interactions.

[0125] Processor 202 generates a clinician's compliance score based on one or more interactions (box 403). Processor 202 can be configured to generate a compliance score based on whether an interaction conforms to one or more protocols. In some embodiments, processor 202 can determine whether an interaction is compliant based on a stored set of rules that instructs or specifies one or more corresponding compliant interactions. For example, the rule set can specify compliant volume rates for one or more medications. Similarly, the rule set can specify one or more of pressure rates, doses, volumes, setting types, etc. In some embodiments, the rule set can specify one or more compliance parameters for one or more medications, patient types, care areas within a healthcare facility, drug types, etc. The rule set can also specify a group or more groups of medications that can be administered simultaneously or sequentially. In some embodiments, the rule set can specify different compliant volume rates, pressure rates, dose rates, etc., for different types of patients (e.g., patients with heart disease, obese patients, patients with one or more allergies, etc.). The rule set can further specify different routes of administration by which medications can be administered. Examples of routes of administration include, but are not limited to, intravenous, epidural, subcutaneous, other parenteral routes, etc.

[0126] Processor 202 can compare information associated with one or more received interactions with corresponding compliant interactions specified by a set of rules to determine whether an interaction is compliant. For example, if a clinician is administering two medications concurrently, and the set of rules specifies one or more sets and / or groups of medications that can be administered concurrently, processor 202 can verify whether both medications are specified as part of a set or group of medications that can be administered concurrently. If processor 202 determines that neither medication is part of a set or group of medications that can be administered concurrently, processor 202 can determine that the clinician's interaction is non-compliant and generate and / or adjust (e.g., lower) the clinician's compliance score to reflect the non-compliant interaction. If processor 202 determines that both medications are part of a set or group of medications that can be administered concurrently, processor 202 can determine that the clinician's interaction is compliant and generate and / or adjust (e.g., increase) the clinician's compliance score to reflect the compliant interaction.

[0127] A compliance score can be determined by identifying rules applicable to interactions within a selected time period. In an interactive embodiment, the time period can be selected via a user interface. In an unattended embodiment (e.g., a periodic compliance reporting engine), the time period can be specified as a configuration parameter of the reporting engine. Processor 202 can obtain the object's interactions over a period of time. Processor 202 can then obtain applicable compliance rules from a set of compliance rules. This filtering can reduce the amount of resources required to generate a compliance score for the object. Once the applicable compliance rules are obtained, processor 202 can then evaluate the interaction by comparing the interaction to the applicable rules. The interaction record can include the interaction type. For example, the interaction type can be used as a key to identify the relevant compliance rule by matching an identifier of the interaction type with a value specified in or by the compliance rule. The interaction record can also include interaction data that identifies, for example, the amount of programming, the rate of programming, or other clinician behaviors used in the interaction. Each rule can contribute a value to the overall compliance score. Rules can be normalized to risk levels, whereby a first constraint is associated with safe or compliant behavior, and a second constraint is associated with unsafe or non-compliant behavior. This normalization allows each rule to contribute equally to the overall score.

[0128] Equation (1) provides an example expression for generating a comprehensive compliance score. Some implementations may include weighting factors to allow certain rules or interactions to contribute more or less to the compliance score. Weighting factors can be specified for all scores, or they can be adjusted for specific clinicians or groups of clinicians to emphasize or de-emphasize the performance of certain activities.

[0129] Equation 1

[0130]

[0131] Where n is the number of interactions;

[0132] x is the number of rules applicable to a given interaction (i);

[0133] ω is a weighting factor used for a given rule (r) or interaction (i); and

[0134] sr is a scoring function applied to a given rule (r) from the interaction (i) data.

[0135] In some embodiments, processor 202 may be configured to compare information related to one or more interactions of a clinician with interactions of other clinicians and determine whether one or more interactions of a clinician are compliant. For example, for a first clinician, if processor 202 receives information related to an interaction indicating that the first clinician administered medication at a certain pressure rate, processor 202 may compare whether the pressure rate at which the first clinician administered the medication is outside the range of pressure rates used by most other clinicians. If processor 202 determines that the pressure rate is outside the pressure rate range, processor 202 may determine that the first clinician's interaction is non-compliant. Similarly, if processor 202 determines that the pressure is not outside the pressure rate range, processor 202 may determine that the first clinician's interaction is compliant.

[0136] Processor 202 can be configured to adjust compliance scores by predetermined adjustment amounts. In some embodiments, processor 202 can be configured to determine the adjustment amount based on the frequency of non-compliance in clinician interactions over a predetermined time period. For example, if a clinician administers medication multiple times at an incorrect dose over a 30-day period, processor 202 can reduce the compliance score by a larger amount each time the clinician administers the medication at an incorrect dose. In some embodiments, each clinician can be associated with a default initial compliance score, and processor 202 can store the compliance score in association with the clinician's identifier. Processor 202 can update and / or maintain the compliance score throughout a clinician's career.

[0137] In some embodiments, processor 202 may group and / or classify clinician interactions into predetermined groups and / or categories based on a predetermined set of rules. For example, processor 202 may group and / or classify interactions related to administering a drug at a certain dose into a group and / or a class of interactions, interactions related to administering a drug at a certain volumetric rate into a second group and / or a second class of interactions, and interactions related to the simultaneous administration of multiple drugs into a third group and / or a third class of interactions. Processor 202 may generate and / or associate compliance scores for each group and / or each class of interactions. In some embodiments, processor 220 may generate an overall compliance score based on the compliance scores of interactions in one or more groups and / or categories.

[0138] Processor 202 determines whether the compliance score meets the training plan threshold compliance score (box 404). The training plan threshold compliance score can be a predetermined threshold compliance score. The threshold compliance score can be specified as a system-wide configurable value. In some embodiments, the configurable value can be specified via a user interface. In some embodiments, the threshold compliance score can be dynamically generated, such as for a specific clinician or group of clinicians. In some embodiments, processor 202 can be configured to determine that the compliance score meets the training plan threshold compliance score if the compliance score corresponds to the training plan threshold compliance score. In some embodiments, processor 202 can be configured to determine that the compliance score meets the training plan threshold compliance score if the compliance score is equal to or greater than the training plan threshold compliance score.

[0139] If processor 202 determines that the compliance score does not meet the threshold compliance score (e.g., the clinician is considered compliant), method 400 proceeds to box 401. If processor 202 determines that the compliance score meets the threshold compliance score (e.g., the clinician is considered non-compliant), method 400 proceeds to box 405. Processor 202 generates a training plan (box 405). Processor 202 may identify training modules associated with one or more interactions and / or categories of one or more interactions. For example, if one or more non-compliant interactions are associated with a category of administering a drug at a certain volume rate, processor 202 may identify training modules associated with that category. In some embodiments, one or more training modules may be associated with one or more training videos, and processor 202 may assemble one or more training videos into a software package and associate the software package with the training plan. In some embodiments, processor 202 may request and / or receive keystroke and / or touch input data from a medical device configured to receive keystroke and / or touch input, and processor 202 may associate the received keystroke and / or touch input data with training videos and / or the training plan. In some embodiments, the processor 202 may generate one or more videos based on keystroke and / or touch input data and provide them to clinicians for visual feedback on the clinicians’ interactions with the medical device.

[0140] Processor 202 can specify one or more training tasks in the training plan. These training tasks can specify instructions and / or tasks for clinicians to perform in order to complete the training plan. Training tasks can specify training materials for clinicians to review and / or tests to verify that clinicians have reviewed the training materials, training videos to review, etc. In some embodiments, processor 202 can determine whether a clinician has completed the training plan based on whether the clinician has completed the training tasks. Processor 202 can transmit the training plan to the clinician. In some embodiments, processor 202 can store the training plan associated with a clinician's identifier and transmit a message containing a link to the training plan to the clinician.

[0141] In some embodiments, processor 202 may associate a clinician with secondary authorizations from other clinicians whose compliance scores are higher than that clinician's. For example, processor 202 may identify clinicians whose compliance scores are equal to or higher than a specific threshold compliance score and associate one or more of the identified clinicians as secondary authorizations for those clinicians. By associating one or more other clinicians as secondary authorizations for the clinician, processor 202 causes the medical device to display a prompt when a clinician accesses the medical device, allowing the one or more other clinicians to log in or access the medical device.

[0142] Processor 202 can adjust one or more features available to a clinician at one or more medical devices based on a training plan (box 406). In response to determining consent for a clinician to access the medical device, processor 202 can cause the medical device to display additional prompts or messages to the clinician based on the generated training plan. For example, processor 202 can transmit a training video associated with the training plan to the medical device and cause the medical device to display the training video in response to consent for the clinician to access the medical device. Processor 202 can cause the medical device to display different training videos associated with the training plan at different steps of the interaction. For example, if the clinician is administering medication intravenously, processor 202 can instruct the medical device to display a first training video that instructs the user to verify whether the medication can be administered intravenously and provides the clinician with prompts to confirm that the medication can be administered intravenously. In response to receiving confirmation from the clinician, processor 202 can cause the medical device to display a second video that instructs the clinician to verify whether the dosage of the medication is appropriate for the specific patient.

[0143] In some embodiments, processor 202 disables certain features for clinicians at one or more medical devices based on a training plan. For example, processor 202 may disable features that allow experienced clinicians to skip several intermediate steps and cause clinicians associated with the training plan to perform additional steps (e.g., checking a marker and confirming that the marker has been checked), steps that clinicians with higher compliance scores may not need to perform. In some embodiments, processor 202 may lock a clinician out of one or more medical devices until processor 202 determines that the clinician has successfully completed the training plan. The medical device may include an idle time lockout value. Once a clinician accesses the medical device, if no interaction with the medical device is detected for a period of time, the clinician can be considered idle. This lack of activity can be logged as an interaction with the medical device and processed as described. The time period used to assess idleness can be dynamically adjusted. For example, clinicians with lower compliance scores may have a longer idle time than clinicians with higher compliance scores. This may encourage poorly performing clinicians to take their time when interacting with the medical device. For more capable clinicians, a lower threshold can improve the security of the medical device. The time period can be further generated based on the drug to be delivered, infusion type, administration kit, or other detectable attributes of drug delivery.

[0144] Processor 202 can monitor and / or track a training program to determine whether a clinician has completed one or more tasks of the training program. In some embodiments, in response to determining that one or more tasks of the training program have been completed, processor 202 can enable one or more features associated with the training tasks. In some embodiments, if a threshold number of training tasks have been completed, processor 202 can grant the clinician access to one or more medical devices.

[0145] Processor 202 can control additional or alternative aspects of the medical device based on a competence score. For example, the medical device can dynamically require secondary review of an activity based on the competence score of a clinician initiating the activity. For instance, if a controlled substance is to be delivered via the medical device and the clinician's competence score is below a threshold, the medical device can prevent the initiation of delivery until confirmed by a second clinician. In some embodiments, the medical device can be configured to receive confirmation from a first clinician or a second clinician whose competence score is above a threshold. This threshold can be associated with the medical device, the drug, the clinician's area of ​​care, or a standard competence threshold. Additional or alternative factors that can be used to configure the medical device for secondary review include the type of infusion, the number of channels for the programming module, the difference between the indicated and actual programming parameters (e.g., a greater deviation from the provided programming parameters may indicate a higher probability of clinician error), the type of application kit (e.g., some kits require specific initiation or may be prone to loading errors), and patient characteristics (e.g., the patient has specific medical conditions, needs, etc.).

[0146] In some embodiments, the medical device may be configured to require a specific clinician to review and approve interactions. For example, to enable a procedure entered by a primary nurse, confirmation from a head nurse may be required. As another example, confirmation from a specific physician may be required to enable a procedure for an experimental drug or treatment (e.g., as part of a clinical trial). Identification can be verified by receiving identification information of a secondary reviewer through an activation credential system. For example, the medical device may scan a badge associated with a secondary reviewer. The scan can provide an identifier for the secondary reviewer, which can then be used to verify identity, competency scores, or other factors to assess whether the individual is qualified to review the work of the initial clinician. The intent and outcome (e.g., consent, refusal) of a specific secondary reviewer may be stored as interactions and included in the processes described herein.

[0147] The compliance scores described so far are typically associated with clinicians. In some embodiments, compliance scores can be generated for devices. In some cases, the focus may be on the device rather than the clinician. In such embodiments, interactions with a specific device, device model or series, or device type can be identified and scored. Based on the compliance score, one or more control signals can be transmitted to devices identified as non-compliant. Control signals can adjust one or more features of the device, such as disabling login or adjusting power status (e.g., sleep mode or off). In some embodiments, control signals can adjust the user interface or other perceptible feedback elements to indicate that the device is malfunctioning. In some embodiments, control signals can be transmitted to a technician or other automated troubleshooting system to initiate device maintenance. Maintenance may include performing remote diagnostic procedures or system refreshes to identify or correct device defects.

[0148] Although some of the accompanying figures illustrate multiple logical stages in a particular order, stages that are not dependent on the order can be reordered, and other stages can be combined or decomposed. While some reorderings or other groupings are specifically mentioned, other orders or groupings will be apparent to those skilled in the art, and therefore the orders and groupings presented herein are not an exhaustive list of alternatives. Furthermore, it should be recognized that these stages can be implemented in hardware, firmware, software, or any combination thereof.

[0149] See Figure 1 for further details. Figure 12 The system of this subject matter can identify one or more interactions between a first user and one or more medical devices, and determine a compliance score associated with the first user based on the one or more interactions and a predetermined set of rules. In response to a compliance score that does not meet a threshold compliance score, the system can reduce the first user's access level to at least one of the one or more medical devices and generate a training program associated with the at least one medical device and the one or more interactions. In this regard, reducing the access level may include reducing a certain number of corresponding features of the at least one medical device available to the first user. The system is then configured to automatically compile and / or send a training package associated with the training program to the first user without user intervention, and notify the first user to complete the training program using the training package.

[0150] Then (at a later time), the system may receive a request from a first user to access the at least one medical device. For example, the first user may attempt to log in to the medical device (e.g., swipe his or her badge). The system may then, in response to the request, determine that the first user has not completed the training procedure and, before granting the first user permission to access the at least one medical device, require authorization from a second user authorized to use the at least one medical device. According to different embodiments, the training procedure may be generated based on categories associated with the one or more interactions and includes one or more training tasks associated with a certain number of corresponding features of the at least one medical device. In some embodiments, the system may determine that the first user has completed the training procedure including the one or more training tasks and, in response to determining that the first user has completed the training procedure, restore the first user's access level to the at least one medical device. In some embodiments, each of the one or more corresponding features of the medical device becomes available to the first user when the first user completes the corresponding training task associated with each feature.

[0151] Description of the subject technology in terms of items

[0152] For convenience, various examples of aspects of this disclosure are described with numbered items (1, 2, 3, etc.). These are provided by way of example and do not limit the subject matter. The identification and reference numerals in the accompanying drawings are provided below by way of example only and for illustrative purposes; these items are not limited by these identifications.

[0153] Item 1: A method comprising: tracking one or more interactions of a first user with one or more medical devices; determining a compliance score based on a stored set of rules and the one or more interactions; determining whether the compliance score meets the threshold compliance score; generating a training plan for the first user based on the one or more interactions in response to determining that the compliance score meets the threshold compliance score; and adjusting one or more features of the one or more medical devices available to the first user at the one or more medical devices based on the training plan.

[0154] Item 2: The method according to Item 1 further includes: receiving a request to access one of the one or more medical devices, wherein the request is associated with an identifier of the first user; determining whether to grant access to the medical device to the identifier of a second user among a plurality of users; and in response to determining that access to the medical device to the second user's identifier is granted, granting access to the medical device to the identifier of the first user.

[0155] Item 3: According to the method described in Item 2, wherein the identifier of the second user is associated with a secondary authorization of the identifier of the first user.

[0156] Item 4: According to the method of Item 3, determining whether to grant access to the medical device by the identifier of the second user further includes: in response to receiving an access request from the first user, providing a request to display credentials associated with the identifier of the second user on a display device associated with the medical device; receiving credentials associated with the identifier of the second user; and granting access to the medical device by the identifier of the second user.

[0157] Item 5: According to the method described in Item 3, wherein the compliance score of the second user is greater than the compliance score of the first user.

[0158] Item 6: The method according to Item 1, wherein generating the training plan for the first user based on the one or more interactions further comprises: determining a category associated with the one or more interactions based on the one or more interactions; identifying one or more training modules based on the categories; and generating the training plan based on the one or more training modules.

[0159] Item 7: The method according to Item 6, wherein the training plan includes one or more training tasks corresponding to the features of the one or more training modules and the one or more medical devices.

[0160] Item 8: The method according to Item 7 further includes: determining whether one of the training tasks in the training plan has been completed; and in response to determining that the training task has been completed, granting the first user access to the corresponding feature of the medical device.

[0161] Item 9: The method according to Item 1, wherein adjusting one or more features of one or more medical devices available to the first user at the one or more medical devices based on the training plan further comprises: providing training videos associated with the one or more features for display on a display device associated with one of the one or more medical devices.

[0162] Item 10: The method according to Item 1 further includes: locking the first user out of the one or more medical devices; receiving a request from the first user to access the one or more medical devices; in response to receiving the request, determining whether the first user has completed the training program; and in response to determining that the first user has completed the training program, granting permission for the first user to access the one or more medical devices.

[0163] Item 11: A system comprising: a memory storing instructions; and one or more processors coupled to the memory and configured to execute the instructions such that the system: tracks one or more interactions of a first user with one or more medical devices; determines a compliance score based on a stored set of rules and the one or more interactions; determines whether the compliance score meets a threshold compliance score; when the compliance score meets the threshold compliance score, generates a training plan for the first user based on the one or more interactions; and adjusts one or more features of the one or more medical devices available to the first user at the one or more medical devices based on the training plan.

[0164] Item 12: The system according to Item 11, wherein the one or more processors are configured to execute the instructions such that the system: receives a request to access one of the one or more medical devices, wherein the request is associated with an identifier of the first user; determines whether to grant access to the medical device to the identifier of a second user among a plurality of users; and, if access to the medical device to the second user is granted, grants access to the medical device to the identifier of the first user.

[0165] Item 13: The system according to Item 12, wherein the identifier of the second user is associated with a secondary authorization of the identifier of the first user.

[0166] Item 14: The system according to Item 13, wherein the one or more processors are configured to execute the instructions such that the system: upon receiving an access request from the first user, provides a request to display credentials associated with the identifier of the second user on a display device associated with the medical device; receives credentials associated with the identifier of the second user; and grants access to the medical device to the identifier of the second user.

[0167] Item 15: The system according to Item 13, wherein the compliance score of the second user is greater than the compliance score of the first user.

[0168] Item 16: The system according to Item 11, wherein the one or more processors are configured to execute the instructions such that the system: determines a category associated with the one or more interactions based on the one or more interactions; identifies one or more training modules based on the categories; and generates the training plan based on the one or more training modules.

[0169] Item 17: The system according to Item 16, wherein the training plan includes one or more training tasks corresponding to the features of the one or more training modules and the one or more medical devices.

[0170] Item 18: The system according to Item 17, wherein the one or more processors are configured to execute the instructions such that the system: determines whether a training task in one or more training tasks of the training plan has been completed; and when the training task has been completed, grants the first user access to the corresponding features of the medical device.

[0171] Item 19: The system according to Item 11, wherein the one or more processors are configured to execute the instructions such that the system: provides training videos associated with the one or more features for display on a display device associated with one of the one or more medical devices.

[0172] Item 20: The system according to Item 11, wherein the one or more processors are configured to execute the instructions such that the system: locks the first user out of the one or more medical devices; receives a request from the first user to access the one or more medical devices; when the request is received, determines whether the first user has completed the training program; and when the first user has completed the training program, grants the first user access to the one or more medical devices.

[0173] Item 21: A method comprising: identifying interactions of a plurality of clinicians with one or more medical devices; generating a performance score for each of the plurality of clinicians based on a stored set of rules and one or more interactions of each user among the plurality of clinicians; receiving a first shift schedule associated with the plurality of clinicians; determining whether the first shift schedule meets one or more scheduling criteria associated with a healthcare institution; in response to determining that the first shift schedule does not meet the one or more scheduling criteria and a first performance score of a first clinician does not meet a first assessment threshold of the one or more scheduling criteria: (1) generating a new second shift schedule for the plurality of clinicians, the new second shift schedule being based on a second performance score of a second clinician, replacing a first clinician scheduled in a first time period with a second clinician who is not currently scheduled in that time period, and (2) electronically preventing the first clinician from using at least one of the one or more medical devices in the first time period; and causing the new shift schedule to be displayed on a display device associated with a clinician scheduling system.

[0174] Item 22: The method according to Item 21 further includes: identifying one or more high-performance resource centers based on the performance scores of a subset of the plurality of clinicians; generating a request from the one or more high-performance resource centers to not be among one or more of the plurality of clinicians; and transmitting the request to a clinician scheduling system.

[0175] Item 23: The method according to Item 21 further includes: determining a subset of the plurality of clinicians whose performance scores meet a threshold low performance score; receiving information related to the interaction between the clinicians of the subset and the medical device; identifying a workflow initiated at the medical device based on the information; identifying the next step in the workflow based on the workflow and a stored set of rules; and causing the next step to be displayed on a display device associated with the medical device.

[0176] Item 24: The method according to Item 23 further includes: determining one or more follow-up activities of a clinician based on information related to the one or more interactions; generating a warning for the one or more follow-up activities; and transmitting the warning for the one or more follow-up activities to a computing device associated with the clinician.

[0177] Item 25: The method according to Item 24 further includes: determining, based on the one or more subsequent activities, whether it is necessary to update the patient's electronic record at the healthcare institution's management system; and in response to determining that the electronic record needs to be updated, causing the warning to be displayed adjacent to the electronic record on a display device associated with the management system.

[0178] Item 26: The method according to Item 21 further includes: receiving information related to a set of interactions between one of the plurality of clinicians and the medical device; identifying a predetermined care area of ​​the medical device based on location information of the medical device; determining a parameter value associated with a drug administered to a patient based on the information; updating a drug counter associated with the predetermined care area in response to determining that the parameter value is outside a predetermined threshold, wherein the drug counter indicates the number of times the drug is administered using the parameter value outside the predetermined threshold; determining whether the drug counter meets a second threshold; and displaying a warning identifying the drug and the predetermined care area on a display device of the drug management system in response to determining that the drug counter meets the second threshold.

[0179] Item 27: The method according to Item 26 further includes: in response to determining that the counter meets the threshold, calculating a new value for the parameter based at least on the value of the drug parameter of the administered drug; and sending a warning to the user of the drug management system to update the current value of the parameter to the new value of the parameter.

[0180] Item 28: The method according to Item 26 further includes: in response to determining that the drug counter does not meet the second threshold, reducing the clinician's performance score by a predetermined amount; determining whether the reduced performance score meets the predetermined threshold low performance score; and in response to determining that the reduced performance score meets the predetermined threshold low performance score, updating the permissions associated with the clinician to electronically prevent the clinician from using the one or more medical devices.

[0181] Item 29: The method according to Item 26 further includes: in response to determining that the reduced performance score meets a predetermined threshold low performance score, assigning a training package to a clinician; determining whether the training package has been successfully completed; and in response to determining that the training package has been successfully completed, electronically consenting to the clinician's use of the one or more medical devices.

[0182] Item 30: The method according to Item 26 further includes: assigning a mentor clinician to a clinician in response to determining that the reduced performance score meets a predetermined threshold low performance score; and electronically preventing the clinician from using one of the one or more medical devices until receiving clinician identification information associated with the mentor clinician.

[0183] Item 31: A system comprising: a memory storing instructions; and one or more processors coupled to the memory and configured to execute the instructions such that the system: identifies interactions between a plurality of clinicians and one or more medical devices; generates a performance score for each of the plurality of clinicians based on a stored set of rules and one or more interactions of each user among the plurality of clinicians; receives a first shift schedule associated with the plurality of clinicians; determines whether the first shift schedule meets one or more scheduling criteria associated with a healthcare institution; when the first shift schedule does not meet the one or more scheduling criteria and a first performance score of a first clinician does not meet a first assessment threshold of the one or more scheduling criteria: (1) generates a new second shift schedule for the plurality of clinicians, the new second shift schedule being based on a second performance score of a second clinician, replacing a first clinician scheduled in a first time period with a second clinician who is not currently scheduled in that time period, and (2) electronically prevents the first clinician from using at least one of the one or more medical devices in the first time period; and displays the new shift schedule on a display device associated with a clinician scheduling system.

[0184] Item 32: The system according to Item 31, wherein the one or more processors are configured to execute the instructions such that the system: identifies one or more high-performance resource centers based on the performance scores of a subset of the plurality of clinicians; generates a request from the one or more high-performance resource centers requesting that the clinicians not be among the plurality of clinicians; and transmits the request to a clinician scheduling system.

[0185] Item 33: The system according to Item 31, wherein the one or more processors are configured to execute the instructions such that the system: determines a subset of the plurality of clinicians whose performance scores meet a threshold low performance score; receives information relating to the interaction of the subset of clinicians with a medical device; identifies a workflow initiated at the medical device based on the information; identifies the next step in the workflow based on the workflow and a stored set of rules; and causes the next step to be displayed on a display device associated with the medical device.

[0186] Item 34: The system according to Item 33, wherein the one or more processors are configured to execute the instructions such that the system: determines one or more subsequent activities of a clinician based on information related to the one or more interactions; generates a warning for the one or more subsequent activities; and transmits the warning for the one or more subsequent activities to a computing device associated with the clinician.

[0187] Item 35: The system according to Item 34, wherein the one or more processors are configured to execute the instructions such that the system: determines, based on the one or more subsequent activities, whether an update of the patient's electronic record at the management system of a healthcare institution is required; and when an update of the electronic record is required, causes the warning to be displayed adjacent to the electronic record on a display device associated with the management system.

[0188] Item 36: The system according to Item 31, wherein the one or more processors are configured to execute the instructions such that the system: receives information related to a set of interactions between one of the plurality of clinicians and a medical device; identifies a predetermined care area of ​​the medical device based on location information of the medical device; determines, based on the information, a parameter value associated with a drug administered to a patient; updates a drug counter associated with the predetermined care area when the parameter value is outside a predetermined threshold, wherein the drug counter indicates the number of times the drug is administered using the parameter value outside the predetermined threshold; determines whether the drug counter meets a second threshold; and when the drug counter meets the second threshold, causes a warning identifying the drug and the predetermined care area to be displayed on a display device of the drug management system.

[0189] Item 37: The system according to Item 36, wherein the one or more processors are configured to execute the instructions such that the system: when the counter meets the threshold, calculates a new value for the parameter based at least on the value of the drug parameter for which the drug is administered; and sends a warning to the user of the drug management system to update the current value of the parameter to the new value of the parameter.

[0190] Item 38: The system according to Item 36, wherein the one or more processors are configured to execute the instructions such that the system: reduces the clinician's performance score by a predetermined amount when the drug counter does not meet the second threshold; determines whether the reduced performance score meets a predetermined threshold low performance score; and updates the permissions associated with the clinician when the reduced performance score meets the predetermined threshold low performance score, thereby electronically preventing the clinician from using the one or more medical devices.

[0191] Item 39: The system according to Item 36, wherein the one or more processors are configured to execute the instructions such that the system: assigns a training package to a clinician when the reduced performance score meets the predetermined threshold low performance score; determines whether the training package has been successfully completed; and electronically consents to the clinician's use of the one or more medical devices when the training package has been successfully completed.

[0192] Item 40: The system according to Item 36, wherein the one or more processors are configured to execute the instructions such that the system: determines that the reduced performance score meets the predetermined threshold low performance score, thereby assigning a mentor clinician to the clinician; and electronically prevents the clinician from using one of the one or more medical devices until receiving clinician identification information associated with the mentor clinician.

[0193] Item 41: A method comprising: identifying one or more interactions of a first user with one or more medical devices; determining a compliance score associated with the first user based on the one or more interactions and a predetermined set of rules; in response to the compliance score not meeting a threshold compliance score, reducing the first user's access level to at least one of the one or more medical devices, and generating a training program associated with the at least one medical device and the one or more interactions, wherein reducing the access level includes reducing a certain number of corresponding features of the at least one medical device available to the first user; and automatically sending a training package associated with the training program to the first user without user participation, and notifying the first user to complete the training program using the training package.

[0194] Item 42: The method according to Item 41 further includes: receiving a request from the first user to access the at least one medical device; in response to the request, determining that the first user has not completed the training program: requesting authorization from a second user authorized to use the at least one medical device before granting the first user's request to access the at least one medical device.

[0195] Item 43: The method according to Item 41, wherein the training program is generated based on categories associated with the one or more interactions and includes one or more training tasks associated with the number of corresponding features of the at least one medical device, and wherein the method further includes: determining that the first user has completed the training program including the one or more training tasks; and in response to determining that the first user has completed the training program, restoring the first user's access level with respect to the at least one medical device.

[0196] Item 44: The method according to Item 3, wherein each of one or more corresponding features of the medical device becomes available to the first user when the first user completes the corresponding training task associated with each feature.

[0197] Item 45: A system comprising: a memory storing instructions; and one or more processors configured to execute instructions such that the system implements any of the methods described in items 41-44.

[0198] Item 46: A non-transitory computer-readable medium storing instructions that, when executed by one or more computing devices, cause the one or more computing devices to perform one or more operations including any of the method steps described in items 41-44.

[0199] Further consideration

[0200] In some embodiments, any item herein may depend on any independent item or any dependent item. In one aspect, any item (e.g., dependent or independent item) may be combined with any other one or more items (e.g., dependent or independent items). In one aspect, a claim may include some or all of the words (e.g., step, operation, device, or component) stated in an item, sentence, phrase, or paragraph. In one aspect, a claim may include some or all of the words stated in one or more items, sentences, phrases, or paragraphs. In one aspect, some words in each item, sentence, phrase, or paragraph may be deleted. In one aspect, additional words or elements may be added to an item, sentence, phrase, or paragraph. In one aspect, the subject matter technique may be implemented without utilizing some of the components, elements, functions, or operations described herein. In one aspect, the subject matter technique may be implemented using additional components, elements, functions, or operations.

[0201] The preceding description is provided to enable any person skilled in the art to practice the various aspects described herein. The preceding description provides various examples of the subject matter, and the subject matter is not limited to these examples. Various modifications to these aspects will be apparent to those skilled in the art, and the general principles defined herein can be applied to other aspects. Therefore, the claims are not intended to be limited to the aspects shown herein, but are given the full scope consistent with the language of the claims, wherein, unless specifically stated otherwise, reference to elements in the singular form is not intended to mean “one and only one,” but rather “one or more.” Unless otherwise specifically stated otherwise, the term “some” refers to one or more. Masculine pronouns (e.g., his) include feminine and neuter pronouns (e.g., her and its), and vice versa. Titles and subtitles, if any, are used only for convenience and do not limit the disclosure.

[0202] While this specification discusses certain features of using a modular infusion pump as an example medical device, adaptive control features can be implemented using different medical devices, such as stand-alone infusion pumps, syringe pumps, drug preparation workstations, or automated drug dispensing cabinets. The predicate terms “configured as,” “operable as,” and “programmed as” do not imply any specific tangible or intangible modification to the subject, but are intended to be used interchangeably. For example, a processor configured to monitor and control operations or components can also mean that the processor is programmed to monitor and control operations, or is operable to monitor and control operations. Similarly, a processor configured to execute code can be interpreted as a processor programmed to execute code or operable to execute code.

[0203] As used herein, the term "automatic" can include actions performed by a computer or machine without user intervention; for example, instructions issued by a computer, machine, or other initiating mechanism in response to a predicate action. The word "example" is used herein to mean "serving as an example or illustration." Any aspect or design described herein as an "example" is not necessarily to be construed as preferred or advantageous over other aspects or designs.

[0204] For example, phrases such as "aspect" do not imply that such an aspect is necessary for the subject matter art, or that such an aspect can be applied to all configurations of the subject matter art. Disclosure related to an aspect may apply to all configurations, or one or more configurations. An aspect may provide one or more examples. For example, phrases such as "aspect" may refer to one or more aspects, and vice versa. For example, phrases such as "embodiment" do not imply that such an embodiment is necessary for the subject matter art, or that such an embodiment can be applied to all configurations of the subject matter art. Disclosure related to an embodiment may apply to all embodiments, or one or more embodiments. An embodiment may provide one or more examples. For example, phrases such as "embodiment" may refer to one or more embodiments, and vice versa. For example, phrases such as "configuration" do not imply that such a configuration is necessary for the subject matter art, or that such a configuration is applicable to all configurations of the subject matter art. Disclosure related to a configuration may apply to all configurations, or one or more configurations. A configuration may provide one or more examples. For example, phrases such as "configuration" may refer to one or more configurations, and vice versa.

[0205] As used herein, the term "determine" or "determining" encompasses a wide variety of actions. For example, "determining" can include calculating, processing, deriving, generating, obtaining, searching (e.g., looking in a table, database, or other data structure), identifying, etc., via hardware components without user intervention. Furthermore, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in memory), etc., via hardware components without user intervention. "Determining" can also include parsing, selecting, choosing, building, etc., via hardware components without user intervention.

[0206] As used herein, the term "provide" or "providing" encompasses a wide variety of actions. For example, "providing" can include storing a value in a location on a storage device for later retrieval, directly transmitting a value to a recipient via at least one wired or wireless communication medium, transmitting or storing a reference to a value, etc. "Providing" can also include encoding, decoding, encrypting, decrypting, authenticating, verifying, etc., via hardware components.

[0207] As used herein, the term "message" encompasses a wide variety of formats used to convey (e.g., transmit or receive) information. A message can include a collection of machine-readable information, such as an XML document, a fixed-field message, a comma-separated message, etc. In some embodiments, a message can include signals for conveying one or more representations of information. Although stated in the singular, it should be understood that a message can be composed, transmitted, stored, received, etc., in multiple parts.

[0208] As used herein, the terms "selectively" or "selectively" cover a wide variety of actions. For example, a "selective" process may include determining an option from a plurality of options. A "selective" process may include one or more of the following: dynamically determined input, pre-configured input, or user-initiated input for making the determination. In some embodiments, n input switches may be included to provide selective functionality, where n is the number of inputs used for making a selection.

[0209] As used herein, the term "correspondence" or "relative" encompasses a structural, functional, quantitative, and / or qualitative association or relationship between two or more objects, data sets, information, and / or the like, preferably wherein the responsiveness or relationship can be used to transform one or more of the two or more objects, data sets, information, and / or the like to appear identical or equivalent. Responsibility can be evaluated using one or more of the following: thresholds, value ranges, fuzzy logic, pattern matching, machine learning evaluation models, or combinations thereof.

[0210] In any embodiment, the generated or detected data may be forwarded to a “remote” device or location, where “remote” means a location or device other than the location or device executing the program. For example, a remote location could be another location in the same city (e.g., an office, laboratory, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Therefore, when an item is described as “far from” another item, it means that the two items may be in the same room but separate, or at least in different rooms or different buildings, and may be at least one mile, ten miles, or at least one hundred miles apart. “Communication” information refers to the transmission of data representing that information as an electrical signal through a suitable communication channel (e.g., a private or public network). “Forwarding” an item refers to any means of transferring the item from one location to another, whether by physically transporting the item or by other means (where possible), and at least in the case of data, includes physically transporting the medium carrying the data or transmitting the data. Examples of communication media include radio or infrared transmission channels and network connections to another computer or networked device, as well as the Internet or including the transmission of information recorded on websites and emails, etc.

[0211] All structural and functional equivalents of elements throughout the various aspects described herein, known or to be known by one of ordinary skill in the art, are expressly incorporated herein by reference and are intended to be covered by the claims. Furthermore, nothing disclosed herein is intended to be contributed to the public, whether or not such disclosure is expressly stated in the claims. No claim element should be construed pursuant to paragraph 6 of 35 USC § 112 unless the element is expressly stated using the phrase “means for…” or, in the case of a method claim, using the phrase “steps for…”. Furthermore, with regard to the terms “comprising,” “having,” or similar terms used in the specification or claims, such terms are intended to be inclusive in a manner similar to how the term “comprising” is interpreted when “comprising” is used as a transitional word in a claim.

Claims

1. A method executed by a central computing system, comprising: Identify interactions between a first user and multiple medical devices in a healthcare facility, one of which includes a response time to one or more alarms generated by a corresponding medical device connected to the patient, the multiple medical devices including infusion devices, syringe pumps, drug preparation workstations, or automated drug dispensing cabinets; Based on the identified interactions between the first user and the plurality of medical devices, and based on a predetermined set of rules, a compliance score associated with the first user's interactions is determined; In response to the compliance score not meeting the threshold compliance score, the central computing system will then process the following: Sending instructions to at least one of the plurality of medical devices to reduce the first user's access level to the at least one medical device by denying access to a certain number of corresponding features of the at least one medical device that the first user can use, including by: requesting one or more subsequent steps related to the process on a display device associated with the medical device while the first user is performing a process using the medical device; increasing the idle time of the at least one medical device before it becomes locked; requesting a second user to provide identification information before the first user is granted access to the medical device; or preventing the first user from interfering with or initiating drug infusion by a pump module connected to the medical device; and The system automatically compiles a training program associated with the at least one medical device without user intervention, sends a training package associated with the training program to the first user, and notifies the first user to complete the training program using the training package. as well as In response to the first user completing the training procedure, the first user's access level with respect to the at least one medical device is restored.

2. The method according to claim 1, further comprising: Receive a request from the first user to access the at least one medical device; In response to the request, it is determined that the first user has not yet completed the training process; Before granting the first user's request to access the at least one medical device, authorization from a second user who is authorized to use the at least one medical device is required.

3. The method according to claim 1, wherein, The training program is generated based on categories associated with the interaction and includes one or more training tasks associated with a certain number of corresponding features of the at least one medical device, wherein the method further includes: It is determined that the first user has completed the training program, including the one or more training tasks.

4. The method according to claim 3, wherein, When the first user completes the corresponding training task associated with each feature, the first user is able to use each of the one or more corresponding features of the medical device.

5. The method of claim 1, further comprising: Based on medical device interactions performed by multiple users with respect to one or more medical devices, a performance score is assigned to each of the multiple users. Receive the first shift schedule associated with the multiple users; Determine whether the first shift schedule meets one or more scheduling criteria associated with the healthcare facility; In response to determining that the first shift schedule does not meet the one or more scheduling criteria, and that the first user's first performance score does not meet the first evaluation threshold of the one or more scheduling criteria: (1) generating a new second shift schedule for the multiple users, the second shift schedule being based on the second user's second performance score, replacing the first user scheduled in the first time period with a second user who is not currently scheduled in the first time period, and (2) electronically preventing the first user from using at least one of the one or more medical devices in the first time period; as well as This allows the new shift schedule to be displayed on the display device associated with the user's scheduling system.

6. The method of claim 5, further comprising: Based on the performance scores of a subset of the multiple users, identify one or more high-performance resource centers; Generate requests from one or more high-performance resource centers that are not among one or more of the multiple users; as well as The request is sent to the user scheduling system.

7. The method of claim 5, further comprising: A subset of the plurality of users is identified whose performance scores meet the threshold of low performance scores. Receive information related to the interaction between a user and a medical device of the subset; Based on the information, identify the workflow initiated at the medical device; Based on the workflow and the stored set of rules, identify the next step in the workflow; as well as This causes the next step to be displayed on a display device associated with the medical device.

8. The method of claim 7, further comprising: Based on information related to the interaction, determine one or more follow-up activities for the user; Generate a warning for the one or more subsequent activities; Warnings for the one or more subsequent activities are sent to the computing device associated with the user; Based on one or more of the subsequent activities, determine whether it is necessary to update the patient's electronic records at the healthcare facility's management system. as well as In response to determining that the electronic record needs to be updated, the warning is displayed on a display device associated with the management system adjacent to the electronic record.

9. The method of claim 5, further comprising: Receive information related to the set of interactions between one of the plurality of users and the medical device; Based on the location information of the medical device, identify the predetermined care area of ​​the medical device; Based on the information, determine the parameter values ​​associated with the medication administered to the patient; In response to determining that the parameter value is outside a predetermined threshold, the medication counter associated with the predetermined care area is updated, wherein the medication counter indicates the number of times the medication is administered using a parameter value outside the predetermined threshold; Determine whether the drug counter meets the second threshold; as well as In response to determining that the drug counter meets the second threshold, a warning identifying the drug and the predetermined care area is displayed on the display device of the drug management system.

10. The method of claim 9, further comprising: In response to determining that the counter meets the threshold, a new value for the parameter is calculated, based at least on the value of the drug parameter for which the drug is administered; as well as A warning is sent to the user of the drug management system to update the current value of the parameter to the new value for the parameter.

11. The method of claim 9, further comprising: In response to determining that the drug counter does not meet the second threshold, the user's performance score is reduced by a predetermined amount; Determine whether the reduced performance score meets the predetermined threshold for a low performance score; as well as In response to determining that the reduced performance score meets the predetermined threshold low performance score, the permissions associated with the user are updated, thereby electronically preventing the user from using the one or more medical devices.

12. The method of claim 9, further comprising: In response to determining that the reduced performance score meets the predetermined threshold low performance score, a mentor user is assigned to the user. as well as Electronically prevent the user from using the at least one medical device until user identification information associated with the mentor user is received.

13. A system comprising: Memory that stores instructions; as well as One or more processors are configured to execute the instructions such that the system: Identify interactions between a first user and multiple medical devices in a healthcare facility, one of which includes a response time to one or more alarms generated by a corresponding medical device connected to the patient, the multiple medical devices including infusion devices, syringe pumps, drug preparation workstations, or automated drug dispensing cabinets; Based on the identified interactions between the first user and the plurality of medical devices, and based on a predetermined set of rules, a compliance score associated with the interactions of the first user is determined; In response to the compliance score not meeting the threshold compliance score: Sending instructions to at least one of the plurality of medical devices to reduce the first user's access level to the at least one medical device by denying access to a certain number of corresponding features of the at least one medical device that the first user can use, including by: requesting one or more subsequent steps related to the process on a display device associated with the medical device while the first user is performing a process using the medical device; increasing the idle time of the at least one medical device before it becomes locked; requesting a second user to provide identification information before the first user is granted access to the medical device; or preventing the first user from interfering with or initiating drug infusion by a pump module connected to the medical device; and The system automatically compiles a training program associated with the at least one medical device without user intervention, sends a training package associated with the training program to the first user, and notifies the first user to complete the training program using the training package. as well as In response to the first user completing the training procedure, the first user's access level with respect to the at least one medical device is restored.

14. The system according to claim 13, wherein, The one or more processors are configured to execute the instructions to further cause the system to: Receive a request from the first user to access the at least one medical device; In response to the request, it is determined that the first user has not yet completed the training process; Before granting the first user's request to access the at least one medical device, authorization from a second user who is authorized to use the at least one medical device is required.

15. The system according to claim 13, wherein, The one or more processors are configured to execute the instructions such that the system: It is determined that the first user has completed the training program.

16. The system according to claim 15, wherein, The training program is generated based on categories associated with the interaction and includes one or more training tasks associated with a certain number of corresponding features of the at least one medical device, wherein when the first user completes the corresponding training task associated with each feature, the first user is able to use each of the one or more corresponding features of the medical device.

17. The system according to claim 13, wherein, The one or more processors are configured to execute the instructions to further cause the system to: Based on medical device interactions performed by multiple users with respect to one or more medical devices, a performance score is assigned to each of the multiple users. Receive the first shift schedule associated with the multiple users; Determine whether the first shift schedule meets one or more scheduling criteria associated with the healthcare facility; In response to determining that the first shift schedule does not meet the one or more scheduling criteria, and that the first user's first performance score does not meet the first evaluation threshold of the one or more scheduling criteria: (1) generating a new second shift schedule for the multiple users, the second shift schedule being based on the second user's second performance score, replacing the first user scheduled in the first time period with a second user who is not currently scheduled in the first time period, and (2) electronically preventing the first user from using at least one of the one or more medical devices in the first time period; as well as This allows the new shift schedule to be displayed on the display device associated with the user's scheduling system.

18. The system according to claim 17, wherein, The one or more processors are configured to execute the instructions to further cause the system to: A subset of the plurality of users is identified whose performance scores meet the threshold of low performance scores. Receive information related to the interaction between the subset of users and the medical device; Based on the information, identify the workflow initiated at the medical device; Based on the workflow and the stored set of rules, identify the next step in the workflow; as well as This causes the next step to be displayed on a display device associated with the medical device.

19. The system according to claim 18, wherein, The one or more processors are configured to execute the instructions to further cause the system to: Based on information related to the interaction, determine one or more subsequent activities for the user; and Generate a warning for the one or more subsequent activities; Warnings for the one or more subsequent activities are sent to the computing device associated with the user; Based on one or more of the subsequent activities, determine whether it is necessary to update the patient's electronic records at the healthcare facility's management system. as well as In response to determining that the electronic record needs to be updated, the warning is displayed on a display device associated with the management system adjacent to the electronic record.

20. The system according to claim 17, wherein, The one or more processors are configured to execute the instructions to further cause the system to: Based on the location information of the medical device, identify the predetermined care area of ​​the medical device; Based on the information, determine the parameter values ​​associated with the medication administered to the patient; In response to determining that the parameter value is outside a predetermined threshold, the medication counter associated with the predetermined care area is updated, wherein the medication counter indicates the number of times the medication is administered using a parameter value outside the predetermined threshold; Determine whether the drug counter meets the second threshold; as well as In response to determining that the drug counter meets the second threshold, a warning identifying the drug and the predetermined care area is displayed on the display device of the drug management system.

21. The system according to claim 20, wherein, The one or more processors are configured to execute the instructions to further cause the system to: In response to determining that the drug counter does not meet the second threshold, the user's performance score is reduced by a predetermined amount; In response to the determination that the reduced performance score meets a predetermined low performance score threshold, a mentor user is assigned to the user. as well as Electronically prevent the user from using the at least one medical device until user identification information associated with the mentor user is received.

22. A non-transitory computer-readable medium storing instructions that, when executed by one or more computing devices, cause the one or more computing devices to perform one or more operations, comprising: Identify interactions between a first user and multiple medical devices in a healthcare facility, one of which includes a response time to one or more alarms generated by a corresponding medical device connected to the patient, the multiple medical devices including infusion devices, syringe pumps, drug preparation workstations, or automated drug dispensing cabinets; Based on the identified interactions between the first user and the plurality of medical devices, and based on a predetermined set of rules, a compliance score associated with the interactions of the first user is determined; In response to the compliance score not meeting the threshold compliance score: Sending instructions to at least one of the plurality of medical devices to reduce the first user's access level to the at least one medical device by denying access to a certain number of corresponding features of the at least one medical device that the first user can use, including by: requesting one or more subsequent steps related to the process on a display device associated with the medical device while the first user is performing a process using the medical device; increasing the idle time of the at least one medical device before it becomes locked; requesting a second user to provide identification information before the first user is granted access to the medical device; or preventing the first user from interfering with or initiating drug infusion by a pump module connected to the medical device; and The system automatically compiles a training program associated with the at least one medical device without user intervention, sends a training package associated with the training program to the first user, and notifies the first user to complete the training program using the training package. as well as In response to the first user completing the training procedure, the first user's access level with respect to the at least one medical device is restored.

Images