Patent Description:
Hemodialysis is a process which employs a machine that includes a dialyzer to aid patients whose renal function has deteriorated to the point where their body cannot adequately rid itself of toxins. The dialyzer may include a semi-permeable membrane, the membrane serving to divide the dialyzer into two chambers. Blood is pumped through one chamber and a dialysis solution through the second. As the blood flows by the dialysis fluid, impurities, such as urea and creatinine, diffuse through the semi-permeable membrane into the dialysis solution. The electrolyte concentration of the dialysis fluid may be set so as to maintain electrolytic balance within the patient. Other purification techniques and processes may additionally be used. Hemodialysis may be generally referred to herein as "dialysis," although it is noted that other types of dialysis exist, such a peritoneal dialysis, and it is noted that the system described herein may be used in connection with any appropriate dialysis system or similar treatment system.

Since dialysis involves removing blood from and returning blood to a patient, performing a dialysis procedure carries a degree of risk. Dialysis treatment requires monitoring of several patient vital signs and dialysis parameters during the dialysis process in order to optimize the overall efficacy of the dialysis procedure, to assess the condition of a fistula (the access to the patient's blood) and to determine the actual purification achieved. Some examples of parameters monitored and analyzed by a dialysis machine or equipment include the blood access flow rate or the rate at which blood flows out of the patient to the dialyzer, a critical parameter; and the ratio Kt/V to measure dialysis efficiency, where K is the clearance or dialysance (both terms representing the purification efficiency of the dialyzer), t is treatment time and V is the patient's total water value.

A processing device coupled to the dialysis machine may be used to manage and oversee the functions of the dialysis process and to, for example, monitor, analyze and interpret patient vital signs and dialysis parameters during a dialysis procedure. The processing device may include a display that displays information concerning the dialysis procedure and include an interface that enables configuration and control of the dialysis machine. A health care practitioner such as a nurse or a patient care technician may oversee the dialysis treatment sessions. Data provided by the dialysis machine and the processing device may aid the health care practitioner in performing his or her duties.

For various descriptions of dialysis systems and components, reference is made, for example, to <CIT>, entitled "Dialysis Systems and Related Components," and <CIT>, entitled "Method and System for Controlling a Medical Device". For a description of a sensor system that may be used in connection with monitoring and issuing alerts during a dialysis procedure, reference is made, for example, to <CIT>, entitled "Wetness Sensor". For various descriptions of interfaces for dialysis systems, reference is made, for example, to <CIT>, entitled "User Interface Processing Device" and <CIT>, entitled "Digital Data Entry Methods and Devices".

In a clinic environment, there may be one health care practitioner for multiple patients, so it is often the case that while the health care practitioner is helping one patient, an alarm may go off for another patient that requires the health care practitioner to investigate and/or attend. In such cases, the health care practitioner may often need to leave a current duty to go to the source of the alarm. Further, where one or more patients are undergoing a dialysis treatment, the health care practitioner may need to adjust the dialysis machine in response to an alarm and/or alert and, in so doing, may often need to re-glove from any prior patient interaction.

Accordingly, it would be desirable to facilitate improvements in the efficient and effective monitoring and control of a dialysis treatment by a health care practitioner overseeing the dialysis treatment, in particular, to enable remote monitoring and control by the health care practitioner of the dialysis treatment and/or dialysis machine and without requiring the health care practitioner to physically contact or even, in some cases, be physically present at the dialysis machine.

<CIT> discloses a method of remotely interfacing with a medical device, comprising providing a head-mounted wearable interface device that enables remote interfacing with a medical device by a user wearing the head-mounted wearable interface device, wirelessly exchanging signals between the head-mounted wearable interface device and the medical device, wherein the signals correspond to a treatment performed using the medical device, processing at least one of the signals at the head-mounted wearable interface device to generate information corresponding to the treatment performed using the medical device, displaying the information on a screen of the head-mounted wearable interface device, and augmenting a real view through the head-mounted wearable interface device with information corresponding to the treatment performed using the medical device.

It is also referred to <CIT>, to an article "<NPL> and to a publication by<NPL>.

According to the system described herein, a method of remotely interfacing with a medical device includes providing a wearable interface device that enables remote interfacing with the medical device by a user wearing the wearable interface device. Signals are wirelessly exchanged between the wearable interface device and the medical device. The signals corresponds to a treatment performed using the medical device. At least one of the signals at the wearable interface device is used to generate information corresponding to the treatment performed using the medical device. The information is displayed on a screen of the wearable interface device. The medical device may be a dialysis machine. The method may further include recognizing, at the wearable interface device, at least one non-contact command input by the user. The non-contact command may be used to remotely control the medical device during the treatment. The non-contact command may include a command to remotely control the medical device during the treatment by modifying at least one parameter of the medical device from a position in which the wearable interface device is out of visual line-of-sight of the medical device. The wearable interface device is a head-mounted device, and the information displayed on the screen of the wearable interface device includes dialysis treatment information. The dialysis treatment information may include an alert concerning the dialysis treatment. The method further includes augmenting a real view through the wearable interface device with information corresponding to the dialysis treatment information.

According further to the system described herein, a non-transitory computer-readable medium stores software that remotely interfaces with a medical device. The software includes executable code that operates a wearable interface device that enables remote interfacing with the medical device by a user wearing the wearable interface device. Executable code is provided that wirelessly exchanges signals between the wearable interface device and the medical device, wherein the signals corresponds to a treatment performed using the medical device. Executable code is provided that processes at least one of the signals at the wearable interface device to generate information corresponding to the treatment performed using the medical device. Executable code is provided that displays the information on a screen of the wearable interface device. The medical device may include a dialysis machine. Executable code may be provided that recognizes, at the wearable interface device, at least one non-contact command input by the user. The non-contact command may be used to remotely control the medical device during the treatment. The non-contact command includes a command to remotely control the medical device during the treatment by modifying at least one parameter of the medical device from a position in which the user is out of visual line-of-sight of the medical device. The wearable interface device is a head-mounted device, and the information displayed on the screen of the wearable interface device includes dialysis treatment information. The dialysis treatment information may include an alert concerning the dialysis treatment. Executable code is provided that augments a real view through the wearable interface device with information corresponding to the dialysis treatment information.

According to the system described herein, a system is provided for enabling remote interfacing with a dialysis machine. The system includes at least one sensor of the dialysis machine that receives and transmits signals corresponding to a dialysis treatment performed by the dialysis machine. A wearable interface device is provided that is worn by a user and that is wirelessly coupled to the at least one sensor. The wearable interface device includes at least one processor that processes received signals into information corresponding to the dialysis treatment and transmits signals used to control the dialysis machine. At least one screen is provided that displays the information corresponding to the dialysis treatment. At least one command recognition component is provided that recognizes a non-contact command input by the user to the wearable interface device. A camera may be provided that captures an image being viewed using the wearable interface device. The wearable interface device controls the dialysis machine when the wearable interface device is out of a visual line-of-sight with the dialysis machine during the dialysis treatment. The screen of the wearable interface device includes a head-mounted display, and the wearable interface device may include a non-transitory computer readable medium storing software that enables control of the dialysis machine during the dialysis treatment using at least one dialysis treatment screen displayed on the head-mounted display.

Embodiments of the system described herein are explained with reference to the several figures of the drawings, which are briefly described as follows.

<FIG> is a schematic illustration of an example of a patient care environment <NUM> in which a patient <NUM> seated in a chair <NUM> receives medical treatment from a treatment station <NUM> and which may be used in connection with an embodiment of the system described herein. The medical treatment is, for example, dialysis. The treatment station <NUM> may be a dialysis treatment station or dialysis machine. A tube or blood line <NUM> transports blood from the patient <NUM> to the dialysis machine <NUM> and back again to the patient <NUM> after processing and treatment in the dialysis machine <NUM>. The dialysis machine <NUM> with display <NUM> may be connected via cabling <NUM> to controller device <NUM> that may include a processor <NUM> which controls a touch screen display <NUM>. In various embodiments, the display <NUM> may display information corresponding to a dialysis treatment being performed by the dialysis machine <NUM>. The touch screen display <NUM> may be mounted on a movable stand <NUM> of the controller device <NUM>. The touch screen display <NUM> may include a touch screen that permits a health care practitioner (HCP), such as a nurse, a patient care technician (PCT), or even a patient, to press the display <NUM> to, for example, to interface with and/or control the dialysis machine <NUM> and/or to enter patient or other data.

According to various embodiments of the system described herein, a sensor <NUM> may be coupled to the controller device <NUM> that may be used to control the dialysis machine <NUM> in connection with transmitting and/or receiving signals to or from a remote or external interface device, as further discussed in detail elsewhere herein. The sensor <NUM> may be wirelessly coupled to one or more wireless interface devices that may be used by a PCT to monitor and/or control a dialysis treatment being performed by the dialysis machine <NUM>. Various embodiments for the one or more wireless interface devices and for the actions and functions of the sensor <NUM> in connection with control of the dialysis machine <NUM> are further discussed in detail elsewhere herein. It is noted that the system described herein may be used with any appropriate wireless communication technology, including, for example, IEEE <NUM>. 11b/g, <NUM>. 11b/g/n, and/or Bluetooth, having appropriate security and encryption standards, and used in conjunction with appropriate wireless networks, with hardware and software components, that support such wireless communication technologies.

<FIG> is a schematic illustration of another example of a patient care environment <NUM> that may be used in connection with an embodiment of the system described herein. In the patient care environment <NUM>, the patient <NUM> is seated in the chair <NUM> and receives medical treatment from a treatment station, such as a dialysis machine <NUM>. The tube or blood line <NUM> is used for transporting blood from the patient <NUM> to the dialysis machine <NUM> and back again to the patient <NUM> after processing and treatment of the blood in the dialysis machine <NUM>. The dialysis machine <NUM> may be configured to communicate with an external network <NUM>, such as a local-area network or the Internet, via a wired or wireless connection <NUM>. The network <NUM> may include one or more databases or other stores of information that securely contain medical information that may be accessed in connection with operation of the system described herein. It is noted that the system described herein may be used in connection with dialysis products produced by Fresenius Medical Care North America of Waltham, Massachusetts, including, for example, Fresenius hemodialysis systems (e.g., a 2008T system).

In an embodiment, the dialysis machine <NUM> may include a display <NUM> with touch screen features. The dialysis machine <NUM> may centralize and consolidate dialysis functions and data entry functions in a single device <NUM>, without, e.g., the use of a separate, external display (e.g., display <NUM> of <FIG>) or a separate, external processor (e.g., processor <NUM>) with associated equipment (e.g., movable stand <NUM>). In an embodiment, the dialysis machine <NUM> may include one or more processors <NUM>, like the processor <NUM>, that may be used in connection with interfacing with, and control of, the dialysis machine <NUM>, for example, by an HCP during a dialysis treatment. Consolidation of functions in a single dialysis machine <NUM> may advantageously reduce the amount of external cabling (e.g., cabling <NUM>) to the device <NUM>. The dialysis machine <NUM> may further reduce the amount of space needed for dialysis treatment and present less crowding of the patient care environment <NUM>. An HCP may be able to focus solely on the dialysis machine <NUM>, or the display <NUM> of the dialysis machine <NUM>, without the HCP's attention being diverted to, e.g., another external display. The dialysis machine <NUM> may reduce power consumption and cost as compared to other, non-centralized implementations.

In an embodiment, a sensor <NUM> may be coupled to the dialysis machine <NUM>. As noted in connection with the sensor <NUM> of <FIG>, and as discussed in detail elsewhere herein, the sensor <NUM> may be used in connection with receiving external or remote signals that may be used to control the dialysis machine <NUM> and/or may be transmit signals in connection with operation of the dialysis machine <NUM>. In another embodiment, a sensor <NUM>', that may be like the sensor <NUM>, but may be separate from the dialysis machine <NUM> and coupled wirelessly thereto. Further, the sensor <NUM>' may also be wireless coupled to the network <NUM>. Accordingly, in various embodiments, functions of the sensor <NUM>' may include control of and/or information chance with the dialysis machine <NUM> via direct communication therewith and/or the sensor <NUM>' may interface with the dialysis machine <NUM> via the network <NUM>. Further discussions of the features and functions of the sensor <NUM> and <NUM>' are discussed in detail elsewhere herein.

<FIG> is schematic illustration of an example implementation <NUM> of the dialysis machine <NUM> according to an embodiment of the system described herein. A user interface processing device (UIP) <NUM> may be configured to share user interface resources, i.e., user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N, between a first processing device <NUM> and a second processing device <NUM>. Both the first and the second processing devices <NUM>, <NUM> may be connected to the UIP <NUM> via respective connections <NUM>, <NUM>, while the user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N are connected to the UIP <NUM> via connections <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. Although one UIP <NUM> is shown in <FIG>, several user interface processing devices may be used to implement the functionality of the UIP <NUM>. The UIP <NUM> is connected to memory <NUM> via a connection <NUM>. Other memory (not shown) may be connected to, and, used by, e.g., the first processing device <NUM> and/or the second processing device <NUM>.

The user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N may include any of a variety of user interface devices known in the art, such as an alphanumeric keyboard or a keypad, a pointing device (e.g., a touchpad, a mouse, or a trackball), a display, and a display with a touch screen. In an implementation, one or more of the user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N may be located external to the HD device <NUM>, specifically user interface device <NUM>-<NUM> is shown remotely located and wirelessly coupled, via wireless connection <NUM>-<NUM>, to the HD device <NUM>. Various embodiments for a user interface device, like that of user interface device <NUM>-<NUM>, being used to wirelessly monitor and/or control the dialysis machine <NUM> are further discussed in detail elsewhere herein.

The second processing device <NUM> of the HD device <NUM> may be configured to communicate with the external network <NUM>, such as a local-area network or the Internet, via a wired or wireless connection <NUM> (and, e.g., via a network interface (not shown)). In other implementations, other processing devices such as the UIP <NUM> or the first processing device <NUM> may communicate with an external network such as the external network <NUM>.

As described herein, the UIP <NUM> may be configured to share the user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N between the first processing device <NUM> and the second processing device <NUM>. The UIP <NUM> may switch focus from the first processing device <NUM> to the second processing device <NUM>. The UIP <NUM> may likewise switch focus from the second processing device <NUM> to the first processing device <NUM>. Specifically, a processing device, such as the first or the second processing device <NUM>, <NUM> of <FIG>, may be said to have focus when the processing device has control of, and/or is controlled by, one or more user interface devices connected to, or communicating with, the processing device (e.g., via one or more user interface processing devices). That is, in this example, when a processing device has focus, a user interface device connected to, or communicating with, the processing device (e.g., via one or more user interface processing devices) will generally affect operation of the processing device, and thereby the dialysis machine <NUM>. User interactions with a user interface device will likewise generally affect operation of the processing device in this instance. Likewise, in this example, when a processing device has focus, the processing device may control a user interface device (such as a video display) connected to, or communicating with, the processing device (e.g., via one or more user interface processing devices).

When a processing device, such as the first or the second processing device <NUM>, <NUM> of <FIG>, does not have focus, then, for example, the processing device may not have control of and/or be controlled by one or more user interface devices connected to, or communicating with, the processing device (e.g., via one or more user interface processing devices). Rather, another processing device may have been given focus. One or more user interface processing devices such as the UIP <NUM> may send protocol data to the processing device, even when the processing device does not presently have focus, so that the processing device may be configured to maintain connections with one or more user interface devices. That is, from the perspective of the processing device, even when the processing device does not have focus, the processing device may have a connection maintained with a user interface device that the processing device does not control and/or that is not controlled by the processing device when the processing device does not have focus. The UIP <NUM> may therefore send protocol data related to the one or more user interface devices to the first and the second processing devices <NUM>, <NUM>, irrespective of which processing device <NUM>, <NUM> has focus.

When a processing device (such as the first processing device <NUM> or the second processing device <NUM>) has focus, one or more user interface processing devices (such as the UIP <NUM>) may manage communications between one or more user interface devices (such as the user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N) and the processing device. The UIP <NUM> may, when the processing device has focus, permit the user interface devices <NUM>-<NUM>, <NUM>-<NUM>, <NUM>-<NUM>. , <NUM>-N to affect operation of the processing device. The UIP <NUM> may switch between modes. The modes may be exclusive of one another and may include a mode in which the first processing device <NUM> has focus, and a mode in which a second processing device <NUM> has focus.

According to various embodiments of the system described herein, one or more of the interface devices <NUM>-<NUM> to <NUM>-N, such as the device <NUM>-<NUM>, may include one or more remote interface devices wireless coupled to the dialysis machine <NUM> via a sensor, such as the sensor <NUM>, <NUM> or <NUM>' discussed in <FIG> and/or <FIG>. The remote interface device(s) <NUM>-<NUM> may include various embodiments and implementations of devices that may be used by a user (such as an HCP) in connection with the monitoring and/or control of the dialysis machine <NUM>, as further discussed in detail elsewhere herein.

<FIG> is a schematic illustration of a more detailed implementation <NUM> of the dialysis machine <NUM> according to an embodiment of the system described herein. A UIP <NUM> is configured to share user interface resources, e.g., a keyboard <NUM>, a pointing device <NUM> (such as a touchpad), a display <NUM> with a touch screen, and/or a remote interface device <NUM>, between a first processing device <NUM> and a second processing device <NUM>. The first processing device <NUM> may be a functional dialysis processing device (FHP) <NUM> that may be configured to monitor dialysis functions of the HD device <NUM>. The second processing device <NUM> may be a microprocessor, such as a standard personal computer (PC) processor, embedded within the HD device <NUM>, and may be referred to as an embedded processing device (EP) <NUM>. The FHP <NUM> is connected to the UIP <NUM> via connections <NUM>, <NUM>, <NUM>, <NUM>, and the EP <NUM> is connected to the UIP <NUM> via connections <NUM>, <NUM>, <NUM>, <NUM>.

The keyboard <NUM> is connected to the UIP <NUM> via connection <NUM>. The pointing device <NUM> is connected to the UIP <NUM> via connection <NUM>. The display <NUM> is connected to a digital video switch <NUM> via connection <NUM>, which is in turn connected to the UIP <NUM>, the FHP <NUM>, and the EP <NUM> via respective connections <NUM>, <NUM>, <NUM>. A touch screen controller <NUM> is connected to the display <NUM> via connection <NUM>, and to the UIP <NUM> via connection <NUM>. Although one UIP <NUM> is shown in <FIG>, several user interface processing devices may be used to implement the functionality of the UIP <NUM>. The UIP <NUM> is connected to memory <NUM> via a connection <NUM>. Other memory (not shown) may be connected to, and, used by, e.g., the FHP <NUM> and/or the EP <NUM>. The EP <NUM>, for example, may utilize a flash memory rather than a conventional hard drive. The HD device <NUM> also includes an audio device <NUM>. The audio device <NUM> is connected to the EP <NUM> via connection <NUM> and the UIP <NUM> via connection <NUM>. <FIG> is intended to show functional connections between devices of the HD device <NUM>, so more or fewer connections may be used than are shown in <FIG>.

As described above, the UIP <NUM> may switch focus from the FHP <NUM> to the EP <NUM>. The UIP <NUM> may likewise switch focus from the EP <NUM> to the FHP <NUM>. When the FHP <NUM> has focus, one or more of the keyboard <NUM>, the pointing device <NUM>, the display <NUM> with a touch screen will generally affect operation of the FHP <NUM>. When the EP <NUM> has focus, the keyboard <NUM>, the pointing device <NUM>, the display <NUM> with a touch screen, and/or the remote interface device <NUM> may generally affect operation of the EP <NUM>. User interactions with the devices <NUM>, <NUM>, <NUM>, <NUM> will likewise generally affect operation of whichever processing device (the FHP <NUM> or the EP <NUM>) has focus. The processing device that has focus (the FHP <NUM> or the EP <NUM>) may control, e.g., the display <NUM> in certain circumstances.

In various implementation, one or more of the user interface devices may be located external to the HD device <NUM>. In this example implementation, when the EP <NUM> has focus, the FHP <NUM> does not have focus, and the FHP <NUM> may not have control of and/or be controlled by the devices <NUM>, <NUM>, <NUM>, <NUM>. When the FHP <NUM> has focus, the EP <NUM> does not have focus, and the EP <NUM> may not have control of and/or be controlled by the devices <NUM>, <NUM>, <NUM>, <NUM>. The UIP <NUM> may send protocol data relating to the devices <NUM>, <NUM>, <NUM> to the EP <NUM> and the FHP <NUM>, even when one of these devices does not have focus, so that the EP <NUM> and the FHP <NUM> may maintain connections with the devices <NUM>, <NUM>, <NUM>. That is, from the perspective of the processing device (EP <NUM> or FHP <NUM>) that does not have focus, a connection at least appears to be maintained with the devices <NUM>, <NUM>, <NUM>, <NUM>, even though these devices <NUM>, <NUM>, <NUM>, <NUM> are not controlled by, and do not control, the processing device that does not have focus. The UIP <NUM> may therefore send protocol data related to the devices <NUM>, <NUM>, <NUM>, <NUM> to the FHP <NUM> and the EP <NUM>, irrespective of which processing device <NUM>, <NUM> has focus. The UIP <NUM> may switch between modes. The modes may be exclusive of one another and may include a mode in which the first processing device <NUM> has focus, and a mode in which the second processing device <NUM> has focus.

In accordance with the system described herein, it is noted that systems and techniques are known for enabling wearable displays, such as glasses, that may provide a controllable display to provide information and a controllable interface to a user wearing the display, and which are sometimes referred to as wearable "augmented reality" systems. For example, "Project Glass" is a research and development program by Google Inc. of Mountain View, California, to develop augmented reality head-mounted displays. Reference is made, for example, to <CIT>, entitled "Multimode Input Field for a Head-Mounted Display," and <CIT>, entitled "Methods and Systems for a Virtual Input Device," both assigned to Google, Inc. , that disclose systems for wearable displays and/or augmented reality systems. Other companies have also developed wearable displays and/or augmented reality systems (see, e.g., <CIT>, entitled "Event Augmentation with Real-Time Information," assigned to Microsoft Corporation of Redmond, Washington, and <CIT>, entitled "Peripheral Treatment for Head-Mounted Displays," assigned to Apple Inc. of Cupertino, California). The system described herein may be used in connection with any appropriate wearable display and/or augmented reality system as implemented in accordance with the features and processing discussed herein.

<FIG> is a schematic illustration of an interface device <NUM> for a head-mounted display that may be a wearable augmented reality system and may be used in accordance with an embodiment of the system described herein. The interface device <NUM> may be an embodiment of the device <NUM> described in <FIG>. The interface device <NUM> may be worn by a user, such as an HCP, in connection with remotely monitoring and/or controlling a dialysis machine or component, such as the dialysis machines <NUM>, <NUM> and/or the controller device <NUM>, during a dialysis treatment, as further discussed in detail elsewhere herein. The interface device is principally shown and described herein in connection with an implementation of the interface device as glasses. However, other head-mounted display implementation may be used in connection with the system described herein. Further, wearable implementations other than head-mounted displays may also be used in connection with the system described herein, including, for example, a wrist watch-style implementation.

The interface device <NUM> may include two sides with screens <NUM>, <NUM> that may be used and function independently of each other. For example, in an embodiment, the screen <NUM> may be clear to enable a user to perform duties remote from the dialysis machine and unobstructed by any visual display during use of the interface device <NUM>, and the screen <NUM> may display information <NUM> used in connection with monitoring and/or controlling the dialysis machine <NUM> and/or component thereof. Alternatively, for example, the screen <NUM> may include a symbol <NUM> that indicates an alert and is presented in a manner that does not obstruct a view through the interface device <NUM>. In other embodiments, different types of information sent to, or generated by, the interface device <NUM> may be displayed on either of the screens <NUM>, <NUM> and, when not in use, both of the sides may be transparent, for example.

In an embodiment, the interface device <NUM> may be communicationally paired with the dialysis machine <NUM> to provide that only the interface device <NUM> is wirelessly controlling the dialysis machine <NUM>. The interface device <NUM> may receive certain information wirelessly transmitted by the sensor <NUM> or the sensor <NUM>', for example, in connection with pairing or authenticating the interface device <NUM> with the dialysis machine <NUM>, and/or in connection with acknowledging control signals sent by the interface device <NUM> to the dialysis machine <NUM> to control the display <NUM> thereof, as discussed herein. In an embodiment, the symbol <NUM> on the screen <NUM> may indicate a successful pairing of the interface device <NUM> with the dialysis machine <NUM>. The screen <NUM> displays identification information in connection with the symbol <NUM> to help ensure the HCP is matching the patient being treated with the proper dialysis machine information being viewed on the interface device <NUM>.

In an embodiment, the information <NUM> may be a screen similar to that being displayed on the display <NUM> of the dialysis machine <NUM> and/or may present other information in connection with the dialysis treatment and/or other functions performed by the HCP for monitoring and/or controlling the dialysis machine <NUM>, as further discussed in detail elsewhere herein. In various other embodiments, the information <NUM> displayed on the interface device <NUM> may include an alert when an alarm of the dialysis machine <NUM> is triggered, an alert when a patient requests help (nurse call), and/or an alert when the dialysis machine <NUM> nears the end of the dialysis treatment. Other types of information may also be displayed including, for example, presenting to the HCP a schedule of patients expected for the dialysis machine <NUM> for the day and/or an alert when a patient does not arrive as expected. According to the system described herein, in a clinical or dialysis setting, while an HCP is performing other duties, including duties for other patients, remote from the dialysis machine <NUM> and dialysis treatment being monitored by the HCP, using the interface device <NUM>, the HCP may remotely monitor and control the dialysis treatment without having to physically contact the dialysis machine <NUM> and/or even without having to be physically present at the dialysis machine <NUM>.

In an embodiment, in connection with the information <NUM> displayed on the interface device <NUM>, the interface device <NUM> may receive information wirelessly transmitted by the sensor <NUM> or the sensor <NUM>' and/or alternatively, may receive information wireless transmitted via the network <NUM>, for example, acting as conduit for information received from the sensor <NUM>, the sensor <NUM>' and/or other component of the dialysis machine <NUM> that is then transmitted to the interface device <NUM> (see, e.g., <FIG>). The interface device <NUM> may include a transceiver device <NUM> that receives and/or transmits signals according to the functionality discussed herein. The transceiver device <NUM> may include one or more processors to process the signals in connection with the display of the information <NUM> and in connection with the transmission of instructions for remotely controlling the dialysis machine <NUM>. The transceiver device <NUM> may further include a memory, and/or other non-transitory computer-readable media, to store data in connection with the information transmitted and/or received by the interface device <NUM> and in connection with the execution of software or other executable code in connection with the operations of the interface device <NUM>.

For example, the interface device <NUM> may include a command recognition device <NUM> that recognizes and interprets commands in connection with operation of the interface device <NUM>, specifically in connection with selection, control and activation of elements on the screens <NUM>, <NUM> of the interface device <NUM>. In various embodiments, the commands may be gestures recognized and used by a gesture-recognition module of the command recognition device <NUM> in connection with the operation of the interface device <NUM> may include, for example, hand gestures, head gestures and/or eye gestures of the user. In other embodiments, the command recognition device <NUM> may include a voice recognition module that enables voice-based control of the interface device <NUM>. The command recognition capability thereby enables hands-free, non-contact operation of the interface device and remote control of the dialysis machine according to the system described herein. Multiple techniques and systems are known for providing non-contact command recognition capability, including gesture and/or voice based command recognition, and reference is made, for purposes of illustrative and descriptive example only, to <CIT>, entitled "Methods and Systems for a Virtual Input Device," and <CIT>, entitled "Multimode Input Field for a Head-Mounted Display".

The interface device <NUM> may further include a camera <NUM> that may be used in connection with capturing images that may be displayed and/or used by the interface device <NUM>, as further discussed in detail elsewhere herein. In various embodiments, the camera <NUM> may also include video capabilities. It is noted that although the devices <NUM>, <NUM> and <NUM> are shown as separate devices, in other embodiments, the functionalities of these devices may be incorporate into one integral device disposed on the interface device <NUM>. Further, the interface device <NUM> may include a power source <NUM>, such as a battery.

The interface device <NUM> may further include an audio input/output device <NUM> that may include a speaker component and a microphone component. The audio device <NUM> may enable the user to hear audible signals that may be transmitted by the sensor <NUM>, <NUM> or <NUM>'. For example, warning or alarm sounds of the dialysis machine <NUM> may be transmitted to interface <NUM> that are heard by the user via the audio device <NUM>. In other embodiments the sensor <NUM>, <NUM> or <NUM>' may also include a speaker and/or a microphone component, such that an intercom-type verbal exchange may be enabled between the user wearing the interface device <NUM> and a patient at the dialysis machine <NUM>. In various embodiments, the audio device <NUM> may also operate in connection with voice command recognition capability of the command recognition device <NUM>, as further discussed elsewhere herein. It is also noted that the processing of the interface device <NUM> may enable the interface device to recognize a verbal communication from the patient that is then converted into text and displayed on one or more of the screens <NUM>, <NUM>. In connection therewith, the processing of the interface device <NUM> may enable translation capabilities. For example, a patient may make a verbal communication at the dialysis machine <NUM> in one language (such as Spanish) and the verbal communication is transmitted as a signal via the sensor <NUM>, <NUM> or <NUM>' to the interface device <NUM>, where the verbal communication is converted into text and then translated into another language (such as English) via processing capabilities of the interface device <NUM> and the translated text displayed on one or more of the screens <NUM>, <NUM> of the interface device <NUM>.

<FIG> is a schematic illustration showing an embodiment of information <NUM>, like that discussed in connection with the information <NUM>, that may be displayed on the interface device <NUM> according to an embodiment of the system described herein. The illustrated embodiment of the information <NUM> is presented by way of example only, and other information, particularly other operational functions and features for controlling and/or monitoring a dialysis treatment, may be displayed and/or controlled in accordance with the system described herein. In the illustrated embodiment, the information <NUM> may include a treatment screen in the display <NUM> of the dialysis machine <NUM> that incorporates the methods and systems for monitoring and/or controlling functions of the dialysis machine <NUM> that are discussed herein. Other systems and interfaces may also be used for controlling a dialysis machine and/or other medical device, and reference is made, for example, to <CIT>, entitled "Method and System for Controlling a Medical Device".

Screen access buttons <NUM> (main access), <NUM> (trends), <NUM> (dialysate), <NUM> (test options), <NUM> (heparin), <NUM> (KtN), <NUM> (BTM), and <NUM> (blood pressure) may be used to access the various treatment screens in a manner that may be similar to that accessed at the display <NUM>, for example, via touch screen functionality of the display <NUM>. For example, as shown in <FIG>, the main access button <NUM> has been activated using the interface device <NUM>, revealing a main treatment access screen <NUM> that may be displayed on the interface device <NUM> and on the display <NUM> of the dialysis machine. It is noted that, in other embodiments, different and/or summarized versions of the information displayed on the display <NUM> of the dialysis machine <NUM> may be displayed on the interface device <NUM>. A different treatment access screen may be displayed, for example, by pressing the different screen access buttons. The main treatment access screen <NUM> provides a general overview of the status of the current treatment. Other treatment screens may offer a more in-depth view of specific aspects of the current treatment, though some treatment screens may have some of the same information displayed as found on other treatment screens.

A status box <NUM> appears at the top left comer of the treatment screen being displayed in the information <NUM>. During normal operation it displays the operation mode of the machine, which in this case is "Dialysis. " During alarm situations, a warning message may be displayed in the status box <NUM>. The message displayed in the status box <NUM> may also prompt the operator for a specific action in situations when the treatment parameters are being set. During normal treatment, a box <NUM> displays the current time and the box <NUM> displays the time of the last blood pressure reading and the patient's blood pressure and pulse rate at that time. Arterial pressure in mmHg is displayed numerically in a meter box <NUM>, and graphically in a bar graph <NUM>. Similarly, venous pressure in mmHg is displayed numerically in a meter box <NUM> and graphically in a bar graph <NUM>, and transmembrane pressure (TMP) in mmHg is displayed numerically in a meter box <NUM> and graphically in a bar graph <NUM>.

A Tx clock button <NUM> may be activated start, or to pause or suspend, the treatment. The Tx clock button <NUM> controls multiple functions of the hemodialysis machine when it is activated. A
UF-goal button <NUM> displays the desired ultrafiltration (UF) in milliliters to be removed during the dialysis treatment. This is typically the difference between the patient's pre and dry weight plus saline or fluid intake during treatment. The UF-time button <NUM> acts as a countdown timer displaying the remaining time in hours and minutes that ultrafiltration will be performed. The timer stops during a blood alarm or whenever the UF pump is stopped. During treatment, A UF-rate button <NUM> displays the current rate of ultrafiltration in milliliters per hour. The rate ultrafiltration occurs is determined by the values entered in a UF-goal button <NUM> and a UF-time button <NUM> and the profile selected with a UF-profile button <NUM>. A UF-removed button <NUM> keeps a running total in milliliters of the fluid drawn from the patient through ultrafiltration. When the value displayed in the UF-Removed button <NUM> is equal to the value entered in the UF-goal button <NUM>, an alarm sounds and the message, "UF GOAL REACHED" is displayed in the status box <NUM>. A UF-profile button <NUM> when touched brings up the UF Profile selection screen. Once a profile is selected, and the operator pushes the main access button <NUM>, the profile selected is displayed in the UF-profile button <NUM>.

A dialysate flow button <NUM> displays the current dialysate flow rate in milliliters per minute. A temperature button <NUM> displays the current temperature in degrees centigrade of the dialysate. Pressing the temperature button <NUM> allows the operator to set the desired temperature, and thereafter the actual temperature is displayed. If the temperature varies too far from the set point, an alarm sounds, a warning message is displayed in the status box <NUM>, and the dialysate goes into bypass. A conductivity button <NUM> displays the current conductivity in millisiemens per centimeter of the dialysate. An RTD (Remaining Time of Dialysis) button <NUM> acts as a countdown timer displaying the amount of treatment time remaining. At the end of treatment (RTD=<NUM>:<NUM>) an alarm sounds and the message "RTD ZERO" is displayed in the status box <NUM>. An SVS profile button <NUM> when touched brings up the Sodium Variation System (SVS) profile selection screen. Once a profile is selected, and the operator pushes the main access button <NUM>, the profile selected is displayed in the SVS profile button <NUM>.

In various embodiments, commands recognized by the interface device <NUM>, such as gesture and/or voice commands, may be used to control functionality of the treatment screen being displayed as information <NUM> on the interface device <NUM>. Accordingly, the mechanism of control of the treatment screen may deviate from control of the treatment screen that is being displayed on the display <NUM> of the dialysis machine <NUM>. For example, whereas the display <NUM> on the dialysis machine <NUM> is controlled by touch screen functionality, treatment screen displayed on the screen <NUM> of the interface device <NUM> may be controlled, for example, by the command-based recognition that may be used to iterate through and/or highlight different buttons of the information <NUM> for the treatment screen that is being displayed on the screen <NUM>. As discussed elsewhere herein, in other embodiments, the information <NUM> being displayed on the interface device <NUM> may present a treatment screen that is somewhat different from the treatment screen presented on the display <NUM> of the dialysis machine <NUM> in a manner that facilitates that command-based recognition control enabled by the interface device <NUM>.

<FIG> is a schematic illustration <NUM> showing a gesture <NUM> by a user that may be used to control an interface device <NUM>', that is like the interface device <NUM> and having similar components thereof but showing a different operational state, according to an embodiment of the system described herein. The screen <NUM> of the interface device <NUM>' shows information <NUM>' in which a section 401a has been activated by the gesture <NUM>, as recognized by the command recognition device <NUM>. The activated section 401a may be a button, such as the main access button <NUM> (see <FIG>) that activates the providing of a main access treatment screen <NUM> to provide a general overview of the status of a current dialysis treatment being performed. The providing of the main access treatment screen <NUM> may be performed by the activation instruction of the button 401a being processed by the transceiver device <NUM> and wirelessly transmitted via a signal <NUM> to the sensor <NUM> of the dialysis machine and/or the sensor <NUM>' either directly or via the network <NUM> (see <FIG>). Updated information concerning the result of the activated section 401a, such as the information for the main access treatment screen <NUM>, may be wirelessly transmitted to the interface device <NUM>' from the dialysis machine <NUM>, which is used by the transceiver device <NUM> to update the screen <NUM> with updated information.

<FIG> is a schematic illustration showing an HCP <NUM> wearing the interface device <NUM> in connection with the monitoring and/or control of a dialysis treatment being performed in the patient care environment <NUM> (see, e.g., <FIG>). The interface device <NUM> enables the HCP <NUM> to remotely monitor and/or control the dialysis machine <NUM> during the dialysis treatment. Information is exchanged among the interface device <NUM> and the dialysis machine <NUM> in a manner as discussed elsewhere herein, and particularly including wireless signal transfers, shown schematically as signals <NUM> from the interface device <NUM> and signal <NUM> or signal <NUM>' from the sensor <NUM> or the sensor <NUM>', respectively. It is noted that the signals <NUM>, <NUM> and <NUM>' are shown schematically and may also include the transfer of information via components of the network <NUM>. Using the interface device <NUM>, the HCP <NUM> may remotely receive alerts and/or other information during the dialysis treatment and may remotely control the dialysis machine <NUM> using, for example, gestures and/or voice in a manner that enables the HCP <NUM> to control, remotely from the patient care environment <NUM>, the dialysis machine <NUM> without being in a visual line-of-sight with the dialysis machine <NUM>, and, of course, without having to touch the dialysis machine <NUM>. The system described herein advantageously enables the HCP <NUM> to perform other duties while also monitoring and/or controlling the dialysis machine <NUM>.

<FIG> is a schematic illustration of an interface device <NUM>', similar to the interface device <NUM>, that is like the interface device <NUM> and having similar components thereof but showing a different functionality and/or operational state, in which the patient care environment <NUM> is being viewed by the HCP through the interface device <NUM>' according to an embodiment of the system described herein. In connection with augmented reality capabilities of the interface device <NUM>, information <NUM> displayed on the interface device <NUM> may be shown in connection with the real time viewing of the patient care environment <NUM>. For example, the information <NUM> may display the station number of the dialysis machine <NUM> and/or may display patient information of the patient <NUM>, such as patient name, age and/or other patient information (e.g., birthdays, etc.). In other embodiments, the interface device <NUM> may be used to document real-time events in connection with treatment, such as emergencies and/or rare or abnormal alarm conditions.

<FIG> is a schematic illustration of an interface device <NUM>, that is like the interface device <NUM> and having similar components thereof but showing a different functionality and/or operational state, in which an image <NUM> has been captured by the camera <NUM> of the interface device <NUM> and displayed on the screen <NUM> of the interface device <NUM> according to the system described herein. Information <NUM> concerning the image <NUM> is displayed on the screen <NUM> of the interface device <NUM>. For example, the image <NUM> is of medications, such as item <NUM>, and the interface device <NUM> is used to document the medications. In other embodiments, the information <NUM> displayed on the interface device <NUM> includes alerts or warnings concerning the item <NUM> in the image <NUM>. In an embodiment, the item
<NUM> may include a matrix or 2D bar code <NUM> (such as a Quick Response (QR) code ) that may be captured by the camera <NUM> and processed by the interface device <NUM>.

<FIG> is a flow diagram <NUM> showing processing steps in connection with receipt and display of information on an interface device, like that described herein, for example, in connection with the interface device <NUM>, <NUM>', <NUM> or <NUM>, according to an embodiment of the system described herein. At a step <NUM>, the interface device receives a wireless signal, transmitted, for example, from a dialysis machine, like the dialysis machine <NUM> or <NUM>, that is performing a dialysis treatment on a patient. The interface device may be worn by a user, such as an HCP who is remotely monitoring the dialysis treatment. After the step <NUM>, processing proceeds to a step <NUM> where the wireless signal is processed by one or more components of the interface device. In an embodiment, the processing of the wireless signal may be in connection with information of the dialysis treatment, including treatments screens and/or other information of the dialysis treatment and/or the dialysis machine.

After the step <NUM>, processing proceeds to a step <NUM> where processed information from the wireless signal is displayed on a display of the dialysis device in connection with navigation of information displayed on the screens of the dialysis device. After the step <NUM>, processing is complete for the described processing iteration of the interface device and dialysis device. It is noted that the processing of the flow diagram <NUM> may be an on-going process in which the interface device repeatedly transmits wireless signals in response to user actions which are then repeatedly received by the dialysis machine. It is noted that the processing steps performed in the flow diagram <NUM> may be performed in connection with the execution of software on a non-transitory computer-readable medium of the interface device by one or more processors of the interface device. In an embodiment, the software may correspond to software that facilitates and/or otherwise interfaces with the dialysis machine in connection with the performance of the dialysis treatment, such as by providing one or more dialysis treatment screens.

<FIG> is a flow diagram <NUM> showing processing steps in connection with command recognition and information transmission in connection with the use of an interface device, like that described herein, for example, in connection with the interface device <NUM>, <NUM>', <NUM> or <NUM>, according to an embodiment of the system described herein. For example, in an embodiment, the processing of the flow diagram <NUM> may follow the processing of the flow diagram <NUM>. At a step <NUM>, one or more components of the interface device recognizes a input command by the user (HCP) who is wearing the interface device. In various embodiments, the input command may be a gesture and/or a voice command that is recognized by the one or more components of the interface device. After the step <NUM>, processing proceeds to a step <NUM> where the input command recognized by the interface device is processed in connection with the information being displayed on the display screen of the interface device.

After the step <NUM>, processing proceeds to a test step <NUM> where it is determined whether the input command corresponds to a control activation of one or more parts of the information being displayed on the interface device that requires transmission from the interface device. For example, the control activation may be in connection with a button being displayed on the interface device. If, at the test step <NUM>, it is determined that the input command is not a control activation command that requires transmission, then processing proceeds to a step <NUM> where the input command is performed at the interface device. For example, in various embodiments, the input command may correspond to scrolling through multiple screens of the information being displayed on the interface device and/or may correspond to the capturing of an image by a camera component of the interface device. After the step <NUM>, processing proceeds to a step <NUM> where updated information is displayed on the interface device.

If, at the test step <NUM>, it is determined that input command corresponds to a control activation command that involves transmission of a wireless signal from the interface device, then processing proceeds to a step <NUM> where the input command is wirelessly transmitted from the interface device. For example, the control activation command may involve activation of a button that controls the dialysis machine and/or dialysis treatment that is being performed and which is being remotely monitored by the HCP wearing the interface device. In such a case, the input command is being wirelessly transmitted to the dialysis machine to control the treatment, such as to adjust a parameter of the dialysis treatment and/or to stop the dialysis treatment, for example. After the step <NUM>, processing proceeds to a step <NUM> where the interface device receives a confirmation that the control activation command has been received and processed by the dialysis machine. The confirmation may be in the form of updated information transmitted to the interface device in processing like that discussed in connection with the flow diagram <NUM>. After the step <NUM>, processing proceeds to the step <NUM>, where updated information is displayed on the interface device. The updated information displayed on the interface device may indicate appropriate processing of the control activation command at the dialysis machine.

After the step <NUM>, processing is complete for the described processing iteration of the interface device. It is noted that the processing of the flow diagram <NUM> may be an on-going process in which the interface device continuously monitors for processes for receipt of input commands. It is noted that the processing steps performed in the flow diagram <NUM> may be performed in connection with the execution of software on a non-transitory computer-readable medium of the interface device by one or more processors of the interface device. In an embodiment, the software may correspond to software that facilitates and/or otherwise interfaces with the dialysis machine in connection with the performance of the dialysis treatment, such as by providing one or more dialysis treatment screens.

<FIG> is a flow diagram <NUM> showing processing in connection with wirelessly transmitting and/or receiving information from the dialysis machine in connection with the dialysis treatment according to an embodiment of the system described herein. In various embodiments, a sensor of the dialysis machine, like that of the sensor <NUM>, <NUM> or <NUM>' discussed herein, may process wireless signals received and/or transmitted in connection with the operation of the dialysis machine and/or dialysis treatment. At a step <NUM>, information of a dialysis treatment being performed by the dialysis machine is wirelessly transmitted from the dialysis machine. In various embodiments, the wireless transmission may include direct broadcast from the sensor of the dialysis machine and/or may include use of one or more components of a network (see, e.g., <FIG>). After the step <NUM>, processing proceeds to test step <NUM> where it is determined whether a wireless signal has been received at the dialysis machine. For example, the wireless signal may be received from an interface device, like the interface device <NUM>, <NUM>', <NUM> or <NUM>, in connection with processing like that discussed in connection with the flow diagram <NUM>. If no wireless signal has been received at the test step <NUM>, processing returns to the step <NUM>.

If, at the test step <NUM>, it is determined that a wireless signal has been received, then processing proceeds to a step <NUM> where the received wireless signal is processed. In various embodiments, the received wireless signal may be a control activation command received from an interface device, like that interface device <NUM>, <NUM>', <NUM> or <NUM>, in connection with the remote control of the dialysis machine by a user (HCP) wearing the interface device. After the step <NUM>, processing proceeds to a step <NUM> where the dialysis machine, e.g., via the sensor <NUM>, <NUM> or <NUM>', transmits a wireless signal that confirms receipt and processing of the received control activation command. For example, the received control activation command may have adjusted a parameter of the dialysis treatment being performed and the confirmation is updated information of the dialysis treatment that is transmitted to the interface device. The updated information may therefore correspond to a treatment screen of the dialysis treatment displayed on the dialysis machine.

After the step <NUM>, processing is complete for the described processing iteration of the interface device. It is noted that the processing of the flow diagram <NUM> may be an on-going process in which the dialysis continuously processes monitors for input commands and/or signals in connection with the system described herein. It is noted that the processing steps performed in the flow diagram <NUM> may be performed in connection with the execution of software on a non-transitory computer-readable medium of the dialysis machine by one or more processors of the dialysis machine, including, in particular, one or more processors of a sensor of the dialysis machine. In an embodiment, the software may correspond to software that facilitates and/or otherwise interfaces with an interface device specifically in connection with remote monitoring and/or control of the dialysis treatment, such as in connection with the providing of dialysis treatment screens. It is noted that the processing of the flow diagram <NUM> may be performed in conjunction with other processing of the dialysis machine, including for example, input of commands directly to the dialysis machine via a touch screen display, for example.

Claim 1:
A method of remotely interfacing with a medical device (<NUM>), comprising:
providing a head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>) that enables remote interfacing with the medical device (<NUM>) by a user (<NUM>) wearing the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>), wherein the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>) includes a camera (<NUM>);
wirelessly exchanging signals between the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>) and the medical device (<NUM>), wherein the signals correspond to a treatment performed using the medical device (<NUM>);
processing at least one of the signals at the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>) to generate information (<NUM>, <NUM>') corresponding to the treatment performed using the medical device (<NUM>);
displaying the information (<NUM>, <NUM>') corresponding to the treatment performed using the medical device (<NUM>) on a screen (<NUM>, <NUM>) of the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>); and
augmenting a real view through the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>) with the information (<NUM>, <NUM>') corresponding to the treatment performed using the medical device (<NUM>),
characterized in that
the screen (<NUM>) displays identification information in connection with a symbol (<NUM>) to help ensure that the user (<NUM>) is matching a patient (<NUM>) being treated with information corresponding to the medical device (<NUM>), wherein the screen (<NUM>) includes the symbol (<NUM>) that indicates an alert and does not obstruct a view through the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>), wherein an image (<NUM>) that has been captured by the camera (<NUM>) is displayed on the screen (<NUM>) of the head-mounted wearable interface device (<NUM>, <NUM>', <NUM>, <NUM>), wherein the image (<NUM>) includes a medication, and wherein one or more of the following is performed: (i) displaying information documenting the medication on the screen (<NUM>), or (ii) displaying an alert concerning the medication on the screen (<NUM>).