Systems and methods for provisioning remote operation of medical equipment using an interface controller device

Abstract

Disclosed herein is an interface controller device, including: a plurality of solenoids, wherein each solenoid is disposed on the interface controller device in a location corresponding to a location of a physical input of medical interfacing equipment; a display; memory storing an interface layout database that maps each solenoid on the interface controller device to a corresponding physical input on the medical interfacing equipment, and a hardware processor.

Description

SYSTEMS AND METHODS FOR PROVISIONING REMOTE OPERATION OF MEDICAL EQUIPMENT USING AN INTERFACE CONTROLLER DEVICEFIELD OF TECHNOLOGY[1] The present disclosure relates to the field of biomedical technology, and, more specifically, to systems and methods for provisioning remote operation of medical equipment using an interface controller device.BACKGROUND[2] Due to advancements in communication technology, the medical field has experienced improved accessibility. Medical professionals performing checkups no longer need to be physically present with their patients. For example, patients are now able to video call their doctors during an appointment instead of going into a hospital or clinic. Likewise, medical specialists that are unable to be physically present in a hospital can remotely monitor operations and provide guidance to technicians, nurses, and other doctors present at the hospital.[3] However, conventional remote assistance fails to meet the requirements of performing complex remote tasks such as taking control of different types of medical equipment from a remote setting and executing commands in near real-time. As medical equipment continues to advance exponentially in sophistication and functionality, it has becoming increasingly difficult to perform remote tasks, which further exposes the weaknesses of conventional remote assistance.[4] Furthermore, several types of medical equipment include specialized input devices (e.g., keyboards, intercoms, etc.) that cannot be remotely controlled. These specialized input devices require a local user to manually press the physical inputs of the specialized input devices. Remote operation of medical equipment can be greatly improved if remote access over the specialized input devices (without the need for a local user) is realized.SUMMARY[5] To overcome the shortcomings of conventional remote assistance technology in the medical field, the present disclosure describes systems and methods that enable the remote operation of medical equipment (e.g., magnetic resonance imaging (MRI) & computerized tomography (CT) equipment) through a platform that combines robotics, hardware, and software in a non-invasive solution. Through the platform, users are also able to stream medical sessions (e.g., MRI, CT, PET-CT, etc.), which improves collaboration, consulting, support, professional training, and quality control. More specifically, the present disclosure describes an interface controller device that can be remotely controlled and is configured to execute manual button presses on a medical interfacing equipment (used interchangeably with medical input device or specialized input device) attached to medical equipment.[6] In some aspects, the techniques described herein relate to an interface controller device, including: a plurality of solenoids, wherein each solenoid is disposed on the interface controller device in a location corresponding to a location of a physical input of medical interfacing equipment; a display; memory storing an interface layout database that maps each solenoid on the interface controller device to a corresponding physical input on the medical interfacing equipment; a hardware processor configured to: generate, on the display, a user interface depicting a plurality of virtual options, wherein each virtual option corresponds to a physical input on the medical interfacing equipment; receive a first selection of a first virtual option of the plurality of virtual options, wherein the first virtual option is a digital representation of a first physical input on the medical interfacing equipment; identify, using the interface layout database, a first solenoid of the plurality of solenoids that corresponds to the first virtual option; transmit a first command to the first solenoid to establish contact with the first physical input, wherein the first solenoid is configured to execute the command.[7] In some aspects, the techniques described herein relate to an interface controller device, wherein the first physical input is a button, and wherein first command is to apply a pressing force on the first physical input for at least a threshold period of time.[8] In some aspects, the techniques described herein relate to an interface controller device, wherein the hardware processor is further configured to: receive, from a computingdevice remotely connected to the interface controller device, a second selection of a second virtual option of the plurality of virtual options; identify, using the interface layout database, a second solenoid of the plurality of solenoids that corresponds to the second virtual option; transmit a second command to the second solenoid to establish contact with the second physical input, wherein the second solenoid is configured to execute the command.[9] In some aspects, the techniques described herein relate to an interface controller device, wherein the second physical input is a dial, and wherein second command is to apply a rotational force on the second physical input for at least a threshold period of time.

[0010] In some aspects, the techniques described herein relate to an interface controller device, wherein the second solenoid includes a rotating motor.

[0011] In some aspects, the techniques described herein relate to an interface controller device, wherein the first solenoid and the second solenoid simultaneously execute the first command and the second command, respectively.

[0012] In some aspects, the techniques described herein relate to an interface controller device, further including: a plurality of light sensors, wherein each light sensor is disposed on the interface controller device in a location corresponding to a location of an LED light of the medical interfacing equipment; wherein the hardware processor is further configured to: determine, using the plurality of light sensors, that at least one LED light of the medical interfacing equipment is illuminated; generate, on the display, an indication that the at least one LED light of the medical interfacing equipment is illuminated.

[0013] In some aspects, the techniques described herein relate to an interface controller device, wherein the hardware processor is further configured to transmit the indication to a remote computing device connected to the interface controller device.

[0014] In some aspects, the techniques described herein relate to an interface controller device, wherein the display is a touchscreen display.

[0015] In some aspects, the techniques described herein relate to an interface controller device, further including an insert that at least partially houses the medical interfacing equipment.

[0016] In some aspects, the techniques described herein relate to an interface controller device, wherein the hardware processor is further configured to generate entries for a log,wherein each entry includes a timestamp, a received selection, a transmitted command, and attributes of the transmitted command.

[0017] In some aspects, the techniques described herein relate to an interface controller device, wherein the attributes includes one or more of: a force value, an amount of time a force was applied, an identifier of a solenoid, and an identifier of a physical input.

