Adaptive control of a medical device based on clinician interaction

Abstract

The system and method identify interactions between a user and one or more medical devices, determine a compliance score associated with the first user based on the one or more interactions and a predetermined set of rules, reduce the user's access level to at least one of the one or more medical devices in response to the compliance score not meeting a threshold compliance score, generate a training program associated with the at least one medical device and the one or more interactions, automatically and without user involvement, transmit a training package associated with the training program to the user, and notify the user to complete the training program using the training package. The system and method also generate a new shift schedule for the clinician in response to the first shift schedule not meeting the criteria and the clinician not meeting a respective performance score.

Description

Technical Field

[0001] This application claims the benefit of priority as a non-provisional application of U.S. Application No. 62 / 897,199, filed on September 6, 2019, entitled "ADAPTIVE CONTROL OF MEDICAL DEVICES BASED ON CLINICIAN INTERACTIONS", and also claims the benefit of priority as a non-provisional application of U.S. Application No. 62 / 865,906, filed on June 24, 2019, entitled "SYSTEMS AND METHODS FOR IDENTIFYING NON-COMPLIANCE PATTERNS OF INTERACTIONS WITH A MEDICAL DEVICE", the entire contents of each of which are hereby incorporated by reference in their entirety.

[0002] This application generally relates to the control of medical devices based on clinician assessments and interactions between medical devices and individual clinicians in a medical institution.

Background Art

[0003] Medical devices such as infusion devices provide various conveniences and simplify the administration of medications to patients by clinicians such as nurses in healthcare facilities. Healthcare facilities and manufacturers of medical devices may establish various protocols and / or safeguards to ensure that fluids or medications are administered safely and consistently by clinicians with different levels of experience and training. However, due to different levels of experience and training, some clinicians may deviate from the protocols of the healthcare facility in their actions, threatening the safety of patients and the operation of the healthcare facility. Furthermore, healthcare institutions utilize various systems from various vendors and clinicians with varying levels of proficiency in those systems to assist in the treatment of patients. Thus, one concern is for healthcare institutions to identify and reduce operational risks for the healthcare institution while improving operational efficiency. However, existing healthcare systems do not adequately identify one or more clinicians with low proficiency in the systems being utilized, thus increasing the risk of patient injury and / or decreasing the operational efficiency of the healthcare institution.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Means for Solving the Problems

[0005] The various interactions of clinicians with different medical devices and systems can increase the operational risks for healthcare institutions. For example, a clinician may not follow one or more protocols when administering medications to a patient. Existing systems are not appropriately configured to track and monitor the interactions of non-compliant clinicians across multiple medical devices. Healthcare institutions also face operational risks from temporary or traveling clinicians who have varying levels of training and expertise in using different medical devices and systems of the healthcare institution. Existing systems also cannot efficiently identify a source center with well-trained temporary clinicians who meet best practice and / or protocol standards, or automatically assist such clinicians to successfully complete tasks in a way that reduces operational risks. Furthermore, existing systems and methods do not allow a healthcare institution to efficiently specify scheduling criteria and schedule clinicians for shifts in the healthcare institution based on the scheduling criteria. In addition, the operational risks of a healthcare institution can be increased by inappropriate and / or inefficient scheduling of clinicians for different shifts in the healthcare institution.

[0006] Accordingly, there is a need for systems and methods that reduce the risk to patients and / or healthcare facilities by clinicians with low compliance by tracking the interactions of individual clinicians, identifying interactions with low compliance, and generating a training plan to address and / or correct the interactions with low compliance. There is also a need for systems and methods that identify clinicians who do not faithfully adhere to the best practices and / or protocol standards of a healthcare institution, assist the clinician in adapting the operation of devices within the institution to meet the best practices and / or protocol standards, identify additional well-trained clinician source centers, and enable the scheduling system of the healthcare institution to dynamically and efficiently schedule clinicians based on scheduling criteria designated to reduce operational risk. The systems and methods disclosed herein can reduce operational risk by effectively identifying interactions with low clinician compliance and addressing the clinician through a training plan generated for the clinician, thereby increasing the safety of medical devices and systems used while treating patients.

[0007] According to various embodiments, the 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, reducing the access level of the first user to at least one of the one or more medical devices, including reducing the number of features of each of at least one medical device available to the first user, in response to the compliance score not meeting a threshold compliance score, generating a training program associated with the at least one medical device and the one or more interactions, and automatically transmitting, without user involvement, a training package associated with the training program to the first user and notifying the first user to complete the training program using the training package.

[0008] According to some implementations, the method includes tracking one or more interactions between a first user and 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, 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 in the one or more medical devices based on the training plan.

[0009] According to some implementations, the method includes identifying interactions between a plurality of clinicians and one or more medical devices, and generating performance scores for each of the plurality of clinicians associated with the interactions based on a set of stored rules and one or more interactions of each user of the plurality of clinicians. The method includes receiving a first shift schedule associated with a plurality of clinicians, and determining whether the first shift schedule meets one or more scheduling criteria associated with a medical facility. In response to determining that the first shift schedule does not meet one or more scheduling criteria and that a first performance score for a first clinician does not meet a first evaluation threshold of the one or more scheduling criteria, (1) generating a training plan for the clinician or generating a new second shift schedule for the plurality of clinicians by swapping the first clinician scheduled during a first period with a second clinician not currently scheduled during that period based on a second performance score of the second clinician, and (2) electronically preventing the first clinician from using at least one of the one or more medical devices during the first period. The method includes displaying the new schedule or training plan related to the shift on a display device associated with a clinician scheduling system.

[0010] Other aspects include corresponding systems, devices, and computer program products for implementing the methods described above.

[0011] According to some implementations, a system includes a memory storing instructions and one or more processors coupled to the memory, the processors executing the instructions to cause the system to identify interactions of a plurality of clinicians with one or more medical devices, generate performance scores for each of the plurality of clinicians based on a stored set of rules and one or more interactions of each user of the plurality of clinicians, and receive a first shift schedule associated with the plurality of clinicians. The one or more processors execute the instructions to cause the system to determine whether the first shift schedule meets one or more scheduling criteria associated with a healthcare facility, and when the first shift schedule does not meet the one or more scheduling criteria and a first performance score for a first clinician does not meet a first evaluation threshold of the one or more scheduling criteria, (1) generate a new second shift schedule for the plurality of clinicians by swapping the first clinician scheduled during a first period with a second clinician not currently scheduled during that period, based on a second performance score of the second clinician, and (2) configure to electronically prevent the first clinician from using at least one of the one or more medical devices during the first period. The one or more processors execute the instructions to cause the system to display a new schedule for the shift on a display device associated with a clinician scheduling system. Other aspects include corresponding systems, apparatuses, 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 any of the operations 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 any of the operations of the methods described in this application.

[0013] To better understand the various described embodiments, reference should be made to the following "Detailed Description of the Invention" in conjunction with the following drawings. Throughout the drawings and the specification, like reference numerals refer to corresponding parts.

Brief Description of the Drawings

[0014]

Figure 1A

Figure 1B

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

[0015] In one or more implementations, not all of the components depicted in each drawing may be required, and one or more implementations may include additional components not shown in the drawings. Changes in component arrangement and type may be made without departing from the technical scope of the subject matter of the present disclosure. Additions of components, changes to components, or reductions in the number of components may be used within the scope of the present disclosure.

[0016] The following detailed description is intended as an explanation of various configurations of the present disclosure and is not intended to represent the only configuration in which the present disclosure can be implemented. The accompanying drawings are incorporated herein and constitute a part of the detailed description. The detailed description includes specific details for the purpose of providing a thorough understanding of the present disclosure. However, it will be apparent to those skilled in the art that the present disclosure may be practiced without these specific details. In some cases, structures and components are shown in block diagrams to avoid obscuring the concepts of the present disclosure. For ease of understanding, like components are given the same reference numerals.

[0017] The terminology used in the description of the various examples described in this specification is for the purpose of describing only specific examples and is not intended to be limiting. When used in the description of the various examples described and in the appended claims, the singular forms "a," "an," and "the" are to be construed to include the plural as well, unless the context clearly dictates otherwise. Also, the term "and / or" as used in this specification, when referring to related listed terms, is intended to cover any and all possible combinations of one or more of the associated listed terms and is to be understood to encompass them. Further, the terms "first" and "second" as used in this specification to describe various elements are not to be construed as limiting these elements. These terms are used only to distinguish one element from another. Additionally, the terms "comprises," "comprising," "includes," and / or "including" as used in this specification are specified to mean the presence of the stated feature, step, operation, element, and / or component, but do not preclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof. A clinician may include a qualified or unqualified individual who operates, maintains, repairs, delivers, or otherwise interacts with a medical device in a medical institution, by means of, or for the purpose of, the medical device. Examples of medical institutions as used in this specification include hospitals, long-term care facilities, nursing homes, outpatient treatment centers, store-front retail treatment centers, pharmacies, regional clinics, non-emergency treatment facilities, emergency treatment facilities, and the like.

[0018] According to various aspects, the subject technology provides means for identifying a user either as an individual or a role so as to associate medical treatment acts and other acts with the user. In this regard, a medical device may have a radio frequency identification (RFID) tag reader and be configured to wirelessly receive data related to clinician identification information stored in an RFID tag, such as a clinician's badge or identification card. The medical device may be configured to grant or deny access to one or more protected functions of the medical device and / or computing system associated with a healthcare facility based on the received clinician identification information, a set of passcodes associated with one or more permissions, and / or one or more badges of the clinician associated with one or more permissions. Protected functions may include, but are not limited to, unlocking the medical device, special clinical functions or workflows of the medical device (e.g., infusion of restricted and / or classified medications), access to a biomedicine service agency (e.g., cleaning mode and / or agency of the medical device, maintenance mode and / or agency of the medical device, etc.), and other similar functions of the medical device.

[0019] According to various embodiments, the disclosed medical device may identify new users associated with a healthcare facility without the need for pre-registration with a central computing system, node, and / or server. For example, in response to a clinician attempting to access a protected function of the medical device, such as unlocking the medical device, or attempting to access a restricted function, the medical device may prompt a display device associated with the medical device to provide clinician identification information, such as by scanning a badge. The medical device may 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's identification information does not exist, the medical device may prompt the display device associated with the medical device to enter the clinician's passcode. In response to determining that the entered passcode is valid, the medical device may identify the permissions associated with the passcode, and based on the associated permissions, the medical device may grant and / or deny access to the function to the clinician. In some embodiments, the use of a passcode enables a clinician to access one or more functions of the medical device without scanning a badge and / or when the clinician does not have a badge.

[0020] The medical device may send a message to a device management server that identifies badge information received from the clinician and associated permissions. The device management server may be configured to automatically store badge information associated with the permissions in one or more data storage units associated with the device management server and / or update a master list of clinician badges and associated permissions. The device management server may automatically send the new badge information and associated permissions to other medical devices of the healthcare facility.

[0021] The technology of the subject matter may also include a device management server configured to identify and track the interaction between a clinician (e.g., a nurse) and a medical device in a medical institution (e.g., a hospital). Based on the interaction between the clinician and the medical device, the device management server may determine the number of times a medicine is administered outside of a predetermined medicine administration parameter value (e.g., dosage). If the number meets a threshold, the device management server may add the medicine to a set of medicines administered outside of the predetermined medicine administration parameter value. In some implementations, the device management server may be configured to provide one or more alerts to a user (e.g., a pharmacist, a pharmacy technician, etc.) indicating the set of medicines administered outside of the predetermined medicine administration parameter value. In this regard, in some implementations, the device management server may provide and / or instruct a corresponding entry of the set of medicines in the medicine library of the medicine management system of the medical institution. In some implementations, the device management server may be configured to determine changes to each entry of the set of medicines based on data regarding the administration of the medicine by the clinician (e.g., the dosage at which the medicine is administered).

[0022] In some implementations, the device management server may generate a score for one or more clinicians based on the interaction between the clinician and the medical device, and schedule the clinician to enter a different shift based on the clinician's score. In some implementations, the device management server may be configured to schedule the clinician's shift to include a predetermined percentage or ratio of high-scoring clinicians to lower-scoring clinicians. In some implementations, if one or more lower-scoring clinicians are scheduled for a shift, the device management server may schedule a clinician assigned as a mentor to the lower-scoring clinician for the same shift. In some implementations, the medical institution may temporarily hire one or more clinicians from various clinician staffing agencies, and based on the clinician's score, the device management server may be configured to request a clinician from the clinician staffing agency associated with the majority of high-scoring clinicians. In some implementations, the device management server may generate and / or update a score for the clinician based on the interaction between the clinician and a different medical device.

[0023] In some implementations, for a lower-scoring clinician, the device management server may be configured to provide one or more reminders or follow-up steps for the clinician to perform next. Examples of such steps can include, but are not limited to, checking device settings, checking vital signs, etc. In some implementations, while the clinician is performing a procedure (e.g., a medication administration procedure) using the medical device, the device management server may display one or more steps related to the procedure on a display device associated with the medical device. For further details of the subject technology, reference is made to the description herein with reference to FIGS. 1-12.

[0024] FIG. 1A is a block diagram of a network architecture 100 according to some implementations of the subject technology.

[0025] Network architecture 100 includes one or more medical devices 104-1, 104-2, …, 104-n, which are collectively referred to as medical devices 104 herein. The one or more medical devices 104 may be communicatively coupled, by one or more communication networks 106, to a device management server 108 and / or one or more computing systems 110-1, 110-2, …, 110-m of a medical facility, which are collectively referred to as computing system 110 herein. Examples of the one or more communication networks include, but are not limited to, an intranet, the Internet, a cellular phone network, a mobile data network, a wide area network, a local area network, a metropolitan area network, etc. In some implementations, the one or more communication networks 106 include a public communication network (e.g., the Internet and / or a cellular data network), a private communication network (e.g., a private LAN or a dedicated line), or a combination of such communication networks. The device management server 108 may be configured to communicate with the medical devices 104 and / or the computing system 110.

[0026] The device management server 108 may be configured to receive clinician-related data from and / or transfer such data to the medical devices 104 and / or the computing system 110. Examples of clinician-related data include, but are not limited to, clinician identifiers, clinician profile information, information related to clinician training plans, etc.

[0027] In some implementations, the device management server 108 may be a single computing device, such as a computer server, while in other implementations, the device management server 108 may be implemented by a plurality of computing devices that cooperate to perform the operations of the server system (e.g., cloud computing). Further details of the device management server 108 are described herein with reference to FIG. 2.

[0028] The medical device 104 may include one or more input devices (shown in FIG. 3) configured to receive input to the medical device 104. Clinicians such as users 102-1, 102-2, … 102-n, collectively referred to herein as user 102, may interact with one or more medical devices 104 via one or more input devices. The user 102 may utilize the medical device 104 to access the device management server 108 and / or the computing system 110 and participate in corresponding services provided by the device management server 108 and / or the computing system 110.

