Medical device positioning and tracking system

文档序号：474729 发布日期：2021-12-31 浏览：11次中文

阅读说明：本技术 医疗设备定位和跟踪系统 (Medical device positioning and tracking system ) 是由 A·S·阿涅洛 G·J·赖克曼 P·R·莱梅于 2020-03-30 设计创作，主要内容包括：用于自动确定关于多个医疗设备控制器(100)的物理定位信息并跟踪相应的医疗设备控制器中各个的物理定位的变化的方法(500)和系统(300、400)。一个或更多个机器学习模块(426、430、434)从自医疗设备控制器接收的计算机网络消息推断物理定位,所述计算机网络消息包括关于靠近医疗设备控制器(100)中各个医疗设备控制器的计算机网络部件(306、308、310、312)的信息。(Methods (500) and systems (300, 400) for automatically determining physical positioning information about a plurality of medical device controllers (100) and tracking changes in the physical positioning of each of the respective medical device controllers. One or more machine learning modules (426, 430, 434) infer physical location from computer network messages received from medical device controllers, including information about computer network components (306, 308, 310, 312) proximate to respective ones of the medical device controllers (100).)

1. A medical device controller localization and tracking system (300, 400), the system (300, 400) comprising:

a first electronic data storage (402) configured to store a plurality of first entries, wherein each first entry contains information associating a respective medical device controller (100) with a respective physical location;

a second electronic data store (404) configured to store a plurality of second entries, wherein each second entry contains information associating a respective computer network device (306, 308, 310, 312) with a respective physical location;

a user interface (410,600,700) configured to:

receiving from a human user: (a) information (204, 414, 710) identifying the identified medical device controller (100) and (b) information identifying a typed physical location (608, 412, 716) of the identified medical device controller (100); and

storing a new first entry (416) in the first electronic data store (402), wherein the new first entry associates the identified medical device controller (100) with the entered physical location (608, 412, 716);

a receiver (418) configured to receive messages (420) from a plurality of medical device controllers via a computer network (302), wherein each message (420) is sent by a respective sender medical device controller (100) of the plurality of medical device controllers, and each message (420) comprises: (a) an identifier (422) of the sender medical device controller and (b) an identifier (424) of a computer network device (306, 308, 310, 312);

the first machine learning module (426) is configured to, in response to receipt of one of the messages (420), automatically:

determining whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location; and is

If an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location, a new second entry (428) is stored in the second electronic data storage (404), wherein the new second entry (428) associates the computer network device (306, 308, 310, 312) with the physical location associated with the sender medical device controller (100).

2. The system according to claim 1, wherein the identifier (424) of the computer network device identifies a computer network device (306, 308, 310, 312) with which the sender medical device controller (100) has communicated.

3. The system according to any preceding claim, wherein the identifier (424) of the computer network device identifies a computer network device (306, 308, 310, 312) with which the sender medical device controller (100) has direct wireless communication.

4. The system according to any preceding claim, wherein the identifier (424) of the computer network device identifies a wireless access point (306) with which the sender medical device controller (100) has direct wireless communication.

5. The system according to any preceding claim, wherein the identifier (424) of the computer network device comprises a base station identifier of a cellular base station (308) with which the sender medical device controller (100) has directly wirelessly communicated.

6. The system of any preceding claim, wherein the identifier (424) of the computer network device identifies a computer network device (310, 312) through which the message passed on its way to the receiver.

7. The system of any preceding claim, wherein the identifier (424) of the computer network device comprises an IP address.

8. The system of any preceding claim, further comprising a second machine learning module (430) configured to, in response to receipt of one of the messages (420), automatically:

determining whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location;

determining whether an entry in the second electronic data storage (404) associates the computer network device (306, 308, 310, 312) with a corresponding physical location if an entry associating the sender medical device controller (100) with a corresponding physical location is not found in the first electronic data storage (402); and

if no entry is found in the first electronic data storage (402) associating the sender medical device controller (100) with a corresponding physical location and an entry is found in the second electronic data storage (404) associating the computer network device (306, 308, 310, 312) with a corresponding physical location, storing a new first entry (432) in the first electronic data storage (402), wherein the new first entry (432) associates the sender medical device controller (100) with the physical location associated with the computer network device (306, 308, 310, 312).

9. The system of any preceding claim, further comprising a third machine learning module (434) configured to, in response to receipt of one of the messages (420), automatically:

determining whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location;

determining whether an entry in the second electronic data storage (404) associates the computer network device (306, 308, 310, 312) with a corresponding physical location if an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location;

comparing the physical location associated with the sender medical device controller (100) in the first electronic data storage (402) with the physical location associated with the computer network device (306, 308, 310, 312) in a second electronic data storage (404) if an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location and an entry is found in the second electronic data storage (404) that associates the computer network device (306, 308, 310, 312) with a corresponding physical location in the second electronic data storage (404); and

if an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location and an entry is found in the second electronic data storage (404) that associates the computer network device (306, 308, 310, 312) with a corresponding physical location and the physical location associated with the sender medical device controller (100) in the first electronic data storage (402) is found to be different than the physical location associated with the computer network device (306, 308, 310, 312) in the second electronic data storage (404), modifying the entry in the first electronic data storage (402) to associate the sender medical device controller (100) with the computer network device (306, 308, 310, 312) in the second electronic data storage (404), 308. 310, 312) associated with the physical location.

10. The system according to claim 9, wherein the third machine learning module (434) is configured to temporarily modify the entry in the first electronic data storage (402) to associate the sender medical device controller (100) with the physical location associated with the computer network device (306, 308, 310, 312) in the second electronic data storage (404), and then automatically modify the entry in the first electronic data storage (402) to associate the sender medical device controller (100) with a default value.

11. A medical device controller localization and tracking system (300, 400), the system (300, 400) comprising:

a receiver (418) configured to receive messages (420) from a plurality of medical device controllers via a computer network (302), wherein each message (420) is sent by a respective sender medical device controller (100) of the plurality of medical device controllers, and each message (420) comprises: (a) an identifier (422) of the sender medical device controller (100) and (b) an identifier (424) of a computer network device (306, 308, 310, 312); and

a second machine learning module (430) configured to, in response to receipt of one of the messages (420), automatically:

determining whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location;

storing a new first entry (432) in the first electronic data store (402), if no entry is found in the first electronic data store (404) that associates the sender medical device controller (100) with a corresponding physical location and an entry is found in the second electronic data store (404) that associates the computer network device (306, 308, 310, 312) with a corresponding physical location, wherein the new first entry (432) associates the sender medical device controller (100) with the physical location associated with the computer network device (306, 308, 310, 312).

