Patent Description:
As medical devices such as fluid delivery pumps become more lightweight and mobile, they are increasingly susceptible to theft and improper removal. Conventional theft prevention technologies such as RFID tags, security cameras, etc., are expensive and difficult to administer, making it difficult to reduce theft or improper removal of medical devices. Tags of any sort, if used, are often very visible and easy to remove. Surveillance is easy to avoid because the medical device can be removed under cover by a person exiting a hospital environment.

From the prior art document <CIT> is known which discloses a medical measuring device and a medical measuring system.

The present invention relates to a medical device operable to:.

The present invention also relates to a computer system comprising:.

The invention is based on the object of designing and further developing the medical device and computer system described above in such a way that theft is deterred without risking a patient's life.

The object is solved by the medical device in that in response to being unable to communicate with the remotely located management resource to obtain authorization: provide the same level of functionality provided the last time it was granted that authorization.

The object is further solved by the computer system comprising a medical device according to any one of claims <NUM> to <NUM>.

Embodiments herein include a novel approach to medical device theft prevention. A medical device is configured to operate only in a specific healthcare enterprise to which the medical device is assigned. When the medical device determines an attempt is being made to operate it in a foreign healthcare enterprise (i.e., a domain that is different than a domain to which the medical device is originally assigned), the medical device inhibits at least a portion of its available functionality, reducing its usefulness of providing care for patients within that enterprise.

As further discussed below, any suitable technique can be used to inhibit functionality in a respective medical device when it is unable to receive authorization from a management resource for use in an assigned domain (such as one or more contiguous or disparately located geographical regions). When a user operates a medical device within boundaries of a healthcare enterprise or domain to which it was a previously associated/assigned, the medical device operates in a potentially full functional mode. Conversely, when a user operates the medical device in a healthcare enterprise different from the previously associated/assigned healthcare enterprise, the medical device is denied authorization. In this latter instance, knowing it (i.e., the medical device) is being used improperly, the medical device prevents use of a portion of its functionality.

In accordance with further embodiments, the medical device can be configured to notify subsequent users of the device that it is operating in a foreign enterprise, indicating that the medical device may have been stolen or inadvertently removed from an originally assigned enterprise.

A healthcare enterprise (such as hospital) includes a management resource. The management resource manages operation of one or more medical devices in the healthcare enterprise. To determine what functionality to enable in a respective medical device, a respective medical device first establishes a communication link to communicate in a network environment. Subsequent to establishing the communication link, the medical device initiates communications over the communication link from the medical device to the remotely located management resource. Depending upon feedback from the management resource, the medical device operates in one of multiple different operational modes such as a fully functional mode or a reduced functionality mode. This deters theft of a respective medical device because the medical device supports a substantially reduced set of functionality when the medical device determines that an attempt is being made to operate the respective medical device in a domain that is different from the respective originally assigned domain (such as a healthcare enterprise that owns the medical device).

In accordance with yet more specific example embodiments, to support authorization, each of the medical devices managed by the management resource is assigned a key value unique to the corresponding enterprise domain to which the medical device is assigned/associated. Each of the medical devices assigned for use in a given enterprise stores a copy of the respective unique key value assigned to the assigned enterprise. In one embodiment, to determine what functionality to enable in a respective medical device, the medical device forwards the unique key value assigned to the medical device over the communication link to the management resource. The management resource then performs an analysis to determine whether the unique key value received from the medical device matches its own key (i.e., the unique key assigned to the corresponding enterprise domain).

If the management resource verifies that the unique key received from the medical device matches its own key (such as the key assigned to the enterprise), the management resource notifies the respective medical device that it is authorized to enable the functionality supported by the respective medical device.

Note that in a similar manner, the management resource can be configured to authorize any of multiple medical devices that provide an appropriate assigned unique key value. That is, each of the multiple medical devices acquired for use in the healthcare domain is assigned the unique key associated with the medical enterprise in which the devices will be used. In a manner as previously discussed, upon use, each of the multiple medical devices forwards the unique key to the management resource for verification as previously discussed.

Assume that a respective medical device is removed from the healthcare enterprise. Further assume that the management resource resides in a private network that is only accessible to the medical device if the medical device is located within a wireless communication range of the healthcare enterprise. In such an instance, the medical device is unable to communicate with the management resource disposed in the healthcare enterprise because the medical device resides outside of the private network. Because the medical device is unable to receive authorization from the management resource, the medical device continues to operate in the mode it operated when it last communicated with a healthcare enterprise. In other words, if the medical device had previously operated with reduced functionality such as due to denial of authorization, it would continue to do so until it reconnects to its associated healthcare enterprise. Conversely, if it was previously operating with full functionality such as because the medical device received authorization, it would continue to do so even though it is unable to communicate with the management resource to obtain authorization.

Note that whether or not a respective medical device operates in a full or reduced functionality mode as discussed above depends upon a setting assigned to the respective medical device. The medical device is assigned configuration setting information indicating to the medical device that the medical device is "locked" to a particular healthcare enterprise domain. The configuration setting information can be stored in any suitable location such as in the medical device or at a remote location with respect to the medical device. In response to detecting a condition such as that the medical device is "locked" to a particular healthcare enterprise, the medical device communicates its assigned key to the management resource as discussed above to determine whether to operate in a fully functional mode or a reduced function mode.

