MEDICAL DATA MANAGEMENT

• US 20090132282A1
• Filed: 10/25/2005
• Published: 05/21/2009
• Est. Priority Date: 10/25/2005
• Status: Abandoned Application

• Current Assignee: St. Jude Medical AB (Abbott Laboratories Incorporated)
• Original Assignee: St. Jude Medical AB (Abbott Laboratories Incorporated)
• Inventors: Kerstna, Jurgen, Malmberg, Patrik
• Application Number:
  US12/091,128
• Publication Number:
  US 20090132282A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06F 21/6245 Protecting personal data, e.g. for financial or medical purposes
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records

Abstract

For exchanging medical data in a healthcare system having multiple patient domains, with at least one of these domains being isolated from the other domains by virtue of a patient identifier for the other domains not having access to patient identifiers used by the isolated domain, patient-related data for a given patient are provided and are sent to this manager. The manager compares the data with stored data to identify an identifier of the given patient utilized by one of the other domains. This identifier is returned to the isolated domain, wherein it is employed for enabling an association of locally or externally generated medical data of the patient with an externally or locally utilized identifier of the patient with an externally or locally utilized identifier of the patient. The isolated domain may utilize model and serial numbers of implantable medical devices as the patient identifiers.

Claims

1. A method of managing medical patient data in a healthcare system comprising a first patient domain, a second patient domain having domain-dedicated patient identifiers for identifying patients within said second patient domain and a patient identifier manager having patient-related data associatively stored with patient-identifiers utilized by said second patient domain, said method comprising, in said first patient domain:

providing patient-related data of a given patient;

