INTEGRATION AND CONTROL OF MEDICAL DEVICES IN A CLINICAL ENVIRONMENT

• US 20090036750A1
• Filed: 05/27/2008
• Published: 02/05/2009
• Est. Priority Date: 05/25/2007
• Status: Abandoned Application

• Current Assignee: Charles Stark Draper Laboratory Incorporated
• Original Assignee: Charles Stark Draper Laboratory Incorporated
• Inventors: Weinstein, William, Perry, Heidi, Traviglia, Daniel
• Application Number:
  US12/127,686
• Publication Number:
  US 20090036750A1
• Time in Patent Office: Days
• US Class Current: 600/300
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• 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/67 for remote operation
• 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 and process is provided for integrating and controlling devices within an environment for executing a procedure. A state of the environment is determined, at least in part, from the monitored information received from the device(s). In response to a predetermined workflow plan and in view of the determined state of the environment, commands are identified for one or more of the multiple devices to support execution of the workflow plan. A middleware bridge is provided for allowing any application to communicate with any device, given that capabilities of the device satisfy requirements of the application. The middleware system includes a device driver generator adapted for creating device drivers from static, descriptive files, and a service generator adapted for generating services from the device model and application requirements. Integration is accomplished by a matching of device and application services. The devices can be medical devices in a clinical environment.

Claims

1. A method of controlling a plurality of medical devices for executing a medical procedure within a clinical environment, each of the plurality of medical devices adapted for one or more of monitoring and controlling an aspect of the clinical environment, comprising:

receiving monitored information from one or more of the plurality of medical devices;

determining at least in part from the monitored information received, a state of the clinical environment; and

identifying respective commands for one or more of the plurality of medical devices in response to a predetermined workflow plan and view of the determined state of the clinical environment, the commands supporting execution of the predetermined workflow plan.

2. The method of claim 1, further comprising controlling autonomously one or more the plurality of medical devices according to the respective identified commands.

3. The method of claim 1, wherein a degree of the autonomous control of one or more the plurality of medical devices is adjustable during execution of the medical procedure.

4. The method of claim 1, wherein the act of identifying respective commands for one or more of the plurality of medical devices comprises:

determining a variance between the determined state of the clinical environment and a predicted state of the clinical environment; and

identifying respective commands for one or more of the plurality of medical devices to reduce the variance between the determined and predicted states of the clinical environment.

5. The method of claim 4, further comprising autonomously controlling one or more the plurality of medical devices according to the respective identified commands.

6. The method of claim 1, wherein the act of identifying respective commands for one or more of the plurality of medical devices further comprises managing interaction among at least some of the plurality of medical devices.

7. The method of claim 6, wherein the act of managing interaction among at least some of the plurality of medical devices comprises consulting predetermined rules.

8. The method of claim 1, further comprising:

analyzing monitored information received from one or more of the plurality of medical devices; and

drawing conclusions regarding status of at least one of the medical procedure and the clinical environment

9. The method of claim 8, wherein the act of identifying respective commands for one or more of the plurality of medical devices is also responsive to conclusions drawn from analysis of the monitored information.

10. The method of claim 8, further comprising combining information received from different medical devices of the plurality of medical devices, wherein the act of analyzing comprises analyzing the combined information.

11. The method of claim 1, further comprising managing device alarms provided within monitored information received from one or more of the plurality of independent medical devices.

12. The method of claim 1, further comprising identifying rules for identifying respective commands for one or more of the plurality of medical devices in response to a predetermined workflow plan, a pre-determined model, and view of the determined state of the clinical environment.

13. A method for integrating a device into an integrated system, comprising:

establishing electrical communication between the device and an integration controller; and

providing to the integration controller a device model associated with the device, the device model usable by the integration controller to access functionality of the device.

14. The method of claim 13, further comprising discovering by the integration controller the device.

15. The method of claim 13, wherein for a non-compliant device, the act of providing the device model associated therewith comprises pre-loading the device model into the integration controller before establishing electrical communication between the device and the integration controller.