Thus, in a manner as previously discussed, the user of a locked medical device can use full functionality of the medical device during conditions in which the management resource authorizes the functions in the medical device. Conversely, during conditions such as when the locked medical device attempts to pass an invalid key to a management resource, the locked medical device operates in a reduced functionality mode. This unique operation deters theft of the medical device because it has less value in a foreign healthcare provider domain when it is set to the locked mode. That is, in a remote domain other than the healthcare provider domain to which the medical device was associated, the locked medical device is prevented from executing one or more operations when denied authorization.

In accordance with still further embodiments not encompassed by the wording of the claims but are considered as useful for understanding the invention, if desired and as further discussed herein, the configuration setting information assigned to the medical device can be set to an "unlocked" mode as opposed to being "locked. " In this latter instance, the medical device can be operated in a similar manner (such as all functionality enabled) regardless of the healthcare enterprise in which it is operating.

These and other more specific embodiments are disclosed in more detail below.

Note that any of the resources as discussed herein can include one or more computerized devices, medical devices, servers, base stations, wireless communication equipment, communication management systems, workstations, handheld or laptop computers, or the like to carry out and/or support any or all of the method operations disclosed herein. In other words, one or more computerized devices or processors can be programmed and/or configured to operate as explained herein to carry out different embodiments of the invention.

Yet other embodiments herein include software programs to perform the steps and operations summarized above and disclosed in detail below. One such embodiment comprises a computer program product including a non-transitory computer-readable storage medium (i.e., any physical computer readable hardware storage medium) on which software instructions are encoded for subsequent execution. The instructions, when executed in a computerized device (e.g., computer processing hardware) having a processor, program and/or cause the processor to perform the operations disclosed herein. Such arrangements are typically provided as software, code, instructions, and/or other data (e.g., data structures) arranged or encoded on a non-transitory computer readable storage medium such as an optical medium (e.g., CD-ROM), floppy disk, hard disk, memory stick, etc., or other a medium such as firmware or shortcode in one or more ROM, RAM, PROM, etc., or as an Application Specific Integrated Circuit (ASIC), etc. The software or firmware or other such configurations can be installed onto a computerized device to cause the computerized device to perform the techniques explained herein.

Accordingly, embodiments herein are directed to a method, system, computer program product, etc., that supports operations as discussed herein.

One embodiment herein includes a computer readable storage medium and/or system having instructions stored thereon. The instructions, when executed by computer processor hardware, cause the computer processor hardware to: initiate communications over a communication link from a medical device to a remotely located management resource; and selectively operate the medical device in one of multiple different operational modes depending on whether the medical device receives current or previous authorization of use from the management resource.

Another embodiment herein includes a computer readable storage medium and/or system having instructions stored thereon. The instructions, when executed by computer processor hardware, cause the computer processor hardware to: from a medical device, establish a communication link; via communications over the communication link, initiate registration of the medical device with a management server that controls an operational mode of the medical device; in response to detecting denial of authorization of the medical device, prevent activation of at least a portion of functionality in the medical device The ordering of the operations above has been added for clarity sake. Note that any of the processing steps as discussed herein can be performed in any suitable order.

Other embodiments of the present disclosure include software programs and/or respective hardware to perform any of the method embodiment steps and operations summarized above and disclosed in detail below.

It is to be understood that the system, method, apparatus, instructions on computer readable storage media, etc., as discussed herein also can be embodied strictly as a software program, firmware, as a hybrid of software, hardware and/or firmware, or as hardware alone such as within a processor, or within an operating system or within a software application.

As discussed herein, techniques herein are well suited for managing and facilitating use of medical devices in different environments. However, it should be noted that embodiments herein are not limited to use in such applications and that the techniques discussed herein are well suited for other applications as well.

Additionally, note that although each of the different features, techniques, configurations, etc., herein may be discussed in different places of this disclosure, it is intended, where suitable, that each of the concepts can optionally be executed independently of each other or in combination with each other. Accordingly, the one or more present inventions as described herein can be embodied and viewed in many different ways.

For additional details and/or possible perspectives (permutations) of the invention(s), the reader is directed to the Detailed Description section and corresponding figures of the present disclosure as further discussed below.

The foregoing and other objects, features, and advantages of the invention will be apparent from the following more particular description of preferred embodiments herein, as illustrated in the accompanying drawings in which like reference characters refer to the same parts throughout the different views. The drawings are not necessarily to scale, with emphasis instead being placed upon illustrating the embodiments, principles, concepts, etc..

Now, more specifically, <FIG> is an example diagram illustrating implementation of a lock feature to control/limit use of functionality in a medical device according to embodiments herein.

As shown in this example embodiment, the medical environment includes private network <NUM> in which medical device <NUM>-<NUM>, medical device <NUM>-<NUM>, etc., reside and are configured to operate.

Note that the medical devices <NUM> as described herein can be any type of medical device. For example, in one embodiment, the each of the medical devices <NUM> is an infusion pump use for delivery of fluid to a respective recipient. Each infusion pump can be configured to support different types of functionality such as first functionality supporting pumping of fluid from the medical infusion pump to a recipient, second functionality supporting retrieval of drug information over a network connection from a remote server resource disparately located with respect to the medical infusion pump, etc..

