Aggregation and sharing of patient data

• US 20040088374A1
• Filed: 10/31/2002
• Published: 05/06/2004
• Est. Priority Date: 10/31/2002
• Status: Abandoned Application

• Current Assignee: Medtronic Incorporated (Medtronic Plc)
• Original Assignee: Medtronic Incorporated (Medtronic Plc)
• Inventors: Webb, James D., Nelson, Chester G.
• Application Number:
  US10/284,921
• Publication Number:
  US 20040088374A1
• Time in Patent Office: Days
• US Class Current: 709/218
• CPC Class Codes: G16H 40/67 for remote operation
• 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

Techniques are described for acquisition of physiological data from a medical device, and manipulation and storage of the physiological data in a format that can allows the data to easily be shared between systems and viewed using different applications. Moreover, the techniques provide for the aggregation of the physiological data acquired from a medical device over multiple telemetry sessions. A system, for example, includes a plurality of medical device programmers to collect physiology data via telemetry sessions with medical devices, and a programmer gateway to receive the session data from the medical device programmers and to process the session data for aggregation in one or more data stores. The session data may include metadata that conforms to a data description language, such as XML, and the programmer gateway may execute a translation engine to store portions of the session data within respective data stores based on the metadata.

Claims

1. A device comprising:

a data processing module to transform session data received from a medical device via a telemetry session into one or more web pages in accordance with one or more style sheets; and

a web server to present the web pages to a remote user.

2. The device of claim 1, wherein the data processing module comprises an Extensible Style Language Transformations (XSLT) processor to transform the session data into the web pages in accordance with XSLT style sheets.

3. The device of claim 1, further comprising a computer-readable medium to store the session data in a format that conforms to a data description language.

4. The device of claim 3, wherein the data description language comprises the extensible markup language (XML).

5. The device of claim 1, further comprising a translation engine to receive the session data and process the session data to aggregate the session data in one or more data stores and in a format that conforms to a data description language.

6. The device of claim 5, wherein data description language comprises the extensible markup language (XML), and the translation engine stores the session data in XML data files.

7. The device of claim 6, wherein the translation engine operates in accordance with translation instructions provided in at least one of Java, C, C++, Visual Basic, ASP, COM objects, Java Beans, ActiveX components, and Web Services.

8. The device of claim 1, wherein the device comprises a medical device programmer to receive the session data from a medical device via telemetry.

9. The device of claim 1, wherein the device comprises a programmer gateway to receive the session data from one of a plurality of medical device programmers.

10. A device comprising a translation engine to receive session data acquired via telemetry sessions with a medical device, and to process the session data for aggregation in one or more data stores in a format that conforms to a data description language.

11. The device of claim 10, wherein the translation engine selects respective data stores to store portions of the session data based on metadata of the data description language.

12. The device of claim 10, wherein data description language comprises the extensible markup language (XML), and the translation engine stores the session data in XML data files.

13. The device of claim 10, wherein the translation engine identifies any data that spans multiple sessions and recombines the session data with session data of similar type within the data stores, and discards any session data that is duplicated across multiple patient sessions.

14. The device of claim 10, further comprising:

a data processing module to transform the session data into one or more web pages in accordance with one or more style sheets; and

a web server to present the web pages to a remote user.

15. The device of claim 14, wherein the data processing module comprises an Extensible Style Language Transformations (XSLT) processor to transform the session data into the web pages in accordance with XSLT style sheets.

16. The device of claim 10, wherein the device comprises a medical device programmer to receive the session data directly from at least one of the medical devices.

17. The device of claim 10, wherein the device comprises a programmer gateway to receive the session data from one of a plurality of medical device programmers.

18. A system comprising:

a plurality of medical device programmers to collect session data from medical devices via telemetry sessions; and

a programmer gateway to receive the session data from the medical device programmers, and to process the session data for aggregation in one or more data stores.

19. The system of claim 18, wherein the session data includes metadata that conforms to a data description language, and the programmer gateway provides an operating environment for a translation engine to store portions of the session data within respective data stores based on the metadata.

20. The system of claim 19, wherein data description language comprises the extensible markup language (XML), and the translation engine stores the session data in XML data files.

21. The system of claim 18, wherein the programmer gateway further comprises:

a data processing module to transform session data acquired from a medical device into one or more web pages in accordance with one or more style sheets; and

a web server to present the web pages to a remote user.

22. The device of claim 21, wherein the data processing module comprises an Extensible Style Language Transformations (XSLT) processor to transform the session data into the web pages in accordance with XSLT style sheets.

