Patent Grant
9517304
Embodiments of the disclosed subject matter relate generally to medical devices and medical device networks, such as infusion systems that deliver fluids into a patient's body. More particularly, embodiments of the subject matter relate to techniques and methods for managing control commands in a medical device system having a plurality of controller devices for one remotely controlled medical device.
Portable medical devices having wireless data communication capabilities are becoming increasingly popular, especially for patients that have conditions that must be monitored on a continuous or frequent basis. For example, diabetics are usually required to modify and monitor their daily lifestyle to keep their body in balance, in particular, their blood glucose (BG) levels. Individuals with Type 1 diabetes and some individuals with Type 2 diabetes use insulin to control their BG levels. To do so, diabetics routinely keep strict schedules, including ingesting timely nutritious meals, partaking in exercise, monitoring BG levels daily, and adjusting and administering insulin dosages accordingly. Diabetics may utilize wireless medical devices that are deployed in a network environment in a manner that facilitates data communication between two or more separate devices.
The prior art includes a number of insulin pump systems that are designed to deliver accurate and measured doses of insulin via infusion sets (an infusion set delivers the insulin through a small diameter tube that terminates at a cannula inserted under the patient's skin). In lieu of a syringe, the patient can simply activate the insulin pump to administer an insulin bolus as needed, for example, in response to the patient's current BG level. A patient can measure his BG level using a BG measurement device, such as a test strip meter, a continuous glucose measurement system, or the like. BG measurement devices use various methods to measure the BG level of a patient, such as a sample of the patient's blood, a sensor in contact with a bodily fluid, an optical sensor, an enzymatic sensor, or a fluorescent sensor. When the BG measurement device has generated a BG measurement, the measurement is displayed on the BG measurement device. A continuous glucose monitoring system can monitor the patient's BG level in real time.
Insulin pumps and other portable medical devices may also be configured to communicate with remote controller devices, monitoring or display devices, BG meters, and other devices associated with such an infusion system. It may be desirable to use multiple wireless controller devices to remotely control one medical device, such as an infusion pump. For example, a patient having a wearable or otherwise portable infusion device may have one or more controller devices at home, another controller device at the office, and yet another controller device in a vehicle. Moreover, it may be desirable to enable different people to remotely control a single infusion device. Thus, the patient may have one wireless controller, and a caregiver (such as a parent) may have another wireless controller, both having independent control capabilities. Furthermore, a patient may use two different remotely controllable medical devices, which may be wirelessly controlled by one or more wireless controllers.
The communication, processing, and execution of remote control commands is somewhat straightforward in a basic medical device system having only one medical device and only one corresponding wireless controller device. As more compatible devices are introduced, however, conflicting or redundant instructions and commands might be issued concurrently (or very close in time) by different controller devices. Conflicting or duplicative commands may be tolerable or troublesome, depending upon the functions or features associated with those commands. Consequently, it becomes increasingly important to manage, regulate, and coordinate the manner in which control commands are handled and processed in a medical device system having a plurality of controller devices for one medical device.
A personal infusion system, such as an insulin infusion system that is worn or carried by a patient, might utilize consumable, refillable, or replaceable parts, components, or items. For example, an insulin infusion pump may cooperate with replaceable or replenishable items such as a continuous glucose sensor, an infusion set, and an insulin reservoir. Such consumables can usually be obtained from a physician, from the equipment manufacturer, and/or from a pharmacy. Some existing infusion systems include reminder or alert features that notify the user whenever it is time to replace or refill a consumable item.
The prior art includes portable medical devices that utilize display elements, which can be used to display information associated with the operation of the medical devices. For example, the display element of an insulin infusion pump (or a remote controller device for the pump) can be used to display a graph, a chart, or other visual representation of data related to the patient and/or to the operation of the pump. In this regard, the pump might display a graph of the patient's glucose level versus time. Due to the small size of the display element of a portable pump device, the time period displayed at any given moment will be limited (e.g., two hours, four hours, twelve hours). If the visible time scale is changed without altering the vertical scale, the slope characteristics of the graphed data will change accordingly. Thus, a relatively high slope (whether increasing or decreasing) may have more or less significance, depending upon the chosen time scale. Consequently, the user may not fully appreciate the significance of slope trends and variations in the charted data, unless the user is always aware of the selected time scale.
Certain types of portable medical devices may implement security features to ensure that sensitive, private, or important functions are not accidentally activated, and/or to ensure that such functions can only be activated by authorized individuals. For example, an infusion pump or specific functions of the pump may be password protected to ensure that only the patient or an authorized caregiver can administer therapy with the pump. Conventional security measures can be cumbersome, difficult to program, and/or inconvenient for the user. For example, usernames and passwords rely on memorization, which introduces human error. Moreover, usernames and passwords can be compromised if the user discloses them to others or documents them in a manner that can be accessed by unauthorized persons.
A method of coordinating control commands in a medical device system is provided. The medical device system includes a medical device for a patient, and a plurality of wireless controller devices for the medical device, where each of the wireless controller devices is capable of independently issuing control commands for the medical device. The method involves wirelessly broadcasting a lockout message from a first controller device of the plurality of wireless controller devices, the lockout message being formatted to disable at least one function of a second controller device of the plurality of wireless controller devices upon receipt of the lockout message at the second controller device. Thereafter, the method wirelessly transmits a control command from the first controller device, the control command being formatted to control a function of the medical device upon receipt of the control command by the medical device. Thereafter, an unlock message is wirelessly broadcast from the first controller device, the unlock message being formatted to clear the lockout message at the second controller device upon receipt of the unlock message at the second controller device.
Another method of coordinating control commands in a medical device system is also provided. The medical device system includes a medical device for a patient, and a plurality of wireless controller devices for the medical device, each of the wireless controller devices being capable of independently issuing control commands for the medical device. This method involves wirelessly receiving a lockout message at a first controller device of the plurality of wireless controller devices, wherein the lockout message is broadcast by a second controller device of the plurality of wireless controller devices in preparation of issuing a control command for the medical device. The method continues by disabling at least one function of the first controller device upon receipt of the lockout message at the first controller device, resulting in at least one disabled function. Thereafter, an unlock message is wirelessly received at the first controller device, and the at least one disabled function is enabled upon receipt of the unlock message at the first controller device.
Also provided is a method of coordinating control commands in a medical device system having a medical device that delivers therapy to a patient, and a plurality of wireless controller devices for the medical device. This method detects user interaction with the medical device and, after detecting the user interaction, the method wirelessly broadcasts a disable message from the medical device. The disable message conveys instructions intended to at least partially disable control functions of the plurality of wireless controller devices. Thereafter, the method executes a function of the medical device and, after execution of the function, wirelessly broadcasts an enable message from the medical device. The enable message conveys instructions intended to override the effect of the disable message.
Another method of coordinating control commands in a medical device system is also provided. The medical device system includes a medical device that delivers therapy to a patient, and a plurality of wireless controller devices for the medical device. This method begins by wirelessly receiving a disable message at the plurality of wireless controller devices, wherein the disable message is broadcast from the medical device in preparation of executing a control command at the medical device. In response to receiving the disable message, the method at least partially disables control functions of the plurality of wireless controller devices, resulting in at least one disabled function. Thereafter, an enable message is wirelessly received at the plurality of wireless controller devices, and, in response to receiving the enable message, the at least one disabled function of the plurality of wireless controller devices is enabled.
Yet another method of coordinating control commands in a medical device system is provided. The medical device system includes a medical device that delivers therapy to a patient, and a wireless controller device for the medical device. This method involves obtaining a user input at the wireless controller device, the user input corresponding to a request to initiate a command that influences therapy delivered by the medical device. In response to the user input, the method checks a synchronization status between the wireless controller device and the medical device. The method continues by transmitting, to the medical device, a control message for the command only when the checking step confirms that the wireless controller device is synchronized with the medical device.
Another method of coordinating control commands in a medical device system is provided. The medical device system includes a medical device that delivers therapy to a patient, and a plurality of wireless controller devices for the medical device. This method begins by wirelessly receiving a control command that is formatted to control a function of the medical device, the control command originating from an active controller device of the plurality of wireless controller devices. In response to receiving the control command, a disable message is wirelessly broadcast from the medical device, the disable message conveying instructions intended to at least partially disable control functions of the plurality of wireless controller devices. The control command is then processed to execute the function.
Also provided is a method of operating a portable medical device having one or more consumables associated therewith. This method automatically determines, with the portable medical device, when a consumable associated with the portable medical device requires replacement. In response to the automatic determination, the method displays an active link to a vendor of the consumable. In response to selection of the active link, the method initiates an electronic transaction for the consumable, using the portable medical device.
A portable medical device is provided. The medical device includes: a tracking module configured to determine when a replenishable item associated with the portable medical device needs to be replenished; and an e-commerce module operatively coupled to the tracking module, the e-commerce module initiating an order of the replenishable item when the tracking module determines that the replenishable item needs to be replenished.
A method of operating a portable medical device that facilitates treatment of a medical condition of a patient is also provided. This method automatically determines, with the portable medical device, a need to acquire an item associated with operation of the portable medical device, and/or associated with treatment of the medical condition. The method also obtains geographic position data that indicates a location of the portable medical device, and identifies, based upon the geographic position data, a provider of the item, wherein the provider maintains inventory of the item at a facility located within a predetermined distance from the location of the portable medical device. The method also initiates, with the portable medical device, an e-commerce transaction with the provider, the e-commerce transaction including an electronic order for the item.
Another method of controlling operation of a portable medical device having one or more consumables associated therewith is provided. This method involves: receiving status data corresponding to operating status of the portable medical device; determining, based upon analysis of the status data, when a consumable associated with the portable medical device requires replacement or replenishment; in response to the determining step, generating a message that indicates a need to replace or replenish the consumable; and communicating the message to the portable medical device.
Also provided is another method of operating a portable medical device having one or more consumables associated therewith. This method begins by obtaining status data that indicates a remaining quantity, supply, or inventory of a consumable used by the portable medical device. The status data is uploaded to a remote computing device that is physically distinct and separate from the portable medical device. The method receives at least one message that indicates a need to replace or replenish the consumable. The at least one message is initiated by the remote computing device when the status data indicates that the consumable should be replaced or replenished.
A portable medical device is also provided. The medical device includes: a tracking module that obtains status data indicative of a remaining quantity, supply, or inventory of a replenishable product used by the portable medical device; a data communication module operatively coupled to the tracking module, the data communication module being configured to transfer the status data to a remote computing device, and configured to receive a message that indicates a need to replace or refill the replenishable product, the message being initiated by the remote computing device when the status data indicates that the replenishable product should be replaced or refilled; and an e-commerce module configured to initiate a transaction for the replenishable product.
Also provided is a method of controlling operation of a portable medical device that facilitates treatment of a medical condition of a patient. The method receives patient data associated with the medical condition of the patient, and determines, based upon analysis of the patient data, when the medical condition of the patient requires attention. In response to the determination, the method communicates at least one advertisement to the portable medical device, wherein the at least one advertisement is for goods and/or services related to treatment of the medical condition.
Another method of operating a portable medical device is provided. The medical device has one or more consumables associated therewith, and the method involves: automatically determining, with the portable medical device, when a consumable associated with the portable medical device requires replacement or replenishment; and in response to the automatically determining step, presenting an advertisement at the portable medical device, the advertisement identifying a supplier, seller, or vendor of the consumable.
Also provided is a method of operating a portable medical device that facilitates treatment of a medical condition of a patient. This method involves: automatically determining, with the portable medical device, when the medical condition of the patient requires attention; and in response to the automatically determining step, presenting an advertisement at the portable medical device, the advertisement identifying a supplier, seller, or provider of goods and/or services associated with treatment of the medical condition.
A portable medical device that facilitates treatment of a medical condition of a patient is provided. The portable medical device includes: a tracking module configured to determine when the medical condition of the patient requires attention; and an advertisement server module operatively coupled to the tracking module. The advertisement server module is configured to present an advertisement at the portable medical device when the tracking module determines that the medical condition requires attention, wherein the advertisement is contextually related to treatment of the medical condition.
Moreover, a method for presenting information on a display element of a portable medical device is provided. This method involves: rendering, on the display element, a first graphical representation of information associated with operation of the portable medical device; obtaining, at the portable medical device, a user-initiated display panning command; and rendering, on the display element, a second graphical representation of the information. At least a portion of the second graphical representation is not included in the first graphical representation. In addition, rendering of the second graphical representation is performed in response to the user-initiated display panning command.
Also provided is a method of providing an intuitive graphical display of patient data for a medical device having a display element. This method obtains measurement data corresponding to values of a physiological characteristic measured over a period of time, and renders a graphical representation of a portion of the measurement data on the display element, resulting in a display of the values of the physiological characteristic measured during a first interval of the period of time. Thereafter, a user-initiated display panning command is processed. In response to the user-initiated display panning command, the method dynamically pans the graphical representation while updating the portion of the measurement data. Thereafter, the method displays the values of the physiological characteristic measured during a second interval of the period of time.
A medical device is also provided. The medical device includes at least one memory element configured to store physiological characteristic data corresponding to values of a physiological characteristic for a patient. The medical device also includes a graphics engine configured to generate image rendering display commands associated with the physiological characteristic data, and a display element coupled to the graphics engine. The display element is configured to receive the image rendering display commands and, in response thereto, render visual representations of the physiological characteristic data. The medical device also includes a human-machine interface element operatively coupled to the graphics engine, and configured to generate display shifting commands in response to user interaction therewith. The display element renders a visual representation of the physiological characteristic data such that it corresponds to a first time interval. Moreover, in response to a display shifting command generated by the human-machine interface element, the display element updates the visual representation of the physiological characteristic data such that it corresponds to a second time interval.
Another embodiment of a medical device is provided. This medical device includes: a security module configured to regulate operations of the medical device; a fingerprint reader operatively coupled to the security module, the fingerprint reader configured to detect fingerprints, and to generate fingerprint data corresponding to swiped fingerprints; and at least one memory element operatively coupled to the security module, and configured to maintain a list of fingerprint-secured operations of the medical device, each of the fingerprint-secured operations being linked to a respective assigned set of identifiable fingerprint data. The security module is configured to analyze a swiped set of fingerprint data, compare the swiped set of fingerprint data to identifiable fingerprint data maintained in the list, and initiate one of the fingerprint-secured operations when the swiped set of fingerprint data satisfies matching criteria for its respective assigned set of identifiable fingerprint data.
A medical device system is also provided. The system includes a portable therapy delivery device that can be worn or carried by a patient, and a controller configured to remotely control delivery of therapy to the patient via the portable therapy delivery device. The controller includes a security module configured to regulate operations of the controller and/or the portable therapy delivery device, and a fingerprint reader operatively coupled to the security module. The fingerprint reader is configured to read fingerprints, and to generate fingerprint data corresponding to swiped fingerprints. The controller also includes at least one memory element operatively coupled to the security module, and configured to maintain a list of fingerprint-secured operations. Each of the fingerprint-secured operations is linked to a respective assigned set of identifiable fingerprint data. The security module is configured to analyze a swiped set of fingerprint data, compare the swiped set of fingerprint data to identifiable fingerprint data maintained in the list, and initiate one of the fingerprint-secured operations when the swiped set of fingerprint data satisfies matching criteria for its respective assigned set of identifiable fingerprint data.
Also provided is a method of operating a medical device in a secure manner. This method maintains a list of fingerprint-secured operations and associated fingerprint data for the medical device, where each of the fingerprint-secured operations is associated with a different fingerprint. The method obtains swiped fingerprint data, determines that the swiped fingerprint data satisfies matching criteria for the associated fingerprint data for a fingerprint-secured operation in the list, and, in response to the determining step, activates the fingerprint-secured operation.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
A more complete understanding of the subject matter may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures.
The following detailed description is merely illustrative in nature and is not intended to limit the embodiments of the subject matter or the application and uses of such embodiments. As used herein, the word “exemplary” means “serving as an example, instance, or illustration.” Any implementation described herein as exemplary is not necessarily to be construed as preferred or advantageous over other implementations. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description.
Techniques and technologies may be described herein in terms of functional and/or logical block components and various processing steps. It should be appreciated that such block components may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices. In addition, those skilled in the art will appreciate that embodiments may be practiced in conjunction with any number of data transmission protocols and that the system described herein is merely one suitable example.
For or the sake of brevity, conventional techniques related to infusion system operation, insulin pump and/or infusion set operation, blood glucose sensing and monitoring, signal processing, data transmission, signaling, network control, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail here. Examples of infusion pumps and/or communication options may be of the type described in, but not limited to, U.S. Pat. Nos. 4,562,751; 4,685,903; 5,080,653; 5,505,709; 5,097,122; 6,554,798; 6,558,320; 6,558,351; 6,641,533; 6,659,980; 6,752,787; 6,817,990; and 6,932,584, which are herein incorporated by reference. Examples of glucose sensing and/or monitoring devices maybe be of the type described in, but not limited to, U.S. Pat. Nos. 6,484,045; 6,809,653; 6,892,085; and 6,895,263, which are herein incorporated by reference.
The systems, methods, and technologies described below can be implemented in a medical device system having any number of different medical device types, along with any number of compatible or cooperating devices that are used with the different medical devices. The different medical devices may be associated with a single patient or with multiple patients. The medical devices may be designed to treat one or more different medical conditions, and each medical device might have a specific function in the context of an overall patient treatment or healthcare plan. The non-limiting examples described below relate to a medical device system used to treat diabetes, although embodiments of the disclosed subject matter are not so limited.
For ease of description, the examples provided below assume that one primary medical device for a single patient (e.g., a therapy delivery device or medication delivery device, such as an insulin infusion pump) can wirelessly communicate with a plurality of physically distinct controller devices. It should be appreciated that the techniques and technologies described herein can also be extended to accommodate a scenario where a single patient has two or more different medical devices, and/or to accommodate a more expansive deployment that contemplates a plurality of different patients. Moreover, the multiple controller devices may be owned or operated by the patient only, by the patient and at least one other person such as a caregiver, by one person other than the patient, or by more than one person other than the patient.
Certain preferred embodiments utilize portable devices that can be worn, carried, or held by the user. Alternatively, a given device could be designed as a somewhat stationary component (e.g., a bedside controller or monitor, a computer-based controller, or an appliance). Regardless of whether a device is mobile or stationary, it may be capable of wireless communication with other devices in the medical device system. In practice, the medical devices can form a relatively short-range wireless and localized network, which may be akin to a personal area network, a body area network, or a home network. The exemplary embodiments described below contemplate such a localized network, which is indicative of a typical deployment for a single patient.
In certain embodiments of insulin infusion system 100, at least one of its devices is suitably configured to communicate with a remote element 114, which may be implemented as a remote server, a server application, a remote computing device, a service provider, a network-based processor, or the like. As used here, remote element 114 is “external” to insulin infusion system 100 because it need not utilize the local data communication protocols and techniques employed within insulin infusion system 100, and because it need not be in close physical proximity to the local devices normally associated with insulin infusion system 100. The manner in which a device within insulin infusion system 100 communicates with remote element 114 may vary depending upon the particular configuration of insulin infusion system 100, the specific characteristics of the communicating devices, and the characteristics of remote element 114. For example, network communications may be routed using one or more data communication networks 116 (including a wide area network such as the internet), which may employ wireless and/or wired data transport links, as schematically depicted in
For the illustrated embodiment, glucose sensor transmitter 104 wirelessly communicates with insulin infusion pump 102 and with each wireless controller device 106. In addition, insulin infusion pump 102 can wirelessly communicate with each wireless controller device 106. Similarly, wireless controller devices 106 could wirelessly communicate with each other if necessary.
Data communicated to (and processed by) a wireless controller device 106 may include or represent, without limitation: physiologic patient data; device status information; time and date information; alarm/alert status; GPS data corresponding to the geographic position of the user; GPS data corresponding to the geographic position of pharmacies, hospitals, restaurants, service providers, stores, etc.; and other information related to the operation, status, or condition of the patient, related to any of the devices within insulin infusion system 100, or related to insulin infusion system 100 itself. For example, such data may include or represent bolus information, basal information, or sensor information. Such data may also include or represent information entered by the patient, a caregiver, or another person having access to a device of insulin infusion system 100 or remote element 114, such as, without limitation: reminders; event markers (for meals, exercise, or the like); alarms; notifications; or the like.
Insulin infusion pump 102 is configured to deliver insulin into the body of the patient via, for example, infusion set 110. In this regard, insulin infusion pump 102 may cooperate with insulin reservoir 112, which can be a replaceable or refillable fluid reservoir for the insulin. Thus, the amount of fluid in insulin reservoir 112 (and insulin reservoir 112 itself) may be considered to be a consumable quantity, element, or product of insulin infusion system 100. Likewise, infusion set 110 can be considered to be a consumable element or component of insulin infusion system 100 because it is typically designed as a disposable unit having a limited lifespan. Similarly, glucose sensor transmitter 104 may be treated as a consumable of insulin infusion system 100. Other features, items, products, accessories, and elements of insulin infusion system 100 could also be designated as consumables.
Glucose sensor transmitter 104 is suitably configured to measure a physiologic characteristic of the patient, namely, a glucose level of the patient. In the exemplary system described here, glucose sensor transmitter 104 measures the glucose level of the patient in real time. Glucose sensor transmitter 104 includes a wireless transmitter that facilitates transmission of physiological data of the user to other devices within insulin infusion system 100, such as insulin infusion pump 102. In turn, insulin infusion pump 102 can respond to the glucose measurements obtained from glucose sensor transmitter 104 by delivering insulin as needed.
For the illustrated embodiment, infusion pump 102 and/or wireless controller devices 106 can process received sensor data in an appropriate manner. For example, a device might display the current glucose level derived from the received sensor data and/or generate an alert or otherwise indicate low or high glucose levels. As another example, a device may process the received sensor data for purposes of calibration. As yet another example, infusion pump 102 may be configured to activate its infusion mechanism in response to the received sensor data.
Any of the devices within insulin infusion system 100 may include a display and related processing logic that facilitates the display of physiologic patient data, device status information, time and date information, alarm/alert status, and other information related to the operation, status, or condition of the patient, related to any of the devices within insulin infusion system 100, or related to insulin infusion system 100 itself.
Insulin infusion pump 102 may be configured to obtain glucose meter data 108 from an appropriate source, such as a blood glucose meter or test instrument (not shown) that measures the glucose level of a user by analyzing a blood sample. The blood glucose meter may be configured to transmit the measured glucose level to infusion pump 102 and/or to any of the wireless controller devices 106. Alternatively or additionally, infusion pump 102 may include a user interface that allows the patient or caregiver to enter the measured glucose level into infusion pump 102 (a wireless controller device 106 could be similarly configured to accept user-entered glucose values).
Each wireless controller device 106 facilitates remote programming, configuration, and activation of therapy-delivering operations carried out by insulin infusion pump 102. In addition, a wireless controller device 106 could serve as a remote monitor of infusion pump 102 (and possibly other devices within insulin infusion system 100). A number of features, functions, and technologies associated with wireless controller devices 106 are described in detail below.
Referring again to
Referring now to
The buttons 230, directional pad 232, and touch screen display element 234 can be used to administer a bolus of insulin, to change therapy settings, to change user preferences, to select display features, and the like. Depending upon the configuration settings, options, and/or user preferences, the wireless controller 206 can be manipulated using the buttons 230 only, the touch screen display element 234 only, or both. In some embodiments, the touch screen display element 234 could be switched on and off if the feature is not desired. In some embodiments, wireless controller 206 includes a suitably configured fingerprint reader 236, scanner, swiper, or detector. Fingerprint reader 236 can be utilized to access certain fingerprint-linked operations of wireless controller 206 and/or certain fingerprint-linked operations of an insulin infusion pump under the control of wireless controller 206 (as described in more detail below). In some embodiments, the functionality of fingerprint reader 236 is incorporated into touch screen display element 234.
The two therapy delivery devices D1/D2 are preferably patient-worn or patient-carried devices that remain with the patient 303 whenever they might be needed for medical treatment. Medical device system 300 includes a number of wireless controller devices that control functions of therapy delivery device D1: a first controller 308; a second controller 310; a third controller 312; and a fourth controller 314. Medical device system 300 includes a number of wireless controller devices that control functions of therapy delivery device D2: a fifth controller 316; a sixth controller 318; a seventh controller 320; and an eighth controller 322. Medical device system 300 also includes a combined controller 324, which is capable of controlling functions of both therapy delivery devices D1/D2.
First location 304 may be, for example, the place of work for patient 303, and second location 306 may be, for example, a vehicle used by patient 303. It might be convenient to have wireless controller devices that can be used when patient 303 enters first location 304 and second location 306. For instance, fourth controller 314 and eighth controller 322 could remain at first location 304 regardless of where patient 303 roams, and seventh controller 320 might remain at second location 306 regardless of where patient 303 travels. Similarly, even though some or all of the controllers located at dwelling 302 are portable, it may be desirable to keep them within the confines of dwelling 302 to ensure that at least one is always within close proximity to patient 303.
The deployment of multiple wireless controller devices for one medical device presents several challenges related to data synchronization, timing and execution of redundant or concurrent control commands, and conflicting wireless messages among the devices. A number of techniques, approaches, and methodologies that address these and other challenges are described in more detail below.
A medical device system as described here can implement a number of features, functions, operations, components, and technologies that enhance the user experience, provide security, facilitate better wireless communication among the devices, and enable e-commerce. Some of these enhancements are associated with the operation and functionality of a therapy delivery device, while others are associated with the operation and functionality of a wireless controller device. In addition, some of these enhancements involve the cooperation between one or more therapy delivery devices and/or one or more wireless controller devices. Moreover, some of the enhancements may involve one or more remote elements, such as a network-based server application.
As mentioned previously, a wireless-enabled therapy delivery device could be designed with native controller functionality. In other words, some or all of the features, functionality, components, and elements found in a wireless controller device may be incorporated into a therapy delivery device. In this regard,
This particular embodiment of medical device 400 generally includes, without limitation: a processing architecture 402, processor, or processor arrangement; a display element 404; a fingerprint reader 406; at least one human-machine interface (HMI) element 408; a suitable amount of memory 410; a graphics engine 412; a global positioning system (GPS) receiver 414; a navigation module 416; an advertisement server module 418; a wireless module 420; infusion pump hardware, software, and applications 422 (included if medical device 400 represents an infusion pump, and omitted if medical device 400 represents a controller device); controller hardware, software, and applications 424 (included if medical device 400 represents a controller device, and omitted if medical device 400 represents an infusion pump that lacks native controller functionality); a security module 426; a function disable/enable module 428; a data sync module 430; a tracking module 432; and an e-commerce module 434. The elements of medical device 400 may be coupled together via a bus 436 or any suitable interconnection architecture or arrangement that facilitates transfer of data, commands, power, etc.
Those of skill in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with medical device 400 (and other devices, elements, and components disclosed here) may be implemented in hardware, computer software, firmware, a state machine, or any combination of these. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and processing steps may be described generally in terms of their functionality. Whether such functionality is implemented as hardware, firmware, a state machine, or software depends upon the particular application and design constraints imposed on the embodiment. Those familiar with the concepts described here may implement such functionality in a suitable manner for each particular application, but such implementation decisions should not be interpreted as being restrictive or limiting.
Processing architecture 402 may be implemented or performed with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described here. A processor device may be realized as a microprocessor, a controller, a microcontroller, or a state machine. Moreover, a processor device may be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
Processing architecture 402 may include one processor device or a plurality of cooperating processor devices. Moreover, a functional or logical module/component of medical device 400 might actually be realized or implemented with processing architecture 402. For example, graphics engine 412, navigation module 416, advertisement server module 418, security module 426, function disable/enable module 428, data sync module 430, tracking module 432 and/or e-commerce module 434 may be implemented in, or be executed by, processing architecture 402.
Display element 404 represents the primary graphical interface of medical device 400. Display element 404 may leverage known CRT, plasma, LCD, TFT, and/or other display technologies. The actual size, resolution, and operating specifications of display element 404 can be selected to suit the needs of the particular application. Notably, display element 404 may include or be realized as a touch screen display element that can accommodate touch screen techniques and technologies. In this regard, a touch screen display element can be utilized to support panning and/or scrolling features (described below) of medical device 400. In practice, display element 404 may be influenced by graphics engine 412, and driven by a suitable display driver, to enable medical device 400 to display physiological patient data, status information for infusion pumps, status information for continuous glucose sensor transmitters, clock information, alarms, alerts, and/or other information and data received or processed by medical device 400. In this regard, display element 404 could be configured to receive image rendering display commands from graphics engine 412 and, in response thereto, render visual representations of physiological characteristic data (e.g., glucose levels), render menu screens, and render other graphical representations and visual displays as needed during the operation of medical device 400.
Fingerprint reader 406 is operatively coupled to security module 426 to accommodate the processing of fingerprint-secured operations of medical device 400 and/or fingerprint-secured operations of another device that is remotely controlled by medical device 400. Fingerprint reader 406 is designed to swipe fingerprints and, in response to such swiping, generate fingerprint data that corresponds to the swiped fingerprints. In preferred embodiments, fingerprint reader 406 is a distinct functional element of medical device 400 (see
HMI elements 408 represents the user interface features of medical device 400. Thus, HMI elements 408 may include a variety of items such as, without limitation: a keypad, keys, buttons, a keyboard, switches, knobs (which may be rotary or push/rotary), a touchpad, a microphone suitably adapted to receive voice commands, a joystick, a pointing device, an alphanumeric character entry device or touch element, a trackball, a motion sensor, a lever, a slider bar, a virtual writing tablet, or any device, component, or function that enables the user to select options, input information, or otherwise control the operation of medical device 400. In this context, HMI elements 408 may include a touch screen display element and/or fingerprint reader 406. Medical device 400 can detect manipulation of, or interaction with, HMI elements 408 and react in an appropriate manner. For example, a user could interact with HMI elements 408 to control the delivery of therapy (e.g., insulin infusion) to a patient via a therapy delivery device under the control of medical device 400. As another example, one or more of the HMI elements 408 could be operatively coupled to graphics engine 412 such that user interaction with those HMI elements 408 results in the generation of display shifting, panning, or scrolling commands that influence the manner in which information is displayed on display element 404. Display panning features are discussed in more detail below with reference to
Memory 410 may be realized as RAM memory, flash memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In this regard, memory 410 can be coupled to processing architecture 402 such that processing architecture 402 can read information from, and write information to, memory 410. In the alternative, memory 410 may be integral to processing architecture 402. As an example, processing architecture 402 and memory 410 may reside in an ASIC. A functional or logical module/component of medical device 400 might be realized using program code that is maintained in memory 410. For example, graphics engine 412, navigation module 416, advertisement server module 418, security module 426, function disable/enable module 428, data sync module 430, tracking module 432 and/or e-commerce module 434 may have associated software program components that are stored in memory 410. Moreover, memory 410 can be used to store data utilized to support the operation of medical device 400, as will become apparent from the following description.
A number of display features and characteristics are described in more detail below. Accordingly, graphics engine 412 may be suitably configured to perform image, graphics, and/or video processing as needed to support the operation of medical device 400. Graphics engine 412 cooperates with the display driver (not shown) of medical device 400 to control and manage the rendering of graphical information on display element 404. For example, graphics engine 412 generates image rendering display commands associated with items to be displayed (such as physiological characteristic data, menu screens, web pages, touch screen interface features, or the like), and display element 404 receives the image rendering display commands and, in response thereto, renders corresponding graphics as needed.
GPS receiver 414 may be any commercial civilian grade receiver. In accordance with known methodologies and techniques, GPS receiver 414 obtains geographic position data (also referred to as GPS data) corresponding to the geographic position of medical device 400. The GPS data may indicate a location of medical device 400 in terms of longitude and latitude measurements. GPS receiver 414 may also provide medical device 400 with the current date, the current time, the current time zone, and other pertinent information. The geographic position data obtained from GPS receiver 414 can be used to provide a variety of location-dependent information to the user of medical device 400. The relevance of such geographic position data is discussed in more detail below with reference to
Navigation module 416 is suitably configured to generate and present navigation instructions, location data, and map information to the user of medical device 400. In this regard, navigation module 416 can be operatively coupled to GPS receiver 414 such that geographic position data obtained by GPS receiver 414 can be processed by navigation module 416. Navigation module 416 may leverage existing navigation and mapping technologies, and utilize preloaded or dynamically downloaded map data to provide directions to a specified location (where the directions are influenced by the geographic position of medical device). Travel guidance is typically performed using a two-step process: (1) calculate a proposed route from the current position of medical device 400 to the desired destination; and (2) present guidance instructions to the user. The guidance instructions can be updated dynamically as the user traverses the proposed route. The relevance of navigation module 416 is discussed in more detail below with reference to
Advertisement server module 418 can generate, access, or present advertisements at medical device 400 at certain times during operation of medical device 400. Although the advertisements could be related to anything, preferred embodiments present contextually relevant advertisements to the user of medical device 400. In this regard, the advertisements can be related to or otherwise associated with: the use of medical device 400; consumables used by or with medical device 400; the treatment of the patient's medical condition; goods and/or services that might be related to the treatment of the medical condition; goods and/or services that might be of interest to the particular user of medical device 400; etc. As described in more detail below with reference to
Advertisement server module 418 can access, retrieve, or otherwise obtain advertisements that are stored and maintained locally at medical device 400. In such embodiments, contextually relevant advertisements (and possibly other types of advertisements) can be preloaded into medical device 400 and/or downloaded to medical device 400 at an appropriate time. Alternatively (or additionally), advertisement server module 418 can access, retrieve, or otherwise obtain advertisements that are stored and maintained remotely. In such embodiments, advertisement server module 418 could dynamically download advertisements on an as-needed basis, or a remote network-based application could push advertisements to advertisement server module 418 when appropriate or desirable to do so.
Advertisement server module 418 may also include or be associated with processing logic that can select, filter, or otherwise determine which advertisements to present at any given time. Filtering of advertisements could be performed in accordance with settings (e.g., user preferences) of medical device 400. In this regard, advertisement server module 418 may be operatively coupled to GPS receiver 414 such that geographic position data obtained by GPS receiver 414 can be processed by advertisement server module 418. Advertisement server module 418 can then select advertisements for goods and/or services that are available at facilities located near to the current location of medical device 400. For example, advertisement server module 418 might filter advertisements and only identify facilities, offices, or stores that are located within a predetermined distance from the current location of medical device 400 (e.g., one mile, five miles, or ten miles). Alternatively (or additionally), advertisement server module 418 might filter advertisements and only identify facilities, offices, or stores that can be reached within a predetermined travel time (e.g., a ten minute drive, a twenty minute walk, or a fifteen minute bike ride).
Wireless module 420 is a data communication module for medical device 400. Wireless module 420 is configured to support one or more wireless data communication protocols. Any number of suitable wireless data communication protocols, techniques, or methodologies may be supported by wireless module 420, including, without limitation: RF; an infrared transmission scheme such as IrDA; a short-range wireless transmission scheme such as Bluetooth; ZigBee (and other variants of the IEEE 802.15 protocol); a wireless local area network scheme such as IEEE 802.11 (any variation); IEEE 802.16 (WiMAX or any other variation); Direct Sequence Spread Spectrum; Frequency Hopping Spread Spectrum; a cellular/wireless/cordless telecommunication scheme; wireless home network communication protocols; paging network protocols; magnetic induction; satellite data communication protocols; wireless hospital or health care facility network protocols such as those operating in the WMTS bands; GPRS; and proprietary wireless data communication protocols such as variants of Wireless USB. In an embodiment of medical device 400, wireless module 420 may include or be realized as hardware, software, and/or firmware, such as an RF front end, a suitably configured radio module (which may be a stand alone module or integrated with other or all functions of the device), a wireless transmitter, a wireless receiver, a wireless transceiver, an infrared sensor, an electromagnetic transducer, or the like. Moreover, wireless device 400 may include one or more antenna arrangements (which may be located inside the housing of medical device 400) that cooperate with wireless module 420.
Medical device 400 may also support data communication over a cable, a wired connection, or other physical link, using one or more wired/cabled data communication protocols. Any number of suitable data communication protocols, techniques, or methodologies may be supported by medical device 400, including, without limitation: Ethernet; home network communication protocols; USB; IEEE 1394 (Firewire); hospital network communication protocols; and proprietary data communication protocols. Although not depicted in
Infusion pump hardware, software, and applications 422 are utilized to carry out features, operations, and functionality that might be specific to an insulin pump implementation. Again, infusion pump hardware, software, and applications 422 need not be deployed if medical device 400 is realized as a controller device having no infusion pump. Notably, infusion pump hardware, software, and applications 422 may include or cooperate with an infusion set 450 and/or a fluid reservoir 452 (as described above with reference to
Controller hardware, software, and applications 424 are utilized to carry out features, operations, and functionality that might be specific to a medical device controller implementation. Again, controller hardware, software, and applications 424 need not be deployed if medical device 400 is realized as a medical device having no native control capabilities. Controller hardware, software, and applications 424 may leverage known techniques to carry out conventional controller and/or monitor device functions and operations, and such known aspects will not be described in detail here.
Security module 426 may be suitably designed to secure certain operations of medical device 400 and/or a device that is remotely controlled by medical device 400, protect medical device 400 from electronic attacks and viruses, perform authentication routines, and otherwise provide security features for medical device 400. Security features are particularly desirable with embodiments that have wireless connectivity, network access, e-commerce capabilities, and the like. In certain embodiments, security module 426 is utilized to regulate operations of medical device 400 using swiped fingerprint data. In this regard, security module 426 may be operatively coupled to fingerprint reader 406 and/or to memory 410 for purposes of fingerprint analysis. As described in more detail below with reference to
Function disable/enable module 428 may be used to selectively disable and enable functions, features, or operations of medical device 400 as needed. Alternatively (or additionally), function disable/enable module 428 may be used to selectively disable and enable functions, features, or operations of a device that is remotely controlled by medical device 400. If medical device 400 includes fingerprint reader 406 and fingerprint-linked security features, then function disable/enable module 428 could be utilized to unlock or lock fingerprint-secured operations as appropriate. Moreover, in a system deployment having multiple therapy delivery devices and/or multiple controller devices (see
Data sync module 430 may be used to synchronize device and user data 454 at medical device 400. In this regard, physiological characteristic data, patient data, device status data, user preference data, device configuration settings, historical data, predictive data, and other types of data generated or otherwise processed by one device (such as a controller device or a therapy delivery device) may need to be shared with medical device 400. In a system deployment having multiple therapy delivery devices and/or multiple controller devices (see
Tracking module 432 was mentioned briefly above with reference to advertisement server module 418. Tracking module 432 is suitably configured to determine when a replenishable, refillable, maintainable, or replaceable item (such as a consumable) associated with medical device 400 needs to be replenished, refilled, maintained, replaced, etc. In this regard, tracking module 432 can monitor a remaining quantity, supply, inventory, an amount, a maintenance schedule, a timer, or any other measurable or detectable characteristic of the item to determine whether or not that item needs to be replenished, replaced, or maintained. In certain embodiments, tracking module 432 automatically determines when a consumable associated with medical device requires replacement or replenishment by analyzing device and user data 454. In the context of an infusion system, a consumable may be, without limitation: a medication such as insulin; a fluid reservoir, such as an insulin reservoir for an insulin infusion pump; an infusion set for an infusion pump; blood glucose meter test strips; blood glucose meter lancets; or a physiological characteristic sensor, such as a glucose sensor. A consumable may also be associated with the operation of the medical device itself. For example, a consumable may be, without limitation: a subscription to a remote monitoring service; additional increments of service time (e.g., a month of monitoring service); ring tones; wallpaper images; or the like.
In some embodiments, tracking module 432 determines a need to acquire a consumable product, item, or goods associated with operation of medical device 400. Alternatively (or additionally), tracking module 432 may determine a need to acquire something that is associated with treatment, diagnosis, or management of the patient's medical condition. In this regard, tracking module 432 could analyze device and user data 454 to determine whether the monitored medical condition requires attention. For example, if medical device 400 is part of an insulin infusion system, then tracking module 432 could monitor the glucose level of the patient and take action when it detects a glucose level that is not within the patient's normal range. In turn, tracking module 432 could influence advertisements or e-commerce features at medical device 400, where such advertisements or e-commerce features are associated with goods and/or services related to treatment of the medical condition. The relevance of tracking module 432 is described in more detail below with reference to
E-commerce module 434 is associated with a number of e-commerce, electronic transaction, and remote ordering features and functions of medical device 400. In preferred embodiments, e-commerce module 434 is operatively coupled to tracking module 432; this allows tracking module 432 to influence e-commerce at medical device 400. For example, e-commerce module 434 could initiate an order of a replenishable item when tracking module 432 determines that the replenishable items needs to be replenished. To accommodate internet-based electronic transactions, medical device 400 may include an appropriate web browser application 456, which could interact with e-commerce module 434. As is well understood by those familiar with online transactions, web browser application 456 can receive and present at least one web page that facilitates the completion of electronic orders for replenishable items, goods, services, or the like. The relevance of e-commerce module 434 is described in more detail below with reference to
Medical devices (e.g., a therapy delivery device, a controller device, or a therapy delivery device with integrated controller functionality) and medical device systems as described herein can support a number of features and operations that enhance the functionality of the medical devices and/or enhance the user experience of the medical devices. Unless otherwise noted, the description of these features and operations can apply generally to a therapy delivery device, a controller device, or a combined therapy/controller device. The following sections include descriptions of various processes and methods that may be performed by a medical device or by the medical device system. The various tasks performed in connection with a given process may be performed by software, hardware, firmware, or any combination thereof. For illustrative purposes, a process might be described with reference to elements mentioned above in connection with
Fingerprint-Linked Control
A medical device as described herein may be suitably configured to support fingerprint-secured or fingerprint-linked operations. Such fingerprint related functions may involve, for example, fingerprint reader 222 (
Task 504 can assign the operations in any desired manner. For example, after swiping a single fingerprint, task 504 could allow the user to select an operation that will be linked to that particular fingerprint. Task 504 could also allow the user to identify the fingerprint by name, relationship, or otherwise. For a combination of at least two fingerprints swiped in sequence, task 504 may prompt the user to swipe the sequence of fingerprints before presenting the option to select and assign the operation to that particular combination of fingerprints. Thus, the list of fingerprint-secured operations could contain ten different operations, each being associated with a different fingerprint (as used here, a thumbprint is also considered to be a fingerprint) of one person. A list could also include fingerprint-secured operations associated with fingerprints of different people. Moreover, the list could associate the same fingerprint-secured operation to two different fingerprints (which may be taken from the same or different people). A one-to-multiple association like this might be desirable to allow the patient and a caregiver to control the same function using different fingerprints. In another deployment, the medical device could be configured to control delivery of therapy to a first patient (via a first therapy delivery device) and to control delivery of therapy to a second patient (via a second therapy delivery device), where the various therapy delivery operations are secured by different fingerprints.
Although a medical device could be suitably configured to support any number of different fingerprint-related operations, the embodiments described here maintain a list that contains therapy delivery operations linked to respective sets of identifiable fingerprint data, a list that contains display setting operations linked to respective sets of identifiable fingerprint data, and/or a list that contains menu selection operations linked to respective sets of identifiable fingerprint data. Different therapy delivery operations cause the medical device to deliver or administer different types or amounts of therapy to the patient (via the medical device itself or via a therapy delivery device under the control of the medical device). For example, one fingerprint-secured operation might correspond to the delivery of a first dosage of insulin, and another fingerprint-secured operation might correspond to the delivery of a second dosage of insulin. A display setting operation may cause the medical device to display a respective visual display, e.g., a chart, a graph, or the like. Thus, different fingerprints can be used to switch the display of the medical device. A menu selection operation may cause the medical device to display a respective menu, e.g., the home menu, a settings menu, a therapy programming menu, or the like. Thus, commonly used menus can be fingerprint-coded to facilitate quick switching of menu screens.
Notably, each fingerprint-secured operation may be associated with one fingerprint or with a combination of different fingerprints. The list of fingerprint data may be indicative of fingerprints taken from any number of different people, e.g., the patient, a caregiver, a parent, a teacher, or the like. Although a combination of fingerprints will usually be taken from the same person, this need not always be the case. This list of
The list also includes one entry corresponding to a single fingerprint from a second person: the left pinky finger. This entry is linked to the operation labeled Deliver Therapy 1. Thus, Delivery Therapy 1 can be initiated by the first person (using the right index finger) or by the second person (using the left pinky finger). The list also includes two entries that require a specific combination or sequence of fingerprints taken from the first person. The operation labeled Show Chart is linked to the combination of the left index finger and the left middle finger. The operation labeled Reset Device is linked to the combination of the left index finger and the right index finger. Although certain embodiments might support only a limited number of fingerprint-secured operations (such as five or ten), the actual number need not be limited.
After the medical device has been trained with swiped fingerprints, process 500 can secure the associated operations such that they can be activated or unlocked using subsequently swiped fingerprint data. For example, the medical device can obtain swiped fingerprint data (task 508) using a fingerprint reader located on the medical device (or using a fingerprint reader that communicates with the medical device). As mentioned previously, a touch screen display element or a devoted sensor element could serve as the fingerprint reader. The swiped fingerprint data can then be analyzed to compare the swiped fingerprint data to identifiable fingerprint data maintained in the list of fingerprint-related operations (task 510). If the swiped fingerprint data satisfies certain matching criteria (query task 512) for a respective set of identifiable fingerprint data, then process 500 can unlock or activate the corresponding fingerprint-secured operation (task 514). The operation could be activated at the medical device itself or, if the medical device is a remote controller, then the remote controller could wirelessly transmit a control message to the device under its control—upon receipt of the control message, the receiving device can then execute the designated operation. If, however, the swiped fingerprint data does not match any of the previously swiped and trained fingerprint data, then process 500 will keep all fingerprint-linked operations secured. In addition, process 500 may present an error message (task 516) or simply exit without taking any action.
Display Features
A medical device, such as an insulin infusion pump and/or a wireless controller for an insulin infusion pump, may include a number of display features that enhance the user experience, appearance of the device, and enable better user interaction with the device. These display features include, without limitation: panning or scrolling of graphs and charts; hyperlinks or shortcuts for navigation of menu screens; and user-customizable display settings.
Display panning techniques and functions may involve, for example, display element 404, HMI elements 408, graphics engine 412 (see
The illustrated embodiment of process 600 obtains measurement data corresponding to values of a physiological characteristic measured over a period of time, e.g., glucose measurement data (task 602). This data may be stored in the memory of the medical device so that it can be processed and rendered at the request of the user.
Process 600 can then render and display a graphical representation of a first portion of the glucose measurement data (task 604). Only a portion of the data shown in
The user of the medical device may want to view the glucose measurement data that is before or after the time interval shown in
The display panning command causes the medical device to pan the graphical representation of the data across the display element, while updating and refreshing the displayed data (task 610). In preferred embodiments, such panning is performed in a smooth and continuous manner such that the user can perceive the graph moving across the display element. After completion of the panning operation, process 600 will render and display a graphical representation of a second portion of the overall glucose measurement data (task 612). In this regard,
Thus, for this example the graph 648 has been panned to the right, thus introducing “older” glucose measurement data on the left side of graph 652 and discarding “newer” glucose measurement data that had previously appeared on the right side of graph 648. In other words, at least a portion of graph 652 is not included in graph 648, and at least a portion of graph 648 has been removed from the display element. Notably, the glucose measurement data is rendered on the display element using fixed display scaling for both graph 648 and graph 652. In other words, the horizontal and vertical display scaling is preserved (task 614) during and after panning. Accordingly, although graph 648 and graph 652 convey values of the glucose level measured during different intervals of the overall period of time (see
The example provided here corresponds to dynamic panning along a time axis for the values of the measured physiological characteristic. Alternatively (or additionally), a display rendered by the medical device could be panned or scrolled along one or more other axes. For example, if the vertical resolution of the display element cannot accommodate the entire range of measured values, then the vertical axis of the rendered graphs could be panned while preserving the vertical scaling. Moreover, a touch screen implementation could accommodate panning in any direction. In other words, panning need not be restricted to the horizontal or vertical axes. In some touch screen implementations, multi-touch gestures could result in other adjustments to a displayed screen. For example, the medical device could support zooming in and out, display rotation, orientation adjustment, and switching of displays by detecting touching or movements of more than one finger.
As mentioned briefly above, the medical device could employ hyperlinks, hotkeys, or shortcuts to facilitate easy navigation and traversal of menu screens. Navigation of menu trees of older medical devices can be cumbersome and time consuming, especially if the menu structure is “linear” in nature, i.e., menus are navigated in a serial or sequential manner. Hyperlinks or shortcuts displayed on menu screens would allow the user to quickly jump to a home screen, to commonly used menu screens, or the like. Thus, even if a particular menu screen is nested rather deeply within a linear menu structure, a shortcut or hyperlink displayed on that particular menu screen would allow the user to easily return to another screen or menu. In practice, a menu shortcut could be linked to a button, a specified pattern or sequence of button presses, an active link that is displayed, a voice command, etc. Alternatively, a hyperlink may be displayed following an alarm, alert, or notification as a logical sequence to address or take action to the indicated state. For example, if the user receives a notification to calibrate their continuous glucose sensor, a hyperlink option would be provided on the notification screen to jump to the sensor calibration function.
As mentioned briefly above, the medical device could support user-customizable display settings that can be adjusted to personalize the look and feel of the medical device. For example, the medical device could support different display screen wallpapers, backgrounds, skins, or themes. Moreover, the medical device could support the use of personalized avatars, photographs, or other indicia of the patient or user. In addition to customizable display features, the medical device could support customizable sounds, alerts, ring tones, and alarms. Such customizable features may be desirable from a user standpoint even if they have little to no impact on the actual functionality of the medical device.
Coordination Between Multiple Devices
As mentioned previously with reference to
For this embodiment, all of the controller devices and the therapy device are maintained in a respective idle state or sleep mode when they are inactive. If all of the devices are in the idle state (query task 702), then process 700 continues because any one of the devices might be activated at any time to issue control commands. If, however, any one of the devices is active, then process 700 can assume that the active device is or will be issuing control commands. If process 700 detects some form of user interaction with one of the idle controller devices (query task 704), then process 700 continues. Otherwise, process 700 may be re-entered at an appropriate point, such as task 702. Regarding query task 704, each controller device can monitor itself to detect when user interaction occurs. Such user interaction may be associated with manipulation of an HMI element, engagement with a touch screen, motion detected by the controller device, a voice command detected by the controller device, or any action that causes the controller device to transition out of the idle state. Referring to
In response to the detected user interaction, the activated controller device wirelessly broadcasts a lockout (disable) message (task 706). As explained in more detail below, the lockout message is broadcast in preparation of issuing a control command for the therapy device. This lockout message is suitably formatted and configured to disable at least one function of other controller devices and/or the therapy device upon receipt. In practice, the lockout message may convey a simple switching instruction that can be interpreted by any device that receives it, or it may convey specific information that is processed and acted upon by the receiving devices. The actual content and format of the lockout message can vary from one system to another, depending upon the specific needs and the deployment environment.
Process 700 assumes that the lockout message is wirelessly received by at least one other device other than the active controller (task 708). Again,
After broadcasting the lockout message, the active controller can wirelessly transmit a control command to the therapy device (task 712). The control command is suitably formatted and configured to control one or more functions of the therapy device upon receipt of the control command at the therapy device. Process 700 assumes that the control command is successfully received and executed at the therapy device (task 714).
In the illustrated embodiment, the therapy device sends an acknowledgement message after it executes the control command (task 716). The acknowledgement message indicates that the control command was executed by the therapy device. The acknowledgement message may be broadcast or it may be intended only for the active controller. Process 700 assumes that the active controller receives the acknowledgement message (task 718). In this regard,
In certain embodiments, the active controller may also broadcast a synchronization message that conveys synchronization data. The synchronization message may be broadcast separately, or it may be broadcast with the unlock message (or the unlock message may include the synchronization data). The synchronization data facilitates synchronizing of status information among the various devices in the system.
In response to the synchronization data conveyed in the unlock message (or in the synchronization message), process 700 will synchronize the status information among the system devices (task 724). Referring to
Notably, process 700 ensures that only one controller device can issue a control command to the therapy device. The lockout message temporarily disables the other controller devices, which prevents them from inadvertently issuing conflicting, redundant, or concurrent control commands. In practice, the devices in the system could implement procedures (e.g., conflict resolution, queuing, etc.) to handle the unlikely situation where two or more controllers simultaneously issue control commands. In such a scenario, the therapy device will resolve the race condition in an appropriate manner to ensure that only one controller is designated as the active controller.
Process 730 is similar to process 700 in that it also checks whether all of the devices are in an idle state (query task 732). Unlike process 700, however, process 730 detects some type of user interaction at the therapy device rather than at one of the controllers (query task 734).
The received lockout message disables at least one function of the controller devices (task 740).
After execution of the commanded function or functions, the therapy device wirelessly broadcasts an unlock message (which may include a synchronization message), which is intended for receipt by the disabled devices (task 746). As described above for process 700, a separate synchronization message could also be broadcast after execution of the commanded function or functions. Task 748 of process 730 assumes that all of the disabled devices receive the unlock/synchronization message(s). Moreover,
Notably, process 730 ensures that the therapy device can issue control commands for itself, while preventing or ignoring conflicting commands that might be issued by a controller device. The lockout message temporarily disables the controller devices, which prevents them from inadvertently issuing conflicting, redundant, or concurrent control commands.
Process 760 is similar to process 700 in that it also checks whether all of the devices are in an idle state (query task 762), and it also detects a form of user interaction at one of the controller devices (query task 764).
In response to receiving the control command, the therapy device wirelessly broadcasts a lockout (disable) message (task 768), which is preferably received by all of the controller devices in the system (task 770). In contrast, the active controller device in process 700 issues the lockout message.
After broadcasting the lockout message, the therapy device can then process, execute, or perform the previously received control command (task 774) in an appropriate manner. In practice, the control command may be acted upon after a slight delay to ensure that the controller devices have been disabled and/or to provide time for the therapy device to resolve any outstanding command conflicts or timing problems.
As described previously in this section, it may be important to keep components in the medical device system synchronized with each other. Synchronization ensures that each device consistently processes the same device status data, the same patient data, the same physiological characteristic data, etc. In this regard,
Process 800 begins with the assumption that the therapy device and the controller device are in wireless communication with each other. In other words, they are within normal wireless operating range. Although not a requirement, the following description designates the therapy device as the “hub” or “master” or “coordinator” device, and designates the controller device as the “slave” or “secondary” or “end node” device. These exemplary designators are utilized for the sake of illustration, and are not intended to limit or otherwise restrict the scope of the embodiments described here.
Process 800 may involve the periodic or scheduled broadcasting or synchronization messages (task 802) by one of the two devices. For this particular embodiment, the therapy device broadcasts beacons according to a predetermined and defined time schedule, and the beacons include, convey, or represent the synchronization messages. Moreover, the synchronization messages are intended for receipt by the controller device. During normal wireless operation, beacons will be broadcast in certain designated time slots, and those time slots are known a priori by both the transmitting device and the receiving device.
Process 800 checks whether the devices have lost wireless connectivity (query task 804). For the embodiment described here, task 804 can be performed by the controller device, and task 804 determines when the controller device loses wireless connectivity with the therapy device. In practice, the controller device can assume that wireless connectivity is lost when at least one synchronization message (or beacon) is not successfully received in its designated time slot. Alternatively, the controller device could monitor an appropriate metric related to wireless connectivity, e.g., received signal strength, signal-to-noise ratio, data error rate, or the like. If process 800 determines that wireless connectivity is lost (query task 804), then it can disable at least one function of the controller device (task 806). For this particular example, task 806 is preferably performed by the controller device itself as part of a self-disabling procedure.
Soon after wireless connectivity is regained or reestablished (query task 808), the controller device will begin receiving synchronization messages from the therapy device (task 810). Once it begins receiving new synchronization messages, the controller device can determine that it missed at least one synchronization message (broadcast during the period of time when wireless connectivity was lacking). This description assumes that some or all of the synchronization messages will include updated synchronization data, which is currently maintained by the therapy device. As mentioned previously in this section, the synchronization data could be associated with the status of the therapy device, patient-related data, physiological characteristic data, the status of the medical device system, or the like. Upon receipt of the updated synchronization data, process 800 synchronizes the controller device with the therapy device. In other words, the relevant status data of the controller device is synchronized with the corresponding current status data of the therapy device. After synchronization is complete, the disabled function(s) of the controller device can be re-enabled (task 814). At this point, both devices will be synchronized and wirelessly communicating with each other.
Process 830 may begin by obtaining a user input at the wireless controller device (task 832). The user input, which may be associated with user interaction with an HMI element of the controller device, corresponds to a request to initiate a command that influences therapy delivered by the therapy device. For example, the user input may be linked to a bolus delivery command, a therapy programming adjustment, a therapy schedule change, or the like. In contrast, other user inputs do not necessarily influence therapy delivered by the therapy device. These non-influencing user inputs include, for example: requests to display historical patient data; requests to display non-critical device status data; requests to view user preference settings; or the like.
Due to the importance of therapy-related commands, process 830 preferably checks a synchronization status between the controller device and the therapy device (query task 834). As described above for process 800, the synchronization status could be verified by checking whether the controller device has missed any synchronization messages that are broadcast in accordance with an agreed upon schedule. This synchronization check may be performed in response to the user input, or it may be performed periodically as a background task regardless of user inputs. If the devices are synchronized, then process 830 can proceed to task 842 (described below). If, however, the devices are not synchronized, then process 830 prevents execution, initiation, or processing of the requested command (task 836). In practice, task 836 may cause the controller device to disregard, ignore, or disable the effect of the requested command. This safeguard is desirable to ensure that the controller device does not inadvertently issue a conflicting or redundant control command due to lack of synchronization with one or more other independently operating controller devices.
If the devices are not properly synchronized, then the requested command may be disregarded until the controller device receives one or more synchronization messages (task 838). As described previously in this section, a synchronization message preferably contains or conveys updated synchronization data that is maintained at a hub or coordinator device. In this example, the synchronization messages are sent by the therapy device (via periodic beacons or upon interrogation by the controller device). Thus, the updated synchronization data can be used to synchronize the controller device with the therapy device (task 840). This synchronization step makes the controller device current with the therapy device and, ideally, with all other controller devices in the medical device system. In connection with task 840, process 830 could confirm that the devices are properly synchronized (query task 834). After synchronization, the controller device transmits one or more control messages to the therapy device (task 842). The control message or messages correspond to the original requested command (task 832). Thus, an actionable or executable control command will be transmitted to the therapy device only when the controller device is synchronized with the therapy device.
Automated E-Commerce and Advertisement Serving
Devices in a medical device system as described here may be suitably configured to automatically detect when to perform certain functions, to learn usage habits or patterns of the users, to intelligently introduce features as needed based on user experience, and the like. For example, a therapy delivery device (e.g., an infusion pump such as an insulin infusion pump) or a controller device for a therapy delivery device could be suitably configured to initiate, perform, or introduce certain e-commerce features and functions when necessary, relevant, or useful to do so. In preferred embodiments, the e-commerce features are contextually related to the operation or status of the medical device, the operation or status of the medical device system, a medical condition of the patient, treatment of the patient, and/or the preferences of the patient or user. The device learning and e-commerce related processes and techniques may involve, for example, some or all of the following components and modules depicted in
A system deployment could also allow the user to purchase, subscribe to, or otherwise participate in a remote monitoring service. In this regard, a healthcare professional or caregiver could actively monitor the patient and/or device status in a remote manner and provide recommendations as needed. The service could also accommodate remote programming and configuration of the patient's medical device if so desired.
The exemplary embodiment described here obtains geographic position data that indicates a location of the medical device (task 904). The geographic position data may include or be realized as GPS data, and the GPS data could be obtained from a suitably configured onboard GPS receiver of the host medical device. In practice, the geographic position data is indicative of the current location of the medical device, and task 904 is preferably performed in an ongoing manner as a background task during active operation of the medical device. The relevance of the geographic position data is described in more detail below.
This particular version of process 900 automatically determines when a consumable associated with the medical device requires replenishment, replacement, maintenance, or the like (query task 906). In connection with this determination, process 900 could also indicate or recommend a quantity, number of units, volume, or amount of the consumable that might be required. Moreover, process 900 can automatically determine when the patient might need medical treatment, medical attention, a medical diagnosis, or the like (query task 908). The determinations associated with query tasks 906 and 908 could be made independently and concurrently at any time. Accordingly,
If query task 906 determines that a consumable needs to be replenished, replaced, maintained, or refilled, then process 900 may prompt an electronic transaction for that particular consumable. In some embodiments, the medical device displays an active link to a vendor, seller, or provider of the consumable (task 910). In this context, the active link may be a graphically rendered interactive element that can be activated or manipulated by the user of the medical device. For example, the active link may be a hyperlink, a soft button, an icon, or other element rendered on the display element of the medical device. In response to selection or manipulation of the active link, process 900 initiates an electronic transaction for the consumable (task 912). The electronic transaction may be associated with an online transaction, an electronic order, an internet-based transaction, a purchase order conveyed over a cellular telephone network, a web-enabled order, an e-commerce transaction, or the like. In this regard, the medical device may establish a wireless e-commerce session with a remote e-commerce application (task 914), which may reside at a network server, a remote computing device, or any location that is physically distinct from the medical device itself. In practice, task 914 may be associated with a data communication session (preferably a secure session) during which information can be transferred between the medical device and the remote e-commerce application.
The medical device or a user of the medical device can order an appropriate quantity, number of units, or amount of the consumable during the e-commerce session (task 916). For instance, during this session the e-commerce module of the medical device can cooperate with the remote e-commerce application to execute a purchase transaction for the consumable. In certain embodiments, the system supports user input that can filter or modify transactions or recommendations made by the medical device. For instance, the user might be allowed to purchase multiple items (which may or may not be suggested by the system, adjust quantities, only order the recommended item, etc.). In certain embodiments, the geographic position data obtained during task 904 is used to identify at least one provider, vendor, or seller of the item of interest (task 918), where the identified party (or parties) maintains an inventory of the item at a facility or store that is located within a predetermined distance from the present location of the medical device. Thus, the geographic position data can be used to guide the user of the medical device to a nearby storefront, office, or facility that carries the consumable product that is in need of replenishment or replacement. Moreover, the geographical position data could be processed to provide directions to the storefront, office, or facility (task 920). Notably, navigation guidance and directions to a facility will be influenced by the geographic position data and by the geographic location of the facility itself. The directions, guidance information, and/or a map could be rendered on the display element of the medical device, and the displayed information could be updated periodically or in substantially real-time in response to movement of the medical device. In certain embodiments, the geographic position data obtained during task 904 is used to support social networking features and applications. For example, the geographic position data could be used to locate and/or identify nearby users of compatible medical devices, and the compatible medical devices could support a variety of social networking applications (such as text messaging, chatting, games, etc.).
Referring to the second branch of process 900, if query task 908 determines that medical treatment, attention, or diagnosis should be recommended, then process 900 may analyze and process the geographic position data (obtained during task 904) to identify at least one provider, vendor, supplier, or seller of goods and/or services that are related to the medical condition or to treatment of the medical condition (task 922). Thus, process 900 can identify a provider of medical services, a physician, a hospital facility, a restaurant or convenience store that sells human nourishment (food and/or drink) that might be associated with treatment of the medical condition, a treatment facility, or the like. As mentioned above, process 900 could filter or limit the identified parties to those having a facility, office, or storefront that is located within a predetermined distance from the present location of the medical device. Moreover, the system may allow the user to interact with the medical device to filter or modify treatment transactions or recommendations made by the medical device.
In this embodiment, the geographical position data is also used to provide directions, a map, and/or navigation guidance to the store, restaurant, medical office, hospital, or facility of interest (task 924), as described above for the other branch of process 900. For example, if the patient is diabetic and the medical device detects a glucose level that is below a certain threshold level for the patient, then process 900 may identify a nearby restaurant or convenience store, and guide the patient to the restaurant or store. In addition, the medical device could prompt or initiate an electronic transaction for the desired goods and/or services (task 926), using the approaches described above for the other branch of process 900.
In connection with process 930, the medical device may generate, produce, or otherwise obtain device status data (task 932), where such status data indicates a remaining quantity, supply, inventory, or amount of a consumable used by the medical device. It should be realized that the device status data may be associated with operation of the medical device itself, or it may be associated with operation of another device that communicates with the medical device. For example, if the medical device is a wireless controller device, then the device status data may be related to operation of the controller device and/or related to operation of a therapy device under the control of the controller device.
Several examples of applicable consumables were mentioned above with reference to process 900. Thus, the status data obtained during task 932 may indicate a level of fluid remaining in a fluid reservoir, a remaining useful life of a physiological characteristic sensor, a remaining useful life of an infusion set, or the like. Process 930 assumes that the medical device is capable of uploading or otherwise transmitting the device status to a remote computing device or application that is physically distinct and separate from the medical device itself (task 934). Although not required, preferred embodiments upload the device status data using wireless data communication techniques. Process 930 also assumes that the device status data is successfully received at the remote server application (task 936). Upon receipt, the server application may analyze and process the device status data in an appropriate manner (task 938) to determine when a consumable associated with the medical device requires replacement, replenishment, maintenance, refilling, etc. This aspect of process 930 was described above with reference to process 900, and will not be redundantly described here.
If the server application determines that a consumable needs to be replenished (query task 940), then the server application can take appropriate action. Otherwise, the server application may continue monitoring the received device status data. When a consumable needs to be replenished or replaced, the server application may generate a message that indicates a need to replenish that particular consumable (task 942). In certain situations, this message may indicate or identify a quantity, number of units, volume, or amount of the consumable that might be required. This replenish message can then be communicated back to the medical device using any suitable data transmission scheme (task 944). Although not always required, preferred embodiments communicate the replenish message in a wireless manner.
The specific content, format, and configuration of the replenish message may vary from one deployment to another, and may vary as necessary to meet the needs of the particular application. For example, the replenish message may include an active link to a vendor, supplier, or seller of the consumable. As mentioned above with reference to process 900, an active link in this context facilitates the initiation of an electronic transaction for the consumable (at the medical device). In practice, the active link could be delivered via an email, a text message, an HTML document such as a web page, or the like. As another example, the replenish message may include or be associated with an advertisement for the particular consumable; the advertisement might identify an address, a business name, a telephone number, and/or other pertinent information related to the vendor, supplier, or provider of the consumable. As yet another example, the replenish message may be conveyed in a voicemail format by placing a telephone call to a telephone-enabled medical device, or it may be conveyed in an electronic media file (audio or video) that is transmitted to the medical device.
Process 930 assumes that the replenish message is successfully received by the medical device (task 946). The medical device can then process and respond to the replenish message in an appropriate manner (task 948). For example, the medical device can perform one or more of the following actions, without limitation: initiate an electronic transaction (or any form of transaction) for the consumable; present an advertisement for the consumable; display an active link to a vendor, seller, or provider of the consumable; display an HTML document, such as a web page that facilitates completion of a transaction for the consumable; convey content that is included in the replenish message; identify a vendor, seller, or provider of the consumable; or provide directions to a facility maintained by a vendor, seller, or provider. As mentioned above, the medical device might allow the user to filter or modify transactions or recommendations made by the medical device. For instance, the user might be allowed to purchase multiple items (which may or may not be suggested by the system, adjust quantities, only order the recommended item, etc.). In certain embodiments, the replenish message includes or conveys one or more advertisements, and the medical device is capable of filtering advertisements using native filtering settings (task 950). Such filtering allows the medical device to selectively present one or more of the advertisements, based on the filtering routine (task 952). Thus, even if the server application sends multiple advertisements to the medical device, process 930 could implement filtering algorithms, user settings, or other logic that blocks certain advertisements and/or allows certain advertisements.
In connection with process 956, the medical device may generate, produce, or otherwise obtain patient data (task 958), where such patient data is somehow associated with, descriptive of, or linked to a medical condition of a patient. It should be realized that the patient data may be associated with operation of the medical device itself, or it may be associated with operation of another device that communicates with the medical device. For example, if the medical device is a wireless controller device, then the patient status data may be related to operation of a patient monitor and/or related to operation of a therapy device that is under the control of the controller device.
The medical device may also generate or obtain geographic position data that indicates a location of the medical device (task 960). As mentioned previously, such geographic position data could be obtained from an onboard GPS receiver. This embodiment of process 956 continues by uploading or otherwise transmitting the patient data and the geographic position data to the remote computing device or application (task 962). Although not required, preferred embodiments upload the patient data and the geographic position data using wireless data communication techniques. Process 956 assumes that the patient data and the geographic position data is successfully received at the remote server application (task 964). The server application can then analyze and process the patient data in an appropriate manner (task 966) to determine whether when the medical condition of the patient requires attention, treatment, or diagnosis (query task 968). This aspect of process 956 was described above with reference to process 900, and will not be redundantly described here.
If the server application determines that medical treatment, diagnosis, or attention is necessary, then the server application can take appropriate action. Otherwise, the server application may continue monitoring the received patient data. When medical attention, treatment, or diagnosis is recommended, the server application processes the geographical position data to find relevant advertisers that maintain one or more facilities that are located within a predetermined distance from the medical device (task 970). In other words, the server application uses the geographic position data as filtering criteria to identify vendors, suppliers, or providers that are located near to the medical device and, presumably, near to the patient. In this regard, process 956 generates at least one advertisement for the geographically filtered advertisers (task 972), and the content of the advertisements will be influenced by the geographic position data. In preferred embodiments, these filtered advertisements are for goods and/or services that are somehow related to the treatment, diagnosis, cure, or research of the patient's medical condition. The generated advertisements can then be communicated back to the medical device using any suitable data transmission scheme (task 974). Although not always required, preferred embodiments communicate the advertisements in a wireless manner.
The specific content, format, and configuration of an advertisement, and the manner in which it is conveyed, may vary from one deployment to another, and may vary as necessary to meet the needs of the particular application. In practice, an advertisement could include or be associated with a text message, an HTML document such as a web page, an active link to a service provider, or the like. Moreover, an advertisement might identify an address, a business name, a telephone number, and/or other pertinent information related to the vendor, supplier, or provider.
Process 956 assumes that at least one advertisement is received by the medical device (task 976). The medical device can then filter the advertisements using native filtering settings (task 978), and selectively present one or more of the filtered advertisements (task 980). Thus, even if the server application sends multiple advertisements to the medical device, process 956 could implement filtering algorithms, user settings, or other logic that blocks certain advertisements and/or allows certain advertisements. The medical device can then process a filtered advertisement in an appropriate manner (task 982). For example, the medical device can perform one or more of the following actions, without limitation: initiate an electronic transaction (or any form of transaction) for the goods/services; present the advertisement at the medical device; display an active link to a vendor, seller, or provider of the goods/services; display an HTML document, such as a web page that facilitates completion of a transaction for the goods/services; convey the content of the advertisement; identify the supplier, vendor, seller, or provider of the goods/services; or provide directions to a facility maintained by the supplier, vendor, seller, or provider. As mentioned previously, the medical device can obtain user input that allows the user to filter or modify transactions or recommendations made by the medical device.
Process 1000 generally relates to a native and embedded process that can be implemented by an individual medical device, regardless of network connectivity, internet connectivity, or connectivity with another medical device in a system. Accordingly, the medical device stores advertisements locally (task 1002), and the advertisements may be preloaded by the manufacturer of the device, by the patient, by a physician, etc. A network-enabled medical device could receive advertisements from a remote application and store the advertisements locally. During process 1000, the medical device may obtain and analyze device status data (its own status data and/or the status data of another device) and/or patient data (task 1004) to determine whether to serve relevant advertisements. In certain embodiments, the medical device also obtains geographic position data for a location of the medical device (task 1006).
The medical device automatically determines when a consumable needs to be replenished or replaced (query task 1008) and/or when the patient needs medical treatment or attention (query task 1010). In response to an affirmative determination by query task 1008 or query task 1010, the medical device processes the geographic position data to find relevant advertisers having facilities, stores, offices, or places of business near the current location of the medical device (task 1012). Task 1012 functions to filter the set of stored advertisements such that the medical device can selectively present advertisements associated with local entities. As described previously in this section, the medical device can utilize the geographic position data to prepare and generate directions to advertiser facilities (task 1014).
The medical device can then present at least one advertisement, preferably using its native display element (task 1016). The advertisement could identify: a supplier, vendor, or seller of a consumable associated with the medical device; a supplier, seller, or provider of medical services; and/or a supplier, vendor, seller, or provider of goods or services associated with the treatment, management, or diagnosis of a medical condition. The advertisement might also indicate or recommend a quantity, number of units, volume, or amount of a consumable that might be required. The medical device may also provide directions to a facility associated with the displayed advertisement (task 1018), and take further action in connection with the rendering of the advertisement (task 1020). For example, process 1000 might initiate a transaction for a consumable, goods or services, or a product. Alternatively (or additionally), process 1000 might display an active link that can be used to initiate an electronic transaction, or display an HTML document, such as the web page of an advertiser. Process 1000 may also process user input at the medical device, where such user input filters or modifies transactions or recommendations made by the medical device.
A network-enabled medical device could also support a feature that allows it to log into a service provider's website or online store, access available consumables, related products, accessories, etc. In this regard, if the device has a native web browser application and internet connectivity, it could be used to complete web-based electronic transactions in a manner that is akin to placing an online order from the user's personal computer. In alternate embodiments, the user could use the medical device to initiate orders for consumables, accessories, or products in an “offline” manner. Such orders can be saved and queued by the medical device for subsequent processing at a time when the medical device has network connectivity. For example, some medical devices may be configured to link with a base station device that is located at the patient's home—the base station might be a network-enabled appliance. When the medical device establishes connectivity with the base station device, the queued orders can be processed and completed with the assistance of the base station device.
Device Learning
A medical device as described herein may be suitably configured to perform certain intelligent learning operations that enhance the overall user experience. For example, a medical device could be designed to detect and learn features and functions that are used or accessed most often (and, conversely, those features and functions that are rarely used or accessed), and modify the display menu structure in a way that makes it easier for the user to access and activate the common features. In this regard, common features and functions might be provided on a main/home menu screen or provided on a menu screen that is easy to navigate to. On the other hand, rarely used features and functions may be embedded deeper into the menu structure so that they do not interfere with or otherwise impede the routine operation of the device.
As another example, the device may gradually introduce advanced features and functions to the user only after it has detected a threshold amount of use or experience associated with the user. The device might use a simple timer and unlock, or provide tutorials for, new or advanced features only after the device has been in use for a predetermined amount of time, e.g., a month. Alternatively, the device could monitor actual use or delivery of therapy and introduce different or advanced features only after the device has been used to administer a certain amount of therapy. In this regard, an insulin infusion pump may gradually introduce more features to the user after it detects the activation of 20, 50, and 100 boluses. This type of gradual introduction ensures that the user is ready and experienced enough to learn new features.
A medical device may also be suitably configured to learn patient habits, usage patterns, or trends, and make adjustments or recommendations as appropriate. For example, if the device determines that a diabetic patient tends to experience high glucose levels an hour after each meal, then the device might suggest an extended bolus prior to the next meal. The extended bolus feature might be an advanced feature that remains hidden or locked by the medical device until it determines that the patient might benefit from that feature. Such hidden and intelligently deployable features can be utilized to make the medical device appear simple or complex in a customized manner to suit the needs and experience of the individual patient.
Device learning features may also consider physiological and/or other information associated with the patient. For example, the medical device could consider the age, weight, and sex of the patient and make adjustments or recommendations as appropriate. The medical device could also consider other medications being used by the patient for purposes of customization, recommendations, and the like.
Dual-Use Devices
As mentioned previously, one controller device could be configured to control two or more therapy delivery devices. In an insulin infusion system, for example, a single wireless controller device can control both a standard tube-based insulin pump and a compact patch pump, if so desired. In another embodiment, a single reconfigurable pump component could be designed to function in a manner akin to a standard tube-based insulin pump and, alternatively, as a patch pump. Such a dual-use pump could be realized by modifying a patch pump such that it can accommodate an optional infusion set. Thus, the dual-use pump could use an infusion set so that it can be held or carried by the patient (e.g., clipped onto a belt). In its patch pump mode of operation, the dual-use pump can be affixed directly to the patient's skin without using an infusion set.
An alternate version of a dual-use pump utilizes a patch pump component that is physically configured in a way that allows it to be “docked” with a standard tube-type pump assembly. A controller device for such dual-use pumps can be designed to control the different physical packages and/or the different modes of operation.
Voice Control and Communication
A medical device as described herein may also support a variety of voice control and communication features that enhance the user experience. For example, the device could be outfitted with a microphone that can be used for voice activated commands. Voice commands may be preprogrammed or customized by the user. If desired, the functions linked to voice commands could be encoded or disguised for secrecy and discretion. For example, rather than linking the saying “administer bolus” to a bolus delivery function, the device could allow the user to program any saying, such as “option three,” to an action.
A device may also be designed for voice response compatibility with the communication system or entertainment system of a vehicle. Such compatibility would enable a user to control the medical device while driving—the user would simply need to utter a voice command while the vehicle's system is active and linked to the medical device.
Communication of remote voice commands could also be supported. In this regard, a user of a remote controller device for a therapy delivery device could control the therapy delivery device by uttering a voice command into the controller device. Moreover, voice-over-IP could be used to communicate voice commands when a WLAN network has been detected.
Automatic Reporting
A medical device, such as an infusion pump, may be provided with a notification feature that is used for automatic reporting of status information. In one embodiment, the notification feature is implemented with a simple LED indicator on the housing of the device. This status light could be activated in a coded manner to convey status information. For example, a flashing state might indicate that the device is currently active (e.g., delivering therapy). A continuously lit state might represent a warning condition. Of course, a vast number of patterns, colors, combinations, and states could be utilized to convey different conditions, states, status, and information.
Alarms And Alerts
A medical device as described here may also support enhanced alarm and alerting features. For example, the device may include or communicate with directional or focused speakers that can be selectively activated such that audible alarms can be directed to specified locations rather than generally broadcast. For example, sound-focused emitters could be employed such that audible alarms and alerts are narrowly focused and directed to a specific point or location, while reducing the amount of sound that can be heard elsewhere.
A medical device may also implement adaptive or smart alarm algorithms that can be utilized to reduce the occurrence of nuisance alarms. For example, it might be desirable to temporarily increase the glucose level threshold (associated with a high glucose alarm) immediately following the delivery of a meal bolus, because patients tend to have a spike in glucose level after eating a meal.
Customized Skins
A medical device as described here may be suitably configured to allow the user to customize certain decorative or appearance features. For example, the device may support customizable display wallpapers, screen savers, avatars, and themes. As another option, the device could accept decorative and/or protective skins, cases, holders, covers, face plates, adhesive strips, or the like. Although these decorative features do not affect the functionality of the device, they add value by allowing the user to feel comfortable with his or her medical device, and they reflect a modern approach towards product design.
Predictive Charts
A medical device as described here may utilize predictive charting or graphing techniques that intelligently predict or estimate trends in physiological characteristic data based upon historic and/or empirical data. The predictive feature may be associated with a projected region or range of values corresponding to a future time or period of time. Such predictive data can be displayed on the display element of a therapy delivery device and/or its associated controller device. In practice, the predictive indicia could be rendered as a “layer” on an otherwise standard graphical representation of the physiological characteristic data. In certain embodiments, the predictive display feature can be toggled on and off as desired. This option allows the user to remove the predictive information to avoid confusion with actual or historical data.
While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the exemplary embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the claimed subject matter in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope defined by the claims, which includes known equivalents and foreseeable equivalents at the time of filing this patent application.
This application is a divisional of U.S. patent application Ser. No. 13/690,160 (filed on Nov. 30, 2012 and issued on Dec. 30, 2014 as U.S. Pat. No. 8,922,330), which is a divisional of U.S. patent application Ser. No. 12/500,272 (filed on Jul. 9, 2009 and issued on Jan. 1, 2013 as U.S. Pat. No. 8,344,847). Moreover, the subject matter of this application is related to the subject matter described in U.S. patent application Ser. No. 12/500,281 (filed on Jul. 9, 2009), U.S. patent application Ser. No. 12/500,283 (filed on Jul. 9, 2009), U.S. patent application Ser. No. 12/500,295 (filed on Jul. 9, 2009), U.S. patent application Ser. No. 12/500,313 (filed on Jul. 9, 2009), and U.S. patent application Ser. No. 12/500,317 (filed on Jul. 9, 2009).
| Number | Name | Date | Kind |
|---|---|---|---|
| 3631847 | Hobbs, II | Jan 1972 | A |
| 4212738 | Henne | Jul 1980 | A |
| 4270532 | Franetzki et al. | Jun 1981 | A |
| 4282872 | Franetzki et al. | Aug 1981 | A |
| 4373527 | Fischell | Feb 1983 | A |
| 4395259 | Prestele et al. | Jul 1983 | A |
| 4433072 | Pusineri et al. | Feb 1984 | A |
| 4443218 | DeCant, Jr. et al. | Apr 1984 | A |
| 4494950 | Fischell | Jan 1985 | A |
| 4542532 | McQuilkin | Sep 1985 | A |
| 4550731 | Batina et al. | Nov 1985 | A |
| 4559037 | Franetzki et al. | Dec 1985 | A |
| 4562751 | Nason et al. | Jan 1986 | A |
| 4671288 | Gough | Jun 1987 | A |
| 4678408 | Nason et al. | Jul 1987 | A |
| 4685903 | Cable et al. | Aug 1987 | A |
| 4731051 | Fischell | Mar 1988 | A |
| 4731726 | Allen, III | Mar 1988 | A |
| 4781798 | Gough | Nov 1988 | A |
| 4803625 | Fu et al. | Feb 1989 | A |
| 4809697 | Causey, III et al. | Mar 1989 | A |
| 4826810 | Aoki | May 1989 | A |
| 4871351 | Feingold | Oct 1989 | A |
| 4898578 | Rubalcaba, Jr. | Feb 1990 | A |
| 5003298 | Havel | Mar 1991 | A |
| 5011468 | Lundquist et al. | Apr 1991 | A |
| 5019974 | Beckers | May 1991 | A |
| 5050612 | Matsumura | Sep 1991 | A |
| 5078683 | Sancoff et al. | Jan 1992 | A |
| 5080653 | Voss et al. | Jan 1992 | A |
| 5097122 | Colman et al. | Mar 1992 | A |
| 5100380 | Epstein et al. | Mar 1992 | A |
| 5101814 | Palti | Apr 1992 | A |
| 5108819 | Heller et al. | Apr 1992 | A |
| 5153827 | Coutre et al. | Oct 1992 | A |
| 5165407 | Wilson et al. | Nov 1992 | A |
| 5247434 | Peterson et al. | Sep 1993 | A |
| 5262035 | Gregg et al. | Nov 1993 | A |
| 5262305 | Heller et al. | Nov 1993 | A |
| 5264104 | Gregg et al. | Nov 1993 | A |
| 5264105 | Gregg et al. | Nov 1993 | A |
| 5284140 | Allen et al. | Feb 1994 | A |
| 5299571 | Mastrototaro | Apr 1994 | A |
| 5307263 | Brown | Apr 1994 | A |
| 5317506 | Coutre et al. | May 1994 | A |
| 5320725 | Gregg et al. | Jun 1994 | A |
| 5322063 | Allen et al. | Jun 1994 | A |
| 5338157 | Blomquist | Aug 1994 | A |
| 5339821 | Fujimoto | Aug 1994 | A |
| 5341291 | Roizen et al. | Aug 1994 | A |
| 5350411 | Ryan et al. | Sep 1994 | A |
| 5354319 | Wyborny et al. | Oct 1994 | A |
| 5356786 | Heller et al. | Oct 1994 | A |
| 5357427 | Langen et al. | Oct 1994 | A |
| 5368562 | Blomquist et al. | Nov 1994 | A |
| 5370622 | Livingston et al. | Dec 1994 | A |
| 5371687 | Holmes, II et al. | Dec 1994 | A |
| 5376070 | Purvis et al. | Dec 1994 | A |
| 5390671 | Lord et al. | Feb 1995 | A |
| 5391250 | Cheney, II et al. | Feb 1995 | A |
| 5398021 | Moore | Mar 1995 | A |
| 5403700 | Heller et al. | Apr 1995 | A |
| 5411647 | Johnson et al. | May 1995 | A |
| 5482473 | Lord et al. | Jan 1996 | A |
| 5485408 | Blomquist | Jan 1996 | A |
| 5497772 | Schulman et al. | Mar 1996 | A |
| 5505709 | Funderburk et al. | Apr 1996 | A |
| 5543326 | Heller et al. | Aug 1996 | A |
| 5569186 | Lord et al. | Oct 1996 | A |
| 5569187 | Kaiser | Oct 1996 | A |
| 5573506 | Vasko | Nov 1996 | A |
| 5582593 | Hultman | Dec 1996 | A |
| 5586553 | Halili et al. | Dec 1996 | A |
| 5593390 | Castellano et al. | Jan 1997 | A |
| 5593852 | Heller et al. | Jan 1997 | A |
| 5594638 | Illiff | Jan 1997 | A |
| 5609060 | Dent | Mar 1997 | A |
| 5626144 | Tacklind et al. | May 1997 | A |
| 5627549 | Park | May 1997 | A |
| 5630710 | Tune et al. | May 1997 | A |
| 5643212 | Coutre et al. | Jul 1997 | A |
| 5660163 | Schulman et al. | Aug 1997 | A |
| 5660176 | Iliff | Aug 1997 | A |
| 5665065 | Colman et al. | Sep 1997 | A |
| 5665222 | Heller et al. | Sep 1997 | A |
| 5685844 | Marttila | Nov 1997 | A |
| 5687734 | Dempsey et al. | Nov 1997 | A |
| 5704366 | Tacklind et al. | Jan 1998 | A |
| 5750926 | Schulman et al. | May 1998 | A |
| 5754111 | Garcia | May 1998 | A |
| 5764159 | Neftel | Jun 1998 | A |
| 5772635 | Dastur et al. | Jun 1998 | A |
| 5779665 | Mastrototaro et al. | Jul 1998 | A |
| 5788669 | Peterson | Aug 1998 | A |
| 5791344 | Schulman et al. | Aug 1998 | A |
| 5800420 | Gross et al. | Sep 1998 | A |
| 5807336 | Russo et al. | Sep 1998 | A |
| 5814015 | Gargano et al. | Sep 1998 | A |
| 5822715 | Worthington et al. | Oct 1998 | A |
| 5832448 | Brown | Nov 1998 | A |
| 5840020 | Heinonen et al. | Nov 1998 | A |
| 5861018 | Feierbach et al. | Jan 1999 | A |
| 5868669 | Iliff | Feb 1999 | A |
| 5871465 | Vasko | Feb 1999 | A |
| 5879163 | Brown et al. | Mar 1999 | A |
| 5885245 | Lynch et al. | Mar 1999 | A |
| 5897493 | Brown | Apr 1999 | A |
| 5899855 | Brown | May 1999 | A |
| 5904708 | Goedeke | May 1999 | A |
| 5913310 | Brown | Jun 1999 | A |
| 5917346 | Gord | Jun 1999 | A |
| 5918603 | Brown | Jul 1999 | A |
| 5925021 | Castellano et al. | Jul 1999 | A |
| 5933136 | Brown | Aug 1999 | A |
| 5935099 | Peterson et al. | Aug 1999 | A |
| 5940801 | Brown | Aug 1999 | A |
| 5948061 | Merriman et al. | Sep 1999 | A |
| 5956501 | Brown | Sep 1999 | A |
| 5960403 | Brown | Sep 1999 | A |
| 5965380 | Heller et al. | Oct 1999 | A |
| 5972199 | Heller et al. | Oct 1999 | A |
| 5978236 | Faberman et al. | Nov 1999 | A |
| 5997476 | Brown | Dec 1999 | A |
| 5999848 | Gord et al. | Dec 1999 | A |
| 5999849 | Gord et al. | Dec 1999 | A |
| 6009339 | Bentsen et al. | Dec 1999 | A |
| 6032119 | Brown et al. | Feb 2000 | A |
| 6043437 | Schulman et al. | Mar 2000 | A |
| 6081736 | Colvin et al. | Jun 2000 | A |
| 6083710 | Heller et al. | Jul 2000 | A |
| 6088608 | Schulman et al. | Jul 2000 | A |
| 6101478 | Brown | Aug 2000 | A |
| 6103033 | Say et al. | Aug 2000 | A |
| 6119028 | Schulman et al. | Sep 2000 | A |
| 6120676 | Heller et al. | Sep 2000 | A |
| 6121009 | Heller et al. | Sep 2000 | A |
| 6127931 | Mohr | Oct 2000 | A |
| 6134461 | Say et al. | Oct 2000 | A |
| 6143164 | Heller et al. | Nov 2000 | A |
| 6162611 | Heller et al. | Dec 2000 | A |
| 6175752 | Say et al. | Jan 2001 | B1 |
| 6183412 | Benkowski et al. | Feb 2001 | B1 |
| 6246992 | Brown | Jun 2001 | B1 |
| 6259937 | Schulman et al. | Jul 2001 | B1 |
| 6329161 | Heller et al. | Dec 2001 | B1 |
| 6408330 | DeLaHuerga | Jun 2002 | B1 |
| 6424847 | Mastrototaro et al. | Jul 2002 | B1 |
| 6472122 | Schulman et al. | Oct 2002 | B1 |
| 6484045 | Holker et al. | Nov 2002 | B1 |
| 6484046 | Say et al. | Nov 2002 | B1 |
| 6503381 | Gotoh et al. | Jan 2003 | B1 |
| 6514718 | Heller et al. | Feb 2003 | B2 |
| 6544173 | West et al. | Apr 2003 | B2 |
| 6553263 | Meadows et al. | Apr 2003 | B1 |
| 6554798 | Mann et al. | Apr 2003 | B1 |
| 6558320 | Causey, III et al. | May 2003 | B1 |
| 6558351 | Steil et al. | May 2003 | B1 |
| 6560741 | Gerety et al. | May 2003 | B1 |
| 6565509 | Say et al. | May 2003 | B1 |
| 6579690 | Bonnecaze et al. | Jun 2003 | B1 |
| 6591125 | Buse et al. | Jul 2003 | B1 |
| 6592745 | Feldman et al. | Jul 2003 | B1 |
| 6605200 | Mao et al. | Aug 2003 | B1 |
| 6605201 | Mao et al. | Aug 2003 | B1 |
| 6607658 | Heller et al. | Aug 2003 | B1 |
| 6616819 | Liamos et al. | Sep 2003 | B1 |
| 6618934 | Feldman et al. | Sep 2003 | B1 |
| 6623501 | Heller et al. | Sep 2003 | B2 |
| 6641533 | Causey, III et al. | Nov 2003 | B2 |
| 6654625 | Say et al. | Nov 2003 | B1 |
| 6659980 | Moberg et al. | Dec 2003 | B2 |
| 6671554 | Gibson et al. | Dec 2003 | B2 |
| 6676816 | Mao et al. | Jan 2004 | B2 |
| 6689265 | Heller et al. | Feb 2004 | B2 |
| 6714132 | Edwards et al. | Mar 2004 | B2 |
| 6728576 | Thompson et al. | Apr 2004 | B2 |
| 6733471 | Ericson et al. | May 2004 | B1 |
| 6746582 | Heller et al. | Jun 2004 | B2 |
| 6747556 | Medema et al. | Jun 2004 | B2 |
| 6749740 | Liamos et al. | Jun 2004 | B2 |
| 6752787 | Causey, III et al. | Jun 2004 | B1 |
| 6790198 | White et al. | Sep 2004 | B1 |
| 6809653 | Mann et al. | Oct 2004 | B1 |
| 6881551 | Heller et al. | Apr 2005 | B2 |
| 6892085 | McIvor et al. | May 2005 | B2 |
| 6893545 | Gotoh et al. | May 2005 | B2 |
| 6895263 | Shin et al. | May 2005 | B2 |
| 6916159 | Rush et al. | Jul 2005 | B2 |
| 6932584 | Gray et al. | Aug 2005 | B2 |
| 6932894 | Mao et al. | Aug 2005 | B2 |
| 6942518 | Liamos et al. | Sep 2005 | B2 |
| 7153263 | Carter et al. | Dec 2006 | B2 |
| 7153289 | Vasko | Dec 2006 | B2 |
| 7225030 | Kroll | May 2007 | B2 |
| 7324843 | Pronk | Jan 2008 | B2 |
| 7396330 | Banet et al. | Jul 2008 | B2 |
| 7813958 | Urbanski et al. | Oct 2010 | B1 |
| 7986802 | Ziller | Jul 2011 | B2 |
| 8009014 | Eberhart | Aug 2011 | B2 |
| 8073008 | Mehta | Dec 2011 | B2 |
| 8344847 | Moberg | Jan 2013 | B2 |
| 8509910 | Sowder | Aug 2013 | B2 |
| 8922330 | Moberg | Dec 2014 | B2 |
| 20010044731 | Coffman et al. | Nov 2001 | A1 |
| 20020013518 | West et al. | Jan 2002 | A1 |
| 20020055857 | Mault et al. | May 2002 | A1 |
| 20020082665 | Haller et al. | Jun 2002 | A1 |
| 20020137997 | Mastrototaro et al. | Sep 2002 | A1 |
| 20020161288 | Shin et al. | Oct 2002 | A1 |
| 20030060765 | Campbell et al. | Mar 2003 | A1 |
| 20030078560 | Miller et al. | Apr 2003 | A1 |
| 20030088166 | Say et al. | May 2003 | A1 |
| 20030144581 | Conn et al. | Jul 2003 | A1 |
| 20030152823 | Heller | Aug 2003 | A1 |
| 20030176183 | Drucker et al. | Sep 2003 | A1 |
| 20030188427 | Say et al. | Oct 2003 | A1 |
| 20030199744 | Buse et al. | Oct 2003 | A1 |
| 20030208113 | Mault et al. | Nov 2003 | A1 |
| 20030220552 | Reghabi et al. | Nov 2003 | A1 |
| 20040039659 | Niwa | Feb 2004 | A1 |
| 20040061232 | Shah et al. | Apr 2004 | A1 |
| 20040061234 | Shah et al. | Apr 2004 | A1 |
| 20040064133 | Miller et al. | Apr 2004 | A1 |
| 20040064156 | Shah et al. | Apr 2004 | A1 |
| 20040073095 | Causey, III et al. | Apr 2004 | A1 |
| 20040074785 | Holker et al. | Apr 2004 | A1 |
| 20040093167 | Braig et al. | May 2004 | A1 |
| 20040097796 | Berman et al. | May 2004 | A1 |
| 20040102683 | Khanuja et al. | May 2004 | A1 |
| 20040111017 | Say et al. | Jun 2004 | A1 |
| 20040122353 | Shahmirian et al. | Jun 2004 | A1 |
| 20040167465 | Mihai et al. | Aug 2004 | A1 |
| 20040225203 | Jemison et al. | Nov 2004 | A1 |
| 20040263354 | Mann et al. | Dec 2004 | A1 |
| 20050038331 | Silaski et al. | Feb 2005 | A1 |
| 20050038680 | McMahon et al. | Feb 2005 | A1 |
| 20050154271 | Rasdal et al. | Jul 2005 | A1 |
| 20050192557 | Brauker et al. | Sep 2005 | A1 |
| 20060197653 | Kung et al. | Sep 2006 | A1 |
| 20060229694 | Schulman et al. | Oct 2006 | A1 |
| 20060238333 | Welch et al. | Oct 2006 | A1 |
| 20060293571 | Bao et al. | Dec 2006 | A1 |
| 20070060869 | Tolle et al. | Mar 2007 | A1 |
| 20070088521 | Shmueli et al. | Apr 2007 | A1 |
| 20070109117 | Heitzmann et al. | May 2007 | A1 |
| 20070135866 | Baker et al. | Jun 2007 | A1 |
| 20070213657 | Jennewine et al. | Sep 2007 | A1 |
| 20070239229 | Masoud et al. | Oct 2007 | A1 |
| 20070251835 | Mehta et al. | Nov 2007 | A1 |
| 20070254593 | Jollota et al. | Nov 2007 | A1 |
| 20080021504 | McCabe et al. | Jan 2008 | A1 |
| 20080120140 | Sirohey et al. | May 2008 | A1 |
| 20080154503 | Wittenber et al. | Jun 2008 | A1 |
| 20090081951 | Erdmann et al. | Mar 2009 | A1 |
| 20090082635 | Baldus et al. | Mar 2009 | A1 |
| 20090216100 | Ebner et al. | Aug 2009 | A1 |
| Number | Date | Country |
|---|---|---|
| 4329229 | Mar 1995 | DE |
| 0319268 | Nov 1988 | EP |
| 0806738 | Nov 1997 | EP |
| 0880936 | Dec 1998 | EP |
| 1338295 | Aug 2003 | EP |
| 1631036 | Mar 2006 | EP |
| 2218831 | Nov 1989 | GB |
| WO 9620745 | Jul 1996 | WO |
| WO 9636389 | Nov 1996 | WO |
| WO 9637246 | Nov 1996 | WO |
| WO 9721456 | Jun 1997 | WO |
| WO 9820439 | May 1998 | WO |
| WO 9824358 | Jun 1998 | WO |
| WO 9842407 | Oct 1998 | WO |
| WO 9849659 | Nov 1998 | WO |
| WO 9859487 | Dec 1998 | WO |
| WO 9908183 | Feb 1999 | WO |
| WO 9910801 | Mar 1999 | WO |
| WO 9918532 | Apr 1999 | WO |
| WO 9922236 | May 1999 | WO |
| WO 0010628 | Mar 2000 | WO |
| WO 0019887 | Apr 2000 | WO |
| WO 0048112 | Aug 2000 | WO |
| WO 02058537 | Aug 2002 | WO |
| PCTUS0203299 | Oct 2002 | WO |
| WO 03001329 | Jan 2003 | WO |
| WO 03094090 | Nov 2003 | WO |
| WO 2005065538 | Jul 2005 | WO |
| Entry |
|---|
| (Animas Corporation, 1999). Animas . . . bringing new life to insulin therapy. |
| Bode B W, et al. (1996). Reduction in Severe Hypoglycemia with Long-Term Continuous Subcutaneous Insulin Infusion in Type I Diabetes. Diabetes Care, vol. 19, No. 4, 324-327. |
| Boland E (1998). Teens Pumping it Up! Insulin Pump Therapy Guide for Adolescents. 2nd Edition. |
| Brackenridge B P (1992). Carbohydrate Gram Counting A Key to Accurate Mealtime Boluses in Intensive Diabetes Therapy. Practical Diabetology, vol. 11, No. 2, pp. 22-28. |
| Brackenridge, B Pet al. (1995). Counting Carbohydrates How to Zero in on Good Control. MiniMed Technologies Inc. |
| Farkas-Hirsch R et al. (1994). Continuous Subcutaneous Insulin Infusion: A Review of the Past and Its Implementation for the Future. Diabetes Spectrum From Research to Practice, vol. 7, No. 2, pp. 80-84, 136-138. |
| Hirsch I B et al. (1990). Intensive Insulin Therapy for Treatment of Type I Diabetes. Diabetes Care, vol. 13, No. 12, pp. 1265-1283. |
| Kulkarni K et al. (1999). Carbohydrate Counting A Primer for Insulin Pump Users to Zero in on Good Control. MiniMed Inc. |
| Marcus A O et al. (1996). Insulin Pump Therapy Acceptable Alternative to Injection Therapy. Postgraduate Medicine, vol. 99, No. 3, pp. 125-142. |
| Reed J et al. (1996). Voice of the Diabetic, vol. 11, No. 3, pp. 1-38. |
| Skyler J S (1989). Continuous Subcutaneous Insulin Infusion [CSII] With External Devices: Current Status. Update in Drug Delivery Systems, Chapter 13, pp. 163-183. Futura Publishing Company. |
| Skyler J S et al. (1995). The Insulin Pump Therapy Book Insights from the Experts. MiniMed•Technologies. |
| Strowig S M (1993). Initiation and Management of Insulin Pump Therapy. The Diabetes Educator, vol. 19, No. 1, pp. 50-60. |
| Walsh J, et al. (1989). Pumping Insulin: The Art of Using an Insulin Pump. Published by MiniMed•Technologies. |
| (Intensive Diabetes Management, 1995). Insulin Infusion Pump Therapy. pp. 66-78. |
| (MiniMed, 1996). The MiniMed 506. 7 pages. Retrieved on Sep. 16, 2003 from the World Wide Web: http://web.archive.org/web/19961111054527/www.minimed.com/files/506—pic.htm. |
| (MiniMed, 1997). MiniMed 507 Specifications. 2 pages. Retrieved on Sep. 16, 2003 from the World Wide Web: http://web.archive.org/web/19970124234841/www.minimed.com/files/mmn075.htm. |
| (MiniMed, 1996). FAQ: The Practical Things . . . pp. 1-4. Retrieved on Sep. 16, 2003 from the World Wide Web: http://web.archive.org/web/19961111054546/www.minimed.com/files/faq—pract.htm. |
| (MiniMed, 1997). Wanted: a Few Good Belt Clips! 1 page. Retrieved on Sep. 16, 2003 from the World Wide Web: http://web.archive.org/web/19970124234559/www.minimed.com/files/mmn002.htm. |
| (MiniMed Technologies, 1994). MiniMed 506 Insulin Pump User's Guide. |
| (MiniMed Technologies, 1994). MiniMed™ Dosage Calculator Initial Meal Bolus Guidelines / MiniMed™ Dosage Calculator Initial Basal Rate Guidelines Percentage Method. 4 pages. |
| (MiniMed, 1996). MiniMed™ 507 Insulin Pump User's Guide. |
| (MiniMed, 1997). MiniMed™ 507 Insulin Pump User's Guide. |
| (MiniMed, 1998). MiniMed 507C Insulin Pump User's Guide. |
| (MiniMed International, 1998). MiniMed 507C Insulin Pump for those who appreciate the difference. |
| (MiniMed Inc., 1999). MiniMed 508 Flipchart Guide to Insulin Pump Therapy. |
| (MiniMed Inc., 1999). Insulin Pump Comparison / Pump Therapy Will Change Your Life. |
| (MiniMed, 2000). MiniMed® 508 User's Guide. |
| (MiniMed Inc., 2000). MiniMed® Now [I] Can Meal Bolus Calculator / MiniMed® Now [I] Can Correction Bolus Calculator. |
| (MiniMed Inc., 2000). Now [I] Can MiniMed Pump Therapy. |
| (MiniMed Inc., 2000). Now [I] Can MiniMed Diabetes Management. |
| (Medtronic MiniMed, 2002). The 508 Insulin Pump a Tradition of Excellence. |
| (Medtronic MiniMed, 2002). Medtronic MiniMed Meal Bolus Calculator and Correction Bolus Calculator. International Version. |
| Abel, P., et al., “Experience with an implantable glucose sensor as a prerequiste of an artificial beta cell,” Biomed. Biochim. Acta 43 (1984) 5, pp. 577-584. |
| Bindra, Dilbir S., et al., “Design and in Vitro Studies of a Needle-Type Glucose Sensor for a Subcutaneous Monitoring,” American Chemistry Society, 1991, 63, pp. 1692-1696. |
| Boguslavsky, Leonid, et al., “Applications of redox polymers in biosensors,” Sold State Ionics 60, 1993, pp. 189-197. |
| Geise, Robert J., et al., “Electropolymerized 1,3-diaminobenzene for the construction of a 1,1′-dimethylferrocene mediated glucose biosensor,” Analytica Chimica Acta, 281, 1993, pp. 467-473. |
| Gernet, S., et al., “A Planar Glucose Enzyme Electrode,” Sensors and Actuators, 17, 1989, pp. 537-540. |
| Gernet, S., et al., “Fabrication and Characterization of a Planar Electromechanical Cell and its Application as a Glucose Sensor,” Sensors and Actuators, 18, 1989, pp. 59-70. |
| Gorton, L., et al., “Amperometric Biosensors Based on an Apparent Direct Electron Transfer Between Electrodes and Immobilized Peroxiases,” Analyst, Aug. 1991, vol. 117, pp. 1235-1241. |
| Gorton, L., et al., “Amperometric Glucose Sensors Based on Immobilized Glucose-Oxidizing Enymes and Chemically Modified Electrodes,” Analytica Chinnica Acta, 249, 1991, pp. 43-54. |
| Gough, D. A., et al., “Two-Dimensional Enzyme Electrode Sensor for Glucose,” Analytical Chemistry, vol. 57, No. 5, 1985, pp. 2351-2357. |
| Gregg, Brian A., et al., “Redox Polymer Films Containing Enzymes. 1. A Redox-Conducting Epoxy Cement: Synthesis, Characterization, and Electrocatalytic Oxidation of Hydroquinone,” The Journal of Physical Chemistry, vol. 95, No. 15, 1991, pp. 5970-5975. |
| Hashiguch I, Yasuhiro, MD, et al., “Development of a Miniaturized Glucose Monitoring System by Combining a Needle-Type Glucose Sensor With Microdialysis Sampling Method,” Diabetes Care, vol. 17, No. 5, May 1994, pp. 387-389. |
| Heller, Adam, “Electrical Wiring of Redox Enzymes,” Acc. Chem. Res., vol. 23, No. 5, May 1990, pp. 128-134. |
| Jobst, Gerhard, et al., “Thin-Film Microbiosensors for Glucose-Lactate Monitoring,” Analytical Chemistry, vol. 68, No. 18, Sep. 15, 1996, pp. 3173-3179. |
| Johnson, K.W., et al., “In vivo evaluation of an electroenzymatic glucose sensor implanted in subcutaneous tissue,” Biosensors & Bioelectronics, 7, 1992, pp. 709-714. |
| Jönsson, G., et al., “An Electromechanical Sensor for Hydrogen Peroxide Based on Peroxidase Adsorbed on a Spectrographic Graphite Electrode,” Electroanalysis, 1989, pp. 465-468. |
| Kanapieniene, J. J., et al., “Miniature Glucose Biosensor with Extended Linearity,” Sensors and Actuators, B. 10, 1992, pp. 37-40. |
| Kawamori, Ryuzo, et al., “Perfect Normalization of Excessive Glucagon Responses to Intraveneous Arginine in Human Diabetes Mellitus With the Artificial Beta-Cell,” Diabetes vol. 29, Sep. 1980, pp. 762-765. |
| Kimura, J., et al., “An Immobilized Enzyme Membrane Fabrication Method,” Biosensors 4, 1988, pp. 41-52. |
| Koudelka, M., et al., “In-vivo Behaviour of Hypodermically Implanted Microfabricated Glucose Sensors,” Biosensors & Bioelectronics 6, 1991, pp. 31-36. |
| Koudelka, M., et al., “Planar Amperometric Enzyme-Based Glucose Microelectrode,” Sensors & Actuators, 18, 1989, pp. 157-165. |
| Mastrototaro, John J., et al, “An electroenzymatic glucose sensor fabricated on a flexible substrate,” Sensors & Actuators, B. 5, 1991, pp. 139-144. |
| Mastrototaro, John J., et al., “An Electroenzymatic Sensor Capable of 72 Hour Continuous Monitoring of Subcutaneous Glucose,” 14th Annual International Diabetes Federation Congress, Washington D.C., Jun. 23-28, 1991. |
| McKean, Brian D., et al., “A Telemetry-Instrumentation System for Chronically Implanted Glucose and Oxygen Sensors,” IEEE Transactions on Biomedical Engineering, Vo. 35, No. 7, Jul. 1988, pp. 526-532. |
| Monroe, D., “Novel Implantable Glucose Sensors,” ACL, Dec. 1989, pp. 8-16. |
| Morff, Robert J., et al., “Microfabrication of Reproducible, Economical, Electroenzymatic Glucose Sensors,” Annuaal International Conference of teh IEEE Engineering in Medicine and Biology Society, Vo. 12, No. 2, 1990, pp. 483-484. |
| Moussy, Francis, et al., “Performance of Subcutaneously Implanted Needle-Type Glucose Sensors Employing a Novel Trilayer Coating,” Analytical Chemistry, vol. 65, No. 15, Aug. 1, 1993, pp. 2072-2077. |
| Nakamoto, S., et al., “A Lift-Off Method for Patterning Enzyme-Immobilized Membranes in Multi-Biosensors,” Sensors and Actuators 13, 1988, pp. 165-172. |
| Nishida, Kenro, et al., “Clinical applications of teh wearable artifical endocrine pancreas with the newly designed needle-type glucose sensor,” Elsevier Sciences B.V., 1994, pp. 353-358. |
| Nishida, Kenro, et al., “Development of a ferrocene-mediated needle-type glucose sensor covereed with newly designd biocompatible membrane, 2-methacryloyloxyethylphosphorylcholine -co-n-butyl nethacrylate,” Medical Progress Through Technology, vol. 21, 1995, pp. 91-103. |
| Poitout, V., et al., “A glucose monitoring system for on line estimation oin man of blood glucose concentration using a miniaturized glucose sensor implanted in the subcutaneous tissue adn a wearable control unit,” Diabetologia, vol. 36, 1991, pp. 658-663. |
| Reach, G., “A Method for Evaluating in vivo the Functional Characteristics of Glucose Sensors,” Biosensors 2, 1986, pp. 211-220. |
| Shaw, G. W., et al., “In vitro testing of a simply constructed, highly stable glucose sensor suitable for implantation in diabetic patients,” Biosensors & Bioelectronics 6, 1991, pp. 401-406. |
| Shichiri, M., “A Needle-Type Glucose Sensor—A Valuable Tool Not Only for a Self-Blood Glucose Monitoring but for a Wearable Artificial Pancreas,” Life Support Systems Proceedings, XI Annual Meeting ESAO, Alpbach-Innsbruck, Austria, Sep. 1984, pp. 7-9. |
| Shichiri, Motoaki, et al., “An artificial endocrine pancreas—problems awaiting solution for long-term clinical applications of a glucose sensor,” Frontiers Med. Biol. Engng., 1991, vol. 3, No. 4, pp. 283-292. |
| Shichiri, Motoaki, et al., “Closed-Loop Glycemic Control with a Wearable Artificial Endocrine Pancreas—Variations in Daily Insulin Requirements to Glycemic Response,” Diabetes, vol. 33, Dec. 1984, pp. 1200-1202. |
| Shichiri, Motoaki, et al., “Glycaemic Control in a Pacreatectomized Dogs with a Wearable Artificial Endocrine Pancreas,” Diabetologia, vol. 24, 1983, pp. 179-184. |
| Shichiri, M., et al., “In Vivo Characteristics of Needle-Type Glucose Sensor—Measurements of Subcutaneous Glucose Concentrations in Human Volunteers,” Hormone and Metabolic Research, Supplement Series vol. No. 20, 1988, pp. 17-20. |
| Shichiri, M., et al., “Membrane design for extending the long-life of an implantable glucose sensor,” Diab. Nutr. Metab., vol. 2, No. 4, 1989, pp. 309-313. |
| Shichiri, Motoaki, et al., “Normalization of the Paradoxic Secretion of Glucagon in Diabetes Who Were Controlled by the Artificial Beta Cell,” Diabetes, vol. 28, Apr. 1979, pp. 272-275. |
| Shichiri, Motoaki, et al., “Telemetry Glucose Monitoring Device with Needle-Type Glucose Sensor: A useful Tool for Blood Glucose Monitoring in Diabetic Individuals,” Diabetes Care, vol. 9, No. 3, May-Jun. 1986, pp. 298-301. |
| Shichiri, Motoaki, et al., “Wearable Artificial Endocrine Pancreas with Needle-Type Glucose Sensor,” The Lancet, Nov. 20, 1982, pp. 1129-1131. |
| Shichiri, Motoaki, et al., “The Wearable Artificial Endocrine Pancreas with a Needle-Type Glucose Sensor: Perfect Glycemic Control in Ambulatory Diabetes,” Acta Paediatr Jpn 1984, vol. 26, pp. 359-370. |
| Shinkai, Seiji, “Molecular Recognitiion of Mono- and Di-saccharides by Phenylboronic Acids in Solvent Extraction and as a Monolayer,” J. Chem. Soc., Chem. Commun., 1991, pp. 1039-1041. |
| Shults, Mark C., “A Telemetry-Instrumentation System for Monitoring Multiple Subcutaneously Implanted Glucose Sensors,” IEEE Transactions on Biomedical Engineering, vol. 41, No. 10, Oct. 1994, pp. 937-942. |
| Sternberg, Robert, et al., “Study and Development of Multilayer Needle-type Enzyme-based Glucose Microsensors,” Biosensors, vol. 4, 1988, pp. 27-40. |
| Tamiya, E., et al., “Micro Glucose Sensors using Electron Mediators Immobilized on a Polypyrrole-Modified Electrode,” Sensors and Actuators, vol. 18, 1989, pp. 297-307. |
| Tsukagoshi, Kazuhiko, et al., “Specific Complexation with Mono- and Disaccharides that can be Detected by Circular Dichroism,” J. Org. Chem., vol. 56, 1991, pp. 4089-4091. |
| Urban, G., et al., “Miniaturized multi-enzyme biosensors integrated with pH sensors on flexible polymer carriers for in vivo applciations,” Biosensors & Bioelectronics, vol. 7, 1992, pp. 733-739. |
| Ubran, G., et al., “Miniaturized thin-film biosensors using covalently immobilized glucose oxidase,” Biosensors & Bioelectronics, vol. 6, 1991, pp. 555-562. |
| Velho, G., et al., “In vivo calibration of a subcutaneous glucose sensor for determination of subcutaneous glucose kinetics,” Diab. Nutr. Metab., vol. 3, 1988, pp. 227-233. |
| Wang, Joseph, et al., “Needle-Type Dual Microsensor for the Simultaneous Monitoring of Glucose and Insulin,” Analytical Chemistry, vol. 73, 2001, pp. 844-847. |
| Yamasaki, Yoshimitsu, et al., “Direct Measurement of Whole Blood Glucose by a Needle-Type Sensor,” Clinics Chimica Acta, vol. 93, 1989, pp. 93-98. |
| Yokoyama, K., “Integrated Biosensor for Glucose and Galactose,” Analytica Chimica Acta, vol. 218, 1989, pp. 137-142. |
| Number | Date | Country | |
|---|---|---|---|
| 20150073393 A1 | Mar 2015 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 13690160 | Nov 2012 | US |
| Child | 14537765 | US | |
| Parent | 12500272 | Jul 2009 | US |
| Child | 13690160 | US |