In this example embodiment, the configuration information <NUM> assigned to each of the medical devices <NUM> is set to a LOCKED operational mode, indicating that the respective medical devices <NUM> must satisfy one or more pre-conditions (such as registration, verification, authentication, authorization, etc.) or have no connection to a management resource within a healthcare enterprise before certain functionality is enabled for use by an operator of the respective medical device.

In accordance with an example embodiment, to determine what functionality to enable in a respective medical device, the respective medical device establishes a communication link to communicate with management resource <NUM>.

More specifically, assume that user <NUM>-<NUM> attempts to operate or execute a function associated with medical device <NUM>-<NUM>. In response to detecting receipt of a respective command and/or activation of the medical device <NUM>-<NUM>, the device manager <NUM>-<NUM> must first determine what portion, if any, of the functionality <NUM>-<NUM> (such as functionality F1, functionality F2, functionality F3, functionality F4, etc.) to enable in the medical device <NUM>-<NUM> for use by the user <NUM>-<NUM>.

More specifically, upon activation or receipt of a respective command with respect to the medical device <NUM>-<NUM> to perform a respective function, as previously discussed, the device manager <NUM>-<NUM> first determines whether it can connect with a management resource. If it cannot communicate with a respective management resource, the medical device operates in the mode it last operated when it connected to a management resource. That is, if the medical device <NUM>-<NUM> was previously authorized for use, then the medical device <NUM>-<NUM> supports full functionality. If the medical device <NUM>-<NUM> was previously denied authorization, then the medical device <NUM>-<NUM> supports limited functionality until receiving further authorization.

In this example embodiment, the medical device <NUM>-<NUM> determines whether or not the medical device is being implemented in a LOCKED or UNLOCKED mode as mentioned above. To determine a respective mode setting, the device manager <NUM>-<NUM> accesses device configuration setting information <NUM>-<NUM> indicating that the medical device <NUM>-<NUM> is set to a LOCKED mode.

Note that the device configuration setting information <NUM>-<NUM> can be stored locally or, alternatively, at a remote location with respect to medical device <NUM>-<NUM>.

Further in this example embodiment, in response to detecting that the device setting information <NUM>-<NUM> indicates that the medical device <NUM>-<NUM> is set to the LOCKED mode, the device manager <NUM>-<NUM> is therefore informed that use of certain functionality <NUM>-<NUM> such as use of functions F3 and function F4 supported by the respective medical device <NUM>-<NUM> are conditional. Functions F1 and F2 may be used by the respective user <NUM>-<NUM> without conditions. In other words, the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> can be configured to enable functions F1 and F2 as a default condition regardless of whether or not the device manager <NUM>-<NUM> is LOCKED or UNLOCKED and receives authorization from the management resource <NUM>.

To enable a portion of functionality such as functions F3 and F4 that require authorization because the device <NUM>-<NUM> is LOCKED, the device manager <NUM>-<NUM> must either be running disconnected from any management resource or register with and/or be authorized by the controller such as management resource <NUM> to use such functionality.

In one embodiment, functionality F1 supports pumping of fluid from the medical device <NUM>-<NUM> (such as an infusion pump) to a recipient, functionality F3 supports retrieval of drug information over a network connection from a remote server resource disparately located with respect to the medical device, etc..

To register/verify authorization of the medical device <NUM>-<NUM> for use of locked functionality F3 and F4, the device manager <NUM>-<NUM> utilizes the network access information <NUM>-<NUM> to identify an appropriate authority to contact. In this example embodiment, the network access information <NUM>-<NUM> indicates the name of a wireless network (such as network XYZ including one or more wireless or WiFi™ access points) to which the medical device <NUM>-<NUM> must connect in order to communicate with management resource <NUM> (control authority). Note that network XYZ can be or include a packet-switched network, the Internet, WiFi™ network, etc., facilitating communications between medical devices <NUM> and a respective manager resource <NUM>. Further note that the manager resource <NUM> can be a logical entity including multiple disparately located servers.

Assume in this example embodiment that the medical device <NUM>-<NUM> is able to establish a respective communication link <NUM>-<NUM> with a wireless access point in network XYZ using the SSID = network name network XYZ and corresponding password/passkey 3567CNM as specified by network access information <NUM>-<NUM>. In one embodiment, the wireless access point in network XYZ requires the medical device <NUM>-<NUM> to use the password/passkey 3567CNM to establish wireless communication link <NUM>-<NUM> as a secured communication link in network XYZ.

Subsequent to establishing the respective communication link <NUM>-<NUM> (such as a secured link), the device manager <NUM>-<NUM> initiates communications with a target recipient such as the management resource <NUM> as specified by the network access information <NUM>-<NUM>. In one embodiment, the server name in network access information <NUM>-<NUM> is a text-based link or string of data specifying a unique name (such as Healthcare Clinic XYZ) of the private network <NUM> in which the medical device <NUM>-<NUM> is configured for use. In such an instance, to access the management resource <NUM>, the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> uses the server name (such as Healthcare Clinic XYZ) to obtain a corresponding network address assigned to the management resource <NUM>. Via subsequent communications addressed to the management resource <NUM> using the corresponding network address, the device manager <NUM>-<NUM> communicates with the management resource <NUM> over network XYZ.

