Medical device control in telehealth systems

• US 10,621,304 B2
• Filed: 03/07/2017
• Issued: 04/14/2020
• Est. Priority Date: 03/07/2017
• Status: Active Grant

• Current Assignee: Ricoh Company Limited
• Original Assignee: Ricoh Company Limited
• Inventors: Wasnik, Pankaj, Kapadia, Maharsh, Namboodiri, Vipin
• Primary Examiner(s): Katsikis, Kostas J
• Application Number:
  US15/452,549
• Publication Number:
  US 20180262550A1
• Time in Patent Office: 1,134 Days
• CPC Class Codes: G16H 40/67 for remote operation
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
• CPC Class Codes: H04L 65/1063 Application servers providing network services systems providing special services to telephonic subscribers H04M3/42
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

A system including one or more processors and a memory. The memory stores instructions that, when executed by the one or more processors, cause the system to receive, via a server, a first real time messaging protocol message from a hub application, the first real time messaging protocol message to control a medical; transmit a device driver command to control the medical device based on the first real time messaging protocol message; receive data from the medical device; and transmit, via the server, the data from the medical device to the hub application.

Claims

1. A method comprising:

receiving, at a node application via a server, a first real time messaging protocol message from a second application, the first real time messaging protocol message to control a medical device located at a node;

parsing the first real time messaging protocol message;

converting each part of the parsed first real time messaging protocol message to one or more system-level commands;

determining whether a device driver for the medical device has been loaded;

responsive to determining that the device driver has not been loaded,

dynamically loading the device driver;

converting the one or more system-level commands to a device driver command that triggers a device-specific sequence of workflow for the medical device; and

transmitting, by the node application, the device driver command to the device driver to control the medical device for effectuating an action specified in the first real time messaging protocol message and in the sequence of workflow;

receiving, by the node application, data from the medical device; and

transmitting, by the node application via the server, the data from the medical device to the second application.

2. The method of claim 1, further comprising recording and storing the first real time messaging protocol message for medical auditing.

3. The method of claim 1, further comprising:

generating a real time streaming protocol stream based on the received data from the medical device; and

transmitting the real time streaming protocol stream to the server.

4. The method of claim 1, further comprising:

responsive to receiving the data from the medical device, generating a second real time messaging protocol message to transmit the data; and

transmitting the second real time messaging protocol message to the server.

5. The method of claim 4, further comprising transmitting the second real time messaging protocol message to the second application.

6. The method of claim 1, wherein the device driver command includes an instruction to read a configuration setting from the medical device.

7. The method of claim 6, wherein

parsing the first real time messaging protocol message includes reading the configuration setting.

8. The method of claim 1, further comprising encrypting the data from the medical device.

9. The method of claim 1, wherein the first real time messaging protocol message is transmitted through a hypertext transfer protocol tunnel.

10. A system comprising:

one or more processors; and

a memory storing instructions that, when executed by the one or more processors, cause the system to;

receive, via a server, a first real time messaging protocol message from an application, the first real time messaging protocol message to control a medical device;

parse the first real time messaging protocol message;

convert each part of the parsed first real time messaging protocol message to one or more system-level commands;

determine whether a device driver for the medical device has been loaded;

responsive to determining that the device driver has not been loaded,

dynamically load the device driver;

convert the one or more system-level commands to a device driver command that triggers a device-specific sequence of workflow for the medical device; and

transmit the device driver command to the device driver to control the medical device for effectuating an action specified in the first real time messaging protocol message and in the sequence of workflow;

receive data from the medical device; and

transmit, via the server, the data from the medical device to the application.

11. The system of claim 10, wherein the instructions, when executed by the one or more processors, cause the system to record and store the first real time messaging protocol message for medical auditing.

12. The system of claim 10, wherein the instructions, when executed by the one or more processors, cause the system to:

generate a real time streaming protocol stream based on the received data from the medical device; and

transmit the real time streaming protocol stream to the server.

13. The system of claim 10, wherein the instructions, when executed by the one or more processors, cause the system to:

responsive to receiving the data from the medical device, generate a second real time messaging protocol message to transmit the data; and

transmit the second real time messaging protocol message to the server.

14. The system of claim 13, wherein the instructions, when executed by the one or more processors, cause the system to transmit the second real time messaging protocol message to the application.

15. The system of claim 10, wherein the device driver command includes an instruction to read a configuration setting from the medical device.

16. The system of claim 15, wherein to parse the first real time messaging protocol message, the instructions, when executed by the one or more processors, cause the system to:

read the configuration setting.

17. The system of claim 10, wherein the instructions, when executed by the one or more processors, cause the system to encrypt the data from the medical device.

18. The system of claim 10, wherein the first real time messaging protocol message is transmitted through a hypertext transfer protocol tunnel.

19. A computer program product comprising a non-transitory computer usable medium including a computer readable program, wherein the computer readable program when executed on a computer causes the computer to:

receive, via a server, a first real time messaging protocol message from an application, the first real time messaging protocol message to control a medical device;

parse the first real time messaging protocol message;

convert each part of the parsed first real time messaging protocol message to one or more system-level commands;

determine whether a device driver for the medical device has been loaded;

responsive to determining that the device driver has not been loaded,

dynamically load the device driver;

convert the one or more system-level commands to a device driver command that triggers a device-specific sequence of workflow for the medical device; and

transmit the device driver command to the device driver to control the medical device for effectuating an action specified in the first real time messaging protocol message and in the sequence of workflow;

receive data from the medical device; and

transmit, via the server, the data from the medical device to the application.

20. The computer program product of claim 19, wherein the computer readable program when executed on a computer further causes the computer to:

generate a real time streaming protocol stream based on the received data from the medical device; and

transmit the real time streaming protocol stream to the server.