TECHNICAL FIELD

The present disclosure is generally directed to systems and methods for controlling a plurality of drug libraries, and in particular systems and methods for controlling a plurality of drug libraries on a plurality of patient devices, such as infusion pumps.

BACKGROUND

Infusion pumps are used to administer drugs and other medicaments to patients. For example, an infusion pump may administer a controlled amount of the medicament over time to the patient. The amount is administered pursuant to parameters entered by a clinician into the pump using a pump user interface.

Drug libraries are used on infusion pumps to provide further configuration beyond the software released by the manufacturer of the device. Drug libraries can include drug names, doses, and limits to the upper and/or lower ranges of administration parameters, for example. Conventionally, drug libraries may be maintained separately on each individual infusion pump.

While drug libraries are desirable, they pose certain challenges where a number of infusion pumps are owned, maintained and/or administered by a single entity. For example, if the limits to the upper and/or lower ranges of administration parameters for a particular drug are to be adjusted, then a change must be made to each drug library on each individual infusion pump. This represents a considerable amount of time and expense to the owner/administrator of the pumps. Further complications arise where user-configurable drug libraries are available. While desirable from the standpoint of the individual patient, such user-configurable drug libraries may cause inconsistencies to occur within the drug libraries maintained on different infusion pumps of a single entity.

SUMMARY

In a first aspect, a system for controlling a plurality of drug libraries includes a computing device on which is stored a master drug library, the master drug library comprising a plurality of drug definitions. The system also includes a plurality of programmable patient devices coupled to the server, each patient device having an individual drug library stored thereon, the individual drug library comprising a reference only to at least one of the drug definitions in the master drug library.

In a second aspect, a method for controlling a plurality of drug libraries includes storing on a computing device a master drug library, the master drug library comprising a plurality of drug definitions. The method also includes storing on each of a plurality of programmable patient devices an individual drug library, the individual drug library comprising a reference only to at least one of the drug definitions in the master drug library.

DESCRIPTION OF THE DRAWINGS

Fig. 1 is a schematic of a system including a server with a master drug library, an associated computer and a plurality of infusion pumps, each pump having its own individual drug library.

Fig. 2 is a schematic of the relationship between a master drug library, or list, which may be maintained on a server, for example, and a plurality of individual drug libraries, each of which may be maintained on an infusion pump, for example.

Fig. 3 is a flow chart illustrating a method of adding, modifying and deleting drug definitions and therapy definitions associated with a master drug library.

Fig. 4 is a simulated screenshot of a plurality of drug definitions maintained in the master drug library.

Fig. 5 is a simulated screenshot of a definition for one of the drugs within the master drug library.

Fig. 6 is a simulated screenshot of a plurality of individual drug libraries associated by or to be associated by reference to a drug definition in the master drug library. Fig. 7 is a simulated screenshot of one of the individual drug libraries and the drug definitions associated therewith.

Fig. 8 is a flow chart illustrating the method of administrating individual drug libraries associated with a master drug library.

DETAILED DESCRIPTION

A more detailed description of the systems and methods in accordance with the present disclosure is set forth below. It should be understood that the description below of specific devices and methods is intended to be exemplary, and not exhaustive of all possible variations or applications. Thus, the scope of the disclosure is not intended to be limiting, and should be understood to encompass variations or embodiments that would occur to persons of ordinary skill.

Fig. 1 illustrates a system of networked devices, including a computing device, such as a server, 100, a network 102 (which may include conventional equipment for defining a network, including servers, gateways, and routers, for example), and a plurality of patient devices, such as infusion pumps, 104, 106, 108. The system also includes a computer 1 10 that provides a user (e.g., an administrator) access to the server 100 to administer a master drug database 1 12 that resides on the server 100. As illustrated, the computer 1 10 may be coupled to the server 100 via the network 102, or optionally may have a more directly coupling to the server 100.

The server 100, the infusion pumps 104, 106, 108 and the computer 1 10 may include a microprocessor (which, in fact may include multiple physical and/or virtual processors). According to other embodiments, the server 100, the infusion pumps 104, 106, 108 and the computer 1 10 may include one or more electrical circuits designed to carry out the actions described herein. In fact, the server 100, the infusion pumps 104, 106, 108 and the computer 1 10 may include a microprocessor and other circuits or circuitry. In addition, the server 100, the infusion pumps 104, 106, 108 and the computer 1 10 may include one or more memories. The instructions by which the microprocessor is programmed may be stored on the one or more memories associated with the microprocessor, which memory/memories may include one or more tangible non-transitory computer readable memories, having computer executable instructions stored thereon, which when executed by the microprocessor, may cause the microprocessors to carry out one or more actions as described below. Each of the infusion pumps 104, 106, 108 has an individual drug library 1 14, 1 16, 1 18. The drug libraries 1 14, 1 16, 1 18 are associated to the master drug library 1 12 according to the methods described in greater detail in Figs. 3 and 8. A general schematic of the association between the master drug library (or list) 1 12 and the individual drug libraries 1 14, 1 16, 1 18 is illustrated in Fig. 2. As illustrated in Fig. 2, the master drug library 1 12 includes a definition 120 for each drug, which definition 120 may have one or more definitions 122 associated therewith for each therapy associated with the drug. As illustrated in Fig. 2, the assignment of the drug (and associated therapies) to the individual drug libraries 1 14, 1 16, 1 18 occurs by adding a reference 124 (and only the reference 124) to the individual drug library 1 14, 1 16, 1 18 to the drug definition 120 of the drug in the master drug library 1 12.

