Drug library manager with customized worksheets

Information

  • Patent Grant
  • 11309070
  • Patent Number
    11,309,070
  • Date Filed
    Monday, July 15, 2019
    5 years ago
  • Date Issued
    Tuesday, April 19, 2022
    2 years ago
Abstract
A drug library management system facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like can be maintained using the drug library management system. The drug library management system can generate and distribute drug library data in pump-specific formats or other customized formats as needed.
Description
TECHNICAL FIELD

This disclosure relates to the field of clinical management, and particularly to systems and methods for efficient management of drug libraries in a networked clinical environment.


BACKGROUND

Modern medical care often involves the use of medical infusion pumps to deliver fluids and/or fluid medicine to patients. Infusion pumps permit the controlled delivery of fluids to a patient and provide flexible yet controlled delivery schedules. Drug libraries within the infusion pumps provide some limits pertaining to the delivery of fluids. Infusion pumps can communicate with a server configured to manage drug library updates and operational software updates of the individual infusion pumps.


SUMMARY

Various techniques for managing drug libraries across a clinical environment and a cloud environment are described herein. These techniques may include creating and maintaining medication and administration data in a drug library database, using the data to create and maintain drug libraries, and distributing the drug libraries to various systems and components. For example, customized drug library data may be provided to infusion pumps for use in administration of medication, while generalized drug library data is proved to middleware, archives, etc. for use in system management, reporting, backup, etc. These and other embodiments are described in greater detail below with reference to FIGS. 1-10. Although many of the examples are described in the context of a hospital environment including particular infusion pumps, data formats, and the like, the techniques described herein can be applied to other types of infusion pumps, data formats, etc.


Some aspects of the present disclosure relate to a drug library management system that facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like are maintained using the drug library management system, also referred to herein as the “drug library manager.”


The drug library manager generates and distributes drug library data in pump-specific formats or other customized formats as needed. Therefore, different types and versions of infusion pumps, even those that use drug library data in different formats or that use different drug library data altogether, may be used in a clinical environment and managed using a single drug library management system.





BRIEF DESCRIPTION OF DRAWINGS

Throughout the drawings, reference numbers may be re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate example embodiments described herein and are not intended to limit the scope of the disclosure.



FIG. 1 is a block diagram of an example clinical environment and an example cloud environment according to some embodiments.



FIG. 2 is a block diagram illustrating components of a clinical environment according to some embodiments.



FIG. 3 is a schematic diagram illustrating components of an infusion pump and a connectivity adapter of a clinical environment according to some embodiments.



FIG. 4 is a block diagram illustrating components of a cloud environment according to some embodiments.



FIG. 5 is a block diagram of various data flows and interactions between a drug library manager, an end user device, an infusion pump, and various other system components during the creation and distribution of drug libraries according to some embodiments.



FIG. 6 is a block diagram of illustrative components of a drug library according to some embodiments.



FIG. 7 is a flow diagram of an illustrative process for managing the creation, maintenance, and distribution of drug libraries according to some embodiments.



FIG. 8 is a user interface diagram of an illustrative interface for creating and maintaining medication and administration data according to some embodiments.



FIG. 9 is a user interface diagram of an illustrative interface for creating and maintaining organizational information according to some embodiments.



FIG. 10 is a block diagram of various data flows and interactions between drug library manager, an infusion pump, and various other system components during the use of drug libraries according to some embodiments.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

The present disclosure is directed to management and use of drug libraries in a networked clinical environment. The clinical environment may include various types and/or versions of infusion pumps. An infusion pump operates using a drug library that describes the medications available for administration, rules for administration of the medications, clinical care areas in which the pump may operate, and the like. Different types or versions of infusion pumps may be configured to use different formats of drug library data. In addition, it may be necessary or desirable to maintain a history of changes to the drug library data.


Some aspects of the present disclosure relate to a drug library management system that facilitates centralized management of the drug libraries that are used by various infusion pumps, including in clinical environments that have different types and/or versions of infusion pumps. Medications, administration rules, critical care area rules, and the like are maintained using the drug library management system, also referred to herein as the “drug library manager.” The drug library manager generates and distributes drug library data in pump-specific formats or other customized formats as needed. Therefore, different types and versions of infusion pumps, even those that use drug library data in different formats or that use different drug library data altogether, may be used in a clinical environment and managed using a single drug library management system.


Additional aspects of the present disclosure relate to generating versions of drug library data that can be used by systems or components in the clinical environment other than infusion pumps. For example, drug library data may be used by middleware systems, reporting systems, archival systems, and the like. When a drug library is to be finalized, the drug library management system may generate a version of drug library data that is standardized or otherwise generalized, in addition to a version that is customized for the specific infusion pump(s) that use the drug library data. The generalized version of the drug library data can be used by middleware systems that process messages received from various infusion pumps, reporting systems that report data generated by or otherwise associated with various infusion pumps, etc. In addition, or alternatively, the generalized version can be archived so that historical versions of the drug library data may be available when needed (e.g., for historical reporting, for troubleshooting problems with infusion pumps when a prior version of the drug library was used, etc.). Advantageously, the generalized version may be archived separately from the drug library database used by the drug library manager, and therefore the drug library database does not need to store historical drug library data.


Although aspects of some embodiments described in the disclosure will focus, for the purpose of illustration, on particular examples of infusion pumps, medication administration rules, formats of drug library data, and the like, the examples are illustrative only and are not intended to be limiting. In some embodiments, the systems and methods described herein may be applied to additional or alternative infusion pumps, medication administration rules, drug library data formats, etc. Various aspects of the disclosure will now be described with regard to certain examples and embodiments, which are intended to illustrate but not limit the disclosure.


Overview of Example Network Environment



FIG. 1 illustrates network environment 100 in which clinical environment 102 communicates with cloud environment 106 via network 104. The clinical environment 102 may include one or more healthcare facilities (e.g., hospitals). The components of the clinical environment 102 are described in greater detail below with reference to FIG. 2. The network 104 may be any wired network, wireless network, or combination thereof. In addition, the network 104 may be a personal area network, local area network, wide area network, over-the-air broadcast network (e.g., for radio or television), cable network, satellite network, cellular telephone network, or combination thereof. For example, the network 104 may be a publicly accessible network of linked networks such as the Internet. In some embodiments, the clinical environment 102 and the cloud environment 106 may each be implemented on one or more wired and/or wireless private networks, and the network 104 may be a public network (e.g., the Internet) via which the clinical environment 102 and the cloud environment 106 communicate with each other. The cloud environment 106 may be a cloud-based platform configured to communicate with multiple clinical environments. The cloud environment 106 may include a collection of services, which are delivered via the network 104 as web services. The components of the cloud environment 106 are described in greater detail below with reference to FIG. 4.


Components of Clinical Environment



FIG. 2 illustrates the clinical environment 102, which includes one or more clinical IT systems 202, one or more infusion pumps 204, and one or more connectivity adapters 206. Further, the clinical environment 102 may be configured to provide cloud user interfaces 208 (e.g., generated and provided by the cloud environment 106). The clinical IT system 202 may include a hospital information system (HIS) designed to manage the facilities' operation, such as medical, administrative, financial, and legal issues and the corresponding processing of services. The HIS can include one or more electronic medical record (EMR) or electronic health record (EHR) systems, as well. The infusion pump 204 is a medical device configured to deliver medication to a patient. The connectivity adapter 206 is a network component configured to communicate with other components of the clinical environment 102 and also communicate with the cloud environment 106 on behalf of the other components of the clinical environment 102. In one embodiment, all messages communicated between the clinical environment 102 and the cloud environment 106 pass through the connectivity adapter 206. In some cases, the connectivity adapter 206 is a network appliance with limited storage space (e.g., memory and/or persistent storage). The cloud user interfaces 208 may be provided to a user in the clinical environment 102 via a browser application, desktop application, mobile application, and the like. The user may access status reports and other data stored in the cloud environment 106 via the cloud user interfaces 208.


The components 202-208 illustrated in FIG. 2 may communicate with one or more of the other components in the clinical environment 102. For example, each of the clinical IT system 202 and the infusion pump 204 may communicate with the connectivity adapter 206 via physical local area network (LAN) and/or virtual LAN (VLAN). Although not shown in FIG. 2, the clinical environment 102 may include other medical devices and non-medical devices that facilitate the operation of the clinical environment 102.


Overview of Messaging in the Clinical Environment



FIG. 3 illustrates the messages and data received, stored, and transmitted by the connectivity adapter 206 in the clinical environment 102. As shown in FIG. 3, the infusion pump 204 may include motor controller unit (MCU) 320 and communications engine (CE) 322, and memory 324 storing drug library data 326 and operational software 328. The drug library data 326 includes boundaries for drug delivery for various medications that can be delivered to patients by infusion pumps. The operational software 328 can include the operating system of the infusion pump 204, as well as other software for performing various functions. Each type of infusion pump and even different versions of the same type of infusion pump may operate with a different operating system. In some embodiments, the MCU 320 uses a less powerful processor (e.g., 12 MHz) and the CE 322 uses a more powerful processor (e.g., 400 MHz).


The MCU 320 may generate and send pump messages to the CE 322 for storage and transmission to the connectivity adapter 206. The pump messages may include clinical information. The CE 322 may send such pump messages to the connectivity adapter 206. Pump messages sent to the connectivity adapter 206 via the CE 322 and generated by the MCU 320 may be transformed by the transformation worker 330 into a standardized dataset message (e.g., message format used by the connectivity adapter 206 to communicate with the cloud environment 106, sometimes referred herein as simply a message). For example, the transformation worker 330 may use drug library data 342, described below, to transform a pump message into a standardized dataset message.


The CE 322 may also receive messages from the connectivity adapter 206 indicating that updates, such as updates to the drug library or updates to the operational software are available and may send messages to the connectivity adapter 206 requesting the updates (e.g., update data). The CE 322 may also receive the update data from the connectivity adapter 206 for storage in the memory 324. The update data may be drug library update data or may be operational software update data. The update data may be provided over a different communication channel than the communication channel(s) used to send or receive messages.


As also shown in FIG. 3, the connectivity adapter 206 may include transformation worker 330, device status manager 332, cache 334, an inbound queue 336, an outbound queue 338, and a data store 340. The transformation worker 330 may transform the messages sent to the connectivity adapter 206 from the infusion pump 204 into the standardized dataset message. The transformation worker 330 may also transform messages sent from the connectivity adapter 206 to the infusion pump 204 into a message format usable by the infusion pump 204.


The inbound queue 336 receives and stores messages from the cloud environment 106 for processing by the connectivity adapter 206. For example, the inbound queue 336 may receive a drug library update message from the cloud environment 106. The drug library update message may be notification that a drug library update is available for at least a portion of the infusion pumps 204 associated with the connectivity adapter 206. In an embodiment, the connectivity adapter 206 may comprise more than one inbound queue such that, for example, there is at least an inbound queue 336 for messages received from the cloud environment 106 over the network 104 and at least another inbound queue for messages received from one or more infusion pumps 204 over the local network. The messages stored in the inbound queue 336 may be associated with one or more sequence identifiers (IDs). The messages received from the cloud environment 106 may be sent over a message channel associated with the network 104.


The outbound queue 338 receives and stores messages to be sent from the connectivity adapter 206. For example, the outbound queue 338 may receive a drug library update message to be sent to one or more infusion pumps over the local network. The drug library update message may be a notification to one or more infusion pumps 204 that a drug library update is available. In an embodiment, the connectivity adapter 206 may comprise more than one outbound queue such that, for example, there is at least an outbound queue 338 for messages to be sent to the cloud environment 106 over the network 104 and at least another outbound queue for messages to be sent to one or more infusion pumps 204 over the local network. The messages stored in the outbound queue 338 may be associated with one or more sequence identifiers (IDs). The messages sent from the connectivity adapter 206 to the infusion pumps 204 may be sent over a message channel associated with the local network.


The device status manager 332 receives the drug library and operational software updates from the cloud environment 106 and caches blocks of the update data in the cache 302. The device status manager 332 processes the received messages from the inbound queue 336 and sends messages to the outbound queue 338 for transmission to the cloud environment 106 or to the infusion pumps 204. The data received from the cloud environment 106 may be sent over a data channel associated with the network 104 and separate from the message channel of the network 104. Because the data channel in the cloud environment is separate from the message channel in the cloud environment, the data transfer does not interfere with the clinical messaging from the connectivity adapter to the cloud environment. The data sent from the cache 302 to the infusion pumps 204 may be sent over a data channel associated with the local network and separate from the message channel associated with the local network. Because the data channel in the local network is separate from the message channel in the local network, the data transfer does not interfere with the clinical messaging from infusion pumps to the connectivity adapter. Thus, congestion on both the message channel of the cloud environment and the message channel of the local network is reduced.


The device status manager 332 also processes transformed messages provided by the transformation worker 330 and merges the data included in the transformed messages into the cache 334 to update the current state of the infusion pump 204 stored in the cache 334.


The data store 340 may store, among other things, drug library data 342. The drug library data 342 may be a generalized version of pump-specific drug library data that is stored on a pump 204. The drug library data 342 may be used to process messages received from a pump 204. For example, the pump 204 may send a message to the connectivity adapter 206 regarding a drug infusion process that has been initiated on the pump 204. The message may include a subset of information about the medication being infused or the infusion process, and the connectivity adapter 206 may derive information from the message. For example, the message may include an identifier of the medication that is being infused, but the message may not include the name of the medication. The connectivity adapter 206 can access the drug library data 342 and obtain the name of the medication that corresponds to the identifier received from the pump. As another example, the message may include an identifier for a clinical care area, but the message may not include the name of the clinical care area. The connectivity adapter 206 can access the drug library data 342 and obtain the name of the medication that corresponds to the identifier of the clinical care area. As a further example, the message may include a channel identifier for a particular channel of the infusion pump, a line identifier for a particular line of the infusion pump, an auto-program reference ID for a particular order number, other identifier information, some combination thereof, etc. The connectivity adapter 206 may determine a corresponding name, description, or other human-readable form from the message data using the drug library data 342. The use of the drug library data 342 to process messages received from an infusion pump 204 is described in greater detail below.


Components of Cloud Environment



FIG. 4 illustrates the cloud environment 106, which includes drug library manager (DLM) 402, report manager 404, device manager 406, data flow manager (DFM) 408, cloud manager (CM) 410, data analyzer (DA) 412, a drug library database (DLDB) 414, and a drug library archive 416.


The DLM 402 may provide a set of features and functions involved in the creation and management of drug libraries for use with infusion pumps, as described in greater detail below. The drug libraries may provide user-defined settings for pump configuration and drug infusion error reduction. For example, the drug libraries may be used as part of a dose error reduction system (DERS). The report manager 404 may provide various reporting capabilities for clinically relevant infusion data which users can choose to use for further analysis, such as tracking and trending of clinical practices.


The device manager 406 may oversee and manage the maintenance of infusion pumps, providing users the capability to view and manage asset and operational data. For example, the device manager 406 may schedule drug library and software updates for infusion pumps.


The DFM 408 may facilitate storing, caching, and routing of data between compatible infusion pumps, compatible external systems, and the like. For example, the DFM 408 may store infusion and operational data received from infusion pumps, store and cache infusion pump drug libraries and software images, convert and route network messaging between the cloud environment 106 and the clinical environment 102, convert and route medication order information from a hospital information system to an infusion pump (e.g., auto-programming or smart-pump programming), and/or convert and route alert information and infusion events from infusion pumps to hospital information systems (e.g., alarm/alert forwarding, and auto-documentation, or infusion documentation).


The CM 410 may serve as a general-purpose computing platform for the other modules illustrated in FIG. 4. Functionally, the CM 410 may be similar to Microsoft Windows or Linux operating systems as it provides the following services: networking, computation, user administration and security, storage, and monitoring.


The DA 412 may provide data analytics tools for generating user interfaces and reports based on the data generated and/or received by the other modules illustrated in FIG. 4.


The DLDB 414 may store data regarding medications, medication administration rules, clinical care areas, and other data maintained and used by the drug library manager 402 to generate drug library data for infusion pumps and other systems or components.


The drug library archive 416 may store generalized drug library data that has been generated by the drug library manager 402. The drug library archive 416 may store a copy of every generalized drug library data set generated by the drug library management, or some subset thereof, for use in record keeping, reporting, etc. Use of archived generalized drug library data is described in greater detail below.


Although not illustrated in FIG. 4, the cloud environment 106 may provide other resources such as processors, memory, disk space, network, etc. The modules 402-412 may be hardware components configured to perform one or more of the techniques described herein. Alternatively, the modules 402-412 may be implemented using software instructions stored in physical storage and executed by one or more processors. Although illustrated as separate components, the modules 402-412 may be implemented as one or more hardware components (e.g., a single component, individual components, or any number of components), one or more software components (e.g., a single component, individual components, or any number of components), or any combination thereof.


In some embodiments, the cloud environment 106 can be implemented using a commercial cloud services provider (e.g., Amazon Web Services®, Microsoft Azure®, Google Cloud®, and the like). In other embodiments, the cloud environment 106 can be implemented using network infrastructure managed by the provider and/or developer of the modules 402-412 shown in FIG. 4. In some embodiments, the features and services provided by one or more of the modules 402-412 may be implemented on one or more hardware computing devices as web services consumable via one or more communication networks. In further embodiments, one or more of the modules 402-412 are provided by one or more virtual machines implemented in a hosted computing environment. The hosted computing environment may include one or more rapidly provisioned and released computing resources, such as computing devices, networking devices, and/or storage devices.


Overview of Drug Library Management System


With reference to an illustrative embodiment, FIG. 5 shows a network environment in which aspects of drug library management may be implemented. As shown, a DLM 402 may include a DLM editor 500 component. The DLM editor 500 may include executable instructions that generate a user interface 512 for display on an end-user computing device 510. For example, the DLM may include, or be associated with, a web server that generates web pages, sends the web pages to the end-user computing device 510, and processes user inputs and interactions with the web pages.


The DLM editor 500 may be used to manage data stored in the DLDB 414, and to generate drug library data for use by various devices and systems, such as infusion pumps 204A, 204B, and the connectivity adapter 206. The data to be stored in the DLDB 414 may include data regarding medications 506, administration rules 508 regarding use of the medications 506, clinical care areas (CCAs) 504 in which medications are used, and other data related to the management of drug libraries.


In some embodiments, the DLDB 414 may include data related to the management of all drug libraries associated with the cloud environment 106. In other embodiments, the DLDB 414 may include data related to a subset of drug libraries associated with the cloud environment 106 (e.g., drug libraries for a particular clinical environment 102 or group of clinical environments, drug libraries for a particular customer or other entity, etc.). For example, there may be multiple DLDBs that are physically or logically separate from each other.


Medications 506 are data entities that represent medications that can be administered via an infusion pump. In some embodiments, a medication 506 data entity may include data regarding a name of a medication, an identifier of the medication (e.g., a unique identifier used by an HIS), an indication of whether the medication is a high-risk medication, and/or other information.


Administration rules 508 are data entities that represent the parameters by which a medication may be administered. For example, an administration rule 508 for a particular medication may include data representing various medication administration parameters such as a dosing unit, a clinical use, and/or other information. In some embodiments, an administration rule 508 for a particular medication 506 may include medication administration parameter data regarding an absolute or “hard” minimum and/or maximum limit to the administration of the medication (e.g., minimum or maximum amount that may be administered overall or in a period of time, minimum or maximum rate at which the medication may be administered, etc.). Such hard limits typically cannot be overridden. In some embodiments, the administration rule 508 may also or alternatively include data regarding a recommended or “soft” minimum and/or maximum limit to administration of the medication. Such soft limits may be overridden (e.g., by users with the proper level of authority, after generation of an alert such as an audible and/or visual notification, etc.). There may be any number of administration rules 508 for a single medication 506. For example, different administration rules 508 may be separately maintained for different clinical uses of the same medication 506, different infusion pumps 204 through which the medication is to be administered, and/or different CCAs 504 in which the medication is to be administered. In some embodiments, a medication 506 may be associated with zero or more administration rules 508. In some embodiments, an administration rule may only be associated with a single medication 506.