In the embodiment as shown, the private network <NUM> is assigned a corresponding unique identifier value (such as unique key value A). To support authorization, each of the medical devices managed by the management resource <NUM> is also assigned the unique identifier value (i.e., unique key value A). The manager resource <NUM> has knowledge of and keeps track of the unique identifier value A assigned to the private network <NUM> as shown in configuration information <NUM>.

Any suitable technique can be used to provide notification to the management resource <NUM> that a respective medical device has been assigned a corresponding unique identifier value and should be authorized for use of full functionality.

For example, in one embodiment, as previously discussed, the management resource <NUM> managing operation of the medical devices <NUM> stores a copy of the respective unique identifier value A assigned to the private network <NUM>.

In one embodiment, the private network <NUM> (located within an enterprise, domain, etc.) can be a single network within a defined perimeter that provides wireless connectivity to medical devices <NUM> residing within a corresponding geographic regionin the defined perimeter.

Alternatively, note that the private network <NUM> of a particular healthcare provider can include multiple disparately located sub-networks, each of which is assigned the same respective unique identifier value A. For example, private network <NUM> (operated by a particular healthcare provider) can include a first sub-network (such as in a first office location) and a second sub-network (such as in a second office location) that each provide wireless coverage in a disparately located geographical regions. As an illustrative example, the first sub-network can be configured to operate in a first geographical region in a first city, the second sub-network can be configured to operate in a second geographical region in a second city.

Each of the sub-networks can be configured to support wireless connectivity to management resource <NUM> because such sub-networks are part of the same logical private network <NUM>. In such an instance, both of the sub-networks and corresponding medical devices associated with the corresponding service provide and operated therein are assigned the unique identifier value A. The medical devices assigned the unique identifier value A can be used in any of the sub-networks. For example, when a corresponding medical device <NUM>-<NUM> resides within the first geographical region supported by the first sub-network, the medical device <NUM>-<NUM> communicates with the management resource <NUM> through the first sub-network of private network <NUM>. When the corresponding medical device <NUM>-<NUM> resides within the second geographical region supported by the second sub-network, the medical device <NUM>-<NUM> communicates with the management resource <NUM> through the second sub-network of private network <NUM>. When the medical device <NUM>-<NUM> is operated outside of the first geographical region and a second geographical region, the medical device <NUM>-<NUM> is unable to communicate with the management resource <NUM>.

Accordingly, the domain, enterprise, etc., as discussed herein can be a single contiguous geographical region or multiple disparately located geographical regions that are assigned the unique identifier value A.

To determine what functionality to enable in a respective medical device, during the communications as discussed above, a respective medical device <NUM>-<NUM> retrieves respective unique identifier value A (such as a key) from configuration information <NUM>-<NUM> assigned to medical device <NUM>-<NUM>. The respective unique identifier value A can be stored in any suitable location that is not accessible to users.

In general, the device manager <NUM>-<NUM> uses the unique identifier value A assigned to the medical device <NUM>-<NUM> to register the medical device <NUM>-<NUM> with the management resource <NUM>. For example, in a more specific embodiment, the device manager <NUM>-<NUM> communicates a respective registration/verification request to the management resource <NUM> over communication link <NUM>-<NUM> and network XYZ to manager resource <NUM>. The management resource <NUM> responds with an appropriate URI in which to forward the unique identifier value A assigned to the medical device <NUM>-<NUM> over the network XYZ to a target recipient. The device manager <NUM>-<NUM> then forwards the unique identifier value A (key information) to the address as specified by the URI.

The management resource <NUM> then performs an analysis of the received unique identifier value A to determine whether the unique identifier value A received from the medical device <NUM>-<NUM> matches the stored copy of the unique identifier value for private network <NUM>.

If the management resource <NUM> verifies that the unique identifier value A received from the medical device <NUM>-<NUM> matches the unique identifier value stored in configuration information <NUM> indicating that the medical device <NUM>-<NUM> is assigned for use in the private network <NUM>, the management resource <NUM> notifies the respective medical device <NUM>-<NUM> that it is authorized to enable functionality (such as conditional LOCKED functionally F3 and F4) associated with the respective medical device <NUM>-<NUM>.

More specifically, in this example embodiment, the management resource <NUM> compares the received unique identifier value A from medical device <NUM>-<NUM> to a copy of the unique identifier value A assigned to the private network <NUM> and stored in configuration information <NUM>. Since the received unique identifier value from medical device <NUM>-<NUM> matches the unique identifier value A in the configuration information <NUM>, the management resource <NUM>, via communications in a reverse direction over the wireless communication link <NUM>-<NUM> and network XYZ, provides notification to the device manager <NUM>-<NUM> in medical device <NUM>-<NUM> that the medical device <NUM>-<NUM> and corresponding functionality <NUM>-<NUM> is authorized/verified for use in private network <NUM>.

In a similar manner, the management resource <NUM> can be configured to authorize any of multiple medical devices that provide an appropriate assigned unique key value. For example, upon activation of medical device <NUM>-<NUM> for input of a respective command to execute functionality <NUM>-<NUM>, the device manager <NUM>-<NUM> utilizes the network access information <NUM>-<NUM> to establish respective communication link <NUM>-<NUM> with network XYZ in a similar manner as previously discussed. Further in this example, the device manager <NUM>-<NUM> utilizes the unique identifier value A assigned to the medical device <NUM>-<NUM> to register the medical device <NUM>-<NUM> with management resource <NUM>. Upon verification of the medical device <NUM>-<NUM> based on the unique identifier value A forwarded from the medical device <NUM>-<NUM> to the management resource <NUM>, the management resource <NUM> verifies the medical device <NUM>-<NUM> and notifies the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> to enable an appropriate LOCKED portion of functionality <NUM>-<NUM> (such as functionality F3 and F4) associated with the medical device <NUM>-<NUM>.