12. A medical device controller positioning and tracking system (300, 400), the system (300, 400) comprising:

a receiver (418) configured to receive messages (420) from a plurality of medical device controllers via a computer network (302), wherein each message (420) is sent by a respective sender medical device controller (100) of the plurality of medical device controllers, and each message (420) comprises: (a) an identifier (422) of the sender medical device controller (100) and (b) an identifier (424) of a computer network device (306, 308, 310, 312); and

a third machine learning module (434) configured to, in response to receipt of one of the messages (420), automatically:

determining whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location;

determining whether an entry in the second electronic data storage (404) associates the computer network device (306, 308, 310, 312) with a corresponding physical location if an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location; and

comparing the physical location associated with the sender medical device controller (100) in the first electronic data storage (402) with the physical location associated with the computer network device (306, 308, 310, 312) in the second electronic data storage (404) if an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location and an entry is found in the second electronic data storage (404) that associates the computer network device (306, 308, 310, 312) with a corresponding physical location in the second electronic data storage (404); and

13. A method (500) for locating and tracking a medical device controller (100), the method comprising:

providing (502) a first electronic data storage (402), the first electronic data storage (402) configured to store a plurality of first entries, wherein each first entry contains information associating a respective medical device controller (100) with a respective physical location;

providing (504) a second electronic data store (404), the second electronic data store (404) configured to store a plurality of second entries, wherein each second entry contains information associating a respective computer network device (306, 308, 310, 312) with a respective physical location;

receiving (506) information (204, 414, 710) identifying the identified medical device controller (100);

receiving (508), from a human user via a user interface (410,600,700), information (608, 412, 716) identifying an entered physical location (608, 412, 716) of the identified medical device controller (100);

storing (510) a new first entry (416) in the first electronic data store (402), wherein the new first entry (416) associates the identified medical device controller (100) with the entered physical location (608, 412, 716);

receiving (512) a message (420) from a sender medical device controller (100) via a computer network (302), the message comprising: (a) an identifier (422) of the sender medical device controller (100) and (b) an identifier (424) of a computer network device (306, 308, 310, 312);

responsive to receipt of the message (420), automatically determining (514) whether an entry in the first electronic data store (402) associates the sender medical device controller (100) with a corresponding physical location; and

if an entry is found (516) in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location, storing (518) a new second entry (428) (404) in the second electronic data storage, wherein the new second entry (428) associates the computer network device (306, 308, 310, 312) with the physical location associated with the sender medical device controller (100).

14. The method according to claim 13, wherein receiving (512) the message (420) including the identifier (424) of the computer network device (306, 308, 310, 312) includes receiving a message identifying a computer network device (306, 308, 310, 312) with which the sender medical device controller (100) has communicated.

15. The method according to any preceding claim, wherein receiving (512) the message (420) including the identifier (424) of the computer network device (306, 308, 310, 312) comprises receiving a message identifying a computer network device (306, 308, 310, 312) with which the sender medical device controller (100) has directly wirelessly communicated.

16. The method of any preceding claim, wherein receiving (512) the message (420) including the identifier (424) of the computer network device (306, 308, 310, 312) comprises receiving a message identifying a wireless access point (306) with which the sender medical device controller (100) has direct wireless communication.

17. The method of any preceding claim, wherein receiving (512) the message (420) including the identifier (424) of the computer network device (306, 308, 310, 312) comprises receiving a message identifying a base station identifier of a cellular base station (308) with which the sender medical device controller (100) has directly wirelessly communicated.

18. The method of any preceding claim, wherein receiving (512) the message (420) including the identifier (424) of the computer network device (310, 312) comprises receiving a message identifying a computer network device through which the message traveled en route to the receiver.

19. The method of any preceding claim, wherein receiving (512) the message (420) including the identifier (424) of the computer network device comprises receiving a message identifying an IP address.

20. The method of any preceding claim, further comprising, in response to receipt of the message (420), automatically:

determining (520) whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location;

if (522) no entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location, determining (524) whether an entry in the second electronic data storage (404) associates the computer network device (306, 308, 310, 312) with a corresponding physical location; and

storing (528) a new first entry (432) in the first electronic data storage (402), if (520) no entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location, and an entry is found (526) in the second electronic data storage (404) that associates the computer network device (306, 308, 310, 312) with a corresponding physical location, wherein the new first entry (432) associates the sender medical device controller (100) with the physical location associated with the computer network device (306, 308, 310, 312).

21. The method of any preceding claim, further comprising, in response to receipt of the message (420), automatically:

determining (530) whether an entry in the first electronic data storage (402) associates the sender medical device controller (100) with a corresponding physical location;

determining (534) that an entry in the second electronic data storage (404) associates the computer network device (306, 308, 310, 312) with a corresponding physical location if (532) an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with the corresponding physical location; and

comparing (538) the physical location associated with the sender medical device controller (100) in the first electronic data storage (402) with the physical location associated with the computer network device in the second electronic data storage if (532) an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location and an entry is found (536) in the second electronic data storage that associates the computer network device with a corresponding physical location; and

if (532) an entry is found in the first electronic data storage (402) that associates the sender medical device controller (100) with a corresponding physical location, and an entry is found in the second electronic data storage (404) that associates the computer network device with a corresponding physical location, and the physical location associated with the sender medical device controller (100) in the first electronic data storage is found to be different (540) than the physical location associated with the computer network device (306, 308, 310, 312) in the second electronic data storage (404), then the entry in the first electronic data storage (402) is modified (542) to associate the sender medical device controller (100) with the computer network device (306, 310, 312) in the second electronic data storage (404), 308. 310, 312) associated with the physical location.

22. The method of claim 21, wherein modifying (542) the entry in the first electronic data storage (402) to associate the sender medical device controller (100) with the physical address associated with the computer network device (306, 308, 310, 312) in the second electronic data storage (404) comprises:

temporarily modifying the entry in the first electronic data storage (402) to associate the sender medical device controller (100) with the physical location associated with the computer network device (306, 308, 310, 312) in the second electronic data storage (404); and

the entry in the first electronic data store (402) is then automatically modified (544) to associate the sender medical device controller (100) with a default value.

23. A non-transitory computer readable medium encoded with instructions that, when executed by a processor, establish a process for performing a computer-implemented method (500) for locating and tracking a medical device controller, the process comprising:

a process configured to provide (502) a first electronic data storage (402), the first electronic data storage (402) configured to store a plurality of first entries, wherein each first entry contains information associating a respective medical device controller (100) with a respective physical location;