CCAs 504 are data entities that represent organizational units of health care enterprises. For example, CCAs may represent hospitals, individual hospital facilities, departments, or lines of care. In some embodiments, a CCA corresponds to a unit of similar clinical uses, patient types, other characteristics, some combination thereof, etc. CCAs 504 may be associated with various medications 506 and administrative rules 508.



FIG. 6 shows an example of a medication 506A associated with multiple administration rules 508A and 508B. The administration rules 508A and 508B are associated with different CCAs 504A and 504B respectively. CCA 504A may correspond to a pediatric unit of a hospital, and CCA 504B may correspond to an ICU of the hospital. The pediatric CCA 504A and ICU 504B may each have various data elements, any or all of which may correspond to medication administration settings. For example, as shown, pediatric CCA 504A may include a data element specifying a maximum dose rate of 200 mL/hr. ICU CCA 504B may include a data element specifying a maximum dose rate of 999 mL/hr. Pediatric CCA 504A may be associated with an administration rule 508A for medication 506A, and that administration rule 508A is more restrictive (e.g., smaller maximum doses) than the administration rule 508B—for the same medication 506A—that is associated with ICU CCA 504B, which is for an adult population. In some embodiments, settings for the pediatric CCA 504A may prevent or override a less restrictive administration rule 508A when the medication 506A is used within the pediatric CCA 504A. However, if the administration rule 508A for the medication 506A is more restrictive than a setting of the pediatric CCA 504A, the setting of the CCA 504A will not override the administration rule 508A.


Returning to FIG. 5, a user may use the DLM editor 500 to organize medications, administration rules, and CCAs into drug libraries that are distributed to infusion pumps and other system components. In some embodiments, the organizational mechanism may be referred to as a worksheet 502. A worksheet 502 is a dataset that includes references to the individual medications and administration rules to be made available to infusion pumps. In addition, the worksheet 502 can be directed to a particular infusion pump 204 or group of infusion pumps 204 that share the same customized drug library data format. Rather than providing data to the infusion pump 204 regarding every medication 506 and administration rule 508 available in the DLDB 414, a worksheet 502 may be used to specify a subset of medications 506 and administration rules 508. For example, a CCA 504 may be added to a worksheet 502, and all of the medications 506 and administration rules 508 associated with the CCA 504 and the target infusion pump 204 are automatically added. In some embodiments, individual medications may optionally be added to a worksheet separately from any CCA that may be added.


The worksheet 502 dataset may be stored in the DLDB 414. The worksheet 502 dataset may include data representing various properties of the worksheet, such as a name, infusion pump type and/or version targeted by the worksheet, creator of the worksheet, creation and/or edit date, approval status, version, and the like. In addition, the worksheet 502 dataset may include a collection of pointers or other references to the data entities representing the various CCAs, medications, and administration rules that are associated with the worksheet 502. Creation of worksheets 502 and other associated operations are discussed in greater detail below.


The DLM editor 500 or some other component of the DLM 402 can generate drug library data using a worksheet 502. For example, once a worksheet 502 has been created or edited, the worksheet 502 may be in a “pending” status, awaiting approval. After the appropriate approval has been granted, the DLM 402 can generate customized drug library data 520 that represents the CCAs, medications, administration rules, and other data in the format that is required for operation of the target pump 204. In addition, the DLM 402 can generate generalized drug library data 522 for use by a middleware component such as the connectivity adapter 206, for reporting and archival purposes, etc.


As shown in FIG. 5, the DLM 402 can send the customized drug library data 520 and generalized drug library data 522 to a connectivity adapter 206 that is in communication with multiple infusion pumps 204A, 204B. The connectivity adapter 206 can store the generalized drug library data 522 in the data store 340. The generalized drug library data 522 may be incorporated into the drug library data 342 as the generalized drug library data that corresponds to the customized drug library data 520 that has also been or soon will be received.


The CA 206 can provide the customized drug library data 520 to the appropriate infusion pump 204A, or instruct the appropriate infusion pump 204A to obtain the customized drug library data 520. The infusion pump 204A can store the customized drug library data 520 in memory 324 for use in future operation. For example, the infusion pump 204A may replace customized drug library data 326 currently in memory with the newly-received customized drug library data 520.


Other infusion pumps, such as those that do not operate using the same format of customized drug library data, are not provided with or instructed to obtain the customized drug library data 520. For example, infusion pump 204B may be a different type of infusion pump than infusion pump 204A, or may be a different version of infusion pump 204A that is not compatible with the customized drug library data 520. In this example, infusion pump 204B is not provided with the customized drug library data 520. As another example, infusion pump 204B may be located in a location that is associated with a different CCA than infusion pump 204A. The customized drug library data 520 may be targeted at the CCA with which infusion pump 204A is associated, but not the CCA with which infusion pump 204B is associated. In this example, infusion pump 204B is not provided with the customized drug library data 520. Details and examples of the drug library update process are described in greater detail in international patent application no. PCT/US2019/041705, titled “UPDATING INFUSION PUMP DRUG LIBRARIES AND OPERATIONAL SOFTWARE IN A NETWORKED ENVIRONMENT” and filed Jul. 12, 2019, which is incorporated by reference herein.


The worksheet structure allows for comparison among different versions of drug library data selected for a particular subset of CCAs and infusion pumps. For example, a worksheet that is being edited can be compared to a current version of the worksheet and/or one or more historical versions of the worksheet. The various versions of the worksheet—and therefore the various versions of the corresponding drug library data—may be stored as generalized drug library data (e.g., JavaScript Object Notation or JSON files) and may be compared to each other (e.g., using text-based comparison methods) to determine any differences between the files. Differences between the files may be presented to a user so that the user can see what is different between the versions of the drug library data. These storage and comparison methods are generally more efficient than storing multiple versions of each individual record of drug library data in the DLDB along with corresponding effective dates, indicators of active/inactive status, and the like.


The worksheet structure also allows users to build specific drug libraries for specific purposes from a shared dataset. For example, a first worksheet designed for a cancer center utilizes a first subset of the overall DLDB, while a second worksheet designed for a pediatric center utilizes a second subset of the overall DLDB that is different than the first subset. The individual records for the CCAs, medications, and administration rules may be maintained in the DLDB without being changed for the different worksheets. The worksheet datasets for the different worksheets may be modified in the DLDB, and may reference data for the CCAs, medications, and administration rules.


The worksheet structure facilitates maintaining and viewing lifecycle of a particular set of drug library data. For example, a particular set of drug library data, corresponding to a particular worksheet, may progress through various stages, including: editable, in review, active, and archived. Data regarding each of the states may be included in the worksheet dataset. Accordingly, the worksheet structure provides revision control for each set of drug library data independently from other sets of drug library data (as managed using other worksheets).


The worksheet structure also facilitates identification and implementation of global changes that are to be cascaded to all worksheets. For example, when two worksheets contain a particular CCA and that CCA is updated (e.g., a new administration rule is added, a limit is changed, etc.), then both worksheets may automatically incorporate the changes made to CCA by virtue of the worksheets referencing the CCA data that has been changed rather than including a copy of CCA as it previously existed. As another example, when a worksheet's dataset has been updated, the system can notify health care professionals that new drug library data may need to be finalized to incorporate the changes for use on infusion pumps.


Example Drug Library Management Process



FIG. 7 is a flow diagram of an illustrative process 700 that may be executed by a DLM Editor 500 or some other component of the DLM 402 to manage the creation and maintenance of data in the DLDB 414, and the creation and maintenance of drug libraries for use by infusion pumps 204, connectivity adaptors 206, reporting systems, archival systems, and the like. Advantageously, the process 700 facilitates the maintenance of DLDB data in a streamlined manner, such that data regarding, medications, administration rules, CCAs, and the like needs to be created or edited only once, and the changes will be reflected across all associated drug libraries. Moreover, the process 700 provides the creation of generalized drug library data that may be archived in addition to being used by other systems or components. Thus, a repository of archived generalized drug library data files can provide snapshots of the state of drug libraries at various points in time, without requiring the maintenance of out-of-date data in the DLDB. Portions of the process 700 will be described with reference to the diagram of illustrative data flows and interactions shown in FIG. 5, and the diagrams of illustrative user interfaces shown in FIGS. 8 and 9.


The process 700 shown in FIG. 7 begins at block 702. The process 700 may begin in response to an event, such as when the DLM editor 500 begins execution. When the process 700 is initiated, a set of executable program instructions stored on one or more non-transitory computer-readable media (e.g., hard drive, flash memory, removable media, etc.) may be loaded into memory (e.g., random access memory or “RAM”) of a computing device of the cloud environment 106. The executable instructions may then be executed by a hardware-based computer processor (e.g., a central processing unit or “CPU”) of the computing device. In some embodiments, the process 700 or portions thereof may be implemented on multiple processors, serially or in parallel.


At block 704, the DLM editor 500 or some other component of the DLM 402 can manage medications in the DLDB 414. Management of medications may include creating, viewing, updating, and/or deleting medication 506 data entities.


In some embodiments, a user may use an end-user computing device 510 to access the DLM editor 500, as shown in FIG. 5. The end-user computing device 510 may present an interface for management of medications in the DLDB 414. For example, the DLM editor 500 may provide interface 800, shown in FIG. 8, to manage a particular medication 506. Interface 800 includes an infusion pump selection area 802, a medication information entry area 804, a dosing limitations entry area 806, and a clinical care area selection control 808.


The user may use the infusion pump selection area 802 to select the infusion pump(s) and/or pump version(s) which may be used to administer the medication. The user may use the medication information entry area 804 to manage properties of the medication. For example, identification-related properties such as a generic drug name 840 and display name 841 may be entered. A clinical use 842 may also be entered. Medication amount 843, volume amount 844, medication unit 845, and concentration type may also be entered.


In some embodiments, a single medication may be associated with different display names. For example, an infusion pump may only support a limited number of characters for display of medication names. Because the length of some medication names may exceed the character limit, a shortened name, such as a brand name, abbreviation, or the like may be used. Additionally, or alternatively, emphasis may be applied to portions of medication names for display to help avoid errors in the administration of the medications. Illustratively, the display name may be entered using “tall man” lettering in which part of a medication's name is displayed in upper case letters to help distinguish it from other medication names that may look and/or sound similar (e.g., “prednisone” and “prednisolone” may be displayed as “predniSONE” and “predniSOLONE”).


A subset of the information in the various entry areas may corresponds to an administration rule for the medication, indicated by administration rule data entry group 810. In some embodiments, additional and/or alternative information in the various entry areas may be part of a particular administration rule. For example, an administration rule may be assigned to a single infusion pump and/or pump type, and therefore the infusion pump selection area 802 may be included in the administration rule data entry group 810. As another example, an administration rule may not include a specific display name for the medication, and therefore administration rule data entry group 810 may not include display name 841, or display name 841 may be optional.


In some embodiments, a single medication may also or alternatively be associated with different clinical uses, amounts, volumes, units, and/or concentration types. Additional medication entries—corresponding to different database records, different presentations of the interface 800, etc. —may be used to capture these different combinations of properties. However, each of the medication entries can be linked to the top-level medication (e.g., as identified by a generic medication name and a unique identifier). In this way, the medication and all of its different available combinations of properties can be treated as a single unit when desired, or as separate medication entities when desired.


Returning to FIG. 7, at block 706 the DLM editor 500 or some other component of the DLM 402 can manage administration rules in the DLDB 414. Management of administration rules may include viewing and/or updating deleting medication 506 data entities.


In some embodiments, a user may use interface 800, shown in FIG. 8, to manage administration rules for a particular medication 506. In addition to identification and other properties of a medication 506 as described above, the interface 800 includes a dosing limitations entry area 806. The dosing limitations entry area 806 may be used to specify various administration limits, permissions, and the like. The data provided in these fields is then incorporated into the drug library for the selected infusion pump, and serves to constrain the manner in which the medication is permitted to be administered by the infusion pump. For example, after specifying a dosing unit 860, a user may enter a lower hard limit 861, lower soft limit 862, upper soft limit 863, and/or upper hard limit 864, all in terms of the selected dosing unit. An infusion pump that is administering the medication subject to this administration rule will not be permitted to administer an amount outside the hard lower and upper limits. The infusion pump may be permitted to administer an amount outside the soft lower and upper limits, but before doing so the infusion pump may be required to perform various procedures, such as initiating alerts, prompting for authorization, or the like.


Additional administration techniques 865, such as bolus administration, piggyback delivery, piggyback interruption, and the like may be permitted or blocked. Some administration techniques may be associated with their own properties, and permission of such techniques may cause display of additional data entry areas or interfaces. For example, if bolus administration is permitted in the additional administration techniques 865 section, then additional fields for dosing unit, upper and lower hard/soft limits, and the like may be shown.


In some embodiments, multiple administration rules 508 may be associated with a single medication 506. For example, different administration rules may be used for different infusion pumps. As another example, different administration rules may be associated with different clinical uses or concentrations of the medication. In these cases, additional medication entries may be added for the medications, and the different administration rules may be created accordingly. However, each of the separate medication entries and corresponding administration rules may be associated with a single top-level medication 506 data entity.


Returning to FIG. 7, at block 708 the DLM editor 500 or some other component of the DLM 402 can manage CCAs in the DLDB 414. Management of CCAs may include creating, viewing, updating, and/or deleting CCA 504 data entities. In some embodiments, a user may use a remote computing device 510 that presents an interface for management of CCAs in the DLDB 414. For example, the DLM editor 500 may provide interface 900, shown in FIG. 9, to manage a particular CCA 504.


Interface 900 includes an infusion pump selection area 902, a CCA information entry area 904, a pump settings entry area 906, and a medication selection control 908. A user may use the infusion pump selection area 902 to select the infusion pump(s) and/or pump version(s) which may be used to administer medication in the CCA. The user may use the CCA information entry area 904 to manage properties of the CCA. For example, identification-related properties such as a CCA name 940, service line 941, and CCA description 942 may be entered. The user may use the pump settings entry area 906 to manage CCA-specific settings for the selected pump(s), such as pump limits and other operational settings of the pump(s) in the CCA. For example, the user may provide a maximum dose rate 960, permit or prohibit additional administration functions 961 such as delayed start or standby, and set occlusion alarm settings 962. In some embodiments, the user may enter CCA-specific patient limits used to constrain which patients are permitted to be treated using the infusion pump on the CCA. For example, patient limits may include minimum body surface area (BSA) 963, maximum BSA 964, minimum height 965, maximum height 966, minimum weight 967, maximum weight 968, and the like.


Although FIG. 7 illustrates blocks 704 and 706 occurring in a sequential manner on one execution path, and block 608 occurring in a parallel execution path, this example is illustrative only. In some embodiments, the operations that correspond to blocks 704, 706, and 708 may be performed sequentially, asynchronously, in parallel, or individual blocks may be repeated as needed.


At block 710, the DLM editor 500 or some other component of the DLM 402 can manage the medications available to the CCAs in the DLDB 414. For example, interface 800 for a particular medication 506 includes a clinical care area selection control 808. A user can activate this control 808 to access an interface that facilitates selection of CCAs in which the medication 506 is permitted to be administered. As another example, interface 900 for a particular CCA 504 includes a medication selection control 908. A user can activate this control 908 to access an interface that facilitates selection of medications that are permitted to be administered in the CCA 504.


At block 712, the DLM editor 500 or some other component of the DLM 402 can generate a worksheet 502 for management of a drug library. The worksheet 502 provides the mechanism by which a drug library is generated for use by an infusion pump. Separate drug libraries may be generated and maintained for different infusion pumps and/or infusion pumps in different facilities, CCAs, and the like. In some embodiments, a user may use a remote computing device 510 that presents an interface for management of worksheets in the DLDB 414. The user may enter worksheet-specific information, such as a name for the worksheet, an infusion pump type and/or version targeted by the worksheet, and the like. Data representing the worksheet-specific information may be stored in the DLDB 414.


At block 714, the DLM editor 500 or some other component of the DLM 402 can add one or more CCAs 504 to the worksheet 502. Addition of CCAs 504 also has the effect of adding the various medications 506 and administration rules 508, associated with the CCAs 504, to the worksheet 502. In this example, the CCAs provide the organizational means by which groups of medications may be added to a particular worksheet and therefore to a particular drug library.


In some embodiments, the DLM editor 500 or some other component of the DLM 402 can add one or more medications 506 to the worksheet 502. Addition of medications 506 to the worksheet 502 may also have the effect of adding various administration rules 508, associated with the medications 506, to the worksheet 502. In some embodiments, medications may be added in addition to CCAs, or medications may be added individually without the addition of CCAs to the worksheet. At block 716, the DLM editor 500 or some other component of the DLM 402 can finalize the worksheet 502. The worksheet 502 may be finalized on-demand (e.g., immediately upon request by a user of the DLM editor 500), or it may be subject to an authorization workflow. For example, the user may request finalization of a worksheet after various changes have been made. Other users may then access the worksheet, view the changes if desired, and approve or reject the worksheet. Once the changes to the worksheet are approved, the worksheet may be finalized.


At block 718, the DLM editor 500 or some other component of the DLM 402 can generate customized drug library data using the worksheet 502. As described above, the worksheet may specify a particular pump type or version to which the worksheet applies. The DLM 402 can use drug library specification data for the particular infusion pump type or version to generate customized drug library data of the pump.


Drug library specification data may include rules for generating customized drug library data required by the infusion pump, such as the data structure and format in which the drug library data is expected to be delivered, functions or other transformations to be applied to data from DLDB 414 to produce data that is able to be used by the infusion pump, etc. For example, a first type of infusion pump may expect data fields a, b, c, d, and e to be present, in that sequence, for each medication record. A second type of infusion pump may also expect fields a, b, and c, to be present, together with data that corresponds to field d with a mathematical transformation applied, and also a different field f instead of field e. In addition, the second type of infusion pump may expect the fields to be in a different sequence than the first type of infusion pump. The drug library specification data for the two different types of infusion pumps can provide data regarding these expected data fields, formats, transformations, sequences, and the like.


The DLM 402 can determine which infusion pump type and/or version is specified in the worksheet 502 data set. The DLM 402 can then generate customized drug library data 520 for the infusion pump using the worksheet 502 data in the DLDB 414 and the drug library specification data for the infusion pump.


At block 720, the DLM editor 500 or some other component of the DLM 402 can generate generalized drug library data using the worksheet 502. As described above, the generalized drug library data is data used by middleware components (e.g., connectivity adapters 206), reporting systems, archival systems, and the like. Each of these different devices and components may be configured to operate using the same generalized drug library data. Illustratively, the generalized drug library data may be created in a standardized data format, such as JavaScript Object Notation (JSON), eXtensible Markup Language (XML), or the like. In some embodiments, generalized drug library specification data may be used to generate the generalized drug library data. Generalized drug library specification data may include rules for generating the generalized drug library data, such as the data structure and format in which the generalized drug library data is to be delivered, the functions or other transformations to be applied to data from the DLDB 414 to produce the generalized drug library data, etc. The DLM 402 can generate the generalized drug library data using the worksheet 502 data in the DLDB 414 and the generalized drug library specification data.


Although FIG. 7 illustrates blocks 718 and 720 occurring in a sequential manner on one execution path, this example is illustrative only. In some embodiments, the operations that correspond to blocks 718 and 720 may be performed in a different sequence, asynchronously, or in parallel.


At block 722, the DLM editor 500 or some other component of the DLM 402 can distribute the drug library data generated above. For example, as shown in FIG. 5, the DLM 402 can provide the generalized drug library data 522 and customized drug library data 520 to a connectivity adapter 206. In some embodiments, the DLM may also or alternatively store the generalized drug library data in a drug library archive 416. Storage of generalized drug library data 522 in the drug library archive 416 can provide certain benefits, such as the ability to access the drug library, as it existed when generated, at some future time even after other intervening versions of the drug library have been generated. In addition, by maintaining prior versions of drug libraries in the separate archive 416, the size and complexity of the DLDB 414 may be controlled because it is not necessary to store records for every prior version of data in the DLDB 414.


