Enhanced interface for a medical device and a terminal

• US 6,957,102 B2
• Filed: 12/10/2001
• Issued: 10/18/2005
• Est. Priority Date: 12/10/2001
• Status: Expired due to Term

• Current Assignee: Physio-Control Incorporated (Stryker Corporation)
• Original Assignee: Medtronic Emergency Response Systems Inc (Stryker Corporation)
• Inventors: Edwards, D. Craig, Silver, H. Ward
• Primary Examiner(s): LAYNO, CARL HERNANDZ
• Application Number:
  US10/016,507
• Publication Number:
  US 20030109904A1
• Time in Patent Office: 1,408 Days
• Field of Search: 607/2, 607 4- 5, 607/32, 607/60, 600/523, 600/524, 600/481, 600/508, 128903-904, 128/920
• US Class Current: 607/2
• CPC Class Codes: A61B 2560/0271 using a remote monitoring unit
• CPC Class Codes: A61B 5/0002 Remote monitoring of patients using telemetry, e.g. transmission of vital signals via a communication network A61B5/07 takes precedence; transmission systems for measured values G08C; transmission H04B; transmission of digital information H04L; wireless communication networks H04W
• CPC Class Codes: A61N 1/37211 Means for communicating with stimulators
• CPC Class Codes: A61N 1/37235 Aspects of the external programmer
• CPC Class Codes: A61N 1/37252 Details of algorithms or data aspects of communication system, e.g. handshaking, transmitting specific data or segmenting data
• CPC Class Codes: A61N 1/37282 characterised by communication with experts in remote locations using a network
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 20/40 relating to mechanical, radiation or invasive therapies, e.g. surgery, laser therapy, dialysis or acupuncture
• 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
• CPC Class Codes: Y10S 128/92 Computer assisted medical diagnostics

Abstract

A system is described that comprises a medical device on which is installed a version of software and a software agent communicatively coupled to the medical device without regard to the version of software installed on the medical device. An example of the medical device includes a defibrillator. The software agent may reside in a personal digital assistant and can be operated to communicate with the defibrillator to access the data stored in the defibrillator irrespective of the version of software of the defibrillator.

Claims

1. A system for communicating medical information, comprising:

a medical device installed with a version of software; and

a software agent communicatively coupled to the medical device for interacting with the medical device, wherein the software agent interacts with the medical device irrespective of correspondence with the version of software installed on the medical device the software agent accessing a directory in the medical device to invoke one or more objects having well-known names in the directory and thereby access information in the medical device.

2. The system of claim 1, wherein the information includes medical information.

3. The system of claim 2, wherein the software agent interacts with the medical device by setting the medical information of the medical device.

4. The system of claim 2, wherein the software agent interacts with the medical device by retrieving the medical information from the medical device.

5. The system of claim 2, wherein the software agent interacts with the medical device by configuring the medical device.

6. The system of claim 1, further comprising another software agent communicatively coupled to the software agent.

7. The system of claim 1, further comprising a data management system communicatively coupled to the software agent.

8. The system of claim 1, wherein the information is structured in a language that contains the data and that describes the data wing a number of textual tags.

9. The system of claim 1, wherein the language includes Extensible Markup Language (XML), wherein data is structured as an XML element.

10. The system of claim 1, wherein each object is formed in a language that contains both configuration data and patient data and describes both the configuration data and the patient data using textual tags when the object is exported external to the medical device.

12. The system of claim 1, further comprising an output device communicatively coupled to the software agent.

13. The system of claim 12, wherein the output device is selected from a group consisting of a printer, a waveform display, a video recorder, a debugging machine, a data card, a cell phone, a therapeutic device trainer, a modem, an ECG monitor, a personal computer, an alarm system, a voice storage system, a personal digital assistant, a service test system, and a manufacturing test system.

14. The system of claim 13, wherein the output device is communicatively coupled to the software agent via a wired local area network.

15. The system of claim 13, wherein the output device is communicatively coupled to the software agent via a wireless local area network.

11. A system for communicating medical information, comprising:

a medical device installed with a version of software;

a software agent communicatively coupled to the medical device for interacting with the medical device, wherein the software agent interacts with the medical device irrespective of correspondence with the version of software installed on the medical device; and

another medical device installed with another version of software, the software agent being communicatively coupled to the another medical device without regard to the another version of software installed on the another medical device, and wherein the another medical device retrieves from the software agent the medical information that the software agent retrieves from the medical device.

16. A system for communicating medical information, comprising:

a therapeutic device for storing data and being installed with a version of software;

a software agent to present a user interface to communicate with the therapeutic device; and