[0029] Referring now to FIG. 1B, a block diagram of the device management server 108 and the computing system 110 communicating with the medical device 104 is shown. As described above, the device management server 108 may communicate with the medical device 104 through the network architecture 100. In some implementations, as shown in FIG. 4, the medical device 104 may include a programming module 60 configured to be connected to one or more functional modules.

[0030] As shown in Figure 1B, the device management server 108 may be configured to receive data related to one or more badges and / or passcodes of a clinician and permissions for one or more functions of one or more medical devices 104 associated with the badges and / or passcodes from the computing system 110. In some implementations, the data related to the clinician's badge and / or passcode, as well as the associated permissions, may be collected via the computing system 110 of the medical facility during an onboarding process of adding the clinician to one or more dosing systems (such as an employee database). As shown in Figure 1B, the device management server 108 may be configured to receive configuration data and / or firmware for one or more medical devices 104 communicatively coupled to the device management server 108. The configuration data and / or firmware may be received from one or more other computing systems 110 of the medical facility.

[0031] As shown in Figure 1B, the device management server 108 may be configured to transmit configuration data and / or firmware, data related to one or more badges and / or passcodes, and the associated permissions to one or more medical devices 104 communicatively coupled to the device management server 108. The data related to one or more badges may be associated with clinician identification information of one or more clinicians. In some implementations, the clinician identification information may be a unique identifier associated with and / or configured to identify the clinician, such as an employee identifier, a badge identifier, an identifier associated with the clinician in another dosing system (such as an EMR system) of the medical institution.

[0032] One or more medical devices 104 may be configured to determine whether clinical identification information provided to the medical device (e.g., by a clinician scanning a badge using an RFID reader of the medical device) and / or a passcode received from a user of the medical device is valid based on received data associated with one or more badges and / or passcodes. The medical device 104 may 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 associated with permissions associated with one or more badges and / or passcodes. For any clinical identification information not found in the received data, the medical device 104 may be configured to register the associated clinician and transmit the new clinical identification information to the device management server 108. The device management server 108 may transmit the clinical identification information, along with the permissions associated therewith, to other medical devices 104 of the medical facility. Further details regarding determining whether the clinician's identification information is valid, granting access to one or more functions of the medical device, and registering the clinician via the medical device 104 are described herein with reference to FIG. 6.

[0033] As shown in FIG. 1B, the medical device 104 may be configured to associate the interaction between the clinician and the medical device with the received clinician identification information (e.g., received badge information) and transmit the data related to the interaction to the device management server 108. The device management server 108 may be configured to determine a performance score for the clinician based on the interaction data received from the medical device 104. As shown in FIG. 1B, the device management server 108 may transmit the data related to the performance score and the corresponding clinician identification information (e.g., clinician's badge information, clinician's passcode, clinician's user identifier) to the computing system 110 of the medical facility, so that the computing system 110 and / or the user of the computing system 110 can generate reports such as reports related to the performance of the clinician in the medical facility. The device management server 108 may be configured to prohibit and / or lock one or more functions of the medical device based on the determined performance score. Further details regarding generating the performance score of the clinician and prohibiting and / or locking one or more functions of the medical device are described herein with reference to FIGS. 7-11.

[0034] Next, referring to FIG. 2, a block diagram showing a device management server 108 according to some embodiments is shown. The device management server 108 generally includes one or more processing devices (processors or cores) 202, one or more networks or other communication interfaces 204, a memory 206, and one or more communication buses 208 that interconnect these components. The communication bus 208 optionally includes circuitry (sometimes called a chipset) that interconnects system components and controls communication. 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, a mouse, a trackpad, and / or input buttons. In some embodiments, the display device 212 may include a touch sensing surface, in which case the display is a touch sensing display.

[0035] The 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 magnetic disk storage devices, optical disk storage devices, flash memory devices, and / or other non-volatile solid state storage devices. In some embodiments, the memory 206 includes one or more storage devices located remotely from the processor 202. The memory 206, or the non-volatile memory device within the memory 206, includes a non-transitory computer-readable storage medium. In some embodiments, the memory 206 or the computer-readable storage medium of the memory 206 stores programs, modules, and / or data structures that may be used to perform one or more operations of the device management server 108. For example, the memory 206 includes programs, modules, and / or data structures for an operating system 226, a network communication module 228, a clinician information module 230, a clinician tracking module 232, a clinician scoring module 234, a clinician training plan module 235, a security module 236, and an access device module 238.

[0036] In some implementations, the modules of the operating system 226 may handle various basic system services and include procedures for performing hardware-dependent 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 clinician-related data including, but not limited to, clinician identifiers, clinician profile information, the clinician's current compliance score, etc. The clinician tracking module 232 may be configured to track information related to the interaction between a clinician and a medical device 104. The clinician tracking module 232 may be configured to track a clinician's interactions over the clinician's career. The clinician tracking module 232 may be configured to group and / or categorize a clinician's interactions into one or more groups and / or categories. Additional details regarding the grouping and / or categorization of interactions are described herein with reference to FIG. 6.

[0037] The clinician scoring module 234 may be configured to generate a score for a clinician based on a determination of whether one or more interactions are in compliance. In some implementations, if one or more interactions are in compliance, the clinician scoring module 234 may increase the score, and if the compliance of one or more interactions is low, the clinician scoring module 234 may decrease the score. In some implementations, the clinician scoring module 234 may be configured to generate and / or maintain a score for each group and / or category of interactions. The access module 238 may 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.

[0038] The clinician training plan module 235 may be configured to determine whether one or more interactions are in compliance and generate and / or update a compliance score based on whether the one or more interactions are in compliance. In some implementations, if one or more interactions are in compliance, the clinician training plan module 235 may increase the compliance score, and if the compliance of one or more interactions is low, the clinician training plan module 235 may decrease the compliance score. The clinician training plan module 235 may be configured to generate a training plan based on the compliance score. In some implementations, the clinician training plan module 235 may be configured to generate and / or maintain a compliance score for each group and / or category of interactions, and may generate a training plan for groups and / or categories of interactions having a compliance score that meets a threshold training plan compliance score. The access module 238 may 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.

[0039] Next, referring to FIG. 3, a block diagram showing a medical device 104 is presented. The medical device 104 may include one or more processors 302, one or more networks 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 networks or communication interfaces 304, the memory 306, and the user interface unit 310 may be configured to communicate with each other via one or more communication buses 308. In some implementations, the communication bus 308 may include circuitry (sometimes referred to as a chipset) that interconnects the components of the medical device 104 and controls communication between them. In some implementations, the medical device 104 may include an image / video capture device 324 such as a camera.

[0040] The user interface unit 310 may include a display 312, one or more input devices 316 such as a keyboard or a mouse, one or more voice output devices 318, and / or one or more voice input devices 320. In some implementations, the display 312 may include a touch-sensitive display or surface 314 configured to receive input from the user 102. Examples of the one or more voice output devices 318 include, but are not limited to, speakers, interfaces configured to transfer voice-related data to a device configured to convey voice. Examples of the one or more input devices 320 include, but are not limited to, microphones, interfaces configured to receive voice-related data from a device configured to receive voice.

[0041] Memory 306 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 magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. In some implementations, memory 306 includes one or more storage devices located remotely from processor 302. Memory 306, or the non-volatile memory device within memory 306, includes a non-transitory computer-readable storage medium. In some implementations, the memory 306 or the computer-readable storage medium of memory 306 stores programs, modules, and data structures that may be used to implement the techniques described herein to perform the operations of the medical device 104 and to identify non-compliance patterns of interaction with the medical device 104. Memory 306 may include an operating system 326, a network communication module 328, an image / video capture module 330, an audio input / output module 332, a clinician information module 334, and the like.

[0042] The operating system 326 may be configured to implement execution procedures of various system services of the medical device 104, including but not limited to hardware and software dependent tasks. The network communication module 328 may be configured to execute instructions to connect the medical device 104 to one or more other computing devices, such as a device management server 108 and a computing system 110, via a communication network such as one or more communication interfaces 304 and a communication network 106. The image / video capture module 330 may be configured to execute instructions to capture an image or a continuous stream of images. The voice input module 332 may be configured to process received input data and transmit instructions and / or related data to one or more other components of the medical device 104. The access module 338 may be configured to grant, deny, and / or modify access to the medical device 104. For example, the access module 338 may be configured to grant or deny access to the medical device 104 based on received login credentials for the medical device 104.

[0043] The modules and applications identified above may correspond to a set of executable instructions that implement one or more functions in the manner described above and / or in the methods described in this application (e.g., computer-implemented methods and other information processing methods described herein). One or more of the modules may be implemented as a dedicated hardware device with appropriate input and output signal paths. The modules may be combined or rearranged in different forms in various implementation examples. In some implementation examples, memory 206 and / or memory 306 store a subset of the modules and data structures identified above. In some implementation examples, memory 206 and / or memory 306 store additional modules and data structures not described above. In some implementation examples, processor 302 may be configured to execute the modules identified above to perform one or more of the functions and / or techniques described above. FIG. 4 is a diagram showing an example medical device that may interact with a clinician within a medical institution. The medical device 104 shown in FIG. 4 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 operably engaged with a respective fluid administration set 30, 32, 34, and 36. The fluid supply devices 38, 40, 42, and 44 may take various forms, but are shown as bottles in this example and are inverted and suspended above the pumps. The fluid supply devices may also take the form of bags or other types of containers. Both the medical device 104 and the fluid supply devices 38, 40, 42, and 44 are mounted on a roller stand or pole 46. The particular fluid supply devices and their orientation within the care area (e.g., mounting location, mounting height, type of mounting, etc.) may be generated by one or more interaction records. The interaction record for a set may be generated, for example, in part by detecting a scannable code associated with the set prior to use. Once scanned, the interaction record is recorded and may be used as described herein.

[0044] As shown in the exemplary implementation of FIG. 4, each dosing set 30, 32, 34, and 36 is connected between the same patient 48 and its respective fluid supply device 38, 40, 42, and 44 such that the patient can receive the fluids of all the fluid supply devices. The dosing set may be actively identified, for example, by a scan by a clinician, or passively identified, for example, by wireless or optical detection of the dosing set. Similar to the fluid supply device, once identified, an interaction record may be generated that identifies the dosing set and one or more of the clinician, programming module, pump, and the positioning of the dosing set (e.g., the administration location (e.g., left forearm, right upper arm, etc.)).

[0045] Separate infusion pumps 22, 24, 26, and 28 may be used to drip the fluids of the fluid supply devices into the patient. The infusion pump is a flow control device that acts on each tube or fluid conduit of the fluid dosing set to move the fluid from the fluid supply device through the conduit to the patient 48. Since individual pumps are used, the specific infusion or operation parameters required to drip a specific chemical solution from each fluid supply device into the patient at the specific rate prescribed by the clinician for that fluid can be set individually. The actions performed by the pump or the clinician to drip a specific chemical solution may be recorded and processed as described, or may be associated with one or more interactions.

[0046] Generally, a chemical solution dosing set has more components than shown in FIG. 4. Many have check valves, drip chambers, valved ports, connectors, and other devices well known to those skilled in the art. For the sake of clarity of the illustration, these other devices are not included in the drawings.

[0047] FIG. 5 is an enlarged view of a portion of the medical device shown in FIG. 4. FIG. 5 shows two of the fluid infusion pumps mounted on both sides of the programming module, along with their respective displays and control keys, and the programming module can program both infusion pumps. Pump 22 includes a door 50 and a handle 52, and the handle locks the door in the closed position for operation, unlocks and opens the door to access the internal injection and sensing mechanisms, and operates to load the administration set onto the pump. When the door 50 is open, the tube can be connected to the pump 22. When the door 50 is closed, the tube is operatively engaged with the injection mechanism, upstream and downstream pressure sensors, and other equipment of the pump. In some implementations, a display 54, such as an LED display, may be placed in a location visible through the door and used to visually convey various information related to the pump 22, such as warning indications (e.g., alarm messages). Control keys 56 are present to program and control the operation of the infusion pump as desired. In some implementations, the control keys may be omitted and presented on the display 54 (e.g., a touch screen display) as an interaction element. Infusion pump 24 also has an audible alarm device in the form of a speaker (not shown).

[0048] In the example shown in FIG. 4, the programming module 60 is attached to the left side of the infusion pump 24. Other devices or modules including another infusion pump may be attached to the right side of the infusion pump 24, as shown in FIG. 4. In such a system, each attached pump represents a pump channel for the entire medical device 20. In some implementations, the programming module is used to provide an interface between the infusion pump 24 and an external device, as well as to provide most of the operator interface for the infusion pump 24. Note U.S. Patent No. 5,713,856, entitled "Modular Patient Care System" by Eggers et al., which is incorporated herein by reference and in which the programming module is described as an advanced interface unit.

[0049] Returning to FIG. 5, the programming module 60 includes a display 62 that visually communicates various information, such as the operating parameters of the pump 24 and warning instructions and alarm messages. The programming module 60 may also include a speaker that provides an audible alarm. The programming module 60 may also include one or more input devices, such as a control key 64 or a bar code scanner (not shown), that scan information related to the infusion, patient, clinician, etc. In some implementations, the display 62 may be implemented as a touch screen display (e.g., display 312). In such implementations, the control key 64 may be omitted or reduced in number by providing corresponding interactive elements via a graphical user interface presented via the display 62. The programming module 60 may include a communication system (not shown), using which the programming module 60 may communicate with external devices such as a server of a medical facility or other computer, as well as portable processors such as a handheld communication device or a laptop-type computer, or other information devices that a clinician may have to transfer information and download a drug library to the programming module 60 or the pump. The communication module may be used to transfer access and interaction information of the clinician encountering the programming module or a device coupled thereto (e.g., pump 22 or bar code scanner). The communication system may include one or more of a radio frequency (RF) system such as an RFID system, an optical system such as infrared, a BLUETOOTH (trademark) system, or other wired or wireless systems. The bar code scanner and the communication system may be included integrally with the infusion pump 24 or, in addition thereto, integrally with the programming module 60, for example, when the programming module is not used. Further, the information input device need not necessarily be wired to the medical device, and the information may also be transferred through a wireless connection.

[0050] The example shown in FIG. 5 includes a second pump module 26 connected to the programming module 60. As shown in FIG. 4, more pump modules may be connected. Additionally, other types of modules may be connected to the pump module or to the programming module such as a syringe pump module, an oximeter reader module, a patient-controlled analgesia module, etc. Each module may generate interaction records of one or more interaction types. The interaction record may include an identifier of the module or device where the interaction was performed. The identifier may include a device type identifier, a model or series identifier, or a unique identifier for a particular device.

[0051] Next, referring to FIG. 6, a flowchart is shown that illustrates the process of registering a clinician via a medical device and approving or denying access to the medical device. For purposes of illustration of a specific example, the components of the network architecture 100 illustrated and described with reference to FIG. 1A, the components illustrated and described with reference to FIG. 1B, the components of the device management server 108 illustrated and described with reference to FIG. 2, and the components of the medical device 104 illustrated and described with reference to FIGS. 3, 4, and 5 may be used to explain the process of registering a clinician via a medical device and approving or denying access to the medical device.

[0052] Method 600 includes transmitting, by processor 202 of device management server 108, data related to clinician identification information and / or a passcode associated with one or more clinicians to medical device 104 (block 601). As described above, examples of clinician identification information for a clinician can include, but are not limited to, a badge identifier, a passcode, an identifier of a different medical and / or dosing system (e.g., an EMR system) associated with the clinician. As described above, device management server 108 may store the clinician identification information and / or passcode of one or more clinicians together with permissions for one or more functions of the medical device. Device management server 108 may transmit permission data associated with the passcode to medical device 104. Medical device 104 displays, on a display device, a prompt for causing the user to provide clinician identification information (block 602). For example, processor 302 of medical device 104 may display, on a display device (e.g., display 62) associated with medical device 104, a prompt for causing the user to scan the user's badge near the RFID reader of the medical device. Medical device 104 receives clinician identification information (block 603). Processor 302 of medical device 104 may receive clinician identification information from an RFID tag (e.g., the clinician's badge or identification card) via the RFID reader of medical device 104.