a process configured to provide (504) a second electronic data store (404), the second electronic data store (404) configured to store a plurality of second entries, wherein each second entry contains information associating a respective computer network device (306, 308, 310, 312) with a respective physical location;

a process configured to receive (506) information (204, 414, 710) identifying the identified medical device controller (100);

a process configured to receive (508), from a human user via a user interface (410,600,700), information (608, 412, 716) identifying the entered physical location of the identified medical device controller (100);

a process configured to store (510) a new first entry (416) in the first electronic data store (402), wherein the new first entry (416) associates the identified medical device controller (100) with the typed physical location;

a process configured to receive (512) a message (420) from a sender medical device controller (100) via a computer network (302), the message comprising: (a) an identifier (422) of the sender medical device controller (100) and (b) an identifier (424) of a computer network device (306, 308, 310, 312);

a process configured to automatically determine (514) whether an entry in the first electronic data store (402) associates the sender medical device controller (100) with a corresponding physical location in response to receipt of the message (420); and

a process configured to store (518) a new second entry (428) in the second electronic data storage (404) if an entry is found in the first electronic data storage that associates the sender medical device controller (100) with a corresponding physical location, wherein the new second entry (428) associates the computer network device (306, 308, 310, 312) with the physical location associated with the sender medical device controller (100).

Technical Field

The present invention relates to medical device location and tracking systems, and more particularly to a machine learning based system that automatically associates network identifiers used by medical devices to report status information with physical locations, thereby automatically detecting when a medical device is moved to other physical locations.

Background

Many medical devices, such as some implantable cardiac pumps, for example, those available from Abiomed, Inc., of Albioumed, Danfoss, Mass2.5 heart pump) to external controllers that collect and display operational data about the medical device, such as heart signal level, battery temperature, blood flow rate, and tubing integrity. An exemplary controller is available from Abio-Alder under the trade name Automatic ImpellaAnd (4) obtaining the product. The controller may issue an alarm when the operational data value exceeds a predetermined value or range, for example if a leak or loss of suction is detected. These controllers include a video display screen as a human-machine interface on which operational data and/or alarms are displayed.

To facilitate remote monitoring by medical personnel to ensure efficacy and patient safety, some such controllers may be coupled via a computer network (typically including a wireless segment) to a central server that is accessible to monitoring stations. The monitoring station may display real-time and/or historical operating data and/or alarms on a display screen for viewing by medical personnel.

Many such controllers are expensive and/or in short supply in hospitals and other medical facilities. Thus, as these controllers become available, for example after removing the heart pump from the patient, these organizations often move these controllers to locations where they are needed, including moving the controllers between floors of buildings, between buildings on a campus, and between campuses. Furthermore, sometimes these controllers move with the patient while the attached medical device is still connected to the patient, for example, if the patient moves from an operating room to an intensive care unit.

However, such movement can cause problems for medical personnel who remotely monitor the controller and the medical equipment to which it is attached. While the user interface of some controllers facilitates entry of positioning information, such information is not always entered when moving the controller, and sometimes the information is entered incorrectly. Thus, if the controller is moved, for example from one room or floor or building to another, medical personnel monitoring the controller remotely may not be able to learn the new location.

The lack of information about the physical location of the controller or incorrect information can compromise the patient's safety. For example, if medical personnel remotely monitoring the implantable cardiac pump are aware of an unsafe condition, e.g., because the respective controller issued an alarm, but the medical personnel did not know the (correct) location (e.g., room number) of the patient in which the implantable cardiac pump is currently located, the medical personnel cannot quickly dispatch a nurse, doctor, or technician to the patient as the case may be.

Disclosure of Invention

Embodiments of the present invention provide a medical device controller positioning and tracking system. The system includes a first electronic data storage device, a second electronic data storage device, a user interface, and a first machine learning module.

The first electronic data store is configured to store a plurality of first entries. Each first entry contains information associating a respective medical device controller with a respective physical location. The second electronic data store is configured to store a plurality of second entries. Each second entry contains information associating a respective computer network device with a respective physical location.

The user interface is configured to receive information identifying the identified medical device controller. The information identifying the identified medical device controller may be entered by a human, or the information identifying the identified medical device controller may be determined automatically without manual input into the user interface. The user interface is also configured to receive information from the human user identifying the typed physical location of the identified medical device controller. The user interface is configured to store the new first entry in the first electronic data storage. The new first entry associates the identified medical device controller with the entered physical location.

The receiver is configured to receive messages from a plurality of medical device controllers. The receiver is configured to receive a message via a computer network. Each message is sent by a respective sender medical device controller of the plurality of medical device controllers. Each message includes an identifier of the sender medical device controller. Each message also includes an identifier of the computer network device.

The first machine learning module is configured to automatically determine, in response to receipt of one of the messages, whether an entry in the first electronic data storage associates the sender medical device controller with a corresponding physical location. In other words, the first machine learning module is configured to automatically determine whether the first electronic data storage device contains such an association, rather than whether the sender medical device controller is associated with a particular physical location. If an entry is found in the first electronic data storage device that associates the sender medical device controller with a corresponding physical location, the first machine learning module is configured to store a new second entry in the second electronic data storage device. The new second entry associates the computer network device with the physical location associated with the sender medical device controller.

In any embodiment, the identifier of the computer network device may identify the computer network device with which the sender medical device controller has communicated. The identifier of the computer network device may identify the computer network device with which the sender medical device controller has directly wirelessly communicated. The identifier of the computer network device may identify a wireless access point with which the sender medical device controller has direct wireless communication. The identifier of the computer network device may comprise a base station identifier of a cellular base station with which the sender medical device controller has directly wirelessly communicated. The identifier of the computer network device may identify the computer network device through which the message passed on its way to the receiver. The identifier of the computer network device may include an IP address.

In any embodiment, the medical device controller positioning and tracking system may include a second machine learning module. The second machine learning module may be configured to automatically determine, in response to receipt of one of the messages, whether an entry in the first electronic data store associates the sender medical device controller with a corresponding physical location. If an entry is not found in the first electronic data store that associates the sender medical device controller with a corresponding physical location, the second machine learning module may be configured to determine whether an entry in the second electronic data store associates the computer network device with a corresponding physical location.

The second machine learning module may be configured to store a new first entry in the first electronic data storage if an entry associating the sender medical device controller with a corresponding physical location is not found in the first electronic data storage and an entry associating the computer network device with a corresponding physical location is found in the second electronic data storage. The new first entry may associate the sender medical device controller with a physical location associated with the computer network device.