The system and method described in general terms with reference to Figs. 1 and 2 limits or eliminates duplication of data and information about drugs and their therapies that are included in each of the different individual drug libraries 1 14, 1 16, 1 18. Specifically, the master drug library 1 12 acts as a central repository in which all drugs and their therapies are defined. Once the required drugs and therapies have been defined, they can be added to individual drug libraries 1 14, 1 16, 1 18 by inclusion of a reference in the libraries 1 14, 1 16, 1 18. The inclusion of a reference in the libraries 1 14, 1 16, 1 18 limits or eliminates the need to copy and store the actual drug/therapy data in multiple places, thereby improving data integrity. In addition, changes made in the master drug library 1 12 will be applied to all of the individual drug libraries 1 12, 1 14, 1 16 because the master drug library represents a single source for this information.

The definition of the drug stored in the master drug library may include such identifying information as its name and concentration, for example. The number of drug definitions maintained in the drug library may be controlled by a system configuration parameter. Each drug definition may support one or more therapy definitions; it is also possible for a drug definition to support no therapy definitions. A therapy definition may include such identifying information as infusion modes, particular protocols, and limits on the infusion rates.

Fig. 3 illustrates a flow chart of how an administrator, via the computer 1 10, may add (create), modify, or delete a drug definition within the master drug library 1 12. Further, the flow chart of Fig. 3 illustrates how an administrator may add (create), modify or delete a therapy definition associated with one of the drug definitions. Fig. 4 illustrates how the information regarding the drug definitions included in one embodiment of a master drug library 1 12 may be displayed to a user, such as an administrator, via an electronic display device associated with the computer 1 10. In particular, the embodiment of the master drug library 1 12 includes a plurality of drug definitions, each identified by a drug name to the user. While a generic name has been used (e.g.,“DRUG 1”) for purposes of illustration in Fig. 4, the specific name of the drug may be used instead. In addition, information such as the number of drug libraries that refer to the drug definition and the number of therapy definitions associated with the drug definition may also be displayed, as has been included in Fig. 4.

Fig. 5 illustrates how the information regarding a particular drug definition (in this case, the definition for DRUG 2) may be displayed to a user, such as an administrator, via an electronic display device associated with the computer 1 10. In particular, the illustrated embodiment of the drug definition includes data regarding the dilutions or concentration of the drug, and the associated therapy definitions. In fact, the displayed information may also include information regarding the associated therapy definitions, such as the therapy definition displayed that includes data on the nature of the patient device (e.g., infusion device) and the dilutions/concentrations permitted. While a generic name has been used (e.g.,“DEVICE 1”) for purposes of illustration in Fig. 4, the specific name of the device may be used instead.

Assuming that a particular drug definition is ready to be included in individual drug libraries, the user may define individual drug libraries including this drug definition. In this regard, Fig. 6 illustrates how a list of the available individual drug libraries may be displayed to the user, for example via an electronic display device associated with the computer 1 10. Again, while a generic name has been used (e.g.,“LIBRARY 1”) for purposes of illustration in Fig. 4, the specific name of the library may be used instead. The user may use an input device, such as a pointing device (e.g., a mouse) or a keyboard, to select one of the drug libraries. Additionally, Fig. 7 illustrates how the information on the individual drug library selected by the user may be displayed to the user, for example via an electronic display device associated with the computer 1 10. As is illustrated, the drug definitions available for association with an individual drug library 1 14, 1 16, 1 18 may be displayed, as well as some information regarding the associated therapy definitions (e.g., the number of such definitions). As noted above, once the reference 124 to a drug definition is added to an individual drug library 1 14, 1 16, 1 18, any updates made to the definitions of the drug or its associated therapies in the master drug library will be reflected immediately in all individual drug libraries that include reference to that drug definition. In a similar fashion, a reference to a therapy definition in an individual drug library will associate that therapy definition with the individual drug library.

Fig. 8 illustrates a method of administering individual drug libraries associated with a master drug library. The method of Fig. 8 includes associating (by creating or by importing) the individual drug libraries, as well as modifying the individual drug libraries adding or removing drug definitions or therapy definitions to the individual drug library. The method further incudes other actions that may be taken relative to a particular individual drug library, such as duplicating the drug library, exporting the drug library, or printing an electronic or hard copy of the drug library.