In accordance with further embodiments, assume that the user <NUM>-<NUM> removes (such as due to theft, inadvertent error, etc.) the medical device <NUM>-<NUM> from the private network <NUM> such that the medical device <NUM>-<NUM> is now out of wireless communication range with respect to network XYZ. In such an instance, the medical device <NUM>-<NUM> is no longer able to communicate over communication link <NUM>-<NUM> and network XYZ to the management resource <NUM>.

Even though the medical device <NUM>-<NUM> is now out of range with respect to the private network <NUM> the device manager <NUM>-<NUM> can be figured to continue enabling use of any or all of functionality <NUM>-<NUM> that does not rely on communication with the management resource <NUM>.

Note that subsequent to authorization of respective functionality <NUM>-<NUM> as described herein, and on an as-needed basis, the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> can be configured to additionally utilize the server name assigned to management resource <NUM> or other server name to communicate over the communication link <NUM>-<NUM> to support functionality F3 and F4.

<FIG> is an example diagram illustrating implementation of a lock feature to control use of a medical device located outside a private network according to embodiments herein.

Upon detecting next use (such as next power-up or after some timeout value) of the medical device <NUM>-<NUM>, as shown in <FIG>, the medical device <NUM>-<NUM> attempts to communicate with the management resource <NUM> to receive authorization to enable functionality LOCKED F3 and F4 in the medical device <NUM>-<NUM>. In this instance, device manager <NUM>-<NUM> again accesses the configuration information <NUM>-<NUM> to learn that it is LOCKED for use in a private network.

Upon detecting a condition such as that the user <NUM>-<NUM> powers up the medical device <NUM>-<NUM> or attempts to use a function associated with the medical device <NUM>-<NUM> while in a foreign network, the device manager <NUM>-<NUM> utilizes the network access information <NUM>-<NUM> to attempt registration/authorization with the management resource <NUM> for use of one or more functions. However, in this instance, because the medical device <NUM>-<NUM> is operated in a foreign network (as opposed to being operated in private network <NUM>), the medical device <NUM>-<NUM> is denied authorization to enable functionality F3 and F4.

In this example embodiment, because the device manager <NUM>-<NUM> is denied authorization, the device manager <NUM>-<NUM> enables only default functionality F1 and F2 in the medical device <NUM>-<NUM>. The device manager <NUM>-<NUM> prevents use of functionality F3 and F4.

Thus, setting the status of the configuration <NUM>-<NUM> in the medical device <NUM>-<NUM> to a LOCKED mode inhibits use of functionality F3 and F4 in a foreign network or at any time subsequent to establishing a connection to that network until the medical device <NUM>-<NUM> is returned to its associated and LOCKED network (private network <NUM>).

Thus, whether or not a respective device manager in a medical device operates in a full or reduced functionality mode depends upon a configuration setting information assigned to the respective medical device. That is, as discussed herein, the user of a LOCKED medical device can use full functionality of the medical device during conditions in which a management resource authorizes or has previously authorized the functions in the medical device.

As described herein, authorization of a respective medical device may be contingent upon the location of the respective medical device. For example, the LOCKED medical device <NUM>-<NUM> can communicate and register with the management resource <NUM> only when the medical device <NUM>-<NUM> is within wireless communication range of network XYZ.

Additionally, during conditions such as when the medical device is unable to communicate with the management resource to obtain authorization, such as because the medical device <NUM>-<NUM> is out of communication range with respect to the network XYZ or simply because there is some type of connection failure, the corresponding device manager <NUM>-<NUM> continues to provide the same level of functionality provided the last time it was granted or denied that authorization. This deters theft of the medical device because it has less value when operating in a healthcare provider domain other than the one in which it is associated and LOCKED.

In accordance with further embodiments, in response to detecting a condition in which the medical device <NUM>-<NUM> is unable to receive authorization from the management resource via communications over a respective communication link as specified by corresponding network access information, the device manager <NUM>-<NUM> provides notification <NUM> on display screen <NUM>-<NUM> to an operator (such as user <NUM>-<NUM>) of the medical device <NUM>-<NUM>.

The notification <NUM> can indicate any suitable type of information such as: i) a medical service provider XYZ to which the medical device belongs or is registered or LOCKED to, ii) that the medical device <NUM>-<NUM> is restricted to operating in a limited operational mode because the medical device <NUM>-<NUM> is LOCKED and has detected that a user attempted to operate it in a foreign network <NUM> (result in denial of authorization), iii) that the medical device <NUM>-<NUM> is stolen, iv) which functionality of the medical device <NUM>-<NUM> is disabled based on its last registration attempt with a management resource, v) which functionality of the medical device <NUM>-<NUM> is enabled for use, etc..

Further embodiments herein can include producing the notification <NUM> to indicate that the medical device <NUM>-<NUM> is configured in a respective LOCKED mode or UNLOCKED MODE depending upon configuration settings <NUM>-<NUM>.