In any embodiment, the medical device controller positioning and tracking system may include a third machine learning module. The third machine learning module may be configured to automatically determine, in response to receipt of one of the messages, whether an entry in the first electronic data store associates the sender medical device controller with a corresponding physical location. If an entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location, the third machine learning module may be configured to determine whether an entry in the second electronic data storage associates the computer network device with a corresponding physical location.

If an entry is found in the first electronic data storage associating the sender medical device controller with a corresponding physical location and an entry is found in the second electronic data storage associating the computer network device with a corresponding physical location, the third machine learning module may be configured to compare the physical location in the first electronic data storage associated with the sender medical device controller with the physical location in the second electronic data storage associated with the computer network device.

If an entry is found in the first electronic data storage associating the sender medical device controller with a corresponding physical location and an entry is found in the second electronic data storage associating the computer network device with a corresponding physical location and the physical location associated with the sender medical device controller in the first electronic data storage is found to be different from the physical location associated with the computer network device in the second electronic data storage, the third machine learning module may be configured to modify the entry in the first electronic data storage to associate the sender medical device controller with the physical location associated with the computer network device in the second electronic data storage.

In any embodiment, the third machine learning module may be configured to temporarily modify an entry in the first electronic data storage to associate the sender medical device controller with a physical location associated with the computer network device in the second electronic data storage. The third machine learning module may be further configured to subsequently automatically modify an entry in the first electronic data store to associate the sender medical device controller with a default value.

Another embodiment of the present invention provides a medical device controller positioning and tracking system. The system includes a first electronic data store, a second electronic data store, a receiver, and a second machine learning module.

The second machine learning module is configured to automatically determine, in response to receipt of one of the messages, whether an entry in the first electronic data store associates the sender medical device controller with a corresponding physical location. If no entry is found in the first electronic data store that associates the sender medical device controller with a corresponding physical location, the second machine learning module is configured to automatically determine whether an entry in the second electronic data store associates the computer network device with a corresponding physical location.

If an entry associating the sender medical device controller with a corresponding physical location is not found in the first electronic data store, and an entry associating the computer network device with a corresponding physical location is found in the second electronic data store, the second machine learning module is configured to automatically store the new first entry in the first electronic data store. The new first entry associates the sender medical device controller with a physical location associated with the computer network device.

Yet another embodiment of the present invention provides a medical device controller positioning and tracking system. The system includes a first electronic data store, a second electronic data store, a receiver, and a third machine learning module.

The third machine learning module is configured to automatically determine, in response to receipt of one of the messages, whether an entry in the first electronic data store associates the sender medical device controller with a corresponding physical location. If an entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location, a third machine learning module is configured to determine whether an entry in the second electronic data storage associates the computer network device with a corresponding physical location.

If an entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location and an entry is found in the second electronic data storage that associates the computer network device with a corresponding physical location, the third machine learning module is configured to compare the physical location in the first electronic data storage associated with the sender medical device controller with the physical location in the second electronic data storage associated with the computer network device.

If an entry is found in the first electronic data storage associating the sender medical device controller with a corresponding physical location and an entry is found in the second electronic data storage associating the computer network device with a corresponding physical location, and the physical location associated with the sender medical device controller in the first electronic data storage is found to be different from the physical location associated with the computer network device in the second electronic data storage, the third machine learning module is configured to modify the entry in the first electronic data storage to associate the sender medical device controller with the physical location associated with the computer network device in the second electronic data storage.

Embodiments of the present invention provide a method for locating and tracking a medical device controller. The method includes providing a first electronic data storage device and a second electronic data storage device. The first electronic data store is configured to store a plurality of first entries. Each first entry contains information associating a respective medical device controller with a respective physical location. The second electronic data store is configured to store a plurality of second electronic data entries. Each second entry contains information associating a respective computer network device with a respective physical location.

Information identifying the identified medical device controller is received.

Information identifying the keyed physical location of the identified medical device is received from a human user via a user interface.

The new first entry is stored in the first electronic data storage. The new first entry associates the identified medical device controller with the entered physical location.

A message is received from a sender medical device controller. The message is received via a computer network. The message includes an identifier of the sender medical device controller. The message also includes an identifier of the computer network device.

In response to receipt of the message, a determination is automatically made to determine whether an entry in the first electronic data store associates the sender medical device with a corresponding physical location. If an entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location, a new second entry is stored in the second electronic data storage. The new second entry associates the computer network device with the physical location associated with the sender medical device controller.

In any embodiment, receiving the message including the identifier of the computer network device may include receiving a message identifying the computer network device with which the sender medical device controller has communicated. In any embodiment, receiving the message including the identifier of the computer network device may include receiving a message identifying the computer network device with which the sender medical device controller has directly wirelessly communicated. In any embodiment, receiving the message including the identifier of the computer network device may include receiving a message identifying a wireless access point with which the sender medical device controller has direct wireless communication. In any embodiment, receiving the message including the identifier of the computer network device may include receiving a message identifying a base station identifier of a cellular base station with which the sender medical device controller has directly wirelessly communicated. In any embodiment, receiving a message that includes an identifier of a computer network device may include receiving a message that identifies the computer network device through which the message traveled on its way to the receiver. In any embodiment, receiving a message including an identifier of a computer network device may include receiving a message identifying an IP address.

In any embodiment, in response to receipt of the message, a determination may be automatically made to determine whether an entry in the first electronic data store associates the sender medical device controller with a corresponding physical location. If an entry is not found in the first electronic data store that associates the sender medical device controller with a corresponding physical location, a determination may be automatically made to determine whether an entry in the second electronic data store associates the computer network device with a corresponding physical location.

If no entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location and an entry is found in the second electronic data storage that associates the computer network device with a corresponding physical location, the new first entry may be stored in the first electronic data storage. The new first entry may associate the sender medical device controller with a physical location associated with the computer network device.

In any embodiment, in response to receipt of the message, a determination may be automatically made to determine whether an entry in the first electronic data store associates the sender medical device controller with a corresponding physical location. If an entry is found in the first electronic data store that associates the sender medical device controller with a corresponding physical location, a determination may be automatically made to determine whether an entry in the second electronic data store associates the computer network device with a corresponding physical location.

If an entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location and an entry is found in the second electronic data storage that associates the computer network device with a corresponding physical location and the physical location associated with the sender medical device controller in the first electronic data storage is found to be different from the physical location associated with the computer network device in the second electronic data storage, the entry in the first electronic data storage may be modified to associate the sender medical device controller with the physical location associated with the computer network device in the second electronic data storage.

In any embodiment, modifying the entry in the first electronic data storage device to associate the sender medical device controller with the physical location associated with the computer network device in the second electronic data storage device may include temporarily modifying the entry in the first electronic data storage device to associate the sender medical device controller with the physical location associated with the computer network device in the second electronic data storage device, and then automatically modifying the entry in the first electronic data storage device to associate the sender medical device controller with a default value.

