FIELD OF THE INVENTION
The present invention relates generally to the field of wireless connectivity of medical devices. More specifically, the present invention relates to methods, apparatus and systems for wireless medical device communication, control and localization.
BACKGROUND
Medical devices operate for therapeutic and/or diagnostic uses such as peristaltic pumps which may be used to infuse medicines into a vein, blood pressure monitors which may monitor a patient's blood pressure and heart rate, electrical thermometers which may measure a patient's body temperature and many more.
A medical device may be used in a hospital, doctor or nurse's office or other medical treatment centers. Medical devices may also be used at patient's homes or personal environments.
Medical devices may be sought for example if they are misplaced, lost, for inventory purposes, when the medical device needs to be updated and more.
SUMMARY OF THE INVENTION
The present invention includes methods, apparatus and systems for medical device communication, control and localization. According to some embodiments of the present invention, there may be provided a medical device including a controller adapted to facilitate intermittent transitions of the device from a sleep mode into a scan mode during which scan mode a transceiver of the medical device is at least partially activated. During scan mode the controller may cause the transceiver to: (1) wirelessly transmit/broadcast its own identifier, (2) listen for wireless packets addressed to the transceiver identifier, and (3) wirelessly connect to and check a registry of a computing platform. According to further embodiments the controller may monitor the transceiver output for an activation event. In the absence of an activation event, the controller may deactivate the transceiver transition to sleep mode for some period of time before initiating another scan mode. In the presence of an activation event, the controller may activate additional portions of the medical device. Depending upon the specific nature of the activation event, the controller may activate: (1) a beacon and/or (2) a signal of the medical device
According to some embodiments, a computing platform may include a wireless transceiver and may scan for one or more medical devices. Upon detection of the medical devices the computing platform may: (1) Identify/Receive a location of the medical device (2) control the medical device or cause the medical device to emit a beacon (3) facilitate wireless update of the medical device (update firmware, update operational modes, update drug libraries and more) and/or (4) facilitate wireless coordination between multiple medical devices.
According to some embodiments the computing platform may be a second medical device, one or more hot spots associated with a server or central management control computer, a moving hot spot or a hand held/mobile device.
BRIEF DESCRIPTION OF THE DRAWINGS
The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:
FIG. 1A-1E are flowcharts including the exemplary steps associated with which may be performed by exemplary medical devices according to the present invention;
FIG. 2 is a functional block diagram of an exemplary medical device communication, control and localization apparatus according to embodiments of the present invention;
FIG. 3 is a functional block diagram of an exemplary computing platform operable to seek for a medical device according to embodiments of the present invention;
FIG. 4A-4E are schematic illustrations, depicting exemplary medical device communication, control and localization systems according to embodiments of the present invention;
FIG. 5A-5C are flow charts including the exemplary steps associated with which may be performed by the exemplary medical devices and/or the medical device communication, control and localization system of FIGS. 2 and 3; and
FIG. 6 is a flow chart including exemplary steps which may be executed by a transceiver and a therapeutic component according to embodiments of the present invention.
It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.
DETAILED DESCRIPTION
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, components and circuits have not been described in detail so as not to obscure the present invention.
Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that throughout the specification discussions utilizing terms such as “processing”, “computing”, “calculating”, “determining”, or the like, refer to the action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.
Embodiments of the present invention may include apparatus for performing the operations herein. This apparatus may be specially constructed for the desired purposes, or it may comprise a general purpose computer selectively activated or reconfigured by a computer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, any type of disk including floppy disks, optical disks, CD-ROMs, magnetic-optical disks, read-only memories (ROMs), random access memories (RAMs) electrically programmable read-only memories (EPROMs), electrically erasable and programmable read only memories (EEPROMs), magnetic or optical cards, or any other type of media suitable for storing electronic instructions, and capable of being coupled to a computer system bus.
A medical device communication system may perform or aid in localizing, monitoring, controlling, updating one or more medical device as well as coordinating between two or more medical devices.
According to some embodiments, medical devices may be dispersed across a healthcare facility or may be located remotely such as offsite, at a patient residence or otherwise. Localizing, estimating coordinates or location of a medical device may be advantageous when a device is being sought. Localizing a medical device may further trigger a beacon on a device being sought, further assisting in finding the device. For example, a medical device being sought within a ward of a hospital may be localized and a beacon triggered on the device may assist in finding the device even when it is in a closet or out of sight.
According to some embodiments, a medical device communication system may maintain accurate monitoring of one or more medical devices dispersed across a healthcare facility and/or located remotely (such as offsite, at a patient residence and more). Accurate monitoring may aid in managing medical device inventory and improve attrition rates stemming from lost or misplaced medical devices.
According to some embodiments, a medical device communication system may enable wireless control of one or more medical devices dispersed across a healthcare facility and/or located remotely. Wireless control of a medical device may enable administering treatment remotely.
According to some embodiments, a medical device communication system may facilitate updating of medical devices dispersed across a healthcare facility and/or located remotely. Update of medical devices may include: firmware, operation modes or regimes and update of drug libraries associated with a medical device and more. Update of medical devices may be improved by a wireless update, thus removing the need to physically reach each medical device in order to carry out update of the medical device. Furthermore, the medical device communication may include detection or localization of the medical devices before updating them.
According to some embodiments, a medical device communication system may facilitate wireless coordination between multiple (two or more) medical devices servicing a given patient or set of patients. For example, two or more medical devices such as pumps administering medication to a patient may be correlated so that the treatment is administered in coordination to achieve optimal administration.
According to some embodiments, a medical device may include a therapeutic component adapted to provide therapeutic functionality during whilst in therapeutic mode and further adapted to enter a device sleep mode (DSM); a transceiver may be configured to provide the device with wireless connectivity and may further be configured to transition into a transceiver sleep mode (TSM) substantially concurrent with transition into DSM. The transceiver may further be configured to intermittently transition between TSM and a scan mode, during which scan mode the transceiver may listen for a wireless packet addressed to the transceiver; and a localization module configured to emit a discovery signal upon receipt of said wireless packet addressed to said transceiver.
According to some embodiments, a medical device may include a therapeutic component adapted to provide therapeutic functionality during whilst in therapeutic mode and further adapted to enter a device sleep mode (DSM); a transceiver may be configured to provide the device with wireless connectivity and may further be configured to transition into a transceiver sleep mode (TSM) substantially concurrent with transition into DSM. The transceiver may further be configured to intermittently transition between TSM and a scan mode, during which scan mode the transceiver may intermittently transmits a wireless packet identifying the transceiver. The medical device may further include a localization module configured to emit a discovery signal upon receipt of a confirmation from a seeking device.
According to some embodiments, substantially upon receipt of the wireless packet, the transceiver may be configured to transition to an awake mode and the therapeutic component may be configured to transition into a therapeutic mode.
According to some embodiments, the medical device may further include a screen which may display a flag indicative of a non-discovery condition.
According to some embodiments, the therapeutic component may be configured to receive an update via the transceiver.
According to some embodiments, the therapeutic component may be configured to transition into a slave mode and to be remotely operated by a master device via the transceiver.
According to some embodiments, the medical device may further include a battery whose full charge capacity and passive discharge rate ratio may be above a threshold value, wherein the ratio threshold is selected such that a battery of the selected type is operative to support the transceiver operation for at least 4 months.
According to some embodiments, the therapeutic component may be a peristaltic pump.
According to some embodiments, a method for localizing a medical device including a transceiver may include receiving an identifier from a medical device at one or more computing platforms, determining an estimated location of the medical device based on secondary information from the one or more computing platforms, seeking the medical device in proximity to the estimated location, hearing a beacon from the medical device and locating the medical device
According to some embodiments, the method may further include confirming a discovery.
According to some embodiments, determining an estimated location may be carried out based on antenna triangulation, look up table and/or computing platform location.
Turning now to FIG. 1A-1E, depicted are flowcharts including the exemplary steps associated with which may be performed by exemplary medical devices according to the present invention.
According to some embodiments, a method for localizing a medical device may be carried out such as method 100 of FIG. 1A. A medical device may be in a sleep, idle, standby or non-active mode, for example, when it is not in use or has concluded administering a treatment (as shown in step 102). Sleep, idle, standby or non-active modes may assist in saving power and lengthening battery life and lowering the frequency in which the medical device needs to be plugged into a socket in order to recharge batteries. The medical device may switch to a scanning mode (as shown in step 104) in which scanning circuitry such as transceivers, controllers and more may be activated. While in scanning mode the medical device may continuously or intermittently listen or await receipt of a poll or signal from a seeking device (as shown in step 106). Receipt of a poll may cause/trigger a localization module within the medical device to emit a localization/discovery signal to aid or assist in detection of the medical device such as a beacon, an alarm, a light or a location indicative signal in response to the poll (as shown in step 108). If no poll or seeking signal were received within a predetermined length of time the medical device may transition back to sleep mode (returning to step 102). The medical device may transition between sleep mode (step 102) and scan mode (step 104) intermittently based on fixed, predetermined periods or may transition according to variable periods depending on secondary parameters such as an internal clock or a preprogrammed schedule. For example, the medical device may transition between sleep mode (step 102) and scan mode (step 104) once every 5 minutes during the day and once every hour at night which may be defined as a period with a lower likelihood to receive a wireless packet from a seeking device (step 106).
According to some embodiments, a method for localizing a medical device may be carried out such as method 120 of FIG. 1B. Steps 122,124 and 128 may be substantially similar to steps 102,104 and 108 (accordingly). While in scanning mode the medical device may continuously or intermittently check an external registry to determine if the medical device was polled for (as shown in step 126). For example, the medical device may broadcast, transmit or emit an identifier associated with the specific medical device to a computing platform. The computing platform may include a log storing all medical devices being sought out. The identifier may be a wireless packet associated with a specific medical device, may be an IP address or otherwise. Thus the computing platform may compare the medical device identifier to sought medical device(s) identifiers and signal a confirmation if there is a correlation or match. The medical device may activate a beacon if a confirmation is received from the computing platform (step 128).
According to some embodiments, a method for localizing a medical device may be carried out such as method 140 of FIG. 1C. Steps 142 and, 144 may be substantially similar to steps 102 and 104 (accordingly). While in scanning mode the medical device may continuously or intermittently contact a computing platform or database within the vicinity of the medical device (as shown in step 146). The medical device may then register in the computing platform or database (step 149). Registration in the computing platform/database may include information such as status (such as the medical device currently in use), estimated location and/or operational logs associated with the medical device. An estimated location and secondary or associated information to an estimated location may include information such as nearby markers, an identifier of a nearby access point, computing platform or nearby additional medical device or may be calculated or detected by known wireless device location estimation methods such as access network received signals and characteristics of the signals (amplitude, strength, direction, correlation between two or more signals received), antenna triangulation or via a look up table correlating the computing platforms which detected a sought device and an estimated location associated with those devices. The access network may be Wi-Fi, RF, Bluetooth, cellular base-station identification, global position system (GPS) information, cellular triangulation, Hotspots or other methods of detecting or tracking movement in a wireless device. Operational logs registered in the register may be information associated with the medical device operation such as drugs delivered, medical device operation rate, date/time of delivery, duration of operation, patient ID and more. Not depicted are subsequent steps of activating a beacon although it is understood that such steps may be subsequent to the logging, for example, when a seeking device identifies the medical device within the log.
According to some embodiments, a method for localizing a medical device may be carried out such as method 150 of FIG. 1D. Steps 152 and 154 are substantially similar to steps 102 and 104 (accordingly). Method 150 may further include the step of transmitting/broadcasting an identifier associated with the medical device. Step 156 may be repeated several times before transitions to sleep mode. Such a method may be utilized to identify medical devices within a vicinity, for inventory control and more.
According to some embodiments, a method for localizing a medical device may be carried out such as method 160 of FIG. 1E. Steps 162,164 and 168 may be substantially similar to steps 102, 104 and 108 (accordingly). Step 166 may be substantially similar or interchangeable with steps 106,126,146 and/or 149. Method 160 may further include the step of transitioning to an active mode and receiving a beacon from a poling/seeking device in the vicinity of the medical device (step 170). Optionally, method 160 may further include the step of downloading, receiving or installing updates associated with the medical device and its functionality such as drug libraries, operational regimes and more (step 172). Optionally, method 160 may further include the step of entering into a slave mode wherein the medical device is at least partially activated or controlled by a remote device or server functioning as a master device (step 174). According to some embodiments step 174 may include control of one medical device by an additional medical device and/or coordination between two or more devices by a server facilitating coordination between multiple medical devices servicing a given patient or set of patients.
Turning now to FIG. 2, depicted is a functional block diagram of an exemplary medical device communication, control and localization apparatus such as apparatus 200 according to embodiments of the present invention. Apparatus 200 may include a medical device such as medical device 202 configured to carry out a medical treatment or therapeutic regiment. Medical device 202 may include a receiver or a transceiver such as transceiver 204 configured to receive a wireless transmission. Transceiver 204 may further be configured to transmit a wireless transmission. Transceiver 204 may include one or more antennas such as antenna 206. Antenna 206 may be a printed antenna, chip antenna, extender antenna and more. Transceiver 204 may be a radio frequency (RF), Wi-Fi, wireless internet, cellular, GPS and/or other transceiver. Transceiver 204 may include a mode selector such as mode selector 208 configured to cause/enable transceiver 204 to alternate between a scan mode, sleep mode and active/awake/on mode. In the active mode medical device 202 is in its operative mode for carrying out a medical use. In its sleep mode medical device 202 is in a battery/energy saving mode where most circuits are shut off or in a sleep mode. In its scan mode the transceiver's circuits may be activated or turned on to: (1) listen for wireless signals/packets addressed to the transceiver identifier, (2) wirelessly transmit/broadcast its own identifier, (3) wirelessly connect to and check a registry of a computing platform and more. Transceiver 204 may further comprise a dedicated battery such as scan mode battery 210 which may be a rechargeable battery, a capacitor and more. Battery 210 may recharge when connected to an external power supply. Battery 210 may be configured or chosen so that the ratio between its full/maximal charge capacity and passive discharge rate (for example due to leakage) is above a threshold so that transceiver operation may be operative for at least 4 months and/or for at least 6 months.
According to some embodiments, battery 210 may be sufficient to power the transceiver to alternate between a sleep mode and a scan mode and operate in the scan mode (emit signal, listen for packets and more) for over 4 months. For example, a battery may have a full charge capacity and a passive discharge rate (for example due to standby leakage) whose rate is above a threshold value. The battery may be selected so that the transceiver is operable with a power supply from the battery for at least 4 months and/or at least 6 months. Furthermore, it is understood that the system design and low power consumption of the transceiver functionality may enable using a standard battery.
According to some embodiments, transceiver 204 may further include a control logic such as transceiver control logic 212. Transceiver control logic 212 may include, be embedded with or be operable with mode selector 208. Transceiver control logic 212 may be a circuit or code/thread running on a general purpose controller. Transceiver control logic 212 may be dedicated for the transceiver or may be joint with a medical device control logic such as medical device control logic 214. Mode selector 208 may control/indicate to the medical device control logic (214) to switch to an on or active mode. Transceiver control logic 212 may be configured to transition operation of the transceiver between modes (such as on, sleep and scan modes). Transceiver control logic may further include a timer and/or sleep/wake circuits.
According to some embodiments, medical device 202 may include a localization module such as beaconing module 216 configured to emit a guiding signal, for example, when medical device 202 is acknowledged as being sought. Exemplary guiding signals are: a beacon, alarm, flashing light, colored light, a signal transmitted by transceiver 204 to indicate location of medical device 202, a combination of the exemplary guiding signals and more. Beaconing module 216 may be included within or external to the transceiver 204.
According to some embodiments, medical device 202 may include one or more memory modules such as transceiver memory 218 and/or medical device memory 220. Optionally, the two memories 218 and 220 may be joined, embedded or separated. Transceiver memory 218 may be stored within the transceiver and may further be configured to be turned on in scan mode to allow access to relevant information needed in that mode such as location information. Memory 218 and/or 220 may store treatment regiments associated with the medical device, coordination regiments between the medical device and an associated medical device, location associated information (such as closest medical device detected, closest hot spot detected, location coordinates) and more.
According to some embodiments, medical device 202 may include a medical device power supply such as medical device power supply 222 which may be a rechargeable battery, a power source or connectivity to an electrical socket and more. Medical device power supply 222 may be combined with or separate from scan mode battery 210.
According to some embodiments, medical device 202 may include medical device therapeutic/diagnostic portion circuit or assembly such as component medical device therapeutic/diagnostic component 224 and may be configured to carry out the therapeutic or diagnostic operations/functionality of the medical device such as a medical pump, a blood pressure measurement apparatus, heart and lung machine, a dialysis machine, a cat scan, an x-ray machine and more. Medical device therapeutic/diagnostic component 224 may be controlled by medical device control logic 214.
According to some embodiments, medical device 202 may further include a screen such as screen 250 which may be a color screen, black and white screen, touch screen, flat screen and/or otherwise. Screen 250 may be configured to display a flag indicative of a non-discovery condition. For example, if medical device 202 was located but was not subsequently discovered (for example, physically located by a user) a flag or notification with relevant information such as: contact information, when the medical device was sought and more may be displayed on the screen so that a subsequent user may choose to notify a person/system seeking the medical device where it is located.
Turning now to FIG. 3 depicted is a functional block diagram of an exemplary computing platform such as computing platform 300 operable to seek for a medical device according to embodiments of the present invention. Computing platform 300 may include a seeking device such as seeking device 302. Seeking device 302 is operable to seek for medical devices such as described with regard to FIG. 2 but not limited to this example. Seeking device 302 may include a transceiver such as transceiver 304 including an antenna such as antenna 306 and a controller such as controller 308. Seeking device 302 may further include a computing platform memory or registry such as memory 310. Transceiver 304 may be a radio frequency (RF), Wi-Fi, wireless internet, cellular, GPS and/or other transceiver operable to receive and transmit signals from transceiver 204. Computing platform 300 may include a server such as server 312 which may be associated wirelessly or otherwise with seeking device 302 and additional seeking devices. Controller 308 may be configure to enable to operate transceiver 304 to: (1) emit a polling or seeking signal for one or more medical devices, (2) register medical devices detected within proximity to the computing platform in the memory 310, (3) compare a registry/list from memory 310 or server 312 of detected medical devices to a sought medical device and send a confirmation to the medical device if it is sought by a user and more.
According to some embodiments, server 312 may be one or more servers. Server 312 may be configured to manage, coordinate or operate a plurality of seeking devices. Server 312 may include a memory for storing and managing which medical devices were detected, where medical devices are located, which seeking devices are in proximity to a medical device, which medical devices are being polled for and more. Server 312 may further be configured to manage wireless updates of medical devices such as: drug library updates and associated information, system updates and associated information, Firmware updates, operational modes/regimes updates, drug libraries updates. Server 312 may be configured to facilitate wireless connection between multiple medical devices servicing a given patient or set of patients.
Turning now to FIG. 4A-4E are schematic illustrations, depicting exemplary medical device communication, control and localization systems according to embodiments of the present invention. FIG. 4A depicts a first exemplary medical device communication, control and localization configuration such as system 4002. System 4002 may include one or more medical devices such as medical devices 402 and 404. Medical devices 402 and 404 may be identical, similar or different types of medical devices. Medical device 402 may function as a medical device as described in FIG. 1A-1E. Medical device 404 may function as wireless polling or seeking device as described above. Medical device 402 may be wirelessly polled for by medical device 404 and when found the two medical devices may create a direct wireless connection or optionally, utilize a hub or additional server such as hub/server 406 to maintain wireless connection between each other. The connection between medical devices 402 and 404 may allow the two medical devices to coordinate treatments between themselves.
According to some embodiments, the use of medical device 404 and additional (not shown here) medical devices as computing platforms or seeking devices may allow creation of an ad hoc grid of polling devices seeking other medical devices. Exemplary embodiments utilizing this configuration could be field hospitals or hospitals lacking sufficient hot spots to increase the amount of seeking devices, or substantially immobile medical devices being used to identify nearby mobile medical devices in their proximity.
Turning now to FIG. 4B, depicts a second exemplary medical device communication, control and localization configuration system according to embodiments of the present invention such as system 4004. System 4004 includes two medical devices such as medical devices 408 and 410 which each may function as described in FIG. 1A-1E. Seeking devices such as hand held/mobile devices 412 and 414 may seek medical devices within their coverage areas 416 and 418 (respectively). A hand held/mobile device may find a medical device if it is within its coverage area so that hand held/mobile device 416 may find medical device 408 while neither hand held/mobile devices 412 nor 414 may find medical device 410 and is thus not found. Hand held/mobile devices 412 and 414 may be personal digital assistant (PDA), tablets, smart phones or cellular phones, laptop computers, barcode scanner joint with a wireless transceiver and more.
Turning now to FIG. 4C, depicted is a third exemplary medical device communication, control and localization configuration system according to embodiments of the present invention such as system 4006. System 4006 is substantially identical to system 4004, elements 420-426 may be substantially identical to elements 408-414 (accordingly). A medical device may register or contact a seeking device if it is within its coverage area (428 and 429) so that medical device 420 may contact hand/held mobile device 424 while medical device 422 does not contact hand held/mobile devices 424 or 426 and is thus may not be detected.
In some exemplary embodiment in accordance with FIGS. 4B and/or 4C may be for home use or home care medical devices distributed to patients to be used in their homes, a misplaced medical device can be located within a patient's home using a hand held seeking device. In a different example, field hospitals may utilize hand held devices to locate misplaced or missing medical devices. In a different example, hospitals may use hand held devices to locate medical devices, a map covering target areas covering parts or all of a hospital can be planned so that sought medical devices (for example 408 and 410) can be found throughout the hospital. For example, a worker may be supplied with a map of places to stand for predefined periods of time so that the whole hospital is eventually covered by coverage areas (for example 416) of the hand held device so that all sought medical devices (for example 408 and 410) are subsequently located.
Turning now to FIG. 4D, depicted is a fourth exemplary medical device communication, control and localization configuration system according to embodiments of the present invention such as system 4008. System 4008 may include medical devices such as medical devices 430, 432, 434 and 436 and each may function as a medical device as described in any of FIG. 1A-1E. a computing platform such as computing platform 440 may poll for sought after medical devices 430-436. Medical devices within computing platform's coverage area 442 may be detected (in this example, medical devices 430-434) while medical device 436 is not. An exemplary embodiment for this configuration may be a nurse's station including a Wi-Fi transmitter and a computer or docking station functioning as the computing platform 440 polling for missing medical devices 430-436 within the ward covered by coverage area 442. A similar configuration depending on a medical device's coverage area as described with regard to FIG. 1C may also be configured.
Turning now to FIG. 4E, depicted is a fifth exemplary medical device communication, control and localization configuration system according to embodiments of the present invention such as system 4010. System 4010 may include medical devices such as medical devices 450 and 452, each may function as a medical device as described in any of FIG. 1A-1E. Computing platform such as computing platforms 454-464 may poll for sought after medical devices 450 and 452. Medical devices within computing platform's coverage areas 474-484 may be detected. The plurality of computing platforms 454-464 may create a grid covering some or all of a predetermined area and may provide additional information such as which computing platform the medical device is nearest to or improved accuracy of localization due to additional information. An exemplary embodiment for this configuration may be a nurse's station including multiple Wi-Fi transmitters throughout a hospital ward and a computer or docking station functioning as the computing platforms 454-464. Polling for missing medical device 450 within the ward is covered by coverage area 474 and polling for missing medical device 452 within the ward is covered by coverage areas 476 and 480. An additional exemplary embodiment may be a hospital covered by a computing platform grid such as created by computing platforms 454-464 to allow monitoring of medical devices within the grid to aid in inventory control of medical devices within the hospital. A similar configuration depending on medical device's coverage area as described with regard to FIG. 1C may also be configured, or that a grid or array created by a multiplicity of medical devices acting also as seeking devices may be implemented.
Turning now to FIG. 5A-5C depicted are flow charts including the exemplary steps associated with according to embodiments of the present invention which may be performed by the exemplary medical devices and/or the medical device communication, control and localization system of FIGS. 2 and 3. FIG. 5A depicts flow 5001 including a medical device and a computing platform exemplary steps. A computing platform may poll for one or more medical devices (step 502). The computing platform may intermittently poll for the sought after medical devices for example for a period of 10 minutes poll for all relevant medical devices every 2 seconds. The medical device may transition into a scan mode (step 504) for example once every 3.5 minutes or if the medical device is connected to an external power source the medical device may stay in a scan mode. The medical device may determine if it is being polled for (step 506) for example once every 5 seconds while in scan mode or continuously if connected to an external power source. Rate or frequency of transition into scan mode (step 504) and/or determining if being polled for (step 506) may also be programmed and modified from time to time, for example, a medical device may be programmed to transition into scan mode (step 504) once every 20 minutes and a system update may reprogram the medical device to transition into scan mode (step 504) once every 5 minutes during night hours (such as 8 pm to 4 am) and once every hour during daytime hours (such as 4 am to 8 pm). If a poll is received, the medical device may transition to an awaken mode for a predetermined length of time (for example 2 hours) and/or may activate a discovery signal (step 508). If a poll is not received the medical device may transition to a sleep mode (step 510) or if connected to an external power source may remain in scan mode.
FIG. 5B depicts flow 5002 including a medical device and a computing platform exemplary steps according to embodiments of the present invention. The medical device may transition into a scan mode (step 514) for example once every 3.5 minutes or if the medical device is connected to an external power source the medical device may stay in a scan mode. The medical device may transmit an identifier (step 516) for example once every 3.5 minutes or once every 5 seconds. A computing platform may receive the identifier (step 518) and determine if the medical device is being sought or polled for (step 520) and optionally may store the identifier in a database or register. If the medical device is being sought or polled for the computing platform may return/send a confirmation (step 522). Upon receipt of the confirmation (step 524) the medical device may transition to an awaken mode for a predetermined length of time (for example 2 hours) and/or may activate a localization signal (step 526).
FIG. 5C depicts flow 5003 including a medical device and a computing platform exemplary steps according to embodiments of the present invention. The medical device may transition into a scan mode (step 614) for example once every 3.5 minutes or if the medical device is connected to an external power source the medical device may stay in a scan mode. The medical device may transmit an identifier (step 616) for example once every 3.5 minutes or once every 5 seconds. A computing platform may receive the identifier (step 618) and store the identifier and or more information in the computing platform (step 620). For example, while managing an inventory it may be desirable to register all of the detectable medical devices. The medical devices may periodically or intermittently transmit their identifier and the computing platform may store the received identifiers in a registry or memory within a server. Furthermore, additional information such as which seeking device(s) received identifier from the medical device, when the identifier was received and more.
Turning now to FIG. 6, depicted is a flow chart (6001) including exemplary steps for a transceiver and a therapeutic component according to embodiments of the present invention. A therapeutic component of a medical device may transition into a sleep mode or a device sleep mode (DSM) wherein while the therapeutic functionality of the medical device is not active, the therapeutic component is turned off so as to save energy (step 702), Substantially concurrently with therapeutic component transitioning into a DSM the transceiver may transition into a transceiver sleep mode (TSM) (step 704) and periodically transition into a scan mode (step 706) as described above, for example, with regard to step 104 of FIG. 1A. The transceiver may then activate various localization methods (step 708) which may further be understood by steps 506 of FIG. 5A, step 526 and 524 of FIG. 5B, step 616 of FIG. 5C and more. If the medical device was found (step 710) the transceiver may transition into an awake mode and the therapeutic component may transition into a therapeutic mode and the medical device may further emit a discovery signal (step 712). If the medical device was not found, the transceiver may transition back to a TSM (step 704).
According to some embodiments, if the medical device was not discovered, for example the medical device was not physically found by a person, an audible beacon was not heard by a user seeking a medical device, or a computing platform remotely located did not receive/identify a substantially accurate location of the medical device (step 714), upon subsequent turning on of the medical device (step 716) by a user a flag may be displayed on a screen with information such as when the medical device was sought for, who was seeking for the medical device and contact information so that the user may notify of the location of the medical device (step 718). It is to be understood that step 716 may be a spontaneous event and may not take place chronologically after step 714 for example but rather, whenever step 714 occurs if the medical device was found (step 710) and not discovered (step 714) a flag indicative of a non-discovery condition may appear on the screen. If the medical device was discovered (step 714) then the flag may be removed or confirming of discovery may be completed (step 720) either electronically (for example, a signal is received) or mechanically (for example, a mechanical switch is set) and either automatically (for example if the seeking device confirm finding) or manually (for example a user confirms finding). According to some embodiments the flag may further be displayed on a screen (step 718) concurrently with emitting of a detection symbol.
According to some embodiments, if therapeutic component is active, for example, administering a treatment the transceiver will not transition to a seeking mode and/or may not respond to a poll. A flag may be displayed (step 718) in such a situation, once the therapeutic component transitions to a non-active mode or once the therapeutic component subsequently awakens. According to some embodiments discovering a medical device (step 714) may include hearing or seeing a beacon emitted from the medical device and physically locating/finding the medical device by a person.
While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
Patent Application
20130279370
