System and method for managing medical databases for patient care devices

• US 8,359,338 B2
• Filed: 07/30/2004
• Issued: 01/22/2013
• Est. Priority Date: 07/30/2004
• Status: Active Grant

• Current Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Original Assignee: Carefusion 303 Incorporated (Becton, Dickinson & Co)
• Inventors: Butterfield, Robert D., Jordan, Kathleen M.
• Primary Examiner(s): PANNALA, SATHYANARAYA R
• Application Number:
  US10/902,989
• Publication Number:
  US 20060026205A1
• Time in Patent Office: 3,098 Days
• Field of Search: 707/104.1, 707/965, 705/3
• US Class Current: 707/803
• CPC Class Codes: G16H 20/10 relating to drugs or medications, e.g. for ensuring correct administration to patients
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 70/20 relating to practices or guidelines

Abstract

A system and method for creating, managing and loading selected configuration datasets used to program a patient care device to have a selected behavior is provided. A common configuration database includes medical treatment guidelines and device operating characteristics for a plurality of patient care device types. A processor operatively connected to the configuration database is programmed to construct at least one device-specific configuration dataset for a selected device behavior from the common configuration database and load the device-specific dataset into the memory of a patient care device. Further, the device-specific configuration datasets may contain device communication information, including communication protocols and data structures, for a plurality of patient care devices types and behaviors to enable communication between patient care devices.

Claims

1. A universal configuration database (UCDB) comprising:

a protocol associated with a medication;

an institutionally established guideline associated with one of a plurality of treatment locations, wherein the guideline comprises a maximum dose rate;

a plurality of first data elements each comprising a device operating characteristic associated with one of the plurality of device types;

a plurality of second data elements each comprising device communication information associated with one of the plurality of device types; and

a device type module comprising a plurality of fields respectively associated with one of the plurality of device types, each field comprising at least one reference link to at least one of the data elements associated with the device type associated with the field;

wherein;

first and second datasets created from the UCDB respectively configure a first device type and a second device type to deliver the medication according to the protocol and the guideline,

delivery of the medication by the first device type when loaded with the first dataset is equivalent to delivery of the medication by the second device type when loaded with the second dataset, and

the second device type will not deliver the medication according to the protocol and the guideline when the second device type is loaded with the first dataset.

2. The UCDB of claim 1, wherein at least one of the data elements is identified by a unique pointer.

3. The UCDB of claim 1, wherein at least one of the data elements in the UCSB is shared by a plurality of device types.

4. The UCDB of claim 1, further comprising a plurality of third data elements each comprising a rule.

5. A patient care system that includes a plurality of patient care device types, the patient care system comprising:

a universal configuration database (UCDB) comprising;

a protocol associated with a medication;

an institutionally established guideline associated with one of a plurality of treatment locations, wherein the guideline comprises a maximum dose rate;

a plurality of device operating characteristics each associated with one of the plurality of device types;

a plurality of device communication elements each associated with one of the plurality of device types; and

a device type module comprising a plurality of fields respectively associated with one of the plurality of device types, each field comprising at least one reference link to at least one of the device operating characteristics and the device communication elements associated with the device type associated with the field; and

a loading tool configured to;

accept a designation of a first device type and a second device type, a medication, a protocol associated with the designated medication, and a treatment location;

obtain the appropriate device operating characteristics and device communication elements from the UCDB in accordance with the reference links;

build a first dataset and a second dataset that respectively configure the designated first device type and second device type to deliver the designated medication according to the designated protocol and implement the guideline associated with the designated treatment location from the obtained device operating characteristics and device communication elements;

load the first dataset into a patient care device of the first device type; and

load the second dataset into a patient care device of the second device type,

wherein delivery of the medication by the first device type when loaded with the first dataset is equivalent to delivery of the medication by the second device type when loaded with the second dataset, and the second device type will not deliver the medication according to the protocol and the guideline when the second device type is loaded with the first dataset.

6. The patient care system of claim 5, wherein:

more than one of the plurality of patient care device types are interchangeably usable to deliver a medication to a patient according to a protocol associated with the medication; and

the plurality of patient care device types each operate according to device-specific operating characteristics.

7. The patient care system of claim 6, wherein:

a first device type is related to a first type of infusion pump;

a second device type is related to a second type of infusion pump that is different from the first type infusion pump;

the first and second types of pumps can be used interchangeably to deliver the medication to a patient according to the protocol associated with the medication; and

a dataset built for the first type of infusion pump cannot be used with the second type of infusion pump.

8. The patient care system of claim 5, wherein a dataset built by the loading tool for a first patient care device type cannot be loaded into any other patient care device type.