Drug library compiler for patient devices

Patent metadata

Field	Value
Publication number	US-12308102-B2
Application number	US-201917054451-A
Country	US
Kind code	B2
Filing date	Apr 4, 2019
Priority date	May 14, 2018
Publication date	May 20, 2025
Grant date	May 20, 2025

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.

First claim

The invention claimed is:

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 disposed within a healthcare facility and configured to:
read the drug library;
identify a type of patient device from a plurality of locally prestored patient device types and prompt the user to load a new compiler program when a patient device type is not recognized among the plurality of locally prestored patient device types;
receive the new compiler program for a new patient device type and store the new compiler program with a plurality of locally prestored compiler programs;
select a compiler program from the plurality of locally prestored compiler programs, each locally 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.

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

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

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

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

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

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

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

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

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

11. 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 locally prestored patient device types and prompting the user to load a new compiler program when a patient device type is not recognized among the plurality of locally prestored patient device types;
receiving the new compiler program for a new patient device type and storing the new compiler program with a plurality of locally prestored compiler programs,
selecting a compiler program from the plurality of locally prestored compiler programs, each locally 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 within a healthcare facility;
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.

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

13. The method of claim 11 , 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.

14. The method of claim 13 , 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.

15. The method of claim 14 , 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.

16. The method of claim 11 , 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.

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

18. The method of claim 11 , 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.

19. 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 disposed within a healthcare facility and configured to:
identify a type of infusion pump from a plurality of locally prestored infusion pump types and prompt the clinician to load a new compiler program when an infusion pump type is not recognized among the plurality of locally prestored infusion pump types;
receive the new compiler program for a new infusion pump type and store the new compiler program with a plurality of locally prestored compiler programs:
select a compiler program from the plurality of locally prestored compiler programs, each locally p

Assignees

• Fresenius Vial Sas

Inventors

• Moskal Witold

Classifications

• G06F8/30

  Creation or generation of source code · CPC title

• G06F8/41

  Compilation · CPC title

• G16H20/13

  delivered from dispensers · CPC title

• G16H20/17 Primary

  delivered via infusion or injection · CPC title

• G16H40/67 Primary

  for remote operation · CPC title