[0018] In some aspects, the techniques described herein relate to an interface controller device, further including: a microphone disposed in a location on the interface controller device corresponding to a location of a speaker on the medical interfacing equipment; and a speaker disposed in a location on the interface controller device corresponding to a location of a microphone on the medical interfacing equipment.

[0019] The above simplified summary of example aspects serves to provide a basic understanding of the present disclosure. This summary is not an extensive overview of all contemplated aspects, and is intended to neither identify key or critical elements of all aspects nor delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present one or more aspects in a simplified form as a prelude to the more detailed description of the disclosure that follows. To the accomplishment of the foregoing, the one or more aspects of the present disclosure include the features described and exemplarily pointed out in the claims.BRIEF DESCRIPTION OF THE DRAWINGS

[0020] The accompanying drawings, which are incorporated into and constitute a part of this specification, illustrate one or more example aspects of the present disclosure and, together with the detailed description, serve to explain their principles and implementations.

[0021] FIG. 1 is a diagram illustrating a remote operation system.

[0022] FIG. 2 is a diagram illustrating network connections in the remote operation system using a keyboard, video, and mouse (KVM) component.

[0023] FIG. 3 is a diagram illustrating an exemplary user interface for accessing medical equipment remotely.

[0024] FIG. 4 is a diagram illustrating an interface controller device and a medical interfacing equipment.

[0025] FIG. 5 is a diagram illustrating an interface controller device placed on a medical interfacing equipment.

[0026] FIG. 6 is a diagram illustrating physical components of the interface controller device.

[0027] FIG. 7 is a diagram illustrating variations of the interface controller device.

[0028] FIG. 8 is a diagram illustrating a mapping between solenoids of the interface controller device and physical inputs of medical interfacing equipment.

[0029] FIG. 9 is a diagram illustrating overlaps between solenoids of the interface controller device and physical inputs of medical interfacing equipment.

[0030] FIG. 10 is a diagram illustrating a sideview of the interface controller device.

[0031] FIG. 11 is a diagram illustrating a solenoid of the interface controller device.

[0032] FIG. 12 illustrates a diagram of an attachment of a solenoid.

[0033] FIG. 13 illustrates a flow diagram of a method for provisioning remote operation of medical equipment.

[0034] FIG. 14 presents an example of a general-purpose computer system on which aspects of the present disclosure can be implemented.DETAILED DESCRIPTION

[0035] Exemplary aspects are described herein in the context of a system, method, and computer program product for provisioning remote operation of medical equipment. Those of ordinary skill in the art will realize that the following description is illustrative only and is not intended to be in any way limiting. Other aspects will readily suggest themselves to those skilled in the art having the benefit of this disclosure. Reference will now be made in detail to implementations of the example aspects as illustrated in the accompanying drawings. The same reference indicators will be used to the extent possible throughout the drawings and the following description to refer to the same or like items.

[0036] FIG. 1 is a diagram illustrating a remote operation system 100. Remote operation system 100 includes medical equipment 102, medical interfacing equipment 104, computing device 106 (e.g., the medical device), camera 112, and interface controller device 114. Medical interfacing equipment 104 may be a controller for adjusting parameters of medicalequipment 102. Computing device 106 may be any computer device capable of receiving and displaying results from medical equipment 102. Camera 112 may be used to monitor the medical environment (e.g., a clinic, hospital room, laboratory room, exam room, workstation, etc.).

[0037] In a typical scenario, user 108 is physically present in the environment and uses medical interfacing equipment 104 to control medical equipment 102 and view results on a monitor of computing device 106. For example, computing device 106 may be a desktop computer, medical equipment 102 may be an MRI machine, and medical interfacing equipment 104 may be a keyboard that controls scanning, adjusts movements of the components in the MRI machine, and enables communication between user 108 and the patient in the MRI machine.

[0038] Remote operation system 100 enables remote user 110 to remotely control medical interfacing equipment 104 using interface controller device 114 and remotely view outputs of medical equipment 102 displayed on computing device 106. Interface controller device 114 receives a remote command from remote user 110, parses the remote command into a physical action (e.g., pressing a button, turning on a switch / toggle, rotating a dial, etc.) to perform on medical interfacing equipment 104. As a result, even though there is no direct connection between the device of remote user 110 and medical interfacing equipment 104, remote user 110 can control medical equipment 102 as through user 108 is physically pressing the physical inputs of medical interfacing equipment 104.

[0039] In an exemplary aspect, the remote operation system 100 utilizes a Keyboard, Video, and Mouse (KVM) component that enables the mentioned remote viewing and control. In one aspect, the KVM component is software-based and is installed on an independent computing device that employs a video capture card and USB cable connected to computing device 106. The video capture card is responsible for capturing the video from the computing device 106 through a video cable. The USB cable is responsible for transmitting mouse movements and keyboard inputs to the computing device 106. In another aspect, the KVM component is hardware-based and is connected to the computing device 106 as an independent KVM device. Both aspects are thoroughly described in this present disclosure.

[0040] FIG. 2 is a diagram 200 illustrating network connections in remote operation system 100. FIG. 2 is a diagram 200 illustrating network connections in the remote operationsystem 100 using KVM component 212 that can be hardware-based or software-based.. Diagram 200 depicts two networks: customer network 202 and public network 204. In some aspects, customer network 202 is a local area network (LAN) and public network 204 is a wide area network (WAN) (e.g., the Internet). In other aspects, both customer network 202 and public network 204 are WANs.

[0041] Customer network 202 features remote communication between devices in site A (e.g., a medical facility) and site B (e.g., a command center). Remote computing device 216 establishes a secure connection with KVM component 212 connected to computing device 206, the secure connection including one or more of virtual private network (VPN) capabilities, multi-protocol label switching (MPLS) capabilities, and LAN to LAN connection capabilities. In some aspects, remote computing device 216 may communicate with camera 208, interface controller device 228, and / or computing device 206 using any combination of Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and Internet Control Message Protocol (ICMP).