At block 724, the process 700 may terminate. In some embodiments, the process 700 may return to prior blocks. For example, a user may return to block 712 to generate additional worksheets for other CCAs, infusion pumps, etc.


Example Drug Library Use



FIG. 10 is a diagram of data flows and interactions between components of the networked clinical environment 102 and cloud environment 106 during use of drug library data. As shown, an infusion pump 204 may send a message at [A] to a connectivity adapter 206. For example, the message may indicate the start of a medication infusion process for a particular medication. The customized drug library data used by the infusion pump 204 may use an identifier of “13BSF68X” for the medication. Therefore, the message may include the identifier “13BSF68X” instead of the name of the medication, in order to reduce the size of the message. The message may include other information about the infusion, such as a timestamp for the start of the infusion, a dosage amount, etc. Alternatively or in addition, to reduce the overall size of the message, the message may include identifiers for other data regarding the infusion, or other information from which human-readable forms can be derived. For example, the message may include a patient identifier, an infusion type identifier, a CCA identifier, a channel identifier, a line identifier, an auto-program reference identifier, other identifiers, some combination thereof, etc.


The connectivity adapter 206 may receive the message from the infusion pump, and process the message at [B]. For example, the connectivity adapter 206 may process the message into a standardized dataset message using generalized drug library data in the data store 340. The generalized drug library data may include the name of the drug that corresponds to the identifier “13BSF68X,” the name of the CCA that corresponds to a CCA identifier, etc. The connectivity adapter 206 may therefore include the drug name, CCA name, etc. in the standardized dataset message without receiving the drug name, CCA name, and the like from the infusion pump 204. The connectivity adapter 206 may send the standardized dataset message to the cloud environment 106 at [C].


The infusion pump 204 may send a second message to the connectivity adapter 206 at [D]. The second message may relate to a past event at the infusion pump 204, such as an infusion occurring days earlier when a different version of customized drug library data was being used by the infusion pump 204. For example, when the cloud environment 106 received the standardized dataset message at [C], it may have determined that a prior message had not been received (e.g., by inspecting a sequential message identifier in the message). The cloud environment 106 may then have initiated a process to obtain the missing message, and as a result the infusion pump 204 re-sent (or sent for the first time) the message to the connectivity adapter 206 at [D].


The connectivity adapter 206 can begin processing the second message at [E]. However, the infusion that is the subject of the message occurred when the infusion pump 204 was using an older version of the customized drug library data. Therefore, the message may include information (e.g., an identifier) that the connectivity adapter 206 is unable to resolve by referencing the generalized drug library data currently present in the data store 340, because generalized drug library data currently present in the data store 340 corresponds to the current customized drug library data used by the infusion pump 204. In this instance, the connectivity adapter 206 may retrieve, from the cloud environment 106 at [F], an archived version of the generalized drug library data that corresponds to the customized drug library data used by the infusion pump 204 when the second message was originally generated.


The connectivity adapter 206 may proceed with processing the second message at [G] into a standardized dataset message using the archived version of generalized drug library data. For example, the connectivity adapter 206 may determine the drug name using the identifier and the archived version of the generalized drug library data and proceed with processing the second message at [G] into a standardized dataset message that includes the drug name. The connectivity adapter 206 may then send a second standardized dataset message to the cloud environment 106 at [H].


Embodiments of the present disclosure can be defined by the following non-limiting clauses:


Clause 1: A system configured to manage a drug library within a clinical environment, the system comprising:

    • a plurality of infusion pumps configured to deliver medication to one or more patients, each respective infusion pump of the plurality of infusion pumps comprising a memory configured to store drug library data;
    • a drug library manager comprising one or more computer processors and memory, the drug library manager configured to:
      • receive, from a user device, first input data representing one or more medications;
      • receive, from the user device, second input data representing one or more administration rules, wherein the second input data comprises:
        • data representing a medication of the one or more medications;
        • data representing an infusion pump type of a plurality of infusion pump types; and
        • data representing one or more medication administration parameters;
      • receive, from the user device, third input data representing one or more clinical care areas, wherein the third input data comprises:
        • data representing one or more clinical care area settings; and
        • data representing an association of a clinical care area with zero
      • or more administration rules
      • receive, from the user device, fourth input data representing selection of a first clinical care area of the one or more clinical care areas; store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
        • a first reference to infusion pump data in the drug library database, the infusion pump data representing the first infusion pump type; and
        • a second reference to clinical care area data in the drug library database, the clinical care area data representing the first clinical care area;
      • generate customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;
      • generate generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules;
      • provide, to a first infusion pump of the plurality of infusion pumps, the customized drug library data, wherein the first infusion pump is associated with the first infusion pump type, and wherein a second infusion pump of the plurality of infusion pumps is not provided with the customized drug library data, the second infusion pump associated with a second infusion pump type; and
      • provide, to a connectivity adapter in communication with the first infusion pump and the second infusion pump, the generalized drug library data.


Clause 2: The system of Clause 1, wherein the first infusion pump is configured to replace, in memory of the first infusion pump, a prior version of customized drug library data with the customized drug library data.


Clause 3: The system of Clause 1, wherein the first infusion pump is configured to:

    • display infusion data comprising a medication name; and
    • transmit an infusion message to the connectivity adapter, wherein the infusion message comprises a medication identifier and does not comprise the medication name.


Clause 4: The system of Clause 3, wherein the connectivity adapter is configured to at least:

    • receive, from the first infusion pump, the infusion message; and
    • determine the medication name using the medication identifier and the generalized drug library data.


Clause 5: The system of Clause 4, wherein the connectivity adapter is further configured to at least:

    • receive, from the second infusion pump, a second infusion message comprising a second mediation identifier; and
    • determine a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump.


Clause 6: The system of Clause 1, wherein:

    • an administration rule of the subset of administration rules is associated with a medication of the subset of medications;
    • the administration rule is associated with a first upper dosing limit;
    • the first clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
    • the second upper dosing limit overrides the first upper dosing limit during administration of the medication by the first infusion pump.


Clause 7: The system of Clause 1, wherein:

    • an administration rule of the subset of administration rules is associated with a medication of the subset of medications;
    • the administration rule is associated with a first upper dosing limit;
    • the first clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
    • the first upper dosing limit is implemented during administration of the medication by the first infusion pump.


Clause 8: The system of Clause 1, wherein the drug library manager is further configured to at least:

    • receive, from the user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
    • store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.


Clause 9: The system of Clause 1, wherein the connectivity adapter is configured to at least:

    • receive, from the first infusion pump, an infusion message associated with a prior version of customized drug library data;
    • obtain a prior version of generalized drug library data that corresponds to the prior version of customized drug library data; and
    • process the infusion message using the prior version of generalized drug library data.


Clause 10: The system of Clause 1, wherein the drug library manager is further configured to at least:

    • store status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
    • receive, from the user device, input indicating a change in status of the worksheet data, wherein the customized drug library data and generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.


Clause 11: The system of Clause 1, further comprising a drug library archive, wherein the drug library manager is further configured to provide the generalized drug library data to the drug library archive, and wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries.


Clause 12: The system of Clause 11, wherein the drug library manager is further configured to:

    • compare the generalized drug library data to one of: second generalized drug library data or second worksheet data; and
    • generate user interface data for displaying a difference based on comparing the generalized drug library data.


Clause 13: A computer-implemented method comprising:

    • under control of one or more computing devices configured with specific computer-executable instructions,
      • storing, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
        • a first reference to infusion pump data in the drug library database, the infusion pump data representing a first infusion pump type of a plurality of infusion pump types; and
        • a second reference to clinical care area data in the drug library database, the clinical care area data representing a first clinical care area of a plurality of clinical care areas;
      • generating customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;
      • generating generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules;
      • providing the customized drug library data to an infusion pump associated with the first infusion pump type; and
      • providing the generalized drug library data to a computing system in communication with the infusion pump.


Clause 14: The computer-implemented method of Clause 13, further comprising:

    • accessing archived generalized drug library data corresponding to a prior version of the worksheet data;
    • comparing the generalized drug library data to the archived generalized drug library data; and
    • presenting a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.


Clause 15: The computer-implemented method of Clause 13, further comprising:

    • receiving input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; and
    • storing, in the drug library database, administration rule data representing the selection, wherein the administration rule references medication data representing the medication.


Clause 16: The computer-implemented method of Clause 13, further comprising:

    • storing status data in connection with the worksheet data, wherein the status data indicates a status of the worksheet data; and
    • receiving input indicating a change in status of the worksheet data, wherein the customized drug library data and generalized drug library data are generated in response to receiving the input indicating the change in status of the worksheet data.


Clause 17: The computer-implemented method of Clause 13, further comprising providing the generalized drug library data to a drug library archive configured to store a plurality of versions generalized drug library data for each of a plurality of different drug libraries.


Clause 18: The computer-implemented method of Clause 13, wherein generating the generalized drug library data comprises formatting the generalized drug library data using JavaScript Object Notation.


Clause 19: A system comprising:

    • a computer-readable memory storing executable instructions; and
    • one or more processors in communication with the computer-readable memory, wherein the one or more processors are programmed by the executable instructions to at least:
      • store, in a drug library database, worksheet data representing a drug library, wherein the worksheet data comprises:
        • a first reference to infusion pump data in the drug library database, the infusion pump data representing a first infusion pump type of a plurality of infusion pump types; and
        • a second reference to clinical care area data in the drug library database, the clinical care area data representing a first clinical care area of a plurality of clinical care areas;
      • generate customized drug library data using the worksheet data, wherein the customized drug library data is formatted according to a pump-specific format associated with the first infusion pump type, wherein the customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;
      • generate generalized drug library data using the worksheet data, wherein the generalized drug library data represents the subset of medications and the subset of administration rules;
      • provide the customized drug library data to an infusion pump associated with the first infusion pump type; and
      • provide the generalized drug library data to a connectivity adapter in communication with the infusion pump.


Clause 20: The system of Clause 19, further comprising the connectivity adapter, wherein the connectivity adapter is configured to at least:

    • receive, from the infusion pump, a first infusion message comprising a medication identifier that corresponds to a medication infused by the infusion pump;
    • determine a medication name using the medication identifier and the generalized drug library data;
    • receive, from the infusion pump, a second infusion message associated with a prior version of customized drug library data;
    • obtain a prior version of generalized drug library data that corresponds to the prior version of customized drug library data; and
    • process the second infusion message using the prior version of generalized drug library data.


Clause 21: A system comprising:

    • computer-readable storage; and
    • one or more computer processors configured to at least:
      • receive customized drug library data formatted according to a pump-specific format associated with a first infusion pump type, wherein the customized drug library data represents a plurality of medications and a plurality of administration rules, and wherein individual administration rules of the plurality of administration rules are associated with individual medications of the plurality of medications;
      • receive generalized drug library data, wherein the generalized drug library data represents the plurality of medications and the plurality of administration rules;
      • send the customized drug library data to an infusion pump associated with the first infusion pump type;
      • store the generalized drug library data in the computer-readable storage, wherein a prior version of the generalized drug library data is stored in the computer-readable storage;
      • receive, from the infusion pump, a first infusion message comprising a first medication identifier that corresponds to a first medication infused by the infusion pump;
      • determine a first medication name using the first medication identifier and the generalized drug library data;
      • receive, from the infusion pump, a second infusion message associated with a prior version of customized drug library data, the second infusion message comprising a second medication identifier that corresponds to a second medication infused by the infusion pump; and
      • determine a second medication name using the second medication identifier and the prior version of generalized drug library data.


Clause 22: The system of Clause 21, further comprising the infusion pump, wherein the infusion pump is configured to replace, in memory of the infusion pump, a prior version of customized drug library data with the customized drug library data.


Clause 23: The system of Clause 22, wherein the infusion pump is configured to:

    • display infusion data comprising the first medication name; and
    • transmit the first infusion message to a connectivity adapter comprising the one or more processors, wherein the first infusion message comprises the first medication identifier and does not comprise the first medication name.


Clause 24: The system of Clause 22, wherein the infusion pump is configured to:

    • display infusion data comprising a clinical care area name; and
    • transmit the first infusion message to a connectivity adapter comprising the one or more processors, wherein the first infusion message comprises a clinical care area identifier and does not comprise the clinical care area name.


Clause 25: The system of Clause 21, wherein the one or more processors are further configured to at least:

    • receive, from a second infusion pump, a third infusion message comprising a third mediation identifier, wherein the second infusion pump is associated with a second infusion pump type; and
    • determine a third medication name using the third medication identifier and second generalized drug library data.


Clause 26: The system of Clause 21, wherein:

    • an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
    • the administration rule comprises a first upper dosing limit;
    • the clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
    • the second upper dosing limit overrides the first upper dosing limit during administration of the first medication by the infusion pump.


Clause 27: The system of Clause 21, wherein:

    • an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
    • the administration rule comprises a first upper dosing limit;
    • the clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
    • the first upper dosing limit is implemented during administration of the first medication by the infusion pump.


Clause 28: A computer-implemented method comprising:

    • under control of one or more computing devices configured with specific computer-executable instructions,
      • receiving customized drug library data formatted according to a pump-specific format associated with a first infusion pump type, wherein the customized drug library data represents a plurality of medications and a plurality of administration rules, and wherein individual administration rules of the plurality of administration rules are associated with individual medications of the plurality of medications;
      • receiving generalized drug library data, wherein the generalized drug library data represents the plurality of medications and the plurality of administration rules;
      • sending the customized drug library data to an infusion pump associated with the first infusion pump type;
      • storing the generalized drug library data in a computer-readable storage, wherein a prior version of the generalized drug library data is stored in the computer-readable storage;
      • receiving, from the infusion pump, a first infusion message comprising a first medication identifier that corresponds to a first medication infused by the infusion pump;
      • processing the first infusion message using the first medication identifier and the generalized drug library data;
      • receiving, from the infusion pump, a second infusion message associated with a prior version of customized drug library data, the second infusion message comprising a second medication identifier that corresponds to a second medication infused by the infusion pump; and
      • processing the second infusion message using the second medication identifier and the prior version of generalized drug library data.


Clause 29: The computer-implemented method of Clause 28, wherein processing the first infusion message comprises determining a first medication name using the first medication identifier and the generalized drug library data.


Clause 30: The computer-implemented method of Clause 28, wherein processing the second infusion message comprises determining a second medication name using the second medication identifier and the generalized drug library data.


Clause 31: The computer-implemented method of Clause 28, wherein sending the customized drug library data to the infusion pump cases the infusion pump to replace, in memory of the infusion pump, a prior version of customized drug library data with the customized drug library data.


Clause 32: The computer-implemented method of Clause 31, further comprising:

    • displaying, by the infusion pump, infusion data comprising the first medication name; and
    • generating, by the infusion pump, the first infusion message, wherein the first infusion message comprises the first medication identifier and does not comprise the first medication name.


Clause 33: The computer-implemented method of Clause 28, further comprising:

    • receiving, from a second infusion pump, a third infusion message comprising a third mediation identifier, wherein the second infusion pump is associated with a second infusion pump type; and
    • processing the third medication identifier and second generalized drug library data.


Clause 34: The computer-implemented method of Clause 28, wherein:

    • an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
    • the administration rule comprises a first upper dosing limit;
    • the clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
    • the second upper dosing limit overrides the first upper dosing limit during administration of the first medication by the infusion pump.


Clause 35: The computer-implemented method of Clause 28, wherein:

    • an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
    • the administration rule comprises a first upper dosing limit;
    • the clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
    • the first upper dosing limit is implemented during administration of the first medication by the infusion pump.


Clause 36: A non-transitory computer storage medium that stores an executable component that directs a computing system to perform a process comprising:

    • receiving customized drug library data formatted according to a pump-specific format associated with a first infusion pump type, wherein the customized drug library data represents a plurality of medications and a plurality of administration rules, and wherein individual administration rules of the plurality of administration rules are associated with individual medications of the plurality of medications;
    • receiving generalized drug library data, wherein the generalized drug library data represents the plurality of medications and the plurality of administration rules;
    • sending the customized drug library data to an infusion pump associated with the first infusion pump type;
    • storing the generalized drug library data in a computer-readable storage, wherein a prior version of the generalized drug library data is stored in the computer-readable storage;
    • receiving, from the infusion pump, a first infusion message comprising a first medication identifier that corresponds to a first medication infused by the infusion pump;
    • processing the first infusion message using the first medication identifier and the generalized drug library data;
    • receiving, from the infusion pump, a second infusion message associated with a prior version of customized drug library data, the second infusion message comprising a second medication identifier that corresponds to a second medication infused by the infusion pump; and
    • processing the second infusion message using the second medication identifier and the prior version of generalized drug library data.


Clause 37: The non-transitory computer storage medium of Clause 36, wherein processing the first infusion message comprises determining a first medication name using the first medication identifier and the generalized drug library data, and wherein processing the second infusion message comprises determining a second medication name using the second medication identifier and the generalized drug library data.


Clause 38: The non-transitory computer storage medium of Clause 36, the process further comprising:

    • receiving, from a second infusion pump, a third infusion message comprising a third mediation identifier, wherein the second infusion pump is associated with a second infusion pump type; and
    • processing the third medication identifier and second generalized drug library data.


Clause 39: The non-transitory computer storage medium of Clause 36, wherein:

    • an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
    • the administration rule comprises a first upper dosing limit; the clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; and
    • the second upper dosing limit overrides the first upper dosing limit during administration of the first medication by the infusion pump.


Clause 40: The non-transitory computer storage medium of Clause 36, wherein:

    • an administration rule of the plurality of administration rules is associated with the first medication and a clinical care area of a plurality of clinical care areas;
    • the administration rule comprises a first upper dosing limit;
    • the clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; and
    • the first upper dosing limit is implemented during administration of the first medication by the infusion pump.


Other Considerations


It is to be understood that not necessarily all objects or advantages may be achieved in accordance with any particular embodiment described herein. Thus, for example, those skilled in the art will recognize that certain embodiments may be configured to operate in a manner that achieves or optimizes one advantage or group of advantages as taught herein without necessarily achieving other objects or advantages as may be taught or suggested herein.


Many other variations than those described herein will be apparent from this disclosure. For example, depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out altogether (e.g., not all described acts or events are necessary for the practice of the algorithms). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially. In addition, different tasks or processes can be performed by different machines and/or computing systems that can function together.


The various illustrative logical blocks, modules, and algorithm elements described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and elements have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.


The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can include electrical circuitry configured to process computer-executable instructions. In another embodiment, a processor includes an FPGA or other programmable device that performs logic operations without processing computer-executable instructions. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. Although described herein primarily with respect to digital technology, a processor may also include primarily analog components. For example, some or all of the signal processing algorithms described herein may be implemented in analog circuitry or mixed analog and digital circuitry. A computing environment can include any type of computer system, including, but not limited to, a computer system based on a microprocessor, a mainframe computer, a digital signal processor, a portable computing device, a device controller, or a computational engine within an appliance, to name a few.


The elements of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module stored in one or more memory devices and executed by one or more processors, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD ROM, or any other form of non-transitory computer-readable storage medium, media, or physical computer storage known in the art. An example storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The storage medium can be volatile or nonvolatile. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.


Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or states. Thus, such conditional language is not generally intended to imply that features, elements and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Further, the term “each,” as used herein, in addition to having its ordinary meaning, can mean any subset of a set of elements to which the term “each” is applied.


Disjunctive language such as the phrase “at least one of X, Y, or Z,” unless specifically stated otherwise, is otherwise understood with the context as used in general to present that an item, term, etc., may be either X, Y, or Z, or any combination thereof (e.g., X, Y, and/or Z). Thus, such disjunctive language is not generally intended to, and should not, imply that certain embodiments require at least one of X, at least one of Y, or at least one of Z to each be present.