requesting, from said patient identifier manager and based on said provided patient-related data, a patient identifier associated with said given patient (and utilized by said second patient domain; and

associating medical data of said given patient (with said requested patient identifier.

2-3. -3. (canceled)

4. A method of managing medical patient data in a healthcare system comprising a first patient domain having domain-dedicated patient identifiers for locally identifying patients within said first patient domain, a second patient domain having domain-dedicated patient identifiers for identifying patients (within said second patient domain and a patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second patient domain, said method comprising, in said first patient domain:

providing patient-related data of a given patient (5);

requesting, from said patient identifier manager and based on said provided patient-related data, a patient identifier associated with said given patient and utilized by said second patient domain;

requesting, from an external medical data storage and based on said requested patient identifier, medical data of said given patient; and

associating said requested medical data with a patient identifier associated with said given patient and utilized locally within said first patient domain.

5. The method according to claim 4, wherein said healthcare system comprises said first patient domain, said second patient domain and a third patient domain, said patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second and said third patient domains, said method further comprising providing, in said first patient domain, a domain identifier associated with said second or third patient domain, and said requesting step comprises requesting, based on said provided patient-related data and said domain identifier, a patient identifier associated with said given patient and utilized by the patient domain associated with said domain identifier.

6. The method according to claim 5, comprising arranging said patient identifier manager said second patient domain.

7. The method according to claim 5, comprising arranging said patient identifier manager in said healthcare system for secure communication with said first patient domain and said second patient domain.

8. The method according to claim 4, comprising providing a patient identifier source n said patient domain having domain-dedicated patient identifiers for identifying patients within said patient domain and providing a patient identifier requester for requesting, from said patient identifier manager, patient identifiers utilized by external patient domains.

9. The method according to claim 8, comprising, in said patient identifier source of said first patient domain storing serial and model numbers of medical devices implanted in patients and comprising embodying said patient identifier requester a programmer configured for communication with said implanted medical devices and communication with said patient identifier manager.

10. The method according to claim 9 comprising, said providing said patient related data by:

uploading at least a portion of said patient-related data from a medical device implanted in said given patient; and

entering said uploaded patient-related data in a search query in said patient identifier requester.

12. The method according to any of the claim 8, comprising entering said patient-related data in a search query in said patient identifier requester.

13. The method according to any of the claim 8, comprising said patient identifier requester inserting, in a search query and based on entered patient-related data of said given patient, further patient-related data of said given patient stored in connection with said patient identifier requester.

11. (canceled)

14. The method according to said patient identifier by:

sending said patient-related data to said patient identifier manager;

receiving, from said patient identifier manager, a list of patient identifiers matching said patient-related data; and

selecting said patient identifier from said list.

15. The method according to claim 14, comprising sending more patient-related data of said given patient until said patient identifier associated with said given patient can be unambiguously identified from said received list.

16. The method according to claim 15, comprising sending step said patient related data by:

sending initial patient-related data from a first set of patient-related data to said patient identifier manager; and

sending said more patient-related data, until said patient identifier associated with said given patient can be unambiguously identified from said received list, from another set of patient-related data to said patient identifier manager.

17. (canceled)

18. An arrangement for managing medical patient data in a healthcare system, said healthcare system 1 comprising a first patient domain, a second patient domain (having domain-dedicated patient identifiers for identifying patients (within said second patient domain and a patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second patient domain, said arrangement having implemented in said first patient domain and comprising:

a source of patient-related data of a given patient;

an identifier requester configured to request, from said patient identifier manager and based on said provided patient-related data, a patient identifier associated with said given patient and utilized by said second patient domain; and

an association unit configured to associate medical data of said given patient with said requested patient identifier.

19. The arrangement according to claim 18, comprising a forwarding unit configured to forward said medical patient data associated with said patient identifier to an external medical data storage.

20. An arrangement for managing medical patient data in a healthcare system, said healthcare system comprising a first patient domain having domain-dedicated patient identifiers for locally identifying patients within said first patient domain, a second patient domain (having domain-dedicated patient identifiers for identifying patients (within said second patient domain and a patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second patient domain, said arrangement is implemented in said first patient domain (and comprising:

a source of patient-related data of a given patient;

an identifier requester configured to request, from said patient identifier manager and based on said provided patient-related data, a patient identifier associated with said given patient and utilized by said second patient domain;

a data requester configured to request, from an external medical data storage and based on said requested patient identifier, medical data of said given patient; and

association unit configured to associate said requested medical data with a patient identifier associated with said given patient and utilized locally within said first patient domain.

21. The arrangement according to claim 20, wherein said healthcare system comprises said first patient domain, said second patient domain and a third patient domain, said patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second (M and said third patient domains, said arrangement further comprising means a source of a domain identifier associated with said second or third patient domain, and wherein said identifier requestor is configured to request, based on said provided patient-related data and said domain identifier, a patient identifier associated with said given patient and utilized by the patient domain associated with said domain identifier.

22. The arrangement according to claim 20, wherein said source comprises:

a user interface for receiving patient-related data; and

an input unit for entering said patient-related data in a search query.

23. The arrangement according to claim 20, wherein said source is configured to upload at least a portion of said patient-related data from a medical device implanted in said given patient and to enter said uploaded patient-related data in a search query.

24. The arrangement according to claim 23, wherein said input unit is configured to insert, in said search query, further patient-related data of said patient stored in a memory accessible in said first patient domain based on entered said patient-related data received by said user interface.

25. The arrangement according to claim 20, wherein said identifier requester is configured to send said patient-related data to said patient identifier manager, for receiving, from said patient identifier manager, a list of patient identifiers matching said patient-related data, and for selecting said patient identifier from said list.

26. The arrangement according to claim 25, wherein said identifier requestor is configured to send more patient-related data of said patient until said patient identifier associated with said given patient can be unambiguously identified from said list.

27. The arrangement according to claim 26, wherein said identifier requester is configured to send initial patient-related data from a first set of patient-related data to said patient identifier manager and to send, until said patient identifier associated with said given patient can be unambiguously identified from said list, patient-related data from another set of said move patient-related data so said patient identifier manager

28-29. -29. (canceled)

30. A method of managing medical patient data in a healthcare system comprising a first patient domain, a second patient domain (having domain-dedicated patient identifiers for identifying patients within said second patient domain and a patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second patient domain, said method comprising:

providing, in said first patient domain, patient-related data of a given patient;

sending said patient-related data from said first patient domain to said patient identifier manager;

said patient identifier manager identifying at least one patient identifier associated with said given patient and having associated patient-related data that matches said patient-related data received from said first patient domain;

said patient identifier manager transmitting said identified at least one patient identifier to said first patient domain; and

associating, in said first patient domain, medical data of said given patient with said at least one patient identifier.

31. A method of managing medical patient data in a healthcare system comprising a first patient domain, a second patient domain (having domain-dedicated patient identifiers for identifying patients within said second patient domain (and a patient identifier manager having patient-related data associatively stored with patient identifiers utilized by said second patient domain, said method is characterized by:

providing, in said first patient domain, patient-related data of a given patient;

sending said patient-related data from said first patient domain to said patient identifier manager;

said patient identifier manager identifying at least one patient identifier associated with said given patient and having associated patient-related data that matches said patient-related data received from said first patient domain;

said patient identifier manager transmitting said identified at least one patient identifier to said first patient domain;

sending said at least one patient identifier to an external medical data storage;

returning from said external medical data storage medical data of said given patient; and

associating, in said first patient domain, said returned medical data with a patient identifier associated with said given patient and utilized locally within said first patient domain.