[0042] Suppose that the display output of medical equipment 214 (e.g., an MRI machine) is presented on computing device 206 (e.g., a desktop computer). For example, MRI images may be displayed on computing device 206, which can be viewed, modified, and interacted with using peripheral devices (e.g., a mouse and keyboard). Using the secure connection, remote computing device 216 is able to receive and replicate the display output of medical equipment 214, as well as transmit commands to control the mouse and keyboard of computing device 206 and / or interface controller device 228 (to control medical interfacing equipment 210). This ultimately allows a remote user to program and perform a medical task (e.g., an examination process using medical equipment 214) directly as if he / she were actually sitting at the clinic or hospital workstation.

[0043] In some aspects, a remote user may also be assisted by one or more of cameras 208 that generate real-time images of the patient's position. For example, camera 208 may capture a video of the workstation in site A and transmit a stream overthe secure connection to remote computing device 216.

[0044] In some aspects, the remote user of remote computing device 216 may communicate with a local user of computing device 207 (e.g., a device dedicated to local support) using Voice over Internet Protocol (VoIP). This is enabled using communicationplatform 222, which receives and transmits audio information between the respective computing devices. In an exemplary aspect, communication platform includes VoIP server(s) 226 that perform communication exchanges.

[0045] In some aspects, cloud computation platform 220 may include a collection of resources and services provided over the Internet to enable users to access, store, manage, and run remote medical software (e.g., nCommand and / or nVirtual software). These platforms are hosted by service providers in their data centers, which includes application server(s) 224, may be used by remote computing device 216 to perform various computational tasks. For example, the software (e.g., nCommand) utilized by remote computing device 216 to perform remote access and control of device(s) in site A may be an application featuring a thin client and thick client. The thin client application may be locally installed on remote computing device 216 to perform non-intensive processing tasks such as displaying information. The thick client application may be installed on application server(s) 224 and may perform intensive processing tasks such as translating keyboard inputs received from remote computing device 216 to inputs for medical interfacing equipment 210 based on layouts. Application server(s) 224 may additionally store device configuration information, user registrations, and other information. It should be noted that no patient information or exam images are stored on public network 204. In some aspects, the software may be a web application.

[0046] In some aspects, both remote computing device 216 and KVM component 212 may communicate with servers in cloud computation platform 220 and communication platform 222 using TCP and Hypertext Transfer Protocol Secure (HTTPS) (with Secure Sockets Layer(SSL) / Transport Layer Security (TLS) 1.2) (Firewall or Proxy).

[0047] In some aspects, both computing device 207 and remote computing device 216 may contact technical support 218 to report, troubleshoot, and resolve remote access issues.

[0048] As mentioned before, a KVM may be implemented as a standalone hardware device (e.g., described in FIG. 4), or may be implemented as a software installed on an independent computing device. In terms of the software implementation, a physical connection (e.g., via a USB cable and / or video) between the device on which KVM component 212 is installed and computing device 206. The KVM component 212 may be programmed to capture the display output on computing device 206 and transmit a real-time video stream ofthe display output to remote computing device 216. A remote control software (e.g., nCommand or nVirtual) installed on remote computing device 216 may receive and generate the video stream for display.

[0049] FIG. 3 is a diagram illustrating an exemplary user interface 300 for accessing medical equipment remotely. For example, user interface 300 may be displayed on remote computing device 216 during an MRI scan. Output window 302 may include the video stream captured from computing device 206. As shown in FIG. 3, output window 302 includes MRI images and various toolbar(s) / menu(s) 304 with imaging options such as for rotating, cropping, zooming into, and modifying the MRI images. A remote user can access these options using their interface hardware (e.g., mouse, touchscreen, keyboard, etc.) connected to remote computing device 216. For example, the remote user may select option 306, which adjusts a contrast / brightness level of an MRI image. The remote control software may transmit the selection of option 306 to KVM component 212, which executes the command on computing device 206.

[0050] In some aspects, the remote control software further receives and displays camera stream 308 on user interface 300. Camera stream 308 may be a video stream captured by camera(s) 208. In some aspects, camera(s) 208 transmit their video stream directly to remote computing device 216. In other aspects, camera(s) 208 transmit their video stream to KVM component 212. The KVM component 212 then forwards the video stream from computing device 206 to remote computing device 216.

[0051] User interface 300 may further display command window 310, which generates virtual options corresponding to physical buttons on medical interfacing equipment 210. It should be noted that while the mouse and keyboard of computing device 206 may be used to interact with the medical equipment 214, medical interfacing equipment 210 is used to control functionality of medical equipment 214. Each medical interfacing equipment 210 may have a particular device type. Accordingly, when beginning a remote session, the remote control software may transmit a query to application server(s) 224 that asks for the device type. This query may specifically ask for a product identifier such as a model number. In response to receiving the device type (e.g., a Philips intercom, a GE intercom, a Siemens intercom, etc.) and / or the product identifier (e.g., part number 4757261), the remote control software may perform a lookup in an interfacing device layout database. The interfacingdevice layout database may indicate, for each entry (of medical interfacing equipment), a plurality of options found physically on the equipment. In response to finding the entry for the received device type and product identifier, the remote control software may generate the corresponding plurality of options in command window 310. In some aspects, interfacing device layout database is stored on application server(s) 224 and is periodically updated to include layouts of new medical equipment.

[0052] Suppose that the remote control software receives a user selection of option 312 in command window 310. In one aspect, the remote control software converts the user selection on remote computing device 216 to a selection of the button corresponding to option 312 on medical interfacing equipment 210. For example, command window 310 displays five options, which correspond to five buttons on medical interfacing equipment 210. In response to receiving option 312, the remote control software determines, based on a mapping in the interfacing device layout database, that button 1 on medical interfacing equipment 210 should be selected. The remote control software transmits a command to interface controller device 228 to select button 1. More specifically, the command may be to activate a solenoid that corresponds to button 1. This is discussed in depth in the subsequent figures.