an interface for communicatively coupling the therapeutic device to the software agent irrespective of correspondence of the software agent to the version of software of the therapeutic device, the software agent accessing a directory in the therapeutic device to invoke one or more objects having well-known names in the directory and thereby access data in the therapeutic device, and the interface having a therapeutic portion that exposes data from the therapeutic device and a software agent portion that obtains the data so that the user interface is invoked upon receiving the data.

17. The system of claim 16, wherein the software agent includes a set of presentation tools that invoke the user interface.

18. The system of claim 17, the directory including a number of constructor objects and a number of activator objects, each constructor object being controllable from the set of presentation tools to query the therapeutic device for the data, and each activator object being controllable from the set of presentation tools to configure the therapeutic device.

19. The system of claim 18, wherein each object in the directory has one of the well-known names so that the software agent may use the well-known name of the object to invoke the object in the directory.

20. The system of claim 16, wherein the data obtained by the agent portion of the interface is structured in a language that contains the data and that describes the data using a number of textual tags.

21. The system of claim 16, further comprising another therapeutic device communicatively coupled to the software agent, the another therapeutic device being reconfigurable by the software agent based on the data obtained from the therapeutic device by the software agent.

22. The system of claim 16, further comprising an output device communicatively coupled to the software agent.

23. The system of claim 22, wherein the output device is selected from a group consisting of a printer, a waveform display, a video recorder, a debugging machine, a data card, a cell phone, a therapeutic device trainer, a modem, an ECG monitor, a personal computer, an alarm system, a voice storage system, a personal digital assistant, a service test system, and a manufacturing test system.

24. The system of claim 23, wherein the output device is communicatively coupled to the software agent via a wired local area network.

25. The system of claim 23, wherein the output device is communicatively coupled to the software agent via a wireless local area network.

26. The system of claim 16, further comprising a data management system communicatively coupled to the software agent.

27. A system for remotely communicating with a medical device, comprising:

a defibrillator for storing data and being installed with a version of software; and

a personal digital assistant being operative to communicate with the defibrillator to access the data irrespective of the software version of the defibrillator, the software agent accessing a directory in the medical device to invoke one or more objects having well-known names in the directory and thereby access the data in the medical device.

28. The system of claim 27, wherein the personal digital assistant communicates with the defibrillator by setting data in the defibrillator.

29. The system of claim 27, wherein the personal digital assistant communicates with the defibrillator by retrieving data from the defibrillator.

30. The system of claim 27, wherein the personal digital assistant communicates with the defibrillator by configuring the data in the defibrillator.

31. The system of claim 27, wherein the defibrillator includes an interface that exposes the directory of objects, a number of objects referencing data relating to the configuration of the defibrillator, and a number of other objects referencing data relating to one or more patients treated by the defibrillator.

32. The system of claim 31, wherein each object in the directory is selected from a group consisting of an inbox, an outbox, device data, patient data, and a root directory.

33. The system of claim 31, wherein the personal digital assistant includes an interface allowing the receipt of the data structured in a language that contains the data and that describes the data through textual tags.

34. The system of claim 33, wherein the language includes Extensible Markup Language (XML), wherein data is structured as an XML element.

35. A system for remotely communicating with a medical device, comprising:

a defibrillator for storing data and being installed with a version of software;

a personal digital assistant being operative to communicate with the defibrillator to access the data irrespective of correspondence to the software version of the defibrillator; and

another defibrillator installed with a software agent, the another defibrillator being communicatively coupled to the defibrillator via the software agent without regard to the version of software installed on the defibrillator, and wherein the another defibrillator retrieves from the defibrillator the medical information that is stored in the defibrillator.

36. A medical device, comprising:

hardware to apply a therapy to a patient according to a set of therapeutic rules;

one or more data storage devices for storing configuration data and patient data; and

a common interface for exporting either the configuration data or the patient data, both the configuration data and the patient data being organized in one or more subdirectories of a directory.

37. The medical device of claim 36, wherein both the configuration data and the patient data are structured as objects in one or more subdirectories, wherein each object is formed in a language that contains both the configuration data and the patient data and that describes both the configuration data and the patient data using textual lags when the object is exported external to the medical device.

38. The medical device of claim 37, wherein a number of objects in one or more subdirectories are defined as constructors, wherein a number of other objects in one or more subdirectories are defined as activators, the constructor being invokable external to the medical device to query an object the activator being invokable external to the medical device to change an object.

39. The medical device of claim 36, further comprising a piece of communication software that contains wired communication protocols and another piece of communication software that contains wireless communication protocols, the device session manager selectively interacting with one of the two pieces of communication software to communicate external to the medical device.