Yet another embodiment of the invention provides a non-transitory computer readable medium. A non-transitory computer readable medium is encoded with instructions. When executed by a processor, the instructions establish procedures for performing a computer-implemented method for locating and tracking a medical device controller. The process includes a process configured to provide a first electronic data storage and a process configured to provide a second electronic data storage.

A process is configured to receive information identifying the identified medical device controller.

A process is configured to receive information identifying the keyed physical location of the identified medical device. The process is configured to receive information from a human user via a user interface.

A process is configured to store the new first entry in the first electronic data storage. The new first entry associates the identified medical device controller with the entered physical location.

A process is configured to receive a message from a sender medical device controller. The process is configured to receive a message via a computer network. The message includes an identifier of the sender medical device controller. The message also includes an identifier of the computer network device.

A process is configured to automatically determine, in response to receipt of the message, whether an entry in the first electronic data store associates the sender medical device with a corresponding physical location.

A process is configured to, if an entry is found in the first electronic data storage that associates the sender medical device controller with a corresponding physical location, store a new second entry in the second electronic data storage, wherein the new second entry associates the computer network device with the physical location associated with the sender medical device controller.

Drawings

The invention will be more fully understood by reference to the following detailed description, taken in conjunction with the accompanying drawings, in which:

fig. 1 is a perspective view of an exemplary conventional medical device controller and an exemplary conventional medical device (in this example, a cardiac pump) coupled to the medical device controller according to the prior art.

Fig. 2 shows exemplary hypothetical display screen content that may be displayed on the screen of the medical device controller of fig. 1, according to the prior art.

FIG. 3 is a schematic block diagram of the major components of a medical device positioning and tracking system for positioning and tracking a medical device controller (e.g., the medical device controller of FIGS. 1 and 2) according to one embodiment of the present invention.

Fig. 4 is a diagram schematically illustrating components of the server of fig. 3 and operations performed by the server, according to one embodiment of the present invention.

Fig. 5A-5C (collectively fig. 5) form a flow chart schematically illustrating operations performed by the server component of fig. 4, including operations performed by the first machine learning module (fig. 5A), operations performed by the second machine learning module (fig. 5B), and operations performed by the third machine learning module (fig. 5C), in accordance with respective embodiments of the present invention.

Fig. 6 illustrates an exemplary hypothetical user interface displayed on a display screen that can be implemented by the medical device controller of fig. 1 to provide medical device positioning information to the server of fig. 3-5 according to one embodiment of the present invention.

Fig. 7 illustrates an exemplary hypothetical user interface displayed on a display screen that can be implemented by the monitoring station of fig. 1 to provide medical device location information to the server of fig. 3-5 according to one embodiment of the present invention.

Detailed Description

Embodiments of the present invention provide methods and systems for automatically determining physical positioning information about a plurality of medical device controllers and tracking changes in the physical positioning of each of the respective medical device controllers. These embodiments utilize one or more machine learning modules to infer physical location from computer network messages received from medical device controllers, the computer network messages including information about computer network components proximate to the respective medical device controllers.

Background

Fig. 1 is a perspective view of an example conventional medical device controller 100 and an example conventional medical device 102 (in this example, a cardiac pump) coupled to the medical device controller 100. In the example shown in FIG. 1, the medical device controller 100 is an Automated Impella from Abio-Maillard, of Danfoss, MassAnd the heart pump 102 is also available from Abio-Maird2.5 cardiac pump, although any suitable medical device and controller may be used. In some cases, a medical device and its associated medical device controller are combined. Such a combination is referred to herein simply as a medical device controller.

The medical device controller 100 includes a display screen 104, and the medical device controller 100 displays operational data about the medical device 102, such as cardiac signal level, battery temperature, blood flow rate, and tubing integrity, on the display screen 104. As discussed in more detail herein, the medical device controller 100 may be connected to a computer network to transmit images of content displayed on the screen 104 to a remote server (not shown).

FIG. 2 illustrates exemplary hypothetical display screen content 200 that can be displayed on the screen 104 of the medical device controller 100 of FIG. 1. For example, the display screen content may include a heart pump type ("Impella5.0") 202, a heart pump serial number ("120703") 204, an alert/error message 206, a date and time 208, a controller software version number 210, a power icon 212, a placement signal 214, a current heart pump speed (performance) setting ("P-0") 216, a heart pump motor current value 218, a current or average blood flow rate 220, and minimum and maximum blood flow rates 222, as well as various charts 224. The display screen content 200 is typically pixilated.

Main component

FIG. 3 is a schematic diagram of the major components of a medical device positioning and tracking system 300. The system 300 may collect, store and retrieve operational data from a plurality of medical device controllers 100 and collect, store and retrieve operational data about the plurality of medical device controllers 100. Further, the system 300 locates and tracks the location of the medical device controller 100 as each medical device controller 100 moves from one physical location to another.

For simplicity, only the medical device controller 100 is shown in fig. 3, rather than a separate medical device. Although only four medical device controllers 100 are shown, other numbers of medical device controllers 100 may be used. Each medical device controller 100 is connectable to a computer network 302, optionally via a remote link module 304. The computer network 302 may include wired and/or wireless segments and/or networks, such as a wireless network conforming to the IEEE 802.1lx standard (wireless local area network (WLAN), commonly referred to as "Wi-Fi") represented by the wireless access point 306 and/or a cellular network represented by the cellular site 308. The computer network 302 may include private and/or public networks, such as a Local Area Network (LAN)310 (e.g., Ethernet) connected via a router 312, and/or a Metropolitan Area Network (MAN) and/or a Wide Area Network (WAN), such as the Internet (Internet) (not shown).

Each medical device controller 100 is configured to automatically repeat capturing status information about a medical device connected thereto and displaying the status information on the display screen 104 (fig. 1). As described above, fig. 2 illustrates corresponding hypothetical display screen content 200 that may be displayed on the screen 104 of any given medical device controller 100.

The server 314 is configured to automatically request and receive images of content displayed on the screen 104 of each medical device controller 100, either periodically or aperiodically, typically about once every 20 seconds. The request and image are sent via a computer network 302. The images may be sent in one or more messages encoded as video frames or sequences of video frames. For example, the video frame(s) may contain a pixelated copy of the image displayed on the display screen 104 of the medical device controller 100.

