Medical Device Connectivity to Hospital Information Systems Using Device Server

• US 20130160082A1
• Filed: 08/31/2011
• Published: 06/20/2013
• Est. Priority Date: 08/31/2010
• Status: Abandoned Application

• Current Assignee: Lantronix Incorporated
• Original Assignee: Lantronix Incorporated
• Inventors: Miller, Daryl R.
• Application Number:
  US13/816,309
• Publication Number:
  US 20130160082A1
• Time in Patent Office: Days
• US Class Current: 726/3
• CPC Class Codes: G16H 40/20 for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

The present invention employs a system and method to allow for connectivity of a plurality of medical devices in a health care setting. The present invention utilizes a device server which may connect the plurality of medical devices to a hospital information system. The system may identify and authenticate a medical device and provide an administrator or privileged user accessing the information received from the medical device at a remote location. It is contemplated that the system utilizes a device server to connect the plurality of medical devices to the hospital information systems.

Claims

1. A system for integrating and connecting medical devices into a medical facility network, comprising:

a device server/terminal interfacing with the medical facility network;

a medical device which is attached to the device server either wired or wirelessly; and

wherein the medical facility network is configured to transmit an initialization signal to the medical device and is configured to automatically initialize in response to receiving the initialization signal.

2. The system of claim 1, wherein a display is in communication with the device server to show status and other information.

3. The system of claim 1, wherein the medical device is automatically detected by the medical facility network upon introduction into the medical treatment area.

4. The system of claim 1, wherein initializing comprises of powering the medical device into an active power state.

5. The system of claim 1, wherein the medical facility network is connected to the Internet, thereby facilitating data exchange between the medical facility network and another entity.

6. The system of claim 1, wherein the wireless range is limited to approximately the medical treatment area.

7. The system of claim 1, wherein the medical facility network comprises of a local network or facility wide network.

8. The system of claim 1, wherein the system is further configured to remotely monitor and diagnose remote medical devices once the medical device has been located and analyzed by the hospital information systems.

9. The system of claim 1, further comprising a conduit manager to create a direct communication tunnel to a medical device.

10. The system of claim 1, wherein the device server/terminal comprises a first device server that resides in a first local network and a second device server that resides in a second local network distinct from the first local network.

11. The system of claim 10, further comprising a device serve that resides in a wide area network external to both the first and second device servers.

12. The system of claim 11, wherein both the first and second device servers create their own direct communication tunnel to the device manager by periodically authenticating themselves to the device manager and establishing an outgoing TCP/IP stream connection to the device manager and then keeps that connection open for future bi-directional communication on the outgoing TCP/IP stream connection and wherein the device servers communicates with both the medical devices and the medical facility network.

13. The system of claim 12, wherein the device server initiates a connection the device manager which will manage the connection between the host and the medical device.

14. The system of claim 1, further configured to target the medical device whereby the system may be notified when the targeted medical device is malfunctioning.

15. The system of claim 14, wherein the device server is further configured to provide information from the medical device to a system administrator through which error messages, device data and other information may be sent remotely to the administrator for analysis and review.

16. A method to allow for connectivity of a medical device in a health care setting comprising:

detecting and locating the medical device in the medical treatment area by the medical facility network;

identifying a medical device and authenticating the medical device and providing an administrator or privileged user access to the information received from the medical device at a remote location;

initializing the medical device; and

connecting and monitoring the medical devices.

17. The method of claim 16, further comprising of using a device server to communicate, monitor and connect the medical devices with an administrator and/or hospital information system.

18. The method of claim 16, further comprising of using an external adaptor to uniquely identify any attached equipment.

19. The method of claim 16, further comprising of automatically detecting the medical device upon introduction of the medical device into the medical treatment area.

20. The method of claim 16, further comprising of powering the medical device into an active power state to cause initialization of the device.