System and method for managing coordination of collected patient data in an automated patient management system

• US 20100063840A1
• Filed: 05/03/2005
• Published: 03/11/2010
• Est. Priority Date: 05/03/2005
• Status: Abandoned Application

• Current Assignee: Cardiac Pacemakers Incorporated (Boston Scientific Corporation)
• Original Assignee: Cardiac Pacemakers Incorporated (Boston Scientific Corporation)
• Inventors: Srivathsa, Muralidharan, Johnson, David C., Simms, Howard D., Hoyme, Kenneth P.
• Application Number:
  US11/121,593
• Publication Number:
  US 20100063840A1
• Time in Patent Office: Days
• US Class Current: 705/3
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A system and method for managing coordination of collected patient data in an automated patient management system is presented. One or more displays of patient data are defined. The patient data is collected from one or more patient data sources operating on a remotely managed patient and selected from at least one of a physiological sensor and a therapy delivery device. One or more controls of patient data collection to specify types of patient data to be collected and periodicities of the patient data collection in relation to the patient data displays are defined. The patient data displays and patient data controls in relation to the data collection of a plurality of patient data types and patient data collection periodicities are coordinated.

Claims

1. A system for managing coordination of collected patient data in an automated patient management system, comprising:

clinician-specific display requirements;

clinician-specific control requirements;

one or more displays of patient data on a server, wherein the patient data is collected from one or more patient data sources operating on a remotely managed patient and selected from at least one of a physiological sensor and a therapy delivery device, wherein the displays are based on the clinician-specific display requirements;

one or more controls of patient data collection on a server, wherein the controls are based on the clinician-specific control requirements and defined to specify types of patient data to be collected and periodicities of the patient data collection in relation to the patient data displays; and

a displayer on a server to coordinate the patient data displays and patient data controls in relation to the data collection of a plurality of patient data types and patient data collection periodicities.

2. A system according to claim 1, wherein the patient data displays are organized comprising at least one of:

a display scheme specified to comprise at least one of default and customized displays of the patient data;

a display scheme specified to comprise at least one of summary and detailed displays of the patient data;

display groups selected to collect patient data from at least one of medical subspecialty,

practice affiliation, organizational affiliation, referring role, following role, billing entity, special permissions, and exceptions;

a subset of the patient data selected through at least one of screen, filtering, and choosing; and

a display scheme specified to comprise hierarchically-structured patient data displays.

3. A system according to claim 1 ,wherein the patient data controls are specified comprising at least one of:

a schedule defined to be associated with at least one such patient data source to provide automated retrieval of the patient data;

a schedule defined to be associated with at least one such patient data source to provide prompted retrieval of the patient data by the remotely managed patient;

a frequency defined to be associated with at least one such patient data source to track on-demand retrieval of the patient data; and

a follow-up scheme defined to be associated with at least one such patient data source executable in an absence of expected patient data assembly;

and a follow-up scheme defined to be associated with at least one of the remotely managed patient, a patient-managing clinician, and an authorized third party executable in an absence of expected patient data collection.

4. A system according to claim 3, wherein conflicts in the patient data collection occurring within a same proximal time span are resolved.

5. A system according to claim 3, wherein conflicts between different schedules are resolved by merging the schedules.

6. A system according to claim 3, wherein conflicts between the different frequencies are resolved by merging the frequencies.

7. A system according to claim 1, wherein the definition of the patient data controls is limited to a subset of clinicians having access to the patient data.

8. A system according to claim 1, further comprising:

one or more triggers on a server defined for each such patient data control and associated with a condition occurring in relation to at least one such patient data evaluateable subsequent to collection; and

a notification scheme determined to be executable upon detection of at least one such trigger to provide an external indicator of the condition occurrence.

9. A system according to claim 1, further comprising:

access control on a server provided to the patient data displays as a hierarchy of permissions with one or more clinicians authorized access in each layer.

10. A system according to claim 1, further comprising:

a database on a server to store the collected patient data, wherein the stored collected patient data is included in relation to the patient data displays.

11. A system according to claim 1, wherein the patient data source comprises at least one of an implantable medical device, implantable diagnostic multi-sensor non-therapeutic device, external medical device, implantable sensor, and external sensor.

12. A method for managing coordination of collected patient data in an automated patient management system, comprising:

defining, on a server, one or more clinician-specific displays of patient data collected from one or more patient data sources operating on a remotely managed patient and selected from at least one of a physiological sensor and a therapy delivery device, wherein the one or more displays are based on clinician-specific display requirements;

defining, on a server, one or more clinician-specific controls of patient data collection to specify types of patient data to be collected and periodicities of the patient data collection in relation to the patient data displays, wherein the one or more controls are based on clinician- specific control requirements; and

coordinating, on a server, the patient data displays and patient data controls in relation to the data collection of a plurality of patient data types and patient data collection periodicities.

13. A method according to claim 12, further comprising:

organizing the patient data displays, comprising at least one of;

specifying a display scheme comprising at least one of default and customized displays of the patient data;

specifying a display scheme comprising at least one of summary and detailed displays of the patient data;

collecting the patient data into display groups selected from at least one of medical subspecialty, practice affiliation, organizational affiliation, referring role, following role, billing entity, special permissions, and exceptions;

selecting a subset of the patent data through at least one of screen, filtering, and choosing; and

specifying a display scheme comprising hierarchically-structured patient data displays.

14. A method according to claim 12, further comprising:

specifying the patient data controls, comprising at least one of;

defining a schedule associated with at least one such patient data source to provide automated retrieval of the patient data;

defining a schedule associated with at least one such patient data source to provide prompted retrieval of the patient data by the remotely managed patient;

defining a frequency associated with at least one such patient data source to track on-demand retrieval of the patient data; and

defining a follow-up scheme associated with at least one such patient data source executable in an absence of expected patient data assembly; and

defining a follow-up scheme associated with at least one of the remotely managed patient, a patient-managing clinician, and an authorized third party executable in an absence of expected patient data collection.

15. A method according to claim 14, further comprising:

resolving conflicts in the patient data collection occurring within a same proximal time span.

16. A method according to claim 14, further comprising:

resolving conflicts between different schedules by merging the schedules.

17. A method according to claim 14, further comprising:

resolving conflicts between the different frequencies by merging the frequencies.

18. A method according to claim 12, further comprising:

limiting the definition of the patient data controls to a subset of clinicians having access to the patient data.

19. A method according to claim 12, further comprising:

defining one or more triggers on a server for each such patient data control and associated with a condition occurring in relation to at least one such patient data evaluateable subsequent to collection; and

determining a notification scheme executable upon detection of at least one such trigger to provide an external indicator of the condition occurrence.

20. A method according to claim 12, further comprising:

providing access control on a server to the patient data displays as a hierarchy of permissions with one or more clinicians authorized access in each layer.

21. A method according to claim 12, further comprising:

storing the collected patient data on a server; and

including the stored collected patient data in relation to the patient data displays.

22. A method according to claim 12, wherein the patient data source comprises at least one of an implantable medical device, implantable diagnostic multi-sensor non-therapeutic device, external medical device, implantable sensor, and external sensor.

23. A computer-readable storage medium for managing coordination of collected patient data in an automated patient management system comprising:

code for defining, on a server, one or more clinician-specific displays of patient data collected from one or more patient data sources operating on a remotely managed patient and selected from at least one of a physiological sensor and a therapy delivery device, wherein the one or more displays are based on clinician-specific display requirements;

code for defining, on a server, one or more clinician-specific controls of patient data collection to specify types of patient data to be collected and periodicities of the patient data collection in relation to the patient data displays, wherein the one or more controls are based on clinician-specific control requirements; and

code for coordinating, on a server, the patient data displays and patient data controls in relation to the data collection of a plurality of patient data types and patient data collection periodicities.

24. (canceled)