<FIG> is another example diagram illustrating implementation of a lock feature to control use of a medical device located outside of an assigned private network according to embodiments herein.

As shown in <FIG>, a respective user such as user <NUM>-<NUM> can reprogram the network access information <NUM>-<NUM> such that the device manager <NUM>-<NUM> is directed to a different selected server when attempting to verify use of a respective functionality <NUM>-<NUM>.

In this example embodiment, assume that the user <NUM>-<NUM> now possesses medical device <NUM>-<NUM> (potentially after being stolen) and reprograms network access information <NUM>-<NUM> to indicate an SSID of QRS, a password of 66678XX, and a server name specifying management resource <NUM>. Thus, the user <NUM>-<NUM> programs the network access information <NUM>-<NUM> to use the medical device <NUM>-<NUM> at a new location through a new network QRS.

In this instance, when the user <NUM>-<NUM> attempts to use functionality (such as by turning the device to an ON state, by attempting to use any of functionality <NUM>-<NUM>, by providing input to connect to manager resource <NUM>, by inputting a respective command, operating a graphical user interface, etc.) associated with medical device <NUM>-<NUM>, the device manager <NUM>-<NUM> checks the configuration information <NUM>-<NUM> to learn that it is a respective LOCKED device.

Based the on this new configuration setting information <NUM>-<NUM>, the device manager <NUM>-<NUM> attempts to communicate with a management resource as specified by the new network access information <NUM>-<NUM>. The device manager <NUM>-<NUM> uses the SSID value (QRS) to connect with network QRS using password 66678XX.

Via the established communication link with network QRS, the device manager <NUM>-<NUM> attempts to register and/or obtain authorization of the medical device <NUM>-<NUM> for use with management resource <NUM>. However, the management resource <NUM> is unable to authorize and/or authenticate the medical device <NUM>-<NUM> because the management resource <NUM> does not possess the same corresponding unique identifier value A assigned to the medical device <NUM>-<NUM>. In other words, the management resource <NUM> is unable to authorize medical device <NUM>-<NUM> for use, the management resource <NUM> denies authorization. Thus, even though the user <NUM>-<NUM> attempts to use the medical device outside of private network <NUM>, the device manager <NUM>-<NUM> prevents operation of LOCKED functionality F3 and F4.

However, as previously discussed, the medical device <NUM>-<NUM> can be configured to allow use of UNLOCKED default functionality F1 and F2.

<FIG> is an example diagram illustrating implementation of a medical device in an unlocked operational mode according to embodiments herein.

In this example embodiment, assume that a medical service provider operating in network environment <NUM> controls use of medical devices <NUM> (such as including medical device <NUM>-<NUM>, medical device <NUM>-<NUM>, etc.). However, instead of configuring each of the medical devices <NUM> to be in a LOCKED mode as previously discussed, assume that service provider GHI (to which the medical devices <NUM> belong) sets configuration settings <NUM>-<NUM> to indicate that each of the medical devices is set to an UNLOCKED mode. The UNLOCKED mode indicates that functionality associated with the respective medical device <NUM>-<NUM> can be used in any suitable environment.

For example, in response to detecting activation of the medical device <NUM>-<NUM> by the user <NUM>-<NUM>, the device manager <NUM>-<NUM> checks configuration information <NUM>-<NUM> to determine whether or not the medical device <NUM>-<NUM> is locked or unlocked. In this example, in response to detecting that the medical device <NUM>-<NUM> is set to an UNLOCKED mode as specified by the configuration information <NUM>-<NUM>, the device manager <NUM>-<NUM> need not register with the management resource <NUM> and thus enables use of UNLOCKED functionality <NUM>-<NUM> such as functionality F1, functionality F2, functionality F3, and functionality F4.

Note that even though certain functionality such as functionality F3 and functionally F4 may unlocked for use, such functionality F3 and F4 may require that the medical device <NUM>-<NUM> be able to communicate (over any suitable communication link) with management resource <NUM> (such as one or more remote servers) in order to support such functionality. In one embodiment, the management resource <NUM> is configured to provide any suitable data that is required to support functionality F3 and at F4. In a reverse direction, because the medical device <NUM>-<NUM> is UNLOCKED, the medical device <NUM>-<NUM> can be configured to provide any suitable data over network GHI to the management resource <NUM> to support functionality F3 and F4.

In furtherance of retrieving data from or transmitting data to the management resource, the medical device <NUM>-<NUM> includes network access information <NUM>-<NUM> indicating how to connect to the respective management resource <NUM>. Using the network access information <NUM>-<NUM>, the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> establishes a respective connection with network GHI to communicate with management resource <NUM>. Each of the medical devices <NUM> in the network environment <NUM> can be configured to operate in a similar manner.

<FIG> is an example diagram illustrating modification of network access information in a medical device and subsequent use of the medical device in an unlocked operational mode according to embodiments herein.

In this example embodiment, assume that the medical device <NUM>-<NUM> is removed from network environment <NUM> previously discussed in <FIG> and is instead operated in network environment <NUM> shown in <FIG>. In such an instance, because the medical device <NUM>-<NUM> is no longer within the wireless communication range of the network environment <NUM>, the device manager <NUM>-<NUM> may not be able to use network access information <NUM>-<NUM> to communicate with the management resource <NUM>.