[0053] In an alternative aspect, interface controller device 228 locally converts the user selection on remote computing device 216 to a selection of the button corresponding to option 312 on medical interfacing equipment 210. For example, command window 310 displays five options, which correspond to five buttons on medical interfacing equipment 210. In response to receiving option 312, the remote control software transmits an indication that option 312 has been selected to interface controller device 228. Interface controller device 228 then determines, based on a mapping in the interfacing device layout database, that button 1 on medical interfacing equipment 210 should be selected.

[0054] Suppose that option 312 involves activating a speaker of medical equipment 214 in order to allow the local user and / or the remote user to speak with a patient inside the MRI machine. This option is unavailable on the software that displays the MRI scans on computing device 206 and requires the use of medical interfacing equipment 210. In a traditional setting, the local user selects the button manually. However, using the remote control software and interface controller device 228, the remote user is able to access the functionality of medicalinterfacing equipment 210 as described above.

[0055] It should be noted that the remote control software is not comparable to the screensharing and remote control capabilities in videotelephony software. This is because videotelephony software requires being installed on both devices to enable screensharing and remote control. However, installing videotelephony software on medical interfacing equipment 210 is not readily possible. This prevents such software from allowing command selection on medical interfacing equipment 210. The fact that the remote control software of the present disclosure does not need to be installed on medical interfacing equipment 210 provides an additional benefit that computing resources are not taken from either medical equipment 214 or medical interfacing equipment 210.

[0056] FIG. 4 is a diagram 400 illustrating an interface controller device 402 and a medical interfacing equipment 404. In some aspects, interface controller device 402 at least partially covers medical interfacing equipment 404 such that any physical inputs of medical interfacing equipment 404 can be reached by solenoids within interface controller device 402.

[0057] Suppose that medical interfacing equipment 404 is an intercom device for an MRI machine. As shown in FIG. 4, medical interfacing equipment 404 has a plurality of physical inputs (e.g., buttons, dials, toggles, switches, etc.) For example, a first button may adjust the position of a patient inside the MRI machine (e.g., by moving the bed on which the patient lays). A second button may enable a microphone within the MRI machine so that the patient may speak to the medical staff. A third button may enable a speakeron the MRI machine and a microphone of the medical interfacing equipment 404 to enable the medical staff to speak to the patient.

[0058] FIG. 5 is a diagram 500 illustrating an interface controller device 402 placed on a medical interfacing equipment 404. In some aspects, an interface controller device 402 has dimensions that are set specifically for medical interfacing equipment 404. As shown in FIG. 5, the entirety of medical interfacing equipment 404 is covered by interface controller device 402.

[0059] In some aspects, when developing interface controller device 402, a specific medical interfacing equipment 404 is modelled. For example, a three-dimensional scan of medical interfacing equipment 404 may be generated using a three-dimensional scanner to obtain physical measurements. In some aspects, the 3D scanner has a resolution of 0.2mmand accuracy of 0.1mm. The three-dimensional scan is used to at least extract the dimensions of medical interfacing equipment 404, the locations of the physical inputs, the type of each physical input (e.g., button, switch, dial, etc.), the dimensions of each physical input. In some aspects, obtaining physical measurements of the medical interfacing equipment 404 also includes determining the spatial details of other elements such as speakers, indicator LEDs, and other keyboard functions. The interface controller device 402 may then be designed such that it includes solenoids that are placed within interface controller device 402 in locations that correspond to a respective physical input of medical interfacing equipment 404.

[0060] Through technical performance data, it can be proven that the use of interface controller device 402 does not cause any damage to the medical interfacing equipment 404, and can even demonstrate that its use helps in preserving the integrity of the medical interfacing equipment 404, for example, always applying the same force to press the button.

[0061] FIG. 6 is a diagram 600 illustrating physical components of the interface controller device. Interface controller device 402 has two parts: housing 601 and base 602. Housing 601 is responsible for enclosing the structural bas and its wiring. In some aspects, there is an opening on at least one side face of housing 601 to allow access to the connectors on main board 608. On the base are motor 603, mic 604, light dependent resistor (LDR) light sensors 620, solenoids 606, main board 608, capacitive screen 610, panel 612, and speaker 614. It should be noted that while medical interfacing equipment 404 may come in different shapes, sizes, and physical inputs, housing 601 remains physically the same albeit with different dimensions.

[0062] FIG. 7 is a diagram 700 illustrating variations of the interface controller device 402. For example, medical interfacing equipment 704a, 704b, 704c, and 704d are all different types of intercoms, keyboards, etc. In order to enable access to each of the physical inputs of the medical interfacing equipment 704, the amount solenoids 606 and their location may be changed. Accordingly, base 602 on which the solenoids 606 are installed and the base 602 may be elongated in certain models of the interface controller device.

[0063] For example, medical interfacing equipment 704d may be a small intercom device with three physical inputs. Interface controller device 702d fully covers medical interfacing equipment 704d. For example, interface controller device 702d may have a length of 220.21 millimeters (mm), a height of 206.53 mm, and a depth of 249.25 mm.

[0064] Medical interfacing equipment 704a may be a large intercom device with ten physical inputs. Interface controller device 702a partially covers medical interfacing equipment 704a (i.e., specifically covering the area where the physical inputs are present). For example, interface controller device 702a may have a length of 666.45 millimeters (mm), a height of 206.53 mm, and a depth of 249.25 mm.

[0065] In certain aspects, the interface control device has a length ranging from 666.45mm to 220.21mm, a depth of 249.25mm, and a height of 206.53mm.