Unless otherwise explicitly stated, articles such as “a”, “an”, or “the” should generally be interpreted to include one or more described items. Accordingly, phrases such as “a device configured to” are intended to include one or more recited devices. Such one or more recited devices can also be collectively configured to carry out the stated recitations. For example, “a processor configured to carry out recitations A, B, and C” can include a first processor configured to carry out recitation A working in conjunction with a second processor configured to carry out recitations B and C.


While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments described herein can be implemented within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. All such modifications and variations are intended to be included herein within the scope of this disclosure. Further, additional embodiments created by combining any two or more features or techniques of one or more embodiments described herein are also intended to be included herein within the scope of this disclosure.

Claims
  • 1. A system configured to manage a drug library within a clinical environment, the system comprising: a plurality of infusion pumps configured to deliver medication to one or more patients, each respective infusion pump of the plurality of infusion pumps comprising a memory configured to store drug library data;a connectivity adapter comprising one or more computer processors and memory storing generalized drug library data in a pump-independent format, the connectivity adapter configured to process messages generated by individual infusion pumps of the plurality of infusion pumps, wherein each respective message is generated using customized drug library data in a pump-specific format; anda drug library manager comprising one or more computer processors and memory;wherein the drug library manager is configured to: store, in a drug library database, a plurality of sets of worksheet data, wherein a first set of worksheet data comprises a first reference to first infusion pump data in the drug library database, the first infusion pump data representing a first infusion pump type of a plurality of infusion pump types; andwherein a second set of worksheet data comprises a second reference to second infusion pump data in the drug library database, the second infusion pump data representing a second infusion pump type of the plurality of infusion pump types;generate first customized drug library data using the first set of worksheet data, wherein the first customized drug library data is formatted according to a first pump-specific format associated with the first infusion pump type, wherein the first customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein individual administration rules of the subset of administration rules are associated with individual medications of the subset of medications;generate second customized drug library data using the second set of worksheet data, wherein the second customized drug library data is formatted according to a second pump-specific format associated with the second infusion pump type, wherein the second pump-specific format is different than the first pump-specific format, and wherein the second customized drug library data represents the subset of medications and the subset of administration rules;generate the generalized drug library data representing the subset of medications and the subset of administration rules;provide, to a first infusion pump of the plurality of infusion pumps, the first customized drug library data, wherein the first infusion pump is associated with the first infusion pump type, and wherein a second infusion pump of the plurality of infusion pumps is not provided with the first customized drug library data, the second infusion pump associated with a second infusion pump type;provide, to the second infusion pump, the second customized drug library data, wherein the first infusion pump is not provided with the second customized drug library data; andprovide, to a connectivity adapter in communication with the first infusion pump and the second infusion pump, the generalized drug library data; andwherein connectivity adapter is further configured to: receive, from the first infusion pump, an infusion message to be processed by the connectivity adapter;determine that the infusion message is associated with a prior version of first customized drug library data based at least partly on data included in the infusion message being unresolvable using the generalized drug library data;convert the infusion message to a standardized message using a prior version of generalized drug library data that corresponds to the prior version of first customized drug library data; andmerge data from the standardized message with data representing a current state of the first infusion pump.
  • 2. The system of claim 1, wherein the first infusion pump is configured to replace, in memory of the first infusion pump, the prior version of customized drug library data with the first customized drug library data.
  • 3. The system of claim 1, wherein the first infusion pump is configured to: display infusion data comprising a medication name; andtransmit a second infusion message to the connectivity adapter, wherein the second infusion message comprises a medication identifier and does not comprise the medication name.
  • 4. The system of claim 3, wherein the connectivity adapter is configured to at least: receive, from the first infusion pump, the second infusion message; anddetermine the medication name using the medication identifier and the generalized drug library data.
  • 5. The system of claim 1, wherein the connectivity adapter is further configured to at least: receive, from the second infusion pump, a second infusion message comprising a second medication identifier; anddetermine a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump.
  • 6. The system of claim 1, wherein: an administration rule of the subset of administration rules is associated with a medication of the subset of medications;the administration rule is associated with a first upper dosing limit;a first clinical care area is associated with a second upper dosing limit that is lower than the first upper dosing limit; andthe second upper dosing limit overrides the first upper dosing limit during administration of the medication by the first infusion pump.
  • 7. The system of claim 1, wherein: an administration rule of the subset of administration rules is associated with a medication of the subset of medications;the administration rule is associated with a first upper dosing limit;a first clinical care area is associated with a second upper dosing limit that is higher than the first upper dosing limit; andthe first upper dosing limit is implemented during administration of the medication by the first infusion pump.
  • 8. The system of claim 1, wherein the drug library manager is further configured to at least: receive, from a user device, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; andstore, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.
  • 9. The system of claim 1, wherein the drug library manager is further configured to at least: store status data in connection with the first set of worksheet data, wherein the status data indicates a status of the first set of worksheet data; andreceive, from a user device, input indicating a change in status of the first set of worksheet data, wherein the first customized drug library data and generalized drug library data are generated in response to receiving the input indicating the change in status of the first set worksheet data.
  • 10. The system of claim 1, further comprising a drug library archive, wherein the drug library manager is further configured to provide the generalized drug library data to the drug library archive, and wherein the drug library archive is configured to store a plurality of versions of generalized drug library data for each of a plurality of different drug libraries.
  • 11. The system of claim 10, wherein the drug library manager is further configured to: compare the generalized drug library data to one of: second generalized drug library data or second worksheet data; andgenerate user interface data for displaying a difference based on comparing the generalized drug library data.
  • 12. A computer-implemented method comprising: storing, by a drug library manager comprising one or more computing devices, a plurality of sets of worksheet data in a drug library database, wherein a first set of worksheet data comprises a first reference to first infusion pump data in the drug library database, the first infusion pump data representing a first infusion pump type of a plurality of infusion pump types; andwherein a second set of worksheet data comprises a second reference to second infusion pump data in the drug library database, the second infusion pump data representing a second infusion pump type of the plurality of infusion pump types;generating, by the drug library manager, first customized drug library data using the first set of worksheet data, wherein the first customized drug library data is formatted according to a first pump-specific format associated with the first infusion pump type, wherein the first customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein the first customized drug library data is provided to a first infusion pump associated with the first infusion pump type;generating, by the drug library manager, second customized drug library data using the second set of worksheet data, wherein the second customized drug library data is formatted according to a second pump-specific format associated with the second infusion pump type, wherein the second pump-specific format is different than the first pump-specific format, and wherein the second customized drug library data is provided to a second infusion pump associated with the second infusion pump type;generating, by the drug library manager, generalized drug library data representing the subset of medications and the subset of administration rules, wherein the generalized drug library data is formatted in a pump-independent format, and wherein the generalized drug library data is provided to a connectivity adapter comprising one or more computing devices in communication with the first and second infusion pumps;receiving, by the connectivity adapter from the first infusion pump, an infusion message to be processed by the connectivity adapter;determining, by the connectivity adapter, that the infusion message is associated with a prior version of first customized library data based at least partly on data included in the infusion message being unresolvable using the generalized drug library data;transforming, by the connectivity adapter, the infusion message to a standardized message using a prior version of generalized drug library data that corresponds to the prior version of first customized drug library data; andsending, by the connectivity adapter, the standardized message to a server.
  • 13. The computer-implemented method of claim 12, further comprising: accessing, by the drug library manager, archived generalized drug library data corresponding to a prior version of the first set of worksheet data;comparing, by the drug library manager, the generalized drug library data to the archived generalized drug library data; andpresenting, by the drug library manager, a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.
  • 14. The computer-implemented method of claim 12, further comprising: receiving, by the drug library manager, input associated with a medication and representing selection of at least one of: a lower hard dosing limit, a lower soft dosing limit, an upper soft dosing limit, or an upper hard dosing limit; andstoring, by the drug library manager, administration rule data representing the selection in the drug library database, wherein the administration rule data references medication data representing the medication.
  • 15. The computer-implemented method of claim 12, further comprising: storing, by the drug library manager, status data in connection with the first set of worksheet data, wherein the status data indicates a status of the first set of worksheet data; andreceiving, by the drug library manager, input indicating a change in status of the first set of worksheet data, wherein the first customized drug library data and generalized drug library data are generated in response to receiving the input indicating the change in status of the first set of worksheet data.
  • 16. The computer-implemented method of claim 12, further comprising providing, by the drug library manager, the generalized drug library data to a drug library archive configured to store a plurality of versions generalized drug library data for each of a plurality of different drug libraries.
  • 17. A system comprising: a drug library manager comprising one or more computing device; anda connectivity adapter comprising one or more computing devices,wherein the drug library manager is configured to at least: store, in a drug library database, a plurality of sets of worksheet data, wherein a first set of worksheet data comprises a first reference to first infusion pump data in the drug library database, the first infusion pump data representing a first infusion pump type of a plurality of infusion pump types; andwherein a second set of worksheet data comprises a second reference to second infusion pump data in the drug library database, the second infusion pump data representing a second infusion pump type of the plurality of infusion pump types;generate first customized drug library data using the first set of worksheet data, wherein the first customized drug library data is formatted according to a first pump-specific format associated with the first infusion pump type, wherein the first customized drug library data represents a subset of medications in the drug library database and a subset of administration rules in the drug library database, and wherein the first customized drug library data is provided to a first infusion pump associated with the first infusion pump type;generate second customized drug library data using the second set of worksheet data, wherein the second customized drug library data is formatted according to a second pump-specific format associated with the second infusion pump type, wherein the second pump-specific format is different than the first pump-specific format, and wherein the second customized drug library data is provided to a second infusion pump associated with the second infusion pump type;generate generalized drug library data representing the subset of medications and the subset of administration rules, wherein the generalized drug library data is formatted in a pump-independent format, and wherein the generalized drug library data is provided to the connectivity adapter, andwherein the connectivity adapter is configured to at least: receive, from the first infusion pump, an infusion message to be processed by the connectivity adapter;determine that the infusion message is associated with a prior version of first customized library data based at least partly on data included in the infusion message being unresolvable using the generalized drug library data;transform the infusion message to a standardized message using a prior version of generalized drug library data that corresponds to the prior version of first customized drug library data; andsend the standardized message to a server.
  • 18. The system of claim 17, further comprising the connectivity adapter, wherein the connectivity adapter is configured to at least: receive, from the first infusion pump, a first infusion message comprising a medication identifier that corresponds to a medication infused by the first infusion pump;determine a medication name using the medication identifier and the generalized drug library data;receive, from the first infusion pump, a second infusion message associated with a prior version of first customized drug library data;obtain a prior version of generalized drug library data that corresponds to the prior version of first customized drug library data; andprocess the second infusion message using the prior version of generalized drug library data.
  • 19. The system of claim 1, wherein the drug library manager is further configured to at least: receive, from a user device, first input data representing one or more medications;receive, from the user device, second input data representing one or more administration rules, wherein the second input data comprises: data representing a medication of the one or more medications;data representing an infusion pump type of a plurality of infusion pump types; anddata representing one or more medication administration parameters;receive, from the user device, third input data representing one or more clinical care areas, wherein the third input data comprises: data representing one or more clinical care area settings; anddata representing an association of a clinical care area with zero or more administration rules; andreceive, from the user device, fourth input data representing selection of a first clinical care area of the one or more clinical care areas.
  • 20. The system of claim 17, wherein the drug library manager is further configured to at least merge data from the standardized message with data representing a current state of the first infusion pump.
CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of International Patent Application No. PCT/US2019/041715, filed on Jul. 12, 2019 and titled “Drug Library Management System,” which claims priority to U.S. Provisional Patent Application No. 62/703,772, filed on Jul. 26, 2018 and titled “Drug Library Management System,” the contents of both of which are incorporated by reference herein.