[0053] The medical device 104 may be configured to determine whether received clinician identification information exists (block 604). In some implementations, the medical device 104 determines whether received clinician identification information exists by providing the clinician identification information to the device management server 108, and may receive confirmation that the clinician associated with the identification information is valid, active, and / or in good standing (e.g., the clinician is not on leave). As described above, for example, referring to FIG. 1B, the device management server 108 may receive data related to the badge identifiers of various clinicians ("badge identifier data"), data related to passcodes ("passcode data"), data related to clinician identifiers in different dosing and / or medical systems (e.g., an EMR system), etc., for the clinical identification information of various clinicians, along with permissions associated with the clinician identification information for different clinicians.

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

[0055] In some implementation examples, the device management server 108 may identify a permission associated therewith and send it to the medical device 104 in response to a determination that the clinician identification information received from the medical device 104 is valid, active, and / or in good condition, so as to ensure that the medical device 104 has the latest permission data. The medical device 104 may be configured to update the stored permission data for the clinician with the permission data most recently received from the device management server 108.

[0056] If the medical device 104 determines that the received clinician identification information exists (Yes in block 604), the method 600 proceeds to block 605. The medical device 104 applies one or more permissions associated with the clinician identification information and sends a message indicating whether the clinician has approved access to the medical device 104 to the device management server 108 (block 605). As described above, in some implementation examples, the permissions associated with the clinician identification information may indicate whether the clinician is permitted to unlock the device, whether the permission to unlock the device has been changed based on the clinician's low performance score, whether the clinician has requested that the second clinician also be provided with the clinician identification information to approve access to the device, whether the clinician has permission to access certain restricted functions, and so on. If the medical device 104 determines that the received clinician identification information does not exist (No in block 604), the method 600 proceeds to block 606.

[0057] The processor 302 of the medical device 104 displays a prompt for the clinician to enter a passcode on a display device associated with the medical device 104 (block 606). The processor 302 may receive the passcode provided by the clinician, and the processor 302 determines whether the passcode is valid (block 607). The processor 302 may be configured to determine whether the passcode is valid based on whether the passcode is found in a list of passcodes received from the device management server 108. For example, if the processor 302 cannot find the received passcode within the list of passcodes, the processor 302 determines that the passcode is not valid. If the processor 302 determines that the passcode is not valid, the method 600 proceeds to block 608. The processor 302 electronically prevents the clinician from using the medical device (block 608). The processor 302 may be configured to electronically prevent the clinician from using the medical device 104 by preventing the clinician from logging in to the medical device 104, denying the clinician access to the functions of the medical device 104 and / or modules connected to the medical device 104, electronically locking the medical device 104, and / or rendering the medical device 104 electronically inoperable. In some implementations, the processor 302 may render inoperable the functions of any module connected to the medical device 104. For example, the processor 302 may stop or prevent the initiation of the infusion of medication to the patient via a pump module connected to the medical device 104 after the medical device 104 has been electronically locked out and / or rendered electronically inoperable.

[0058] The processor 302 may electronically lock and / or disable the medical device 104 until the medical device 104 receives clinician identification information associated with a permission for one or more functions of the medical device 104. For example, the processor 302 may electronically lock and / or disable the medical device 104 until the processor 302 receives clinician badge information and / or a passcode that includes permission to unlock the medical device 104, or until electronic access to use the medical device 104 is authorized. Returning to block 607, if the processor 302 determines that the passcode is valid (e.g., identified within a list of received passcodes), the method 600 proceeds to block 609. The processor 302 applies the permission associated with the passcode (block 609). The processor 302 authorizes access to the medical device 104 based on the permission associated with the passcode. The processor 302 may associate the permission and passcode associated with the passcode with the clinician identification information (e.g., clinician badge identifier) received in block 604, and transmit the clinician identification information, associated passcode, and associated permission to the device management server 108 (block 610). The processor 202 of the device management server 108 transmits the new clinician identification information along with the associated passcode and permission to other medical devices 104 (block 611). In some implementations, the processor 202 may transmit the new clinician identification information along with the associated passcode and permission to other medical devices 104 at multiple medical facilities of the medical institution. The processor 202 may store the new clinician identification information along with the associated passcode and permission in one or more data storage units associated with the device management server 108.

[0059] The device management server 108 transmits, along with permissions associated with new clinician identification information, to other medical devices 104 of a healthcare facility and / or institution, thereby ensuring that the medical devices 104 are updated with the most recent clinician identification information and associated permissions. Thus, a clinician registered by one medical device 104 is recognized by other medical devices 104 without the need to register on those other medical devices 104. The consent and / or updated permissions for the clinician are also applied to other medical devices 104, and thus similar access and / or functionality is provided to the clinician. For example, if a clinician registered by a first medical device 104 provides their clinician identification information to a second medical device 104, such as by scanning their badge on the second medical device 104, the second medical device 104 determines, based on the corresponding clinician identification information received from the device management server 108, that the clinician identification information exists, is valid, is active, and / or is in good standing, and may apply the permissions associated with the clinician identification information based on the corresponding permission data received from the device management server 108. The second medical device 104 may be configured to utilize the techniques described above with reference to blocks 604 and 605 to determine whether the clinician identification information exists, is valid, is active, and / or is in good standing, and to apply the associated permissions.

[0060] In some implementation examples, the operation parameters and / or preferences may be associated with one or more clinicians (e.g., associated with corresponding clinician identification information). Examples of operation parameters and / or preferences may include, but are not limited to, modifications made by a clinician to a user interface and / or workflow associated with one or more medications frequently administered by the clinician. In such implementation examples, the device management server 108 may provide the operation parameters associated with the clinician to the medical device 104, and the processor 302 of the medical device 104 may be configured to update a display device associated with the medical device 104 based on the associated operation parameters. For example, in the case of a medication identified as a frequently administered medication, the processor 302 may modify the associated user interface based on one or more operation parameters and / or preferences indicating modifications previously made by the clinician to the user interface while administering the medication.