[0066] Referring back to FIG. 6, interface controller device 402 may have a plurality of solenoids. The number of solenoids may equal the number of physical inputs on medical interfacing equipment 404.

[0067] Mic 604 and speaker 614 may be used to establish communication between the remote user of remote computing device 216 and the patient / local user. For example, for the use of an intercom system's microphone and sound output, a microphone is positioned on the sound output of the intercom and a speaker is placed over the microphone of the intercom. This provides an interface between these intercom system peripherals and the nCommand platform.

[0068] In some aspects, motor 603 is an example of a solenoid that can turn dials. For example, volume control on medical interfacing equipment may be achieved through a potentiometer. As this potentiometer may not have grooves, motor 603 may be used as a gear to fit around it. Therefore, by attaching another gear to motor 603, it becomes possible to change the volume level without directly rotating it on medical interfacing equipment 404.

[0069] Main board 608 parses and executes instructions. For example, main board 608 may include a hardware processor (described in FIG. 13) that receives digital signals and converts them into analog signals for each solenoid.

[0070] In some cases, a local user may wish to access the controls of medical interfacing equipment 404. Because interface controller device 402 covers the medical interfacing equipment 404, the physical inputs are not directly accessible. Accordingly, in some aspects, a digital representation of each physical input of the medical interfacing equipment 404 may be presented on a graphical user interface 616 on interface controller device 402. In particular, interface controller device 402 may have a display panel 612 and capacitive screen 610 that displays the graphical user interface 616. A user may select (e.g., via a touchscreenpress on capacitive screen 610) a digital representation of the physical input of the medical interfacing equipment 404. The processor on main board 608 receives the selection and converts the selection into an analog signal for a corresponding solenoid associated with the selected option. In some aspects, sound effects indicating a selection or a physical input interaction (e.g., a press, a toggle, etc.) may be output via speaker 614.

[0071] In certain aspects, the connection to the external power source on the printed circuit board is made through the 2-way LEMO connector, model 2B, capable of handling a maximum current of 15A, with a connector for 20AWG wires and dimensions of up to 18.5mm in maximum diameter, 26.7mm in length, and an 18mm external diameter connection (compatible with model IB connector for 0.75mm wire diameters and 18mm external diameter connection). In some cases, its assembly is performed with positive polarity indicated by the red marking on the edge near the connection hole (this marking indicates a 0° rotation for the connector).. In some aspects, the correct and safe operation of the interface controller device 402, according to the requirements raised and achieved during its development stage, is ensured by using a 12V (DC) power supply with a current supply capacity of 5.0 amperes.

[0072] In some aspects, the connection of interface controller device 402 to the local network of the medical environment is made through an RJ-45 connector. In some aspects, the RJ-45 connector is directly soldered to the circuit board and is accessed through the rear panel of interface controller device, allowing for the connection of a network cable that also meets IEEE 802.3 specifications.

[0073] In some aspects, the connection between a remote computing device 216 and interface controller device 402 is made through the WebSocket protocol. With the equipment connected to the computer network, the interface controller device 402 is available for connection from a WebSocket client with authentication (e.g., username and password provided by the nCommand platform). Forthe client connection, the equipment needs to be connected to the network, so it will provide an endpoint on the network allowing the nCommand platform to connect. Authentication is done automatically, authorizing the WebSocket connection.

[0074] In some aspects, the processor of interface controller device 402 collects logs of commands. The logs may indicate timestamps, received commands, executed commands,identifiers of solenoids (e.g., solenoid 1, solenoid 2, etc.), and errors. A connection may be established between the interface controller device and a log server, which aims to control software versions on devices, monitor the interface controller device (online, offline, in use or not), as well as have logs of button activations, feedback of button LEDs, as in the case of the patient safety pneumatic device. If the manufacturer's equipment has such a feature, all log information will be saved with date and time.

[0075] In some aspects, on the rear or side panel, depending on the model of the interface controller device, there may be a USB-C connector that is directly soldered to the electronic board, for connection between the interface controller device and the computing device 207 via USB-C / USB-A cable. This USB port is responsible for audio communication between the platform and the medical interfacing equipment.

[0076] FIG. 8 is a diagram 800 illustrating a mapping between solenoids 802 of the interface controller device 402 and physical inputs 804 of medical interfacing equipment 404. Each respective solenoid of solenoids 802 corresponds to a specific physical input of physical inputs 804. For example, there are five solenoids on interface controller device 402 and each one is positioned above one of five physical inputs on medical interfacing equipment 404. Microphone 814 is disposed above a physical input corresponding to a microphone of medical interfacing equipment 404. Microphone 814 is connected to the main board 608. As shown in FIG. 8, the positions of solenoids 802 on the base of interface controller device 402 match the positions of physical inputs 804. For example, if the center points of two physical inputs are 28 mm apart in terms of width and 7 mm apart in terms of length, the corresponding two solenoids that interact with the physical inputs will have the same dimensions apart.

[0077] In some aspects, light dependent resistor (LDR) light sensors 806 are installed on interface controller device 402. These LDR light sensors are positioned directly above physical inputs or LED lights 808 on medical interfacing equipment 404. Light dependent resistor (LDR) light sensors 806 are configured to detect when there is a lit LED on medical interfacing equipment 404, providing the same warning signal on interface controller device 402 (e.g., via panel 612) and the user interface shown in FIG. 3 (e.g., via Command Window 310). For example, as some physical input(s) and / or LED(s) are illuminated, the sensor(s) pointed directly at the illuminated physical input(s) and / or LED(s) change resistance values. The processor on main board 608, which is connected to light dependent resistor (LDR) lightsensors 806, detects the change in resistance and identifies the corresponding physical in put(s) / LED(s). For example, there may be a interfacing layout database mapping each light sensor to an LED / physical stored on memory on main board 608. The processor may refer to the database to determine which LED / physical input to show on the respective user interfaces described above as illuminated. For example, the remote control software can perform a search in a database of interface device layouts that maps each light sensor to a corresponding LED / input and generates virtual options corresponding to the physical LED / input on the medical interface equipment 210 - displaying them on the respective user interfaces mentioned above as illuminated.