US Referenced Citations (1173)
Number Name Date Kind
4024864 Davies et al. May 1977 A
4055175 Clemens et al. Oct 1977 A
4151845 Clemens May 1979 A
4213454 Shim Jul 1980 A
4240438 Updike et al. Dec 1980 A
4280494 Cosgrove et al. Jul 1981 A
4308866 Jeliffe Jan 1982 A
4370983 Lichtenstein et al. Feb 1983 A
4373527 Fischell Feb 1983 A
4392849 Petre et al. Jul 1983 A
4395259 Prestele et al. Jul 1983 A
4457751 Rodler Jul 1984 A
4464170 Clemens Aug 1984 A
4469481 Kobayashi Sep 1984 A
4475901 Kraegen et al. Oct 1984 A
4494950 Fischell Jan 1985 A
4498843 Schneider et al. Feb 1985 A
4515584 Abe et al. May 1985 A
4526568 Clemens et al. Jul 1985 A
4529401 Leslie et al. Jul 1985 A
4543955 Schroeppel Oct 1985 A
4551133 Zegers de Beyl et al. Nov 1985 A
4553958 LeCocq Nov 1985 A
4559037 Franetzki et al. Dec 1985 A
4613937 Batty Sep 1986 A
4624661 Arimond Nov 1986 A
4633878 Bombardieri Jan 1987 A
4634426 kamen Jan 1987 A
4634427 Hannula et al. Jan 1987 A
4674652 Aten et al. Jun 1987 A
4676776 Howson et al. Jun 1987 A
4679562 Luksha Jul 1987 A
4685903 Cable et al. Aug 1987 A
4695954 Rose Sep 1987 A
4696671 Epstein et al. Sep 1987 A
4714462 DiDomenico Dec 1987 A
4722734 Kolin Feb 1988 A
4731051 Fischell Mar 1988 A
4741732 Crankshaw et al. May 1988 A
4756706 Kerns et al. Jul 1988 A
4776842 Franetzki et al. Oct 1988 A
4785969 McLaughlin Nov 1988 A
4803625 Fu et al. Feb 1989 A
4835372 Gombrich et al. May 1989 A
4838275 Lee Jun 1989 A
4838856 Mulreany et al. Jun 1989 A
4838857 Strowe et al. Jun 1989 A
4854324 Hirschman et al. Aug 1989 A
4857716 Gombrich et al. Aug 1989 A
4858154 Anderson et al. Aug 1989 A
4898578 Rubalcaba, Jr. Feb 1990 A
4908017 Howson et al. Mar 1990 A
4933873 Kaufman et al. Jun 1990 A
4943279 Samiotes et al. Jul 1990 A
4946439 Eggers Aug 1990 A
4953745 Rowlett Sep 1990 A
4978335 Arthur, III Dec 1990 A
5000739 Kulisz et al. Mar 1991 A
5010473 Jacobs Apr 1991 A
5014698 Cohen May 1991 A
5016172 Dessertine May 1991 A
5026084 Paisfield Jun 1991 A
5034004 Crankshaw Jul 1991 A
5041086 Koenig et al. Aug 1991 A
5058161 Weiss Oct 1991 A
5078683 Sancoff et al. Jan 1992 A
5084828 Kaufman et al. Jan 1992 A
5088981 Howson et al. Feb 1992 A
5097505 Weiss Mar 1992 A
5100380 Epstein et al. Mar 1992 A
5102392 Sakai et al. Apr 1992 A
5104374 Bishko et al. Apr 1992 A
5109850 Blanco et al. May 1992 A
5131816 Brown Jul 1992 A
5142484 Kaufman et al. Aug 1992 A
5153827 Coutre et al. Oct 1992 A
5157640 Backner Oct 1992 A
5161222 Montejo et al. Nov 1992 A
5177993 Beckman et al. Jan 1993 A
5181910 Scanlon Jan 1993 A
5190522 Wocicki et al. Mar 1993 A
5199439 Zimmerman et al. Apr 1993 A
5200891 Kehr et al. Apr 1993 A
5216597 Beckers Jun 1993 A
5221268 Barton et al. Jun 1993 A
5230061 Welch Jul 1993 A
5243982 Möstl et al. Sep 1993 A
5244463 Cordner, Jr. et al. Sep 1993 A
5249260 Nigawara et al. Sep 1993 A
5256156 Kern et al. Oct 1993 A
5256157 Samiotes et al. Oct 1993 A
5261702 Mayfield Nov 1993 A
5317506 Coutre et al. May 1994 A
5319355 Russek Jun 1994 A
5319363 Welch et al. Jun 1994 A
5330634 Wong et al. Jul 1994 A
5338157 Blomquist Aug 1994 A
5341476 Lowell Aug 1994 A
5364346 Schrezenmeir Nov 1994 A
5366346 Danby Nov 1994 A
5368562 Blomquist et al. Nov 1994 A
5373454 Kanda et al. Dec 1994 A
5376070 Purvis et al. Dec 1994 A
5378231 Johnson et al. Jan 1995 A
5389071 Kawahara et al. Feb 1995 A
5389078 Zalesky et al. Feb 1995 A
5417222 Dempsey et al. May 1995 A
5423748 Uhala Jun 1995 A
5429602 Hauser Jul 1995 A
5431627 Pastrone et al. Jul 1995 A
5432777 Le Boudec et al. Jul 1995 A
5445621 Poli et al. Aug 1995 A
5447164 Shaya et al. Sep 1995 A
5455851 Chaco et al. Oct 1995 A
5461365 Schlager et al. Oct 1995 A
5464392 Epstein et al. Nov 1995 A
5465082 Chaco Nov 1995 A
5485408 Blomquist Jan 1996 A
5486286 Peterson et al. Jan 1996 A
5493430 Lu et al. Feb 1996 A
5496273 Pastrone et al. Mar 1996 A
5505828 Wong et al. Apr 1996 A
5507288 Bocker et al. Apr 1996 A
5507786 Morgan et al. Apr 1996 A
5508499 Ferrario Apr 1996 A
5515713 Saugues et al. May 1996 A
5520637 Pager et al. May 1996 A
5522798 Johnson et al. Jun 1996 A
5547470 Johnson et al. Aug 1996 A
5554013 Owens et al. Sep 1996 A
5562615 Nassif Oct 1996 A
5577169 Prezioso Nov 1996 A
5582323 Kurtenbach Dec 1996 A
5582593 Hultman Dec 1996 A
5594786 Chaco et al. Jan 1997 A
5598519 Narayanan Jan 1997 A
5620608 Rosa et al. Apr 1997 A
5630710 Tune et al. May 1997 A
5636044 Yuan et al. Jun 1997 A
5643212 Coutre et al. Jul 1997 A
5651775 Walker et al. Jul 1997 A
5658131 Aoki et al. Aug 1997 A
5658250 Blomquist et al. Aug 1997 A
5665065 Colman et al. Sep 1997 A
5669877 Blomquist Sep 1997 A
5672154 Sillén et al. Sep 1997 A
5681285 Ford et al. Oct 1997 A
5685844 Marttila Nov 1997 A
5687717 Halpern et al. Nov 1997 A
5689229 Chaco et al. Nov 1997 A
5697899 Hillman et al. Dec 1997 A
5699509 Gary et al. Dec 1997 A
5713350 Yokota et al. Feb 1998 A
5713856 Eggers et al. Feb 1998 A
5718562 Lawless et al. Feb 1998 A
5719761 Gatti et al. Feb 1998 A
5733259 Valcke et al. Mar 1998 A
5738102 Lemelson Apr 1998 A
5744027 Connell et al. Apr 1998 A
5752621 Passamante May 1998 A
5754111 Garcia May 1998 A
5764034 Bowman et al. Jun 1998 A
5764159 Neftel et al. Jun 1998 A
5772635 Dastur et al. Jun 1998 A
5774865 Glynn Jun 1998 A
5778256 Darbee Jul 1998 A
5778345 McCartney Jul 1998 A
5781442 Engleson et al. Jul 1998 A
5782805 Meinzer et al. Jul 1998 A
5788669 Peterson Aug 1998 A
5797515 Lift et al. Aug 1998 A
5800387 Duffy et al. Sep 1998 A
5814015 Gargano et al. Sep 1998 A
5822544 Chaco et al. Oct 1998 A
5822715 Worthington et al. Oct 1998 A
5827179 Lichter et al. Oct 1998 A
5832448 Brown Nov 1998 A
5836910 Duffy et al. Nov 1998 A
5850344 Conkright Dec 1998 A
5867821 Ballantyne et al. Feb 1999 A
5870733 Bass et al. Feb 1999 A
5871465 Vasko Feb 1999 A
5873731 Predergast Feb 1999 A
5885245 Lynch et al. Mar 1999 A
5897493 Brown Apr 1999 A
5897498 Canfield, II et al. Apr 1999 A
5910252 Truitt et al. Jun 1999 A
5912818 McGrady et al. Jun 1999 A
5915240 Karpf Jun 1999 A
5920054 Uber, III Jul 1999 A
5920263 Huttenhoff et al. Jul 1999 A
5924074 Evans Jul 1999 A
5931764 Freeman et al. Aug 1999 A
5935099 Peterson et al. Aug 1999 A
5935106 Olsen Aug 1999 A
5941846 Duffy et al. Aug 1999 A
5956501 Brown Sep 1999 A
5957885 Bollish et al. Sep 1999 A
5960085 de la Huerga Sep 1999 A
5961448 Swenson et al. Oct 1999 A
5967559 Abramowitz Oct 1999 A
5971594 Sahai et al. Oct 1999 A
5975081 Hood et al. Nov 1999 A
5990838 Burns et al. Nov 1999 A
5997476 Brown Dec 1999 A
6000828 Leet Dec 1999 A
6003006 Colella et al. Dec 1999 A
6012034 Hamparian et al. Jan 2000 A
6017318 Gauthier et al. Jan 2000 A
6021392 Lester et al. Feb 2000 A
6024539 Blomquist Feb 2000 A
6024699 Surwit et al. Feb 2000 A
6032155 de la Huerga Feb 2000 A
6032676 Moore Mar 2000 A
6039251 Holowko et al. Mar 2000 A
6070761 Bloom et al. Jun 2000 A
6073106 Rozen et al. Jun 2000 A
6104295 Gaisser et al. Aug 2000 A
6112182 Akers et al. Aug 2000 A
6112323 Meizlik et al. Aug 2000 A
RE36871 Epstein et al. Sep 2000 E
6115390 Chuah Sep 2000 A
6122536 Sun et al. Sep 2000 A
6126637 Kriesel et al. Oct 2000 A
6135949 Russo et al. Oct 2000 A
6150942 O'Brien Nov 2000 A
6151643 Cheng et al. Nov 2000 A
6157914 Seto et al. Dec 2000 A
6159147 Lichter et al. Dec 2000 A
6167567 Chiles et al. Dec 2000 A
6182667 Hanks et al. Feb 2001 B1
6189105 Lopes Feb 2001 B1
6195589 Ketcham Feb 2001 B1
6208974 Campbell et al. Mar 2001 B1
6222323 Yamashita et al. Apr 2001 B1
6223440 Rashman May 2001 B1
6226277 Chuah May 2001 B1
6227371 Song May 2001 B1
6234176 Domae et al. May 2001 B1
6241704 Peterson et al. Jun 2001 B1
6248067 Causey, III et al. Jun 2001 B1
6249705 Snell Jun 2001 B1
6257265 Brunner et al. Jul 2001 B1
6259355 Chaco et al. Jul 2001 B1
6269340 Ford et al. Jul 2001 B1
6270455 Brown Aug 2001 B1
6271813 Palalau Aug 2001 B1
6277072 Bardy Aug 2001 B1
6280380 Bardy Aug 2001 B1
6283761 Joao Sep 2001 B1
6285665 Chuah Sep 2001 B1
6292860 Cochcroft, Jr. Sep 2001 B1
6312378 Bardy Nov 2001 B1
6327254 Chuah Dec 2001 B1
6330008 Razdow et al. Dec 2001 B1
6339718 Zatezalo et al. Jan 2002 B1
6346886 de la Huerga Feb 2002 B1
6363282 Nichols et al. Mar 2002 B1
6371719 Hildebrandt Apr 2002 B1
6377548 Chuah Apr 2002 B1
6388951 Matsumoto et al. May 2002 B1
6406426 Reuss et al. Jun 2002 B1
6408330 de la Huerga Jun 2002 B1
6418334 Unger et al. Jul 2002 B1
6427088 Bowman et al. Jul 2002 B1
6428483 Carlebach Aug 2002 B1
6442432 Lee Aug 2002 B2
6469991 Chuah Oct 2002 B1
6475180 Peterson et al. Nov 2002 B2
6482158 Mault Nov 2002 B2
6485418 Yasushi et al. Nov 2002 B2
6494694 Lawless et al. Dec 2002 B2
6494831 Koritzinsky Dec 2002 B1
6497680 Holst et al. Dec 2002 B1
6514460 Fendrock Feb 2003 B1
6517482 Eiden et al. Feb 2003 B1
6519569 White et al. Feb 2003 B1
6520930 Critchlow et al. Feb 2003 B2
6540672 Simonsen et al. Apr 2003 B1
6542902 Dulong et al. Apr 2003 B2
6544212 Galley et al. Apr 2003 B2
6544228 Heitmeier Apr 2003 B1
6546350 Hartmann et al. Apr 2003 B1
6551276 Mann et al. Apr 2003 B1
6554798 Mann et al. Apr 2003 B1
6558320 Causey et al. May 2003 B1
6558351 Steil et al. May 2003 B1
6565509 Say et al. May 2003 B1
6567416 Chuah May 2003 B1
6571294 Simmon et al. May 2003 B2
6572542 Houben et al. Jun 2003 B1
6572545 Knobbe et al. Jun 2003 B2
6578002 Derzay et al. Jun 2003 B1
6581117 Klein et al. Jun 2003 B1
6587034 Heiman et al. Jul 2003 B1
6589229 Connelly et al. Jul 2003 B1
6599281 Struys et al. Jul 2003 B1
6602191 Quy Aug 2003 B2
6605072 Struys et al. Aug 2003 B2
6628809 Rowe et al. Sep 2003 B1
6631353 Davis et al. Oct 2003 B1
6640246 Gardy, Jr. et al. Oct 2003 B1
6641533 Causey, III et al. Nov 2003 B2
6647299 Bourget Nov 2003 B2
6652455 Kocher Nov 2003 B1
6653937 Nelson et al. Nov 2003 B2
6659947 Carter et al. Dec 2003 B1
6669630 Joliat et al. Dec 2003 B1
6671563 Engleson et al. Dec 2003 B1
6673033 Sciulli et al. Jan 2004 B1
6674403 Gray et al. Jan 2004 B2
6681003 Linder et al. Jan 2004 B2
6689091 Bui et al. Feb 2004 B2
6692241 Watanabe et al. Feb 2004 B2
6694191 Starkweather et al. Feb 2004 B2
6694334 DuLong et al. Feb 2004 B2
6721286 Williams et al. Apr 2004 B1
6721582 Trepagnier et al. Apr 2004 B2
6725200 Rost Apr 2004 B1
6731989 Engleson et al. May 2004 B2
6740072 Starkweather et al. May 2004 B2
6751651 Crockett Jun 2004 B2
6752787 Causey, III et al. Jun 2004 B1
6753830 Gelbman Jun 2004 B2
6758810 Lebel et al. Jul 2004 B2
6773396 Flach et al. Aug 2004 B2
6774786 Havekost et al. Aug 2004 B1
6775577 Cmkovich et al. Aug 2004 B2
6780156 Haueter et al. Aug 2004 B2
6790198 White et al. Sep 2004 B1
6796956 Hartlaub et al. Sep 2004 B2
6799149 Hartlaub Sep 2004 B2
6809653 Mann et al. Oct 2004 B1
6811534 Bowman, IV et al. Nov 2004 B2
6816605 Rowe et al. Nov 2004 B2
6839753 Biondi et al. Jan 2005 B2
6852104 Blomquist Feb 2005 B2
6859134 Heiman et al. Feb 2005 B1
6871211 Labounty et al. Mar 2005 B2
6873268 Lebel et al. Mar 2005 B2
6876303 Reeder et al. Apr 2005 B2
6885881 Leonhardt Apr 2005 B2
6891525 Ogoro May 2005 B2
6892278 Ebergen May 2005 B2
6899695 Herrera May 2005 B2
6915170 Engleson et al. Jul 2005 B2
6923763 Kovatchev et al. Aug 2005 B1
6924781 Gelbman Aug 2005 B1
6928338 Buchser et al. Aug 2005 B1
6928490 Bucholz et al. Aug 2005 B1
6936029 Mann et al. Aug 2005 B2
6945954 Hochman et al. Sep 2005 B2
6948492 Wemeling et al. Sep 2005 B2
6958677 Carter Oct 2005 B1
6958691 Anderson et al. Oct 2005 B1
6958705 Lebel et al. Oct 2005 B2
6961448 Nichols et al. Nov 2005 B2
6969352 Chiang et al. Nov 2005 B2
6969865 Duchon et al. Nov 2005 B2
6974437 Lebel et al. Dec 2005 B2
6979326 Mann et al. Dec 2005 B2
6980958 Surwit et al. Dec 2005 B1
6985870 Martucci et al. Jan 2006 B2
6986347 Hickle Jan 2006 B2
6997880 Carlebach et al. Feb 2006 B2
6997920 Mann et al. Feb 2006 B2
6998984 Zittrain Feb 2006 B1
7017293 Riley Mar 2006 B2
7025743 Mann et al. Apr 2006 B2
7029455 Flaherty Apr 2006 B2
7038584 Carter May 2006 B2
7060031 Webb et al. Jun 2006 B2
7060059 Keith et al. Jun 2006 B2
7069552 Lindberg et al. Jun 2006 B2
7072725 Bristol et al. Jul 2006 B2
7079035 Bock et al. Jul 2006 B2
7092943 Roese et al. Aug 2006 B2
7096072 Engleson et al. Aug 2006 B2
7099809 Dori Aug 2006 B2
7103419 Engleson et al. Sep 2006 B2
7103578 Beck et al. Sep 2006 B2
7107106 Engleson et al. Sep 2006 B2
7108680 Rohr et al. Sep 2006 B2
7109878 Mann et al. Sep 2006 B2
7114002 Okumura et al. Sep 2006 B1
7117041 Engleson et al. Oct 2006 B2
7136645 Hanson et al. Nov 2006 B2
7137964 Flaherty Nov 2006 B2
7142190 Martinez Nov 2006 B2
7150741 Erickson et al. Dec 2006 B2
7153289 Vasko Dec 2006 B2
7154397 Zerhusen et al. Dec 2006 B2
7156807 Carter et al. Jan 2007 B2
7158030 Chung Jan 2007 B2
7161484 Tsoukalis et al. Jan 2007 B2
7167755 Seeberger et al. Jan 2007 B2
7167920 Traversal Jan 2007 B2
7171277 Engleson et al. Jan 2007 B2
7171492 Borella et al. Jan 2007 B1
7181493 English et al. Feb 2007 B2
7185288 McKeever Feb 2007 B2
7193514 Ritson Mar 2007 B2
7197025 Chuah Mar 2007 B2
7201734 Hickle Apr 2007 B2
7204823 Estes et al. Apr 2007 B2
7213009 Pestotnik May 2007 B2
7216802 de la Huerga May 2007 B1
7220240 Struys et al. May 2007 B2
7224979 Singhal et al. May 2007 B2
7229430 Hickle et al. Jun 2007 B2
7230529 Ketcherside Jun 2007 B2
7236936 White et al. Jun 2007 B2
7238164 Childers et al. Jul 2007 B2
7247154 Hickle Jul 2007 B2
7248239 Dowling Jul 2007 B2
7250856 Havekost et al. Jul 2007 B2
7255683 Vanderveen et al. Aug 2007 B2
7256888 Staehr et al. Aug 2007 B2
7258534 Fathallah et al. Aug 2007 B2
7263213 Rowe Aug 2007 B2
7267664 Rizzo Sep 2007 B2
7267665 Steil et al. Sep 2007 B2
7275156 Balfanz et al. Sep 2007 B2
7278983 Ireland et al. Oct 2007 B2
7289815 Gfeller et al. Oct 2007 B2
7289948 Mohri Oct 2007 B1
7293107 Hanson et al. Nov 2007 B1
7295119 Rappaport et al. Nov 2007 B2
7295556 Roese et al. Nov 2007 B2
7301451 Hastings Nov 2007 B2
7308300 Toews et al. Dec 2007 B2
7315825 Rosenfeld et al. Jan 2008 B2
7319386 Collins, Jr. et al. Jan 2008 B2
7324000 Zittrain et al. Jan 2008 B2
7327705 Fletcher et al. Feb 2008 B2
7343224 DiGianfilippo et al. Mar 2008 B2
7346025 Bryson Mar 2008 B2
7347836 Peterson et al. Mar 2008 B2
7354420 Steil et al. Apr 2008 B2
7369897 Boveja et al. May 2008 B2
7369948 Ferenczi et al. May 2008 B1
7383088 Spinelli et al. Jun 2008 B2
7384410 Eggers et al. Jun 2008 B2
7398183 Holland et al. Jul 2008 B2
7398279 Muno, Jr. Jul 2008 B2
7399277 Saidara et al. Jul 2008 B2
7402153 Steil et al. Jul 2008 B2
7420472 Tran Sep 2008 B2
7432807 Schmitt Oct 2008 B2
7447643 Olson Nov 2008 B1
7454314 Holland et al. Nov 2008 B2
7457804 Uber, III et al. Nov 2008 B2
7464040 Joao Dec 2008 B2
7471994 Ford et al. Dec 2008 B2
7483756 Engleson et al. Jan 2009 B2
7489808 Gerder Feb 2009 B2
7490021 Holland et al. Feb 2009 B2
7490048 Joao Feb 2009 B2
7491187 Van Den Berghe et al. Feb 2009 B2
7519905 Kougiouris et al. Apr 2009 B2
7523401 Aldridge Apr 2009 B1
7524304 Genosar Apr 2009 B2
7551078 Carlson Jun 2009 B2
7559321 Wermeling et al. Jul 2009 B2
7565197 Haulbrich et al. Jul 2009 B2
7572230 Neumann et al. Aug 2009 B2
7578802 Hickle Aug 2009 B2
7621009 Elhabashy Nov 2009 B2
D606533 De Jong et al. Dec 2009 S
7636718 Steen et al. Dec 2009 B1
7640172 Kuth Dec 2009 B2
7645258 White et al. Jan 2010 B2
7647237 Malave et al. Jan 2010 B2
7662124 Duchon et al. Feb 2010 B2
7668731 Martucci et al. Feb 2010 B2
7671733 McNeal et al. Mar 2010 B2
7678071 Lebel et al. Mar 2010 B2
7687678 Jacobs Mar 2010 B2
7697994 VanDanacker et al. Apr 2010 B2
7698239 Lieuallen Apr 2010 B2
7705727 Pestotnik Apr 2010 B2
7724147 Brown et al. May 2010 B2
7739126 Cave Jun 2010 B1
7746218 Collins, Jr. Jun 2010 B2
7766873 Moberg et al. Aug 2010 B2
7776029 Whitehurst et al. Aug 2010 B2
7776031 Hartlaub et al. Aug 2010 B2
7785313 Mastrototaro Aug 2010 B2
7806852 Jurson Oct 2010 B1
7806886 Kanderian, Jr. et al. Oct 2010 B2
7826981 Goode, Jr. et al. Nov 2010 B2
7835927 Schlotterbeck et al. Nov 2010 B2
7836314 Chieu Nov 2010 B2
7856276 Ripart et al. Dec 2010 B2
7860583 Condurso et al. Dec 2010 B2
7868754 Salvat, Jr. Jan 2011 B2
7871394 Halbert et al. Jan 2011 B2
7886231 Hopermann et al. Feb 2011 B2
7895053 Holland et al. Feb 2011 B2
7896842 Palmroos et al. Mar 2011 B2
7899546 Sieracki et al. Mar 2011 B2
7905710 Wang et al. Mar 2011 B2
7920061 Klein et al. Apr 2011 B2
7933780 de la Huerga Apr 2011 B2
7938796 Moubayed May 2011 B2
7945452 Fathallah et al. May 2011 B2
7974714 Hoffberg Jul 2011 B2
7976508 Hoag Jul 2011 B2
7996241 Zak Aug 2011 B2
8034026 Grant Oct 2011 B2
8038593 Friedman et al. Oct 2011 B2
8048040 Kiani Nov 2011 B2
8060576 Chan et al. Nov 2011 B2
8065161 Howard et al. Nov 2011 B2
8066672 Mandro Nov 2011 B2
8075514 Butterfield et al. Dec 2011 B2
8078983 Davis et al. Dec 2011 B2
8082018 Duchon et al. Dec 2011 B2
8082312 Chan et al. Dec 2011 B2
8095692 Mehta et al. Jan 2012 B2
8147448 Sundar et al. Apr 2012 B2
8149131 Blornquist Apr 2012 B2
8169914 Bajpai May 2012 B2
8171094 Chan et al. May 2012 B2
8172798 Hungerford et al. May 2012 B2
8185322 Schroeder et al. May 2012 B2
8195478 Petersen et al. Jun 2012 B2
8206350 Mann et al. Jun 2012 B2
8219413 Martinez et al. Jul 2012 B2
8231578 Fathallah et al. Jul 2012 B2
8234128 Martucci et al. Jul 2012 B2
8267892 Spencer et al. Sep 2012 B2
8271106 Wehba et al. Sep 2012 B2
8287495 Michaud et al. Oct 2012 B2
8291337 Gannin et al. Oct 2012 B2
8298184 DiPerna et al. Oct 2012 B2
8312272 Serenyl et al. Nov 2012 B1
8352290 Bartz et al. Jan 2013 B2
8359338 Butterfiled et al. Jan 2013 B2
8380536 Howard et al. Feb 2013 B2
8387112 Ranjan et al. Feb 2013 B1
8394077 Jacobson et al. Mar 2013 B2
8398592 Leibner-Druska Mar 2013 B2
8403908 Jacobson et al. Mar 2013 B2
8435206 Evans et al. May 2013 B2
8449523 Brukalo et al. May 2013 B2
8452953 Buck et al. May 2013 B2
8453645 Figueiredo et al. Jun 2013 B2
8480648 Burnett et al. Jul 2013 B2
8489427 Simpson et al. Jul 2013 B2
8494879 Davis et al. Jul 2013 B2
8504179 Blomquist Aug 2013 B2
8517990 Teel et al. Aug 2013 B2
8518021 Stewart et al. Aug 2013 B2
8543416 Palmroos et al. Sep 2013 B2
8551038 Tsoukalis et al. Oct 2013 B2
8560345 Wehba et al. Oct 2013 B2
8577692 Silkaitis et al. Nov 2013 B2
8579884 Lanier et al. Nov 2013 B2
8626530 Tran Jan 2014 B1
8655676 Wehba et al. Feb 2014 B2
8660860 Wehba et al. Feb 2014 B2
8662388 Belkin Mar 2014 B2
8666769 Butler et al. Mar 2014 B2
8700421 Feng et al. Apr 2014 B2
8731960 Butler et al. May 2014 B2
8768719 Wehba et al. Jul 2014 B2
8771251 Ruchti et al. Jul 2014 B2
8777894 Butterfield et al. Jul 2014 B2
8777895 Hsu et al. Jul 2014 B2
8799012 Butler et al. Aug 2014 B2
8876793 Ledford et al. Nov 2014 B2
8922330 Moberg et al. Dec 2014 B2
8936565 Chawla Jan 2015 B2
8945043 Lee et al. Feb 2015 B2
8952794 Bloomquist et al. Feb 2015 B2
8998100 Halbert et al. Apr 2015 B2
9026370 Rubalcaba et al. May 2015 B2
9069887 Gupta et al. Jun 2015 B2
9077544 Baker et al. Jul 2015 B2
9089642 Murphy et al. Jul 2015 B2
9114217 Sur et al. Aug 2015 B2
9123077 Silkaitis et al. Sep 2015 B2
9192712 DeBelser et al. Nov 2015 B2
9240002 Hume et al. Jan 2016 B2
9381296 Arrizza et al. Jul 2016 B2
9393362 Cozmi et al. Jul 2016 B2
9483615 Roberts Nov 2016 B2
9498583 Sur et al. Nov 2016 B2
9539383 Kohlbrecher Jan 2017 B2
9572923 Howard et al. Feb 2017 B2
9594875 Arrizza et al. Mar 2017 B2
9604000 Wehba et al. Mar 2017 B2
9641432 Jha et al. May 2017 B2
9649431 Gray et al. May 2017 B2
9662436 Belkin et al. May 2017 B2
9690909 Stewart et al. Jun 2017 B2
9707341 Dumas, III et al. Jul 2017 B2
9717845 Istoc Aug 2017 B2
9724470 Day et al. Aug 2017 B2
9764082 Day et al. Sep 2017 B2
9886550 Lee et al. Feb 2018 B2
9943269 Muhsin et al. Apr 2018 B2
9971871 Arrizza et al. May 2018 B2
9995611 Ruchti et al. Jun 2018 B2
10022498 Ruchti et al. Jul 2018 B2
10042986 Ruchti et al. Aug 2018 B2
10046112 Oruklu et al. Aug 2018 B2
10166328 Oruklu et al. Jan 2019 B2
10173008 Simpson et al. Jan 2019 B2
10238799 Kohlbrecher Mar 2019 B2
10238801 Wehba et al. Mar 2019 B2
10242060 Butler et al. Mar 2019 B2
10300194 Day et al. May 2019 B2
10311972 Kohlbrecher et al. Jun 2019 B2
10314974 Day et al. Jun 2019 B2
10333843 Jha et al. Jun 2019 B2
10430761 Hume et al. Oct 2019 B2
10434246 Silkaitis et al. Oct 2019 B2
10463788 Day Nov 2019 B2
10617815 Day et al. Apr 2020 B2
10646651 Day et al. May 2020 B2
10692595 Xavier et al. Jun 2020 B2
10740436 Moskal Aug 2020 B2
10741280 Xavier et al. Aug 2020 B2
10757219 Moskal Aug 2020 B2
10765799 Belkin et al. Sep 2020 B2
10799632 Kohlbrecher Oct 2020 B2
10812380 Jha et al. Oct 2020 B2
10861592 Xavier et al. Dec 2020 B2
11052193 Day et al. Jul 2021 B2
20010016056 Westphal et al. Aug 2001 A1
20010031944 Peterson et al. Oct 2001 A1
20010032099 Joao Oct 2001 A1
20010037060 Thompson et al. Nov 2001 A1
20010044731 Coffman et al. Nov 2001 A1
20010048027 Walsh Dec 2001 A1
20010051787 Haller et al. Dec 2001 A1
20010056358 Dulong et al. Dec 2001 A1
20020010595 Kapp Jan 2002 A1
20020013551 Zaitsu et al. Jan 2002 A1
20020013723 Mise Jan 2002 A1
20020015018 Shimazu et al. Feb 2002 A1
20020019584 Schulze et al. Feb 2002 A1
20020021700 Hata et al. Feb 2002 A1
20020026103 Norris et al. Feb 2002 A1
20020029776 Blomquist Mar 2002 A1
20020032583 Joao Mar 2002 A1
20020040208 Flaherty et al. Apr 2002 A1
20020040282 Bailey et al. Apr 2002 A1
20020044043 Chaco et al. Apr 2002 A1
20020082728 Mueller et al. Jun 2002 A1
20020087115 Hartlaub Jul 2002 A1
20020087116 Hartlaub Jul 2002 A1
20020095486 Bahl Jul 2002 A1
20020103675 Vanelli Aug 2002 A1
20020123905 Goodroe et al. Sep 2002 A1
20020143580 Bristol et al. Oct 2002 A1
20020152239 Bautista-Lloyd et al. Oct 2002 A1
20020154600 Ido et al. Oct 2002 A1
20020173702 Lebel et al. Nov 2002 A1
20020173875 Wallace Nov 2002 A1
20020194329 Alling Dec 2002 A1
20030009244 Engleson Jan 2003 A1
20030013959 Grunwald et al. Jan 2003 A1
20030014222 Klass et al. Jan 2003 A1
20030014817 Gallant et al. Jan 2003 A1
20030025602 Medema et al. Feb 2003 A1
20030028082 Thompson Feb 2003 A1
20030036683 Kehr et al. Feb 2003 A1
20030036744 Struys et al. Feb 2003 A1
20030047126 Tomaschko Mar 2003 A1
20030050621 Lebel et al. Mar 2003 A1
20030059750 Bindler et al. Mar 2003 A1
20030060688 Ciarniello et al. Mar 2003 A1
20030069963 Jayant et al. Apr 2003 A1
20030079746 Hickle May 2003 A1
20030097529 Arimilli et al. May 2003 A1
20030104982 Wittmann et al. Jun 2003 A1
20030105389 Noonan et al. Jun 2003 A1
20030106553 Vanderveen Jun 2003 A1
20030115358 Yun Jun 2003 A1
20030120384 Haitin et al. Jun 2003 A1
20030125662 Bui Jul 2003 A1
20030130616 Steil Jul 2003 A1
20030135087 Hickle et al. Jul 2003 A1
20030139701 White et al. Jul 2003 A1
20030140928 Bui et al. Jul 2003 A1
20030140929 Wilkes et al. Jul 2003 A1
20030141981 Bui et al. Jul 2003 A1
20030143746 Sage, Jr. Jul 2003 A1
20030144878 Wilkes et al. Jul 2003 A1
20030158749 Olchanski et al. Aug 2003 A1
20030187338 Say et al. Oct 2003 A1
20030200116 Forrester Oct 2003 A1
20030204416 Acharya Oct 2003 A1
20030204781 Peebles et al. Oct 2003 A1
20030212364 Mann et al. Nov 2003 A1
20030212379 Bylund et al. Nov 2003 A1
20030212821 Gillies et al. Nov 2003 A1
20030217962 Childers et al. Nov 2003 A1
20040008123 Carrender et al. Jan 2004 A1
20040015132 Brown Jan 2004 A1
20040019607 Moubayed et al. Jan 2004 A1
20040030323 Ullestad et al. Feb 2004 A1
20040039257 Hickle Feb 2004 A1
20040057226 Berthou et al. Mar 2004 A1
20040064341 Langan et al. Apr 2004 A1
20040064342 Browne et al. Apr 2004 A1
20040064435 Moubayed et al. Apr 2004 A1
20040073811 Sanin Apr 2004 A1
20040077934 Massad Apr 2004 A1
20040078231 Wilkes et al. Apr 2004 A1
20040078236 Stoodley et al. Apr 2004 A1
20040085186 Eveland et al. May 2004 A1
20040104271 Martucci et al. Jun 2004 A1
20040122530 Hansen Jun 2004 A1
20040128162 Schlotterbeck et al. Jul 2004 A1
20040128163 Goodman et al. Jul 2004 A1
20040133441 Brady et al. Jul 2004 A1
20040139004 Cohen et al. Jul 2004 A1
20040145480 Despotis Jul 2004 A1
20040147034 Gore et al. Jul 2004 A1
20040167464 Ireland et al. Aug 2004 A1
20040167465 Kohler Aug 2004 A1
20040167804 Simpson Aug 2004 A1
20040172222 Simpson et al. Sep 2004 A1
20040172283 Vanderveen Sep 2004 A1
20040172301 Mihai et al. Sep 2004 A1
20040172302 Martucci et al. Sep 2004 A1
20040176667 Mihai et al. Sep 2004 A1
20040176980 Bulitta et al. Sep 2004 A1
20040176984 White et al. Sep 2004 A1
20040181314 Zaleski Sep 2004 A1
20040189708 Larcheveque et al. Sep 2004 A1
20040193325 Bonderud Sep 2004 A1
20040193328 Butterfield et al. Sep 2004 A1
20040193453 Butterfield et al. Sep 2004 A1
20040204673 Flaherty et al. Oct 2004 A1
20040215278 Stegink et al. Oct 2004 A1
20040220517 Starkweather et al. Nov 2004 A1
20040225252 Gillespie et al. Nov 2004 A1
20040236240 Kraus et al. Nov 2004 A1
20040243438 Mintz Dec 2004 A1
20040254434 Goodnow et al. Dec 2004 A1
20050010269 Lebel et al. Jan 2005 A1
20050020886 Hutchinson et al. Jan 2005 A1
20050021006 Tonnies Jan 2005 A1
20050027560 Cook Feb 2005 A1
20050027567 Taha Feb 2005 A1
20050038311 Kuth Feb 2005 A1
20050038669 Sachdeva et al. Feb 2005 A1
20050038680 McMahon Feb 2005 A1
20050040226 Al-Sheikh Feb 2005 A1
20050043620 Fallows et al. Feb 2005 A1
20050049910 Lancaster et al. Mar 2005 A1
20050055242 Bello et al. Mar 2005 A1
20050055244 Mullan et al. Mar 2005 A1
20050065465 Lebel et al. Mar 2005 A1
20050065817 Mihai et al. Mar 2005 A1
20050075544 Shapiro et al. Apr 2005 A1
20050080801 Kothandaraman et al. Apr 2005 A1
20050086071 Fox, Jr. et al. Apr 2005 A1
20050086072 Fox Apr 2005 A1
20050090808 Malave et al. Apr 2005 A1
20050099624 Staehr May 2005 A1
20050102162 Blumenfeld May 2005 A1
20050102165 Oshita et al. May 2005 A1
20050102167 Kapoor May 2005 A1
20050102669 Marney et al. May 2005 A1
20050107923 Vanderveen May 2005 A1
20050108057 Cohen et al. May 2005 A1
20050117529 Ramos-Escano Jun 2005 A1
20050119788 Engleson et al. Jun 2005 A1
20050119914 Batch Jun 2005 A1
20050131739 Rabinowitz et al. Jun 2005 A1
20050135306 McAllen et al. Jun 2005 A1
20050137522 Aoki Jun 2005 A1
20050137573 McLaughlin Jun 2005 A1
20050144043 Hollad et al. Jun 2005 A1
20050154769 Eckart et al. Jul 2005 A1
20050160057 Wefers et al. Jul 2005 A1
20050171503 Van Den Berghe et al. Aug 2005 A1
20050171815 Vanderveen Aug 2005 A1
20050177096 Bollish et al. Aug 2005 A1
20050177395 Blomquist Aug 2005 A1
20050182306 Sloan Aug 2005 A1
20050182355 Bui Aug 2005 A1
20050187950 Parker Aug 2005 A1
20050192557 Brauker et al. Sep 2005 A1
20050197554 Polcha Sep 2005 A1
20050197621 Poulsen et al. Sep 2005 A1
20050210037 Wefers et al. Sep 2005 A1
20050216479 Wefers et al. Sep 2005 A1
20050216480 Wefers et al. Sep 2005 A1
20050223045 Funahashi et al. Oct 2005 A1
20050224083 Crass Oct 2005 A1
20050234746 Funahashi Oct 2005 A1
20050240305 Bogash et al. Oct 2005 A1
20050246416 Blomquist Nov 2005 A1
20050251418 Fox, Jr. et al. Nov 2005 A1
20050261660 Choi Nov 2005 A1
20050273059 Mernoe et al. Dec 2005 A1
20050273367 Nourie et al. Dec 2005 A1
20050277873 Stewart et al. Dec 2005 A1
20050277890 Stewart et al. Dec 2005 A1
20050277911 Stewart et al. Dec 2005 A1
20050278194 Holland et al. Dec 2005 A1
20060004772 Hagan et al. Jan 2006 A1
20060009727 O'Mahony et al. Jan 2006 A1
20060009734 Martin Jan 2006 A1
20060010098 Goodnow et al. Jan 2006 A1
20060042139 Mendes Mar 2006 A1
20060047270 Shelton Mar 2006 A1
20060053036 Coffman et al. Mar 2006 A1
20060064020 Burnes et al. Mar 2006 A1
20060074633 Mahesh et al. Apr 2006 A1
20060074920 Wefers et al. Apr 2006 A1
20060079831 Gilbert Apr 2006 A1
20060089854 Holland et al. Apr 2006 A1
20060089855 Holland et al. Apr 2006 A1
20060100746 Leibner-Druska May 2006 A1
20060100907 Holland et al. May 2006 A1
20060106649 Eggers et al. May 2006 A1
20060111943 Wu May 2006 A1
20060116904 Brem Jun 2006 A1
20060116907 Rhodes et al. Jun 2006 A1
20060122481 Sievenpiper et al. Jun 2006 A1
20060122867 Eggers et al. Jun 2006 A1
20060129140 Todd et al. Jun 2006 A1
20060129429 Moubayed et al. Jun 2006 A1
20060129434 Smitherman et al. Jun 2006 A1
20060129435 Smitherman et al. Jun 2006 A1
20060136266 Tarassenko et al. Jun 2006 A1
20060136271 Eggers et al. Jun 2006 A1
20060143051 Eggers et al. Jun 2006 A1
20060173260 Gaoni et al. Aug 2006 A1
20060173406 Hayes et al. Aug 2006 A1
20060173715 Wang et al. Aug 2006 A1
20060173927 Beyer et al. Aug 2006 A1
20060190302 Eggers et al. Aug 2006 A1
20060195022 Trepagnier et al. Aug 2006 A1
20060200007 Brockway et al. Sep 2006 A1
20060200369 Batch et al. Sep 2006 A1
20060211404 Cromp et al. Sep 2006 A1
20060224141 Rush et al. Oct 2006 A1
20060229918 Fotsch et al. Oct 2006 A1
20060258985 Russell Nov 2006 A1
20060259327 Hoag Nov 2006 A1
20060264895 Flanders Nov 2006 A1
20060265246 Hoag Nov 2006 A1
20060267753 Hussey et al. Nov 2006 A1
20060268710 Appanna et al. Nov 2006 A1
20060270971 Gelfand et al. Nov 2006 A1
20060277206 Bailey et al. Dec 2006 A1
20060287885 Frick Dec 2006 A1
20070015972 Wang et al. Jan 2007 A1
20070016443 Wachman et al. Jan 2007 A1
20070027506 Stender et al. Feb 2007 A1
20070060796 Kim Mar 2007 A1
20070060870 Tolle et al. Mar 2007 A1
20070060871 Istoc Mar 2007 A1
20070061393 Moore Mar 2007 A1
20070065363 Dalal et al. Mar 2007 A1
20070073419 Sesay Mar 2007 A1
20070078314 Grounsell Apr 2007 A1
20070083870 Kanakogi Apr 2007 A1
20070088333 Levin et al. Apr 2007 A1
20070093786 Goldsmith et al. Apr 2007 A1
20070100665 Brown May 2007 A1
20070100667 Bardy May 2007 A1
20070106126 Mannheimer et al. May 2007 A1
20070112298 Mueller et al. May 2007 A1
20070116037 Moore May 2007 A1
20070118405 Campbell et al. May 2007 A1
20070135866 Baker et al. Jun 2007 A1
20070136098 Smythe et al. Jun 2007 A1
20070142822 Remde Jun 2007 A1
20070156282 Dunn Jul 2007 A1
20070156452 Batch Jul 2007 A1
20070169008 Varanasi et al. Jul 2007 A1
20070179448 Lim et al. Aug 2007 A1
20070186923 Poutiatine et al. Aug 2007 A1
20070191817 Martin Aug 2007 A1
20070191973 Holzbauer et al. Aug 2007 A1
20070213598 Howard Sep 2007 A1
20070213657 Jennewine et al. Sep 2007 A1
20070213684 Hickle et al. Sep 2007 A1
20070214003 Holland et al. Sep 2007 A1
20070215545 Bissler et al. Sep 2007 A1
20070232867 Hansmann Oct 2007 A1
20070233035 Wehba et al. Oct 2007 A1
20070233049 Wehba et al. Oct 2007 A1
20070233206 Frikart Oct 2007 A1
20070233520 Wehba et al. Oct 2007 A1
20070251835 Mehta et al. Nov 2007 A1
20070253021 Mehta et al. Nov 2007 A1
20070254593 Jollota et al. Nov 2007 A1
20070255125 Moberg et al. Nov 2007 A1
20070257788 Carlson Nov 2007 A1
20070258395 Jollota et al. Nov 2007 A1
20070299687 Palmer et al. Dec 2007 A1
20070299695 Jung et al. Dec 2007 A1
20080004904 Tran Jan 2008 A1
20080009684 Corsetti et al. Jan 2008 A1
20080033361 Evans et al. Feb 2008 A1
20080033966 Wahl Feb 2008 A1
20080034323 Blomquist Feb 2008 A1
20080041942 Aissa Feb 2008 A1
20080052704 Wysocki Feb 2008 A1
20080065007 Peterson et al. Mar 2008 A1
20080065417 Jung et al. Mar 2008 A1
20080071217 Moubayed et al. Mar 2008 A1
20080071251 Moubayed et al. Mar 2008 A1
20080091466 Butler et al. Apr 2008 A1
20080095339 Elliott Apr 2008 A1
20080097289 Steil et al. Apr 2008 A1
20080126969 Blomquist May 2008 A1
20080133265 Silkaitis Jun 2008 A1
20080139907 Rao et al. Jun 2008 A1
20080149117 Raghuram Jun 2008 A1
20080154177 Moubayed et al. Jun 2008 A1
20080172337 Banfield et al. Jul 2008 A1
20080184219 Matsumoto Jul 2008 A1
20080188796 Steil et al. Aug 2008 A1
20080214919 Harmon et al. Sep 2008 A1
20080246748 Cassidy et al. Oct 2008 A1
20080256305 Kwon Oct 2008 A1
20080259926 Tavares et al. Oct 2008 A1
20080262469 Bristol et al. Oct 2008 A1
20080269714 Mastrototaro et al. Oct 2008 A1
20080269723 Mastrototaro et al. Oct 2008 A1
20080275384 Mastrototaro et al. Nov 2008 A1
20080300572 Rankers et al. Dec 2008 A1
20080320387 Sasaki et al. Dec 2008 A1
20080320466 Dias Dec 2008 A1
20090003554 Katis et al. Jan 2009 A1
20090005703 Fasciano Jan 2009 A1
20090005728 Weinert et al. Jan 2009 A1
20090006061 Thukral et al. Jan 2009 A1
20090006129 Thukral Jan 2009 A1
20090006133 Weinert Jan 2009 A1
20090018495 Panduro Jan 2009 A1
20090051560 Manning et al. Feb 2009 A1
20090054743 Stewart Feb 2009 A1
20090054754 McMahon et al. Feb 2009 A1
20090057399 Sajkowsky Mar 2009 A1
20090063187 Johnson Mar 2009 A1
20090069785 Miller et al. Mar 2009 A1
20090099867 Newman Apr 2009 A1
20090135196 Holland et al. May 2009 A1
20090143662 Estes et al. Jun 2009 A1
20090149743 Barron et al. Jun 2009 A1
20090150174 Buck et al. Jun 2009 A1
20090150439 Gejdos Jun 2009 A1
20090150878 Pathak et al. Jun 2009 A1
20090156991 Roberts Jun 2009 A1
20090157695 Roberts Jun 2009 A1
20090158274 Roberts Jun 2009 A1
20090177146 Nesbitt et al. Jul 2009 A1
20090177769 Roberts Jul 2009 A1
20090177992 Rubalcaba et al. Jul 2009 A1
20090183147 Davis et al. Jul 2009 A1
20090209938 Aalto-Setala Aug 2009 A1
20090210250 Prax et al. Aug 2009 A1
20090221890 Saffer et al. Sep 2009 A1
20090231249 Wang et al. Sep 2009 A1
20090270833 DeBelser Oct 2009 A1
20090275886 Bloomquist et al. Nov 2009 A1
20090275896 Kamen et al. Nov 2009 A1
20090284691 Marhefka et al. Nov 2009 A1
20090292340 Mass et al. Nov 2009 A1
20090306573 Gagner et al. Dec 2009 A1
20090326340 Wang Dec 2009 A1
20090326516 Bangera et al. Dec 2009 A1
20100022988 Wochner Jan 2010 A1
20100036310 Hillman Feb 2010 A1
20100056992 Hayter Mar 2010 A1
20100083060 Rahman Apr 2010 A1
20100095229 Dixon et al. Apr 2010 A1
20100121170 Rule May 2010 A1
20100121246 Peters et al. May 2010 A1
20100121415 Skelton et al. May 2010 A1
20100121654 Portnoy et al. May 2010 A1
20100121752 Banigan May 2010 A1
20100130933 Holland et al. May 2010 A1
20100131434 Magent et al. May 2010 A1
20100138523 Umess et al. Jun 2010 A1
20100146137 Wu et al. Jun 2010 A1
20100156633 Buck et al. Jun 2010 A1
20100160854 Gauthier Jun 2010 A1
20100160860 Celentano et al. Jun 2010 A1
20100174266 Estes Jul 2010 A1
20100191525 Rabenko et al. Jul 2010 A1
20100198034 Thomas et al. Aug 2010 A1
20100198196 Wei Aug 2010 A1
20100200506 Ware et al. Aug 2010 A1
20100209268 Davis Aug 2010 A1
20100212675 Walling et al. Aug 2010 A1
20100217621 Schoenberg Aug 2010 A1
20100234708 Buck et al. Sep 2010 A1
20100250732 Bucknell Sep 2010 A1
20100271479 Heydlauf Oct 2010 A1
20100273738 Valcke et al. Oct 2010 A1
20100274218 Yodfat et al. Oct 2010 A1
20100280486 Khair et al. Nov 2010 A1
20100292634 Kircher Nov 2010 A1
20100298765 Budiman et al. Nov 2010 A1
20100318025 John Dec 2010 A1
20110001605 Kiani et al. Jan 2011 A1
20110021898 Wei et al. Jan 2011 A1
20110040158 Katz et al. Feb 2011 A1
20110060758 Schlotterbeck et al. Mar 2011 A1
20110071844 Cannon et al. Mar 2011 A1
20110072379 Gannon Mar 2011 A1
20110078253 Chan et al. Mar 2011 A1
20110078608 Gannon et al. Mar 2011 A1
20110093284 Dicks et al. Apr 2011 A1
20110099313 Bolanowski Apr 2011 A1
20110125095 Lebel et al. May 2011 A1
20110138185 Ju et al. Jun 2011 A1
20110175728 Baker, Jr. Jul 2011 A1
20110178462 Moberg et al. Jul 2011 A1
20110196748 Caron et al. Aug 2011 A1
20110231216 Fyke et al. Sep 2011 A1
20110257496 Terashima et al. Oct 2011 A1
20110257798 Ali et al. Oct 2011 A1
20110259954 Bartz et al. Oct 2011 A1
20110264043 Kotnick et al. Oct 2011 A1
20110264044 Bartz Oct 2011 A1
20110266221 Ware et al. Nov 2011 A1
20110270045 Lebel et al. Nov 2011 A1
20110275904 Lebel et al. Nov 2011 A1
20110286457 Ee Nov 2011 A1
20110289497 Kiaie et al. Nov 2011 A1
20110295196 Chazot et al. Dec 2011 A1
20110295341 Estes et al. Dec 2011 A1
20110296051 Vange Dec 2011 A1
20110296411 Tang et al. Dec 2011 A1
20110313789 Karmen et al. Dec 2011 A1
20110319813 Kamen et al. Dec 2011 A1
20110320049 Chossat et al. Dec 2011 A1
20120005680 Dolby et al. Jan 2012 A1
20120011253 Friedman et al. Jan 2012 A1
20120016305 Jollota Jan 2012 A1
20120029941 Malave et al. Feb 2012 A1
20120036102 Fletcher et al. Feb 2012 A1
20120065990 Howard Mar 2012 A1
20120066501 Xiong Mar 2012 A1
20120070045 Vesper et al. Mar 2012 A1
20120095437 Hemmerling Apr 2012 A1
20120112903 Kaib et al. May 2012 A1
20120130198 Beaule May 2012 A1
20120143116 Ware et al. Jun 2012 A1
20120150556 Galasso et al. Jun 2012 A1
20120157920 Flachbart et al. Jun 2012 A1
20120179135 Rinehart et al. Jul 2012 A1
20120179136 Rinehart et al. Jul 2012 A1
20120185267 Kamen et al. Jul 2012 A1
20120203177 Lanier Aug 2012 A1
20120245554 Kawamura Sep 2012 A1
20120259978 Petersen et al. Oct 2012 A1
20120277716 Ali et al. Nov 2012 A1
20120283630 Lee et al. Nov 2012 A1
20120284734 McQuaid et al. Nov 2012 A1
20120323212 Murphy Dec 2012 A1
20130006666 Schneider Jan 2013 A1
20130006702 Wu Jan 2013 A1
20130012877 Debelser et al. Jan 2013 A1
20130012879 Debelser et al. Jan 2013 A1
20130012880 Blomquist Jan 2013 A1
20130015980 Evans et al. Jan 2013 A1
20130036403 Geist Feb 2013 A1
20130036412 Birtwhistle et al. Feb 2013 A1
20130047113 Hume Feb 2013 A1
20130066265 Grant Mar 2013 A1
20130072872 Yodfat et al. Mar 2013 A1
20130096444 Condurso et al. Apr 2013 A1
20130096648 Benson Apr 2013 A1
20130102963 Marsh et al. Apr 2013 A1
20130104120 Arrizza et al. Apr 2013 A1
20130138452 Cork et al. May 2013 A1
20130144206 Lee et al. Jun 2013 A1
20130150824 Estes et al. Jun 2013 A1
20130167245 Birtwhistle et al. Jun 2013 A1
20130173473 Birtwhistle et al. Jul 2013 A1
20130191770 Bartz et al. Jul 2013 A1
20130204188 Kamen et al. Aug 2013 A1
20130218080 Peterfreund et al. Aug 2013 A1
20130274669 Stempfle et al. Oct 2013 A1
20130275539 Gross et al. Oct 2013 A1
20130291116 Homer Oct 2013 A1
20130296823 Melker et al. Nov 2013 A1
20130296984 Burnett et al. Nov 2013 A1
20130317753 Kamen Nov 2013 A1
20130346108 Kamen et al. Dec 2013 A1
20140025392 Chandrasenan Jan 2014 A1
20140163517 Finan et al. Jun 2014 A1
20140180711 Kamen Jun 2014 A1
20140257251 Bush et al. Sep 2014 A1
20140266790 Al-Ali et al. Sep 2014 A1
20140266794 Brown et al. Sep 2014 A1
20140269643 Sun Sep 2014 A1
20140276571 Ludolph Sep 2014 A1
20140280522 Watte Sep 2014 A1
20140288947 Simpson Sep 2014 A1
20140297329 Rock Oct 2014 A1
20140366878 Baron Dec 2014 A1
20150005935 Bae et al. Jan 2015 A1
20150058044 Butler Feb 2015 A1
20150066531 Jacobson et al. Mar 2015 A1
20150100038 McCann et al. Apr 2015 A1
20150100787 Westin et al. Apr 2015 A1
20150117234 Raman et al. Apr 2015 A1
20150151051 Tsoukalis Jun 2015 A1
20150161354 Blomquist Jun 2015 A1
20150199192 Borges et al. Jul 2015 A1
20150230760 Schneider Aug 2015 A1
20150328396 Adams et al. Nov 2015 A1
20150371004 Jones Dec 2015 A1
20150379237 Mills et al. Dec 2015 A1
20160006695 Prodoehl et al. Jan 2016 A1
20160015885 Pananen et al. Jan 2016 A1
20160034655 Gray et al. Feb 2016 A1
20160045661 Gray et al. Feb 2016 A1
20160051749 Istoc Feb 2016 A1
20160074573 Kohlbrecher Mar 2016 A1
20160228633 Welsch et al. Aug 2016 A1
20160241391 Fenster Aug 2016 A1
20160285876 Perez et al. Sep 2016 A1
20160350513 Jacobson et al. Dec 2016 A1
20170147761 Moskal May 2017 A1
20170262590 Karakosta et al. Sep 2017 A1
20170274140 Howard et al. Sep 2017 A1
20170286637 Arrizza et al. Oct 2017 A1
20170319780 Belkin et al. Nov 2017 A1
20180121613 Connely, IV et al. May 2018 A1
20180126067 Ledford et al. May 2018 A1
20180181712 Ensey et al. Jun 2018 A1
20180247712 Muhsin et al. Aug 2018 A1
20180322948 Drost et al. Nov 2018 A1
20190006044 Brask Jan 2019 A1
20190096518 Pace Mar 2019 A1
20190132196 Trivedi et al. May 2019 A1
20190147998 Ruchti et al. May 2019 A1
20190228863 Dharwad et al. Jul 2019 A1
20190229982 Ikuta et al. Jul 2019 A1
20190240405 Wehba et al. Aug 2019 A1
20190243829 Butler et al. Aug 2019 A1
20190245942 Moskal Aug 2019 A1
20190269852 Kohlbrecher Sep 2019 A1
20190311803 Kohlbrecher et al. Oct 2019 A1
20190348160 Heavelyn et al. Nov 2019 A1
20190392929 Gassman Dec 2019 A1
20200027541 Xavier et al. Jan 2020 A1
20200027542 Xavier et al. Jan 2020 A1
20200027543 Xavier et al. Jan 2020 A1
20200027548 Xavier et al. Jan 2020 A1
20200027549 Xavier et al. Jan 2020 A1
20200027550 Xavier et al. Jan 2020 A1
20200027551 Xavier et al. Jan 2020 A1
20200028837 Xavier et al. Jan 2020 A1
20200028914 Xavier et al. Jan 2020 A1
20200028929 Xavier et al. Jan 2020 A1
20200035346 Xavier et al. Jan 2020 A1
20200054825 Kamen et al. Feb 2020 A1
20200061291 Day et al. Feb 2020 A1
20200206413 Silkaitis et al. Jul 2020 A1
20200282139 Susi Sep 2020 A1
20200306443 Day Oct 2020 A1
20200330685 Day Oct 2020 A1
20200353168 Keenan et al. Nov 2020 A1
20210252210 Day et al. Aug 2021 A1
Foreign Referenced Citations (138)
Number Date Country
2 060 151 Aug 1997 CA
2 125 300 Oct 1999 CA
2 898 825 Jul 2014 CA
01110843 Aug 2003 CO
31 12 762 Jan 1983 DE
34 35 647 Jul 1985 DE
198 44 252 Mar 2000 DE
199 32 147 Jan 2001 DE
103 52 456 Jul 2005 DE
0 319 267 Jun 1989 EP
0 380 061 Aug 1990 EP
0 384 155 Aug 1990 EP
0 460 533 Dec 1991 EP
0 564 127 Jun 1993 EP
0 633 035 Jan 1995 EP
0 652 528 May 1995 EP
0 672 427 Sep 1995 EP
0 683 465 Nov 1995 EP
0 880 936 Dec 1998 EP
1 157 711 Nov 2001 EP
1 174 817 Jan 2002 EP
0 664 102 Apr 2002 EP
1 197 178 Apr 2002 EP
0 830 775 Aug 2002 EP
1 500 025 Apr 2003 EP
2 113 842 Nov 2009 EP
2 228 004 Sep 2010 EP
2 243 506 Oct 2010 EP
2 410 448 Jan 2012 EP
2 742 961 Jun 2014 EP
2 717 919 Sep 1995 FR
2 285 135 Jun 1995 GB
04-161139 Jun 1992 JP
07-502678 Mar 1995 JP
11-500643 Jan 1999 JP
2000-316820 Nov 2000 JP
2002-531154 Sep 2002 JP
2003-016183 Jan 2003 JP
2003-296173 Oct 2003 JP
2005-021463 Jan 2005 JP
2005-527284 Sep 2005 JP
2005-284846 Oct 2005 JP
2006-047319 Feb 2006 JP
2006-520949 Sep 2006 JP
2007-518479 Jul 2007 JP
2007-525256 Sep 2007 JP
2008-080036 Apr 2008 JP
2008-516303 May 2008 JP
2008-158622 Jul 2008 JP
2008-529675 Aug 2008 JP
2009-163534 Jul 2009 JP
2010-502361 Jan 2010 JP
2011-506048 Mar 2011 JP
2012-011204 Jan 2012 JP
2012-070991 Apr 2012 JP
2012-523895 Oct 2012 JP
2014-068283 Apr 2014 JP
WO 84001719 May 1984 WO
WO 91016416 Oct 1991 WO
WO 92010985 Jul 1992 WO
WO 92013322 Aug 1992 WO
WO 94005355 Mar 1994 WO
WO 96008755 Mar 1996 WO
WO 96025186 Aug 1996 WO
WO 98012670 Mar 1998 WO
WO 98019263 May 1998 WO
WO 99051003 Oct 1999 WO
WO 00013580 Mar 2000 WO
WO 00053243 Sep 2000 WO
WO 01014974 Mar 2001 WO
WO 01033484 May 2001 WO
WO 01045014 Jun 2001 WO
WO 02005702 Jan 2002 WO
WO 02036044 May 2002 WO
WO 02049153 Jun 2002 WO
WO 02049279 Jun 2002 WO
WO 02069099 Sep 2002 WO
WO 02081015 Oct 2002 WO
WO 02088875 Nov 2002 WO
WO 03006091 Jan 2003 WO
WO 03050917 Jun 2003 WO
WO 03091836 Nov 2003 WO
WO 03094092 Nov 2003 WO
WO 2004060455 Jul 2004 WO
WO 2004070557 Aug 2004 WO
WO 2004070562 Aug 2004 WO
WO 2004072828 Aug 2004 WO
WO 2005036447 Apr 2005 WO
WO 2005050526 Jun 2005 WO
WO 2005057175 Jun 2005 WO
WO 2005066872 Jul 2005 WO
WO 2007087443 Aug 2007 WO
WO 2007117705 Oct 2007 WO
WO 2007127879 Nov 2007 WO
WO 2007127880 Nov 2007 WO
WO 2008067245 Jun 2008 WO
WO 2008082854 Jul 2008 WO
WO 2008088490 Jul 2008 WO
WO 2008097316 Aug 2008 WO
WO 2008103915 Aug 2008 WO
WO 2008124478 Oct 2008 WO
WO 2008134146 Nov 2008 WO
WO 2009016504 Feb 2009 WO
WO 2009023406 Feb 2009 WO
WO 2009023407 Feb 2009 WO
WO 2009023634 Feb 2009 WO
WO 2009036327 Mar 2009 WO
WO 2009049252 Apr 2009 WO
WO 2010017279 Feb 2010 WO
WO 2010033919 Mar 2010 WO
WO 2010053703 May 2010 WO
WO 2010075371 Jul 2010 WO
WO 2010099313 Sep 2010 WO
WO 2010114929 Oct 2010 WO
WO 2010119409 Oct 2010 WO
WO 2010124127 Oct 2010 WO
WO 2010130992 Nov 2010 WO
WO 2010135646 Nov 2010 WO
WO 2010135654 Nov 2010 WO
WO 2010135686 Nov 2010 WO
WO 2011005633 Jan 2011 WO
WO 2011022549 Feb 2011 WO
WO 2012048833 Apr 2012 WO
WO 2012049214 Apr 2012 WO
WO 2012049218 Apr 2012 WO
WO 2012120078 Sep 2012 WO
WO 2012140547 Oct 2012 WO
WO 2012164556 Dec 2012 WO
WO 2012170942 Dec 2012 WO
WO 2013045506 Apr 2013 WO
WO 2014100736 Jun 2014 WO
WO 2014131729 Sep 2014 WO
WO 2014131730 Sep 2014 WO
WO 2015124569 Aug 2015 WO
WO 2019219290 Nov 2019 WO
WO-2019219290 Nov 2019 WO
WO 2020018388 Jan 2020 WO
WO 2020018389 Jan 2020 WO
Non-Patent Literature Citations (114)
Entry
Frank Doesburg et al., Improved Usability of a Multi-Infusion Setup Using a Centralized Control Interface: A Task-Based Usability Test, 2017, PLoS One 12(8): e0183104. https://doi.org/10.1371/journal.pone.0183104 (Year: 2017).
Akridge, Jeannie, “New Pumps Outsmart User Error”, Healthcare Purchasing News, Apr. 2011, pp. 10, http://web.archive.org/web/20110426122450/http://www.hpnonline.com/inside/2011 -04/1104-OR-Pumps.html.
Alur et al., “Formal Specifications and Analysis of the Computer-Assisted Resuscitation Algorithm (CARA) Infusion Pump Control System”, International Journal on Software Tools for Technology Transfer, Feb. 2004, vol. 5, No. 4, pp. 308-319.
Aragon, Daleen RN, Ph.D., CCRN, “Evaluation of Nursing Work Effort and Perceptions About Blood Glucose Testing in Tight Glycemic Control”, American Journal of Critical Care, Jul. 2006, vol. 15, No. 4, pp. 370-377.
ASHP Advantage, “Improving Medication Safety in Health Systems Through Innovations in Automation Technology”, Proceedings of Educational Symposium and Educational Sessions during the 39th ASHP Midyear Clinical Meeting, Dec. 5-9, 2004, Orlando, FL, pp. 28.
Beard et al., “Total Quality Pain Management: History, Background, Resources”, Abbott Laboratories, TQPM Survey History, available Feb. 2015 or earlier, pp. 1-3.
Bektas et al., “Bluetooth Communication Employing Antenna Diversity”, Proceedings of Eight IEEE International Symposium on Computers and Communication, Jul. 2003, pp. 6.
Bequette, Ph.D., “A Critical Assessment of Algorithms and Challenges in the Development of a Closed-Loop Artificial Pancreas”, Diabetes Technology & Therapeutics, Feb. 28, 2005, vol. 7, No. 1, pp. 28-47.
Bequette, B. Wayne, Ph.D., “Analysis of Algorithms for Intensive Care Unit Blood Glucose Control”, Journal of Diabetes Science and Technology, Nov. 2007, vol. 1, No. 6, pp. 813-824.
Braun, “Infusomat® Space and Accessories”, Instructions for Use, Nov. 2010, p. 68. http://corp.bbraun.ee/Extranet/Infusioonipumbad/Kasutusjuhendid/Vanad/Kasutusjuhend-Infusomat_Space(vers688J,inglise_k).pdf.
Brownlee, Seth, “Product Spotlight: The Plum A+ with Hospira MedNet Infusion System”, PP&P Magazine, Dec. 2005, vol. 2, No. 7, pp. 2.
Cannon, Md et al., “Automated Heparin-Delivery System to Control Activated Partial Thromboplastin Time”, Circulation, Feb. 16, 1999, vol. 99, pp. 751-756.
Cardinal Health, “Alaris® Syringe Pumps” Technical Service Manual, Copyright 2002-2006, Issue 9, pp. 1-88, http://www.frankshospitalworkshop.com/equipment/documents/infusion_pumps/service_manuals/Cardinal_Alaris_-_Service_Manual.pdf.
“CareAware® Infusion Management”, Cerner Store, as printed May 12, 2011, pp. 3, https://store.cerner.com/items/7.
Chen et al., “Enabling Location-Based Services on Wireless LANs”, The 11th IEEE International Conference on Networks, ICON 2003, Sep. 28-Oct. 1, 2003, pp. 567-572.
“Computer Dictionary”, Microsoft Press, Third Edition, Microsoft Press, 1997, pp. 430 & 506.
“Context-Free Grammar”, Wikipedia.org, as last modified Mar. 5, 2010 in 11 pages, https://en.wikipedia.org/w/index.php/?title=Context-free_grammar&oldid=347915989.
Crawford, Anne J., MSN, RNC, “Building a Successful Quality Pain Service: Using Patient Satisfaction Data and the Clinical Practice Guideline”, USA, 1995, pp. 1-6.
Crocker et al., “Augmented BNF for Syntax Specifications: ABNF”, Network Working Group, Standards Track, Jan. 2008, pp. 16.
Davidson et al., “A Computer-Directed Intravenous Insulin System Shown to be Safe, Simple, and Effective in 120,618 h of Operation”, Diabetes Care, Oct. 2005, vol. 28, No. 10, pp. 2418-2423.
Davies, T., “Cordless Data Acquisition in a Hospital Environment”, IEE Colloquium on Cordless Computing—Systems and User Experience, 1993, pp. 4.
Dayhoff et al., “Medical Data Capture and Display: The Importance of Clinicians' Workstation Design”, AMIA, Inc., 1994, pp. 541-545.
Diabetes Close Up, Close Concerns AACE Inpatient Management Conference Report, Consensus Development Conference on Inpatient Diabetes and Metabolic Control, Washington, D.C., Dec. 14-16, 2003, pp. 1-32.
EAST PhD et al., “Digital Electronic Communication Between ICU Ventilators and Computers and Printers”, Respiratory Care, Sep. 1992, vol. 37, No. 9, pp. 1113-1122.
Einhorn, George W., “Total Quality Pain Management: A Computerized Quality Assessment Tool for Postoperative Pain Management”, Abbott Laboratories, Chicago, IL, Mar. 2, 2000, pp. 1-4.
Eskew et al., “Using Innovative Technologies to Set New Safety Standards for the Infusion of Intravenous Medications”, Hospital Pharmacy, 2002, vol. 37, No. 11, pp. 1179-1189.
Felleiter et al., “Data Processing in Prehospital Emergency Medicine”, International journal of Clinical Monitoring and Computing, Feb. 1995, vol. 12, No. 1, pp. 37-41.
“File Verification”, Wikipedia.org, as last modified Oct. 11, 2011 in 2 pages, https://en.wikipedia.org/w/index.php?title=File_verification&oldid=455048290.
Fogt et al., Development and Evaluation of a Glucose Analyzer for a Glucose-Controlled Insulin Infusion System (Biostator®), Clinical Chemistry, 1978, vol. 24, No. 8, pp. 1366-1372.
Gabel et al., “Camp: A Common API for Measuring Performance”, 21st Large Installations System Administration Conference (LISA '07), 2007, pp. 49-61.
Gage et al., “Automated Anesthesia Surgery Medical Record System”, International Journal of Clinical Monitoring and Computing, Dec. 1990, vol. 7, No. 4, pp. 259-263.
Galt et al., “Personal Digital Assistant-Based Drug Information Sources: Potential to Improve Medication Safety”, Journal of Medical Library Association, Apr. 2005, vol. 93, No. 2, pp. 229-236.
Gardner, Ph.D. et al., “Real Time Data Acquisition: Recommendations for the Medical Information Bus (MIB)”, 1992, pp. 813-817.
“General-Purpose Infusion Pumps”, Health Devices, EXRI Institute, Oct. 1, 2002, vol. 31, No. 10, pp. 353-387.
Givens et al., “Exploring the Internal State of User Interfaces by Combining Computer Vision Techniques with Grammatical Inference”, Proceedings of the 2013 International Conference on Software Engineering, San Francisco, CA, May 18-26, 2013, pp. 1165-1168.
Glaeser, “A Hierarchical Minicomputer System for Continuous Post-Surgical Monitoring”, Computers and Biomedical Research, Aug. 31, 1975, pp. 336-361.
Goldberg et al., “Clinical Results of an Updated Insulin Infusion Protocol in Critically Ill Patients”, Diabetes Spectrum, 2005, vol. 18, No. 3, pp. 188-191.
Gomez et al., “CLAM: Connection-Less, Lightweight, and Multiway Communication Support for Distributed Computing”, Computer Science, 1997, vol. 1199, pp. 227-240.
“GPS Tracker for Medical Equipment”, http://www.trackingsystem.com/forbusinesses/corporate-trackingsystem/1098-gps-tracker-formedicalequipment.html, Mar. 15, 2015, pp. 2.
Graseby, “Model 3000/500 and Micro 3100/505: Volumetric Infusion Pump”, Technical Service Manual, Graseby Medical Ltd., Apr. 2002, Issue A, pp. 160.
Graseby, “Model 3000/500 and Micro 3100/505: Volumetric Infusion Pump: Illustrated Parts List for Pump Serial Nos. from 3000 to 59,999”, Technical Service Manual, Graseby Medical Ltd., Apr. 2002, Issue A, pp. 71.
Halpern et al., “Changes in Critical Care Beds and Occupancy in the United States 1985-2000: Differences Attributable to Hospital Size”, Critical Care Medical, Aug. 2006, vol. 34, No. 8, pp. 2105-2112.
Hamann et al., “PUMPSIN: A Software Package for Simulating Computer-Controlled Drug Infusion Pumps”, Annual International Conference of the IEEE Engineering in Medicine and Biology Society, 1990, vol. 12, No. 5, pp. 2019-2020.
Hasegawa et al., “On a Portable Memory Device for Physical Activities and Informations of Maternal Perception”, Journal of Perinatal Medicine, 1988, vol. 16, No. 4, pp. 349-356.
Hawley et al., “Clinical Implementation of an Automated Medical Information Bus in an Intensive Care Unit”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 9, 1988, pp. 621-624.
Hayes-Roth et al., “Guardian: A Prototype Intelligent Agent for Intensive-Care Monitoring”, Artificial Intelligence in Medicine, vol. 4, Dec. 31, 1992, pp. 165-185.
Hospira, GemStar® Pain Management Infusion System 9-084-PR1-2-2, www.hospira.com/products/gemstar_painmanagement.aspx, Jan. 28, 2010, pp. 1-2.
Introducing Abbott TQPM (Total Quality Pain Management), Abbott Laboratories, Abbott Park, IL, May 2000, pp. 1-4.
“Infusion Pump”, Wikipedia.org, as last modified Mar. 27, 2014, in 3 pages, https://web.archive.org/web/20140703024932/https://en.wikipedia.org/wiki/Infusion_pump.
International Search Report and Written Opinion received in PCT Application No. PCT Application No. PCT/US2019/041715, dated Aug. 23, 2019 in 40 pages.
Isaka et al., “Control Strategies for Arterial Blood Pressure Regulation”, IEEE Transactions on Biomedical Engineering, Apr. 1993, vol. 40, No. 4, pp. 353-363.
Johnson et al., “Using BCMA Software to Improve Patient Safety in Veterans Administration Medical Centers”, Journal of Healthcare Information Management, Dec. 6, 2004, vol. 16, No. 1, pp. 46-51.
Kent Displays, “Reflex™ Electronic Skins”, Product Brief 25127B, 2009, pp. 2.
Kent Displays, “Reflex Electronic Skins Engineering Evaluation Kit”, 25136A, Mar. 10, 2009.
Lefkowitz et al., “A Trial of the Use of Bar Code Technology to Restructure a Drug Distribution and Administration System”, Hospital Pharmacy, Mar. 31, 1991, vol. 26, No. 3, pp. 239-242.
Lenssen et al., “Bright Color Electronic Paper Technology and Applications”, IDS '09 Publication EP1-2 (Phillips Research), 2009, pp. 529-532.
Leveson, Nancy, “Medical Devices: The Therac-25”, Appendix A, University of Washington, 1995, pp. 49.
Linkens, D.A. “Computer Control for Patient Care”, Computer Control of Real-Time Processes, IEE Control Engineering Series 41, 1990, Ch. 13, pp. 216-238.
Mako Hill et al., “The Official Ubuntu Book”, Shoeisha Co., Ltd., 1st Edition, Jun. 11, 2007, pp. 115 to 125.
Marshall, et al., “New Microprocessor-Based Insulin Controller”, IEEE Transactions on Biomedical Engineering, Nov. 1983, vol. BME-30, No. 11, pp. 689-695.
Martino et al., “Automation of a Medical Intensive Care Environment with a Flexible Configuration of Computer Systems”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 5, 1980, vol. 3, pp. 1562-1568.
Matsunaga et al., “On the Use of Machine Learning to Predict the Time and Resources Consumed by Applications”, 2010 10th IEEE/ACM International Conference on Cluster, Cloud and Grid Computing (CCGrid), May 17-20, 2010, pp. 495-504.
Mauseth et al., “Proposed Clinical Application for Tuning Fuzzy Logic Controller of Artificial Pancreas Utilizing a Personalization Factor”, Journal of Diabetes Science and Technology, Jul. 2010, vol. 4, No. 4, pp. 913-922.
Medfusion™, “Medfusion Syringe Infusion Pump Model 4000”, Operator's Manual, Software Version V1.1, Sep. 2011, pp. 154. http://www.medfusionpump.com/assets/literature/manuals/Operators_Manual_4000_40-5760-51A.pdf.
Metnitz et al., “Computer Assisted Data Analysis in Intensive Care: the ICDEV Project-Development of a Scientific Database System for Intensive Care”, International Journal of Clinical Monitoring and Computing, Aug. 1995, vol. 12, No. 3, pp. 147-159.
Micrel Medical Devices, “MP Daily +” http://web.archive.org/web/20130803235715/http://www.micrelmed.com/index.aspx?productid=9 as archived Aug. 3, 2013 in 1 page.
Moghissi, Etie, MD, FACP, FACE, “Hyperglycemia in Hospitalized Patients”, A Supplement to ACP Hospitalist, Jun. 15, 2008, pp. 32.
Murray, Jr et al., “Automated Drug Identification System (during surgery)”, IEEE Proceedings of Southeastcon '91, Apr. 7-10, 1991, pp. 265.
Nicholson et al., “‘Smart’ Infusion Apparatus for Computation and Automated Delivery of Loading, Tapering, and Maintenance Infusion Regimens of Lidocaine, Procainamide, and Theophylline”, Proceedings of The Seventh Annual Symposium on Computer Applications in Medical Care, Oct. 1983, pp. 212-213.
Nolan et al., “The P1073 Medical Information Bus Standard: Overview and Benefits for Clinical Users”, 1990, pp. 216-219.
Omnilink Systems, Inc., “Portable Medical Equipment Tracking”, http://www.omnilink.com/portablemedicalequipmenttracking/, Mar. 15, 2015, pp. 2.
O'SHEA, Kristen L., “Infusion Management: Working Smarter, Not Harder”, Hospital Pharmacy, Apr. 2013, vol. 48, No. 3, pp. S1-S14.
Package Management in Debian GNU/Linux, Debian GNU/Linux Expert Desktop Use Special, Giutsu-Hyohron Co., Ltd., First Edition, Sep. 25, 2004, pp. 183-185.
Passos et al., “Distributed Software Platform for Automation and Control of General Anaesthesia”, Eighth International Symposium on Parallel and Distributed Computing, ISPDC '09, Jun. 30-Jul. 4, 2009, pp. 8.
Philips, “IntelliSpace Event Management and IntelliVue Patient Monitoring”, Release 10, 2011, http://incenter.medical.philips.com/doclib/enc/fetch/2000/4504/577242/577243/577247/582646/583147/8359175/Philips_Patient_Monitoring_and_IntelliSpace_Event_Management_Interoperability.pdf%3fnodeid%3d8508574%26vernum%3d-2, pp. 2.
Pretty et al., “Hypoglycemia Detection in Critical Care Using Continuous Glucose Monitors: An in Silico Proof of Concept Analysis”, Journal of Diabetes Science and Technology, Jan. 2010, vol. 4, No. 1, pp. 15-24.
Rappoport, Arthur E., “A Hospital Patient and Laboratory machine-Readable Identification System (MRIS) Revisited”, Journal of Medical Systems, Apr. 1984, vol. 8, Nos. 1/2, pp. 133-156.
Ritchie et al., “A Microcomputer Based Controller for Neuromuscular Block During Surgery”, Annals of Biomedical Engineering, Jan. 1985, vol. 13, No. 1, pp. 3-15.
Saager et al., “Computer-Guided Versus Standard Protocol for Insulin Administration in Diabetic Patients Undergoing Cardiac Surgery”, Annual Meeting of the American Society of Critical Care Anesthesiologists, Oct. 13, 2006.
Sanders et al., “The Computer in a Programmable Implantable Medication System (PIMS)”, Proceedings of the Annual Symposium on Computer Application in Medical Care, Nov. 2, 1982, pp. 682-685.
Schilling et al., “Optimizing Outcomes! Error Prevention and Evidence-Based Practice with IV Medications”, A Pro-Ce Publication, Hospira, Inc., Feb. 6, 2012, pp. 56.
Schulze et al., “Advanced Sensors Technology Survey”, Final Report, Feb. 10, 1992, pp. 161.
Scott, et al., “Using Bar-Code Technology to Capture Clinical Intervention Data in a Hospital with a Stand-Alone Pharmacy Computer System”, Mar. 15, 1996, American Journal of Health-System Pharmacy, vol. 53, No. 6, pp. 651-654.
Sebald et al., “Numerical Analysis of a Comprehensive in Silico Subcutaneous Insulin Absorption Compartmental Model”, 31st Annual International Conference of the IEEE Engineering in Medicine and Biology Society, Sep. 2-6, 2009, pp. 3901-3904.
Shabot, M. Michael, “Standardized Acquisition of Bedside Data: The IEEE P1073 Medical Information Bus”, International Journal of Clinical Monitoring and Computing, vol. 6, Sep. 27, 1989, pp. 197-204.
Sheppard, Louis, Ph.D., “Automation of the Infusion of Drugs Using Feedback Control”, Journal of Cardiothoracic and Vascular Anesthesia, Feb. 28, 1989, vol. 3, No. 1, pp. 1-3.
Sheppard, Louis, Ph.D., “Computer Control of the Infusion of Vasoactive Drugs”, Annals of Biomedical Engineering, Jul. 1980, vol. 8, No. 4-6, pp. 431-444.
Sheppard, Louis, Ph.D., “The Application of Computers to the Measurement, Analysis, and Treatment of Patients Following Cardiac Surgical Procedures”, The University of Alabama in Birmingham, Oct. 31, 1977, pp. 297-300.
Sheppard, Louis, Ph.D., “The Computer in the Care of Critically Ill Patients”, Proceedings of the IEEE, Sep. 1979, vol. 67, No. 9, pp. 1300-1306.
“Sigma Spectrum: Operator's Manual”, Oct. 2009, pp. 72. http://static.medonecapital.com/manuals/userManuals/Sigma-Spectrum-Operator-Manual-October-2009.pdf.
Simonsen, Michael Ph.D., POC Testing, New Monitoring Strategies on Fast Growth Paths in European Healthcare Arenas, Biomedical Business & Technology, Jan. 2007, vol. 30, No. 1, pp. 1-36.
Siv-Lee et al., “Implementation of Wireless ‘Intelligent’ Pump IV Infusion Technology in a Not-for-Profit Academic Hospital Setting”, Hospital Pharmacy, Sep. 2007, vol. 42, No. 9, pp. 832-840. http://www.thomasland.com/hpj4209-832.pdf.
Slack, W.V., “Information Technologies for Transforming Health Care”, https://www.andrew.cmu.edu/course/90-853/medis.dir/otadocs.dir/03ch2.pdf, Ch. 2, 1995, pp. 29-78.
Smith, Joe, “Infusion Pump Informatics”, CatalyzeCare: Transforming Healthcare, as printed May 12, 2011, pp. 2.
Sodders, Lisa, “A Center Keeps Medicine in Right Hands”, The Capital Journal, Dec. 4, 1999, pp. 1-2.
“Software Versioning”, Wikipedia.org, dated Oct. 16, 2011 in 11 pages, https://en.wikipedia.org/w/index.php?title=Software_versioning&oldid=455859110.
Stitt, F.W., “The Problem-Oriented Medical Synopsis: a Patient-Centered Clinical Information System”, Proceedings of the Annual Symposium on Computer Application in Medical Care, 1994, pp. 88-92.
Stokowski, Laura A. RN, MS, “Using Technology to Improve Medication Safety in the Newborn Intensive Care Unit”, Advances in Neonatal Care, Dec. 2001, vol. 1, No. 2, pp. 70-83.
Sutton et al., “The Syntax and Semantics of the PROforma Guideline Modeling Language”, Journal of the American Medical Informatics Association, Sep./Oct. 2003, vol. 10, No. 5, pp. 433-443.
Szeinbach et al., “Automated Dispensing Technologies: Effect on Managed Care”, Journal of Managed Care Pharmacy (JMCP), Sep./Oct. 1995, vol. 1, No. 2, pp. 121-127.
Szolovits et al., “Guardian Angel: Patient-Centered Health Information Systems”, Technical Report MIT/LCS/TR-604, Massachusetts Institute of Technology Laboratory for Computer Science, May 1994, pp. 39.
Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in Critically Ill Patients”, The New England Journal of Medicine, Nov. 8, 2001, vol. 345, No. 19, pp. 1359-1367.
Van Den Berghe, M.D., Ph.D., et al., “Intensive Insulin Therapy in the Medical ICU”, The New England Journal of Medicine, Feb. 2, 2006, vol. 354, No. 5, pp. 449-461.
Van Der Maas et al., “Requirements for Medical Modeling Languages”, Journal of the American Medical Informatics Association, Mar./Apr. 2001, vol. 8, No. 2, pp. 146-162.
Villalobos et al., “Computerized System in Intensive Care medicine”, Medical Informatics, vol. 11, No. 3, 1986, pp. 269-275.
Wilkins et al., “A Regular Language: The Annotated Case Report Form”, PPD Inc., PharmaSUG2011—Paper CD18, 2011, pp. 1-9.
Ying et al., “Regulating Mean Arterial Pressure in Postsurgical Cardiac Patients. A Fuzzy Logic System to Control Administration of Sodium Nitroprusside”, IEEE Engineering in Medicine and Biology Magazine, vol. 13, No. 5, Nov.-Dec. 1994, pp. 671-677.
Yue, Ying Kwan, “A Healthcare Failure Mode and Effect Analysis on the Safety of Secondary Infusions”, Thesis, Institute of Biomaterials and Biomedical Engineering, University of Toronto, 2012, pp. 168.
Yurkonis et al., “Computer Simulation of Adaptive Drug Infusion”, IEEE Transactions on Biomedical Engineering, vol. BME-34, No. 8, Aug. 1987, pp. 633-635.
Zakariah et al., “Combination of Biphasic Transmittance Waveform with Blood Procalcitonin Levels for Diagnosis of Sepsis in Acutely Ill Patients”, Critical Care Medicine, 2008, vol. 36, No. 5, pp. 1507-1512.
“Download”, Free On-Line Dictionary of Computing, as archived Jun. 16, 2010 in 1 page, http://web.archive.org/web/20100616010314/https://folddoc.org/download.
Edworthy, Judy, “Medical Audible Alarms: A Review”, Journal of the American Medical Informatics Association, vol. 20, No. 3, 2013, pp. 584-589.
“McKesson Automation and ALARIS Medical Systems Developing Point-of-Care Bar Coding Solution to Improve IV Medication Safety”, PR Newswire, NY, Dec. 9, 2002, pp. 4.
Ahn et al., To“wards Scalable Authentication in Health Services”, Eleventh IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, Jun. 2002, pp. 83-88.
Related Publications (1)
Number Date Country
20200035355 A1 Jan 2020 US
Provisional Applications (1)
Number Date Country
62703772 Jul 2018 US
Continuations (1)
Number Date Country
Parent PCT/US2019/041715 Jul 2019 US
Child 16512243 US