METHOD AND APPARATUS FOR AUTOMATIC REGISTRATION OF A PATIENT-BOUND MEDICAL UNIT

• US 20070282175A1
• Filed: 05/29/2007
• Published: 12/06/2007
• Est. Priority Date: 05/30/2006
• Status: Active Grant

• Current Assignee: Biotronik SE & Company KG
• Original Assignee: Biotronik VI Patent AG (Biotronik SE & Company KG)
• Inventors: Urbaszek, Albrecht, Bode, Sven, Diebold, Michael, Seidelt, Andre
• Granted Patent: US 7,859,400 B2
• Time in Patent Office: Days
• US Class Current: 600/300
• CPC Class Codes: A61B 2560/0271 using a remote monitoring unit
• CPC Class Codes: A61B 2560/045 with a separable interface unit, e.g. for communication
• CPC Class Codes: A61B 5/0017 transmitting optical signals transmission by light H04B10/00
• CPC Class Codes: A61B 5/0031 Implanted circuitry
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• 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/67 for remote operation

Abstract

A method for automatic registration of a patient-bound medical device with a remote data processing system, physician identification data being transmitted to the patient-bound medical device, the physician identification data being combined together with device identification data to form a registration message, the registration message being transmitted from the patient-bound medical device to the data processing system, and the data processing system checking the data contained in the registration message and, in case of success, performing the registration, as well as apparatuses for this purpose.

Claims

1. A method for automatic registration of a patient-bound medical device (1) at a remote data processing system (2), comprising:

transmitting physician identification data (102, 201) to the patient-bound medical device (1);

combining the physician identification data together with device identification data to form a registration message (103, 205, 202);

transmitting the registration message (103, 205, 202) by the patient-bound medical device (1) to the data processing system (2); and

,

checking via the data processing system (2) the data contained in the registration message (103, 202) and performing the registration in case of success.

2. The method according to claim 1, further comprising assembling the device identification data from identification data of individual system components (11, 12) of the patient-bound medical device (1).

3. The method according to claim 2, further comprising checking compatibility of the system components (11, 12) via the data processing system (2) using the device identification data.

4. The method according to claim 1, further comprising checking authorization using the physician identification data in the data processing system (2).

5. The method according to claim 1, further comprising:

querying device identification data (101) via a programming device (3) from the patient-bound medical device (1, 11);

combining said device identification data (101) with physician identification data stored in the programming device (3) to form registration message (102); and

,

transmitting said registration message (102) via the programming device (3) to the patient-bound medical device (1, 12).

6. The method according to claim 5, further comprising incorporating personal data in the physician identification data.

7. The method according to claim 5, further comprising transmitting a confirmation (104a) via the data processing system (2) to the patient-bound medical device (1, 12) in the case of successful registration and otherwise transmitting an error message (104b).

8. The method according to claim 1, further comprising:

selecting a key expression (201a) as the physician identification data; and

,

transmitting said physician identification data by a programming device (3) to the patient-bound medical device (1, 11).

9. The method according to claim 8, further comprising transmitting a triggering command (201b) for triggering a registration message from the programming device (3) to the patient-bound medical device (1) and combining the physician identification data with the device identification data stored in the patient-bound medical device to form the registration message in the patient-bound medical device (1).

10. The method according to claim 8, further comprising transmitting a registration request (203) by the programming device (3) to the data processing system (2).

11. The method according to claim 10, further comprising incorporating the device identification data and/or the physician identification data and/or personal data in the registration request (203).

12. The method according to claim 10, further comprising transmitting via the data processing system (2) a confirmation (204a) to the programming device (3) in case of successful registration and otherwise transmitting an error message (204b).

13. The method according to claim 10, further comprising comparing the data contained in the registration message in the data processing system (2) to the data contained in the registration request.

14. The method according to claim 10, further comprising checking in the data processing system (2) whether registration message (202) and associated registration request (203) have been received within a predefined time slot.

15. The method according to claim 10, further comprising checking in the data processing system (2) whether precisely one registration message (202) has been received for a received registration request (203).

16. The method according to claim 5, further comprising producing an infrared connection between the programming device (3) and the patient-bound medical device (1, 12).

17. The method according to claim 5, further comprising producing an Internet connection between the programming device (3) and the data processing system (2).

18. The method according to claim 1, further comprising producing a movable wireless connection between the patient-bound medical device (1, 12) and the data processing system (2).

28. A configuration for executing the method for automatic registration of a patient-bound medical device at a remote data processing system according to claim 1, having a programming device (3) according to claim 19, a patient-bound medical device (1) according to claim 22, and a data processing system (2) according to claim 25.

19. A programming device (3) for programming a patient-bound medical device (1) having at least one interface for transmitting and receiving data and having a memory for storing and retrieving data, means for inputting user data and means for querying device identification data from the patient-bound medical device (1), wherein the programming device is implemented to generate a data structure from the device identification data and the user data and is also implemented to serialize and transmit the data structure as a registration message (102) to the patient-bound medical device (1, 12).

21. The programming device according to claim 19, wherein the data structure has a first data field for storing the device identification data of the first system component (11) of a patient-bound medical device (1) and a second data field for storing the device identification data of a second system component (12) of a patient-bound medical device (1) and further data fields for storing user data.

20. A programming device (3) for programming a patient-bound medical device (1) having at least one interface for transmitting and receiving data and having a memory for storing and retrieving data, means for inputting user data and means for querying device identification data from the patient-bound medical device (1), wherein the programming device is implemented to generate a data structure from the device identification data and the user data, is implemented to serialize and transmit the data structure as a registration request (203) to a data processing system (2), and is also implemented to generate and transmit a triggering command (201) for a registration message to a patient-bound medical device (1, 11).

29. The programming device according to claim 20, wherein the data structure has a first data field for storing the device identification data of the first system component (11) of a patient-bound medical device (1) and a second data field for storing the device identification data of a second system component (12) of a patient-bound medical device (1) and further data fields for storing user data.

22. A patient-bound medical device (1) having at least one interface for transmitting and receiving data and having stored device identification data and configured to transmit a registration message (103, 202) to a data processing system (2).

23. The patient-bound medical device (1, 11) according to claim 22, configured to receive and process physician identification data (201a) and to receive and process a triggering command (201b) for a registration message from a programming device (3).

24. A patient-bound medical device according to claim 22, configured to generate a data structure from the device identification data and the physician identification data and further configured to serialize and transmit the data structure as the registration message (205, 202) to the data processing system (2).

25. A data processing system (2) having at least one communication interface for receiving and transmitting messages (103, 104a, 104b, 202, 203, 204a, 204b) and a memory (21) for storing and retrieving data, wherein said data processing system is configured to receive a registration message (103, 202) from a patient-bound medical device (1) to check the data contained therein, and to register and to transmit a confirmation message (104a, 204a) or an error message (104b, 204b) to a patient-bound medical device (1, 12) and/or to a programming device (3).

26. The data processing system according to claim 25, configured to receive a registration request (203) and, furthermore, to bring together a received registration request (203) with a received registration message (202).

27. The data processing system according to claim 26, further comprising a timer (23) to establish a device time frame and wherein said data processing system is configured to check whether precisely one registration message (202) was received within the time frame for a registration request (203).