The server 314 is configured to process the received frames (images). Server 314 parses the image through an Optical Character Recognition (OCR) portion of the image and extracts textual information such as heart pump serial number, blood flow rate, warning message text, and the like. The server 314 may also parse the image and extract graphical information, such as power icons, and compare the graphical information to a predetermined pixel pattern and/or color. The server 314 may include an OCR engine or the server 314 may be in communication with an external OCR engine 316, for example via the computer network 302. The server 314 may then use the recognized text to automatically determine a serial number or other identifier of the medical device controller 100, operating parameters of the medical device controller 100, whether one of the medical device controllers 100 has issued an alert, and the like.

The data storage 318 is configured to store one or more media files, particularly frames (images), such as MP4 video or other suitable type of media files, and the server 314 is configured to automatically store the received frames (images) in the data storage 318. The data storage 318 records screen images received by the server 314 for later playback, for example in response to a request from one of several monitoring stations 320. For simplicity, only two monitoring stations 320 are shown, however any number of monitoring stations 320 may be included. The monitoring station 320 may use cloud-based technology to securely and remotely display images of the medical device controller 100 screen 104 to doctors and hospital staff anywhere with internet connectivity. An exemplary remote monitoring system is available under the trade name ImpellaAvailable under an on-line equipment management system, available from Abio-Maide, of Danfoss, Mass.

The data storage 318 is configured to provide the requested portion of the stored media file in response to the provisioning request. The data storage 318 thereby supports playback of medical device controller 100 status information. For example, the data storage 318 may provide one or more frames (images) of a video stored in a media file for display to a user by the monitoring station 320. The server 314 may also be configured to provide status information regarding one or more of the medical device controllers 100 to one of the monitoring stations 320 based on images received by the server 314 in real-time and/or based on historical information maintained in the data storage 318.

Each monitoring station 320 may display information about a plurality of medical device controllers 100, including their respective physical locations. As described above, each medical device controller 100 can move from one physical location to another, which can cause problems for medical personnel viewing the monitoring station 320 if the location information is lost or inaccurate. For example, a user of the monitoring station 320 may instruct the monitoring station 320 to display information about all medical device controllers 100 within a specified location. However, if the positioning information of one or more medical device controllers 100 is lost or incorrect, information about the wrong set of medical device controllers 100 will be displayed to the user.

Automatic physical location inference

To address this issue, server 314 includes a component 400 schematically shown in FIG. 4. 4. Using these components 400, the server 314 automatically learns the physical locations of some or all of the medical device controllers 100 and automatically tracks changes in these physical locations. The process may begin with a user manually entering physical positioning information about a subset of the medical device controllers 100 (e.g., one or more of the medical device controllers 100). This information is stored in a first data storage 402, which associates the medical device controller 100 with its respective physical location. This process is referred to as seeding the first data storage device 402.

From this information, the server 314 infers the physical location of the components of the computer network 302. For example, if the server 314 communicates via the computer network 302 with a medical device controller 100 whose physical location is known, and the communication involves a network component, such as the wireless access point 306 (fig. 3), that must be in close proximity to the medical device controller 100, then the server 314 stores information in the second data storage 404 that associates the network component with its corresponding physical location.

The necessary approach does not require any specific approach. The server 314 may use any available information and the server 314 may replace known physical location information with more accurate physical location information as it becomes available. For example, the server 314 may initially store physical location information about an Internet Protocol (IP) address, such as a physical location associated with an IP network to which the medical device controller 100 is connected, and then subsequently replace the location information with more accurate physical location information about the wireless access point.

From the physical location information about the network component, the server 314 infers the physical location of the medical device controller 100 for which the location is unknown or for which the physical location has changed from its previously known value. For example, if the server 314 communicates with a medical device controller 100 whose physical location is unknown, but the communication involves a network component that must be close to the medical device controller 100 and the location of the network component is known, the server 314 automatically infers the physical location of the medical device controller 100 from the physical location of the network component.

Similarly, if the server 314 communicates with a medical device controller 100 whose physical location is known, but the communication involves network components that must be close to the medical device controller 100, and the location of the network components is known to be more accurate than the physical location of the medical device controller 100, the server 314 automatically infers the more accurate physical location of the medical device controller 100 from the physical location of the network components, and the server 314 updates the physical location of the medical device controller 100.

Similarly, if the server 314 communicates with a medical device controller 100 whose physical location is known, and the communication involves a network component that must be close to the medical device controller 100 and the location of the network component is known, but the known location of the network component does not match the known location of the medical device controller 100, then the server 314 automatically infers that the medical device controller 100 has moved to a new physical location, and the server 314 infers the new physical location from the physical location of the network component.

Other sources of physical location information 406 may be used by server 314. For example, some commercial providers provide IP-based geolocation information, including physical locations associated with IP addresses. The server 314 may use the IP address or a portion thereof of the network message from the medical device controller 100 to automatically determine or at least estimate the physical location of the medical device controller 100, or at least process the address of an Internet Service Provider (ISP) of network traffic from the medical device controller 100 by querying such an IP-based geolocation service or database 408. A well-known Whois database may be similarly used. A database of cell sites may be similarly used. Thus, the first and/or second data storage devices 402 and/or 404 may, alternatively or additionally, be seeded with information from one or more geo-location service providers or databases 408.

Fig. 5 is a flow chart schematically illustrating operations performed by server 314 to implement a method 500 for locating and tracking a medical device. At 502, a first electronic data storage 402 is provided. The first data store 402 is configured to store a plurality of first entries. Each first entry contains information associating the respective medical device controller 100 with a respective physical location. Table 1 lists exemplary hypothetical contents of a first data storage device 402 according to one embodiment of the present invention. The left column lists identifiers, such as serial numbers, of the medical device controller 100. The right column lists the identifiers of the physical locations associated with the corresponding medical device controllers 100 in the left column.

At 504 (FIG. 5), a second electronic data store 404 is provided. The second data store 404 is configured to store a plurality of second entries. Each second entry contains information associating the respective computer network component with a respective physical location. Table 2 lists exemplary hypothetical contents of the second data storage device 404 according to one embodiment of the present invention. The left column lists identifiers of network components such as the IP or Media Access Control (MAC) address of a network or router (e.g., local area network 310 or router 312), the Service Set Identifier (SSID) of a wireless access point (e.g., wireless access point 306), the GSM Cell Identifier (CID) of a Base Transceiver Station (BTS) or sector of a BTS. The right column lists the identifiers of the physical locations associated with the corresponding network components in the left column.

At 506 (fig. 5), information identifying a medical device controller ("identified medical device controller") is received, and at 508, information identifying a physical location ("entered physical location") of the identified medical device is received. As described above, the first data storage device 402 may be seeded with one or more user entries. The server 314 (fig. 3) may include a user interface 410 (fig. 4) through which a user may enter information identifying the physical location of the medical device controller 100 and, optionally, the medical device controller 100.