[0078] FIG. 9 is a diagram 900 illustrating overlaps between solenoids of the interface controller device 402 and physical inputs of medical interfacing equipment 404. Diagram 900 is an overhead visualization that depicts interface controller device 402 above medical interfacing equipment 404. As can be seen, overlap 902 is one example of multiple overlaps between a solenoid and its corresponding physical input. Because the solenoid is directly above the physical input, it has access to interact with (e.g., press, turn, click, hold down, etc.) the physical input.

[0079] FIG. 10 is a diagram 1000 illustrating a sideview of the interface controller device 402. There are four solenoids visible in diagram 1000. One example of an overlap is solenoid 1002 over physical input 1004.

[0080] FIG. 11 is a diagram 1100 illustrating a solenoid (e.g., solenoid 1002) of the interface controller device 402. Diagram 1000 includes both a front view and a side view of the solenoid. The components of the solenoid include return spring 1102, housing 1104, movable actuator 1106, coil 1108, and push pin 1110. A solenoid is a long wire, wound with a helical pattern, preferably surrounded by a steel frame, and having a steel core inside the winding. When carrying a current, the solenoid becomes an electro-mechanical device, in which electrical energy is converted into mechanical work.

[0081] In some aspects, the interaction between interface controller device 402 in relation to the medical interfacing equipment 404 involves both functions where there is physical contact between interface controller device 402 and medical interfacing equipment 404 and functions where there is no contact, such as light sensors or sound emission and capture.

[0082] From scientific studies, it is found that the force applied by an adult finger can reach around 20 to 30 Newtons (N). Taking into account the force mentioned above, the maximum force applied by each solenoid is 30 N, so as not to exert a greater force on the physical inputs than an adult finger. When a physical input is selected by a remote user via the interface shown in FIG. 3 or is selected by a local user via panel 612, a hardware processor identifies the corresponding solenoid and transmits an analog signal that causes the corresponding solenoid to interact with the physical input. For example, the solenoid may establish contact with a dial input and rotate, which cause a dial input to turn. In another example, the solenoid may establish contact with a button / switch / toggle input and apply a force for a given period of time. In some aspects, the adopted solenoid valve model exerts a force of 8 N or less.