However, user <NUM>-<NUM> can overwrite the network access information <NUM>-<NUM> with new network access information <NUM>-<NUM>. In this example, the updated network access information <NUM>-<NUM> overwriting network access information <NUM>-<NUM> indicate a corresponding network LMN and password 3752HJ in which to communicate with the target management resource <NUM>.

Upon activation of medical device <NUM>-<NUM>, because the configuration setting information <NUM>-<NUM> indicates that the medical device <NUM>-<NUM> is set to an UNLOCKED mode, the device manager <NUM>-<NUM> enables all functionality <NUM>-<NUM> including functionality F1, functionality F2, functionality F3, and functionality F4. This functionality requires connectivity with respect to a network, the device manager <NUM>-<NUM> utilizes the replacement network access information <NUM>-<NUM> to communicate with management resource <NUM> associated with network LMN.

As previously discussed, the device manager <NUM>-<NUM> may be required to establish the respective communication link over network LMN to management resource <NUM> in order to transmit and/or receive data with respect to executing functionality F3 and F4. In other words, functionality F3 and F4 may require connection with a corresponding management resource <NUM>.

Thus, in this example embodiment, because each of the medical devices <NUM> is set to a respective UNLOCKED mode, the respective medical devices can be reconfigured for use in any network that supports functionality F3 and F4. This illustrates how the respective medical devices <NUM> can be misappropriated such as stolen or inadvertently removed from one network and used in another network because they are not LOCKED.

<FIG> is an example diagram illustrating modification of configuration information in a medical device to switch from an UNLOCKED mode to a LOCKED mode according to embodiments herein.

Embodiments herein can further include binding a respective UNLOCKED medical device to a respective private network. More specifically, assume that the medical device <NUM>-<NUM> is initially set to the UNLOCKED mode as shown and as previously discussed. The user <NUM>-<NUM> operates medical device <NUM>-<NUM>. This prompts the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> to utilize network access information <NUM>-<NUM> to establish a respective communication link and communicate through network TUV with management resource <NUM>.

Via configuration information <NUM>-<NUM>, the device manager <NUM>-<NUM> detects that the medical device <NUM>-<NUM> is initially set to an UNLOCKED mode. To bind the medical device <NUM>-<NUM> to the private network <NUM>, the management resource <NUM> communicates a LOCK command and unique identifier value B (such as a key value assigned to private network <NUM>) over network TUV to the device manager <NUM>-<NUM> in medical device <NUM>-<NUM>. In response to receiving the LOCK command, the device manager <NUM>-<NUM> initiates modification of configuration information <NUM>-<NUM> to indicate that the medical device <NUM>-<NUM> has been changed to a LOCKED mode. Additionally, the device manager <NUM>-<NUM> modifies the configuration information <NUM>-<NUM> to include the unique identifier value B. Subsequent to updating the configuration information <NUM>-<NUM>, the medical device <NUM>-<NUM> must be used and obtain authorization from the management resource <NUM> in private network <NUM> in order to execute functionality F3 and F4.

Locking the medical device <NUM>-<NUM> and providing the unique identifier value B assigned to the private network <NUM> binds the medical device <NUM>-<NUM> to the private network <NUM>. Thereafter, after binding, the medical device <NUM>-<NUM> must be operated in the private network <NUM> and verified/authorized by the management resource <NUM> in a manner as previously discussed in order for the device manager <NUM>-<NUM> to enable functionality F3 and F4. In a similar manner as previously discussed, the device manager <NUM>-<NUM> can be configured to enable functionality F1 and F2 as a default when the medical device <NUM>-<NUM> is used outside of the private network <NUM>.

<FIG> is an example block diagram of a computer device for implementing any of the operations as discussed herein.

As shown, computer system <NUM> such as a computer device of the present example in any medical device such as medical device <NUM>-<NUM>, medical device <NUM>-<NUM>, medical device <NUM>-<NUM>, <NUM>-<NUM>, etc., can include an interconnect <NUM> that couples computer readable storage media <NUM> such as a non-transitory type of media (i.e., any type of hardware storage medium, tangible storage medium, etc.) in which digital information can be stored and retrieved, a processor <NUM> (e.g., one or more processor devices or hardware processors), I/O interface <NUM>, and a communications interface <NUM>. Communications interface <NUM> enables the computer system <NUM> to communicate with other network elements present in a corresponding network environment.

I/O interface <NUM> provides connectivity to a repository <NUM> and, if present, other devices such as a playback device, display screen, keypad, a computer mouse, etc..

Computer readable storage medium <NUM> can be any hardware storage resource or device such as memory, optical storage, hard drive, floppy disk, etc. In one embodiment, the computer readable storage medium <NUM> stores instructions and/or data.

Communications interface <NUM> enables the computer system <NUM> and corresponding processor <NUM> to communicate with network elements in communication environment <NUM> retrieve information from remote sources such as network elements and communicate with other computers. I/O interface <NUM> enables processor <NUM> to retrieve stored information from repository <NUM>.

As shown, computer readable storage media <NUM> is encoded with device manager application <NUM>-A (e.g., software, firmware, computer code, etc., associated with device manager <NUM>) executed by processor <NUM>. Device manager application <NUM>-A can be configured to include instructions to implement any of the operations as discussed herein.

During operation of one embodiment, processor <NUM> accesses computer readable storage media <NUM> via the use of interconnect <NUM> in order to launch, run, execute, interpret or otherwise perform the instructions in device manager application <NUM>-A stored on computer readable storage medium <NUM>.