One embodiment of such a user interface 410 is implemented by the medical device controller 100. Fig. 6 illustrates an exemplary user interface 600 displayed on the display screen 104 of the medical device controller 100. In this embodiment, the display screen 104 is a touch sensitive screen capable of receiving user input, although in other embodiments a physical keyboard may be connected to the medical device controller 100. The user interface 600 includes a prompt 602 and an area 604 in which the user can enter text identifying the physical location of the medical device controller 100. The user interface 600 includes a virtual keyboard 606 on the touch-sensitive display screen 104 on which a user can make inputs. A hypothesis entry is shown at 608. The user's input constitutes information identifying the physical location 412 (FIG. 4) of the typing user interface 410.

The user does not need to enter information identifying the medical device controller 100 because the medical device controller 100 has stored information such as its serial number, as shown on the display screen 104 at 204. When the medical device controller 100 sends the user's input 608 to the server 314, the medical device controller 100 also sends its serial number or other identifying information. The serial number or other identifying information constitutes information that identifies the medical device controller 414 (FIG. 4).

In another embodiment, the user interface 410 is implemented by one of the monitoring stations 320 (fig. 3). Fig. 7 shows an exemplary user interface 700 displayed on a display screen 702 of the monitoring station 320. In this embodiment, the display 702 may be a touch sensitive screen, as in the user interface 600 described with reference to fig. 6. Alternatively or additionally, a physical keyboard may be connected to the monitoring station 320. The user interface 700 includes a prompt 704 and a field 708 where the user can type in text identifying the medical device controller 100, such as a serial number 710 of the medical device controller 100. The user interface 700 also includes a prompt 712 and a field 714 in which the user may enter text identifying the physical location of the medical device controller 100. Hypothesis entries are shown at 716. The user entries 710 and 716 constitute information identifying the medical device controller 414 (FIG. 4) and information identifying the physical location 412.

In yet another embodiment, user interface 410 is implemented through an administration console (not shown) communicatively coupled to server 314. The management console may be implemented through a physical or virtual display and keyboard, a telnet connection from another computer, or any other suitable interface.

Based on the information collected by the user interface 410, i.e., the information 414 identifying the medical device controller 100 and the information 412 identifying the physical location, the user interface 410 stores a new first entry 416 in the first electronic data storage 402, as indicated by operation 510 (FIG. 5). The new first entry associates the identified medical device controller 100 with the entered physical location, as discussed with respect to table 1.

As described above, the medical device controller 100 sends a message to the server 314 via the computer network 302 to transfer an image of the display screen 104 on the medical device controller 100. These messages include a "sender" address identifying the corresponding medical device controller 100. The medical device controller 100 may send additional messages to the server 314 via the computer network 302. These additional messages may contain information about the network environment perceived by the medical device controller 100. From this information, the server 314 can infer which network component(s) are in proximity to the medical device controller 100. Server 314 includes a receiver 418 (fig. 4) configured to receive these network messages 420.

For example, if the medical device controller 100 is capable of wireless network communication, the medical device controller 100 sends information (such as an SSID) to the server 314 identifying the wireless access point 306 or other wireless infrastructure within radio range of the medical device controller 100, and the medical device controller 100 can wirelessly communicate with the wireless access point 306 or other wireless infrastructure. Optionally, the information includes a relative or absolute Received Signal Strength Indicator (RSSI) for the in-range wireless access point 306 or other wireless infrastructure, as measured by the medical device controller 100. Based on the RSSI, the server 314 may infer the relative proximity of the identified wireless access point 306 to the medical device controller 100, e.g., based on the relative strengths of the signals from the various wireless access points 306, etc.

In other examples, the medical device controller 100 sends a message to the server 314 identifying other network components (e.g., routers, switches, etc.) with which the medical device controller 100 has communicated. The medical device controller 100 may use tools such as traceroute (trace), ping, etc. to probe its network environment and automatically determine the relative proximity of the network components to the medical device controller 100. The medical device controller may then send this proximity information and the identifier of the corresponding network component to server 314.

Thus, any message received by the server 314 may include information 422 (fig. 4) identifying the sending medical device controller 100 and information 424 identifying the computer network component. The operations are summarized at operation 512 (fig. 5), where the server 314 receives a message 420 from the sender medical device controller 100 via the computer network 302. The message includes: (a) an identifier 422 of the sender medical device controller 100 and (b) an identifier 424 of the computer network component.

First machine learning module inferring location of network element

At 514 (FIG. 5), in response to receipt of the message 420, the server 314 automatically determines whether an entry in the first electronic data store 402 associates the sender medical device controller 100 with a corresponding physical location. The test determines whether the first electronic data storage device 402 contains such an association, rather than whether the sender medical device controller 100 is associated with a particular physical location. At 516, if an entry is found in the first electronic data storage 402 that associates the sender medical device controller 100 with a corresponding physical location, then control passes to 518 where the first machine learning module 426 in the server 314 stores a new second entry 428 in the second electronic data storage 404. The new second entry 428 associates the computer network component with the physical location associated with the sender medical device controller 100, as discussed with respect to table 2.

The identifier 424 of the computer network device may identify the computer network component with which the sender medical device controller 100 has communicated or with which the sender medical device controller 100 has directly wirelessly communicated. For example, the identifier 424 of the computer network device may identify the wireless access point 306 (fig. 3) with which the sender medical device controller 100 has directly wirelessly communicated, or a base station identifier of the cellular base station 308 with which the sender medical device controller 100 has directly wirelessly communicated. The identifier 424 of the computer network component may identify the computer network component through which the message 420 traveled on its way to the receiver 418. The identifier 424 of the computer network component may, for example, comprise an IP address or a MAC address.

The second machine learning module infers a location of the medical device controller

The server 324 may include a second machine learning module 430 (fig. 4). The second machine learning module 430 may be configured to automatically determine, in response to receipt of the message 420, whether an entry in the first electronic data store 402 associates the sender medical device controller 100 (identified by the ID 422) with a corresponding physical location, as shown in operation 520 (fig. 5).

If no entry is found in the first electronic data storage 402 that associates the sender medical device controller 100 with a corresponding physical location, then control passes from operation 522 to operation 524, where the server 314 determines whether an entry in the second electronic data storage 404 associates a computer network component (identified by the ID 424) with a corresponding physical location. If an entry associating the sender medical device controller 100 with a corresponding physical location is not found in the first electronic data storage 402 and an entry associating the computer network component with a corresponding physical location is found in the second electronic data storage 404 at operation 524, then control passes from operation 526 to operation 528, where the second machine learning module 430 stores the new first entry 432 in the first electronic data storage 402. The new first entry 432 associates the sender medical device controller 100 (identified by ID 422) with the physical location associated with the computer network component (identified by ID 424). The location of the computer network component is replicated from the second data storage 404 as represented in the right column of table 2.

