Data Transformation System and Method

• US 20100114993A1
• Filed: 10/31/2008
• Published: 05/06/2010
• Est. Priority Date: 10/31/2008
• Status: Abandoned Application

• Current Assignee: Medtronic Incorporated (Medtronic Plc)
• Original Assignee: Medtronic Incorporated (Medtronic Plc)
• Inventors: Johnson, Kevin M., Bhujle, Sunil S., Porter, Miles R., Holschbach, Jean M., Knoblauch, Karl W.
• Application Number:
  US12/263,410
• Publication Number:
  US 20100114993A1
• Time in Patent Office: Days
• US Class Current: 707/810
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records

Abstract

A data transformation system and method for importing data from an implantable medical device from a particular manufacturer is provided. The data transformation system includes a data transformation engine. The data transformation engine includes a bootstrap subsystem that receives the data in a native format and determines the particular manufacturer. The data transformation engine also includes a data transformation component that categorizes at least some of the data into an object model representation and a data normalization component that normalizes at least some of the data in the object model representation and serializes the object model representation into an extensible markup language file. The data transformation engine further includes a schema transformer that validates the extensible markup language file.

Claims

1. A data transformation engine for obtaining data in a native format from a programmer of an implantable medical device from a particular manufacturer of a plurality of manufacturers, the data transformation engine comprising:

a bootstrap subsystem that receives the data in the native format from the programmer and determines the particular manufacturer;

a data transformation component that categorizes at least some of the data into an object model representation;

a data normalization component that normalizes at least some of the data in the object model representation and serializes the object model representation into an extensible markup language file; and

a schema transformer that validates the extensible markup language file.

2. The data transformation engine of claim 1 wherein the bootstrap subsystem includes a device encyclopedia with detectable attributes about the native format of the particular manufacturer.

3. The data transformation engine of claim 1 wherein the data transformation component determines the at least some of the data to categorize based on the particular manufacturer determined by the bootstrap subsystem.

4. The data transformation engine of claim 1 wherein the data normalization component normalizes the at least some of the data based on the particular manufacturer determined by the bootstrap subsystem.

5. The data transformation engine of claim 1 wherein the at least some of the data includes at least one of static information about the implantable medical device and dynamic information about the implantable medical device.

6. The data transformation engine of claim 5 wherein the static information about the implantable medical device includes at least one of the particular manufacturer, model information, recommended replacement time information, elective replacement time information, warranty information, commentary, serial number information, references, and implant date information.

7. The data transformation engine of claim 5 wherein the dynamic information of the implantable medical device includes at least one of programming information, telemetry information, threshold information, process-related attributes, device-related attributes, and programmer-related attributes.

8. The data transformation engine of claim 7 wherein the programming information includes at least one of pacing mode information, lower rate information, tracking rate information, max sensor rate information, hysteresis rate information, PMT intervention information, automatic model switch information, VV delay information, sensing information, pacing information, rate modulation information, AV delay information, and therapy status information.

9. The data transformation engine of claim 7 wherein the telemetry information includes at least one of battery voltage information, test charge time information, test charge energy information, last high voltage energy information, event counters, and impedance information.

10. The data transformation engine of claim 7 wherein the threshold information includes at least one of amplitude and duration of events stored, atrial fibrillation threshold information, onset stability logic detection parameters, and atrial to ventricular comparison rates.

11. The data transformation engine of claim 7 wherein the process-related attributes include at least one of data type information, operator information, and import date information.

12. The data transformation engine of claim 7 wherein the device-related attributes include at least one of manufacturer attributes, model number information, serial number information, and interrogation date information.

13. The data transformation engine of claim 7 wherein the programmer-related attributes include at least one of programmer software model information, programmer software version information, and programmer hardware model information.

14. The data transformation engine of claim 8 wherein the therapy status information includes at least one of therapy type information, therapy configurations information, shock therapies information, and ATP therapies information.

15. The data transformation engine of claim 1 wherein the extensible markup language file is used for automated testing.

16. A method of transforming data from an implantable medical device having a native format for a particular manufacturer of a plurality of manufacturers, the method comprising:

receiving the data in the native format;

determining the particular manufacturer;

categorizing at least some of the data into an object model representation;

normalizing at least some of the data in the object model representation; and

serializing the object model representation into an extensible markup language file.

17. The method of claim 16 and further comprising validating the extensible markup language file.

18. The method of claim 16 and further comprising providing a server and transmitting the extensible markup language file to the server.

19. The method of claim 16 and further comprising providing a user interface and transmitting the extensible markup language file to the user interface.

20. The method of claim 19 and further comprising modifying the extensible markup language file in relation to a particular software application used by the user interface.