[0061] As described above, in some implementations, the medical device 104 may be configured to receive a clinician identifier from a patient-related system of a healthcare facility (e.g., an EMR system). The processor 302 may be configured to determine whether a clinician identifier (e.g., the clinician identifier in the EMR) exists in one or more data storage units associated with the medical device 104. If the identifier exists, the processor 302 may apply a permission associated with the medical device 104. If the processor 302 determines that the identifier does not exist, the processor 302 may prompt the clinician regarding other clinician identification information (e.g., scanning the clinician's badge) and / or the clinician's passcode to determine whether to grant access to the medical device 104. If the processor 302 determines that valid clinician identification information and / or passcode has been provided, the processor 302 may apply the associated permission and transmit information related to the clinician identifier in the patient-related system to the device management server 108, and the device management server 108 may automatically update other medical devices 104 with the clinician identifier in the patient-related system, as well as the associated permission, passcode, and / or other clinician identification information.

[0062] When another medical device 104 receives a clinician identifier and an associated permission in a patient-related system, the clinician is then recognized by the other medical device 104. Thus, the permission associated with the clinician identifier in the patient-related system of the medical device 104 may be applied by another medical device 104 that receives the clinician 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 corresponding identifier of the clinician in the EMR system, the second medical device 104 may be configured to apply the permission associated with the clinician identifier without registering the clinician identifier in the EMR system in the second medical device 104.

[0063] Next, referring to FIG. 7, a flowchart is shown that illustrates a process for determining the performance score of one or more clinicians in a medical facility. To illustrate a specific example, the components of the network architecture 100 illustrated and described with reference to FIG. 1A, the components illustrated and described with reference to FIG. 1B, the components of the device management server 108 illustrated and described with reference to FIG. 2, and the components of the medical device 104 illustrated and described with reference to FIGS. 3, 4, and 5 may be used to explain the process for determining the performance score for one or more clinicians in a medical facility.

[0064] Method 700 includes receiving, by processor 202 of device management server 108, information related to an identifier of a clinician in medical device 104 (block 701). As described above, processor 202 may receive information related to the identifier of the clinician in response to the clinician attempting access to medical device 104 (e.g., by scanning their identification card with medical device 104). Processor 202 receives information related to one or more interactions between the clinician and the medical device (block 702). As described above, examples of information related to an interaction between the clinician and medical device 104 include the simultaneous administration of two or more medications, an interaction between medications in the simultaneously administered medications, the amount of medication administered, the dosage of the medication administered, the care area where the clinician interacted with the medical device, the class of the medication administered, the type of patient to whom the medication is administered, the response time to one or more alarms generated by the medical device, the route of treatment for administering the medication (e.g., intravenous, subcutaneous, arterial, epidural, etc.), the type of set for administering the fluid or medication (e.g., tubing, syringe, or connection), the duration of set use for dosing, the type of tubing and connection used during the infusion, the tubing change (e.g., tubing changed at 72 hours, 96 hours, etc.), the administration of a specific medication to a patient, the volumetric flow rate of the medication administered (e.g., administering the medication at a flow rate of 75 milliliters per hour), and other similar information, but is not limited thereto. The interaction may also be associated with a sequence that determines which interaction was performed and the order or timing in which the interaction was performed.

[0065] Based on one or more interactions between the clinician and the medical device, the processor 202 generates and / or updates a performance score for the clinician (block 703). The device management server 108 may be configured to store the performance score of the clinician associated with the clinician (e.g., associated with the clinician's identifier) in one or more data storage systems associated with the device management server 108. In some implementations, the processor 202 may be configured to determine whether the performance score is available for the clinician by querying one or more data storage systems associated with the device management server 108. If the processor 202 obtains the performance score associated with the clinician, the processor 202 updates the performance score based on the received information related to one or more interactions of the clinician. If the performance score is not obtained, the processor 202 generates a performance score based on the received information related to one or more interactions of the clinician and stores the performance score associated with the clinician in one or more data storage systems associated with the device management server 108.

[0066] The processor 202 may be configured to generate and / or update a performance score based on whether an interaction between a clinician and a medical device meets a set of rules associated with one or more treatments for treating a patient. Examples of one or more treatments for treating a patient include, but are not limited to, administering a medicine to a patient using a medical device, responding to an alarm generated by a medical device connected to the patient, following up on a patient after administering a particular medicine, patient monitoring, and the like. Examples of a set of rules associated with a treatment may specify a predetermined volumetric flow rate, pressure rate, dosage, volume, etc. for one or more medicines. In some implementations, the set of rules may also specify one or more groups of medicines that may be administered simultaneously or sequentially. In some implementations, the set of rules may specify different volumetric flow rates, pressure rates, dosage rates, etc. for different types of patients (e.g., patients with heart conditions, diabetic patients, patients with one or more allergies, etc.). In some implementations, the set of rules may further specify different treatment routes of administration (e.g., intravenous, epidural, subcutaneous, other parenteral routes, etc.) that may be used to administer a medicine.

[0067] The processor 202 may determine whether a clinician's interaction with a medical device regarding a treatment for a patient meets a corresponding set of rules based on a comparison of received information related to one or more interactions with corresponding values and / or interactions specified by the set of rules. For example, if a clinician administers two medications simultaneously and the set of rules specifies one or more sets and / or groups of medications that may be administered simultaneously, the processor 202 may verify whether both medications are designated as part of a group or set of medications that may be administered simultaneously. If the processor 202 determines that both medications are not part of a group or set of medications that may be administered simultaneously, the processor 202 may determine that the clinician's interaction does not meet the set of rules regarding the procedure of administering medications, and may generate and / or adjust (e.g., reduce) the clinician's performance score to reflect the clinician's interaction. If the processor 202 determines that both medications are part of a group or set of medications that may be administered simultaneously, the processor 202 may determine that the clinician's interaction meets the set of rules, and may generate and / or adjust (e.g., increase) the clinician's performance score to reflect the clinician's interaction.

[0068] In some implementation examples, the performance score may be determined by identifying rules applicable to interactions during a selected period. The period may be provided as an input. In some implementation examples, the period may be provided as an input via a user interface. In some implementation examples, the period may be specified by a configuration parameter for the device management server 108. The processor 202 may obtain interactions regarding the subject over the period. The processor 202 may then obtain applicable rules from a set of rules for the treatment. This filtering process can reduce the amount of resources required to generate a performance score for the subject. Once the applicable rules are obtained, the processor 202 may then evaluate the interactions by comparing the interactions with the applicable rules. The interaction record may include the type of interaction. The type of interaction may be used as a key to identify relevant compliance rules, for example, by matching an identifier regarding the type of interaction with a value specified in or by the rules regarding the treatment. The interaction record may also include interaction data that identifies, for example, a programmed volume, a programmed amount, or other clinician behavior regarding the interaction. Each rule may contribute a value to a composite performance score.

[0069] The processor 202 may be configured to update the performance score by a predetermined adjustment amount. In some implementation examples, the processor 202 may be configured to determine the amount based on how frequently the clinician's interactions meet the corresponding rules over a predetermined period. For example, if the clinician administers a drug at an inappropriate dose multiple times over 30 days, the processor 202 may decrease the performance score by a larger amount for each successive occurrence.

[0070] The processor 202 may update and / or maintain the performance score over the clinician's career by associating the performance score with the clinician's identifier. In some implementations, the clinician's performance score may be an inter-product common performance score that reflects the clinician's performance score across different medical device products. For example, the processor 202 may update and / or maintain a device-specific performance score for the clinician, each device-specific performance score may be associated with a different medical device product, and the device-specific performance score may be based on the interaction of one or more clinicians with the medical device product. In such implementations, the processor 202 may generate, maintain, and / or update an aggregate performance score based on one or more of the device-specific performance scores.

[0071] The processor 202 determines whether the clinician's performance score meets a low threshold performance score (block 704). The low threshold performance score may be a predetermined performance score indicating that the clinician requires additional guidance and support to satisfactorily complete one or more procedures when treating a patient. If the processor 202 determines that the performance score does not meet the low threshold performance score (e.g., the performance score is higher than the low threshold performance score) (Yes in block 704), the method 700 proceeds to block 707. The processor 202 determines whether the performance score meets a high threshold performance score (block 707).

[0072] If the processor 202 determines that the performance score does not meet the threshold high performance score (e.g., is less than the high performance score) (the "no" in block 707), method 700 proceeds to block 701. If the processor 202 determines that the performance score meets the threshold high performance score (e.g., is greater than or equal to the high performance score) (the "yes" in block 707), method 700 proceeds to block 708. The processor 202 adds the clinician to the list of mentor clinicians (block 708). In some implementations, each clinician in the list of mentor clinicians may be associated with a performance score that meets the threshold high performance score. The processor 202 may store the list of mentor clinicians in one or more data storage systems associated with the device management server 108 in the form of a data structure. In some implementations, the processor 202 may add the clinician to the list of mentor clinicians by adding the identifier of the clinician to a data structure comprising the list of mentor clinicians.

[0073] In block 704, if the processor 202 determines that the performance score meets the threshold low performance score (e.g., the performance score is less than or equal to the threshold low performance score) (the "yes" in block 704), method 700 proceeds to block 705. The processor 202 identifies a mentor clinician for the clinician (block 705). In some implementations, the processor 202 identifies the mentor clinician associated with the fewest number of clinicians. The processor 202 associates the mentor clinician with the clinician (block 706). The processor 202 stores the association between the mentor clinician and the clinician in a data storage system associated with the device management server 108.

[0074] The device management server 108 may be configured to utilize the performance scores of clinicians to improve the efficiency and performance of other systems of a healthcare facility communicatively coupled to the device management server 108. For example, in some scenarios, a healthcare facility may utilize an external clinician staffing resource center for temporary or traveling clinicians who can assist the healthcare facility, and the device management server 108 may be configured to identify one or more excellent external clinician staffing resource centers based on the performance scores of those clinicians.

[0075] Additional details regarding identifying one or more excellent external clinician staffing resource centers are described herein with reference to FIG. 9. In another example, the device management server 108 may be configured to optimize their scheduling based on clinician performance scores and / or scheduling criteria. Additional details regarding optimized scheduling of clinicians are described herein with reference to FIG. 10. In yet another example, the device management server 108 may identify clinicians with low performance scores and generate alerts and / or reminders for completing follow-up activities for the clinicians. Additional details regarding generating alerts and / or reminders for follow-up activities for clinicians with low performance scores are described with reference to FIG. 11.

[0076] In some implementations, the processor 202 may be configured to identify a set of clinicians having a performance score that meets a high threshold performance score over a threshold amount of time (e.g., several weeks, consecutive months, etc.) as highly rated clinicians, and associate a title (e.g., "Hall of Fame", "M.V.P.", etc.) and / or a graphical icon (e.g., a crown graphic, etc.) with the clinicians, and may transmit the association of the title and / or graphical icon with the clinicians to the medical device 104. For example, the processor 202 may be configured to identify a set of clinicians having a performance score that meets a high threshold performance score over five consecutive months as "Hall of Fame" clinicians, and associate the "Hall of Fame" title and the crown graphical icon with the clinician identification information of the corresponding clinicians. In some implementations, the processor 302 of the medical device 104 may determine whether a clinician requesting access to the medical device 104 is associated with any particular title (e.g., "Hall of Fame", "M.V.P.", etc.) and / or graphical icon, and may be configured to display the associated title and / or graphical icon on a display device associated with the medical device 104 (e.g., near the name of the clinician).

[0077] In some implementations, the processor 202 may be configured to determine one or more high-performance care areas (e.g., intensive care unit, emergency treatment room, ward, etc.) and / or one or more low-performance care areas of a healthcare facility based on the performance scores of clinicians associated with the care areas. In some implementations, the processor 202 may be configured to display one or more high-performance care areas on one or more display devices located on one or more floors of the healthcare facility. In some implementations, the processor 202 may be configured to generate and send a message to clinicians associated with a low-performance care area indicating that the care area associated with them is a low-performance care area. In some implementations, the processor 202 may identify a set of clinicians and / or a group of low-performance care areas having low-performance scores over a threshold period, and may be configured to associate the set of clinicians and / or the care area with a group name (e.g., a group name such as "Wall of Shame", etc.).

[0078] In some implementations, the device management server 108 may be configured to send to the medical device 104 an instruction for a clinician having a performance score that meets a low performance threshold score to electronically lock out and / or deny access to one or more features of the medical device 104. In response to receiving the instruction, the medical device 104 may be configured not to grant the clinician access to any functionality of the medical device (e.g., unlocking the medical device 104). In some implementations, the device management server 108 may be configured to associate a clinician having a performance score that meets a low performance threshold score with a second clinician (e.g., an instructor clinician) and require the second clinician to also be provided with clinician identification information in order for the medical device 104 to grant access to the clinician. In some implementations, the device management server 108 may be configured to compile a training package to address the clinician's low performance score. In some implementations, the device management server 108 may be configured to determine the effectiveness of the training package based on changes to the clinician's performance score. In some implementations, the device management server 108 may be configured to cause additional safety alerts to be displayed on a display device associated with the medical device and / or modify the workflow of the medical device to reduce any safety risks while a clinician having a low performance score is interacting with the medical device. In some implementations, the processor 202 may electronically lock out a clinician having a low performance score from the medical device 104 and / or deny access to one or more features of a functional module connected to the medical device 104 (e.g., an infusion pump connected to the medical device 104) to prevent the clinician from initiating and / or interfering with the administration of medication.The additional details of electronically locking out clinicians from a medical device and / or denying access to one or more features of a medical device, generating and / or compiling a training package, assessing the effectiveness of training, and / or requiring authorization for a second clinician to access a medical device and / or one or more functions of a medical device are described in U.S. Provisional Patent Application No. 62 / 865,906, which is incorporated herein by reference.

[0079] Referring now to FIG. 8, a flowchart is shown that depicts a process for warning a healthcare facility's dosing system and / or pharmacist that a clinician has overridden the operating parameters of a medication administration, and determining whether one or more medication administration parameters can be adjusted based on the interaction of one or more clinicians with a medical device used to administer the medication. For purposes of illustration of specific examples, the components of the network architecture 100 illustrated and described with reference to FIG. 1A, the components illustrated and described with reference to FIG. 1B, the components of the device management server 108 illustrated and described with reference to FIG. 2, and the components of the medical device 104 illustrated and described with reference to FIGS. 3, 4, and 5 may be used to explain the process for warning a healthcare facility's dosing system and / or pharmacist that a clinician has overridden the operating parameters of a medication administration, and determining whether one or more medication administration parameters can be adjusted based on the interaction of one or more clinicians with a medical device used to administer the medication.

[0080] Method 800 includes receiving, by processor 202 of device management server 108, information related to an identifier of a clinician in medical device 104 (block 801). Processor 202 may receive information related to the identifier of the clinician in response to the clinician attempting access to medical device 104. In some implementations, the clinician may attempt access to medical device 104 by providing their access credentials for medical device 104 (e.g., scanning their identification card with medical device 104). The clinician's access credentials may be associated with and / or include a unique identifier of the clinician, and medical device 104 may be configured to transmit to device management server 108 a unique identifier associated with the clinician in response to a successful grant of access to the clinician. Examples of the unique identifier of the clinician include, but are not limited to, a user identifier, an employee identifier, and the like.

[0081] The processor 202 identifies a predetermined care area of a medical facility based on the location information of the medical device (block 802). The location of the medical device may be determined using a GPS locator system within the medical device, or by transmitting to or connecting with a specific WiFi transceiver at a known location of the medical device. Examples of care areas include, but are not limited to, an intensive care unit (ICU), a hospital ward, etc. The processor 202 receives information related to one or more interactions between a clinician and the medical device (block 803). Examples of information related to the interaction between a clinician and the medical device 104 include, but are not limited to, the administration of a specific medicine to a patient, the volumetric flow rate of the medicine being administered (e.g., the administration of the medicine at a flow rate of 105 milliliters per hour). In some implementations, the processor 202 may group the interactions between the medical device and the clinician into groups associated with a predetermined care area where the medical device is located. For example, the processor 202 may group the interactions between a clinician and a medical device located in the intensive care unit into a group associated with the intensive care unit, and may group the interactions between a clinician and a different medical device located in the hospital ward into a group associated with the hospital ward.

[0082] Processor 202 identifies the medicine to be administered to the patient using the medical device (block 804). In some implementations, processor 202 may identify the medicine based on one or more interactions between the clinician and the medical device. For example, the interaction between the clinician and the medical device may be programming the medical device to administer the medicine to the patient, the information related to the interaction may indicate the identifier and / or name of the medicine, and processor 202 may determine the medicine to be administered to the patient based on the identifier and / or name of the medicine indicated by the information related to the interaction. In some implementations, processor 202 may identify the medicine to be administered based on the patient's record in the EMR system communicatively coupled to device management server 108.

[0083] Processor 202 determines whether the medicine is administered outside the predetermined values of the medicine administration parameters (block 805). Examples of medicine administration parameters include, but are not limited to, the dose of the medicine, the volumetric flow rate of the medicine administered, the simultaneous administration of two or more medicines, the interaction between the medicines in the simultaneously administered medicines, the amount of the medicine administered, a list of medicines that may be used to simultaneously administer the medicine, etc. The predetermined values of the medicine administration parameters may be stored in the data storage system associated with the pharmacy management system in association with the medicine. The predetermined values of the medicine administration parameters may be provided as an input to the pharmacy management system by a user of the pharmacy management system, such as a pharmacist. Device management server 108 may be communicatively coupled to the pharmacy management system. In some implementations, processor 202 may receive the predetermined values of one or more medicine administration parameters from the medical device and / or the pharmacy management system. In some implementations, processor 202 may be configured to query the pharmacy management system regarding one or more of the predetermined values of the medicine administration parameters.

[0084] Based on the received information related to one or more interactions between the clinician and the medical device, the processor 202 may determine one or more administration values of the medicine by the clinician. For example, the received information may indicate that the clinician administered the medicine at a volumetric flow rate of 100 milliliters per hour. The processor 202 may determine whether the medicine was administered outside the predetermined administration parameter values based on a comparison between the administration value and the predetermined value of the corresponding administration parameter. For example, the processor 202 may determine that the medicine was administered outside the predetermined administration parameter values if the volumetric flow rate at which the medicine was administered by the clinician is greater than or less than the predetermined volumetric flow rate for that medicine.

[0085] If the processor 202 determines that the medicine was not administered outside the predetermined administration parameter values (No in block 805), the method 800 proceeds to block 801. If the processor 202 determines that the medicine was administered outside the predetermined administration parameter values (Yes in block 805), the method proceeds to block 806. The processor 202 updates a counter (block 806). The counter may be associated with the medicine and / or the administration parameters of the medicine. The counter may be associated with a predetermined care area. For example, the processor 202 may maintain multiple counters for a single medicine and / or the administration parameters of the medicine, and each counter may be associated with a different predetermined care area of the medical facility. The processor 202 may update the counter by increasing the counter by a predetermined value (for example, incrementing the value by 1) to indicate that the medicine was administered outside the predetermined administration parameter values again.

[0086] The processor 202 determines whether the number of times a medicine has been administered outside a predetermined value of the administration parameter meets a threshold (block 807). The processor 202 may determine whether the threshold is met based on the value of a counter. If the threshold is not met (the "no" of block 807), the method 800 proceeds to block 801. In some implementations, the processor 202 may update (e.g., decrease) a score associated with a clinician, indicating that the clinician has not sufficiently followed the expected procedure regarding the administration of the medicine. If the processor 202 determines that the threshold is met (the "yes" of block 807), the method 800 proceeds to block 808. In some implementations, when the processor 202 determines that the threshold is met, the processor 202 may not perform an adjustment to lower the performance score of the clinician.

[0087] The processor 202 sends one or more alerts regarding medications to the user of the medication management system (block 808). The processor 202 may indicate corresponding entries in the medication management system for the medications, and / or other information related to the administration of the medications in the alerts. For example, the processor 202 may include the identifier of the medication in the medication management system, and information related to the clinician in a given care area who administered the medication outside of a predetermined value. In some implementations, the processor 202 may add the medication to a list of medications that have been administered a threshold number of times outside of one or more respective predetermined values of their administration parameters. The processor 202 may send to the medication management system an instruction to cause a graphical icon to be displayed on a display device associated with the medication management system, the graphical icon identifying a list of medications and indicating that those medications are most frequently administered outside of a predetermined value. In some implementations, the processor 202 may order a list of medications based on the number of times the medications have been administered outside of a predetermined value (e.g., the top 10 medication violators), and include the ordered list in the alert. In some implementations, if the threshold number of times is not met, the processor 202 may order a list of clinicians who most frequently administer medications outside of a given parameter, include the list in the alert, and cause the list to be displayed on a display device associated with the dosing system.

[0088] In some implementation examples, the processor 202 may determine a new value for a predetermined value of the administration parameter of the medicine in the list. The processor 202 may determine a new value for the administration parameter based on the value of the administration parameter at which the medicine is administered. For example, if the medicine is administered a threshold number of times at a volume flow rate outside a predetermined volume flow rate value (for example, 100 ml / hour), the processor 202 may calculate the average of the administration volume flow rate (for example, 105 ml / hour), and determine the new value of the volume flow rate of the medicine as the average of the administration volume flow rate (for example, 105 ml / hour), and / or may cause the new value of the volume flow rate to be displayed via the editor of the dosing system. In some implementation examples, the processor 202 may determine a new value only for a predetermined care area where the medicine is administered outside the predetermined value of the administration parameter. For example, if the medicine is administered a threshold number of times at a volume flow rate outside a predetermined volume flow rate value in the ICU, the processor 202 may calculate the average of the volume flow rate at which the medicine is administered in that ICU, and may determine the new value of the volume flow rate of the medicine in that ICU as the average of the administration volume flow rate in that ICU.

[0089] The processor 202 may send the determined new value to the user of the drug management system in a message indicating the new value as an update proposed for the predetermined value. In some implementation examples, the processor 202 may indicate in the message that the new value is for a predetermined care area. In some implementation examples, the processor 202 may display the determined new value on the editor user interface for various medicines stored in the data storage system associated with the drug management system.

[0090] Next, referring to FIG. 9, a flowchart is shown that depicts a process for rating and identifying one or more elite external clinician staffing resource centers. To illustrate a specific example, the components of the network architecture 100 illustrated and described with reference to FIG. 1A, the components illustrated and described with reference to FIG. 1B, the components of the device management server 108 illustrated and described with reference to FIG. 2, and the components of the medical device 104 illustrated and described with reference to FIGS. 3, 4, and 5 may be used to explain the process of identifying one or more elite external clinician staffing resource centers.

[0091] Method 900 includes identifying, by the processor 202 of the device management server 108, one or more clinicians associated with an external clinician staffing resource center (block 901). The device management server 108 may receive clinician information from a clinician staffing system of a medical facility, and the clinician information may specify an external clinician staffing resource center with respect to clinicians who are temporary and / or traveling clinicians. The processor 202 may associate a clinician (e.g., a clinician identifier) with the corresponding external clinician staffing resource center and store it in a data storage system associated with the device management server 108. The processor 202 may identify one or more clinicians based on the association with the external clinician staffing resource center.

[0092] The processor 202 determines a set of clinicians from one or more clinicians who meet a threshold performance score (block 902). As described above, the processor 202 associates the performance score of the clinician with the clinician (e.g., the identifier of the clinician) and stores it in the data storage system. The processor 202 may identify the performance score for each of one or more clinicians and determine whether the performance score meets the threshold performance score (e.g., the performance score is greater than or equal to the threshold performance score). The threshold performance score may be a predetermined performance score specified by the medical facility. If the performance score of the clinician meets the threshold performance score, the processor 202 may add the clinician to the set of clinicians.

[0093] Based on the set of clinicians, the processor 202 identifies one or more external clinician staffing resource centers as excellent clinician resource centers (block 903). The processor 202 may identify one or more external clinician staffing resource centers having a threshold number of clinicians in a predetermined set and identify them as one or more external clinician staffing resource centers. For example, the threshold number may be pre - determined to be 3, and the processor 202 may group clinicians in sets based on the associated external clinician staffing resource centers and identify external clinician staffing resource centers having at least 3 clinicians. In some implementations, the processor 202 may be configured to identify one or more clinicians having the highest performance scores and identify the external clinician staffing resource centers associated with them as excellent external clinician staffing resource centers. In some implementations, the processor 202 may be configured to generate a rating for each of one or more external clinician staffing resource centers based on the number of clinicians associated with the resource center and having a performance score that meets the threshold performance score.

[0094] The processor 202 may send a message indicating a human resources dispatching resource center for one or more excellent external clinicians to the human resources dispatching system of the medical facility (block 904). In some implementations, in response to sending the message to the human resources dispatching system, the processor 202 may cause the human resources dispatching system to request clinicians from the human resources dispatching resource center for one or more excellent external clinicians.

[0095] Next, referring to FIG. 10, a flowchart showing a process of verifying and / or optimizing a shift schedule for a clinician is shown. For purposes of illustrating a specific example, the components of the network architecture 100 illustrated and described with reference to FIG. 1A, the components illustrated and described with reference to FIG. 1B, the components of the device management server 108 illustrated and described with reference to FIG. 2, and the components of the medical device 104 illustrated and described with reference to FIGS. 3, 4, and 5 may be used to explain the process of optimizing the scheduling of the clinician.

[0096] Method 1000 includes receiving, by processor 202 of device management server 108, a shift schedule for clinicians in a medical facility (block 1001). In some implementations, performance scores of the clinicians in the shift schedule may be received. Processor 202 determines whether the received shift schedule meets one or more scheduling criteria associated with the medical facility (block 1002). Device management server 108 may be configured to receive one or more scheduling criteria for the medical facility, and processor 202 may store the received scheduling criteria in association with the medical facility. Processor 202 may be configured to verify and / or optimize the received shift schedule based on the scheduling criteria associated with the medical facility. In some implementations, the scheduling criteria may indicate a ratio of clinicians with non-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 being scheduled, three clinicians with non-low performance scores should be scheduled.

[0097] In some implementation examples, the processor 202 may be configured to apply scheduling criteria based on the time of the shift. For example, in the case of a night shift, the processor 202 may be configured to apply scheduling criteria indicating two clinicians with non-low performance scores for every two clinicians with low performance scores, and in the case of an afternoon shift, the processor 202 may be configured to apply scheduling criteria indicating four clinicians with non-low performance scores for every two clinicians with low performance scores. The processor 202 may identify the performance scores of the clinicians included in the received shift schedule, and based on the performance scores of the clinicians, determine whether the ratio of the clinicians with non-low performance scores to the clinicians with low performance scores included in the shift schedule meets the ratio indicated by the scheduling criteria. If the ratio is met, the processor 202 may determine that the received shift schedule meets the scheduling criteria.

[0098] In some implementation examples, the scheduling criteria indicate a threshold average performance score for the shift based on the performance scores of the clinicians scheduled for the shift. The processor 202 may calculate an average performance score based on the performance scores associated with the clinicians included in the received shift schedule, and may determine that the scheduling criteria are met if the calculated average performance meets the indicated threshold average performance score, and then the processor 202 may determine that the received shift schedule meets the scheduling criteria. In some implementation examples, the scheduling criteria may indicate a threshold deviation between the performance scores of the clinicians included in the shift schedule to achieve an even distribution of performance scores across different shifts in the healthcare facility. The processor 202 may be configured to determine whether the shift schedule meets this scheduling criteria based on whether the difference between the performance scores of the clinicians included in the shift schedule meets the threshold deviation.

[0099] If the processor 202 determines that the received shift schedule does not meet one or more scheduling criteria associated with the medical facility (the "No" in block 1002), method 1000 proceeds to block 1003. The processor 202 adjusts the received shift schedule (block 1003). The processor 202 may be configured to adjust the received shift schedule by swapping one or more clinicians included in the shift schedule with one or more other clinicians who are not currently scheduled for a shift during the same period as the shift and / or the period of the received shift schedule. For example, the processor 202 may, based on the performance score of a second clinician who meets a specified threshold performance score, swap a first clinician having a performance score that does not meet the threshold performance score specified by the scheduling criteria of the received shift schedule with a second clinician who is not scheduled during the same period as the shift of the received shift schedule, thereby adjusting the received shift schedule and / or generating a new shift schedule. In some implementations, the processor 202 may electronically prevent the first clinician from using one or more medical devices during the period of the shift of the received shift schedule.

[0100] In some implementation examples, the processor 202 may be configured to swap one or more clinicians scheduled for different shifts. In some implementation examples, the processor 202 may swap one or more clinicians scheduled for a shift that has not yet started. The 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 medical facility. The processor 202 may be configured to store one or more adjusted schedules in a data storage system associated with the device management server 108. The processor 202 transmits (block 1004) a message indicating one or more adjusted schedules to the clinician scheduling system. The processor 202 may include, in the message, an instruction to cause the clinician scheduling system to update the corresponding schedule of the adjusted schedule within the clinician scheduling system.

[0101] Returning to block 1002 next, if the processor 202 determines that the received shift schedule meets one or more scheduling criteria associated with the medical facility (Yes in block 1002), the method 1000 proceeds to block 1005. The processor 202 transmits (block 1005) a message to the clinician scheduling system indicating that it has successfully met one or more scheduling criteria associated with the medical facility for the shift schedule.

[0102] In some implementation examples, the processor 202 may be configured to cause the display device of the medical device 104 to display the clinician's schedule. For example, the processor 202 may identify patients associated with each clinician and medical devices 104 associated with the patients based on a verified and / or optimized schedule. The processor 202 may transmit information related to the clinician's schedule (e.g., information related to when the clinician's shift starts and ends) to the medical device 104 to cause the display device of the medical device 104 to display the clinician's shift schedule. In some implementation examples, the processor 202 may be configured to transmit a verified and / or optimized schedule to be displayed on a display device associated with the clinician scheduling system.

[0103] Referring to FIG. 11, a flowchart is shown that depicts a process of identifying a workflow and generating alerts and / or reminders for follow-up activities for clinicians having low performance scores. For purposes of illustration, the components of the network architecture 100 shown and described with reference to FIG. 1A, the components shown and described with reference to FIG. 1B, the components of the device management server 108 shown and described with reference to FIG. 2, and the components of the medical device 104 shown and described with reference to FIGS. 3, 4, and 5 may be used to describe a process of generating alerts and / or reminders for follow-up activities for clinicians having low performance scores.

[0104] Method 1100 includes receiving, by processor 202 of device management server 108, identification information of a clinician from a medical device (block 1101). As described above, in some implementations, after a clinician is permitted access to a medical device, processor 202 can receive the clinician's identification information. Processor 202 identifies a performance score associated with the clinician (block 1102). As described above, the clinician's performance score can be stored in a data storage system associated with device management server 108, associated with the clinician (e.g., the clinician's identification information), and processor 202 identifies the performance score based on information related to the clinician and / or the received clinician identification information.

[0105] Processor 202 receives information related to one or more interactions between the clinician and the medical device (block 1103). Processor 202 determines whether the performance score of the clinician meets the conditions of a threshold low performance score (block 1104). If processor 202 determines that the performance score of the clinician does not meet the conditions of the threshold low performance score ( 'NO' in block 1104), method 1100 ends. If processor 202 determines that the performance score of the clinician meets the conditions of the threshold low performance score ( 'YES' in block 1104), method 1100 proceeds to block 1105.

[0106] The processor 202 identifies one or more next steps for the clinician (block 1105). The processor 202 may be configured to identify one or more next steps for a plurality of clinicians based on a stored set of rules that specify one or more next steps in the various workflows in which the medical device is configured. In some implementations, the processor 202 may be configured to identify the appropriate next step in a workflow based on the last completed step and / or the current step in that workflow. In some implementations, the processor 202 can identify the last completed step and / or the current step in that workflow based on information received in connection with one or more interactions of the clinician with the medical device. For example, if the information received in connection with one or more interactions indicates that the final step completed by the clinician is the selection of a drug injection, the processor 202 can confirm that the next step is to check the settings of the medical device based on one or more next steps specified by the stored set of rules for the injection workflow for the medical device.

[0107] The processor 202 can cause one or more identified next steps to be displayed on a display device associated with the medical device (block 1106). In some implementations, the processor 202 can send instructions to cause the medical device to display one or more identified next steps and one or more transmitted next steps to the medical device, and the medical device can display one or more next steps on a display device associated with the medical device. In some implementations, the medical device can be configured to display image items (e.g., alert boxes, message boxes, etc.) associated with steps in one workflow in which the medical device is configured, and the processor 202 can send a message and / or instructions indicating identification information associated with the identified next steps, causing the processor of the medical device (e.g., processor 302) to identify the next steps among the stored steps for that workflow and display them on a display device associated with the medical device using the associated image items.

[0108] The processor 202 determines one or more follow-up activities for the clinician (block 1107). Examples of follow-up activities include, but are not limited to, checking one or more settings and / or configuration data of a medical device, checking for improper operation of a medical device, and checking vital signs of a patient or the like. The processor 202 can determine one or more follow-up activities based on one or more identified next steps. For example, if the identified next step is to provide an input to start an infusion of a drug, the processor 202 can determine a follow-up activity of checking the operating state of a pump module connected to the medical device after a predetermined time. In some implementations, the processor 202 can determine one or more follow-up activities based on information related to one or more interactions of the clinician with the medical device. For example, if information related to one or more interactions of the clinician with the medical device indicates that a patient associated with the medical device is separated from the medical device, the processor 202 can determine a follow-up activity of checking that the record of that patient in the EMR system accurately indicates the time when the clinician was separated from the medical device.

[0109] The processor 202 generates and transmits one or more alerts and / or reminders (block 1108) indicating one or more determined follow-up activities to clinicians of a healthcare facility communicatively connected to the device management server 108 and / or to other computing systems. In some implementations, the processor 202 may be configured to transmit alerts and / or reminders for the determined follow-up activities based on whether the determined follow-up activities include performing one or more tasks in a computing system of the healthcare facility. If the processor 202 determines that the follow-up activities include performing one or more tasks in a computing system, the processor 202 can send the alerts and / or reminders to the computing system such that the alerts and / or reminders are displayed on a display device of the computing system. For example, if the follow-up activities include updating patient records in an EMR system of a healthcare facility, the processor 202 can send alerts and / or reminders for the follow-up activities to the EMR such that the alerts and / or reminders are displayed in response to a clinician accessing the EMR. In some implementations, the processor 202 can send one or more alerts and / or reminders to a computing device associated with a clinician (e.g., a clinician's mobile device) to provide the one or more alerts and / or reminders to the clinician. In some implementations, the processor 202 can be configured to lock the clinician out of the medical device 104 if the clinician completes one or more tasks of the follow-up activities within a predetermined threshold of time associated with the follow-up activities (e.g., within 3 hours).

[0110] Referring to FIG. 12, a flowchart showing a process for determining a compliance score and generating a clinician training plan is shown. For purposes of illustration, a plurality of components of network architecture 100 shown and described with reference to FIG. 1, a plurality of components of device management server 108 shown and described with reference to FIG. 2, and a plurality of components of medical device 104 shown and described with reference to FIG. 3 can be used to describe the process for determining a compliance score and generating a clinician training plan.

[0111] Method 400 includes receiving, by processor 202 of device management server 108, information associated with clinician identification information in medical device 104 (block 401). Processor 202 can receive information related to the clinician identification information in response to a clinician attempting to access medical device 104. In some implementations, a clinician can attempt to access medical device 104 by providing his or her access credentials to medical device 104 (e.g., swiping his or her identification information card in medical device 104). The clinician's access credentials can be associated with and / or include the clinician's unique identification information, and medical device 104 can be configured to transmit the unique identification information associated with the clinician to device management server 108 in response to receiving the clinician's access credentials and / or this unique identification information. Examples of the clinician's unique identification information include, but are not limited to, user identification information, employee identification information, etc. In some implementations, processor 202 can determine whether to permit the clinician to access medical device 104 based on whether the clinician requires secondary authorization for the clinician.

[0112] Processor 202 receives information related to one or more interactions with the clinician's medical device (block 402). Examples of information related to an interaction with the clinician's medical device 104 include the administration of a certain drug to a patient, the volumetric flow rate of the administered drug (e.g., administering the drug at a flow rate of 5 milliliters per hour), the administration of two or more drugs simultaneously, the drug-drug interaction between the simultaneously administered drugs, the volume of the administered drug, the dosage of the administered drug, the care area where the clinician interacted with the medical device, the class of the administered drug, the type of patient to whom the drug is administered, the response time to one or more alarms generated by the medical device, the medical route of drug administration (e.g., intravenous, subcutaneous, arterial, epidural, etc.), the type of fluid or drug administration set (e.g., tube, syringe, or connection), the continuous use time of the administration set, the type and connection of the tube used during infusion, the tube replacement parameters (e.g., the tube is replaced at 72 hours, 96 hours, etc.), and other similar information, including but not limited to these. The interaction can be associated with a sequence that determines which interaction occurred and the order or timing of the occurred interaction.

[0113] The processor 202 generates a compliance score for the clinician based on one or more interactions (block 403). The processor 202 can be set to generate a compliance score based on whether the interaction complies with one or more protocols. In some implementations, the processor 202 can determine whether an interaction is protocol compliant based on a stored set of rules that indicate or specify one or more corresponding protocol-compliant interactions. For example, the set of rules can specify a protocol-compliant volumetric flow rate for one or more drugs. Similarly, the set of rules can specify one or more pressure ratios, dosages, volumes, set types, etc. In some implementations, the set of rules can specify one or more protocol-compliant parameters for one or more drugs, patient type, care area within a healthcare facility, drug class, etc. The set of rules can also specify one or more groups of drugs that can be administered simultaneously or sequentially. In some implementations, the set of rules can specify various protocol-compliant volumetric flow rates, pressure ratios, administration rates, etc. for various types of patients (e.g., cardiac patients, obese patients, patients having one or more allergies, etc.). The set of rules can further specify the various medical administration routes through which a drug can be administered. Examples of medical administration routes include, but are not limited to, intravenous, epidural, subcutaneous, and other parenteral routes.

[0114] The processor 202 can compare information related to one or more received interactions with corresponding protocol-compliant interactions specified by a set of rules to determine whether the interaction is protocol-compliant. For example, if a clinician administers two drugs simultaneously and the set of rules specifies one or more combinations and / or groups of drugs that can be administered simultaneously, the processor 202 can check whether both drugs are specified as part of a group or combination of drugs that can be administered simultaneously. If the processor 202 determines that both drugs are not part of a group or combination of drugs that can be administered simultaneously, the processor 202 can determine that the clinician's interaction is non-protocol-compliant and generate and / or adjust (e.g., decrease) the clinician's compliance score to reflect the clinician's non-protocol-compliant interaction. If the processor 202 determines that both drugs are part of a group or combination of drugs that can be administered simultaneously, the processor 202 can determine that the clinician's interaction is protocol-compliant and generate and / or adjust (e.g., increase) the clinician's compliance score to reflect the clinician's protocol-compliant interaction.

[0115] The compliance score can be determined by identifying the rules applicable to the interactions during a selected period. In an interactive implementation, this period can be selected via the user interface. In a non-attended implementation (such as a periodic compliance reporting engine), the above period can be specified as a configuration parameter of the reporting engine. The processor 202 can obtain the interactions for the subject over the above period. Then, the processor 202 can obtain the applicable compliance rules from the set of compliance rules. This filtering can reduce the amount of resources required to generate the compliance score for the subject. Once the applicable compliance rules are obtained, then the processor 202 can evaluate the interactions by comparing the interactions with the applicable rules. The interaction record can include the type of interaction. The type of interaction can be used as a key to identify the relevant compliance rules, for example, by finding in the compliance rules the identification information of the type of interaction, or the value specified by the compliance rules. The interaction record can also include, for example, the data of the interaction for the programmed amount, the programmed speed, or other clinician behaviors. Each rule can provide a value to the composite compliance score. The rules can be normalized to a risk scale. Here, the first limit is associated with safe or protocol-compliant behavior, and the second limit is associated with unsafe or protocol-non-compliant behavior. By this normalization, each rule can contribute equally to the composite score.

[0116] Equation (1) provides one exemplary equation for generating a composite compliance score. Some implementations include weight factors such that certain rules or interactions can contribute more or less heavily to the compliance score. The weight factors may be specified for all scores, or may be adjusted to emphasize, or not emphasize, the performance of certain activities for a particular clinician, or group of clinicians.

Number

[0117] In some implementations, the processor 202 can be configured to compare information related to one or more interactions of one clinician with the interactions of other clinicians to determine whether one or more interactions of one clinician are protocol compliant. For example, for a first clinician, when the processor 202 receives information related to an interaction indicating that the first clinician administered a drug at a certain pressure ratio, the processor 202 can compare whether the pressure ratio at which the first clinician administered the drug is outside the range of pressure ratios used by the majority of other clinicians. If the processor 202 determines that the pressure ratio is outside the range, the processor 202 can determine that the interaction of the first clinician is non - protocol compliant. Similarly, if the processor 202 determines that the pressure is not outside the range of pressure ratios, the processor 202 can determine that the interaction of the first clinician is protocol compliant.

[0118] The processor 202 can be set to adjust the compliance score by a predetermined adjustment amount. In some implementations, the processor 202 can be set to determine the adjustment amount based on how frequently a clinician's interaction was non - compliant with the protocol over a predetermined period. For example, if a clinician administers a drug at incorrect dosages several times over 30 days, each time the clinician administers the drug at an incorrect dosage, the processor 202 can decrease the compliance score by a larger amount. In some implementations, each clinician can be associated with a default starting compliance score, and the processor 202 can store the compliance score in association with the clinician's identification information. The processor 202 can update and / or maintain the compliance score over the clinician's history.

[0119] In some implementations, the processor 202 can group and / or categorize a clinician's interactions into predetermined groups and / or categories based on a set of predetermined rules. For example, the processor 202 can group and / or categorize interactions related to administering a drug at a certain dosage into one group and / or category of interactions, group and / or categorize interactions related to administering a drug at a certain volumetric flow rate into a second group and / or category of interactions, and group and / or categorize interactions related to administering multiple drugs simultaneously into a third group and / or category of interactions. The processor 202 can generate and / or associate a compliance score for each group and / or category of interactions. In some implementations, the processor 220 can generate an overall compliance score based on the compliance scores of one or more groups and / or categories of interactions.

[0120] The processor 202 determines whether the compliance score meets the conditions of the training plan threshold compliance score (block 404). The training plan threshold compliance score may be a predetermined threshold compliance score. The threshold compliance score may be specified as an all-system configurable value. In some implementations, the configurable value may be specified via a user interface. In some implementations, the threshold compliance score may be dynamically generated for a particular clinician or group of clinicians, for example. In some implementations, the processor 202 may be set to determine that the compliance score meets the conditions of the training plan threshold compliance score when the compliance score corresponds to the training plan threshold compliance score. In some implementations, the processor 202 may be set to determine that the compliance score meets the conditions of the training plan threshold compliance score when the compliance score is greater than or equal to the training plan threshold compliance score.

[0121] If the processor 202 determines that the compliance score does not meet the condition of the threshold compliance score (for example, the clinician is considered to be protocol compliant), the method 400 proceeds to block 401. If the processor 202 determines that the compliance score meets the condition of the threshold compliance score (for example, the clinician is considered to be non - protocol compliant), the method 400 proceeds to block 405. The processor 202 generates a training plan (block 405). The processor 202 can identify one or more interactions and / or training modules associated with one or more categories of interactions. For example, if one or more non - protocol - compliant interactions are associated with the category of administering a drug at a certain volumetric flow rate, the processor 202 can identify the training module associated with that category. In some implementations, one or more training modules can be associated with one or more training videos, and the processor 202 can package the one or more training videos into a software package and associate the package with the training plan. In some implementations, the processor 202 can request and / or receive key operation and / or touch input data from a medical device configured to receive key operations and / or touch inputs, and the processor 202 can associate the received key operation and / or touch input data with the training video and / or the training plan. In some implementations, the processor 202 can generate one or more videos based on the key operation and / or touch input data and provide them to the clinician for visual feedback of the clinician's interaction with the medical device.

[0122] Processor 202 can specify one or more training tasks of the training plan. The one or more training tasks can specify instructions and / or tasks for the clinician to perform in order to complete the training plan. The training tasks can specify training materials for the clinician to review and / or for tests to confirm that the clinician has reviewed training materials, review training videos, etc. In some implementations, processor 202 can determine whether the training plan has ended based on whether the clinician has completed the training tasks. Processor 202 can send the training plan to the clinician. In some implementations, processor 202 can save the training plan in association with the clinician's identification information and send a message including a link to the training plan to the clinician.

[0123] In some implementations, processor 202 can associate the clinician with a secondary authorization from another clinician having a higher compliance score than the clinician. For example, processor 202 can identify clinicians having a compliance score above a particular threshold compliance score and associate one or more of the identified clinicians as a secondary authorization for the clinician. By associating one or more other clinicians as a secondary authorization for the clinician, processor 202 causes the medical device to display a prompt for one or more other clinicians to log in or access the medical device when the clinician is accessing the medical device.

[0124] Based on the training plan, the processor 202 can adjust one or more features available to the clinician on one or more medical devices (block 406). In response to determining that the clinician is permitted access to the medical device, the processor 202 can cause the medical device to display additional prompts or messages to the clinician based on the generated training plan. For example, the processor 202 can send a training video related to the training plan to the medical device and cause the medical device to display the training video in response to the clinician being permitted access to the medical device. The processor 202 can cause the medical device to display various training videos associated with the training plan at various steps of the interaction. For example, when the clinician is administering a drug intravenously, the processor 202 can instruct the medical device to display a first training video that instructs the user to confirm whether the drug can be administered intravenously, and can provide a prompt to the clinician to confirm that the drug can be administered intravenously. In response to receiving confirmation from the clinician, the processor 202 can cause the medical device to display a second video that instructs the clinician to confirm whether the dosage of the drug is appropriate for a particular patient.

[0125] In some implementations, the processor 202 disables certain features for the clinician in one or more medical devices based on the training plan. For example, the processor 202 can disable features that allow a skilled clinician to skip some intermediate steps, and cause the clinician associated with the training plan to perform additional steps (e.g., inspection labels and confirmation labels are verified) that clinicians with a higher compliance score do not need to perform. In some implementations, the processor 202 can lock the clinician out of one or more medical devices until the processor 202 determines that the clinician has successfully completed the training plan. The medical device can include an idle time lock out value. Once the clinician accesses the medical device, if no interaction is detected by the medical device for a certain period of time, the clinician can be considered to be in an inactive state. This lack of activity can be recorded as an interaction with the medical device and processed as described. The time used to evaluate inactivity can be adjusted dynamically. For example, a clinician with a low compliance score can have a higher idle time than a clinician with a higher compliance score. This can help clinicians with low performance take more time during their interaction with the medical device. A lower threshold for more capable clinicians can improve the safety of the medical device. The above-mentioned certain period of time can be further created based on the supplied drug, type of infusion, administration set, or other detectable characteristics of the drug supply.

[0126] 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 implementations, 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 task. In some implementations, when a threshold number of training tasks have been completed, processor 202 can permit a clinician access to one or more medical devices.

[0127] Processor 202 can control additional or alternative aspects of a medical device based on an ability score. For example, a medical device can dynamically require a secondary review for an activity based on the ability score of the clinician who initiated the activity. For example, if a regulated drug is to be delivered via a medical device and the clinician's ability score is below a threshold level, the medical device can prevent initiation of delivery until confirmed by a second clinician. In some implementations, the medical device can be set to receive confirmation from a second clinician having a higher ability score than the first clinician, or a higher ability score than a threshold level. The threshold level can be related to the medical device, the drug, the care area for the clinician, or a standard ability threshold level. Additional or alternative factors that can be used to configure a medical device for a secondary review can include the type of infusion, the number of channels being executed for a programming module, the difference between an instruction and an actual programmed parameter (e.g., a greater difference from a provided programming parameter can indicate a higher probability of clinician error), the type of administration set (e.g., some sets may require specific priming or may be prone to loading errors), patient characteristics (e.g., the patient has a particular medical condition, needs, etc.).

[0128] In some implementations, the medical device can be configured to require a particular clinician to review and approve the interaction. For example, it may be necessary for a nursing manager to confirm in order to start a program entered by a junior nurse. As another example, confirmation by a particular physician may be necessary to start a program for an experimental drug or treatment (e.g., as part of a clinical trial). Identity confirmation can be verified by activating a credential submission system that receives identification information for a secondary reviewer. For example, the medical device can scan a badge associated with the secondary reviewer. The scan can be used to provide identity information of the secondary reviewer that can be used to evaluate whether the work of the clinician who started it can be reviewed, or to confirm identity, competency scores, or other factors. Attempts and results (e.g., permitted, rejected) for a particular secondary reviewer can be stored as an interaction and can be included in the processes described herein.

[0129] The compliance scores described so far are typically associated with clinicians. In some implementations, the compliance score can be generated for a device. In some cases, it is the device (rather than the clinician) that requires attention. In this type of implementation, an interaction with a particular device, a particular model or series of devices, or a particular type of device can be identified and a score recorded. Based on the compliance score, one or more control signals can be sent to the device identified as being in non-compliance. The control signal can adjust one or more features of the device, such as disabling the login or adjusting the power status (e.g., sleep mode, or power off). In some implementations, the control signal can adjust the user interface, or other perceivable feedback elements, to indicate that the device may not be functioning properly. In some implementations, the control signal can be sent to a technician who initiates maintenance of the device, or to another automated troubleshooting system. The maintenance can include performing a remote diagnostic process or system refresh to identify or correct a device defect.

[0130] Although some of the various drawings illustrate many of the logical stages in a particular order, for stages that are not order-dependent, the order can be changed, other stages can be combined, or they can be split. Although some order changes or other groupings are specifically mentioned, others are obvious to those skilled in the art, so the rankings and groupings presented herein are not an exhaustive list of variations. Further, it should be recognized that the stages can be implemented by hardware, firmware, software, or any combination thereof.

[0131] Referring further to FIGS. 1-12, the system of the subject technology can identify one or more interactions of a first user with one or more medical devices and can determine a compliance score associated with the first user based on the one or more interactions and a set of predetermined rules. In response to a compliance score that does not meet the criteria of a threshold compliance score, the system can lower the access level of the first user to at least one of the one or more medical devices and can generate a training program associated with the at least one medical device and the one or more interactions. In this regard, lowering the access level can include reducing the number of features of each of the at least one medical device available to the first user. Then, the system is configured to automatically and without regard to the user, assemble and / or transmit to the first user a training package associated with the training program and notify the first user to complete the training program using the training package.

[0132] Subsequently (later), the system may receive a request asking the 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., by swiping his or her badge). Then, in response to this request, the system determines that the first user has not yet completed the training program and may request authorization from a second user who has been granted the right to use the at least one medical device before permitting the request for the first user to access the at least one medical device. According to various implementations, the training program may be generated based on categories associated with the one or more interactions and include one or more training tasks associated with the number of respective features of the at least one medical device. In some implementations, the system may determine that the first user has completed a training program including the one or more training tasks, and in response to determining that the first user has completed the training program, may restore the first user's access level with respect to the at least one medical device. In some implementations, when the corresponding training task associated with each feature is completed by the first user, the one or more respective features of the medical device are made available to the first user.

[0133] Description of the Subject Technology as a Term Various examples of aspects of the present disclosure are described, for convenience, as numbered terms (1, 2, 3, etc.). These are provided as examples and do not limit the subject technology. The identification and reference numbers of the drawings are provided merely as examples and for illustrative purposes, and the following terms are not limited by their identification.

[0134] Item 1. Tracking one or more interactions of a first user with one or more medical devices, determining a compliance score based on a set of stored rules and the one or more interactions, determining whether the compliance score meets the conditions of a 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 conditions of the threshold compliance score, and adjusting one or more features of the one or more medical devices that are available to the first user in the one or more medical devices based on the training plan. A method including these steps.

[0135] Item 2. Receiving a request for access to one of the one or more medical devices, which is associated with the identification information of the first user, determining whether the identification information of the second user among a plurality of users is permitted to access the medical device, and permitting access to the medical device for the identification information of the first user in response to determining that the identification information of the second user is permitted to access the medical device. The method according to Item 1, further including these steps.

[0136] Item 3. The method according to Item 2, wherein the identification information of the second user is associated as a secondary authorization for the identification information of the first user.

[0137] Item 4. Determining whether the identification information of the second user is permitted to access the medical device further includes, in response to receiving the request for access from the first user, providing a request for a certificate associated with the identification information of the second user for display on a display device associated with the medical device, receiving a certificate associated with the identification information of the second user, and permitting access to the medical device for the identification information of the second user, the method according to item 3.

[0138] Item 5. The method according to item 3, wherein the compliance score of the second user is greater than the compliance score of the first user.

[0139] Item 6. Generating a training plan for the first user based on the one or more interactions further includes, based on the one or more interactions, determining a category associated with the one or more interactions, identifying one or more training modules based on the category, and generating the training plan based on the one or more training modules, the method according to item 1.

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

[0141] Item 8. Determining whether one of the one or more training tasks of the training plan has been completed, and in response to determining that the training task has been completed, permitting the first user to access the corresponding characteristic of the medical device, the method according to item 7.

[0142] Item 9. Adjusting, based on the training plan, one or more features of the one or more medical devices that are available to the first user in the one or more medical devices further includes providing a training video associated with the one or more features for display on a display device associated with one of the one or more medical devices. The method according to claim 1.

[0143] Claim 10. The method according to claim 1 further includes expelling the first user from the one or more medical devices, receiving a request for access to the one or more medical devices by the first user, determining, in response to receiving the request, whether the first user has completed the training plan, and permitting access to the one or more medical devices by the first user in response to determining that the first user has completed the training plan.

[0144] Claim 11. A system comprising a memory storing instructions and one or more processors connected to the memory, the one or more processors being configured to execute the instructions to cause the system to track one or more interactions of a first user with one or more medical devices, determine a compliance score based on a set of stored rules and the one or more interactions, determine whether the compliance score meets a threshold compliance score condition, generate a training plan for the first user based on the one or more interactions when the compliance score meets the threshold compliance score condition, and adjust one or more features of the one or more medical devices that are available to the first user in the one or more medical devices based on the training plan.

[0145] Item 12 The one or more processors are configured to execute instructions to cause the system to receive a request for access to one of the one or more medical devices, the request being associated with the identification information of the first user, and to determine whether the identification information of a second user among the plurality of users is permitted access to the medical device, and, if it is determined that the identification information of the second user is permitted access to the medical device, to permit access to the medical device for the identification information of the first user. The system according to claim 11

[0146] Item 13 The system according to claim 12, wherein the identification information of the second user is associated as a secondary authorization for the identification information of the first user

[0147] Item 14 The one or more processors are configured to execute instructions to cause the system to, upon receiving the request for access from the first user, provide a request for a certificate associated with the identification information of the second user for display on a display device associated with the medical device, receive the certificate associated with the identification information of the second user, and permit access to the medical device for the identification information of the second user. The system according to claim 13

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

[0149] Item 16 The one or more processors are configured to execute instructions to cause the system to determine a category associated with the one or more interactions based on the one or more interactions, identify one or more training modules based on the category, and generate the training plan based on the one or more training modules, the system of claim 11.

[0150] Claim 17. The training plan includes one or more training tasks corresponding to the one or more training modules and characteristics of the one or more medical devices, the system of claim 16.

[0151] Claim 18. The one or more processors are configured to execute instructions to cause the system to determine whether one of the one or more training tasks of the training plan has been completed, and, upon determining that the training task has been completed, permit access to the corresponding characteristic of the medical device to the first user, the system of claim 17.

[0152] Claim 19. The one or more processors are configured to execute instructions to cause the system to provide a training video associated with the one or more characteristics for display on a display device associated with one of the one or more medical devices, the system of claim 11.

[0153] Claim 20. The one or more processors of claim 11 are configured to execute instructions to cause the system to: evict the first user from the one or more medical devices; receive a request from the first user for access to the one or more medical devices; upon receiving the request, determine whether the first user has completed the training program; and upon determining that the first user has completed the training program, permit the first user access to the one or more medical devices.

[0154] Claim 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 set of stored rules and one or more interactions of each user of the plurality of clinicians; receiving a first shift schedule associated with the plurality of clinicians; determining whether the first shift schedule meets the conditions of one or more scheduling criteria associated with a healthcare facility; in response to determining that the first shift schedule does not meet the conditions of the one or more scheduling criteria and that a first performance score for a first clinician does not meet the conditions of a first evaluation threshold of the one or more scheduling criteria, (1) generating a new second shift schedule for the plurality of clinicians by replacing the first clinician scheduled for a first time interval based on a second performance score of a second clinician with the second clinician not currently scheduled for that time interval, (2) electronically preventing the first clinician from using at least one of the one or more medical devices during the first time interval; and displaying the new schedule of the shift on a display device associated with a clinician scheduling system.

[0155] Claim 22. Identifying one or more high-performance resource centers based on the performance scores of some of the plurality of clinicians; generating a request for one or more clinicians from the one or more high-performance resource centers rather than from among the plurality of clinicians; and transmitting the request to the clinician scheduling system. The method according to claim 21 further includes these steps.

[0156] Claim 23. Determining a portion of the plurality of clinicians whose performance scores meet the criteria of a threshold low-performance score; receiving information related to the interaction of one clinician belonging to the portion with one medical device; identifying, based on the information, a workflow initiated in the one medical device; identifying, based on the workflow and the set of stored rules, the next step in the workflow; and displaying the next step on a display device associated with the one medical device. The method according to claim 21 further includes these steps.

[0157] Claim 24. Determining one or more follow-up activities for the one clinician based on the information related to the one or more interactions; generating an alert for the one or more follow-up activities; and transmitting the alert for the one or more follow-up activities to a computing device associated with the one clinician. The method according to claim 23 further includes these steps.

[0158] Claim 25. Determining whether an update to the patient's electronic record in the administration system of the healthcare facility is required based on the one or more follow-up activities; and in response to determining that an update to the electronic record is required, displaying the alert adjacent to the electronic record on a display device associated with the administration system. The method according to claim 24 further includes these steps.

[0159] Item 26. Receiving information related to a set of interactions of one of the plurality of clinicians with one medical device, identifying a predetermined care area of the one medical device based on the location information of the one medical device, determining a parameter value associated with a drug administered to a patient based on the information, in response to determining that the parameter value is outside a predetermined threshold, updating a drug counter associated with the predetermined care area and indicating the number of times the drug is administered using the parameter value outside the predetermined threshold, determining whether the drug counter meets the condition of a second threshold, and in response to determining that the drug counter meets the condition of the second threshold, displaying an alert identifying the drug and the predetermined care area on a display device of a drug management system. The method according to item 21, further comprising:

[0160] Item 27. In response to determining that the counter meets the condition of the threshold, further calculating a new value for the parameter based at least on the value of the parameter of the drug administered at that value, sending an alert to a user of the drug management system, and updating the current value of the parameter to the new value of the parameter. The method according to item 26, further comprising:

[0161] Item 28. In response to determining that the drug counter does not meet the condition of the second threshold, reducing the performance score of the one clinician by a predetermined amount, determining whether the reduced performance score meets the condition of a predetermined low threshold performance score, and in response to determining that the reduced performance score meets the condition of the predetermined low threshold performance score, updating the permission associated with the one clinician to electronically prevent the one clinician from using the one or more medical devices. The method according to item 26, further comprising:

[0162] Item 29. In response to determining that the reduced performance score meets the conditions of a predetermined threshold low performance score, assigning a training package to the one clinician, determining whether the training package has been successfully completed, and in response to determining that the training package has been successfully completed, electronically permitting the one clinician access to use the one or more medical devices, the method of claim 26, further comprising.

[0163] Item 30. In response to determining that the reduced performance score meets the conditions of a predetermined threshold low performance score, assigning a mentoring clinician to the one clinician and electronically preventing the one clinician from using one of the one or more medical devices until clinician identification information associated with the mentoring clinician is received, the method of claim 26, further comprising.

[0164] Item 31. A system comprising a memory for storing instructions and one or more processors connected to the memory, wherein the one or more processors execute the instructions to cause the system to identify interactions of a plurality of clinicians with one or more medical devices, generate a performance score for each of the plurality of clinicians based on a set of stored rules and one or more interactions of each user of the plurality of clinicians, receive a first shift schedule associated with the plurality of clinicians, determine whether the first shift schedule meets the conditions of one or more scheduling criteria associated with a healthcare facility, and when the first shift schedule does not meet the one or more scheduling criteria and the first performance score of a first clinician does not meet the conditions of a first evaluation threshold of the one or more scheduling criteria, (1) generate a new second shift schedule for the plurality of clinicians by replacing the first clinician who was scheduled in a first time interval based on the second performance score of a second clinician with the second clinician who was not scheduled in the current time interval of that time interval, (2) electronically prevent the first clinician from using at least one of the one or more medical devices during the first time interval, and display the new schedule of the shift on a display device associated with a clinician scheduling system.

[0165] Item 32. The system according to item 31, wherein the one or more processors are configured to execute instructions to cause the system to identify one or more high-performance resource personnel based on the performance scores of some of the plurality of clinicians, generate a request for one or more clinicians from the one or more high-performance resource personnel rather than from the plurality of clinicians, and transmit the request to the clinician scheduling system.

[0166] Item 33. The one or more processors execute instructions to cause the system to determine, for the system, a portion of the plurality of clinicians whose performance score meets the condition of a threshold low performance score; receive information related to an interaction between one medical device of one clinician belonging to the portion; identify, based on the information, a workflow initiated in the one medical device; identify, based on the workflow and the set of stored rules, a next step in the workflow; and cause the next step to be displayed on a display device associated with the one medical device. The system according to claim 31, which is set to perform the above operations.

[0167] Item 34. The one or more processors execute instructions to cause the system to determine, based on the information related to the one or more interactions, one or more follow-up activities for the one clinician; generate an alert for the one or more follow-up activities; and transmit the alert for the one or more follow-up activities to a computing device associated with the one clinician. The system according to claim 33, which is set to perform the above operations.

[0168] Item 35. The one or more processors execute instructions to cause the system to determine, based on the one or more follow-up activities, whether an update to an electronic record of a patient in an administration system of a health care facility is required; and when an update to the electronic record is required, cause the alert to be displayed adjacent to the electronic record on a display device associated with the administration system. The system according to claim 34, which is set to perform the above operations.

[0169] Item 36. The one or more processors execute instructions to cause the system to receive information related to a set of interactions of one of the plurality of clinicians with one medical device, identify a predetermined care area of the one medical device based on the location information of the one medical device, determine a parameter value associated with a drug administered to a patient based on the information, update a drug counter associated with the predetermined care area indicating the number of times the drug is administered using the parameter value outside a predetermined threshold when the parameter value is outside the predetermined threshold, determine whether the drug counter meets a condition of a second threshold, and display an alert identifying the drug and the predetermined care area on a display device of the drug management system when the drug counter meets the condition of the second threshold. The system according to claim 31 is configured to perform the above operations.

[0170] Claim 37. The one or more processors execute instructions to cause the system to calculate a new value for the parameter based at least on the value of the parameter of the drug administered at that value when the counter meets the condition of the threshold, and to send an alert to a user of the drug management system to update the current value of the parameter to the new value of the parameter. The system according to claim 36 is configured to perform the above operations.

[0171] Claim 38. The one or more processors are configured to execute instructions to cause the system to reduce the performance score of the one clinician by a predetermined amount when the drug counter does not meet the condition of the second threshold, determine whether the reduced performance score meets the condition of a predetermined low threshold performance score, and when the reduced performance score meets the condition of the predetermined low threshold performance score, update the permission associated with the one clinician to electronically prevent the one clinician from using the one or more medical devices, the system according to claim 36.

[0172] Claim 39. The one or more processors are configured to execute instructions to cause the system to assign a training package to the one clinician when the reduced performance score meets the condition of a predetermined low threshold performance score, determine whether the training package has been successfully completed, and when the training package has been successfully completed, electronically grant the one clinician electronic access to use the one or more medical devices, the system according to claim 36.

[0173] Claim 40. The one or more processors are configured to execute instructions to cause the system to determine that the reduced performance score meets the condition of a predetermined low threshold performance score, assign a mentor clinician to the one clinician, and electronically prevent the one clinician from using one of the one or more medical devices until clinician identification information associated with the mentor clinician is received, the system according to claim 36.

[0174] Claim 41. 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 set of predetermined rules; reducing the number of features of each of the at least one medical device available to the first user in response to the compliance score not meeting the threshold compliance score condition, thereby lowering the access level to the first user for at least one of the one or more medical devices; generating a training program associated with the at least one medical device and the one or more interactions; automatically and without user intervention, sending a training package associated with the training program to the first user; and notifying the first user to complete the training program using the training package. A method comprising:

[0175] Item 42. 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 yet completed the training program; and seeking authorization from a second user who has the right to use the at least one medical device before granting the request from the first user to access the at least one medical device. The method according to Item 41, further comprising:

[0176] Item 43. 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 respective features of the at least one medical device. The method further includes the first user 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 access level of the first user with respect to the at least one medical device. The method according to claim 41.

[0177] Claim 44. For each of the features of the one or more medical devices, when the corresponding training task associated with each feature has been completed by the first user, it is made available to the first user. The method according to claim 3.

[0178] Claim 45. A system comprising a memory for storing instructions and one or more processors, wherein the one or more processors are configured to execute the instructions to cause the system to perform any of the methods described in claims 41 to 44.

[0179] Claim 46. A non-transitory computer-readable storage 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 steps of the methods described in claims 41 to 44.

[0180] Further Considerations In some embodiments, any one of the above plurality of terms in this specification may be dependent on any one of the independent terms or any one of the dependent terms. In one aspect, any one of the above plurality of terms (e.g., a dependent or independent term) may be combined with one or more other arbitrary terms (e.g., a dependent or independent term). In one aspect, one claim may include some or all of a plurality of words (e.g., steps, operations, means, or components) described in one term, sentence, clause, or paragraph. In one aspect, one claim can include some or all of a plurality of words described in one or more terms, sentences, clauses, or paragraphs. In one aspect, some of the plurality of words in each of the terms, sentences, clauses, or paragraphs may be deleted. In one aspect, additional words or elements may be added to the terms, sentences, clauses, or paragraphs. In one aspect, the subject technology may be implemented without using some of the components, elements, functions, or operations described herein. In one aspect, the subject technology may be implemented using additional components, elements, functions, or operations.

[0181] The above description is provided so that any person skilled in the art can implement the various aspects described herein. The above description provides various examples of the subject technology, but the subject technology is not limited to these examples. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other aspects as well. Accordingly, all claims are not intended to be limited to the aspects shown herein, but are to be regarded as corresponding to the entire scope of the technical scope that does not conflict with the claims described in words. Here, references to elements in the singular are not intended to mean "only one" unless specifically stated as such, but rather are intended to mean "one or more." Unless otherwise specified, the term "some" means one or more. Masculine pronouns (e.g., he) include cases of feminine and neuter (e.g., she, and it), and vice versa. Headings and subheadings, if any, are used for convenience and do not limit the present disclosure.

[0182] This description describes certain features using a modular infusion pump as an example of a medical device, and the adaptive control function can be implemented using different medical devices (e.g., a stand-alone drug infusion pump, a syringe pump, a drug preparation workstation, or an automated drug dispensing cabinet). The predicates "configured to", "capable of being implemented to", and "programmed to" do not imply any particular tangible or intangible change to the subject, but rather are intended to be used interchangeably. For example, a processor configured to monitor and control an operation or component can also mean a processor programmed to monitor and control the operation, or a processor capable of being implemented to monitor and control the operation. Similarly, a processor configured to execute code can be interpreted as a processor programmed to execute the code or a processor capable of being implemented to execute the code.

[0183] As used herein, the term "automatic" can include execution by a computer or machine without user operation (e.g., by instructions responsive to assertive actions by the computer or machine or other initiating mechanism). The term "example" is used herein to mean "serving as an example or illustration". No aspect or design described herein as an "example" should necessarily be construed as preferred or more advantageous than other aspects or designs.

[0184] Terms such as "aspect" do not mean that this kind of aspect is important to the subject technology or that this kind of aspect applies to all components of the subject technology. The disclosure regarding one aspect may apply to all components, or to one or more components. One aspect can provide one or more examples. Phrases such as "one aspect" can mean one or more aspects and vice versa. Terms such as "embodiment" do not mean that this kind of embodiment is important to the subject technology or that this kind of embodiment applies to all components of the subject technology. One disclosure regarding one embodiment may apply to all embodiments, or to one or more embodiments. One embodiment can provide one or more examples. Terms such as "embodiment" can refer to one or more embodiments and vice versa. Terms such as "configuration" do not mean that this kind of configuration is important to the subject technology or that this kind of configuration applies to all components of the subject technology. One disclosure regarding one configuration may apply to all configurations, or to one or more configurations. One configuration can provide one or more examples. Terms such as "configuration" can mean one or more configurations and vice versa.

[0185] As used herein, the term "determine" or "determining" includes a variety of operations. For example, "determining" can include calculating, computing, processing, deriving, generating, obtaining, searching (e.g., looking up in a table, database, or other data structure), verifying, etc. without user intervention via a hardware element. Also, "determining" can include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. without user intervention via a hardware element. "Determining" can include resolving, selecting, choosing, establishing, etc. without user intervention via a hardware element.

[0186] As used herein, the terms "provide" or "providing" include a variety of operations. For example, "provide" can include storing a value at a location in a memory device for subsequent retrieval, transmitting a value directly to a recipient via at least one wired or wireless communication medium, transmitting or storing the semantic content of a value, and the like. "Provide" can also include, via a hardware element, encoding, decoding a code, encrypting, decrypting an encryption, attesting, verifying, and the like.

[0187] As used herein, the term "message" includes a variety of formats for communicating information (e.g., transmitting or receiving). A message can include an aggregate of machine-readable information such as an XML document, a fixed-field message, a comma-separated message, and the like. In some implementations, a message can include a signal utilized to transmit one or more representations of information. Even when described in the singular, it will be understood that one message can be assembled, transmitted, stored, received, etc. in multiple parts.

[0188] As used herein, the terms "selectively" or "selective" can include a variety of operations. For example, a "selective" process can include determining one option from a plurality of options. A "selective" process can include one or more of the following: a dynamically determined input, a preset input, or a user-initiated input for making a decision. In some implementations, an n-input switch can be included to provide selective functionality, where n is the number of inputs used to make a selection.

[0189] As used herein, the terms "correspond" or "corresponding" include a structural, functional, quantitative, and / or qualitative correlation or relationship between two or more objects, data sets, information, and / or others, and preferably, the correspondence or relationship can be used to interpret one or more from two or more objects, data sets, information, and / or others that appear to be the same or equal. The correspondence can be evaluated using one or more of a threshold value, a range of values, fuzzy logic, pattern matching, a machine learning evaluation model, or a combination thereof.

[0190] In any embodiment, the generated or detected data can be transferred to a "remote" device or location. Here, "remote" means a location or device other than the location or device where the program is executed. For example, a remote location can be another location in the same city (e.g., an office, a laboratory, etc.), another location in a different city, another location in a different state, another location in a different country, etc. Thus, when one item is indicated as "remote" from another item, it can mean that the two items are in the same room but separated, or at least in different rooms or buildings. Further, the two items can be at least 1.6 km (1 mile), 16 km (10 miles), or at least 160 km (100 miles) apart. "Transmitting" information means sending data representing the information as an electrical signal over a suitable communication channel (e.g., a private or public network). "Transferring" an item means any means of carrying that item from one location to the next. Here, any means includes physically transporting the item or, if possible, in other ways, including physically transporting the medium holding the data, at least in the case of data, or transmitting the data. Examples of transmission media include wireless or infrared transmission channels, network connections to other computers or networked devices, and the Internet including information recorded on e-mail transmissions and websites.

[0191] All structural and functional equivalents to the elements of the various aspects described throughout this disclosure that are already known to those of ordinary skill in the art or will later become known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. Further, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is expressly recited in the claims. No element of any of the claims is to be construed under the provisions of 35 U.S.C. § 112, paragraph 6, unless such element is expressly recited using the phrase "means for" or, in the case of a method claim, using the phrase "step for". Additionally, to the extent that the words "include", "have", etc. are used in this specification or claims, such words are intended to be as inclusive as the word "comprise" is construed when used as a transitional term in a claim.

Claims

**Claim 1** A method executed by a processor, comprising: 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 whether a value or type of the one or more interactions meets a corresponding value or type of an interaction specified by a predetermined set of rules, wherein the compliance score increases if each of the interactions meets each of the rules and decreases if each of the interactions does not meet each of the rules; reducing an access level of the first user to at least one of the one or more medical devices, including reducing a number of features of each of at least one medical device available to the first user, in response to the compliance score not meeting a threshold compliance score, and generating a training program associated with the at least one medical device and the one or more interactions; automatically transmitting, without user involvement, a training package associated with the training program to the first user and notifying the first user to complete the training program using the training package. **Claim 2** receiving a request to allow the first user access to the at least one medical device; in response to the request, determining that the first user has not completed the training program; before granting the request to allow the first user access to the at least one medical device, requesting authorization from a second user authorized to use the at least one medical device. The method according to claim 1, further comprising: **Claim 3** 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 features of each of the at least one medical device. The method further comprises: determining that the first user has completed the training program including the one or more training tasks. Responding to a determination that the first user has completed the training program by restoring the first user's access level to the at least one medical device, the method of claim 1, comprising:

4. The method of claim 3, wherein each of the one or more respective features of the medical device is made available to the first user when a corresponding training task associated with each feature is completed by the first user.

5. Assigning a performance score to each of the plurality of users based on medical device interactions performed by the plurality of users on the one or more medical devices; Receiving a first shift schedule associated with the plurality of users; Determining whether the first shift schedule meets one or more scheduling criteria associated with a medical facility; In response to a determination that the first shift schedule does not meet the one or more scheduling criteria and that a first performance score for a first user does not meet a first evaluation threshold of the one or more scheduling criteria, (1) generating a new second shift schedule for the plurality of users by swapping the first user scheduled during a first period with a second user not currently scheduled during the period based on a second performance score of the second user, and (2) electronically preventing the first user from using at least one of the one or more medical devices during the first period; The method of claim 1, further comprising displaying the new second shift schedule on a display device associated with a user scheduling system.

6. Identifying one or more high-performance resource centers based on performance scores of a subset of the plurality of users; Generating a request for one or more users not included in the plurality of users from the one or more high-performance resource centers; The method of claim 5, further comprising transmitting the request to the user scheduling system.

7. Determining a subset of the plurality of users whose performance score meets a low threshold performance score; Receiving information regarding the interaction between the users of the subset and a medical device; Identifying, based on the information, a workflow initiated by the medical device; Identifying, based on the workflow and a stored set of rules, a next step of the workflow; Displaying the next step on a display device associated with the medical device, the method of claim 5 further comprising.

8. Determining, based on the information regarding the one or more interactions, one or more follow-up activities for the user; Generating an alert for the one or more follow-up activities; Sending the alert for the one or more follow-up activities to a computing device associated with the user; Determining, based on the one or more follow-up activities, whether an update to an electronic record of a patient in a medication system of the medical facility is necessary; In response to determining that an update to the electronic record is necessary, displaying the alert adjacent to the electronic record on a display device associated with the medication system, the method of claim 7 further comprising.

9. Receiving information regarding a set of interactions between a user among the plurality of users and a medical device; Identifying a predetermined care area of the medical device based on the location information of the medical device; Determining, based on the information, a parameter value associated with a medicine administered to a patient; In response to determining that the parameter value is outside a predetermined threshold, updating a medicine counter indicating the number of times the medicine is administered using the parameter value outside the predetermined threshold associated with the predetermined care area; Determining whether the medicine counter meets a second threshold; In response to determining that the medicine counter meets the second threshold, displaying an alert identifying the medicine and the predetermined care area on a display device of a medicine management system, the method of claim 5 further comprising.

10. In response to a determination that the medicine counter meets the threshold value, calculating a new value for the parameter value based at least on the parameter value of the medicine to be administered before the medicine is administered; The method according to claim 9, further comprising sending an alert to a user of the drug management system to update the current value of the parameter value to the new value for the parameter value.

11. In response to a determination that the medicine counter does not meet the second threshold value, reducing the performance score of the user by a predetermined amount; Determining whether the reduced performance score meets a predetermined threshold low performance score; The method according to claim 9, further comprising updating a permission associated with the user to electronically prevent the user from using the one or more medical devices in response to a determination that the reduced performance score meets the predetermined threshold low performance score.

12. Assigning a mentoring user to the user in response to a determination that the reduced performance score meets a predetermined threshold low performance score; The method according to claim 9, further comprising electronically preventing the user from using a medical device among the one or more medical devices until user identification information associated with the mentoring user is received.

13. A system, A memory for storing instructions; Executing the instructions to cause the system to Identify one or more interactions between a first user and one or more medical devices, Determine a compliance score associated with the first user based on whether the value or type of the one or more interactions meets the corresponding value or type of the interactions specified by a predetermined set of rules, the compliance score increasing when each of the interactions conforms to each of the rules and decreasing when each of the interactions does not conform to each of the rules, In response to the compliance score not meeting a threshold compliance score, reducing the number of features of each of at least one medical device available to the first user, including reducing the access level of the first user to at least one of the one or more medical devices, generating a training program associated with the at least one medical device and the one or more interactions, automatically, without user involvement, transmitting a training package associated with the training program to the first user, and notifying the first user to complete the training program using the training package, one or more processors configured to comprise a system.

14. The one or more processors 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, determine that the first user has not completed the training program, The system according to claim 13, wherein before approving the request of the first user to access the at least one medical device, a request for approval from a second user authorized to use the at least one medical device is requested.

15. The one or more processors execute the instructions to further cause the system to determine that the first user has completed the training program, The system according to claim 13, wherein in response to the determination that the first user has completed the training program, the access level of the first user to the at least one medical device is restored.

16. 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 features of each of the at least one medical device, wherein each of the one or more features of the medical device is respectively associated with a corresponding training task. When completed by the first user, it is made available to the first user. The system according to claim 15.

17. the one or more processors execute the instructions to further cause the system to assign a performance score to each of the plurality of users based on medical device interactions performed by the plurality of users with the one or more medical devices receive a first shift schedule associated with the plurality of users determine whether the first shift schedule meets one or more scheduling criteria associated with a medical facility in response to a determination that the first shift schedule does not meet the one or more scheduling criteria and that a first performance score for a first user does not meet a first evaluation threshold of the one or more scheduling criteria, (1) generate a new second shift schedule for the plurality of users that exchanges the first user scheduled during a first period with a second user not currently scheduled during the period based on a second performance score of the second user, and (2) electronically prevent the first user from using at least one of the one or more medical devices during the first period The system of claim 13, configured to display the new second shift schedule on a display device associated with a user scheduling system **Claim 18** the one or more processors execute the instructions to further cause the system to determine a subset of the plurality of users whose performance scores meet a threshold low performance score receive information regarding interactions between the subset of users and medical devices identify a workflow initiated on the medical device based on the information identify a next step of the workflow based on the workflow and a stored set of rules The system of claim 17, configured to display the next step on a display device associated with the medical device **Claim 19** the one or more processors execute the instructions to further cause the system to determine one or more tracking activities for the user based on the information regarding the one or more interactions generate alerts for the one or more tracking activities, send the alerts for the one or more tracking activities to a computing device associated with the user, determine whether an update to an electronic record of a patient in the medication system of the healthcare facility is necessary based on the one or more tracking activities, The system according to claim 18, configured to, in response to a determination that an update to the electronic record is necessary, cause the alert to be displayed adjacent to the electronic record on a display device associated with the medication system.

20. when the one or more processors execute the instructions to further cause the system to, identify a predetermined care area of the medical device based on the location information of the medical device, determine a parameter value associated with a medicament administered to a patient based on the information, in response to a determination that the parameter value is outside a predetermined threshold, update a medicament counter indicating the number of times the medicament is administered using the parameter value outside the predetermined threshold associated with the predetermined care area, determine whether the medicament counter meets a second threshold, The system according to claim 18, configured to, in response to a determination that the medicament counter meets the second threshold, cause an alert identifying the medicament and the predetermined care area to be displayed on a display device of a drug management system.

21. when the one or more processors execute the instructions to further cause the system to, in response to a determination that the medicament counter does not meet the second threshold, reduce the user's performance score by a predetermined amount, in response to a determination that the reduced performance score meets a predetermined low performance score threshold, assign a coaching user to the user, The system according to claim 20, configured to electronically prevent the user from using a medical device among the one or more medical devices until user identification information associated with the coaching user is received.

22. when executed by one or more computing devices, 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 whether the value or type of the one or more interactions meets the corresponding value or type of interaction specified by a predetermined set of rules, wherein the compliance score increases if each of the interactions conforms to each of the rules and decreases if each of the interactions does not conform to each of the rules; Reducing the access level of the first user to at least one of the one or more medical devices, including reducing the number of features of each of at least one medical device available to the first user, in response to the compliance score not meeting a threshold compliance score, and generating a training program associated with the at least one medical device and the one or more interactions; Causing one or more computing devices to perform one or more operations, including automatically transmitting, without user involvement, a training package associated with the training program to the first user and notifying the first user to complete the training program using the training package, storing instructions in a non-transitory computer-readable medium.

Images