Execution of the device manager application <NUM>-A produces processing functionality such as device manager process <NUM>-B in processor <NUM>. In other words, the device manager process <NUM>-B associated with processor <NUM> represents one or more aspects of executing device manager application <NUM>-A within or upon the processor <NUM> in the computer system <NUM>.

Those skilled in the art will understand that the computer system <NUM> can include other processes and/or software and hardware components, such as an operating system that controls allocation and use of hardware resources to execute device manager application <NUM>-A.

In accordance with different embodiments, note that computer system <NUM> may be any of various types of devices, including, but not limited to, a mobile computer, a medical device, infusion pump, a personal computer system, a server resource, a wireless device, base station, phone device, desktop computer, laptop, notebook, netbook computer, mainframe computer system, handheld computer, workstation, network computer, application server, storage device, a consumer electronics device such as a camera, camcorder, set top box, mobile device, video game console, handheld video game device, a peripheral device such as a switch, modem, router, or in general any type of computing or electronic device. The computer system <NUM> may reside at any location or can be included in any suitable resource in communication environment <NUM> to implement functionality as discussed herein.

Functionality supported by the different resources will now be discussed via flowcharts in <FIG>. Note that the steps in the flowcharts below can be executed in any suitable order.

<FIG> is a flowchart <NUM> illustrating an example method according to embodiments herein. Note that there will be some overlap with respect to concepts as discussed above.

In processing block <NUM>, the device manager <NUM>-<NUM> in medical device <NUM>-<NUM> initiates communications over a communication link <NUM>-<NUM> from the medical device <NUM>-<NUM> to a remotely located management resource <NUM>.

In processing block <NUM>, the device manager <NUM>-<NUM> selectively operates the medical device <NUM>-<NUM> in one of multiple different operational modes (such as enables any of one or more different functions) depending on whether the device manager <NUM>-<NUM> of medical device <NUM>-<NUM> currently receives or previously received authorization/verification from the management resource <NUM>.

<FIG> is a flowchart <NUM> illustrating an example method according to embodiments. Note that there will be some overlap with respect to concepts as discussed above.

In processing block <NUM>, the device manager <NUM>-<NUM> of the medical device <NUM>-<NUM> establishes a communication link <NUM>-<NUM> between medical device <NUM>-<NUM> and the wireless access point in network XYZ.

In processing block <NUM>, via communications over the communication link <NUM>-<NUM>, the device manager <NUM>-<NUM> initiates registration/verification of use of the medical device <NUM>-<NUM> with management resource <NUM>. As previously discussed, the device manager <NUM>-<NUM> controls an operational mode of the medical device <NUM>-<NUM> based on feedback from the management resource <NUM>. Controlling an operational mode of the medical device <NUM>-<NUM> includes enabling all or a less-than-all portion of functionality <NUM>-<NUM>.

In processing block <NUM>, in response to detecting an inability of the medical device <NUM>-<NUM> to register/verify the use with the management server <NUM>, the device manager <NUM>-<NUM> prevents activation of at least a portion of functionality supported by the medical device <NUM>-<NUM>. For example, as previously discussed, the device manager <NUM>-<NUM> can prevent use of functions F3 and F4, but allow use of functions F1 and F2 in response to detecting a condition such as that the medical device <NUM>-<NUM> has been currently or previously denied authentication from a management server <NUM> or other server resource that performs authorization checks.

In certain instances, if desired, the device manager <NUM>-<NUM> can be configured to prevent use of all of functionality <NUM>-<NUM> in response to a denial of authentication from a resource such as the management server <NUM>.

Note again that techniques herein are well suited for inhibiting theft of medical devices. However, it should be noted that embodiments herein are not limited to use in such applications and that the techniques discussed herein are well suited for other applications as well.

Claim 1:
A medical device (<NUM>-<NUM>) operable to:
initiate communications over a wireless communication link (<NUM>-<NUM>) from the medical device (<NUM>-<NUM>) to a remotely located management resource (<NUM>); and
support first functionality (F1) and second functionality (F3), the medical device (<NUM>-<NUM>) further operable to:
access configuration information (<NUM>-<NUM>) assigned to the medical device (<NUM>-<NUM>); and
the configuration information (<NUM>-<NUM>) indicating that the medical device (<NUM>-<NUM>) is assigned a lock mode in which the medical device (<NUM>-<NUM>) requires confirmation by the remotely located management resource (<NUM>) that the medical device (<NUM>-<NUM>) resides within a corresponding private network (<NUM>) to execute the second functionality (F3); and
in response to receiving authorization from the remotely located management resource (<NUM>): enable both the first functionality (F1) and the second functionality (F3) in the medical device (<NUM>-<NUM>); and
in response to detecting denial of authorization during a condition in which the medical device (<NUM>-<NUM>) attempts authorization of the medial device (<NUM>-<NUM>) while the medical device (<NUM>-<NUM>) operates in a foreign wireless network outside the corresponding private network (<NUM>):
enable the first functionality (F1) and prevent use of the second functionality (F3) in the medical device (<NUM>-<NUM>); and
in response to being unable to communicate with the remotely located management resource (<NUM>) to obtain authorization:
provide the same level of functionality (F1, F3) provided the last time it was granted that authorization.