# US 11,309,070 B2 · Drug library manager with customized worksheets

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,309,070 B2
- Document ID: US11309070B2
- Status: Granted
- Kind: B2
- Application number: 16/512,243
- Filed: 2019-07-15
- Published: 2020-01-30
- Granted: 2022-04-19
- Earliest claimed: 2018-07-26
- Assignees: ICU Medical, Inc.
- Applicants: ICU Medical, Inc.
- Inventors: Ben Xavier; Dennis Krabbe; Timothy Kil; Jody Polk; Aaron Fields-Cypress; Julius Tobias
- Web page: https://patentgrep.com/patent/US11309070B2

## CPC

- G16H 20/17: delivered via infusion or injection
- A61M 5/142: Pressure infusion, e.g. using pumps
- A61M 5/172: electrical or electronic
- G06F 16/252: {between a Database Management System and a front-end application}
- G16C 20/62: Design of libraries
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 40/40: for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
- G16H 70/40: relating to drugs, e.g. their side effects or intended usage
- A61M 2005/14208: {with a programmable infusion control system, characterised by the infusion program}
- A61M 2205/3553: remote, e.g. between patient's home and doctor's office
- A61M 2205/3584: using modem, internet or Bluetooth®
- A61M 2205/3592: using telemetric means, e.g. radio or optical transmission
- A61M 2205/50: with microprocessors or computers
- A61M 2205/52: with memories providing a history of measured variating parameters of apparatus or patient
- A61M 2205/6009: for matching patient with his treatment, e.g. to improve transfusion security
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- A61M: DEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY (introducing media into or onto the bodies of animals A61D7/00; means for inserting tampons A61F13/26; devices for administering food or medicines orally A61J; containers for collecting, storing or administering blood or medical fluids A61J1/05); DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY (surgery A61B; chemical aspects of surgical articles A61L); DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR {(Electrotherapy, e.g. producing anaesthesia by the use of alternating or intermittent currents A61N1/36021)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- G16C: COMPUTATIONAL CHEMISTRY; CHEMOINFORMATICS; COMPUTATIONAL MATERIALS SCIENCE

## 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.

## Claims

### Claim 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; and
a 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; and
wherein 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; and
provide, to a connectivity adapter in communication with the first infusion pump and the second infusion pump, the generalized drug library data; and
wherein 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; and
merge data from the standardized message with data representing a current state of the first infusion pump.

### Claim 2 (depends on 1)

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.

### Claim 3 (depends on 1)

The system of claim 1, wherein the first infusion pump is configured to:
display infusion data comprising a medication name; and
transmit a second infusion message to the connectivity adapter, wherein the second infusion message comprises a medication identifier and does not comprise the medication name.

### Claim 4 (depends on 3)

The system of claim 3, wherein the connectivity adapter is configured to at least:
receive, from the first infusion pump, the second infusion message; and
determine the medication name using the medication identifier and the generalized drug library data.

### Claim 5 (depends on 1)

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; and
determine a second medication name using the second medication identifier and second generalized drug library data associated with the second infusion pump.

### Claim 6 (depends on 1)

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; and
the second upper dosing limit overrides the first upper dosing limit during administration of the medication by the first infusion pump.

### Claim 7 (depends on 1)

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; and
the first upper dosing limit is implemented during administration of the medication by the first infusion pump.

### Claim 8 (depends on 1)

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; and
store, in the drug library database, administration rule data representing the selection, wherein the administration rule data references medication data representing the medication.

### Claim 9 (depends on 1)

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; and
receive, 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.

### Claim 10 (depends on 1)

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.

### Claim 11 (depends on 10)

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; and
generate user interface data for displaying a difference based on comparing the generalized drug library data.

### Claim 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; and
wherein 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; and
sending, by the connectivity adapter, the standardized message to a server.

### Claim 13 (depends on 12)

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; and
presenting, by the drug library manager, a user interface displaying a difference between the generalized drug library data and the archived generalized drug library data.

### Claim 14 (depends on 12)

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; and
storing, 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.

### Claim 15 (depends on 12)

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; and
receiving, 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.

### Claim 16 (depends on 12)

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.

### Claim 17

A system comprising:
a drug library manager comprising one or more computing device; and
a 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; and
wherein 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, and
wherein 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; and
send the standardized message to a server.

### Claim 18 (depends on 17)

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; and
process the second infusion message using the prior version of generalized drug library data.

### Claim 19 (depends on 1)

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; 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; and
receive, from the user device, fourth input data representing selection of a first clinical care area of the one or more clinical care areas.

### Claim 20 (depends on 17)

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.