MULTI-COMMUNICATION PATH SELECTION AND SECURITY SYSTEM FOR A MEDICAL DEVICE
A multi-communication path selection and security system for a medical device includes a medical device and a computer. The medical device includes a processor, one or more communication interfaces, and a memory that stores configurable settings, medical device policies and profiles associated with a plurality of communication links. The processor establishes a location variable associated with the medical device and when the location variable exceeds a location proximity threshold, the processor alters one or more settings of the medical device based on the medical device policies. The processor establishes a source location variable associated with the computer or an incoming message from the computer, and when the source location variable exceeds a source proximity threshold, the processor alters the incoming message or the settings of the medical device based on the medical device policies.
This application is a continuation of U.S. application Ser. No. 16/317,480, filed Jan. 11, 2019, entitled MULTI-COMMUNICATION PATH SELECTION AND SECURITY SYSTEM FOR A MEDICAL DEVICE, which is a National Stage Entry of Application No. PCT/US2017/041981, filed Jul. 13, 2017, entitled MULTI-COMMUNICATION PATH SELECTION AND SECURITY SYSTEM FOR A MEDICAL DEVICE, which claims benefit of U.S. Provisional Application No. 62/362,299, filed Jul. 14, 2016, entitled MULTI-COMMUNICATION PATH SELECTION AND SECURITY SYSTEM FOR A MEDICAL DEVICE. The contents of the aforementioned application are hereby incorporated by reference in its entirety as if fully set forth herein. The benefit to the foregoing application is claimed under the appropriate legal bias, including, without limitation, under 35. U.S.C. § 119(e).
BACKGROUND OF THE INVENTION Field of the InventionOne or more embodiments of the invention are related to the field of medical device network connectivity and security. Specifically, one or more embodiments relate to selection of multi-communication paths and security systems for medical devices.
Description of the Related ArtGenerally, medical devices include critical data that pertain to the patient and to the healthcare facility. Typically, stolen medical device not only impact the critical availability required for potentially life-sustaining activities or therapy, but also the medical device may be reverse engineered by third parties to hack into and access such critical data.
Generally, customers and patients of the medical devices have no way of specifying how to restrict or lock down usage of the medical device if the medical device is deemed stolen or if an attempt is being made to access the medical device in unauthorized manner or by an unauthorized user. Typically, the current way to track medical devices is based on where the medical device was last registered, for example with a hospital or clinic using a software-based application. For example, generally, the medical devices may be tracked by finding the approximate location based on an access point associated with the registration. Such tracking methods typically result in several drawbacks, including wherein the medical device must generally remain connected to the registration software being used, the location determined is only an approximation, and the medical device is thus capable of being removed and used in an unauthorized or unintended manner at any geographic location.
In addition, generally, while using such medical devices, customers and patients of the medical devices have no way of restricting or filtering out incoming connections to the medical device based on geographic preferences. For example, typically, such medical devices may include firewall and external devices such as hospital system may not be capable of ingress filtering based on where the Internet protocol (IP) connection originated.
Generally, medical devices have been incorporated with wireless technologies; however such wireless technologies are limited regarding defining which wireless technology to use for the services provided by each of the medical devices. Typically, such medical devices lack a wireless technology selection system that is dependent on medical device usage scenarios and that is specific to the type of medical device. As such, generally, customers and patients of the medical devices and hospitals associated with the medical devices have no way of ensuring that critical functions of the medical devices remain continuously active during low or no network connectivity, such as when a Wi-Fi connection degrades or becomes unavailable, during therapy.
With respect to the types of communication used by electronics devices, current communications technologies include regulated and unregulated types. For example, cell phones typically operate in a frequency spectrum that is regulated and assigned by is the United States Federal Communication Commission and similar agencies in other jurisdictions. Whereas, Wi-Fi, Bluetooth, ZigBee, RFID and infrared communication technologies typically use frequency spectrums that are not regulated or specifically assigned.
For at least the limitations described above, there is a need for a system that secures medical devices and any data associated therewith, that tracks the medical devices based on geographical coordinates, and that enables selection of communication paths between the medical devices and external devices using regulated and unregulated wireless technologies based on the specific usage scenarios and critical availability needs of the medical devices.
SUMMARY OF THE INVENTIONThe following simplified summary of various embodiments of the invention is presented to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. The following summary merely presents some concepts of the disclosure in a simplified form as a prelude to the more detailed description provided below.
One or more embodiments of the invention include a multi-communication path selection and security system for a medical device. In at least one embodiment, the multi-communication path selection and security system includes at least one medical device and at least one computer located remotely to the at least one medical device. In one or more embodiments, the at least one medical device may include an infusion pump. In at least one embodiment, the at least one medical device includes a processor, a bi-directional communication interface, and a memory. In one or more embodiments, the memory may store one or more configurable settings, one or more medical device policies, and one or more medical device service profiles associated with a plurality of network communication links.
By way of at least one embodiment, the at least one computer includes a computer network interface and a wireless multi-communication path selection engine. In one or more embodiments, the at least one computer may communicate with the at least one medical device via the computer network interface over a network. In at least one embodiment, the processor may establish a network connection using a bidirectional communication link from the plurality of network communication links based on one or more of the one or more configurable settings, the one or more medical device policies, one or more medical device service profiles, and input received from the wireless multi-communication path selection engine.
One advantage of the present invention is that the policy engine would not need to be a one-size-fit-all solution for the hospitals/customers, and each hospital/customer would be able to decide what policies make most sense for them to operate the medical devices tailored to their needs.
According to one or more embodiments, the processor may establish a location variable associated with the at least one medical device and when the location variable exceeds a pre-defined location proximity threshold, the processor may alter one or more settings of the at least one medical device, based on the one or more medical device policies. In at least one embodiment, the processor may establish a source location variable associated with one or more of the at least one computer and an incoming message from the at least one computer, and when the source location variable exceeds a predefined source proximity threshold, the processor may alter one or more of the incoming message or the one or more settings of the at least one medical device, based on the one or more medical device policies.
In one or more embodiments, the one or more profiles may be associated with a plurality of geographical locations and/or wireless network communication interfaces. In at least one embodiment, the at least one computer may prioritize the plurality of network communication links based on the one or more medical device policies. In one or more embodiments of the invention, the one or more configurable settings and the one or more medical device policies may be determined and accepted from a user located remotely to the at least one medical device. By way of at least one embodiment, the location variable or source location variable or both may include a relative proximity between the at least one medical device and the at least one computer.
According to at least one embodiment, the processor may alter one or more settings of the at least one medical device to limit or otherwise alter network connectivity of the at least one medical device when a predefined distance between the at least one medical device and the at least one computer is detected. In one or more embodiments, the processor may alter one or more settings of the at least one medical device to limit therapy administration capabilities of the at least one medical device. In at least one embodiment, when the at least one medical device exceeds the pre-defined location proximity threshold, the processor may alter settings of the at least one medical device to reset the one or more settings of the at least one medical device to factory default settings. In at least one embodiment, when the at least one medical device exceeds the pre-defined location proximity threshold, the processor may alter settings of the at least one medical device to disable or limit network connectivity, device debug capabilities. In another embodiment, the medical device might be assigned a specific location within a care facility and a pre-defined or preconfigured radius can be established such that when the medical device is moved outside of the perimeter established at the pre-defined radius from its original location, the processor will take one or more of the actions described above or further below.
In one or more embodiments of the invention, when the at least one medical device exceeds the pre-defined location proximity threshold, the processor may transmit a message to an external device. In at least one embodiment, the message may include a geographic location of the at least one medical device. In one or more embodiments, the message may include an alert indicating wherein the at least one medical device is stolen. By way of at least one embodiment, when the at least one medical device exceeds the pre-defined location proximity threshold, the processor may lock down or otherwise alter device debug capabilities of the at least one medical device.
In one or more embodiments, the location variable may include a geographic location of an Internet Protocol (IP) address of the at least one medical device. In at least one embodiment, the source location variable may include a geographic location of an Internet Protocol (IP) address of an external device attempting to connect with the at least one medical device.
In an embodiment, a system for improving security of an infusion pump can include a memory and a hardware processor. The memory can store a selected geographical area. The hardware processor can determine a location of an infusion pump. The hardware processor can determine whether the location is outside of the selected geographical area. The hardware processor can further alter a functionality of the infusion pump based on the determination that the location of the infusion pump is outside of the selected geographical area.
The system of the preceding paragraph can include can have any sub-combination of the following features: wherein the hardware processor is further configured to reset the infusion pump to a factory default setting; wherein the hardware processor is can to disable a device debugging mode of the infusion pump; wherein the hardware processor can to disable infusion capabilities of the infusion pump; wherein the functionality comprises network connectivity and wherein the hardware processor is further configured to disable a network interface of the infusion pump; wherein the hardware processor can transmit a message to a server, wherein the message comprises the location of the infusion pump; wherein the location is determined based on a global positioning system; wherein the location is determined based on one or more network connections of the infusion pump; receive a message from a first computer, wherein the first computer is remote to the infusion pump; determine a remote location of the first computer; determine a distance between the infusion pump and the first computer based on the determined location of the infusion pump and the remote location of the first computer; determine that the distance exceeds a predetermined threshold distance; limit the functionality of the infusion pump based on the determination that the distance exceeds the predetermined threshold distance; wherein the hardware processor is further configured to select a network access protocol based on the location of the infusion pump; wherein the selection of the network access protocol is further based on a quality of service required at the location of the infusion pump; wherein the selection of the network access protocol is further based on an operation of the infusion pump; and wherein the selection of the network access protocol is further based on a hospital policy.
The system of the preceding paragraph can have any sub-combination of the following features: wherein the hardware processor is further configured to reset the infusion pump to a factory default setting; wherein the hardware processor is can to disable a device debugging mode of the infusion pump; wherein the hardware processor can to disable infusion capabilities of the infusion pump; wherein the functionality comprises network connectivity and wherein the hardware processor is further configured to disable a network interface of the infusion pump; wherein the hardware processor can transmit a message to a server, wherein the message comprises the location of the infusion pump; wherein the location is determined based on a global positioning system; wherein the location is determined based on one or more network connections of the infusion pump; receive a message from a first computer, wherein the first computer is remote to the infusion pump; determine a remote location of the first computer; determine a distance between the infusion pump and the first computer based on the determined location of the infusion pump and the remote location of the first computer; determine that the distance exceeds a predetermined threshold distance; limit the functionality of the infusion pump based on the determination that the distance exceeds the predetermined threshold distance; wherein the hardware processor is further configured to select a network access protocol based on the location of the infusion pump; wherein the selection of the network access protocol is further based on a quality of service required at the location of the infusion pump; wherein the selection of the network access protocol is further based on an operation of the infusion pump; and wherein the selection of the network access protocol is further based on a hospital policy.
In certain embodiments, a method for improving security of an infusion pump includes storing a selected geographical area in a memory. The method can further include determining a location of an infusion pump. The method can also include determining whether the location is outside of the selected geographical area. The method includes altering a functionality of the infusion pump based on the determination that the location of the infusion pump is outside of the selected geographical area.
The method of the preceding paragraph can have any sub-combination of the following features: wherein the hardware processor is further configured to reset the infusion pump to a factory default setting; wherein the hardware processor is can to disable a device debugging mode of the infusion pump; wherein the hardware processor can to disable infusion capabilities of the infusion pump; wherein the functionality comprises network connectivity and wherein the hardware processor is further configured to disable a network interface of the infusion pump; wherein the hardware processor can transmit a message to a server, wherein the message comprises the location of the infusion pump; wherein the location is determined based on a global positioning system; wherein the location is determined based on one or more network connections of the infusion pump; receive a message from a first computer, wherein the first computer is remote to the infusion pump; determine a remote location of the first computer; determine a distance between the infusion pump and the first computer based on the determined location of the infusion pump and the remote location of the first computer; determine that the distance exceeds a predetermined threshold distance; limit the functionality of the infusion pump based on the determination that the distance exceeds the predetermined threshold distance; wherein the hardware processor is further configured to select a network access protocol based on the location of the infusion pump; wherein the selection of the network access protocol is further based on a quality of service required at the location of the infusion pump; wherein the selection of the network access protocol is further based on an operation of the infusion pump; and wherein the selection of the network access protocol is further based on a hospital policy.
In an embodiment, a system for dynamic configuration of security or network protocol of an infusion pump can include a memory and a hardware processor. The memory can store a hospital policy. The hardware processor can retrieve the stored hospital policy. The hardware processor can determine a parameter associated with an infusion pump, wherein the parameter corresponds to one of a plurality of parameters stored in the hospital policy and wherein one or more rules are associated with each of the plurality of parameters. The hardware processor can further identify a rule corresponding to the determined parameter from the stored hospital policy. The hardware processor can also alter a functionality of the infusion pump based on the identified rule.
The system of the preceding paragraph can have sub-combination of the any of the following features: wherein the parameter comprises location of the infusion pump; wherein the parameter comprises quality of service; wherein the parameter comprises signal strength; wherein the parameter comprises a priority associated with an operation of the infusion pump; wherein the rule comprises disabling a network interface of the infusion pump; wherein the rule comprises disabling a device debugging mode of the infusion pump; wherein the rule comprises resetting the infusion pump to a factory default setting; wherein the rule comprises switching network protocol; wherein the hospital policy can be dynamically updated over a network.
In certain embodiments, a method for dynamic configuration of security or network protocol of an infusion pump can include retrieving a stored hospital policy. The method can further include determining a parameter associated with an infusion pump, wherein the parameter corresponds to one of a plurality of parameters stored in the hospital policy and wherein one or more rules are associated with each of the plurality of parameters. The method can also include identifying a rule corresponding to the determined parameter from the stored hospital policy. The method can further include altering a functionality of the infusion pump based on the identified rule.
The method of the preceding paragraph can have sub-combination of the any of the following features: wherein the parameter comprises location of the infusion pump; wherein the parameter comprises quality of service; wherein the parameter comprises signal strength; wherein the parameter comprises a priority associated with an operation of the infusion pump; wherein the rule comprises disabling a network interface of the infusion pump; wherein the rule comprises disabling a device debugging mode of the infusion pump; wherein the rule comprises resetting the infusion pump to a factory default setting; wherein the rule comprises switching network protocol; wherein the hospital policy can be dynamically updated over a network.
The details of these and other embodiments of the disclosure are set forth in the accompanying drawings and description below. Other features and advantages of aspects of the disclosure will be apparent from the description, drawings, and claims.
The above and other aspects, features and advantages of the invention will be more apparent from the following more particular description thereof, presented in conjunction with the following drawings wherein:
A multi-communication path selection and security system and method will now be described. In the following exemplary description numerous specific details are set forth in order to provide a more thorough understanding of embodiments of the invention. It will be apparent, however, to an artisan of ordinary skill that the present invention may be practiced without incorporating all aspects of the specific details described herein. In other instances, specific features, quantities, or measurements well known to those of ordinary skill in the art have not been described in detail so as not to obscure the invention. Readers should note that although examples of the invention are set forth herein, the claims, and the full scope of any equivalents, are what define the metes and bounds of the invention.
In one or more embodiments, the one or more profiles 116 may be associated with a plurality of geographical locations. In at least one embodiment, the at least one computer 120 may prioritize the plurality of network communication links based on the one or more medical device policies 115. In one or more embodiments of the invention, the one or more configurable settings 114 and the one or more medical device policies 115 may be determined and accepted from a user located locally with medical device 110 or remotely to the at least one medical device 110 via any computer that may communicate with medical device 110 for example.
By way of at least one embodiment, the at least one computer 120 includes a computer network interface 121 and a wireless multi-communication path selection engine 122. In at least one embodiment, the at least one medical device 110 bi-directionally communicates with the at least one computer 120. In one or more embodiments, the at least one computer 120 may communicate with the at least one medical device 110 via the computer network interface 121 over a network, shown as a bi-directional arrow as illustrated with exemplary wireless signals. Embodiments may include a multi-communication selection engine 122a on medical device 110 in lieu of multi-communication selection engine 122, or in other embodiments may include both engines 122 and 122a that operate in parallel or in case of failover. Hence, medical device 110 may contain multi-communication selection engine 122a, computer 120 may contain multi-communication selection engine 122, or portions of multi-communication selection engine 122a and multi-communication selection engine 122 may operate in any partial manner to form one functioning multi-communication selection engine. For example, multi-communication selection engine 122a or multi-communication selection engine 122 may operate in a master slave or peer-to-peer or any other relationship so long as system 110 comprises one or more multi-communication selection engine capable of the selection of a particular communication path from a plurality of communication paths.
As shown in
According to at least one embodiment, the processor 111 may alter one or more settings of the at least one medical device 110 to limit network connectivity of the at least one medical device 110 when a predefined distance between the at least one medical device 110 and the at least one computer 120 is detected. In one or more embodiments, the processor 111 may alter one or more settings of the at least one medical device 110 to limit therapy administration capabilities of the at least one medical device 110. In at least one embodiment, the processor 111 may alter one or more settings of the at least one medical device 110 to reset the one or more settings of the at least one medical device 110 to factory default settings.
In one or more embodiments of the invention, when the at least one medical device 110 or the location variable exceeds the pre-defined location proximity threshold, the processor 111 may transmit a message to an external device, such as external device 230, at 305. In at least one embodiment, the message may include a geographic location of the at least one medical device 110. In one or more embodiments, the message may include an alert indicating wherein the at least one medical device 110 is stolen. By way of at least one embodiment, when the at least one medical device 110 or the location variable exceeds the pre-defined location proximity threshold, the processor 111 may lock down or otherwise alter device debug capabilities of the at least one medical device 110, at 306. By way of at least one embodiment, when the at least one medical device 110 or the location variable exceeds the pre-defined location proximity threshold, the processor 111 may limit drug delivery or infusion capabilities of the at least one medical device 110, at 311.
As shown in
By way of at least one embodiment, the location variable or source location variable, or both, may include a relative proximity between the at least one medical device 110 and the at least one computer 120. In one or more embodiments, the location variable may include a geographic location of an Internet Protocol (IP) address of an external device, such as external device 230, attempting to connect with the at least one medical device 110. In at least one embodiment, the source location variable may include a geographic location of an Internet Protocol (IP) address of an external device such as external device 230, attempting to connect with the at least one medical device 110.
By way of at least one embodiment, the at least one computer 120 may include a wireless technology selection controller 410 and a policy engine 420. In an embodiment, the policy engine 420 is a hospital policy engine. In one or more embodiments, the medical device 110, instead of or in addition to the computer 120, may include the policy engine 420 (see
In one or more embodiments, the wireless technology selection controller 410 may determine whether an Internet Protocol (IP) or data connectivity is available on a pre-determined wireless technology, such as Wi-Fi connectivity, cellular network connectivity or a new interface connectivity, for a pre-defined quality of service profile. In at least one embodiment, when a data connectivity is available, the policy engine 420 and the wireless multi-communication selection path engine 122 may transmit data to the at least one external device 230 to enable the at least one external device 230, or at least one user associated with the at least one external device 230, or the policy engine 420, or the wireless multi-communication selection path engine 122 to manually or automatically determine which wireless technology to use. For example, in one or more embodiments, the wireless technology to use may include one or more of the unregulated wireless technology associated with controller 411 and wireless router 210, or the regulated wireless technology associated with controller 412 and cellular network tower 220, or a new network connectivity associated with controller 413. As such, at least one embodiment of the invention may include simultaneous usage of more than one wireless technology, for example to use concurrent services over multiple technologies, using one or more of the WiFi controller 411, the cellular network controller 412 and the new interface controller 413.
According to one or more embodiments, the one or more profiles 116 may include a service profile, a policy profile and a technology profile, as shown in
In one or more embodiments, the technology profile defines the availability and quality of service provided by the various wireless technologies, the regulated, the unregulated or the new interface. In at least one embodiment, input from the technology profile is fed into the wireless multi-communication selection path engine 122. By way of at least one embodiment, one or more of the unregulated wireless technology controller 411, the regulated wireless technology controller 412, and the new interface controller 413 may dynamically update the technology profile as the network characteristics change. In one or more embodiments, the availability of the wireless technology and the network characteristics thereof may be based on or include a plurality of factors such as subscription status, signal quality, signal to noise ratio, etc. In at least one embodiment, the quality of service may be based on or may include various parameters such as best effort or guaranteed bit rate throughput requirements, service priority, packet loss characteristics and latency characteristics of the underlying wireless network connection.
In one or more embodiments, the service profile may be associated with predefined service applications of the at least one medical device 110, such as programs 421, including the manual or automatic therapy programs, software downloads 422, such as firmware downloads, firmware updates or other updates, drug library downloads 423, for example to be used during therapy for the therapy programs, and new services 424, such as new updates, new programs and new service requirements of the at least one medical device 110. In at least one embodiment, the various service applications 421, 422, 423 and 424 may each define an expected minimum required characteristic that the wireless technology to be used must provide in order for the service application, of the at least one medical device 110, to use the selected wireless technology.
In one or more embodiments, the policy profile may feed the selected policy profile to the wireless multi-communication selection path engine 122. In at least one embodiment, the policy profile may determine the selection of the wireless technology and define which wireless technology to use based on one or more usage profiles required by a remote user, such as a hospital, doctor, clinic etc. In one or more embodiments, the usage profiles may include coverage-based usage, priority based usage, role-based usage, service-based usage, or any combination thereof.
By way of at least one embodiment, the coverage-based usage may determine the selection of the wireless technology and define which wireless technology to use based on a policy that determines when it is acceptable to switch from one wireless technology to another when inadequate coverage and/or weak signal strength is detected from one wireless technology of the various wireless technologies. For example, the coverage-based usage policy may determine wherein the unregulated technology, such as using a Wi-Fi technology via the Wi-Fi router 210, may provide inadequate coverage, a weak signal, or both, and therefore determines wherein it is acceptable to switch to the regulated technology, such as to a cellular network technology via the cellular network tower 220.
According to one or more embodiments, the priority based usage may determine the selection of the wireless technology and define which wireless technology to use based on which programs, downloads, updates, messages, services, etc. of the at least one medical device 110 may use regulated technologies and which may use unregulated technologies. In at least one embodiment, the remote user, such as the hospital, doctor, clinic etc., may determine which programs, downloads, updates, updates and/or new services may continuously operate on regulated wireless technologies, and which may continuously operate on unregulated technologies. For example, in at least one embodiment, the priority based usage may indicate wherein auto programming, such as therapy programs or programs 201 of the at least one medical device 110, may continuously operate using regulated wireless technologies, such as 3G, 4G, LTE etc., however the downloads, updates and messages may use unregulated wireless technologies, such as a Wi-Fi network, when available.
In one or more embodiments of the invention, the role-based usage may determine the selection of the wireless technology and define which wireless technology to use based on a determination of whether the at least one medical device 110 is to operate in a life critical or sustaining mode or whether the at least one medical device 110 is to operate on a non-critical mode. For example, in at least one embodiment, when the at least one medical device 110 is to be used in a life critical mode, it is determined wherein the wireless technology to use is the regulated wireless technology, such as 3G/4G, and if not currently in use, the wireless multi-communication selection path engine 122 enables a seamless switch to the regulated wireless technology. However, in one or more embodiments, when the at least one medical device 110 is to be used in a non-critical mode, the wireless multi-communication selection path engine 122 may place various constraints and restrictions on when the regulated wireless technology may be used, and little to no requirements on when the unregulated wireless technology may be used.
In at least one embodiment of the invention, the service-based usage may determine the selection of the wireless technology and define which wireless technology to use based on any new services received, such as services 424. For example, in one or more embodiments, the remote user may offer a new premium service on the at least one medical device 110, such as Internet Protocol multimedia services, wherein a user of the at least one medical device 110, such as a patient, may conduct a remote tele-consultation with the remote user via the at least one medical device 110, such as using a user interface and screen of the at least one medical device 110. As such, the wireless multi-communication selection path engine 122 may determine wherein regulated wireless technologies may be used over unregulated wireless technologies to provide the desired end-to-end quality of service for the premium service provided, for example when the premium service provided requires remote communication.
According to one or more embodiments of the invention, the wireless multi-communication selection path engine 122 may switch or transfer from one wireless technology to another wireless technology seamlessly, such that the connection, programming, updates, data transfer and any communication protocol is continuous, unbroken and uninterrupted during the switch and thereafter.
In one or more embodiments of the invention, policy engine 420 may also couple with or include various profiles 116 for wireless technology as described above, Service, Hospital Policy, the latter of which may include Coverage, Priority, Service and Security usage profiles.
The technology profile in one or more embodiments may also include availability and quality of service provided by the underlying wireless technologies that is fed back into the wireless multi-communication selection path engine(s) 122 and/or 122a. The underlying technology controllers (e.g., Wi-Fi, L TE, etc.) may dynamically update the technology profile as the network characteristics change. The availability may then be based on various factors like subscription status, signal quality, signal to noise ratio, etc. Quality of service may be based on various parameters like Best Effort or Guaranteed Bit rate throughput requirements, service priority, packet loss characteristics and latency characteristics of the underlying connection.
The Service profile in one or more embodiments of the invention may configured for a given service application, (e.g., Auto Program, Drug Library Download, etc.) that indicates the expected minimum characteristics that the wireless service provides for the service application to use the wireless technology.
A hospital customized policy profile may be utilized by the policy engine 420 to feed the selected policy profile into the wireless multi-communication selection engine 122 and/or 122a. The policy profile may determine the selection of the underlying wireless technology based on certain usage profiles specified by the hospital. In one or more embodiments these may include Coverage, Priority, Service and Security usage profiles.
One advantage of the present invention is that the policy engine would not need to be a one-size-fit-all solution for the hospitals/customers, and each hospital/customer would be able to decide what policies make most sense for them to operate the medical devices tailored to their needs.
The Coverage based usage policy may be utilized by the policy engine 420 to determine if it is acceptable to switch to a premium service if inadequate coverage or a weak signal strength is detected on the unregulated technologies. Example scenarios may include network maintenance, downtime, denial of service attack, etc.
The Priority based usage policy may be utilized by a hospital to specify that auto-programing may utilize 3G/4G, but that software updates, or log and status messages would utilize Wi-Fi, when available for example.
The Role based usage policy may be utilized if in life critical I sustaining mode, for example to enable seamless handoff to 3G/4G. If used in non-critical mode, then higher constraints on when 3G/4G can be used may be specified.
The Service based policy may be utilized by a hospital to potentially offer an IMS (IP Multimedia Services) based premium service where a patient could be provided teleconsulting with a nurse/doctor on the pump user interface or UI itself. In this scenario, 3G/4G may be a better fit to provide the desired end-to-end QoS for IMS service for example. In some embodiments, a default hospital policy may be set to provide a highest quality of service, which may require switching to paid cellular connections like 3G or 4G whenever the speed or bandwidth of a WiFi connection does not meet the quality of service parameters. Furthermore, in some locations, WiFi may not be available and paid solutions may be required for network communications.
The Security based usage policy may be utilized by a hospital to specify an antitheft policy where once the medical device or infusion pump detects that there has been an unauthorized removal of the pump from its designated area (which may be handled using techniques such as GPS, WPS, Triangulation, etc.) Policy engine 420 may lock down part of network connectivity, lock down infusion capabilities, perform a device reset to factory defaults, send a message to backend servers regarding the stolen device with geo-location information, alert/SMS the hospital administrator, lock down device debug capabilities for example.
One or more embodiments of the invention may include a pre-defined secure virtual perimeter 510 around the at least one medical device 110. For example, in at least one embodiment, the pre-defined source location proximity threshold, or location proximity threshold, may include the perimeter 510 around the at least one medical device 110. In one or more embodiments, the pre-defined source location proximity threshold, or location proximity threshold, may include a pre-defined geographic radius 520 around the at least one medical device 110.
By way of one or more embodiments, the pre-defined secure virtual perimeter 510 and the pre-defined geographic radius 520 are dependent on geo-coordinates of the at least one medical device 110, as determined by the at least one medical device 110. In at least one embodiment, the at least one medical device 110 may include one or more of global positioning system (GPS) technologies, network triangulation and WiFi Positioning System (WPS) technologies with varying levels of granularity and accuracy to determine its geo-coordinates.
In one or more embodiments, the pre-defined secure virtual perimeter 510 and the pre-defined geographic radius 520 may be determined and set via one or more of the at least one medical device 110, the at least one computer 120 and the at least one external server 230. In at least one embodiment, the pre-defined secure virtual perimeter 510 and the pre-defined geographic radius 520 may be determined and set using geo-lockdown techniques and geo-fencing techniques to control the at least one medical device 110. In at least one embodiment, the geo-lockdown techniques are defined by the at least one medical device 110 that includes an administrator setting defining a given radius or perimeter, such as the pre-defined secure virtual perimeter 510 and the pre-defined geographic radius 520. As such, in one or more embodiments, the administrator setting allows the at least one medical device 110 to be used only within one or more of the pre-defined secure virtual perimeter 510 and the pre-defined geographic radius 520, for the determined geo-coordinates of the at least one medical device 110. For example, using the geo-lockdown techniques, in at least one embodiment, when the at least one medical device 110 exceeds the threshold defined by one or more of the pre-defined secure virtual perimeter 510 and the pre-defined geographic radius 520, and/or when the at least one medical device 110 is being used in an unauthorized manner, as discussed above, the processor 111 may alter one or more settings of the at least one medical device 110, for example based on the one or more medical device policies 115. In at least one embodiment, the one or more medical device policies 115 may be determined and set by the remote user via the at least one external device 230, such as by a hospital, doctor, clinic or any other authorized user. By way of one or more embodiments, the at least one external device 230, or the computer 120, or both, may communicate with the processor 111 to alter one or more settings of the at least one medical device 110, such that the request to alter the one or more settings of the at least one medical device 110 is initiated from the at least one external device 230, or the computer 120, or both.
According to at least one embodiment, the processor 111 may lock down usage of the at least one medical device 110 by altering the one or more settings of the at least one medical device 110 to limit network connectivity of the at least one medical device 100 when a predefined distance between the at least one medical device 110 and the at least one computer 120 is detected, or for example when the at least one medical device 110 is located outside the pre-defined secure virtual perimeter 510 or the pre-defined geographic radius 520, or both. In one or more embodiments, the processor 111 may lock down usage of the at least one medical device 110 by altering one or more settings of the at least one medical device 110 to limit therapy administration capabilities of the at least one medical device 110. For example, in one or more embodiments, the processor 111 may lock down infusion capabilities or any other therapy administration capabilities. In at least one embodiment, the processor 111 may lock down usage of the at least one medical device 110 by altering one or more settings of the at least one medical device 110 to reset the one or more settings of the at least one medical device 110 to factory default settings. As such, in one more embodiments, any critical data on the at least one medical device 110 may be erased.
In one or more embodiments of the invention, when the at least one medical device 110 or the location variable exceeds the pre-defined location proximity threshold, the processor 111 may lock down usage of the at least one medical device 110 and may transmit a message to an external device, such as external device 230. In at least one embodiment, the message may include a current geographic location of the at least one medical device 110, such as the geographic coordinates of the at least one medical device 110 located outside the pre-defined secure virtual perimeter 510 or the predefined geographic radius 520, or both. In one or more embodiments, the message may include an alert indicating wherein the at least one medical device 110 is stolen. By way of at least one embodiment, when the at least one medical device 110 or the location variable exceeds the pre-defined location proximity threshold, the processor 111 may lock down device debug capabilities of the at least one medical device 110. In one or more embodiments, the processor 111 may accept specific pre-defined custom policies from the remote user, such as the hospital, doctor, clinic or any other authorized user. In at least one embodiment, the pre-defined custom policies may include various policies dependent on the laws and regulations of one or more of the remote user, the at least one computer 120, and the at least one external device 230. In one or more embodiments, the pre-defined custom policies may include various protocols dependent on the location and size of one or more of the at least one medical device 110, the at least one computer 120, the at least one external device 230 and the remote user. In at least one embodiment, the pre-defined custom policies may include various protocols dependent on one or more of the type of at least one medical device 110, the type of therapy administered by the at least one medical device 110, the manufacturer of the at least one medical device 110, the power consumption of the at least one medical device 110, and the lifecycle of the at least one medical device 110. As such, in one or more embodiments, the processor 111 may lock down or otherwise alter usage of the at least one medical device 110 based on the pre-defined custom policies and the various policies thereof.
By way of at least one embodiment, the location variable or source location variable, or both, may include a relative proximity between the at least one medical device 110 and the at least one computer 120. In one or more embodiments, the source location variable and/or the location variable may include a geographic location of an Internet Protocol (IP) address of an external device, such as external device 230, attempting to connect with the at least one medical device 110, such that the source IP address of the external device attempting to connect to the at least one medical device 110 is mapped to a specific geographic location. As such, in at least one embodiment, the pre-defined source location proximity threshold, or location proximity threshold, may include a pre-defined geographic radius 520 around the at least one medical device 110.
In one or more embodiments, using the geo-fencing techniques, one or more of the at least one medical device 110, the at least one computer 120 and the at least one external device 230 may include Internet Protocol (IP) geo-location services to determine the source location variable, such as the geographic location, using an Internet Protocol (IP) address of an external device, such as external device 230, attempting to connect with the at least one medical device 110. In one or more embodiments, the processor 111 may enable the at least one medical device 110 to only connect with a source Internet Protocol (IP) address located only within the predefined geographic radius 520, and to not connect to any source Internet Protocol (IP) address located outside the pre-defined geographic radius 520. As such, in at least one embodiment, using the determined geographic location, such as via the geographic coordinates, of the at least one medical device 110 and using the determined Internet Protocol (IP) address and geographic location of the external device attempting to connect to the at least one medical device 110, access to the at least one medical device 110 may be controlled. In one or more embodiments, access to the at least one medical device 110 may be controlled, accepted or denied via one or more of the processor 111, the at least one computer 120 and the at least one external device 230.
For example, one or more embodiments may determine wherein the at least one medical device 110 may be used at a pre-defined location, such as a hospital in San Diego, Calif., and geo-fencing is enabled to enforce a constraint to not allow an external device to connect to the at least one medical device 110 from outside of a pre-determined distance or radius from the pre-defined location, such as outside of a quarter of a mile. As such, in at least one embodiment, any attempt to access the at least one medical device 110 from a source IP address that is mapped to a location within the pre-determined distance or radius from the pre-defined location will be accepted. In one or more embodiments, any attempt to access the at least one medical device 110 from a source IP address that is mapped to a location outside of the pre-determined distance or radius from the pre-defined location will be denied. As such, in at least one embodiment, the at least one medical device 110 may be protected using an added cyber security protection layer, for example in addition to ingress filtering that may be provided by the remote user or by the default factory settings.
It will be apparent to those skilled in the art that numerous modifications and is variations of the described examples and embodiments are possible in light of the above teaching. The disclosed examples and embodiments are presented for purposes of illustration only. Other alternate embodiments may include some or all of the features disclosed herein. Therefore, it is the intent to cover all such modifications and alternate embodiments as may come within the true scope of this invention.
Claims
1.-43. (canceled)
44. A system for dynamic configuration of security or network protocol of an infusion pump, the system comprising:
- a memory configure to store a hospital policy; and
- a hardware processor configured to: retrieve the stored hospital policy; determine a parameter associated with an infusion pump, wherein the parameter corresponds to one of a plurality of parameters stored in the hospital policy and wherein one or more rules are associated with each of the plurality of parameters; identify a rule corresponding to the determined parameter from the stored hospital policy; and alter a functionality of the infusion pump based on the identified rule.
45. The system of claim 44, wherein the parameter comprises location of the infusion pump.
46. The system of claim 44, wherein the parameter comprises quality of service.
47. The system of claim 44, wherein the parameter comprises signal strength.
48. The system of claim 44, wherein the parameter comprises a priority associated with an operation of the infusion pump.
49. The system of claim 44, wherein the rule comprises disabling a network interface of the infusion pump.
50. The system of claim 44, wherein the rule comprises disabling a device debugging mode of the infusion pump.
51. The system of claim 44, wherein the rule comprises resetting the infusion pump to a factory default setting.
52. The system of claim 44, wherein the rule comprises switching network protocol.
53. The system of claim 44, wherein the hospital policy can be dynamically updated over a network.
54. A method for dynamic configuration of security or network protocol of an infusion pump, the method comprising:
- retrieving a stored hospital policy;
- determining a parameter associated with an infusion pump, wherein the parameter corresponds to one of a plurality of parameters stored in the hospital policy and wherein one or more rules are associated with each of the plurality of parameters;
- identifying a rule corresponding to the determined parameter from the stored hospital policy; and
- altering a functionality of the infusion pump based on the identified rule.
55. The method of claim 54, wherein the parameter comprises location of the infusion pump.
56. The method of claim 54, wherein the parameter comprises quality of service.
57. The method of claim 54, wherein the parameter comprises signal strength.
58. The method of claim 54, wherein the parameter comprises a priority associated with an operation of the infusion pump.
59. The method of claim 54, wherein the rule comprises disabling a network interface of the infusion pump.
60. The method of claim 54, wherein the rule comprises disabling a device debugging mode of the infusion pump.
61. The method of claim 54, wherein the rule comprises resetting the infusion pump to a factory default setting.
62. The method of claim 54, wherein the rule comprises switching network protocol.
63. The method of claim 54, wherein the hospital policy can be dynamically updated over a network.
Type: Application
Filed: Feb 2, 2023
Publication Date: Aug 10, 2023
Inventors: Harsh DHARWAD (San Clemente, CA), Hrishikesh Anil DANDEKAR (San Clemente, CA)
Application Number: 18/105,129