23. A system comprising:

a plurality of distributed peer servers having data stores of session data received from medical devices via telemetry sessions; and

a client device executing a peer-to-peer client software application for accessing the session data directly from the distributed servers.

24. The system of claim 23, wherein the peer-to-peer client software application provides a search interface for identifying session data stored at the peer servers.

25. The system of claim 24, wherein the search interface of the peer-to-peer software application allows a user to search the session data based on at least one of a patient name and a device serial number.

26. The system of claim 23, wherein the peer servers are located at a plurality of entities that acquired the session data from medical devices via telemetry sessions with medical device programmers, and the peer-to-peer client software application allows a user to retrieve and view the session data directly from the peer servers of entities.

27. The system of claim 23, wherein the session data includes metadata that conforms to a data description language, and the peer servers execute a translation engines to store portions of the session data within respective data stores based on the metadata.

28. The system of claim 23, wherein data description language comprises the extensible markup language (XML), and the translation engine stores the session data in XML data files.

29. The system of claim 23, wherein each of the peer server further comprise:

a data processing module to transform session data into one or more web pages in accordance with one or more style sheets; and

a web server to present the web pages to a remote user via the peer-to-peer client software application.

30. A method comprising:

receiving session data acquired via telemetry sessions with a medical device; and

processing the session data for aggregation in one or more data stores and in a format that conforms to a data description language.

31. The method of claim 30, wherein the session data includes metadata that conforms to the data description language and includes elements that encapsulate the session data, the method further comprising selecting respective data stores to store portions of the session data based on the metadata.

32. The method of claim 31, wherein the data description language comprises the extensible markup language (XML), and the method further comprises storing the session data in XML data files.

33. The method of claim 32, further comprising processing the session data in accordance with translation instructions provided in an XML format.

34. The method of claim 30, further comprising transforming the session data acquired into one or more web pages in accordance with one or more style sheets

35. The method of claim 34, wherein transforming the session data comprises transforming the session data using an Extensible Style Language Transformations (XSLT) processor in accordance with XSLT style sheets.

36. The method of claim 34, further comprising presenting the web pages to a remote user via a web server.

37. The method of claim 30, further comprising presenting the session data to a remote user via a peer-to-peer software application.

38. The method of claim 30, wherein receiving the session data comprises receiving the session data directly from at least one of the medical devices.

39. The method of claim 30, wherein receiving the session data comprises receiving the session data at a programmer gateway from one or more medical device programmers.

40. A computer-readable medium comprising instructions to cause a processor to:

receive session data acquired via telemetry sessions with a medical device; and

process the session data for aggregation in one or more data stores in a format that conforms to a data description language.

41. The computer-readable medium of claim 40, wherein the session data includes metadata that conforms to the data description language and includes elements that encapsulate the session data, and the instructions cause the processor to select respective data stores to store portions of the session data based on the metadata.

42. The computer-readable medium of claim 41, wherein the data description language comprises the extensible markup language (XML), and the instructions cause the processor to store the session data in XML data files.

43. The computer-readable medium of claim 42, wherein the instructions cause the processor to process the session data in accordance with translation instructions provided in an XML format.

44. The computer-readable medium of claim 40, wherein the instructions cause the processor to transform the session data acquired into one or more web pages in accordance with one or more style sheets

45. The computer-readable medium of claim 44, wherein the instructions cause the processor to transform the session data using an Extensible Style Language Transformations (XSLT) processor in accordance with XSLT style sheets.

46. The computer-readable medium of claim 44, wherein the instructions cause the processor to present the web pages to a remote user via a web server.

47. The computer-readable medium of claim 40, wherein the instructions cause the processor to present the session data to a remote user via a peer-to-peer software application.

48. The computer-readable medium of claim 40, wherein the instructions cause the processor to receive the session data directly from at least one of the medical devices.

49. The computer-readable medium of claim 40, wherein the instructions cause the processor to receive the session data at a programmer gateway from one or more medical device programmers.

50. A method comprising:

receiving login information from a clinician;

accessing clinician-specific preferences based on the login information; and

applying the clinician-specific preferences to a medical device programmer.

51. The method of claim 50, further comprising validating the login information to verify that the clinician is authorized to access the programmer.

52. The method of claim 50, wherein receiving login information from a clinician comprises receiving a user name and password.

53. The method of claim 50, wherein accessing clinician-specific information comprises retrieving the clinician specific preferences from a programmer gateway.