[0083] FIG. 12 illustrates a diagram 1200 of an attachment of a solenoid. The attachment is connected to a tip of each solenoid such that the attachment is in contact with the corresponding physical input of the solenoid. The use of support attachments at the end of the solenoid valve plunger is necessary both for adjusting the distance between the valve and the button and for preserving the integrity of the intercom system button. In some aspects, the attachment has a universal dimension (e.g., 15 mm diameter and 15 mm depth). In some aspects, the attachment has dimensions based on the physical input dimensions. For example, a large physical input (e.g., a circular button with a 40 mm diameter) will have a relatively larger attachment (e.g., up to 40 mm diameter). In contrast, a smaller physical input (e.g., a circular button with a 20 mm diameter will have a relatively smaller attachment (e.g., up to 20 mm diameter).

[0084] FIG. 13 illustrates a flow diagram of a method 1300 for provisioning remote operation of medical equipment. In an exemplary aspect, method 1300 is executed using an interface controller device (e.g., interface controller device 402) that includes a plurality of solenoids (e.g., solenoids 802), wherein each solenoid is disposed on the interface controller device in a location corresponding to a location of a physical input (e.g., physical inputs 804) of medical interfacing equipment (e.g., medical interfacing equipment 404). The interface controller device further includes a display (e.g., screen 610), a memory (e.g., on main board 608) storing an interface layout database that maps each solenoid on the interface controller device to a corresponding physical input on the medical interfacing equipment, and aY1hardware processor (e.g., on main board 608). In particular, the hardware processor executes method 1300.

[0085] At 1302, an interface controller device generates, on the display, a user interface (e.g., graphical user interface 616) depictinga plurality of virtual options, wherein each virtual option corresponds to a physical input on the medical interfacing equipment. At 1304, the interface controller device receives a first selection of a first virtual option of the plurality of virtual options, wherein the first virtual option is a digital representation of a first physical input on the medical interfacing equipment. At 1306, the interface controller device identifies, using the interface layout database, a first solenoid of the plurality of solenoids that corresponds to the first virtual option. At 1308, the interface controller device transmits a first command to the first solenoid to establish contact with the first physical input, wherein the first solenoid is configured to execute the command.

[0086] In some aspects, the first physical input is a button, and wherein first command is to apply a pressing force (e.g., 8 N) on the first physical input for at least a threshold period of time (e.g., 1 second)

[0087] In some aspects, the hardware processor is further configured to receive, from a computing device remotely connected to the interface controller device, a second selection of a second virtual option of the plurality of virtual options, identify, usingthe interface layout database, a second solenoid of the plurality of solenoids that corresponds to the second virtual option, and transmit a second command to the second solenoid to establish contact with the second physical input, wherein the second solenoid is configured to execute the command.

[0088] In some aspects, the second physical input is a dial, and wherein second command is to apply a rotational force on the second physical input for at least a threshold period of time.

[0089] In some aspects, the second solenoid comprises a rotating motor.

[0090] In some aspects, the first solenoid and the second solenoid simultaneously execute the first command and the second command, respectively.

[0091] In some aspects, the interface controller device further includes a plurality of light sensors (e.g., LDR 620), wherein each light sensor is disposed on the interface controller device in a location corresponding to a location of an LED light of the medical interfacingequipment. The hardware processor is further configured to determine, using the plurality of light sensors, that at least one LED light of the medical interfacing equipment is illuminated, and generate, on the display, an indication that the at least one LED light of the medical interfacing equipment is illuminated.

[0092] In some aspects, the hardware processor is further configured to transmit the indication to a remote computing device connected to the interface controller device.

[0093] In some aspects, the display is a touchscreen display.

[0094] In some aspects, the interface controller device includes an insert that at least partially houses the medical interfacing equipment. For example, the insert may be a hollow space in the interface controller device within which the medical interfacing equipment may be placed (as shown in FIG. 10).

[0095] In some aspects, the hardware processor is further configured to generate entries for a log, wherein each entry comprises a timestamp, a received selection, a transmitted command, and attributes of the transmitted command.

[0096] In some aspects, the attributes comprises one or more of: a force value, an amount of time a force was applied, an identifier of a solenoid, and an identifier of a physical input.

[0097] In some aspects, the interface controller device further includes a microphone (e.g., mic 604) disposed in a location on the interface controller device corresponding to a location of a speaker on the medical interfacing equipment, and a speaker disposed in a location on the interface controller device corresponding to a location of a microphone on the medical interfacing equipment.

[0098] FIG. 14 is a block diagram illustrating a computer system 20 on which aspects of systems and methods for provisioning remote operation of medical equipment may be implemented in accordance with an exemplary aspect. The computer system 20 can be in the form of multiple computing devices, or in the form of a single computing device (e.g., computing device 206, remote computing device 216, interface controller device 402 etc.), for example, a desktop computer, a notebook computer, a laptop computer, a mobile computing device, a smart phone, a tablet computer, a server, a mainframe, an embedded device, and other forms of computing devices.

[0099] As shown, the computer system 20 includes a central processing unit (CPU) 21, asystem memory 22, and a system bus 23 connecting the various system components, including the memory associated with the central processing unit 21. The system bus 23 may comprise a bus memory or bus memory controller, a peripheral bus, and a local bus that is able to interact with any other bus architecture. Examples of the buses may include PCI, ISA, PCI-Express, HyperTransport™, InfiniBand™, Serial ATA, l2C, and other suitable interconnects. The central processing unit 21 (also referred to as a processor) can include a single or multiple sets of processors having single or multiple cores. The processor 21 may execute one or more computer-executable code implementing the techniques of the present disclosure. For example, any of commands / steps discussed in FIGS. 1-13 may be performed by processor 21. The system memory 22 may be any memory for storing data used herein and / or computer programs that are executable by the processor 21. The system memory 22 may include volatile memory such as a random access memory (RAM) 25 and non-volatile memory such as a read only memory (ROM) 24, flash memory, etc., or any combination thereof. The basic input / output system (BIOS) 26 may store the basic procedures for transfer of information between elements of the computer system 20, such as those at the time of loading the operating system with the use of the ROM 24.

[0100] The computer system 20 may include one or more storage devices such as one or more removable storage devices 27, one or more non-removable storage devices 28, or a combination thereof. The one or more removable storage devices 1 and non-removable storage devices 28 are connected to the system bus 23 via a storage interface 32. In an aspect, the storage devices and the corresponding computer-readable storage media are powerindependent modules for the storage of computer instructions, data structures, program modules, and other data of the computer system 20. The system memory 22, removable storage devices 27, and non-removable storage devices 28 may use a variety of computer- readable storage media. Examples of computer-readable storage media include machine memory such as cache, SRAM, DRAM, zero capacitor RAM, twin transistor RAM, eDRAM, EDO RAM, DDR RAM, EEPROM, NRAM, RRAM, SONOS, PRAM; flash memory or other memory technology such as in solid state drives (SSDs) or flash drives; magnetic cassettes, magnetic tape, and magnetic disk storage such as in hard disk drives or floppy disks; optical storage such as in compact disks (CD-ROM) or digital versatile disks (DVDs); and any other medium which may be used to store the desired data and which can be accessed by the computersystem 20.

[0101] The system memory 22, removable storage devices 27, and non-removable storage devices 28 of the computer system 20 may be used to store an operating system 35, additional program applications 37, other program modules 38, and program data 39. The computer system 20 may include a peripheral interface 46 for communicating data from input devices 40, such as a keyboard, mouse, stylus, game controller, voice input device, touch input device, or other peripheral devices, such as a printer or scanner via one or more I / O ports, such as a serial port, a parallel port, a universal serial bus (USB), or other peripheral interface. A display device 47 such as one or more monitors, projectors, or integrated display, may also be connected to the system bus 23 across an output interface 48, such as a video adapter. In addition to the display devices 47, the computer system 20 may be equipped with other peripheral output devices (not shown), such as loudspeakers and other audiovisual devices.

[0102] The computer system 20 may operate in a network environment, using a network connection to one or more remote computers 49. The remote computer (or computers) 49 may be local computer workstations or servers comprising most or all of the aforementioned elements in describing the nature of a computer system 20. Other devices may also be present in the computer network, such as, but not limited to, routers, network stations, peer devices or other network nodes. The computer system 20 may include one or more network interfaces 51 or network adapters for communicating with the remote computers 49 via one or more networks such as a local-area computer network (LAN) 50, a wide-area computer network (WAN), an intranet, and the Internet. Examples of the network interface 51 may include an Ethernet interface, a Frame Relay interface, SONET interface, and wireless interfaces.

[0103] Aspects of the present disclosure may be a system, a method, and / or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present disclosure.

[0104] The computer readable storage medium can be a tangible device that can retain and store program code in the form of instructions or data structures that can be accessed by a processor of a computing device, such as the computing system 20. The computer readable storage medium may be an electronic storage device, a magnetic storage device, an opticalstorage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination thereof. By way of example, such computer-readable storage medium can comprise a random access memory (RAM), a read-only memory (ROM), EEPROM, a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), flash memory, a hard disk, a portable computer diskette, a memory stick, a floppy disk, or even a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon. As used herein, a computer readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or transmission media, or electrical signals transmitted through a wire.

