MEDICAL DEVICE INFORMATION PORTAL

• US 20130317852A1
• Filed: 03/15/2013
• Published: 11/28/2013
• Est. Priority Date: 05/22/2012
• Status: Abandoned Application

• Current Assignee: Geneva Healthcare, Inc.
• Original Assignee: Geneva Healthcare LLC (Koninklijke Philips N.V.)
• Inventors: Worrell, Kai R., Petrina, Maria E. L., Wadhwa, Manish K., Ungab, GilAnthony D.
• Application Number:
  US13/840,804
• Publication Number:
  US 20130317852A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 40/63 for local operation
• CPC Class Codes: G16H 80/00 ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring

Abstract

The medical device information portal provides a user-friendly platform for presentation of data obtained from device interrogation. The device data is presented in a uniform fashion irrespective of the device manufacturer. Further, the MDI Portal provides easy interpretation of interrogation findings from noticeable differences between normal and abnormal findings.

Claims

1. A medical device information portal comprising:

at least one computing device including at least one processing device; and

at least one computer readable storage device comprising data instructions, which when executed by the computing device cause the at least one computing device to generate;

an authentication engine configured to receive an authentication request from a Health Information Exchange, the authentication engine analyzes the authentication request to determine whether to allow communication with the Health Information Exchange;

a HIE communication engine to transmit and receive communication with the Health Information Exchange, the HIE communication engine is configured to receive patient and device information from the HIE relating to an implantable device, the patient and device information identifying a device vendor for the implantable device;

an interrogation data engine to receive interrogation data relating to interrogation of a medical device;

a device vendor communication engine for querying the device vendor regarding the patient and device information, the device vendor communication engine configured to receive registry and device information from the device vendor; and

a user interface engine that presents the patient and device information from the HIE communication engine, the interrogation data from the interrogation data engine, and the registry and device information from the device vendor communication engine.

2. The medical device information portal of claim 1, wherein the interrogation data engine receives interrogation data from a point-of-care provider via an upload mechanism on the user interface.

3. The medical device information portal of claim 1, wherein the interrogation data engine receives interrogation data from a database from the device vendor.

4. The medical device information portal of claim 1, wherein the user interface engine presents historical information relating to the device.

5. The medical device information portal of claim 1, wherein the user interface engine presents an indication to identify abnormal results in the interrogation data.

6. The medical device information portal of claim 1, wherein the authentication engine receive an authentication request via a single sign on request from a user authenticated to access a patient'"'"'s electronic medical record.

8. The medical device information portal of claim 1, wherein the interrogation data engine receives interrogation data from a point-of-care provider via an upload mechanism on the user interface.

9. The medical device information portal of claim 1, wherein the interrogation data engine receives interrogation data from a database from the device vendor.

10. The medical device information portal of claim 1, wherein the user interface engine presents historical information relating to the device.

11. The medical device information portal of claim 1, wherein the user interface engine presents an indication to identify abnormal results in the interrogation data.

12. The medical device information portal of claim 1, wherein the authentication engine receive an authentication request via a single sign on request from a user authenticated to access a patient'"'"'s electronic medical record.

14. The medical device information portal of claim 1, wherein receiving medical device information associated with a first medical device includes interrogation data uploaded from a point-of-care provider.

15. The medical device information portal of claim 1, wherein receiving medical device information associated with a first medical device includes receiving medical device information associated with a first medical device from a first medical device manufacturer.

16. The medical device information portal of claim 1, wherein receiving medical device information associated with a first medical device includes receiving interrogation data from a device manufacturer database.

17. The medical device information portal of claim 1, wherein the user interface engine presents historical information relating to the device.

18. The medical device information portal of claim 1, wherein the user interface engine presents an indication to identify abnormal results in the interrogation data.

19. The medical device information portal of claim 1, wherein the authentication engine receive an authentication request via a single sign on request from a user authenticated to access a patient'"'"'s electronic medical record.

7. A medical device information portal comprising:

at least one computing device including at least one processing device; and

at least one computer readable storage device comprising data instructions, which when executed by the computing device cause the at least one computing device to generate;

an authentication engine configured to receive an authentication request, the authentication engine analyzes the authentication request to determine whether to allow communication with the medical device information portal;

a EMR communication engine to transmit and receive communication with the EMR System, the EMR communication engine is configured to receive patient and device information from the EMR System relating to an implantable device, the patient and device information identifying a device vendor for the implantable device;

an interrogation data engine to receive interrogation data relating to interrogation of a medical device;

a device vendor communication engine for querying the device vendor regarding the patient and device information, the device vendor communication engine configured to receive registry and device information from the device vendor; and

a user interface engine that presents the patient and device information from the HIE communication engine, the interrogation data from the interrogation data engine, and the registry and device information from the device vendor communication engine.

13. A method of providing access to information relating to medical devices, the method comprising:

receiving medical device information associated with a first medical device;

receiving medical device information associated with a second medical device from a second different medical device manufacturer;

generating a first user interface to display the first medical device information; and

generating a second user interface to display the second medical device information, wherein the second user interface is configured in a common format as the first user interface.