Third machine learning module infers movement of medical device controller

The server 324 may include a third machine learning module 434 (fig. 4). The third machine learning module 434 may be configured to automatically determine, in response to receipt of the message 420, whether an entry in the first electronic data store 402 associates the sender medical device controller 100 (identified by the ID 422) with a corresponding physical location, as shown at operation 530. If an entry is found in the first electronic data storage 402 that associates the sender medical device controller 100 with a corresponding physical location, then control passes from operation 532 to operation 534, where the server 314 determines whether the entry in the second electronic data storage 404 associates the computer network component (identified by the ID 424) with the corresponding physical location.

If an entry is found in the first electronic data store 402 that associates the sender medical device controller 100 with a corresponding physical location, and an entry is found in the second electronic data store 404 that associates the computer network component with a corresponding physical location at operation 534, control passes from operation 536 to operation 538. At operation 538, the server compares the physical location associated with the sender medical device controller 100 in the first electronic data store 402 with the physical location associated with the computer network device in the second electronic data store 404.

If an entry is found in the first electronic data storage 402 that associates the sender medical device controller 100 with a corresponding physical location and an entry is found in the second electronic data storage 404 that associates the computer network device with a corresponding physical location, and, at operation 540, the physical location associated with the sender medical device controller 100 in the first electronic data storage 402 is found to be different than the physical location associated with the computer network device in the second electronic data storage 404, then at operation 542 the server modifies the entry 436 (FIG. 4) in the first electronic data storage 402 to associate the sender medical device controller 100 with the physical location associated with the computer network device in the second electronic data storage 404.

In some embodiments, at operation 542 the server only temporarily modifies the entry 436 (fig. 4) in the first electronic data storage 402 to associate the sender medical device controller 100 with the physical location associated with the computer network device in the second electronic data storage 404. Subsequently, for example after a predetermined time, the server modifies the entry 436 (FIG. 4) in the first electronic data store 402 to associate the sender medical device controller 100 with the default location, as shown at operation 544.

Detailed description of the preferred embodiments

The server 314, including the first, second, and third machine learning modules 426, 430, 434 and the receiver 418, may be implemented by a processor executing instructions stored in a memory. The instructions may include instructions for implementing the method 500 described with reference to fig. 5 and for implementing the processes of the user interface described with reference to fig. 6 and 7.

The first and second data stores 402 and 404 may be implemented with a relational database and may include a front end (load balancer) that distributes access requests across multiple copies of the database to support a large number of requests.

In the written description and claims, phrases such as "automatically determining whether an entry in the first electronic data storage associates a sender medical device controller (or network component) with a corresponding physical location" mean determining whether the electronic data storage contains such an association, rather than whether the sender medical device controller (or network component, as the case may be) is associated with a particular physical location. In such phrases, "corresponding physical location" does not refer to a particular physical location, but rather refers to any physical location. Thus, the decision is not compared to a particular physical location. Instead, the decision only tests whether an association currently exists.

Thus, if the data storage device contains information to record such associations, the result of the determination is true, whereas if the data storage device does not contain information to record any such associations, the result of the determination is false. The results of the determination may be referred to in subsequent phrases, such as "if an entry associating the sender medical device controller (or network component, as the case may be) with a corresponding physical location is found in the electronic data store, … …". In such phrases, the "corresponding physical location" does not raise a question of reference basis or clarity, since no particular physical location is mentioned. This phrase is equivalent to "if a previous determination produced a result of true (TURE.)".

While the present invention has been described by the above exemplary embodiments, modifications and variations may be made to the illustrated embodiments without departing from the inventive concepts disclosed herein. For example, while specific network element identifiers, such as IP addresses and SSIDs, may be recited in connection with the disclosed embodiments, the values of all parameters may be varied over a wide range to accommodate different applications within the scope of the present invention.

As used herein, including in the claims, the term "and/or" used in connection with a list of items refers to one or more of the items in the list, i.e., at least one of the items in the list, but not necessarily all of the items in the list. As used herein, including in the claims, the term "or" used in connection with a list of items refers to one or more of the items in the list, i.e., at least one of the items in the list, but not necessarily all of the items in the list. "or" does not mean "exclusive or".

Although aspects of the embodiments may be described with reference to flowchart illustrations and/or block diagrams, functions, operations, decisions, etc., of all or a portion of each block or a combination of blocks may be combined, divided into separate operations, or performed in other orders. Reference to "module" is for convenience and is not intended to limit its implementation. All or a portion of each block, module, or combination thereof, may be implemented as computer program instructions (e.g., software), hardware (e.g., combinational logic, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), processors, or other hardware), firmware, or combinations thereof.

The server 314, including the first, second, and third machine learning modules 426, 430, and 434, the receiver 418, or portions thereof, may be implemented by one or more processors executing or controlled by instructions stored in memory. Each processor may optionally be a general purpose processor, such as a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), a special purpose processor, etc., or a combination thereof.

The memory may be Random Access Memory (RAM), Read Only Memory (ROM), flash memory, or any other memory or combination thereof suitable for storing control software or other instructions and data. Instructions defining the functions of the invention can be delivered to a processor in a variety of forms, including, but not limited to, permanently stored on a tangible, non-transitory, non-writable storage medium (e.g., a read-only memory device within a computer such as a ROM or a computer I/O accessory readable device such as a CD-ROM or DVD disk, information variably stored on a tangible, non-transitory, writable storage medium such as a floppy disk, removable flash memory and hard drive, or information conveyed to a computer by a communication medium including a wired or wireless computer network.

The disclosed aspects or portions thereof may be combined in ways not listed above and/or not explicitly claimed. In addition, the embodiments disclosed herein may be suitably practiced in the absence of any element not specifically disclosed herein. Accordingly, the invention should not be considered limited to the disclosed embodiments.

As used herein, numerical terms such as "first," "second," and "third" are used to distinguish various elements from one another, and are not intended to indicate any particular order or total number of elements in any particular embodiment. Thus, for example, a given embodiment may include only the second machine learning module and the third machine learning module.

30页详细技术资料下载

上一篇：一种医用注射器针头装配设备

下一篇：用于产生工作区体积和识别外科器械的可及工作区的系统和方法

Medical device positioning and tracking system

相关技术

网友询问留言