[0105] Computer readable program instructions described herein can be downloaded to respective computing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and / or edge servers. A network interface in each computing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing device.

[0106] Computer readable program instructions for carrying out operations of the present disclosure may be assembly instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language, and conventional procedural programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a LAN or WAN, or the connection may be made to an external computer (for example, through the Internet). In some embodiments, electronic circuitry including, forexample, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present disclosure.

[0107] In various aspects, the systems and methods described in the present disclosure can be addressed in terms of modules. The term "module" as used herein refers to a real- world device, component, or arrangement of components implemented using hardware, such as by an application specific integrated circuit (ASIC) or FPGA, for example, or as a combination of hardware and software, such as by a microprocessor system and a set of instructions to implement the module's functionality, which (while being executed) transform the microprocessor system into a special-purpose device. A module may also be implemented as a combination of the two, with certain functions facilitated by hardware alone, and other functions facilitated by a combination of hardware and software. In certain implementations, at least a portion, and in some cases, all, of a module may be executed on the processor of a computer system. Accordingly, each module may be realized in a variety of suitable configurations, and should not be limited to any particular implementation exemplified herein.

[0108] In the interest of clarity, not all of the routine features of the aspects are disclosed herein. It would be appreciated that in the development of any actual implementation of the present disclosure, numerous implementation-specific decisions must be made in order to achieve the developer's specific goals, and these specific goals will vary for different implementations and different developers. It is understood that such a development effort might be complex and time-consuming, but would nevertheless be a routine undertaking of engineering for those of ordinary skill in the art, having the benefit of this disclosure.

[0109] Furthermore, it is to be understood that the phraseology or terminology used herein is for the purpose of description and not of restriction, such that the terminology or phraseology of the present specification is to be interpreted by the skilled in the art in light of the teachings and guidance presented herein, in combination with the knowledge of those skilled in the relevant art(s). Moreover, it is not intended for any term in the specification or claims to be ascribed an uncommon or special meaning unless explicitly set forth as such.

[0110] The various aspects disclosed herein encompass present and future known equivalents to the known modules referred to herein by way of illustration. Moreover, while aspects and applications have been shown and described, it would be apparent to those skilled in the art having the benefit of this disclosure that many more modifications than mentioned above are possible without departing from the inventive concepts disclosed herein.

Claims

CLAIMS1. An interface controller device, comprising: a plurality of solenoids, wherein each solenoid is disposed on the interface controller device in a location corresponding to a location of a physical input of medical interfacing equipment; a display; memory storing an interface layout database that maps each solenoid on the interface controller device to a corresponding physical input on the medical interfacing equipment; a hardware processor configured to: generate, on the display, a user interface depicting a plurality of virtual options, wherein each virtual option corresponds to a physical input on the medical interfacing equipment; receive a first selection of a first virtual option of the plurality of virtual options, wherein the first virtual option is a digital representation of a first physical input on the medical interfacing equipment; identify, using the interface layout database, a first solenoid of the plurality of solenoids that corresponds to the first virtual option; transmit a first command to the first solenoid to establish contact with the first physical input, wherein the first solenoid is configured to execute the command.

2. The interface controller device of claim 1, wherein the first physical input is a button, and wherein first command is to apply a pressing force on the first physical input for at least a threshold period of time.

3. The interface controller device of claim 1, wherein the hardware processor is further configured to: receive, from a computing device remotely connected to the interface controller device, a second selection of a second virtual option of the plurality of virtual options; identify, using the interface layout database, a second solenoid of the plurality of solenoids that corresponds to the second virtual option;transmit a second command to the second solenoid to establish contact with the second physical input, wherein the second solenoid is configured to execute the command.

4. The interface controller device of claim 3, wherein the second physical input is a dial, and wherein second command is to apply a rotational force on the second physical input for at least a threshold period of time.

5. The interface controller device of claim 4, wherein the second solenoid comprises a rotating motor.

6. The interface controller device of claim 3, wherein the first solenoid and the second solenoid simultaneously execute the first command and the second command, respectively.

7. The interface controller device of claim 1, further comprising: a plurality of light sensors, wherein each light sensor is disposed on the interface controller device in a location corresponding to a location of an LED light of the medical interfacing equipment; wherein the hardware processor is further configured to: determine, using the plurality of light sensors, that at least one LED light of the medical interfacing equipment is illuminated; generate, on the display, an indication that the at least one LED light of the medical interfacing equipment is illuminated.

8. The interface controller device of claim 7, wherein the hardware processor is further configured to transmit the indication to a remote computing device connected to the interface controller device.

9. The interface controller device of claim 1, wherein the display is a touchscreen display.

10. The interface controller device of claim 1, further comprising an insert that at least partially houses the medical interfacing equipment.

11. The interface controller device of claim 1, wherein the hardware processor is further configured to generate entries for a log, wherein each entry comprises a timestamp, a received selection, a transmitted command, and attributes of the transmitted command.

12. The interface controller device of claim 11, wherein the attributes comprises one or more of: a force value, an amount of time a force was applied, an identifier of a solenoid, and an identifier of a physical input.

13. The interface controller device of claim 1, further comprising: a microphone disposed in a location on the interface controller device corresponding to a location of a speaker on the medical interfacing equipment; and a speaker disposed in a location on the interface controller device corresponding to a location of a microphone on the medical interfacing equipment.

Images