40. The medical device of claim 39, further comprising a device session manager for coordinating the interaction among the number of therapeutic rules, the configuration data, patient data, and one of the two pieces of communication software.

41. The medical device of claim 39, wherein the wired communication protocols include File Transfer Protocol (FTP), Transmission Control Protocol (TCP), Internet Protocol (IP), Lightweight Directory Access Protocol (LDAP), Simple Object Access Protocol (SOAP), Common Object Request Broker Architecture (CORBA) protocol, RS-232-C protocol, HyperLAN, and IEEE 802.x protocols, and wherein the wireless communication protocols include Object Exchange (OBEX) protocol, Infrared Data Association (IrDA) protocols, and Bluetooth protocols.

42. A terminal for communicating with a medical device that stores data, the medical device being installed with a version of software, the terminal comprising:

a data storage device for storing a set of presentation tools;

a user interface being invokable by a presentation tool; and

an interface for importing data stored in the medical device and for allowing the user interface to configure the medical device irrespective of correspondence to the version of software of the medical device, wherein the interface exposes a directory of objects on the medical device so that each object can be accessed, each object referencing data relating to the medical device, and wherein the data to configure the medical device is structured in a language that contains the data and that describes the data through textual tags.

43. The terminal of claim 42, wherein the language includes Extensible Markup Language (XML), wherein the data is structured as an XML element, and wherein upon receiving the data as an XML element, the set of presentation tools are invoked to present the user interface.

44. The terminal of claim 43, wherein the terminal includes a set of agent rules to determine which presentation tool is invoked when the XML element is received by the terminal.

45. The terminal of claim 44, further comprising a device session manager for coordinating the interaction among the set of presentation tools, the user interface, the interface, and the set of agent rules.

46. The terminal of claim 45, further comprising a piece of communication software that contains wired communication protocols and another piece of communication software that contains wireless communication protocols, the device session manager selectively interacting with one of the two pieces of communication software to communicate external to the terminal.

47. The terminal of claim 46, wherein the wired communication protocols include File Transfer Protocol (FTP), Transmission Control Protocol (TCP), Internet Protocol (IP), RS-232-C protocol, and IEEE 802.x protocol, and wherein the wireless communication protocols include Object Exchange (OBEX) protocol and Infrared Data Association (IrDA) protocols.

48. A method for communicating between a medical device and a terminal, comprising:

establishing a communication session between the medical device and the terminal by selecting a wired communication protocol or a wireless communication protocol;

exposing a directory of objects on the medical device so that each object can be accessed by the terminal, each object referencing data relating to the medical device; and

presenting a user interface component to configure the medical device when data is imported into the terminal, the data being structured in a language that contains the data and that describes the data.

49. The method of claim 48, wherein the act of exposing a directory of objects includes exposing objects that have well-known names so that each object can be accessed by the terminal using the well-known name of the object.

50. The method of claim 49, wherein the directory of objects includes activator objects, each activator object being controllable by the user interface component to configure the medical device.

51. The method of claim 49, wherein the directory of objects includes constructor objects, each constructor object being controllable by the user interface component to query the medical device for a piece of data.

52. The method of claim 48, wherein the method does not proceed in the order presented.

53. A medical device comprising:

hardware to apply a therapy to a patient according to a set of therapeutic rules;

one or more data storage devices for storing configuration data and patient data; and

a processor for exposing a directory of objects having well-known names that may be used to invoke the objects external to the medical device, a set of objects being invokable to retrieve configuration data or the patient data, and another set of objects being invokable to change the configuration data so that the therapy to be applied to the patient is changed.

54. The medical device of claim 53, wherein each well-known name includes one or more letters.

55. The medical device of claim 53, wherein each well-known name includes one or more numbers.

56. The medical device of claim 53, wherein each well-known name includes one or more symbols.

57. The medical device of claim 53, wherein each well-known name is composed from a combination of letters, numbers, and symbols.

58. A system comprising:

a defibrillator having a memory storing objects relating to patient data and defibrillator configuration data; and

a device to communicate with the defibrillator to access the patient data and the defibrillator configuration data via the objects,

wherein the data is structured in a language that contains the data and describes the data through textual tags.

59. The system of claim 58, wherein the language includes Extensible Mark Language (XML), the data being structured as one or more XML elements.

60. The system of claim 58, further comprising a second defibrillator having a memory storing objects relating to patient data and defibrillator configuration data, wherein the device communicates with the second defibrillator to access the patient data and the defibrillator configuration data via the objects stored by the memory in the second defibrillator.