US20020091454A1 - Remotely programmable infusion system - Google Patents

Remotely programmable infusion system Download PDF

Info

Publication number
US20020091454A1
US20020091454A1 US10/097,552 US9755202A US2002091454A1 US 20020091454 A1 US20020091454 A1 US 20020091454A1 US 9755202 A US9755202 A US 9755202A US 2002091454 A1 US2002091454 A1 US 2002091454A1
Authority
US
United States
Prior art keywords
remote
programmable
protocol
infusion system
mode
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
US10/097,552
Other versions
US6749586B2 (en
Inventor
Robert Vasko
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kimberly Clark Worldwide Inc
Original Assignee
Vasko Robert S.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US08/344,973 external-priority patent/US5573506A/en
Priority claimed from US09/626,571 external-priority patent/US6355018B1/en
Application filed by Vasko Robert S. filed Critical Vasko Robert S.
Priority to US10/097,552 priority Critical patent/US6749586B2/en
Publication of US20020091454A1 publication Critical patent/US20020091454A1/en
Application granted granted Critical
Priority to US10/868,662 priority patent/US7153289B2/en
Publication of US6749586B2 publication Critical patent/US6749586B2/en
Priority to US11/608,167 priority patent/US20070100394A1/en
Assigned to KIMBERLY-CLARK WORLDWIDE, INC. reassignment KIMBERLY-CLARK WORLDWIDE, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: I-FLOW CORPORATION
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/142Pressure infusion, e.g. using pumps
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M5/00Devices for bringing media into the body in a subcutaneous, intra-vascular or intramuscular way; Accessories therefor, e.g. filling or cleaning devices, arm-rests
    • A61M5/14Infusion devices, e.g. infusing by gravity; Blood infusion; Accessories therefor
    • A61M5/168Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body
    • A61M5/172Means for controlling media flow to the body or for metering media to the body, e.g. drip meters, counters ; Monitoring media flow to the body electrical or electronic
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/04Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/10Programme control other than numerical control, i.e. in sequence controllers or logic controllers using selector switches
    • G05B19/106Programme control other than numerical control, i.e. in sequence controllers or logic controllers using selector switches for selecting a programme, variable or parameter
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • G16H20/17ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients delivered via infusion or injection
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00General characteristics of the apparatus
    • A61M2205/35Communication
    • A61M2205/3546Range
    • A61M2205/3553Range remote, e.g. between patient's home and doctor's office
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00General characteristics of the apparatus
    • A61M2205/35Communication
    • A61M2205/3546Range
    • A61M2205/3569Range sublocal, e.g. between console and disposable
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00General characteristics of the apparatus
    • A61M2205/35Communication
    • A61M2205/3576Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
    • A61M2205/3584Communication with non implanted data transmission devices, e.g. using external transmitter or receiver using modem, internet or bluetooth
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00General characteristics of the apparatus
    • A61M2205/35Communication
    • A61M2205/3576Communication with non implanted data transmission devices, e.g. using external transmitter or receiver
    • A61M2205/3592Communication with non implanted data transmission devices, e.g. using external transmitter or receiver using telemetric means, e.g. radio or optical transmission
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00General characteristics of the apparatus
    • A61M2205/50General characteristics of the apparatus with microprocessors or computers
    • A61M2205/502User interfaces, e.g. screens or keyboards
    • A61M2205/505Touch-screens; Virtual keyboard or keypads; Virtual buttons; Soft keys; Mouse touches
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2205/00General characteristics of the apparatus
    • A61M2205/58Means for facilitating use, e.g. by people with impaired vision
    • A61M2205/581Means for facilitating use, e.g. by people with impaired vision by audible feedback
    • AHUMAN NECESSITIES
    • A61MEDICAL OR VETERINARY SCIENCE; HYGIENE
    • A61MDEVICES FOR INTRODUCING MEDIA INTO, OR ONTO, THE BODY; DEVICES FOR TRANSDUCING BODY MEDIA OR FOR TAKING MEDIA FROM THE BODY; DEVICES FOR PRODUCING OR ENDING SLEEP OR STUPOR
    • A61M2209/00Ancillary equipment
    • A61M2209/01Remote controllers for specific apparatus
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/23Pc programming
    • G05B2219/23039Remote programmer
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/23Pc programming
    • G05B2219/23386Voice, vocal command or message
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/24Pc safety
    • G05B2219/24172Use of second password, different from first
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/20Pc systems
    • G05B2219/26Pc applications
    • G05B2219/2607Infusion controller
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S128/00Surgery
    • Y10S128/904Telephone telemetry

Definitions

  • the present invention relates to a remotely programmable infusion system for medical applications. More particularly, the present invention relates to an infusion system for delivering a variety of medicines and fluids that sends voice commands and queries to a remote touch-tone transceiver and that can be programmed by pressing keys on the keypad of the remote touch-tone transceiver in response to the commands and queries.
  • Infusion devices are used in the medical field to administer and deliver medicines and other fluids to a patient.
  • Today due in part to rising health costs and the high cost of hospital rooms, and in part to the desire to provide comfort and convenience to patients, the medical industry has promoted in-home care for patients suffering from various maladies. Particularly, many patients require delivery and administration of medicines or other IV fluids on a regular basis. Delivery and administration is accomplished via a variety of infusion devices, such IV pumps and gravity pumps and other types of IV administration.
  • IV pumps and gravity pumps and other types of IV administration.
  • a home infusion device can be monitored and reprogrammed.
  • one system employs a patient activated switch on a diagnostic apparatus that causes automatic dialing of a telephone number corresponding to a care provider remote from the diagnostic apparatus. This enables the patient to communicate with the care provider through a speaker and microphone on the diagnostic apparatus, permitting interactive communication with the care provider regarding the routines to be performed by the diagnostic apparatus.
  • This system merely provides the capability for the care provider to monitor the infusion device, but does not offer the capacity to remotely reprogram the infusion device.
  • Another remote monitoring system employs a user interface for programming blood pressure testing protocol into, and downloading blood pressure data from, ambulatory blood pressure monitoring units.
  • the user interface is connected to a central processing computer via a telephone line.
  • Control units located at the blood pressure testing site transfer blood pressure data to the central computer, which generates comprehensive medical reports for specific patients, but which cannot transmit reprogramming signals back to the control unit.
  • the infusion device has a delivery unit for delivering the medicinal solution and a removable logic unit for controlling operation of the delivery unit.
  • the logic unit is either attached to or separate from the delivery unit, and the latter can be worn by the patient.
  • the logic unit is connected to a programming computer via a telephone line.
  • the computer can be used to program the logic unit with a logic configuration suitable for operating the delivery unit in accordance with the intended delivery requirements.
  • the present invention is directed to a remotely programmable infusion system and a method for remotely programming an infusion system via a remote transceiver that substantially obviates one or more of the problems due to limitations and disadvantages of the related art.
  • the present invention defines a remotely programmable infusion system having a programmable protocol, the infusion system being remotely programmable by a remote touch-tone transceiver.
  • the remotely programmable infusion system comprises a memory for storing a programmable protocol and a remote communication port for sending a voice signal to the remote touch-tone transceiver and for receiving a remote programming signal from the remote touch-tone transceiver.
  • the remotely programmable infusion system also comprises a voice storage unit for storing the voice signal and a processor, coupled to the remote communication port and to the voice storage unit and to the memory, for accessing the voice signal from the voice storage unit and the programmable protocol from the memory, and for processing the programmable protocol in response to receiving the remote programming signal.
  • the present invention defines a method for remotely programming an infusion system.
  • the infusion system has a voice storage unit for storing a voice signal and has a programmable protocol and is remotely programmable by a remote touch-tone transceiver.
  • the method comprises several steps: establishing a connection between the infusion system and the remote touch-tone transceiver; accessing the voice signal from the voice storage unit in response to establishing the connection; sending the voice signal to the remote touch-tone transceiver; receiving a remote programming signal from the remote touch-tone transceiver; and processing the programmable protocol in response to receiving the remote programming signal.
  • the present invention comprises a remotely programmable infusion system having a programmable protocol stored in a protocol memory, the remotely programmable infusion system being programmable by a remote touch-tone transceiver.
  • the infusion system comprises an infusion pump for delivering fluids to a patient.
  • the infusion pump has an infusion data port.
  • the infusion system also comprises a homebase unit, coupled to the infusion communication port on the infusion pump via a homebase data port, for processing the programmable protocol.
  • the homebase unit comprises a voice storage unit for storing a voice signal and a remote communication port for sending the voice signal to the remote touch-tone transceiver and for receiving a dual-tone multi-frequency (DTMF) signal from the remote touch-tone transceiver.
  • the homebase unit further comprises a processor, coupled to the remote communication port, to the voice storage unit, and to the protocol memory, for accessing the voice signal from the voice storage unit, for accessing the programmable protocol from the protocol memory, and for processing the programmable protocol to obtain a processed programmable protocol in response to the DTMF signal.
  • the processed programmable protocol is relayed from the processor to the infusion pump via the homebase data port and the infusion data port.
  • FIG. 1 is a diagrammatical representation of the programmable infusion system of the present invention.
  • FIG. 2 is a block diagram of the homebase unit in accordance with the present invention.
  • FIG. 3 is a flow diagram illustrating entry of an access code and the main menu in an example of the present invention.
  • FIG. 4 is a flow diagram illustrating an access code menu in accordance with an example of the present invention.
  • FIG. 5 is a flow diagram illustrating a review mode menu in accordance with an example of the present invention.
  • FIG. 6 is a flow diagram illustrating an edit mode menu in accordance with an example of the present invention.
  • FIG. 7 is a flow diagram illustrating sub-menus of the edit mode menu in accordance with an example of the present invention.
  • FIGS. 8A and 8B represent a flow diagram illustrating a programming mode menu in accordance with an example of the present invention.
  • FIG. 9 is a flow diagram illustrating sub-menus of the programming mode menu in accordance with an example of the present invention.
  • FIG. 10 is a table illustrating the alarm functions that can be employed in the system of the present invention.
  • a remotely programmable infusion system that allows remote programming of the infusion system from a remotely located transceiver, such as a push-button telephone.
  • the remotely programmable infusion system includes a memory and a voice storage unit.
  • the infusion system also includes a remote communication port, as well as a processor that is coupled to the remote communication port, the voice storage unit, and the memory.
  • programming is generalized terms that refer to a host of operations, functions, and data manipulation. Those terms, therefore, are not to limited herein to editing and deleting data, parameters, protocol, and codes.
  • programming and processing may encompass editing, changing, erasing, entering, re-entering, viewing, reviewing, locking, and inserting functions.
  • FIG. 1 An exemplary embodiment of the apparatus of the present invention is shown in FIG. 1 and is designated generally by reference numeral 10 .
  • the remotely programmable infusion system 10 includes a pump unit 12 and a homebase 14 .
  • the pump unit 12 and homebase 14 may be two separate units, as illustrated in FIG. 1, or may comprise a single integral unit housing both the pump 12 and the homebase 14 . With both elements integrated into a single infusion device, the device may be entirely portable and programmable, both via local and remote programming devices.
  • the pump unit 12 includes a housing 16 that contains the electrical and mechanical elements of the pump unit 12 .
  • An example of a pump unit 12 that can be used in the present invention is disclosed in U.S. Pat. No. 5,078,683, assigned to the assignee of the present invention.
  • the pump unit 12 also includes an infusion line 18 that is connected to a patient at end 19 .
  • the pump unit 12 further includes a display 20 and various controls 22 .
  • the homebase 14 includes a cradle 24 for holding the pump unit 12 , a cable for connecting the homebase 14 to the pump unit 12 , controls 26 for controlling operation of the homebase 14 , display lights 28 for indicating various conditions of the homebase 14 , and an internal audio device 29 for providing audio alarm signals.
  • the controls 26 include a link button 30 , a local button 32 , and a send button 34 .
  • the display lights 28 include a wait light 36 , a phone light 38 , and an alarm light 40 . The function of the controls 26 and the display lights 28 will be described in detail below.
  • the homebase 14 also includes a remote communication port 42 and a local communication port 44 .
  • the homebase 14 and pump 12 are interconnected by an infra-red communications link 46 , 48 .
  • the remote communication port 42 and the local communication port 44 each comprise a standard modem, as is well known in the art.
  • the modem module of the present invention is a Cermetek modem No. CH1785 or CH1782. These modem modules may operate at 2400 baud or other baud rates. Other baud rates, however, can also be employed in the present invention.
  • the local button 32 is used to activate the local communication port 44 . For example, when the care provider is at the premises where the infusion system 10 is located, the care provider presses the local button 32 , thereby activating the local communication port 44 .
  • the care provider can then communicate with the homebase 14 via a local telephone (not shown) at the premises that is connected to the local communication port 44 . If, on the other hand, the care provider is at a location remote from the infusion system 10 , the link button 30 is pressed, activating the remote communication port 42 . In this way, the care provider can communicate with the homebase 14 via a telephone (or other such transceiver) located at the remote location.
  • touch-tone transceiver is not limited to conventional push-button telephones having a 12 key keypad, with 0-9, “*”, and “#” keys.
  • touch-tone transceiver refers to any transceiver capable of generating signals via a keyboard or other data entry system and thus is not limited to transceivers that generate DTMF signals, such as conventional telephones.
  • Examples of “touch-tone transceivers” as defined herein include conventional push-button telephones, computers having a keyboard and/or mouse, transmitters that convert human voice to pulse or digital or analog signals, and pager transceivers.
  • the homebase data port 46 and pump data port 48 comprise a wireless emitter/detector pair.
  • data ports 46 , 48 each comprise and infra-red emitter/detector, permitting wireless communication between the pump unit 12 and the homebase 14 .
  • Other wireless communications ports may be employed, however, or the pump unit 12 and the homebase 14 may have their data ports 46 , 48 hard-wired together.
  • the pump unit 12 and the homebase 14 may comprise a single unit, obviating the need for a wireless or hard-wired link between the two units.
  • a power cable 50 is preferably employed to provide power to the pump unit 1 2 via the homebase 14 .
  • the pump unit 12 may have its own power cable coupled directly to the power source, as opposed to being connected through the homebase 14 .
  • the homebase 14 comprises the remote communication port 42 , the local communication port 44 , a protocol memory 51 , a voice storage unit 52 , a processor 53 , a voice synthesizer 49 , and an access code memory 54 .
  • the protocol memory 51 , the voice storage unit 52 , and the access code memory 54 can all be contained in the same memory device (such as a random-access memory), or in separate memory units.
  • the voice storage unit 52 comprises a read-only memory (ROM)
  • the processor 53 comprises an 8-bit microcontroller, such as the Motorola MC68HC1 1 AOFN.
  • the homebase 14 also includes the data port 48 for relaying information between the homebase 14 and pump unit 12 .
  • the voice synthesizer 49 is preferably an integrated circuit that converts digitized voice signals to a signal that emulates the sound of a human voice. As embodied herein, the voice synthesizer 49 need only be used to convert the signals outgoing from the homebase 14 to the remote or local telephone and thus is not required for converting incoming signals from the remote or local telephone.
  • the voice synthesizer may comprise an LSI speech synthesis chip commercially available from Oki, part number MSM6585.
  • the remote communication port 42 , the local communication port 44 , and the homebase data port 48 are all coupled to the processor 53 via data buses 55 a, 56 a, 57 a, respectively.
  • the communication ports 42 , 44 receive signals from a transceiver (such as a telephone) and relay those signals over the buses 55 a, 56 a, respectively, to the processor 53 , which in turn processes the signals, performing various operations in response to those signals.
  • the processor 53 receives digitized voice signals from the voice storage unit 52 via bus 59 a and sends those digitized voice signals to the voice synthesizer 49 via bus 59 b, where the signals are converted human voice emulating signals.
  • Those human voice signals are sent from the voice synthesizer 49 via buses 55 b, 56 b, 57 b to buses 55 a, 56 a, 57 a, which in turn relay the those signals to the remote communication port 42 , the local communication port 44 , and the homebase data port 48 , respectively.
  • the processor 53 sends a voice address signal over a data bus 59 a coupling the processor 53 to the voice storage unit 52 .
  • the voice address signal corresponds to a location in the voice storage unit 52 containing a particular voice signal that is to be sent to the remote transceiver.
  • the particular voice signal is accessed from the voice storage unit 52 and sent, via the data bus 59 a, to the processor 53 .
  • the processor 53 then relays the voice signal via the data bus 59 b to the voice synthesizer 49 , which converts the voice signal and sends the converted signal via data buses 55 b and 55 a to the remote communication port 42 , which sends the converted signal to the remote transceiver.
  • the voice signal retrieved from the voice storage unit 52 may be a digitized representation of a person's voice or a computer generated voice signal (both being well known in the art).
  • the digitized voice signal is converted by the voice synthesizer 49 to a signal that emulates the sound of a human voice.
  • the voice signal instructs the care provider on how to respond to the voice signal and what type of information the care provider should send.
  • the remote transceiver may be a push-button telephone having a keypad with multiple keys, the care provider then presses the appropriate key or keys, thereby sending a DTMF signal back to the remote communication port 42 of the homebase 14 .
  • the remote transceiver need not be a push-button telephone, but rather any transceiver capable of sending and receiving DTMF or other similar signals.
  • the remote transceiver may be a computer or portable remote controller.
  • the DTMF signal sent by the care provider is a remote programming signal, which is transmitted from the remote telephone to the remote communication port 42 of the homebase 14 .
  • the remote communication port 42 then relays the remote programming signal via the data bus 55 a to the processor 53 .
  • the processor 53 accesses a particular parameter of the programming protocol from the protocol memory 51 .
  • the processor 53 transmits a protocol address signal over the data bus 58 that couples the processor 53 and the protocol memory 51 .
  • the protocol address signal corresponds to a location in the protocol memory 51 containing the parameter.
  • the parameter is then sent from the protocol memory 51 to the processor 53 over the data bus 58 .
  • the processor 53 can then perform one of a number of operations on the parameter, including editing, erasing, or sending the parameter back to the remote transceiver for review.
  • Those skilled in the art will recognize that many types of signals or commands can be sent from the remote transceiver to the homebase 14 for processing. Examples of such signals, how they are processed, and their effect will be described in detail below in conjunction with the description of the operation of the present invention.
  • the infusion system 10 can incorporate various security measures to protect against unwanted programming of the pump protocol.
  • a user access code can be used to block programming except by persons with the user access code, which may be a multi-digit number (preferably a four digit number).
  • the infusion system 10 can be equipped with one or multiple user access codes, which are stored in the access code memory.
  • a care provider is connected to the infusion system 10 via a remote conventional push-button telephone (not shown). This connection may be initiated by a call from the care provider to the infusion system 10 (or a patient talking on a telephone located near the infusion system 10 ), or by a call from the patient to the care provider.
  • the care provider is connected to the infusion system 10 .
  • the care provider is asked (via a voice signal stored in the voice storage unit 52 ) to enter the user access code. If the care provider enters a valid user access code (as explained above, there may be several valid codes), the care provider is permitted to access and/or program the pump protocol.
  • a programming signal is sent by the care provider (from, e.g., a remote push button telephone) to the homebase 14 . That programming signal is relayed by the remote communication port 42 to the processor 53 , which processes the signal and generates an access code address signal.
  • the access code address signal which corresponds to a memory location in access code memory 54 holding a user access code, is sent over a data bus 60 to the access code memory 54 . The particular user access code is then retrieved and sent back over the data bus 60 to the processor 53 , which processes the user access code in some manner.
  • the homebase is equipped with the homebase data port 48 .
  • the pump protocol can be sent from the homebase 14 to the pump 12 via the homebase data port 48 and the pump data port 46 .
  • the processor 53 accesses the protocol from the protocol memory 51 and sends the protocol via data bus 57 a to the homebase data port 48 .
  • the homebase data port 48 then sends the information over the infra-red link to the pump data port 46 , where it is processed by circuitry and/or software in the pump 12 .
  • the pump protocol can be programmed (e.g., edited, redone, reviewed, locked, re-entered, etc.).
  • the local button 32 is used to activate the local transceiver. If the care provider is located at the homebase 14 , and a local transceiver (e.g., a push-button telephone) is at that location and connected to the local communication port 44 , the local button 32 is depressed, activating the local communication port 44 and thereby providing a communication connection between the local telephone and the homebase 14 .
  • a local transceiver e.g., a push-button telephone
  • the send button 34 is designed to permit sending of the infusion system 10 protocol to a remote (or local) computer (not shown). In this way, a remote or local computer can maintain a file having the protocol of many infusion systems 10 located in various places and monitor those protocols. If the computer is remote from the infusion system 10 , a person located at the homebase 14 presses the send button 34 , which in turn downloads the existing protocol to the remote communication port 42 . The protocol is then transmitted via the remote communication port 42 to the remote computer.
  • the link button 30 is used to initiate a remote (or local) programming session, or, in other words, to enter the remote touch-tone programming mode of the infusion system 10 .
  • the care provider calls the telephone number corresponding to the infusion system 10 (or the patient's home phone). The call may ring at a local telephone coupled to the homebase 14 via the local communication port 44 .
  • the patient answers the call, and the care provider and patient can communicate between the remote and local telephones via standard voice signals. This is known herein as a phone mode or patient conversation mode.
  • the care provider then instructs the patient to depress the link button 30 , which disconnects the patient from the telephone line and initiates the programming mode described below with reference to FIGS. 3 - 9 .
  • the homebase may be equipped with an internal switching system that directly connects the care provider with the homebase 14 and initiates the programming mode.
  • the internal switching may be accomplished with hardware in the homebase 14 or with software that controls the processor 53 , or with a hardware-software combination. Either way, the care provider may then begin processing the information and protocol stored in the homebase 14 . (As described above, the call may be initiated by the patient to the care provider.)
  • the display lights 28 comprise LEDs.
  • the wait light 36 indicates when the homebase 14 is involved in a programming session or when its is downloading the protocol to the remote computer. Accordingly, the wait light 36 tells the patient not to disturb the homebase 14 until the wait light 36 goes off, indicating that internal processing elements of the homebase 14 are inactive.
  • the phone light 38 indicates when the care provider and the patient are involved in voice communication via the remote telephone and the local telephone and thus when the internal processing elements of the homebase 14 are inactive. The phone light 38 may also indicate when the infusion system 10 is ready.
  • the alarm light 40 indicates various alarm conditions and functions in the infusion system 10 . The alarm conditions and operation of the alarm light in response to those conditions will be described below with reference to FIG. 10.
  • the programming mode or sequence of the present invention will be described in detail.
  • the care provider when a care provider wants to access and process the protocol of the homebase 14 from a remote telephone, the care provider calls a telephone number corresponding to the infusion device 10 .
  • the call from the care provider rings at a local telephone coupled to the homebase 14 . If the call is answered by the patient (or some other person) located at the local telephone and homebase 14 , the care provider and patient communicate by standard voice signals between the remote and local telephones (i.e., communicate in the phone or patient conversation mode).
  • the care provider asks the patient to depress the link button 30 (or some series of buttons) on the homebase 14 , which connects the care provider with homebase 14 , terminates the phone mode, and initiates a remote touch-tone programming session. If, on the other hand, the care provider's call is not answered, the care provider may be directly connected to the homebase 14 , as described above, thereby directly initiating a remote touch-tone programming session without entering the phone mode. Alternatively, a touch-tone programming session can be initiated by a care provider located at the local push-button telephone simply by picking up the telephone handset and pressing the local button 32 , which gives the local telephone access to the homebase 14 .
  • the processor 53 accesses from the voice storage unit 52 a greeting message 61 , which is transmitted to the care provider at the remote or local telephone. Following the greeting message 61 , a voice command 62 (which is accessed by the processor 53 from the voice storage unit 52 ) is sent to the care provider asking the care provider to enter an access code. Using the keys on the remote push-button telephone, the care provider enters the access code, and the processor 53 determines whether the entered access code is valid (Step 63 ). If it is valid, the processor 53 determines in Step 64 whether it is a master access code or a user access code. If the care provider has entered a master access code, the care provider is transferred (circle 65 ) to an access code menu 90 illustrated in FIG. 4, which provides for programming of the master and user access codes.
  • Step 66 ansks whether the care provider wants to review the current programmable homebase protocol, instructing the care provider to depress a particular key on the touch-tone key pad to select this option;
  • Step 67 an asks whether the care provider wants to edit the current protocol, providing a similar instruction;
  • Step 68 an asks whether the care provider wants to create an entirely new protocol, with instructions on how to select this option;
  • Step 69 an asks whether the care provider wants to terminate the programming session and return to voice communication with the patient.
  • Step 66 the care provider is transferred (circle 70 ) to a review mode menu 195 illustrated in FIG. 5.
  • Step 67 the care provider is transferred (circle 71 ) to an edit mode menu 200 illustrated in FIG. 6.
  • Step 68 the care provider is transferred (circle 72 ) to a create mode menu 300 illustrated in FIG. 8A.
  • Step 73 the phone mode, the care provider can talk with the patient to verify programming changes (Step 74 ). The care provider can then hang up the remote telephone after completing the conversation with the patient (Step 75 ).
  • Step 63 the care provider entered an invalid access code
  • the care provider is asked (in Step 63 ) to enter another access code because the one previously entered was invalid. If this next entered access code is valid, the care provider is transferred (via Step 77 ) to the access code decision step (i.e., Step 64 ), and the process is as described above. If, however, the care provider enters another invalid access code, decision Step 77 goes to Step 78 , in which the care provider is told the access code is invalid and is asked to enter another access code. If this code is valid, decision Step 79 transfers the care provider to access code decision step 64 .
  • Step 79 goes to Step 80 .
  • the care provider is told in Step 80 that the access code is invalid and to contact a home healthcare provider to obtain a correct access code, and the homebase 14 hangs up (Step 81 ).
  • the homebase could hang up, or it could permit the care provider more than three tries to enter a proper access code.
  • the access code menu 90 will be described. If the care provider has entered a master access code, the care provider is transferred to the access code menu 90 (via circle 65 ). Upon accessing this menu, the homebase 14 generates a number of voice queries that are transmitted to the care provider and provide the care provider with a number of options. First, in Step 91 , the care provider is asked whether a new master access code is to be entered and is instructed to press a certain button on the touch tone key pad (in this case the number “1”) to select this option. If the care provider selects this option, the homebase 14 tells the care provider to enter the existing master access code (Step 92 ) and to enter a new master access code (Step 93 ).
  • the newly entered master access code is then read back to the care provider by the homebase 14 (Step 94 ), and the homebase 14 generates a voice command that tells the care provider to press the “#” key on the key pad to accept this new master access code (Step 95 ). If the care provider presses the “#” key, the homebase 14 returns (Step 96 ) the care provider to the access code menu 90 (via circle 65 ).
  • the keys to be pressed by the care provider are only exemplary and that other keys could be designated to accept and/or select various options and programming 5 entries.
  • Step 97 the care provider is asked whether a new user access code is to be entered and is instructed to press a certain button on the touch tone key pad (in this case the number “2”) to select this option. If the care provider selects this option, the homebase 14 tells the care provider to enter a new user access code (Step 98 ). If the entered new user access code already exists, the program loops around (Steps 99 - 100 ) and asks the care provider to enter a new master access code again (Step 97 ).
  • the new user access code is then read back to the care provider by the homebase 14 (Step 101 ), and the homebase 14 generates a voice command that tells the care provider to press the “#” key on the key pad to accept this new user access code (Step 102 ). If the care provider presses the “#” key, the homebase 14 returns (Step 103 ) the care provider to the access code menu 90 (via circle 65 ).
  • Step 104 the care provider is asked whether he or she would like to query the user access codes and is instructed to press a certain button on the touch tone key pad (in this case the number “3”) to select this option. If the care provider selects this option, the homebase 14 tells the care provider in Step 105 that there are a certain number of user access codes (depending on how many there are). In Step 106 , the homebase 14 recites the user access codes to the care provider and continues reciting the user access codes (Step 107 ) until all are recited. After completing reciting the user access codes, the homebase 14 returns (Step 108 ) the care provider to the access code menu 90 (via circle 6-E).
  • a certain button on the touch tone key pad in this case the number “3”
  • Step 109 the care provider is asked whether he or she would like to erase the user access codes and is instructed to press a certain button on the touch tone key pad (in this case the number “4”) to select this option. If the care provider selects this option, the homebase 14 asks the care provider to select one of two options: (1) to erase specific user access codes, press a certain button on the touch-tone key pad (in this case the number “1”) (see Step 1 10 ); or (2) to erase all user access codes, press a different button (in this case the number “2”) (see Step 115 ).
  • Step 1 10 the care provider is asked to enter the specific user access code to be deleted (Step 111 ), and the homebase 14 reads back that specific user access code in Step 1 12 .
  • the homebase 14 then asks the care provider to press the “#” button on the touch-tone key pad to accept deletion of that user access code (Step 113 ) and is returned to the access code menu in Step 114 .
  • Step 115 global deletion
  • the homebase 14 warns the care provider that he or she is about to erase all the user access codes and asks for the care provider to press the “#” button to accept (Step 1 16 ).
  • the homebase then returns to the access code menu 90 (Step 117 ).
  • Step 118 the care provider is asked to press a certain number (in this case “5”) to exit the access code menu. If the care provider selects this option, the homebase 14 returns (via Step 119 ) to the access code prompt 62 (see FIG. 3).
  • the homebase 14 transfers (circle 70 ) the care provider to a review mode menu 195 illustrated in FIG. 5.
  • the homebase 14 Upon accessing this menu, the homebase 14 generates a number of voice queries that are transmitted to the care provider and provide the care provider with a number of options—namely, reviewing the following information: (1) the operating parameters of a continuous mode of the pump 12 (Step 120 ); (2) the operating parameters of an intermittent mode of the pump 12 (Step 121 ); (3) the operating parameters of a taper mode of the pump 12 (Step 122 ); (4) the operating parameters of a patient controlled analgesia (PCA) mode in milliliters (mL) of the pump 12 (Step 123 ); and (5) the operating parameters of a PCA mode in milligrams (mg) of the pump 12 (Step 124 ).
  • PCA patient controlled analgesia
  • the continuous mode refers to a pump that continually delivers fluid to the patient
  • the intermittent mode refers to intermittent delivery of fluids.
  • the taper mode refers to a mode in which fluid delivery is stepped-up to a base rate then stepped-down to a “keep vein open” rate periodically during administration.
  • the PCA mode refers to the ability of the patient to self-administer an additional burst (or “bolus”) of the fluid being administered by the pump. In other words, when the present dosage of analgesia being administered to the patient by the pump is inadequate to relieve pain, the patient can self-administer a bolus shot to bolster the dosage being automatically delivered by the pump.
  • the homebase 14 provides the care provider with a variety of information.
  • the care provider is told whether the protocol is locked or unlocked (Step 125 ); whether the “air-in-line” (AIL) alarm is on or off (Step 126 ); the elapsed time in hours, minutes, and/or seconds of the present administration to the patient (Step 127 ); the programmed rate of fluid being delivered in mLs per hour (Step 128 ); the current rate of fluid in mLs per hour (Step 129 ); the volume of fluid to be infused in mLs (Step 130 ); the volume of fluid already infused (Step 131 ); the level in mLs at which the low volume alarm will sound (Step 132 ); and the last occurrence of the alarm (Step 133 ). (See also FIG. 10, which illustrates the alarm table.) After providing this information to the care provider, the homebase 14 in Step 134 returns to the main
  • Step 121 the homebase 14 also provides the care provider with a variety of information.
  • Steps 135 - 137 provide the same information as Steps 125 127 , respectively.
  • Step 141 provides the same information as Step 131
  • Steps 145 - 146 provide the same information as Steps 132 - 133 , respectively.
  • Additional information provided to the care provider in the intermittent mode is as follows: the programmed dose rate of fluid being delivered in mLs per hour (Step 138 ); the current dose rate of fluid in mLs per hour (Step 139 ); the dose volume of fluid to be infused in mLs (Step 140 ); the background rate in mLs per hour (Step 142 ); the time between doses (or “Q” hours) (Step 143 ); and the number of doses (Step 144 ).
  • the homebase 14 After providing this information to the care provider, the homebase 14 returns in Step 147 to the main menu 82 .
  • Step 122 the homebase 14 also provides the care provider with a variety of information.
  • Steps 148 - 150 provide the same information as Steps 125 - 127 , respectively.
  • Step 1 54 provides the same information as Step 1 31
  • Steps 157 - 158 provide the same information as Steps 132 - 133 , respectively.
  • Step 151 the programmed base rate of fluid being delivered in mLs per hour
  • Step 152 the current base rate of fluid in mLs per hour
  • Step 153 the volume of fluid before taper down in mLs
  • Step 153 the step-up rate in mLs per hour
  • Step 1 56 the step-down rate in mLs per hour
  • Step 123 If the care provider selects review of the PCA mL mode (Step 123 ), the care provider is also given information.
  • Steps 160 - 162 provide the same information as Steps 125 - 127 , respectively.
  • Steps 165 - 166 provide the same information as Steps 130 - 131 , respectively, and Steps 172 - 173 provide the same information as Steps 132 - 133 , respectively.
  • Additional information provided to the care provider in the PCA mL mode is as follows: the programmed continuous rate of fluid being delivered in mLs per hour (Step 163 ); the current continuous rate of fluid in mLs per hour (Step 164 ); the bolus volume of fluid in mLs (Step 167 ); the bolus interval in hours and minutes (Step 168 ); the number of boli/hour (Step 169 ); the number of boli attempted (Step 170 ); and the number of boli delivered (Step 171 ).
  • the homebase 14 After providing this information to the care provider, the homebase 14 returns in Step 174 to the main menu 82 .
  • Step 124 If the care provider selects review of the PICA mg mode (Step 124 ), the care provider is given other information. Steps 175 - 177 provide the same information as Steps 125 - 127 , respectively, and Steps 188 - 189 provide the same information as Steps 132 - 133 , respectively.
  • Additional information provided to the care provider in the PCA mg mode is as follows: the concentration of fluid delivered in mg/mL (Step 178 ); the programmed continuous rate of fluid in mgs/hour (Step 179 ); the current continuous rate in mg s/hour (Step 180 ); the mgs to be infused (Step 181 ); the mgs infused in mgs (Step 182 ); the bolus dose in mgs (Step 183 ); the bolus interval in hours and minutes (Step 184 ); the number of boli/hour (Step 185 ); the number of boli attempted (Step 186 ); and the number of boli delivered (Step 187 ).
  • the homebase 14 After providing this information to the care provider, the homebase 14 returns in Step 190 to the main menu 82 .
  • the homebase 14 transfers (circle 71 ) the care provider to an edit mode menu 200 illustrated in FIG. 6.
  • the homebase 14 Upon accessing this menu, the homebase 14 generates a number of voice queries that are transmitted to the care provider and provide the care provider with a number of options—namely: (1) editing the operating parameters of the continuous mode (Step 201 ); (2) editing the operating parameters of PCA mL mode (Step 202 ); and (3) editing the operating parameters of the PCA mg mode (Step 203 ).
  • the care provider is transferred (see circle 204 ) to the edit mode sub-menus 270 , 280 illustrated FIG. 7.
  • the homebase 14 permits the care provider to edit the rate of delivery. In this mode, some parameters are maintained and others may be edited.
  • the care provider is told the current rate at which the pump 12 is delivering fluid in mLs/hour (Step 210 ).
  • the care provider is then asked to enter a new rate, or press the “#” button to accept the current rate (Step 211 ).
  • the care provider is told the new rate in mLs/hour and is asked to press the “#” button on the key pad to accept the new rate (Step 212 ).
  • the homebase 14 transfers (circle 204 ) to the sub-menus 270 , 280 of FIG. 7.
  • Step 202 If the care provider selects editing of the PCA mL mode (Step 202 ), the care provider is asked to edit various parameters of the PCA mL protocol. The care provider is first told what the current continuous rate is in mLs/hour (Step 221 ), and in Step 222 is asked to enter a new continuous rate or press the “#” button to accept the present rate. The care provider is then told what the new rate is and asked to press the “#” button to accept that new rate (Step 223 ). Similar operations are performed on the bolus volume (Steps 224 - 226 ), the number of boli/hour (Steps 227 - 229 ), and the bolus interval (Steps 230 - 232 ). After editing, the homebase 14 transfers (circle 204 ) to the sub-menus 270 , 280 of FIG. 7.
  • Step 203 If the care provider selects editing of the PCA mg mode (Step 203 ), the care provider is asked to edit various parameters of the PCA mL protocol. The care provider is first told what the current continuous rate is in mgs/hour (Step 241 ), and in Step 242 is asked to enter a new continuous rate or press the “#” button to accept the present rate. The care provider is then told what the new rate is and asked to press the “#” button to accept that new rate (Step 243 ). Similar operations are performed on the bolus volume (Steps 244 - 246 ), the number of boli/hour (Steps 247 - 2491 , and the bolus interval (Steps 250 - 252 ). After editing, the homebase 14 transfers (circle 204 ) to the sub-menus 270 , 280 of FIG. 7.
  • the edit mode sub-menus 270 , 280 provide the care provider with several options after editing the protocol.
  • the first edit mode sub-menu 270 allows the care provider to send (i.e., save) the edits to the pump 1 2 (Step 271 ) by pressing a certain key on the key pad (in this case “1”), to review the edits (Step 272 ) by pressing a different key on key pad (in this case “2”), and to cancel the edits (Step 273 ) by pressing still a different number on she key pad (in this case “3”).
  • Step 271 If the care provider selects sending the edits (Step 271 ), the new protocol is sent to the pump 12 (Step 274 ), and the care provider is told “goodbye” (Step 275 ). The care provider is then transferred to the phone or patient conversation mode (Step 276 ), and the care provider is put in connection with the patient to verify the programming (Step 277 ). After verifying the programming changes with the patient, the care provider hangs up the remote telephone (Step 278 ), and the programming session is terminated.
  • the homebase 14 reports the new parameters of the protocol to the care provider (Step 279 ). After reporting, the care provider is taken to the second edit mode sub-menu 280 .
  • the second edit mode sub-menu 280 permits the care provider to select one of several options: (1) send the edits by pressing a key on the key pad (Step 281 ), (2) edit the edits by pressing a different key on the key pad (Step 282 ), or (3) cancel the edits by pressing still a different key on the key pad (Step 283 ).
  • Step 281 If the care provider selects sending the edits (Step 281 ), the new protocol is sent to the pump 12 (Step 284 ), and the care provider is told “goodbye” (Step 285 ). The care provider is then transferred to the phone or patient conversation mode (Step 286 ), and the care provider is put in connection with the patient (the patient conversation mode) to verify the programming (Step 287 ). After verifying the programming changes with the patient, the care provider hangs up the remote telephone (Step 288 ), and the programming session is terminated. If the care provider selects editing of the edits (Step 282 ), the care provider is transferred to the edit mode menu (Step 289 ) illustrated in FIG. 6 and described above. If the care provider selects cancelling of the edits (Step 283 ), the care provider is transferred to the main menu 82 (Step 290 ).
  • the create mode will now be described. If the care provider selects the create mode in Step 68 , the homebase 14 transfers the care provider to a create mode menu 300 .
  • the care provider has several options for processing the protocol: (1) the continuous mode 302 , (2) the intermittent mode 304 , (3) the taper mode 306 , and (4) the PCA mode 308 . For any of these modes to be selected, the care provider presses a predetermined number on the keypad of the remote programming transceiver or push button telephone.
  • the care provider selects programming of the continuous mode 302 from the create mode menu 300 , the care provider is asked to program various parameters of the continuous mode protocol.
  • the care provider is asked to enter the rate (Step 310 ), after which the entered rate is read back, and the care provider is asked to press the “#” button to accept this rate (Step 31 1 ).
  • the care provider follows the same procedure for entering volume (Steps 312 and 313 ), low volume alarm (Steps 314 and 315 ), protocol locking (Steps 316 and 317 ), and AIL on or off (Steps 318 and 319 ). After programming, the care provider is transferred (circle 397 ) to the sub-menus of FIG. 9.
  • the care provider selects programming of the intermittent mode 304 , the care provider is asked to program various parameters of the intermittent mode protocol. The care provider is asked to enter the number of “Q” hours (Step 320 ), after which the entered number of “Q” hours is read back, and the care provider is asked to press the “#” button to accept this number (Step 321 ).
  • the care provider follows the same procedure for entering dose rate (Steps 322 and 323 ), dose volume (Steps 324 and 325 ), background rate (Steps 326 and 327 ), number of deliveries (Steps 328 and 329 ), low volume alarm (Steps 330 and 331 ), protocol locking (Steps 332 and 333 ), and AIL on or off (Steps 334 and 335 ).
  • the care provider is transferred (circle 397 ) to the sub-menus of FIG. 9.
  • the care provider selects programming of the taper mode 306 , the care provider is asked to program various parameters of the taper mode protocol.
  • the care provider is asked to enter the total volume (Step 336 ), after which the entered total volume is read back, and the care provider is asked to press the “#” button to accept (Step 337 ) this volume.
  • the care provider follows the same procedure for entering taper up time (Steps 338 and 339 ), taper down time (Steps 340 and 341 ), and total delivery time (Steps 342 and 343 ).
  • the homebase unit 14 calculates the base rate (Step 344 ) and reads this base rate back to the care provider (Step 345 ); calculates the volume before taper down (Step 346 ) and reads this volume back to the care provider (Step 347 ); and calculates the step up and step down rates (Steps 348 and 350 ) and reads these back (Steps 349 and 351 ).
  • the care provider is also asked to enter protocol locking (Steps 352 and 353 ) and AIL on or off (Steps 354 and 355 ). After programming, the care provider is transferred (circle 397 ) to the sub-menus of FIG. 9.
  • the care provider selects programming of the PCA mode 308 , the care provider is taken to a PCA mode sub-menu 360 .
  • the care provider is asked to select the PCA mL mode (Step 361 ) or the PCA mg mode (Step 362 ).
  • the care provider selects the PCA mL mode, the care provider is asked to enter the protocol of this mode, including the continuous rate (Steps 363 and 364 ), total volume (Steps 365 and 366 ), bolus volume (Steps 367 and 368 ), number of boli/hour (Steps 369 and 370 ), bolus interval (Steps 371 and 372 ), low volume alarm (Steps 373 and 374 ), protocol locking (Steps 375 and 376 ), and AIL on or off (Steps 377 and 378 ).
  • the continuous rate Steps 363 and 364
  • total volume Steps 365 and 366
  • bolus volume Steps 367 and 368
  • number of boli/hour Steps 369 and 370
  • bolus interval Steps 371 and 372
  • low volume alarm Steps 373 and 374
  • protocol locking Steps 375 and 376
  • AIL on or off Steps 377 and 378 .
  • Step 362 the care provider is asked to enter that mode's protocol, including the concentration (Steps 379 and 380 ), continuous rate (Steps 381 and 382 ), total volume (Steps 383 and 384 ), bolus volume (Steps 385 and 386 ), number of boli/hour (Steps 387 and 388 ), bolus interval (Steps 389 and 390 ), low volume alarm (Steps 391 and 392 ), protocol locking (Steps 393 and 394 ), and AIL on or off (Steps 395 and 396 ). After programming, the care provider is transferred (circle 397 ) to the sub-menus of FIG. 9.
  • the care provider is transferred (via circle 397 ) to a primary create mode sub-menu 400 .
  • the care provider can make various selections, including sending the newly programmed protocol (Step 402 ), reviewing the newly programmed protocol (Step 404 ), and cancelling the newly programmed protocol (Step 406 ).
  • Step 402 If the care provider selects send (Step 402 ), the care provider is told that the new protocol is being sent to the pump 12 and then told “goodbye” (Steps 410 and 41 1 ), and the connection is switched to the phone or patient conversation mode (i.e., communication with the patient) (Step 412 ). The care provider may then speak with the patient to verify the programming (Step 413 ) and then hang up after verifying (Step 414 ). If the cancel option 406 is selected, the care provider is transferred (Step 437 ) to the main menu 82 .
  • Step 415 the parameters of the new programmed protocol are reported to the care provider (Step 415 ).
  • the care provider is then transferred to a secondary create mode sub-menu 420 , from which the care provider can select various options, including sending the new protocol (Step 422 ), editing the new protocol (Step 424 ), and cancelling the new protocol (Step 426 ).
  • Steps 430 through 434 are performed, which are the same as those performed if the care provider were to select the sending option 402 from the primary create mode sub-menu 400 .
  • the editing option 424 is selected, the care provider is transferred (Step 435 ) to the create mode menu 300 .
  • the cancel option 424 is selected, the care provider is transferred (Step 436 ) to the main menu 82 .
  • the homebase 14 can be provided with a variety of features that facilitates remote or local programming of the protocol.
  • “#” key can be used to enter changes or selections.
  • the “*” key can be used for exiting the programming mode, for backspacing from a currently operating step to a previous step or from a portion of a parameter being processed to a previous portion of that parameter, or for entering a decimal point, depending on the instance in the programming sequence.
  • the system can be set up such that it rejects out of range values and advises on the erroneous value.
  • the alarm table 500 may include a variety of alarm functions, including air in the line alarm 502 for the line 18 connecting the pump 12 to the patient, a bad battery alarm 504 , a bar code fault alarm 506 , an alarm indicating the need for a battery change 508 , a door open alarm 510 , an end of program alarm 512 , a low battery alarm 514 , a low volume alarm 516 , a malfunction alarm 518 , an occlusion alarm 520 , an over-voltage alarm 522 , a pump interrupted alarm 524 , and a pumping complete alarm 526 .
  • air in the line alarm 502 for the line 18 connecting the pump 12 to the patient a bad battery alarm 504 , a bar code fault alarm 506 , an alarm indicating the need for a battery change 508 , a door open alarm 510 , an end of program alarm 512 , a low battery alarm 514 , a low volume alarm 516 , a malfunction alarm 518 , an occlusion
  • All of these alarms can be made audible, with a variety of different or identical tones, or visual, via the alarm light 40 , multiple lights, or a digital or analog display.
  • the above alarm functions are exemplary, and other alarm functions can be provided. Alternatively, only some, or one, or none of the above alarm functions can be implemented in the present invention, depending on the particular application.
  • the alarm light 40 may comprise a number of lights, for example, red, yellow, green, and other colored LEDs.
  • the audio device 29 may comprise a speaker, siren, or similar apparatus.
  • red and green LEDs which comprise the alarm light 40
  • a yellow LED may flash with intermittent audio. If someone is trying to access the local, send, or link modes (i.e., is depressing the link button 30 , local button 32 , or send button 34 ) without the pump 12 being properly attached to the homebase 14 , yellow and red LEDs may flash with intermittent audio. If the telephone connection between the remote or local telephone and the homebase 14 is lost, a red LED may flash with intermittent audio. Finally, if an internal system error occurs in the homebase 14 and/or pump 12 , a red LED may flash with intermittent audio. It should be understood that the above operation of the alarm light 40 and audio device 29 are only exemplary and that variations can be made on these alarms.
  • FIGS. 3 - 10 provide only examples of how the care provider and the homebase unit 14 may interact via a remote or local push button telephone or similar transceiver. Therefore, additional or alternative steps and procedures can be designed and implemented for remote programming of the present invention. Accordingly, only some of the steps described above need be included in the invention; the steps may be conducted in a different order; additional or fewer protocol parameters may be controlled by the care provider; and different operational modes (i.e., other than continuous, intermittent, etc.) may be chosen.
  • the present invention can be used in a variety of applications.
  • the present invention is used for controlling and programming the protocol of an infusion pump.
  • ventilators e.g., for blood/oxygen level
  • respiratory equipment e.g., EKG machines
  • blood/gas analyzers e.g., enteral pumps (i.e., stomach infusion pumps)
  • enteral pumps i.e., stomach infusion pumps
  • blood glucose monitors e.g., dialysis equipment
  • open wound irrigation devices e.g., open wound irrigation devices, and urology equipment.

Abstract

A remotely programmable infusion system. The remotely programmable infusion system comprises a memory for storing a programmable protocol and a remote communication port for sending a voice signal to a remote touch-tone transceiver and for receiving a remote programming signal from the remote touch-tone transceiver. The remotely programmable infusion system also comprises a voice storage unit for storing the voice signal. The remotely programmable infusion system further comprises a processor, coupled to the remote communication port, to the voice storage unit, and to the memory, for accessing the voice signal from the voice storage unit and the programmable protocol from the memory, and for processing the programmable protocol in response to receiving the remote programming signal.

Description

    PRIORITY INFORMATION
  • This application is a continuation of prior applicaion Ser. No. 09/626,571 filed Jul. 27, 2000, which is a continuation of application Ser. No. 09/251,021 filed Feb. 16, 1999, which is a continuation of application Ser. No. 08/658,689 filed Jun. 5, 1996, which is a continuation of application Ser. No. 08/344,973 filed Nov. 25, 1994.[0001]
  • BACKGROUND OF THE INVENTION
  • 1. Field of the Invention [0002]
  • The present invention relates to a remotely programmable infusion system for medical applications. More particularly, the present invention relates to an infusion system for delivering a variety of medicines and fluids that sends voice commands and queries to a remote touch-tone transceiver and that can be programmed by pressing keys on the keypad of the remote touch-tone transceiver in response to the commands and queries. [0003]
  • 2. Description of the Related Art [0004]
  • Infusion devices are used in the medical field to administer and deliver medicines and other fluids to a patient. Today, due in part to rising health costs and the high cost of hospital rooms, and in part to the desire to provide comfort and convenience to patients, the medical industry has promoted in-home care for patients suffering from various maladies. Particularly, many patients require delivery and administration of medicines or other IV fluids on a regular basis. Delivery and administration is accomplished via a variety of infusion devices, such IV pumps and gravity pumps and other types of IV administration. By supplying patients with infusion devices that are lightweight and easy to use, the patients can receive their medicinal needs at home, i.e., without having to be at a hospital and without direct assistance by a care provider, such as a nurse. [0005]
  • Nevertheless, the operating parameters of infusion devices must frequently be changed, due to variations in the patient's needs. Therapy changes may also require that entire protocols be programmed. In early versions of home infusion devices, the physical presence of a care provider at the infusion device was required to reprogram the device's protocol. Such reprogramming was costly and time-consuming, thereby severely limiting the efficiency and convenience of infusion devices. [0006]
  • Since the introduction of these early home infusion devices, the medical industry has made advances in the techniques by which a home infusion device can be monitored and reprogrammed. For example, one system employs a patient activated switch on a diagnostic apparatus that causes automatic dialing of a telephone number corresponding to a care provider remote from the diagnostic apparatus. This enables the patient to communicate with the care provider through a speaker and microphone on the diagnostic apparatus, permitting interactive communication with the care provider regarding the routines to be performed by the diagnostic apparatus. This system, however, merely provides the capability for the care provider to monitor the infusion device, but does not offer the capacity to remotely reprogram the infusion device. [0007]
  • Another remote monitoring system employs a user interface for programming blood pressure testing protocol into, and downloading blood pressure data from, ambulatory blood pressure monitoring units. The user interface is connected to a central processing computer via a telephone line. Control units located at the blood pressure testing site transfer blood pressure data to the central computer, which generates comprehensive medical reports for specific patients, but which cannot transmit reprogramming signals back to the control unit. [0008]
  • Other systems employ remote computers for monitoring and reprogramming the protocol of the infusion device. In one such system, the infusion device has a delivery unit for delivering the medicinal solution and a removable logic unit for controlling operation of the delivery unit. The logic unit is either attached to or separate from the delivery unit, and the latter can be worn by the patient. The logic unit is connected to a programming computer via a telephone line. The computer can be used to program the logic unit with a logic configuration suitable for operating the delivery unit in accordance with the intended delivery requirements. Thus, while such systems provide for remote reprogramming of the protocol, they require a remotely located computer to accomplish reprogramming. [0009]
  • The previous conventional systems have a variety of drawbacks. Most importantly, they do not provide simple, interactive reprogramming by a care provider without the need for a remote reprogramming computer. The ability to have the care provider access the remotely located infusion device on a standard telephone and reprogram the infusion device via the keys on the telephone keypad is a significant advance over conventional reprogramming techniques. This is because touch-tone reprogramming is less costly, quicker, and much more convenient for both the care provider and the patient, making infusion devices easier to use and more versatile. Conventional home infusion systems also do not have the capacity to send recorded voice signals to the remote care provider instructing and asking the care provider about reprogramming the infusion device. By using recorded voice commands and queries stored in the infusion system that direct the care provider in reprogramming the infusion device, the process of reprogramming is made simpler and more efficient, with little chance of making programming errors. Therefore, a need exists for an infusion device that can be remotely programmed via a transceiver without the need for a remote programming computer and that sends recorded voice signals from the infusion device to a care provider. [0010]
  • SUMMARY OF THE INVENTION
  • Accordingly, the present invention is directed to a remotely programmable infusion system and a method for remotely programming an infusion system via a remote transceiver that substantially obviates one or more of the problems due to limitations and disadvantages of the related art. [0011]
  • Additional features and advantages of the invention will be set forth in the description that follows and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention will be realized and attained by the apparatus and method particularly pointed out in the written description and claims of this application, as well as the appended drawings. [0012]
  • To achieve these and other advantages, and in accordance with the purpose of the invention as embodied and broadly described herein, the present invention defines a remotely programmable infusion system having a programmable protocol, the infusion system being remotely programmable by a remote touch-tone transceiver. The remotely programmable infusion system comprises a memory for storing a programmable protocol and a remote communication port for sending a voice signal to the remote touch-tone transceiver and for receiving a remote programming signal from the remote touch-tone transceiver. The remotely programmable infusion system also comprises a voice storage unit for storing the voice signal and a processor, coupled to the remote communication port and to the voice storage unit and to the memory, for accessing the voice signal from the voice storage unit and the programmable protocol from the memory, and for processing the programmable protocol in response to receiving the remote programming signal. [0013]
  • In another aspect, the present invention defines a method for remotely programming an infusion system. The infusion system has a voice storage unit for storing a voice signal and has a programmable protocol and is remotely programmable by a remote touch-tone transceiver. The method comprises several steps: establishing a connection between the infusion system and the remote touch-tone transceiver; accessing the voice signal from the voice storage unit in response to establishing the connection; sending the voice signal to the remote touch-tone transceiver; receiving a remote programming signal from the remote touch-tone transceiver; and processing the programmable protocol in response to receiving the remote programming signal. [0014]
  • In a further aspect, the present invention comprises a remotely programmable infusion system having a programmable protocol stored in a protocol memory, the remotely programmable infusion system being programmable by a remote touch-tone transceiver. The infusion system comprises an infusion pump for delivering fluids to a patient. The infusion pump has an infusion data port. The infusion system also comprises a homebase unit, coupled to the infusion communication port on the infusion pump via a homebase data port, for processing the programmable protocol. The homebase unit comprises a voice storage unit for storing a voice signal and a remote communication port for sending the voice signal to the remote touch-tone transceiver and for receiving a dual-tone multi-frequency (DTMF) signal from the remote touch-tone transceiver. The homebase unit further comprises a processor, coupled to the remote communication port, to the voice storage unit, and to the protocol memory, for accessing the voice signal from the voice storage unit, for accessing the programmable protocol from the protocol memory, and for processing the programmable protocol to obtain a processed programmable protocol in response to the DTMF signal. The processed programmable protocol is relayed from the processor to the infusion pump via the homebase data port and the infusion data port. [0015]
  • It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.[0016]
  • The accompanying drawings are included to provide a further understanding of the invention and are incorporated in and constitute a part of this specification, to illustrate the embodiments of the invention, and, together with the description, to explain the principles of the invention. [0017]
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a diagrammatical representation of the programmable infusion system of the present invention. [0018]
  • FIG. 2 is a block diagram of the homebase unit in accordance with the present invention. [0019]
  • FIG. 3 is a flow diagram illustrating entry of an access code and the main menu in an example of the present invention. [0020]
  • FIG. 4 is a flow diagram illustrating an access code menu in accordance with an example of the present invention. [0021]
  • FIG. 5 is a flow diagram illustrating a review mode menu in accordance with an example of the present invention. [0022]
  • FIG. 6 is a flow diagram illustrating an edit mode menu in accordance with an example of the present invention. [0023]
  • FIG. 7 is a flow diagram illustrating sub-menus of the edit mode menu in accordance with an example of the present invention. [0024]
  • FIGS. 8A and 8B represent a flow diagram illustrating a programming mode menu in accordance with an example of the present invention. [0025]
  • FIG. 9 is a flow diagram illustrating sub-menus of the programming mode menu in accordance with an example of the present invention. [0026]
  • FIG. 10 is a table illustrating the alarm functions that can be employed in the system of the present invention.[0027]
  • DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
  • Reference will now be made in detail to the present preferred embodiment of the invention, an example of which is illustrated in the accompanying drawings. Wherever possible, the same reference numbers will be used throughout the drawings to refer to the same or like parts. [0028]
  • In accordance with the present invention, a remotely programmable infusion system is provided that allows remote programming of the infusion system from a remotely located transceiver, such as a push-button telephone. The remotely programmable infusion system includes a memory and a voice storage unit. The infusion system also includes a remote communication port, as well as a processor that is coupled to the remote communication port, the voice storage unit, and the memory. It should be understood herein that the terms “programming,” “programmable,” and “processing” are generalized terms that refer to a host of operations, functions, and data manipulation. Those terms, therefore, are not to limited herein to editing and deleting data, parameters, protocol, and codes. For example, programming and processing, as used herein, may encompass editing, changing, erasing, entering, re-entering, viewing, reviewing, locking, and inserting functions. [0029]
  • An exemplary embodiment of the apparatus of the present invention is shown in FIG. 1 and is designated generally by [0030] reference numeral 10. As herein embodied and shown in FIG. 1, the remotely programmable infusion system 10 includes a pump unit 12 and a homebase 14. The pump unit 12 and homebase 14 may be two separate units, as illustrated in FIG. 1, or may comprise a single integral unit housing both the pump 12 and the homebase 14. With both elements integrated into a single infusion device, the device may be entirely portable and programmable, both via local and remote programming devices.
  • The [0031] pump unit 12 includes a housing 16 that contains the electrical and mechanical elements of the pump unit 12. An example of a pump unit 12 that can be used in the present invention is disclosed in U.S. Pat. No. 5,078,683, assigned to the assignee of the present invention. The pump unit 12 also includes an infusion line 18 that is connected to a patient at end 19. The pump unit 12 further includes a display 20 and various controls 22.
  • The [0032] homebase 14 includes a cradle 24 for holding the pump unit 12, a cable for connecting the homebase 14 to the pump unit 12, controls 26 for controlling operation of the homebase 14, display lights 28 for indicating various conditions of the homebase 14, and an internal audio device 29 for providing audio alarm signals. As embodied herein, the controls 26 include a link button 30, a local button 32, and a send button 34. The display lights 28 include a wait light 36, a phone light 38, and an alarm light 40. The function of the controls 26 and the display lights 28 will be described in detail below. The homebase 14 also includes a remote communication port 42 and a local communication port 44. Preferably, the homebase 14 and pump 12 are interconnected by an infra-red communications link 46, 48.
  • As embodied herein, the [0033] remote communication port 42 and the local communication port 44 each comprise a standard modem, as is well known in the art. Preferably, the modem module of the present invention is a Cermetek modem No. CH1785 or CH1782. These modem modules may operate at 2400 baud or other baud rates. Other baud rates, however, can also be employed in the present invention. The local button 32 is used to activate the local communication port 44. For example, when the care provider is at the premises where the infusion system 10 is located, the care provider presses the local button 32, thereby activating the local communication port 44. The care provider can then communicate with the homebase 14 via a local telephone (not shown) at the premises that is connected to the local communication port 44. If, on the other hand, the care provider is at a location remote from the infusion system 10, the link button 30 is pressed, activating the remote communication port 42. In this way, the care provider can communicate with the homebase 14 via a telephone (or other such transceiver) located at the remote location.
  • For convenience, this description refers to local and remote telephones, but it should be understood that any touch-tone or DTMF transceiver can be employed in the present invention, or for that matter, any transceiver that is capable of two-way communication and activation or selection of programming parameters both independently of and in response to various prompts and queries. It should also be understood that the term “touch-tone transceiver” is not limited to conventional push-button telephones having a [0034] 12 key keypad, with 0-9, “*”, and “#” keys. Rather, as defined herein, the term “touch-tone transceiver” refers to any transceiver capable of generating signals via a keyboard or other data entry system and thus is not limited to transceivers that generate DTMF signals, such as conventional telephones. Examples of “touch-tone transceivers” as defined herein include conventional push-button telephones, computers having a keyboard and/or mouse, transmitters that convert human voice to pulse or digital or analog signals, and pager transceivers.
  • The [0035] homebase data port 46 and pump data port 48 comprise a wireless emitter/detector pair. Preferably, data ports 46, 48 each comprise and infra-red emitter/detector, permitting wireless communication between the pump unit 12 and the homebase 14. Other wireless communications ports may be employed, however, or the pump unit 12 and the homebase 14 may have their data ports 46, 48 hard-wired together. As described above, moreover, the pump unit 12 and the homebase 14 may comprise a single unit, obviating the need for a wireless or hard-wired link between the two units. A power cable 50 is preferably employed to provide power to the pump unit 1 2 via the homebase 14. Alternatively, the pump unit 12 may have its own power cable coupled directly to the power source, as opposed to being connected through the homebase 14.
  • With reference to FIG. 2, the elements included in the [0036] homebase 14 will be described. The homebase 14 comprises the remote communication port 42, the local communication port 44, a protocol memory 51, a voice storage unit 52, a processor 53, a voice synthesizer 49, and an access code memory 54. The protocol memory 51, the voice storage unit 52, and the access code memory 54 can all be contained in the same memory device (such as a random-access memory), or in separate memory units. Preferably, the voice storage unit 52 comprises a read-only memory (ROM), and the processor 53 comprises an 8-bit microcontroller, such as the Motorola MC68HC1 1 AOFN. The homebase 14 also includes the data port 48 for relaying information between the homebase 14 and pump unit 12. The voice synthesizer 49 is preferably an integrated circuit that converts digitized voice signals to a signal that emulates the sound of a human voice. As embodied herein, the voice synthesizer 49 need only be used to convert the signals outgoing from the homebase 14 to the remote or local telephone and thus is not required for converting incoming signals from the remote or local telephone. The voice synthesizer may comprise an LSI speech synthesis chip commercially available from Oki, part number MSM6585.
  • The [0037] remote communication port 42, the local communication port 44, and the homebase data port 48 are all coupled to the processor 53 via data buses 55 a, 56 a, 57 a, respectively. The communication ports 42, 44 receive signals from a transceiver (such as a telephone) and relay those signals over the buses 55 a, 56 a, respectively, to the processor 53, which in turn processes the signals, performing various operations in response to those signals. The processor 53 receives digitized voice signals from the voice storage unit 52 via bus 59 a and sends those digitized voice signals to the voice synthesizer 49 via bus 59 b, where the signals are converted human voice emulating signals. Those human voice signals are sent from the voice synthesizer 49 via buses 55 b, 56 b, 57 b to buses 55 a, 56 a, 57 a, which in turn relay the those signals to the remote communication port 42, the local communication port 44, and the homebase data port 48, respectively.
  • For example, suppose it is necessary to provide instructions to the care provider operating the remote telephone (not shown). The [0038] processor 53 sends a voice address signal over a data bus 59 a coupling the processor 53 to the voice storage unit 52. The voice address signal corresponds to a location in the voice storage unit 52 containing a particular voice signal that is to be sent to the remote transceiver. Upon receiving the voice address signal, the particular voice signal is accessed from the voice storage unit 52 and sent, via the data bus 59 a, to the processor 53. The processor 53 then relays the voice signal via the data bus 59 b to the voice synthesizer 49, which converts the voice signal and sends the converted signal via data buses 55 b and 55 a to the remote communication port 42, which sends the converted signal to the remote transceiver. The voice signal retrieved from the voice storage unit 52 may be a digitized representation of a person's voice or a computer generated voice signal (both being well known in the art). The digitized voice signal is converted by the voice synthesizer 49 to a signal that emulates the sound of a human voice. The voice signal instructs the care provider on how to respond to the voice signal and what type of information the care provider should send. As the remote transceiver may be a push-button telephone having a keypad with multiple keys, the care provider then presses the appropriate key or keys, thereby sending a DTMF signal back to the remote communication port 42 of the homebase 14. It should be understood, however, that the remote transceiver need not be a push-button telephone, but rather any transceiver capable of sending and receiving DTMF or other similar signals. For example, the remote transceiver may be a computer or portable remote controller.
  • Suppose the DTMF signal sent by the care provider is a remote programming signal, which is transmitted from the remote telephone to the [0039] remote communication port 42 of the homebase 14. The remote communication port 42 then relays the remote programming signal via the data bus 55 a to the processor 53. In response to receiving the remote programming signal, the processor 53 accesses a particular parameter of the programming protocol from the protocol memory 51. To access the parameter, the processor 53 transmits a protocol address signal over the data bus 58 that couples the processor 53 and the protocol memory 51. The protocol address signal corresponds to a location in the protocol memory 51 containing the parameter. The parameter is then sent from the protocol memory 51 to the processor 53 over the data bus 58. Depending on the nature of the remote programming signal, the processor 53 can then perform one of a number of operations on the parameter, including editing, erasing, or sending the parameter back to the remote transceiver for review. Those skilled in the art will recognize that many types of signals or commands can be sent from the remote transceiver to the homebase 14 for processing. Examples of such signals, how they are processed, and their effect will be described in detail below in conjunction with the description of the operation of the present invention.
  • In accordance with the present invention, the [0040] infusion system 10 can incorporate various security measures to protect against unwanted programming of the pump protocol. Significantly, a user access code can be used to block programming except by persons with the user access code, which may be a multi-digit number (preferably a four digit number). The infusion system 10 can be equipped with one or multiple user access codes, which are stored in the access code memory. To initiate communication with the infusion system 10, a care provider is connected to the infusion system 10 via a remote conventional push-button telephone (not shown). This connection may be initiated by a call from the care provider to the infusion system 10 (or a patient talking on a telephone located near the infusion system 10), or by a call from the patient to the care provider. Either way, the care provider is connected to the infusion system 10. After the connection is made between the care provider and the infusion system 10, the care provider is asked (via a voice signal stored in the voice storage unit 52) to enter the user access code. If the care provider enters a valid user access code (as explained above, there may be several valid codes), the care provider is permitted to access and/or program the pump protocol.
  • During a programming session, in certain circumstances (which will be described below), the user access codes can be reviewed, edited, and/or erased entirely and re-entered. To perform any of these functions, a programming signal is sent by the care provider (from, e.g., a remote push button telephone) to the [0041] homebase 14. That programming signal is relayed by the remote communication port 42 to the processor 53, which processes the signal and generates an access code address signal. The access code address signal, which corresponds to a memory location in access code memory 54 holding a user access code, is sent over a data bus 60 to the access code memory 54. The particular user access code is then retrieved and sent back over the data bus 60 to the processor 53, which processes the user access code in some manner.
  • To communicate with the [0042] pump 12, the homebase is equipped with the homebase data port 48. The pump protocol can be sent from the homebase 14 to the pump 12 via the homebase data port 48 and the pump data port 46. Thus, for example, the processor 53 accesses the protocol from the protocol memory 51 and sends the protocol via data bus 57 a to the homebase data port 48. The homebase data port 48 then sends the information over the infra-red link to the pump data port 46, where it is processed by circuitry and/or software in the pump 12. In this way, the pump protocol can be programmed (e.g., edited, redone, reviewed, locked, re-entered, etc.).
  • The functions of the [0043] controls 26 of the infusion system 10 will now be described. The local button 32 is used to activate the local transceiver. If the care provider is located at the homebase 14, and a local transceiver (e.g., a push-button telephone) is at that location and connected to the local communication port 44, the local button 32 is depressed, activating the local communication port 44 and thereby providing a communication connection between the local telephone and the homebase 14.
  • The [0044] send button 34 is designed to permit sending of the infusion system 10 protocol to a remote (or local) computer (not shown). In this way, a remote or local computer can maintain a file having the protocol of many infusion systems 10 located in various places and monitor those protocols. If the computer is remote from the infusion system 10, a person located at the homebase 14 presses the send button 34, which in turn downloads the existing protocol to the remote communication port 42. The protocol is then transmitted via the remote communication port 42 to the remote computer.
  • The [0045] link button 30 is used to initiate a remote (or local) programming session, or, in other words, to enter the remote touch-tone programming mode of the infusion system 10. When initiating a programming session, the care provider calls the telephone number corresponding to the infusion system 10 (or the patient's home phone). The call may ring at a local telephone coupled to the homebase 14 via the local communication port 44. The patient answers the call, and the care provider and patient can communicate between the remote and local telephones via standard voice signals. This is known herein as a phone mode or patient conversation mode. The care provider then instructs the patient to depress the link button 30, which disconnects the patient from the telephone line and initiates the programming mode described below with reference to FIGS. 3-9. If, however, the patient does not answer the care provider's call, the homebase may be equipped with an internal switching system that directly connects the care provider with the homebase 14 and initiates the programming mode. The internal switching may be accomplished with hardware in the homebase 14 or with software that controls the processor 53, or with a hardware-software combination. Either way, the care provider may then begin processing the information and protocol stored in the homebase 14. (As described above, the call may be initiated by the patient to the care provider.)
  • The functions of the display lights [0046] 28 will now be described. Preferably, the display lights 28 comprise LEDs. The wait light 36 indicates when the homebase 14 is involved in a programming session or when its is downloading the protocol to the remote computer. Accordingly, the wait light 36 tells the patient not to disturb the homebase 14 until the wait light 36 goes off, indicating that internal processing elements of the homebase 14 are inactive. The phone light 38 indicates when the care provider and the patient are involved in voice communication via the remote telephone and the local telephone and thus when the internal processing elements of the homebase 14 are inactive. The phone light 38 may also indicate when the infusion system 10 is ready. The alarm light 40 indicates various alarm conditions and functions in the infusion system 10. The alarm conditions and operation of the alarm light in response to those conditions will be described below with reference to FIG. 10.
  • Illustrated in FIGS. [0047] 3-9, the programming mode or sequence of the present invention will be described in detail. As described above, when a care provider wants to access and process the protocol of the homebase 14 from a remote telephone, the care provider calls a telephone number corresponding to the infusion device 10. Preferably, the call from the care provider rings at a local telephone coupled to the homebase 14. If the call is answered by the patient (or some other person) located at the local telephone and homebase 14, the care provider and patient communicate by standard voice signals between the remote and local telephones (i.e., communicate in the phone or patient conversation mode). During such communications, the care provider asks the patient to depress the link button 30 (or some series of buttons) on the homebase 14, which connects the care provider with homebase 14, terminates the phone mode, and initiates a remote touch-tone programming session. If, on the other hand, the care provider's call is not answered, the care provider may be directly connected to the homebase 14, as described above, thereby directly initiating a remote touch-tone programming session without entering the phone mode. Alternatively, a touch-tone programming session can be initiated by a care provider located at the local push-button telephone simply by picking up the telephone handset and pressing the local button 32, which gives the local telephone access to the homebase 14.
  • Once the care provider has accessed the programming mode of the [0048] homebase 14, a series of steps are followed to enable the care provider to program the operational protocol of the infusion device 10. It should be understood that the following programming and access steps are exemplary only and that many variations can be made to the disclosed scheme.
  • With reference to FIG. 3, the [0049] processor 53 accesses from the voice storage unit 52 a greeting message 61, which is transmitted to the care provider at the remote or local telephone. Following the greeting message 61, a voice command 62 (which is accessed by the processor 53 from the voice storage unit 52) is sent to the care provider asking the care provider to enter an access code. Using the keys on the remote push-button telephone, the care provider enters the access code, and the processor 53 determines whether the entered access code is valid (Step 63). If it is valid, the processor 53 determines in Step 64 whether it is a master access code or a user access code. If the care provider has entered a master access code, the care provider is transferred (circle 65) to an access code menu 90 illustrated in FIG. 4, which provides for programming of the master and user access codes.
  • If the care provider has entered a user access code, the [0050] processor 53 accesses from the voice storage unit 52 a number of voice queries comprising a main menu 82: (1) Step 66—asks whether the care provider wants to review the current programmable homebase protocol, instructing the care provider to depress a particular key on the touch-tone key pad to select this option; (2) Step 67—asks whether the care provider wants to edit the current protocol, providing a similar instruction; (3) Step 68—asks whether the care provider wants to create an entirely new protocol, with instructions on how to select this option; and (4) Step 69—asks whether the care provider wants to terminate the programming session and return to voice communication with the patient. If the care provider selects the review mode (Step 66), the care provider is transferred (circle 70) to a review mode menu 195 illustrated in FIG. 5. If the care provider selects the edit mode (Step 67), the care provider is transferred (circle 71) to an edit mode menu 200 illustrated in FIG. 6. If the care provider selects the create mode (Step 68), the care provider is transferred (circle 72) to a create mode menu 300 illustrated in FIG. 8A. Finally, if the care provider selects direct conversation with the patient (Step 69), the connection is switched to a phone mode (Step 73). In the phone mode, the care provider can talk with the patient to verify programming changes (Step 74). The care provider can then hang up the remote telephone after completing the conversation with the patient (Step 75).
  • If the care provider entered an invalid access code, the following steps are followed. In response to receiving an invalid code (see Step [0051] 63), the care provider is asked (in Step 63) to enter another access code because the one previously entered was invalid. If this next entered access code is valid, the care provider is transferred (via Step 77) to the access code decision step (i.e., Step 64), and the process is as described above. If, however, the care provider enters another invalid access code, decision Step 77 goes to Step 78, in which the care provider is told the access code is invalid and is asked to enter another access code. If this code is valid, decision Step 79 transfers the care provider to access code decision step 64.
  • If, on the other hand, the care provider has entered a third invalid access code, [0052] decision Step 79 goes to Step 80. The care provider is told in Step 80 that the access code is invalid and to contact a home healthcare provider to obtain a correct access code, and the homebase 14 hangs up (Step 81). It should be understood that any number of iterations of access code entering can be employed in the present invention. For example, if the care provider enters two invalid access codes, the homebase could hang up, or it could permit the care provider more than three tries to enter a proper access code.
  • Referring now to FIG. 4, the [0053] access code menu 90 will be described. If the care provider has entered a master access code, the care provider is transferred to the access code menu 90 (via circle 65). Upon accessing this menu, the homebase 14 generates a number of voice queries that are transmitted to the care provider and provide the care provider with a number of options. First, in Step 91, the care provider is asked whether a new master access code is to be entered and is instructed to press a certain button on the touch tone key pad (in this case the number “1”) to select this option. If the care provider selects this option, the homebase 14 tells the care provider to enter the existing master access code (Step 92) and to enter a new master access code (Step 93). The newly entered master access code is then read back to the care provider by the homebase 14 (Step 94), and the homebase 14 generates a voice command that tells the care provider to press the “#” key on the key pad to accept this new master access code (Step 95). If the care provider presses the “#” key, the homebase 14 returns (Step 96) the care provider to the access code menu 90 (via circle 65). Those skilled in the art will recognize that the keys to be pressed by the care provider are only exemplary and that other keys could be designated to accept and/or select various options and programming 5 entries.
  • Second, in [0054] Step 97, the care provider is asked whether a new user access code is to be entered and is instructed to press a certain button on the touch tone key pad (in this case the number “2”) to select this option. If the care provider selects this option, the homebase 14 tells the care provider to enter a new user access code (Step 98). If the entered new user access code already exists, the program loops around (Steps 99-100) and asks the care provider to enter a new master access code again (Step 97). If the newly entered user access code does not already exist, the new user access code is then read back to the care provider by the homebase 14 (Step 101), and the homebase 14 generates a voice command that tells the care provider to press the “#” key on the key pad to accept this new user access code (Step 102). If the care provider presses the “#” key, the homebase 14 returns (Step 103) the care provider to the access code menu 90 (via circle 65).
  • Third, in [0055] Step 104, the care provider is asked whether he or she would like to query the user access codes and is instructed to press a certain button on the touch tone key pad (in this case the number “3”) to select this option. If the care provider selects this option, the homebase 14 tells the care provider in Step 105 that there are a certain number of user access codes (depending on how many there are). In Step 106, the homebase 14 recites the user access codes to the care provider and continues reciting the user access codes (Step 107) until all are recited. After completing reciting the user access codes, the homebase 14 returns (Step 108) the care provider to the access code menu 90 (via circle 6-E).
  • Fourth, in Step [0056] 109, the care provider is asked whether he or she would like to erase the user access codes and is instructed to press a certain button on the touch tone key pad (in this case the number “4”) to select this option. If the care provider selects this option, the homebase 14 asks the care provider to select one of two options: (1) to erase specific user access codes, press a certain button on the touch-tone key pad (in this case the number “1”) (see Step 1 10); or (2) to erase all user access codes, press a different button (in this case the number “2”) (see Step 115). If the care provider selects Step 1 10, the care provider is asked to enter the specific user access code to be deleted (Step 111), and the homebase 14 reads back that specific user access code in Step 1 12. The homebase 14 then asks the care provider to press the “#” button on the touch-tone key pad to accept deletion of that user access code (Step 113) and is returned to the access code menu in Step 114. If the care provider selects Step 115 (global deletion), the homebase 14 warns the care provider that he or she is about to erase all the user access codes and asks for the care provider to press the “#” button to accept (Step 1 16). The homebase then returns to the access code menu 90 (Step 117).
  • Fifth, in [0057] Step 118, the care provider is asked to press a certain number (in this case “5”) to exit the access code menu. If the care provider selects this option, the homebase 14 returns (via Step 119) to the access code prompt 62 (see FIG. 3).
  • Referring now to FIG. 5, the review mode will be described in detail. If the care provider has selected the review mode in [0058] Step 66, the homebase 14 transfers (circle 70) the care provider to a review mode menu 195 illustrated in FIG. 5. Upon accessing this menu, the homebase 14 generates a number of voice queries that are transmitted to the care provider and provide the care provider with a number of options—namely, reviewing the following information: (1) the operating parameters of a continuous mode of the pump 12 (Step 120); (2) the operating parameters of an intermittent mode of the pump 12 (Step 121); (3) the operating parameters of a taper mode of the pump 12 (Step 122); (4) the operating parameters of a patient controlled analgesia (PCA) mode in milliliters (mL) of the pump 12 (Step 123); and (5) the operating parameters of a PCA mode in milligrams (mg) of the pump 12 (Step 124). The continuous mode refers to a pump that continually delivers fluid to the patient, whereas the intermittent mode refers to intermittent delivery of fluids. The taper mode refers to a mode in which fluid delivery is stepped-up to a base rate then stepped-down to a “keep vein open” rate periodically during administration. The PCA mode refers to the ability of the patient to self-administer an additional burst (or “bolus”) of the fluid being administered by the pump. In other words, when the present dosage of analgesia being administered to the patient by the pump is inadequate to relieve pain, the patient can self-administer a bolus shot to bolster the dosage being automatically delivered by the pump.
  • If the care provider selects review of the continuous mode (Step [0059] 120), the homebase 14 provides the care provider with a variety of information. The care provider is told whether the protocol is locked or unlocked (Step 125); whether the “air-in-line” (AIL) alarm is on or off (Step 126); the elapsed time in hours, minutes, and/or seconds of the present administration to the patient (Step 127); the programmed rate of fluid being delivered in mLs per hour (Step 128); the current rate of fluid in mLs per hour (Step 129); the volume of fluid to be infused in mLs (Step 130); the volume of fluid already infused (Step 131); the level in mLs at which the low volume alarm will sound (Step 132); and the last occurrence of the alarm (Step 133). (See also FIG. 10, which illustrates the alarm table.) After providing this information to the care provider, the homebase 14 in Step 134 returns to the main menu 82.
  • If the care provider selects review of the intermittent mode (Step [0060] 121), the homebase 14 also provides the care provider with a variety of information. Steps 135-137 provide the same information as Steps 125 127, respectively. Step 141 provides the same information as Step 131, and Steps 145-146 provide the same information as Steps 132-133, respectively. Additional information provided to the care provider in the intermittent mode is as follows: the programmed dose rate of fluid being delivered in mLs per hour (Step 138); the current dose rate of fluid in mLs per hour (Step 139); the dose volume of fluid to be infused in mLs (Step 140); the background rate in mLs per hour (Step 142); the time between doses (or “Q” hours) (Step 143); and the number of doses (Step 144). After providing this information to the care provider, the homebase 14 returns in Step 147 to the main menu 82.
  • If the care provider selects review of the taper mode (Step [0061] 122), the homebase 14 also provides the care provider with a variety of information. Steps 148-150 provide the same information as Steps 125-127, respectively. Step 1 54 provides the same information as Step 1 31, and Steps 157-158 provide the same information as Steps 132-133, respectively. Additional information provided to the care provider in the taper mode is as follows: the programmed base rate of fluid being delivered in mLs per hour (Step 151); the current base rate of fluid in mLs per hour (Step 152); the volume of fluid before taper down in mLs (Step 153); the step-up rate in mLs per hour (Step 1 55); and the step-down rate in mLs per hour (Step 1 56). After providing this information to the care provider, the homebase 14 returns in Step 159 to the main menu 82.
  • If the care provider selects review of the PCA mL mode (Step [0062] 123), the care provider is also given information. Steps 160-162 provide the same information as Steps 125-127, respectively. Steps 165-166 provide the same information as Steps 130-131, respectively, and Steps 172-173 provide the same information as Steps 132-133, respectively. Additional information provided to the care provider in the PCA mL mode is as follows: the programmed continuous rate of fluid being delivered in mLs per hour (Step 163); the current continuous rate of fluid in mLs per hour (Step 164); the bolus volume of fluid in mLs (Step 167); the bolus interval in hours and minutes (Step 168); the number of boli/hour (Step 169); the number of boli attempted (Step 170); and the number of boli delivered (Step 171). After providing this information to the care provider, the homebase 14 returns in Step 174 to the main menu 82.
  • If the care provider selects review of the PICA mg mode (Step [0063] 124), the care provider is given other information. Steps 175-177 provide the same information as Steps 125-127, respectively, and Steps 188-189 provide the same information as Steps 132-133, respectively. Additional information provided to the care provider in the PCA mg mode is as follows: the concentration of fluid delivered in mg/mL (Step 178); the programmed continuous rate of fluid in mgs/hour (Step 179); the current continuous rate in mg s/hour (Step 180); the mgs to be infused (Step 181); the mgs infused in mgs (Step 182); the bolus dose in mgs (Step 183); the bolus interval in hours and minutes (Step 184); the number of boli/hour (Step 185); the number of boli attempted (Step 186); and the number of boli delivered (Step 187). After providing this information to the care provider, the homebase 14 returns in Step 190 to the main menu 82.
  • With reference to FIG. 6, the edit mode will be described in detail. If the care provider has selected the edit mode in [0064] Step 67, the homebase 14 transfers (circle 71) the care provider to an edit mode menu 200 illustrated in FIG. 6. Upon accessing this menu, the homebase 14 generates a number of voice queries that are transmitted to the care provider and provide the care provider with a number of options—namely: (1) editing the operating parameters of the continuous mode (Step 201); (2) editing the operating parameters of PCA mL mode (Step 202); and (3) editing the operating parameters of the PCA mg mode (Step 203). No matter which option is selected, after editing the operating parameters (or protocol) of that mode, the care provider is transferred (see circle 204) to the edit mode sub-menus 270, 280 illustrated FIG. 7.
  • If the care provider selects editing of the continuous mode (Step [0065] 201), the homebase 14 permits the care provider to edit the rate of delivery. In this mode, some parameters are maintained and others may be edited. The care provider is told the current rate at which the pump 12 is delivering fluid in mLs/hour (Step 210). The care provider is then asked to enter a new rate, or press the “#” button to accept the current rate (Step 211). Finally, the care provider is told the new rate in mLs/hour and is asked to press the “#” button on the key pad to accept the new rate (Step 212). After the rate has been edited, the homebase 14 transfers (circle 204) to the sub-menus 270, 280 of FIG. 7.
  • If the care provider selects editing of the PCA mL mode (Step [0066] 202), the care provider is asked to edit various parameters of the PCA mL protocol. The care provider is first told what the current continuous rate is in mLs/hour (Step 221), and in Step 222 is asked to enter a new continuous rate or press the “#” button to accept the present rate. The care provider is then told what the new rate is and asked to press the “#” button to accept that new rate (Step 223). Similar operations are performed on the bolus volume (Steps 224-226), the number of boli/hour (Steps 227-229), and the bolus interval (Steps 230-232). After editing, the homebase 14 transfers (circle 204) to the sub-menus 270, 280 of FIG. 7.
  • If the care provider selects editing of the PCA mg mode (Step [0067] 203), the care provider is asked to edit various parameters of the PCA mL protocol. The care provider is first told what the current continuous rate is in mgs/hour (Step 241), and in Step 242 is asked to enter a new continuous rate or press the “#” button to accept the present rate. The care provider is then told what the new rate is and asked to press the “#” button to accept that new rate (Step 243). Similar operations are performed on the bolus volume (Steps 244-246), the number of boli/hour (Steps 247-2491, and the bolus interval (Steps 250-252). After editing, the homebase 14 transfers (circle 204) to the sub-menus 270, 280 of FIG. 7.
  • Referring now to FIG. 7, the [0068] edit mode sub-menus 270, 280 provide the care provider with several options after editing the protocol. The first edit mode sub-menu 270 allows the care provider to send (i.e., save) the edits to the pump 1 2 (Step 271) by pressing a certain key on the key pad (in this case “1”), to review the edits (Step 272) by pressing a different key on key pad (in this case “2”), and to cancel the edits (Step 273) by pressing still a different number on she key pad (in this case “3”). If the care provider selects sending the edits (Step 271), the new protocol is sent to the pump 12 (Step 274), and the care provider is told “goodbye” (Step 275). The care provider is then transferred to the phone or patient conversation mode (Step 276), and the care provider is put in connection with the patient to verify the programming (Step 277). After verifying the programming changes with the patient, the care provider hangs up the remote telephone (Step 278), and the programming session is terminated.
  • If the care provider selects reviewing the edits (Step [0069] 272), the homebase 14 reports the new parameters of the protocol to the care provider (Step 279). After reporting, the care provider is taken to the second edit mode sub-menu 280. The second edit mode sub-menu 280 permits the care provider to select one of several options: (1) send the edits by pressing a key on the key pad (Step 281), (2) edit the edits by pressing a different key on the key pad (Step 282), or (3) cancel the edits by pressing still a different key on the key pad (Step 283). If the care provider selects sending the edits (Step 281), the new protocol is sent to the pump 12 (Step 284), and the care provider is told “goodbye” (Step 285). The care provider is then transferred to the phone or patient conversation mode (Step 286), and the care provider is put in connection with the patient (the patient conversation mode) to verify the programming (Step 287). After verifying the programming changes with the patient, the care provider hangs up the remote telephone (Step 288), and the programming session is terminated. If the care provider selects editing of the edits (Step 282), the care provider is transferred to the edit mode menu (Step 289) illustrated in FIG. 6 and described above. If the care provider selects cancelling of the edits (Step 283), the care provider is transferred to the main menu 82 (Step 290).
  • With reference to FIGS. 8A and 8B, the create mode will now be described. If the care provider selects the create mode in [0070] Step 68, the homebase 14 transfers the care provider to a create mode menu 300. Within the create mode menu 300, the care provider has several options for processing the protocol: (1) the continuous mode 302, (2) the intermittent mode 304, (3) the taper mode 306, and (4) the PCA mode 308. For any of these modes to be selected, the care provider presses a predetermined number on the keypad of the remote programming transceiver or push button telephone.
  • If the care provider selects programming of the [0071] continuous mode 302 from the create mode menu 300, the care provider is asked to program various parameters of the continuous mode protocol. The care provider is asked to enter the rate (Step 310), after which the entered rate is read back, and the care provider is asked to press the “#” button to accept this rate (Step 31 1). The care provider follows the same procedure for entering volume (Steps 312 and 313), low volume alarm (Steps 314 and 315), protocol locking (Steps 316 and 317), and AIL on or off (Steps 318 and 319). After programming, the care provider is transferred (circle 397) to the sub-menus of FIG. 9.
  • If the care provider selects programming of the [0072] intermittent mode 304, the care provider is asked to program various parameters of the intermittent mode protocol. The care provider is asked to enter the number of “Q” hours (Step 320), after which the entered number of “Q” hours is read back, and the care provider is asked to press the “#” button to accept this number (Step 321). The care provider follows the same procedure for entering dose rate (Steps 322 and 323), dose volume (Steps 324 and 325), background rate (Steps 326 and 327), number of deliveries (Steps 328 and 329), low volume alarm (Steps 330 and 331), protocol locking (Steps 332 and 333), and AIL on or off (Steps 334 and 335). After programming, the care provider is transferred (circle 397) to the sub-menus of FIG. 9.
  • If the care provider selects programming of the [0073] taper mode 306, the care provider is asked to program various parameters of the taper mode protocol. The care provider is asked to enter the total volume (Step 336), after which the entered total volume is read back, and the care provider is asked to press the “#” button to accept (Step 337) this volume. The care provider follows the same procedure for entering taper up time (Steps 338 and 339), taper down time (Steps 340 and 341), and total delivery time (Steps 342 and 343). The homebase unit 14 then calculates the base rate (Step 344) and reads this base rate back to the care provider (Step 345); calculates the volume before taper down (Step 346) and reads this volume back to the care provider (Step 347); and calculates the step up and step down rates (Steps 348 and 350) and reads these back (Steps 349 and 351). The care provider is also asked to enter protocol locking (Steps 352 and 353) and AIL on or off (Steps 354 and 355). After programming, the care provider is transferred (circle 397) to the sub-menus of FIG. 9.
  • If the care provider selects programming of the [0074] PCA mode 308, the care provider is taken to a PCA mode sub-menu 360. In the PCA mode sub-menu 360, the care provider is asked to select the PCA mL mode (Step 361) or the PCA mg mode (Step 362). If the care provider selects the PCA mL mode, the care provider is asked to enter the protocol of this mode, including the continuous rate (Steps 363 and 364), total volume (Steps 365 and 366), bolus volume (Steps 367 and 368), number of boli/hour (Steps 369 and 370), bolus interval (Steps 371 and 372), low volume alarm (Steps 373 and 374), protocol locking (Steps 375 and 376), and AIL on or off (Steps 377 and 378). If the care provider selects the PCA mg mode (Step 362), the care provider is asked to enter that mode's protocol, including the concentration (Steps 379 and 380), continuous rate (Steps 381 and 382), total volume (Steps 383 and 384), bolus volume (Steps 385 and 386), number of boli/hour (Steps 387 and 388), bolus interval (Steps 389 and 390), low volume alarm (Steps 391 and 392), protocol locking (Steps 393 and 394), and AIL on or off (Steps 395 and 396). After programming, the care provider is transferred (circle 397) to the sub-menus of FIG. 9.
  • Referring now to FIG. 9, after a programming sequence in accordance with FIGS. 8A and 8B, the care provider is transferred (via circle [0075] 397) to a primary create mode sub-menu 400. In the primary create mode sub-menu 400, the care provider can make various selections, including sending the newly programmed protocol (Step 402), reviewing the newly programmed protocol (Step 404), and cancelling the newly programmed protocol (Step 406). If the care provider selects send (Step 402), the care provider is told that the new protocol is being sent to the pump 12 and then told “goodbye” (Steps 410 and 41 1), and the connection is switched to the phone or patient conversation mode (i.e., communication with the patient) (Step 412). The care provider may then speak with the patient to verify the programming (Step 413) and then hang up after verifying (Step 414). If the cancel option 406 is selected, the care provider is transferred (Step 437) to the main menu 82.
  • If the [0076] review option 404 is selected, the parameters of the new programmed protocol are reported to the care provider (Step 415). The care provider is then transferred to a secondary create mode sub-menu 420, from which the care provider can select various options, including sending the new protocol (Step 422), editing the new protocol (Step 424), and cancelling the new protocol (Step 426). If the sending option 422 is selected, Steps 430 through 434 are performed, which are the same as those performed if the care provider were to select the sending option 402 from the primary create mode sub-menu 400. If the editing option 424 is selected, the care provider is transferred (Step 435) to the create mode menu 300. Finally, if the cancel option 424 is selected, the care provider is transferred (Step 436) to the main menu 82.
  • In all of the above processing modes, the [0077] homebase 14 can be provided with a variety of features that facilitates remote or local programming of the protocol. For example, “#” key can be used to enter changes or selections. The “*” key can be used for exiting the programming mode, for backspacing from a currently operating step to a previous step or from a portion of a parameter being processed to a previous portion of that parameter, or for entering a decimal point, depending on the instance in the programming sequence. The system can be set up such that it rejects out of range values and advises on the erroneous value. If the communicating phone line is equipped with call waiting, the existence of an incoming call on the additional call waiting line does not cause the presently communicating (i.e., programming) line to hang up. With reference to FIG. 10, an alarm table 500 of the present invention will be described. The alarm table 500 may include a variety of alarm functions, including air in the line alarm 502 for the line 18 connecting the pump 12 to the patient, a bad battery alarm 504, a bar code fault alarm 506, an alarm indicating the need for a battery change 508, a door open alarm 510, an end of program alarm 512, a low battery alarm 514, a low volume alarm 516, a malfunction alarm 518, an occlusion alarm 520, an over-voltage alarm 522, a pump interrupted alarm 524, and a pumping complete alarm 526. All of these alarms can be made audible, with a variety of different or identical tones, or visual, via the alarm light 40, multiple lights, or a digital or analog display. The above alarm functions are exemplary, and other alarm functions can be provided. Alternatively, only some, or one, or none of the above alarm functions can be implemented in the present invention, depending on the particular application.
  • Examples of how the [0078] alarm light 40 and internal audio device 29 operate in response to various alarm conditions will now be described. The alarm light 40 may comprise a number of lights, for example, red, yellow, green, and other colored LEDs. The audio device 29 may comprise a speaker, siren, or similar apparatus. As an example of an alarm condition and the response thereto, if the phone line is improperly connected to the homebase unit 14 or the infusion system 10 is setup in some other improper manner, red and green LEDs (which comprise the alarm light 40) may flash together with intermittent audio from the audio device 29. If someone is trying to access the local mode (i.e., communicate with the homebase 14 via a local telephone connected to the local communication port 44) without the local telephone line being attached to the homebase 14, a yellow LED may flash with intermittent audio. If someone is trying to access the local, send, or link modes (i.e., is depressing the link button 30, local button 32, or send button 34) without the pump 12 being properly attached to the homebase 14, yellow and red LEDs may flash with intermittent audio. If the telephone connection between the remote or local telephone and the homebase 14 is lost, a red LED may flash with intermittent audio. Finally, if an internal system error occurs in the homebase 14 and/or pump 12, a red LED may flash with intermittent audio. It should be understood that the above operation of the alarm light 40 and audio device 29 are only exemplary and that variations can be made on these alarms.
  • It should also be understood that the above programming and functions described in FIGS. [0079] 3-10 provide only examples of how the care provider and the homebase unit 14 may interact via a remote or local push button telephone or similar transceiver. Therefore, additional or alternative steps and procedures can be designed and implemented for remote programming of the present invention. Accordingly, only some of the steps described above need be included in the invention; the steps may be conducted in a different order; additional or fewer protocol parameters may be controlled by the care provider; and different operational modes (i.e., other than continuous, intermittent, etc.) may be chosen.
  • Furthermore, the present invention can be used in a variety of applications. In the exemplary application described herein, the present invention is used for controlling and programming the protocol of an infusion pump. A variety of infusion applications exist for which the present invention can be used, including ambulatory IVs, insulin pumps, hospital pumps, enteral pumps, blood pumps, intra-aortal pumps, subcutaneous pumps, and spinal (or epidural) pumps. Other medical applications also exist in which the present invention can be used for remote programming, as well as other functions described above, including use with ventilators (e.g., for blood/oxygen level), respiratory equipment, EKG machines, blood/gas analyzers, enteral pumps (i.e., stomach infusion pumps), blood glucose monitors, dialysis equipment, open wound irrigation devices, and urology equipment. [0080]
  • It will therefore be apparent to those skilled in the art that various modifications and variations can be made in the apparatus and method of the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention cover the modifications and variations of this invention, provided they come within the scope of the appended claims and their equivalents. [0081]

Claims (30)

What is claimed is:
1. A remotely programmable infusion system having a programmable protocol, said remotely programmable infusion system being programmable by a remote touch-tone transceiver, comprising
a memory for storing said programmable protocol; a voice storage unit for storing a voice signal;
a remote communication port for sending said voice signal to said remote touch-tone transceiver and for receiving a remote programming signal from said remote touch-tone transceiver; and
a processor, coupled to said remote communication port and to said voice storage unit and to said memory, for accessing said voice signal from said voice storage unit, for accessing said programmable protocol from said memory, and for processing said programmable protocol in response to receiving said remote programming signal.
2. The remotely programmable infusion system recited in claim 1 wherein the remotely programmable infusion system has a user access code; and wherein the processor permits remote programming of the programmable protocol in response to receiving said user access code from the remote touch-tone transceiver.
3. The remotely programmable infusion system recited in claim 1 wherein the remotely programmable infusion system has a user access code and a master access code; wherein the user access code is stored in the memory and is programmable; wherein the processor permits programming of the user access code in response to receiving said master access code from the remote touch-tone transceiver; and wherein the processor permits remote programming of the programmable protocol in response to receiving said user access code from the remote touch-tone transceiver.
4. The remotely programmable infusion system recited in claim 1 wherein the processor accesses a mode query signal from the voice storage unit, the remote communication port relays said mode query signal from the processor to the remote transceiver, and the processor selects one of a plurality of programming modes in response to a mode select signal being received from the remote touch-tone transceiver, said mode select signal being sent by the remote touch-tone transceiver in response to the remote touch-tone transceiver receiving said mode query signal.
5. The remotely programmable infusion system recited in claim 4 wherein the plurality of programming modes includes an edit mode for editing the programmable protocol, a review mode for reviewing the programmable protocol, and a create mode for entering a new programmable protocol.
6. The remotely programmable infusion system recited in claim 1, further comprising a local communication port, coupled to the processor, for relaying signals between the processor and a local touch-tone transceiver.
7. The remotely programmable infusion system recited in claim 1 wherein the remotely programmable infusion system has a status report mode, the remotely programmable infusion system further comprising a switch for selecting said status report mode; and wherein the processor accesses the programmable protocol from the memory in response to said status report mode being selected.
8. The remotely programmable infusion system recited in claim 7 wherein the remote communication port relays the programmable protocol from the processor to a computer in response to the processor accessing the programmable protocol.
9. The remotely programmable infusion system recited in claim 1, further comprising a programming access switch for selecting either a patient conversation mode or a programming mode, said programming mode providing programming of the programmable protocol by the remote touch-tone transceiver.
10. The remotely programmable infusion system recited in claim 9, further comprising an override circuit for bypassing the patient conversation mode and thereby directly initiating the programming mode.
11. The remotely programmable infusion system recited in claim 1, further comprising an alarm for indicating an alarm condition in the remotely programmable infusion system.
12. The remotely programmable infusion system recited in claim 1 wherein the voice signal is a digital voice signal, the system further comprising a voice synthesizer for converting said digital voice signal into an analog human voice signal, said analog human voice signal emulating the sound of a human voice.
13. A method for remotely programming an infusion system, said infusion system having a voice storage unit for storing a voice signal and having a programmable protocol, said infusion system being programmable by a remote touch-tone transceiver, the method comprising:
establishing a connection between said infusion system and said remote touch-tone transceiver;
first accessing said voice signal from said voice storage unit after establishing said connection between said remote touch-tone transceiver and said infusion system;
first sending said voice signal to said remote touch-tone transceiver;
second receiving a remote programming signal from said remote touch-tone transceiver; and
processing said programmable protocol in response to receiving said remote programming signal.
14. The method recited in claim 13 wherein the infusion system has a user access code and the voice storage unit stores an access code voice command, the method further comprising:
second sending said access code voice command to the remote touch-tone transceiver in response to establishing the connection; and
initiating a remote programming session for the programmable protocol in response to receiving said user access code from the remote touch-tone transceiver.
15. The method recited in claim 13 wherein the infusion system has a master access code and a user access code, wherein the user access code is programmable, and wherein the voice storage unit stores an access code voice command, the method further comprising:
second sending said access code voice command to the remote touch-tone transceiver in response to establishing the connection;
first initiating a remote programming session for said user access code in response to receiving said master access code from the remote touch-tone transceiver; and
second initiating a remote programming session for the programmable protocol in response to receiving said user access code from the remote touch-tone transceiver.
16. The method recited in claim 13, further comprising:
second accessing a mode query signal from the voice storage unit;
second sending said mode query signal to the remote touch-tone transceiver;
third sending a mode select signal from the remote touch-tone transceiver to the infusion system in response to said mode query signal; and
selecting one of a plurality of programming modes in response to receiving said mode select signal.
17. The method recited in claim 16 wherein the plurality of programming modes includes an edit mode for editing the programmable protocol, a review mode for reviewing the programmable protocol, and a create mode for entering a new programmable protocol.
18. The method recited in claim 13, further comprising relaying signals between the infusion system and a local transceiver.
19. The method recited in claim 13 wherein the infusion system has a status report mode and a protocol memory for storing the programmable protocol, the method further comprising selecting said status report mode; and accessing the programmable protocol from the protocol memory in response to selecting said status report mode.
20. The method recited in claim 19, further comprising second sending the programmable protocol to a computer in response to accessing the programmable protocol from the protocol memory.
21. The method in claim 13, further comprising selecting either a patient conversation mode or a programming mode, said programming mode providing for remote programming of the programmable protocol by the remote touch-tone transceiver.
22. The method recited in claim 21, further comprising bypassing the patient conversation mode and thereby directly initiating the programming mode.
23. The method recited in claim 13, further comprising detecting an alarm condition in the infusion system and indicating said alarm condition.
24. The method recited in claim 13 wherein the voice signal comprises a digital voice signal, the method further comprising converting said digital voice signal to a human voice signal, said human voice signal emulating the sound of a human voice.
25. A remotely programmable infusion system having a programmable protocol stored in a protocol memory, said remotely programmable infusion system being programmable by a remote touch-tone transceiver, comprising:
an infusion pump for delivering fluids to a patient, said infusion pump having a pump data port; and
a homebase unit, coupled to said pump data port on said infusion pump via a homebase data port, for processing said programmable protocol, said homebase unit comprising:
a voice storage unit for storing a voice signal;
a remote communication port for sending said voice signal to said remote touch-tone transceiver and for receiving a remote signal from said remote touch-tone transceiver; and
a processor, coupled to said remote communication port and to said voice storage unit and to said protocol memory, for accessing said voice signal from said voice storage unit, for accessing said programmable protocol from said protocol memory, and for processing said programmable protocol to obtain a processed programmable protocol in response to said remote signal, said processed programmable protocol being relayed from said processor to said infusion pump via said homebase data port and said infusion data port.
26. The remotely programmable infusion system recited in claim 25 wherein the remote signal comprises a DTMF signal and wherein the remote touch-tone transceiver has a keypad, said keypad having a plurality of touch-tone keys, and the DTMF signal being generated by pressing one of said plurality of touch-tone keys.
27. The remotely programmable infusion system recited in claim 26 wherein the programmable protocol has a plurality of operating parameters, and wherein the voice signal comprises either a recorded voice command or a recorded voice query, said recorded voice command instructing a care provider operating the remote touch-tone transceiver to press at least one of the plurality of touch tone keys, and said recorded voice query asking said care provider operating the remote touch-tone transceiver to enter at least one of said plurality of operating parameters via the plurality of touch-tone keys.
28. The remotely programmable infusion device recited in claim 25 wherein the remotely programmable infusion system has a user access code; and wherein the processor permits remote programming of the programmable protocol in response to receiving said user access code from the remote touch-tone transceiver.
29. The remotely programmable infusion system recited in claim 25 wherein the remotely programmable infusion system has a user access code and a master access code; wherein the user access code is stored in an access code memory and is programmable; wherein the processor permits programming of the user access code in response to receiving said master access code from the remote touch-tone transceiver; and wherein the processor permits remote programming of the programmable protocol in response to receiving said user access code from the remote touch-tone transceiver.
30. The remotely programmable infusion system recited in claim 25 wherein the voice signal comprises a digital voice signal, the system further comprising a voice synthesizer for converting said digital voice signal to a human voice signal, said human voice signal emulating the sound of a human voice.
US10/097,552 1994-11-25 2002-03-12 Remotely programmable infusion system Expired - Fee Related US6749586B2 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US10/097,552 US6749586B2 (en) 1994-11-25 2002-03-12 Remotely programmable infusion system
US10/868,662 US7153289B2 (en) 1994-11-25 2004-06-15 Remotely programmable infusion system
US11/608,167 US20070100394A1 (en) 1994-11-25 2006-12-07 Remotely programmable infusion system

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US08/344,973 US5573506A (en) 1994-11-25 1994-11-25 Remotely programmable infusion system
US08/658,689 US5871465A (en) 1994-11-25 1996-06-05 Remotely programmable infusion system
US09/251,021 US6228057B1 (en) 1994-11-25 1999-02-16 Remotely programmable infusion system
US09/626,571 US6355018B1 (en) 1995-11-25 2000-07-27 Remotely programmable infusion system
US10/097,552 US6749586B2 (en) 1994-11-25 2002-03-12 Remotely programmable infusion system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US09/626,571 Continuation US6355018B1 (en) 1994-11-25 2000-07-27 Remotely programmable infusion system

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10/868,662 Continuation US7153289B2 (en) 1994-11-25 2004-06-15 Remotely programmable infusion system

Publications (2)

Publication Number Publication Date
US20020091454A1 true US20020091454A1 (en) 2002-07-11
US6749586B2 US6749586B2 (en) 2004-06-15

Family

ID=27500380

Family Applications (3)

Application Number Title Priority Date Filing Date
US10/097,552 Expired - Fee Related US6749586B2 (en) 1994-11-25 2002-03-12 Remotely programmable infusion system
US10/868,662 Expired - Fee Related US7153289B2 (en) 1994-11-25 2004-06-15 Remotely programmable infusion system
US11/608,167 Abandoned US20070100394A1 (en) 1994-11-25 2006-12-07 Remotely programmable infusion system

Family Applications After (2)

Application Number Title Priority Date Filing Date
US10/868,662 Expired - Fee Related US7153289B2 (en) 1994-11-25 2004-06-15 Remotely programmable infusion system
US11/608,167 Abandoned US20070100394A1 (en) 1994-11-25 2006-12-07 Remotely programmable infusion system

Country Status (1)

Country Link
US (3) US6749586B2 (en)

Cited By (48)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20060102091A1 (en) * 2004-08-09 2006-05-18 Bioanalytical Systems, Inc. (An Indiana Corporation) Portable sampling or testing device and method for pharmacokinetics and physiology studies
WO2006098927A1 (en) * 2005-03-09 2006-09-21 Cardinal Health 303, Inc. System and method for controlling access to features of a medical instrument
WO2008055037A3 (en) * 2006-10-31 2008-07-03 Abbott Diabetes Care Inc Infusion devices and methods
US7679407B2 (en) 2003-04-28 2010-03-16 Abbott Diabetes Care Inc. Method and apparatus for providing peak detection circuitry for data communication systems
US7756561B2 (en) 2005-09-30 2010-07-13 Abbott Diabetes Care Inc. Method and apparatus for providing rechargeable power in data monitoring and management systems
US7768408B2 (en) 2005-05-17 2010-08-03 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US7922458B2 (en) 2002-10-09 2011-04-12 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8016789B2 (en) 2008-10-10 2011-09-13 Deka Products Limited Partnership Pump assembly with a removable cover assembly
US8029460B2 (en) 2005-03-21 2011-10-04 Abbott Diabetes Care Inc. Method and system for providing integrated medication infusion and analyte monitoring system
US8034026B2 (en) 2001-05-18 2011-10-11 Deka Products Limited Partnership Infusion pump assembly
US8047811B2 (en) 2002-10-09 2011-11-01 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8066672B2 (en) 2008-10-10 2011-11-29 Deka Products Limited Partnership Infusion pump assembly with a backup power supply
US8112138B2 (en) 2005-06-03 2012-02-07 Abbott Diabetes Care Inc. Method and apparatus for providing rechargeable power in data monitoring and management systems
US8113244B2 (en) 2006-02-09 2012-02-14 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US8223028B2 (en) 2008-10-10 2012-07-17 Deka Products Limited Partnership Occlusion detection system and method
US8262616B2 (en) 2008-10-10 2012-09-11 Deka Products Limited Partnership Infusion pump assembly
US8267892B2 (en) 2008-10-10 2012-09-18 Deka Products Limited Partnership Multi-language / multi-processor infusion pump assembly
US8343093B2 (en) 2002-10-09 2013-01-01 Abbott Diabetes Care Inc. Fluid delivery device with autocalibration
US8344966B2 (en) 2006-01-31 2013-01-01 Abbott Diabetes Care Inc. Method and system for providing a fault tolerant display unit in an electronic device
US8414563B2 (en) 2007-12-31 2013-04-09 Deka Products Limited Partnership Pump assembly with switch
US8467972B2 (en) 2009-04-28 2013-06-18 Abbott Diabetes Care Inc. Closed loop blood glucose control algorithm analysis
US8496646B2 (en) 2007-02-09 2013-07-30 Deka Products Limited Partnership Infusion pump assembly
US8560082B2 (en) 2009-01-30 2013-10-15 Abbott Diabetes Care Inc. Computerized determination of insulin pump therapy parameters using real time and retrospective data processing
US8638220B2 (en) 2005-10-31 2014-01-28 Abbott Diabetes Care Inc. Method and apparatus for providing data communication in data monitoring and management systems
US8708376B2 (en) 2008-10-10 2014-04-29 Deka Products Limited Partnership Medium connector
US8798934B2 (en) 2009-07-23 2014-08-05 Abbott Diabetes Care Inc. Real time management of data relating to physiological control of glucose levels
US20140338663A1 (en) * 2006-01-03 2014-11-20 Shahzad Saad Pirzada System, device and process for remotely controlling a medical device
US9173996B2 (en) 2001-05-18 2015-11-03 Deka Products Limited Partnership Infusion set for a fluid pump
US9180245B2 (en) 2008-10-10 2015-11-10 Deka Products Limited Partnership System and method for administering an infusible fluid
US9204833B2 (en) 2012-03-27 2015-12-08 Phlebotics, Inc. Cartridge for automated blood sampling system
US10272190B2 (en) * 2008-07-09 2019-04-30 Baxter International Inc. Renal therapy system including a blood pressure monitor
WO2021059210A1 (en) 2019-09-25 2021-04-01 Janssen Pharmaceuticals, Inc. Interconnection of drug administration systems
WO2022079514A1 (en) 2020-05-06 2022-04-21 Janssen Pharmaceuticals, Inc. Monitoring and communicating information using drug administration devices
WO2022079513A1 (en) 2020-05-06 2022-04-21 Janssen Pharmaceuticals, Inc. Patient monitoring using drug administration devices
US11364335B2 (en) 2006-02-09 2022-06-21 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11395877B2 (en) 2006-02-09 2022-07-26 Deka Products Limited Partnership Systems and methods for fluid delivery
US11404776B2 (en) 2007-12-31 2022-08-02 Deka Products Limited Partnership Split ring resonator antenna adapted for use in wirelessly controlled medical device
US11426512B2 (en) 2006-02-09 2022-08-30 Deka Products Limited Partnership Apparatus, systems and methods for an infusion pump assembly
US11478623B2 (en) 2006-02-09 2022-10-25 Deka Products Limited Partnership Infusion pump assembly
US11497846B2 (en) 2006-02-09 2022-11-15 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11497686B2 (en) 2007-12-31 2022-11-15 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11524151B2 (en) 2012-03-07 2022-12-13 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11523972B2 (en) 2018-04-24 2022-12-13 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11534542B2 (en) 2007-12-31 2022-12-27 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11597541B2 (en) 2013-07-03 2023-03-07 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11642283B2 (en) 2007-12-31 2023-05-09 Deka Products Limited Partnership Method for fluid delivery
US11723841B2 (en) 2007-12-31 2023-08-15 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11890448B2 (en) 2006-02-09 2024-02-06 Deka Products Limited Partnership Method and system for shape-memory alloy wire control

Families Citing this family (166)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6749586B2 (en) * 1994-11-25 2004-06-15 I-Flow Corporation Remotely programmable infusion system
US6671563B1 (en) * 1995-05-15 2003-12-30 Alaris Medical Systems, Inc. System and method for collecting data and managing patient care
US8504179B2 (en) * 2002-02-28 2013-08-06 Smiths Medical Asd, Inc. Programmable medical infusion pump
US8250483B2 (en) 2002-02-28 2012-08-21 Smiths Medical Asd, Inc. Programmable medical infusion pump displaying a banner
US8065161B2 (en) 2003-11-13 2011-11-22 Hospira, Inc. System for maintaining drug information and communicating with medication delivery devices
US9123077B2 (en) 2003-10-07 2015-09-01 Hospira, Inc. Medication management system
US7029456B2 (en) * 2003-10-15 2006-04-18 Baxter International Inc. Medical fluid therapy flow balancing and synchronization system
US8954336B2 (en) 2004-02-23 2015-02-10 Smiths Medical Asd, Inc. Server for medical device
US7758563B2 (en) * 2004-09-09 2010-07-20 Plc Medical Systems, Inc. Patient hydration monitoring and maintenance system and method for use with administration of a diuretic
US11213621B2 (en) 2004-09-09 2022-01-04 Reprieve Cardiovascular, Inc. Fluid therapy method
US20080027409A1 (en) * 2004-09-09 2008-01-31 Rudko Robert I Patient hydration/fluid administration system and method
US7736354B2 (en) * 2004-09-09 2010-06-15 Plc Medical Systems, Inc. Patient hydration system with hydration state detection
US20180185577A9 (en) 2004-09-09 2018-07-05 Plc Medical Systems, Inc. Fluid therapy method
US7837667B2 (en) * 2004-09-09 2010-11-23 Plc Medical Systems, Inc. Patient hydration system with abnormal condition sensing
US7938817B2 (en) * 2004-09-09 2011-05-10 Plc Medical Systems, Inc. Patient hydration system and method
US7758562B2 (en) 2004-09-09 2010-07-20 Plc Medical Systems, Inc. Patient hydration system with a redundant monitoring of hydration fluid infusion
US7727222B2 (en) * 2004-09-09 2010-06-01 Plc Medical Systems, Inc. Patient hydration system with taper down feature
US20070088333A1 (en) * 2005-10-13 2007-04-19 G&L Consulting, Llc Method and system for infusing an osmotic solute into a patient and providing feedback control of the infusing rate
US20070158249A1 (en) * 2006-01-06 2007-07-12 Ash Stephen R Dialysis machine with transport mode
US20070158268A1 (en) * 2006-01-06 2007-07-12 Decomo Peter Dual purpose acute and home treatment dialysis machine
US20070253021A1 (en) * 2006-04-28 2007-11-01 Medtronic Minimed, Inc. Identification of devices in a medical device network and wireless data communication techniques utilizing device identifiers
US8073008B2 (en) 2006-04-28 2011-12-06 Medtronic Minimed, Inc. Subnetwork synchronization and variable transmit synchronization techniques for a wireless medical device network
US20070258395A1 (en) * 2006-04-28 2007-11-08 Medtronic Minimed, Inc. Wireless data communication protocols for a medical device network
US20070255126A1 (en) * 2006-04-28 2007-11-01 Moberg Sheldon B Data communication in networked fluid infusion systems
US20070255125A1 (en) 2006-04-28 2007-11-01 Moberg Sheldon B Monitor devices for networked fluid infusion systems
US8149131B2 (en) 2006-08-03 2012-04-03 Smiths Medical Asd, Inc. Interface for medical infusion pump
US8435206B2 (en) 2006-08-03 2013-05-07 Smiths Medical Asd, Inc. Interface for medical infusion pump
US8858526B2 (en) 2006-08-03 2014-10-14 Smiths Medical Asd, Inc. Interface for medical infusion pump
US8965707B2 (en) 2006-08-03 2015-02-24 Smiths Medical Asd, Inc. Interface for medical infusion pump
US8025634B1 (en) * 2006-09-18 2011-09-27 Baxter International Inc. Method and system for controlled infusion of therapeutic substances
US8075513B2 (en) * 2006-10-13 2011-12-13 Plc Medical Systems, Inc. Patient connection system for a balance hydration unit
CA2666509C (en) 2006-10-16 2017-05-09 Hospira, Inc. System and method for comparing and utilizing activity information and configuration information from multiple medical device management systems
US8034019B2 (en) * 2007-04-10 2011-10-11 Amrita Vishwa Vidyapeetham Dual microcontroller-based liquid infusion system
US20080300572A1 (en) * 2007-06-01 2008-12-04 Medtronic Minimed, Inc. Wireless monitor for a personal medical device system
CN102831293B (en) 2007-08-10 2016-05-18 施曼信医疗Asd公司 The formulating method of Medical Equipment Maintenance timetable and management system
US9129047B2 (en) * 2007-10-03 2015-09-08 Medallion Therapeutics, Inc. Programming and bolus monitoring device for an implantable drug pump
US8313467B2 (en) 2007-12-27 2012-11-20 Medtronic Minimed, Inc. Reservoir pressure equalization systems and methods
US20110004188A1 (en) * 2008-02-04 2011-01-06 Avraham Shekalim Drug delivery system with wireless monitor
US8133197B2 (en) 2008-05-02 2012-03-13 Smiths Medical Asd, Inc. Display for pump
US10045734B2 (en) 2009-01-28 2018-08-14 Plc Medical Systems, Inc. Fluid replacement device
US8271106B2 (en) 2009-04-17 2012-09-18 Hospira, Inc. System and method for configuring a rule set for medical event management and responses
DE102009002537A1 (en) * 2009-04-21 2010-10-28 Robert Bosch Gmbh Medical device to be used by a patient
US8777897B2 (en) * 2009-07-06 2014-07-15 Carefusion 303, Inc. Fluid delivery systems and methods having wireless communication
US8344847B2 (en) 2009-07-09 2013-01-01 Medtronic Minimed, Inc. Coordination of control commands in a medical device system having at least one therapy delivery device and at least one wireless controller device
US8487758B2 (en) 2009-09-02 2013-07-16 Medtronic Minimed, Inc. Medical device having an intelligent alerting scheme, and related operating methods
US8386042B2 (en) 2009-11-03 2013-02-26 Medtronic Minimed, Inc. Omnidirectional accelerometer device and medical device incorporating same
US8574201B2 (en) 2009-12-22 2013-11-05 Medtronic Minimed, Inc. Syringe piston with check valve seal
US8755269B2 (en) 2009-12-23 2014-06-17 Medtronic Minimed, Inc. Ranking and switching of wireless channels in a body area network of medical devices
US8603033B2 (en) 2010-10-15 2013-12-10 Medtronic Minimed, Inc. Medical device and related assembly having an offset element for a piezoelectric speaker
US8562565B2 (en) 2010-10-15 2013-10-22 Medtronic Minimed, Inc. Battery shock absorber for a portable medical device
US8603032B2 (en) 2010-10-15 2013-12-10 Medtronic Minimed, Inc. Medical device with membrane keypad sealing element, and related manufacturing method
US8479595B2 (en) 2010-10-20 2013-07-09 Medtronic Minimed, Inc. Sensor assembly and medical device incorporating same
US8495918B2 (en) 2010-10-20 2013-07-30 Medtronic Minimed, Inc. Sensor assembly and medical device incorporating same
US8474332B2 (en) 2010-10-20 2013-07-02 Medtronic Minimed, Inc. Sensor assembly and medical device incorporating same
US8628510B2 (en) 2010-12-22 2014-01-14 Medtronic Minimed, Inc. Monitoring the operating health of a force sensor in a fluid infusion device
US8469942B2 (en) 2010-12-22 2013-06-25 Medtronic Minimed, Inc. Occlusion detection for a fluid infusion device
US8197444B1 (en) 2010-12-22 2012-06-12 Medtronic Minimed, Inc. Monitoring the seating status of a fluid reservoir in a fluid infusion device
US8690855B2 (en) 2010-12-22 2014-04-08 Medtronic Minimed, Inc. Fluid reservoir seating procedure for a fluid infusion device
US9283318B2 (en) 2011-02-22 2016-03-15 Medtronic Minimed, Inc. Flanged sealing element and needle guide pin assembly for a fluid infusion device having a needled fluid reservoir
US9463309B2 (en) 2011-02-22 2016-10-11 Medtronic Minimed, Inc. Sealing assembly and structure for a fluid infusion device having a needled fluid reservoir
US9393399B2 (en) 2011-02-22 2016-07-19 Medtronic Minimed, Inc. Sealing assembly for a fluid reservoir of a fluid infusion device
US20120211946A1 (en) 2011-02-22 2012-08-23 Medtronic Minimed, Inc. Sealing element for a hollow needle of a fluid infusion device
US8614596B2 (en) 2011-02-28 2013-12-24 Medtronic Minimed, Inc. Systems and methods for initializing a voltage bus and medical devices incorporating same
US9101305B2 (en) 2011-03-09 2015-08-11 Medtronic Minimed, Inc. Glucose sensor product and related manufacturing and packaging methods
US8564447B2 (en) 2011-03-18 2013-10-22 Medtronic Minimed, Inc. Battery life indication techniques for an electronic device
US9018893B2 (en) 2011-03-18 2015-04-28 Medtronic Minimed, Inc. Power control techniques for an electronic device
EP2769357B1 (en) 2011-10-21 2023-08-30 ICU Medical, Inc. Medical device update system
US9610401B2 (en) 2012-01-13 2017-04-04 Medtronic Minimed, Inc. Infusion set component with modular fluid channel element
US8603027B2 (en) 2012-03-20 2013-12-10 Medtronic Minimed, Inc. Occlusion detection using pulse-width modulation and medical device incorporating same
US8523803B1 (en) 2012-03-20 2013-09-03 Medtronic Minimed, Inc. Motor health monitoring and medical device incorporating same
US8603026B2 (en) 2012-03-20 2013-12-10 Medtronic Minimed, Inc. Dynamic pulse-width modulation motor control and medical device incorporating same
US20130338630A1 (en) 2012-06-07 2013-12-19 Medtronic Minimed, Inc. Diabetes therapy management system for recommending adjustments to an insulin infusion device
US9333292B2 (en) 2012-06-26 2016-05-10 Medtronic Minimed, Inc. Mechanically actuated fluid infusion device
US8808269B2 (en) 2012-08-21 2014-08-19 Medtronic Minimed, Inc. Reservoir plunger position monitoring and medical device incorporating same
US10130767B2 (en) 2012-08-30 2018-11-20 Medtronic Minimed, Inc. Sensor model supervisor for a closed-loop insulin infusion system
US9623179B2 (en) 2012-08-30 2017-04-18 Medtronic Minimed, Inc. Safeguarding techniques for a closed-loop insulin infusion system
US9662445B2 (en) 2012-08-30 2017-05-30 Medtronic Minimed, Inc. Regulating entry into a closed-loop operating mode of an insulin infusion system
US9849239B2 (en) 2012-08-30 2017-12-26 Medtronic Minimed, Inc. Generation and application of an insulin limit for a closed-loop operating mode of an insulin infusion system
US20140066884A1 (en) 2012-08-30 2014-03-06 Medtronic Minimed, Inc. Sensor model supervisor for a closed-loop insulin infusion system
US10496797B2 (en) 2012-08-30 2019-12-03 Medtronic Minimed, Inc. Blood glucose validation for a closed-loop operating mode of an insulin infusion system
US9878096B2 (en) 2012-08-30 2018-01-30 Medtronic Minimed, Inc. Generation of target glucose values for a closed-loop operating mode of an insulin infusion system
US8870818B2 (en) 2012-11-15 2014-10-28 Medtronic Minimed, Inc. Systems and methods for alignment and detection of a consumable component
US9033924B2 (en) 2013-01-18 2015-05-19 Medtronic Minimed, Inc. Systems for fluid reservoir retention
US9522223B2 (en) 2013-01-18 2016-12-20 Medtronic Minimed, Inc. Systems for fluid reservoir retention
US9107994B2 (en) 2013-01-18 2015-08-18 Medtronic Minimed, Inc. Systems for fluid reservoir retention
WO2014116832A1 (en) 2013-01-28 2014-07-31 Smiths Medical Asd, Inc. Medication safety devices and methods
US9308321B2 (en) 2013-02-18 2016-04-12 Medtronic Minimed, Inc. Infusion device having gear assembly initialization
EP2964079B1 (en) 2013-03-06 2022-02-16 ICU Medical, Inc. Medical device communication method
US8920381B2 (en) 2013-04-12 2014-12-30 Medtronic Minimed, Inc. Infusion set with improved bore configuration
US9433731B2 (en) 2013-07-19 2016-09-06 Medtronic Minimed, Inc. Detecting unintentional motor motion and infusion device incorporating same
US9402949B2 (en) 2013-08-13 2016-08-02 Medtronic Minimed, Inc. Detecting conditions associated with medical device operations using matched filters
US9880528B2 (en) 2013-08-21 2018-01-30 Medtronic Minimed, Inc. Medical devices and related updating methods and systems
US9889257B2 (en) 2013-08-21 2018-02-13 Medtronic Minimed, Inc. Systems and methods for updating medical devices
US9259528B2 (en) 2013-08-22 2016-02-16 Medtronic Minimed, Inc. Fluid infusion device with safety coupling
JP6621748B2 (en) 2013-08-30 2019-12-18 アイシーユー・メディカル・インコーポレーテッド System and method for monitoring and managing a remote infusion regimen
US9662436B2 (en) 2013-09-20 2017-05-30 Icu Medical, Inc. Fail-safe drug infusion therapy system
US10311972B2 (en) 2013-11-11 2019-06-04 Icu Medical, Inc. Medical device system performance index
EP3071253B1 (en) 2013-11-19 2019-05-22 ICU Medical, Inc. Infusion pump automation system and method
US9750878B2 (en) 2013-12-11 2017-09-05 Medtronic Minimed, Inc. Closed-loop control of glucose according to a predicted blood glucose trajectory
US9750877B2 (en) 2013-12-11 2017-09-05 Medtronic Minimed, Inc. Predicted time to assess and/or control a glycemic state
US9849240B2 (en) 2013-12-12 2017-12-26 Medtronic Minimed, Inc. Data modification for predictive operations and devices incorporating same
US10105488B2 (en) 2013-12-12 2018-10-23 Medtronic Minimed, Inc. Predictive infusion device operations and related methods and systems
US9694132B2 (en) 2013-12-19 2017-07-04 Medtronic Minimed, Inc. Insertion device for insertion set
US9399096B2 (en) 2014-02-06 2016-07-26 Medtronic Minimed, Inc. Automatic closed-loop control adjustments and infusion systems incorporating same
US9861748B2 (en) 2014-02-06 2018-01-09 Medtronic Minimed, Inc. User-configurable closed-loop notifications and infusion systems incorporating same
US9610402B2 (en) 2014-03-24 2017-04-04 Medtronic Minimed, Inc. Transcutaneous conduit insertion mechanism with a living hinge for use with a fluid infusion patch pump device
US10001450B2 (en) 2014-04-18 2018-06-19 Medtronic Minimed, Inc. Nonlinear mapping technique for a physiological characteristic sensor
US10232113B2 (en) 2014-04-24 2019-03-19 Medtronic Minimed, Inc. Infusion devices and related methods and systems for regulating insulin on board
AU2015253001A1 (en) 2014-04-30 2016-10-20 Icu Medical, Inc. Patient care system with conditional alarm forwarding
US9681828B2 (en) 2014-05-01 2017-06-20 Medtronic Minimed, Inc. Physiological characteristic sensors and methods for forming such sensors
US10275572B2 (en) 2014-05-01 2019-04-30 Medtronic Minimed, Inc. Detecting blockage of a reservoir cavity during a seating operation of a fluid infusion device
US10007765B2 (en) 2014-05-19 2018-06-26 Medtronic Minimed, Inc. Adaptive signal processing for infusion devices and related methods and systems
US10274349B2 (en) 2014-05-19 2019-04-30 Medtronic Minimed, Inc. Calibration factor adjustments for infusion devices and related methods and systems
US10152049B2 (en) 2014-05-19 2018-12-11 Medtronic Minimed, Inc. Glucose sensor health monitoring and related methods and systems
US9724470B2 (en) 2014-06-16 2017-08-08 Icu Medical, Inc. System for monitoring and delivering medication to a patient and method of using the same to minimize the risks associated with automated therapy
US9539383B2 (en) 2014-09-15 2017-01-10 Hospira, Inc. System and method that matches delayed infusion auto-programs with manually entered infusion programs and analyzes differences therein
US9839753B2 (en) 2014-09-26 2017-12-12 Medtronic Minimed, Inc. Systems for managing reservoir chamber pressure
US9833563B2 (en) 2014-09-26 2017-12-05 Medtronic Minimed, Inc. Systems for managing reservoir chamber pressure
US10279126B2 (en) 2014-10-07 2019-05-07 Medtronic Minimed, Inc. Fluid conduit assembly with gas trapping filter in the fluid flow path
US9833564B2 (en) 2014-11-25 2017-12-05 Medtronic Minimed, Inc. Fluid conduit assembly with air venting features
US10195341B2 (en) 2014-11-26 2019-02-05 Medtronic Minimed, Inc. Systems and methods for fluid infusion device with automatic reservoir fill
US9987420B2 (en) 2014-11-26 2018-06-05 Medtronic Minimed, Inc. Systems and methods for fluid infusion device with automatic reservoir fill
US9943645B2 (en) 2014-12-04 2018-04-17 Medtronic Minimed, Inc. Methods for operating mode transitions and related infusion devices and systems
US9636453B2 (en) 2014-12-04 2017-05-02 Medtronic Minimed, Inc. Advance diagnosis of infusion device operating mode viability
US9937292B2 (en) 2014-12-09 2018-04-10 Medtronic Minimed, Inc. Systems for filling a fluid infusion device reservoir
US10307535B2 (en) 2014-12-19 2019-06-04 Medtronic Minimed, Inc. Infusion devices and related methods and systems for preemptive alerting
US10265031B2 (en) 2014-12-19 2019-04-23 Medtronic Minimed, Inc. Infusion devices and related methods and systems for automatic alert clearing
US10307528B2 (en) 2015-03-09 2019-06-04 Medtronic Minimed, Inc. Extensible infusion devices and related methods
US10449298B2 (en) 2015-03-26 2019-10-22 Medtronic Minimed, Inc. Fluid injection devices and related methods
US10137243B2 (en) 2015-05-26 2018-11-27 Medtronic Minimed, Inc. Infusion devices with distributed motor control and related operating methods
EP3304370B1 (en) 2015-05-26 2020-12-30 ICU Medical, Inc. Infusion pump system and method with multiple drug library editor source capability
US9999721B2 (en) 2015-05-26 2018-06-19 Medtronic Minimed, Inc. Error handling in infusion devices with distributed motor control and related operating methods
US10575767B2 (en) 2015-05-29 2020-03-03 Medtronic Minimed, Inc. Method for monitoring an analyte, analyte sensor and analyte monitoring apparatus
US9879668B2 (en) 2015-06-22 2018-01-30 Medtronic Minimed, Inc. Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and an optical sensor
US9987425B2 (en) 2015-06-22 2018-06-05 Medtronic Minimed, Inc. Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and sensor contact elements
US9878095B2 (en) 2015-06-22 2018-01-30 Medtronic Minimed, Inc. Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and multiple sensor contact elements
US9993594B2 (en) 2015-06-22 2018-06-12 Medtronic Minimed, Inc. Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and rotor position sensors
US10010668B2 (en) 2015-06-22 2018-07-03 Medtronic Minimed, Inc. Occlusion detection techniques for a fluid infusion device having a rotary pump mechanism and a force sensor
US10463297B2 (en) 2015-08-21 2019-11-05 Medtronic Minimed, Inc. Personalized event detection methods and related devices and systems
US20170053552A1 (en) 2015-08-21 2017-02-23 Medtronic Minimed, Inc. Management and prioritization of the delivery of glycemic insight messages
US10293108B2 (en) 2015-08-21 2019-05-21 Medtronic Minimed, Inc. Infusion devices and related patient ratio adjustment methods
US10478557B2 (en) 2015-08-21 2019-11-19 Medtronic Minimed, Inc. Personalized parameter modeling methods and related devices and systems
US10201657B2 (en) 2015-08-21 2019-02-12 Medtronic Minimed, Inc. Methods for providing sensor site rotation feedback and related infusion devices and systems
US10117992B2 (en) 2015-09-29 2018-11-06 Medtronic Minimed, Inc. Infusion devices and related rescue detection methods
US11666702B2 (en) 2015-10-19 2023-06-06 Medtronic Minimed, Inc. Medical devices and related event pattern treatment recommendation methods
US11501867B2 (en) 2015-10-19 2022-11-15 Medtronic Minimed, Inc. Medical devices and related event pattern presentation methods
US10146911B2 (en) 2015-10-23 2018-12-04 Medtronic Minimed, Inc. Medical devices and related methods and systems for data transfer
US10037722B2 (en) 2015-11-03 2018-07-31 Medtronic Minimed, Inc. Detecting breakage in a display element
US10449306B2 (en) 2015-11-25 2019-10-22 Medtronics Minimed, Inc. Systems for fluid delivery with wicking membrane
US10589038B2 (en) 2016-04-27 2020-03-17 Medtronic Minimed, Inc. Set connector systems for venting a fluid reservoir
EP3484541A4 (en) 2016-07-14 2020-03-25 ICU Medical, Inc. Multi-communication path selection and security system for a medical device
US11097051B2 (en) 2016-11-04 2021-08-24 Medtronic Minimed, Inc. Methods and apparatus for detecting and reacting to insufficient hypoglycemia response
US10238030B2 (en) 2016-12-06 2019-03-26 Medtronic Minimed, Inc. Wireless medical device with a complementary split ring resonator arrangement for suppression of electromagnetic interference
US10272201B2 (en) 2016-12-22 2019-04-30 Medtronic Minimed, Inc. Insertion site monitoring methods and related infusion devices and systems
US10500135B2 (en) 2017-01-30 2019-12-10 Medtronic Minimed, Inc. Fluid reservoir and systems for filling a fluid reservoir of a fluid infusion device
US10532165B2 (en) 2017-01-30 2020-01-14 Medtronic Minimed, Inc. Fluid reservoir and systems for filling a fluid reservoir of a fluid infusion device
US10363365B2 (en) 2017-02-07 2019-07-30 Medtronic Minimed, Inc. Infusion devices and related consumable calibration methods
US10552580B2 (en) 2017-02-07 2020-02-04 Medtronic Minimed, Inc. Infusion system consumables and related calibration methods
US11207463B2 (en) 2017-02-21 2021-12-28 Medtronic Minimed, Inc. Apparatuses, systems, and methods for identifying an infusate in a reservoir of an infusion device
US10646649B2 (en) 2017-02-21 2020-05-12 Medtronic Minimed, Inc. Infusion devices and fluid identification apparatuses and methods
US10861592B2 (en) 2018-07-17 2020-12-08 Icu Medical, Inc. Reducing infusion pump network congestion by staggering updates
EP3824383B1 (en) 2018-07-17 2023-10-11 ICU Medical, Inc. Systems and methods for facilitating clinical messaging in a network environment
WO2020018388A1 (en) 2018-07-17 2020-01-23 Icu Medical, Inc. Updating infusion pump drug libraries and operational software in a networked environment
US11152108B2 (en) 2018-07-17 2021-10-19 Icu Medical, Inc. Passing authentication token to authorize access to rest calls via web sockets
US10692595B2 (en) 2018-07-26 2020-06-23 Icu Medical, Inc. Drug library dynamic version management
EP3827337A4 (en) 2018-07-26 2022-04-13 ICU Medical, Inc. Drug library management system

Family Cites Families (67)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5338157B1 (en) 1992-09-09 1999-11-02 Sims Deltec Inc Systems and methods for communicating with ambulat
US3768014A (en) * 1972-01-28 1973-10-23 Gen Electric Cardiac pacemaker rate/interval computer system
US3872252A (en) 1973-03-07 1975-03-18 Esb Inc Apparatus for monitoring electrical signals, either artificial and/or natural in a living body, via a communication link
US4068096A (en) 1976-06-16 1978-01-10 Continental Il National Bank And Trust Co. Pressure monitoring system
US4102332A (en) * 1977-05-17 1978-07-25 Gessman Lawrence J Remote, telephonic cardiac resuscitation device
US4207959A (en) 1978-06-02 1980-06-17 New York University Wheelchair mounted control apparatus
US4731051A (en) 1979-04-27 1988-03-15 The Johns Hopkins University Programmable control means for providing safe and controlled medication infusion
US4692147A (en) 1980-04-02 1987-09-08 Medtronic, Inc. Drug administration device
EP0108052A4 (en) * 1982-04-23 1985-09-26 Survival Technology Ambulatory monitoring system with real time analysis and telephone transmission.
US4447224A (en) 1982-09-20 1984-05-08 Infusaid Corporation Variable flow implantable infusion apparatus
US5100380A (en) 1984-02-08 1992-03-31 Abbott Laboratories Remotely programmable infusion system
CA1254091A (en) 1984-09-28 1989-05-16 Vladimir Feingold Implantable medication infusion system
US4695954A (en) 1984-10-31 1987-09-22 Rose Robert J Modular medication dispensing system and apparatus utilizing portable memory device
US4676776A (en) 1985-01-18 1987-06-30 Intelligent Medicine, Inc. Device and method for effecting application of a therapeutic agent
US4810243A (en) 1985-01-18 1989-03-07 Intelligent Medicine, Inc. Device and method for effecting application of a therapeutic agent
US5088981A (en) 1985-01-18 1992-02-18 Howson David C Safety enhanced device and method for effecting application of a therapeutic agent
US4782511A (en) 1986-07-11 1988-11-01 Murex Corporation Interactive medical laboratory specimen apparatus system
EP0290683A3 (en) 1987-05-01 1988-12-14 Diva Medical Systems B.V. Diabetes management system and apparatus
US5211626A (en) 1987-05-01 1993-05-18 Product Innovation Holdings Ltd. Medical infusion apparatus
US4845773A (en) * 1987-09-08 1989-07-04 Arnaldo Attallah Method and a system for remotely switching an electrically operated device by the use of signals generated by a telephone
US5007429A (en) 1987-09-21 1991-04-16 Pulsetrend, Inc. Interface using 12-digit keypad for programming parameters in ambulatory blood pressure monitor
US4828887A (en) * 1987-11-23 1989-05-09 General Electric Company Method and apparatus for applying material to selected areas of a moving part
US4941172A (en) 1987-11-24 1990-07-10 U.S. News Preprogrammed autodialer and related process
US4838887A (en) 1987-12-15 1989-06-13 Shiley Infusaid Inc. Programmable valve pump
US5369699A (en) 1988-08-29 1994-11-29 Bi Incorporated Adaptable personnel supervisory system with automatic fee collection
EP0404932A4 (en) 1989-01-13 1993-01-27 The Scott Fetzer Company Apparatus and method for controlling and monitoring the exercise session for remotely located patients
US5276611A (en) 1989-05-25 1994-01-04 Andrea Ghiraldi Management of parameters relating to a dialysis treatment
US5165874A (en) 1990-05-04 1992-11-24 Block Medical, Inc. Disposable infusion apparatus and peristaltic pump for use therewith
US5078683A (en) 1990-05-04 1992-01-07 Block Medical, Inc. Programmable infusion system
US5226086A (en) 1990-05-18 1993-07-06 Minnesota Mining And Manufacturing Company Method, apparatus, system and interface unit for programming a hearing aid
US5321618A (en) 1990-05-29 1994-06-14 Lawrence Gessman Apparatus and method for remotely monitoring implanted cardioverter defibrillators
JP2921936B2 (en) 1990-07-13 1999-07-19 株式会社東芝 Image monitoring device
US5594786A (en) 1990-07-27 1997-01-14 Executone Information Systems, Inc. Patient care and communication system
US5119412A (en) * 1990-08-06 1992-06-02 Arnaldo Attallah Method and a system for remotely switching and/or regulating and monitoring and electrically operated device or an environment by the use of signals generated by a telephone or a modem
US5321619A (en) 1990-09-17 1994-06-14 Honda Giken Kogyo Kabushiki Kaisha Production control method and system therefor
US5228449A (en) 1991-01-22 1993-07-20 Athanasios G. Christ System and method for detecting out-of-hospital cardiac emergencies and summoning emergency assistance
US5311449A (en) 1991-03-25 1994-05-10 Angeion Corporation Sterilizable hand-held programmer/interrogator
US5666404A (en) 1991-07-31 1997-09-09 Manfred Asrican Device for telephone monitoring of patients having peripheral arterial occlusive disease
US5335313A (en) 1991-12-03 1994-08-02 Douglas Terry L Voice-actuated, speaker-dependent control system for hospital bed
US5581369A (en) * 1992-09-25 1996-12-03 Ralin, Inc. Apparatus and method for communicating electrocardiographic data to a facsimile machine
US5375604A (en) 1992-12-11 1994-12-27 Siemens Medical Electronics, Inc. Transportable modular patient monitor
SE9300281D0 (en) * 1993-01-29 1993-01-29 Siemens Elema Ab IMPLANTABLE MEDICAL DEVICE AND EXTRACORPORAL PROGRAMMING AND MONITORING DEVICE
US5416695A (en) 1993-03-09 1995-05-16 Metriplex, Inc. Method and apparatus for alerting patients and medical personnel of emergency medical situations
US5576952A (en) 1993-03-09 1996-11-19 Metriplex, Inc. Medical alert distribution system with selective filtering of medical information
US5394445A (en) 1993-06-25 1995-02-28 Ball; Randel H. Telephone call screening and answering device
WO1995002426A1 (en) 1993-07-13 1995-01-26 Sims Deltec, Inc. Medical pump and method of programming
US5579378A (en) 1993-08-25 1996-11-26 Arlinghaus, Jr.; Frank H. Medical monitoring system
WO1995006938A1 (en) 1993-09-03 1995-03-09 Compuspeak Laboratories, Inc. System for host computer control of remote voice interface
US5550902A (en) 1994-08-17 1996-08-27 American Telecare, Inc. Remote stethoscope signal processing system
US5633910A (en) 1994-09-13 1997-05-27 Cohen; Kopel H. Outpatient monitoring system
US5626630A (en) * 1994-10-13 1997-05-06 Ael Industries, Inc. Medical telemetry system using an implanted passive transponder
US5579001A (en) 1994-10-20 1996-11-26 Hewlett-Packard Co. Paging-based backchannel in a medical telemetry system
US5827180A (en) 1994-11-07 1998-10-27 Lifemasters Supported Selfcare Method and apparatus for a personal health network
US5919141A (en) 1994-11-15 1999-07-06 Life Sensing Instrument Company, Inc. Vital sign remote monitoring device
US5573506A (en) * 1994-11-25 1996-11-12 Block Medical, Inc. Remotely programmable infusion system
US6355018B1 (en) * 1995-11-25 2002-03-12 I-Flow Corporation Inc. Remotely programmable infusion system
US6749586B2 (en) * 1994-11-25 2004-06-15 I-Flow Corporation Remotely programmable infusion system
US5805676A (en) 1995-05-19 1998-09-08 Pcpi Phone, Inc. Telephone/transaction entry device and system for entering transaction data into databases
US5704364A (en) 1995-11-08 1998-01-06 Instromedix, Inc. Concurrent medical patient data and voice communication method and apparatus
US5748103A (en) 1995-11-13 1998-05-05 Vitalcom, Inc. Two-way TDMA telemetry system with power conservation features
US5936539A (en) 1996-03-19 1999-08-10 Siemens Medical Systems, Inc. Method and apparatus for automatic configuration of a network node
US5895371A (en) 1996-08-27 1999-04-20 Sabratek Corporation Medical treatment apparatus and method
US5855550A (en) 1996-11-13 1999-01-05 Lai; Joseph Method and system for remotely monitoring multiple medical parameters
US5902234A (en) 1997-04-10 1999-05-11 Webb; Nicholas J. Medical communication system for ambulatory home-care patients
US6014432A (en) 1998-05-19 2000-01-11 Eastman Kodak Company Home health care system
US6263245B1 (en) 1999-08-12 2001-07-17 Pacesetter, Inc. System and method for portable implantable device interogation
US6473638B2 (en) 1999-12-24 2002-10-29 Medtronic, Inc. Medical device GUI for cardiac electrophysiology display and data communication

Cited By (96)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8034026B2 (en) 2001-05-18 2011-10-11 Deka Products Limited Partnership Infusion pump assembly
US9173996B2 (en) 2001-05-18 2015-11-03 Deka Products Limited Partnership Infusion set for a fluid pump
US7993109B2 (en) 2002-10-09 2011-08-09 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8047811B2 (en) 2002-10-09 2011-11-01 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8047812B2 (en) 2002-10-09 2011-11-01 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8029245B2 (en) 2002-10-09 2011-10-04 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8029250B2 (en) 2002-10-09 2011-10-04 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US7993108B2 (en) 2002-10-09 2011-08-09 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US8343093B2 (en) 2002-10-09 2013-01-01 Abbott Diabetes Care Inc. Fluid delivery device with autocalibration
US7922458B2 (en) 2002-10-09 2011-04-12 Abbott Diabetes Care Inc. Variable volume, shape memory actuated insulin dispensing pump
US7679407B2 (en) 2003-04-28 2010-03-16 Abbott Diabetes Care Inc. Method and apparatus for providing peak detection circuitry for data communication systems
US8512246B2 (en) 2003-04-28 2013-08-20 Abbott Diabetes Care Inc. Method and apparatus for providing peak detection circuitry for data communication systems
US8052617B2 (en) * 2004-08-09 2011-11-08 Phlebotics, Inc. Portable sampling or testing device and method for pharmacokinetics and physiology studies
WO2006033715A3 (en) * 2004-08-09 2008-11-13 Bioanalytical Systems Inc Portable sampling or testing device and method for pharmacokinetics and physiology studies
US20060102091A1 (en) * 2004-08-09 2006-05-18 Bioanalytical Systems, Inc. (An Indiana Corporation) Portable sampling or testing device and method for pharmacokinetics and physiology studies
US20060247606A1 (en) * 2005-03-09 2006-11-02 Batch Richard M System and method for controlling access to features of a medical instrument
WO2006098927A1 (en) * 2005-03-09 2006-09-21 Cardinal Health 303, Inc. System and method for controlling access to features of a medical instrument
US8343092B2 (en) 2005-03-21 2013-01-01 Abbott Diabetes Care Inc. Method and system for providing integrated medication infusion and analyte monitoring system
US8029460B2 (en) 2005-03-21 2011-10-04 Abbott Diabetes Care Inc. Method and system for providing integrated medication infusion and analyte monitoring system
US8029459B2 (en) 2005-03-21 2011-10-04 Abbott Diabetes Care Inc. Method and system for providing integrated medication infusion and analyte monitoring system
US7884729B2 (en) 2005-05-17 2011-02-08 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US9750440B2 (en) 2005-05-17 2017-09-05 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US8089363B2 (en) 2005-05-17 2012-01-03 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US9332944B2 (en) 2005-05-17 2016-05-10 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US10206611B2 (en) 2005-05-17 2019-02-19 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US8653977B2 (en) 2005-05-17 2014-02-18 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US8471714B2 (en) 2005-05-17 2013-06-25 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US7768408B2 (en) 2005-05-17 2010-08-03 Abbott Diabetes Care Inc. Method and system for providing data management in data monitoring system
US8112138B2 (en) 2005-06-03 2012-02-07 Abbott Diabetes Care Inc. Method and apparatus for providing rechargeable power in data monitoring and management systems
US7756561B2 (en) 2005-09-30 2010-07-13 Abbott Diabetes Care Inc. Method and apparatus for providing rechargeable power in data monitoring and management systems
US8638220B2 (en) 2005-10-31 2014-01-28 Abbott Diabetes Care Inc. Method and apparatus for providing data communication in data monitoring and management systems
US20140338663A1 (en) * 2006-01-03 2014-11-20 Shahzad Saad Pirzada System, device and process for remotely controlling a medical device
US8344966B2 (en) 2006-01-31 2013-01-01 Abbott Diabetes Care Inc. Method and system for providing a fault tolerant display unit in an electronic device
US11491273B2 (en) 2006-02-09 2022-11-08 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11559625B2 (en) 2006-02-09 2023-01-24 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11904134B2 (en) 2006-02-09 2024-02-20 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11890448B2 (en) 2006-02-09 2024-02-06 Deka Products Limited Partnership Method and system for shape-memory alloy wire control
US8414522B2 (en) 2006-02-09 2013-04-09 Deka Products Limited Partnership Fluid delivery systems and methods
US8545445B2 (en) 2006-02-09 2013-10-01 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11844926B2 (en) 2006-02-09 2023-12-19 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11786651B2 (en) 2006-02-09 2023-10-17 Deka Products Limited Partnership Patch-sized fluid delivery system
US8585377B2 (en) 2006-02-09 2013-11-19 Deka Products Limited Partnership Pumping fluid delivery systems and methods using force application assembly
US11738139B2 (en) 2006-02-09 2023-08-29 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11717609B2 (en) 2006-02-09 2023-08-08 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11712513B2 (en) 2006-02-09 2023-08-01 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11690952B2 (en) 2006-02-09 2023-07-04 Deka Products Limited Partnership Pumping fluid delivery systems and methods using force application assembly
US11617826B2 (en) 2006-02-09 2023-04-04 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11534543B2 (en) 2006-02-09 2022-12-27 Deka Products Limited Partnership Method for making patch-sized fluid delivery systems
US11497846B2 (en) 2006-02-09 2022-11-15 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11478623B2 (en) 2006-02-09 2022-10-25 Deka Products Limited Partnership Infusion pump assembly
US11426512B2 (en) 2006-02-09 2022-08-30 Deka Products Limited Partnership Apparatus, systems and methods for an infusion pump assembly
US8113244B2 (en) 2006-02-09 2012-02-14 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11413391B2 (en) 2006-02-09 2022-08-16 Deka Products Limited Partnership Patch-sized fluid delivery systems and methods
US11406753B2 (en) 2006-02-09 2022-08-09 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11408414B2 (en) 2006-02-09 2022-08-09 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11395877B2 (en) 2006-02-09 2022-07-26 Deka Products Limited Partnership Systems and methods for fluid delivery
US11391273B2 (en) 2006-02-09 2022-07-19 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US11364335B2 (en) 2006-02-09 2022-06-21 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11339774B2 (en) 2006-02-09 2022-05-24 Deka Products Limited Partnership Adhesive and peripheral systems and methods for medical devices
US10007759B2 (en) 2006-10-31 2018-06-26 Abbott Diabetes Care Inc. Infusion devices and methods
WO2008055037A3 (en) * 2006-10-31 2008-07-03 Abbott Diabetes Care Inc Infusion devices and methods
US11508476B2 (en) 2006-10-31 2022-11-22 Abbott Diabetes Care, Inc. Infusion devices and methods
US11043300B2 (en) 2006-10-31 2021-06-22 Abbott Diabetes Care Inc. Infusion devices and methods
US11837358B2 (en) 2006-10-31 2023-12-05 Abbott Diabetes Care Inc. Infusion devices and methods
US9064107B2 (en) 2006-10-31 2015-06-23 Abbott Diabetes Care Inc. Infusion devices and methods
US8579853B2 (en) 2006-10-31 2013-11-12 Abbott Diabetes Care Inc. Infusion devices and methods
US8496646B2 (en) 2007-02-09 2013-07-30 Deka Products Limited Partnership Infusion pump assembly
US11404776B2 (en) 2007-12-31 2022-08-02 Deka Products Limited Partnership Split ring resonator antenna adapted for use in wirelessly controlled medical device
US11894609B2 (en) 2007-12-31 2024-02-06 Deka Products Limited Partnership Split ring resonator antenna adapted for use in wirelessly controlled medical device
US11723841B2 (en) 2007-12-31 2023-08-15 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US9526830B2 (en) 2007-12-31 2016-12-27 Deka Products Limited Partnership Wearable pump assembly
US8491570B2 (en) 2007-12-31 2013-07-23 Deka Products Limited Partnership Infusion pump assembly
US11701300B2 (en) 2007-12-31 2023-07-18 Deka Products Limited Partnership Method for fluid delivery
US11497686B2 (en) 2007-12-31 2022-11-15 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11534542B2 (en) 2007-12-31 2022-12-27 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11642283B2 (en) 2007-12-31 2023-05-09 Deka Products Limited Partnership Method for fluid delivery
US8414563B2 (en) 2007-12-31 2013-04-09 Deka Products Limited Partnership Pump assembly with switch
US10272190B2 (en) * 2008-07-09 2019-04-30 Baxter International Inc. Renal therapy system including a blood pressure monitor
US8708376B2 (en) 2008-10-10 2014-04-29 Deka Products Limited Partnership Medium connector
US8267892B2 (en) 2008-10-10 2012-09-18 Deka Products Limited Partnership Multi-language / multi-processor infusion pump assembly
US8262616B2 (en) 2008-10-10 2012-09-11 Deka Products Limited Partnership Infusion pump assembly
US8016789B2 (en) 2008-10-10 2011-09-13 Deka Products Limited Partnership Pump assembly with a removable cover assembly
US8066672B2 (en) 2008-10-10 2011-11-29 Deka Products Limited Partnership Infusion pump assembly with a backup power supply
US8223028B2 (en) 2008-10-10 2012-07-17 Deka Products Limited Partnership Occlusion detection system and method
US9180245B2 (en) 2008-10-10 2015-11-10 Deka Products Limited Partnership System and method for administering an infusible fluid
US8560082B2 (en) 2009-01-30 2013-10-15 Abbott Diabetes Care Inc. Computerized determination of insulin pump therapy parameters using real time and retrospective data processing
US8467972B2 (en) 2009-04-28 2013-06-18 Abbott Diabetes Care Inc. Closed loop blood glucose control algorithm analysis
US10872102B2 (en) 2009-07-23 2020-12-22 Abbott Diabetes Care Inc. Real time management of data relating to physiological control of glucose levels
US8798934B2 (en) 2009-07-23 2014-08-05 Abbott Diabetes Care Inc. Real time management of data relating to physiological control of glucose levels
US11524151B2 (en) 2012-03-07 2022-12-13 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US9204833B2 (en) 2012-03-27 2015-12-08 Phlebotics, Inc. Cartridge for automated blood sampling system
US11597541B2 (en) 2013-07-03 2023-03-07 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
US11523972B2 (en) 2018-04-24 2022-12-13 Deka Products Limited Partnership Apparatus, system and method for fluid delivery
WO2021059210A1 (en) 2019-09-25 2021-04-01 Janssen Pharmaceuticals, Inc. Interconnection of drug administration systems
WO2022079513A1 (en) 2020-05-06 2022-04-21 Janssen Pharmaceuticals, Inc. Patient monitoring using drug administration devices
WO2022079514A1 (en) 2020-05-06 2022-04-21 Janssen Pharmaceuticals, Inc. Monitoring and communicating information using drug administration devices

Also Published As

Publication number Publication date
US7153289B2 (en) 2006-12-26
US20050027254A1 (en) 2005-02-03
US6749586B2 (en) 2004-06-15
US20070100394A1 (en) 2007-05-03

Similar Documents

Publication Publication Date Title
US7153289B2 (en) Remotely programmable infusion system
US6228057B1 (en) Remotely programmable infusion system
WO1996016685A9 (en) Remotely programmable infusion system
US7778852B2 (en) Method and apparatus for monitoring a patient
EP1036464B1 (en) Method and apparatus for monitoring a patient
US6024539A (en) Systems and methods for communicating with ambulatory medical devices such as drug delivery devices
US6355018B1 (en) Remotely programmable infusion system
US8190452B2 (en) Method and apparatus for monitoring a patient
AU2001279028B2 (en) Method and apparatus for monitoring a patient
AU2001279028A1 (en) Method and apparatus for monitoring a patient
ES2350390T3 (en) METHOD AND APPLIANCE FOR MONITORING A PATIENT.
AU714459B2 (en) Systems and methods for communicating with ambulatory medical devices such as drug delivery devices

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: KIMBERLY-CLARK WORLDWIDE, INC., WISCONSIN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:I-FLOW CORPORATION;REEL/FRAME:027308/0732

Effective date: 20110124

FPAY Fee payment

Year of fee payment: 8

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20160615