System and Apparatus for Electronic Patient Care

• US 20130346108A1
• Filed: 03/15/2013
• Published: 12/26/2013
• Est. Priority Date: 01/22/2010
• Status: Active Grant

• Current Assignee: Deka Products Limited Partnership
• Original Assignee: Deka Products Limited Partnership
• Inventors: KAMEN, DEAN, BIASI, JOHN J.
• Granted Patent: US 10,242,159 B2
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G16H 20/17 delivered via infusion or injection
• 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: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A system for electronic patient care includes a network, a facility gateway, a device gateway application and a medical device. The facility gateway is configured to provide a publish-subscribe service for an application. The device gateway application is configured for execution by the facility gateway. The device gateway is configured to communicate via the network by providing a web service. The medical device is in operative communication with the network. The medical device is configured to communicate with the device gateway using the web service.

Claims

1. A system for electronic patient care, the system comprising:

a network;

a facility gateway configured to provide a publish-subscribe service for an application; and

a device gateway application configured for execution by the facility gateway, the device gateway is configured to communicate via the network by providing a web service; and

a medical device in operative communication with the network, wherein the medical device is configured to communicate with the device gateway using the web service.

2. The system according to claim 1, further comprising a publish-subscribe engine configured to provide the publish-subscribe service.

3. The system according to claim 1, wherein the network is a TCP/IP-based network.

4. The system according to claim 1, wherein the device gateway application is a web server of the web service and the medical device is a client of the web service.

5. The system according to claim 1, wherein the device gateway application is configured to register a topic using the publish-subscribe service.

6. The system according to claim 5, further comprising an integration API configured for execution by the facility gateway, wherein the integration API is configured to subscribe to the topic and communicate an event received by the subscription to the topic to at least one external server.

7. The system according to claim 6, wherein the topic is at least one of a reportable biomed events topic and a reportable clinical events topic.

8. The system according to claim 5, wherein the topic is a reportable biomed event topic and the device gateway reformats a medical device event received via the web service into a reportable biomed event receivable by a subscriber to the topic via the publish-subscribe engine.

9. The system according to claim 8, wherein the medical device communicates the medical device event via the network using the web service

10. The system according to claim 5, wherein the topic is a reportable clinical event topic and the device gateway reformats a medical device event received via the web service into a reportable clinical event receivable by a subscriber to the topic via the publish-subscribe engine.

11. The system according to claim 10, wherein the medical device communicates the medical device event via the network using the web service

12. The system according to claim 5, wherein the topic corresponds to at least one class of pump events.

13. The system according to claim 12, wherein the at least one class of pump events includes at least one of an infusion event regarding an alarm, alert or notification, an infusion event regarding infusing, an infusion event regarding programming, a device event regarding communication, a device event regarding an access request, a device event regarding configuration updates, a device event regarding logging, and a device event regarding power consumption.

14. The system according to claim 1, further comprising a continuous quality improvement listener configured for execution by the facility gateway, wherein:

the continuous quality improvement listener subscribes to a reportable biomed event topic and to a reportable clinical even topic,

the continuous quality improvement is configured to communicate a reportable biomed event received by the subscription to the reportable biomed event topic to an external database, and

the continuous quality improvement is configured to communicate a reportable clinical event received by the subscription to the reportable clinical event topic to an external database.

15. The system according to claim 14, wherein the external database records at least one of the reportable biomed event and the reportable clinical event.

16. The system according to claim 1, further comprising a device manager executable on the facility gateway, wherein the device manager is configured to maintain a list of medical devices including the medical device.

17. The system according to claim 16, wherein the list of the medical devices includes a list of serial numbers corresponding to the list of medical devices.

18. The system according to claim 1, further comprising a monitoring client in operative communication with the medical device through the network to receive status information therefrom.

19. A medical device, comprising:

a network;

a processor;

a transceiver in operative communication with the processor and configured to communicate via the network; and

a device gateway communication manager executable on the processor and configured to operatively communicate via the transceiver, wherein the device gateway communication manager is configured to communicate a device event using a web method over the network.

20. The device according to claim 19, wherein the network is a WiFi network.

21. The device according to claim 19, wherein the transceiver is a WiFi transceiver.

22. The device according to claim 19, wherein only the device is configured to initiate communication using the web method.

23. The device according to claim 19, wherein the device is configured to send data to a monitoring device via the network.

24. A system for electronic patient care, the system comprising:

a network;

a facility gateway configured to provide a publish-subscribe service;

a device gateway application configured for execution by the facility gateway, the device gateway is configured to communicate via the network by providing a web service, wherein the device gateway publishes a medical device event topic;

a device application configured for execution on the facility gateway and configured to subscribe to the medical device event topic, wherein the device application publishes a CQI-message topic, and wherein the device application is configured to receive an event from the subscription to the medical device event topic and publish the event as a CQI message through the CQI-message topic; and

a medical device in operative communication with the network, wherein the medical device is configured to communicate with the device gateway using the web service and to generate the event using a web method of the web service.

25. The system according to claim 24, wherein the device gateway subscribes to the CQI-message topic to receive the CQI-message.

26. The system according to claim 25, further comprising a CQI listener configured for execution by the facility gateway, wherein the CQI listener is subscribed to the CQI-message topic to receive the CQI message.

27. The system according to claim 26, wherein the CQI listener communicates the CQI-message to an external database.

28. The system according to claim 24, wherein the CQI message is one of a reportable biomed event and a reportable clinical event.

29. The system according to claim 24, further comprising a monitoring client configured to operatively communicate with the medical device.

30. The system according to claim 29, wherein the monitoring client communicate with the medical device by subscribing to the CQI-message topic.