# US 2021/0233638 A1 · Drug library compiler for patient devices

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

- Number: US 2021/0233638 A1
- Document ID: US20210233638A1
- Status: Published application
- Kind: A1
- Application number: 17/054,451
- Filed: 2019-04-04
- Published: 2021-07-29
- Earliest claimed: 2018-05-14
- Assignees: Fresenius Vial SAS
- Applicants: Fresenius Vial SAS
- Inventors: Witold Moskal
- Web page: https://patentgrep.com/patent/US20210233638A1

## CPC

- G16H 20/17: delivered via infusion or injection
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- G16H 40/67: for remote operation
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA

## Abstract

A compiler system and method for providing a drug library to patient devices includes a memory and a processing circuit. The memory stores a drug library in a first format, the drug library comprising drug data to be used by software on the patient devices to program the patient devices to administer a drug to a patient according to a protocol determined at least in part by a user. The processing circuit configured to identify a type of patient device from prestored patient device types and select a compiler program from prestored compiler programs. The selected program is used translate the drug library from the first format into a selected second format. The translated drug library is stored in the second format and distributed to a patient device of the identified type.

## Claims

### Claim 1

A compiler system for providing a drug library to patient devices, comprising:
a memory configured to store a drug library in a first format, the drug library comprising drug data to be used by software on the patient devices to program the patient devices to administer a drug to a patient according to a protocol determined at least in part by a user; and
a processing circuit configured to:
read the drug library;
identify a type of patient device from a plurality of prestored patient device types;
select a compiler program from a plurality of prestored compiler programs, each prestored compiler program configured to compile the drug library from the first format into a respective second format, each second format being different for each type of patient device;
use the compiler program selected to translate the drug library from the first format into a selected second format;
store the drug library in the selected second format; and
distribute the drug library in the selected second format to a patient device of the type identified.

### Claim 2 (depends on 1)

The compiler system of claim 1, wherein the first format is a source code format and the selected second format is a code format having a lower level than the source code format.

### Claim 3 (depends on 1)

The compiler system of claim 1, wherein the patient device of the type identified is an infusion pump selected from the group comprising a syringe infusion pump and a volume-type infusion pump.

### Claim 4 (depends on 1)

The compiler system of claim 1, further comprising:
a drug library editor workspace comprising a first dedicated user interface configured to receive drug library parameters from a pharmacist; and
a release workspace comprising a second dedicated user interface configured to release the drug library in the selected second format to the patient device.

### Claim 5 (depends on 4)

The compiler system of claim 4, wherein the drug library editor workspace comprises a first dedicated database and first defined entry and exit criteria for a user, wherein the release workspace comprises a second dedicated database and second defined entry and exit criteria for a user.

### Claim 6 (depends on 5)

The compiler system of claim 5, wherein the release workspace is configured to generate a release report based on the drug library in the selected second format and to receive a sign-off authorization via the second dedicated user interface from the user.

### Claim 7 (depends on 6)

The compiler system of claim 6, wherein the release workspace is configured to store and release the drug library in the selected second format in a read-only format if a sign-off authorization has been received.

### Claim 8 (depends on 1)

The compiler system of claim 1, wherein the processing circuit is configured to translate the drug library in the first format to a plurality of different second formats using different patient device-type compiler programs for different respective patient device types.

### Claim 9 (depends on 1)

The compiler system of claim 1, further comprising a linker configured to link a plurality of drug libraries into a binary data set for the type of patient device identified.

### Claim 10 (depends on 1)

The compiler system of claim 1, wherein the processing circuit is configured to receive a new compiler program for a new patient device type and to store the new compiler program with the plurality of prestored compiler programs.

### Claim 11 (depends on 1)

The compiler system of claim 1, wherein the patient devices are clinician-programmable infusion pumps, wherein the drug library comprises hard and soft limits for parameters to be programmed by a clinician.

### Claim 12

A method of providing a drug library to patient devices, comprising:
storing a drug library in a first format, the drug library comprising drug data to be used by software on the patient devices to program the patient devices to administer a drug to a patient according to a protocol determined at least in part by a user;
reading the drug library;
identifying a type of patient device from a plurality of prestored patient device types;
selecting a compiler program from a plurality of prestored compiler programs, each prestored compiler program configured to compile the drug library from the first format into a respective second format, each second format being different for each type of patient device;
using the compiler program selected to translate the drug library from the first format into a selected second format;
storing the drug library in the selected second format; and
distributing the drug library in the selected second format to a patient device of the type identified.

### Claim 13 (depends on 12)

The method of claim 12, wherein the first format is a source code format and the selected second format is a machine code format.

### Claim 14 (depends on 12)

The method of claim 12, further comprising:
receiving drug library parameters from a pharmacist via a first dedicated user interface of a drug library editor; and
releasing the drug library in the selected second format to the patient device via a second dedicated user interface.

### Claim 15 (depends on 14)

The method of claim 14, further comprising using the second dedicated interface to generate a release report based on the drug library in the selected second format and to receive a sign-off authorization from the user.

### Claim 16 (depends on 15)

The method of claim 15, further comprising storing and releasing the drug library in the selected second format in a read-only format if a sign-off authorization has been received from the user.

### Claim 17 (depends on 12)

The method of claim 12, further comprising translating the drug library in the first format to a plurality of different second formats using different patient device-type compiler programs for different respective patient device types.

### Claim 18 (depends on 12)

The method of claim 12, further comprising linking a plurality of drug libraries into a binary data set for the identified type of patient device identified.

### Claim 19 (depends on 12)

The method of claim 12, further comprising receiving a new compiler program for a new patient device type and storing the new compiler program with the plurality of prestored compiler programs, wherein the patient devices are clinician-programmable infusion pumps, wherein the data set comprises hard and soft limits for parameters to be programmed by a clinician.

### Claim 20

A computer system for providing a drug library to infusion pumps, comprising:
a compiler circuit comprising:
a memory configured to store a drug library in a source code format, the drug library comprising drug data to be used by software already programmed on the infusion pumps to program the infusion pumps to administer a drug to a patient according to a protocol determined at least in part by a clinician, wherein the drug library comprises hard and soft limits for parameters to be programmed by the clinician; and
a processing circuit configured to:
identify a type of infusion pump from a plurality of prestored infusion pump types;
select a compiler program from a plurality of prestored compiler programs, each prestored compiler program configured to compile the drug library from the source code format into a respective machine code format, each machine code format being different for each type of infusion pump;
use the complier program selected to translate the drug library from the source code format into a selected machine code format;
store the drug library in the selected machine code format; and
distribute the drug library in the selected machine code format to a patient device of the type identified;
a drug library editor circuit comprising a first dedicated user interface configured to receive drug library parameters from a pharmacist; and
a release circuit comprising a second dedicated user interface configured to release the translated drug library in the second format to the infusion pump of the identified type.