16. The method of claim 15, further comprising for a non-compliant device communicating with a non-compliant message protocol, informing the integration controller of a message protocol usable by the device.

17. The method of claim 16, wherein the act of informing the integration controller of the message protocol usable by the device comprises providing at least one of a grammar file and a protocol file describing message exchanges expected by the device, the integration manager generating a protocol manager adapted to handle messaging requirements of the non-compliant device.

18. The method of claim 13, wherein for a compliant device, the act of providing the device model associated therewith comprises exporting through the established electrical communications the device model from the device to the integration controller.

19. The method of claim 18, wherein for a compliant device, the device model is describable by a predetermined device meta-model.

20. The method of claim 13, further comprising negotiating a security protocol for securing transfer of information between the device and the integration controller.

21. The method of claim 13, wherein the device is an independent medical device.

22. A system for integrating and controlling a plurality of independent medical devices for executing a medical procedure within a clinical environment, comprising:

a medical device controller receiving monitored information from one or more of the plurality of independent medical devices, each of the plurality of independent medical devices adapted for one or more of monitoring and controlling a respective aspect of the clinical environment;

a situational awareness processor receiving monitored information from one or more of the plurality of independent medical devices, the situational awareness processor adapted for determining a state of the clinical environment based at least in part upon monitored information received from one or more of the plurality of independent medical devices; and

a diagnostic processor in communication with the situational awareness processor and the medical device controller, the diagnostic processor adapted to identify respective commands for one or more of the plurality of independent medical devices in response to a predetermined workflow plan and view of the determined state of the clinical environment.

23. The system of claim 22, further comprising a user interface allowing interaction with one or more of the medical device controller, the situational awareness processor, and the diagnostic processor during execution of the medical procedure, the interaction allow modification of a predetermined work flow during execution of the medical procedure.

24. The system of claim 22, further comprising a flexible medical device interface adapted for interconnecting the plurality of independent medical devices to the system without requiring the plurality of independent medical devices prescribe to a particular interface.

25. The system of claim 22, further comprising a communications interface allowing at least one of a user, the medical device controller, the situational awareness processor, and the diagnostic processor to be located remotely from the plurality of independent medical devices disposed within the clinical environment.

26. The system of claim 22, wherein at least one of the medical device controller, the situational awareness processor, and the diagnostic processor is fault tolerant.

27. The system of claim 22, wherein the system is reconfigurable by a user.

28. A system for integrating a device into an integrated system, comprising:

means for establishing electrical communication between the device and an integration controller;

means for discovering by the integration controller the device; and

means for providing to the integration controller a device model associated with the device, the device model usable by the integration controller to access functionality of the device.

29. A software engine for establishing plug-and-play connectivity to one or more devices according to a respective static description of each of the one or more devices, comprising:

a. an interface to one or more application programs adapted to communicate with the one or more devices;

b. an interface to each of the one or more devices connected via respective communication ports;

c. a module for device driver generation adapted to generate from a set of descriptive files, driver software for establishing device communication with each of the one or more connected medical devices;

d. a module for service generation adapted to generate services from application requirements and the static description of the one or more devices;

e. middleware for device association adapted to enable plug-and-play interoperability of the one or more devices, utilizing a service matching method; and

f. middleware for data transfer using semantically coded types and a database of terms and codes.

30. The software engine of claim 29, wherein at least one of the one or more devices is a medical device, the database of terms and codes including a database of medical terms and codes.

31. A middleware system for allowing any application to communicate with any device, given that the capabilities of the device satisfy the requirements of the application, comprising:

a. a device driver generator adapted for creating a device driver from a static, descriptive file;

b. a service generator adapted for generating a service from the device model and application requirements, resulting in device service and application services;

c. a service-matching process for matching device services and application services, for enabling managed communication between applications and services, and for providing a compatibility check between an application and a set of devices; and

d. a data transfer process for transferring data between a device and an application using a semantic mapping between the created device driver, device services, and the application service.