Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20100063840 A1
Publication typeApplication
Application numberUS 11/121,593
Publication date11 Mar 2010
Filing date3 May 2005
Priority date3 May 2005
Publication number11121593, 121593, US 2010/0063840 A1, US 2010/063840 A1, US 20100063840 A1, US 20100063840A1, US 2010063840 A1, US 2010063840A1, US-A1-20100063840, US-A1-2010063840, US2010/0063840A1, US2010/063840A1, US20100063840 A1, US20100063840A1, US2010063840 A1, US2010063840A1
InventorsKenneth P. Hoyme, Howard D. Simms, David C. Johnson, Muralidharan Srivathsa
Original AssigneeHoyme Kenneth P, Simms Howard D, Johnson David C, Muralidharan Srivathsa
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
System and method for managing coordination of collected patient data in an automated patient management system
US 20100063840 A1
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.
Images(7)
Previous page
Next page
Claims(24)
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)
Description
    FIELD OF THE INVENTION
  • [0001]
    The present invention relates in general to automated patient management and, specifically, to a system and method for managing coordination of collected patient data in an automated patient management system.
  • BACKGROUND OF THE INVENTION
  • [0002]
    A patient's medical history is a key source of information used in modern clinical practice. A medical history is used to collect information obtained directly from the patient and data gathered from other sources in-clinic, as well as from interrogations of medical devices and sensors, for example, implantable medical devices (IMDs), such as pacemakers or defibrillators. A medical history documents the patient's physical status and physiological, social, and sexual functions and provides a basis for diagnosis, treatment, care, and follow-up. The medical history often includes written and transcribed notes supplemented by laboratory and testing documentation and medical device and sensor telemetry data. Medical histories are reviewed by healthcare providers prior to patient interviews and to provide referrals or consultations to colleagues and other authorized health care professionals.
  • [0003]
    Increasingly, patient medical histories are being maintained in digital form on electronic medical record (EMR) systems, which maintain a set of patient medical records collectively storing patient information, including medical histories, as well as appointment, billing, insurance, and other patient data. Due to patient privacy concerns, such as the Health Insurance Portability and Accountability Act (HIPAA) and the European Privacy Directive (EPD) mandates, as well as pragmatic considerations, EMR systems are generally intended only for in-clinic or in-hospital use by clinicians that are formally affiliated with the organization or entity responsible for the EMR system.
  • [0004]
    As an adjunct to EMR systems, alternative data collection methods for interrogations of medical devices and sensors, such as transtelephonic monitoring, can enable a healthcare provider to provide limited remote patient management on a more frequent, often monthly, basis. In addition, dedicated remote patient management devices, such as repeaters, have enabled healthcare providers to remotely perform follow-up monitoring on a daily basis using a data communications network, such as the Internet. Due to concerns similar to those relating to EMR systems, the patient data obtained through these data collection methods are also generally intended only for use by clinicians that are formally affiliated with the clinic, hospital or organization. Moreover, the devices used to interrogate the medical devices and sensors are generally configured to operate as stand-alone systems that operate independently from other interrogation devices and records systems.
  • [0005]
    Consequently, cooperative collection of and access to patient information by authorized, but non-affiliated clinicians, is not available due to the artificial constraints of formal affiliation and for a lack of controls for facilitating the coordination of the types of patient data needed and the intervals at which such patient data is collected by multiple, cooperating clinicians.
  • [0006]
    Therefore, there is a need for a cooperative approach to providing automated patient management of remote patients for a plurality of clinicians that can have differing patient data type and collection interval needs. Preferably, such an approach would allow groups of clinicians to independently or cooperatively define flexible patient data display and collection requirements.
  • SUMMARY OF THE INVENTION
  • [0007]
    A system and method includes accommodating the needs of a plurality of clinicians, such as individual physicians and organizations, by providing clinician-specific display, clinician-specific control, and clinician coordination of collected patient data. Patient data is collected from patient data sources, including implantable and external medical devices and sensors. A set of individual displays of the patient data are provided for presenting various views of the patient data, formatted, for instance, for viewing as Web pages, in hard copy, and in other forms of physical media. A set of controls are also provided to specify the types of patient data that are to be collected and the associated periodicities with which those types of patient data will be collected. Finally, different clinician needs for patient data display and collection are coordinated where possible or practicable, for example, by reconciling and merging patient data collection schedules.
  • [0008]
    One embodiment provides a system and method for managing coordination of collected patient data in an automated patient management system. 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.
  • [0009]
    Still other embodiments of the present invention will become readily apparent to those skilled in the art from the following detailed description, wherein are described embodiments of the invention by way of illustrating the best mode contemplated for carrying out the invention. As will be realized, the invention is capable of other and different embodiments and its several details are capable of modifications in various obvious respects, all without departing from the spirit and the scope of the present invention. Accordingly, the drawings and detailed description are to be regarded as illustrative in nature and not as restrictive.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0010]
    FIG. 1 is a functional block diagram showing, by way of example, an automated patient management environment, in accordance with one embodiment.
  • [0011]
    FIG. 2 is a functional block diagram showing data collection in the environment of FIG. 1.
  • [0012]
    FIG. 3 is a process flow diagram showing collected patient data coordination in the environment of FIG. 1.
  • [0013]
    FIG. 4 is a data flow diagram showing collected patient data display settings for use in the environment of FIG. 1.
  • [0014]
    FIG. 5 is a screen diagram showing, by way of example, a patient data display generated by the server of FIG. 1.
  • [0015]
    FIG. 6 is a functional block diagram showing, by way of example, hierarchically structured patient data displays provided in the environment of FIG. 1, in accordance with a further embodiment.
  • [0016]
    FIG. 7 is a functional block diagram showing a server for managing coordination of collected patient data in an automated patient management system for use in the environment of FIG. 1.
  • DETAILED DESCRIPTION Automated Patient Management Environment
  • [0017]
    Automated patient management encompasses a range of activities, including remote patient management and automatic diagnosis of patient health, such as described in commonly-assigned U.S. Patent application Pub. No. US 2004/0103001, pending, published May 27, 2004, the disclosure of which is incorporated by reference. Such activities can be performed proximal to a patient, such as in the patient's home or office, through a centralized server, such as in a hospital, clinic or physician's office, or through a remote workstation, such as a secure wireless mobile computing device. FIG. 1 is a functional block diagram showing, by way of example, an automated patient management environment 10, in accordance with one embodiment. An individual patient 11 is remotely managed through one or more data collection devices 17, for example, such as described in commonly-assigned U.S. Patent application, entitled, “System and Method for Managing Alert Notifications in an Automated Patient Management System,” Ser. No. ______, filed May 3, 2005, pending, the disclosure of which is incorporated by reference. Each data collection device 17 is interconnected remotely over an internetwork 22, such as the Internet to a centralized server 18. The internetwork 22 can provide both conventional wired and wireless interconnectivity. In one embodiment, the internetwork 22 is based on the Transmission Control Protocol/Internet Protocol (TCP/IP) network communication specification, although other types or combinations of networking implementations are possible. Similarly, other network topologies and arrangements are possible.
  • [0018]
    Each data collection device 17 is uniquely assigned to an individual patient 11 to provide a localized and network-accessible interface to one or more patient data sources 12-16, either through direct means, such as wired connectivity, or through indirect means, such as inductive, radio frequency or wireless telemetry based on, for example, “strong” Bluetooth or IEEE 802.11 wireless fidelity “WiFi” interfacing standards. Other configurations and combinations of patient data source interfacing are possible.
  • [0019]
    Patient data includes physiological measures, which can be quantitative or qualitative, parametric data regarding the status and operational characteristics of the patient data source itself, and environmental parameters, such as the temperature or time of day. Other types of patient data are possible. The patient data sources collect and forward the patient data either as a primary or supplemental function. Patient data sources include, by way of example, medical devices that deliver or provide therapy to the patient 11, sensors that sense physiological data in relation to the patient 11, and measurement devices that measure environmental parameters occurring independent of the patient 11. Each patient data source can generate one or more types of patient data and can incorporate one or more components for delivering therapy, sensing physiological data and measuring environmental parameters. In a further embodiment, data values could be entered by a patient 11 directly into a patient data source. For example, answers to health questions could be input into a measurement device that includes interactive user interfacing means, such as a keyboard and display or microphone and speaker. Such patient-provided data values could also be collected as patient information. Additionally, measurement devices are frequently incorporated into medical devices and sensors. Medical devices include implantable medical devices (IMDs) 12, such as pacemakers, implantable cardiac defibrillators (ICDs), drug pumps, and neuro-stimulators, and external medical devices (EMDs) 14, such as automatic external defibrillators (AEDs). Sensors include implantable sensors 13, such as implantable heart and respiratory monitors and implantable diagnostic multi-sensor non-therapeutic devices, and external sensors 15, 16, such as Holter monitors, weight scales, and blood pressure cuffs. Other types of medical, sensing, and measuring devices, both implantable and external, are possible.
  • [0020]
    The data collection device 17 collects and temporarily stores patient data from the patient data sources 12-16 for periodic upload over the internetwork 22 to the server 18 and storage in a database 21. Patient data collection can be defined to be initiated by either the patient collection device 17 or by one or more of the patient data sources 12-16. The collected patient data can also be accessed and analyzed by one or more locally-configured clients 19 a-b or one or more remote clients 20 a-d securely-interconnected over the internetwork 22, as further described below with reference to FIGS. 3 and 4. Access to the collected patient data includes a capability to provide flexible display and control that is securely and intelligently coordinated between a plurality of clinicians, such as physicians, nurses, or qualified medical specialists. In a further embodiment, the clients 19 a-b and remote clients 20 a-d can be used, for example, by clinicians to select and prioritize patients for health care provisioning, such as described in commonly-assigned U.S. Patent application, entitled, “System and Method for Managing Patient Triage in an Automated Patient Management System,” Ser. No. ______, filed May 3, 2005, pending, the disclosure of which is incorporated by reference. Although described herein with reference to clinicians, the entire discussion applies equally to organizations, including hospitals, clinics, and laboratories, and other individuals or interests, such as researchers, scientists, universities, and governmental agencies, seeking access to the patient data.
  • [0021]
    The collected patient data can also be evaluated for the occurrence of one or more conditions, such as described in related, commonly-owned U.S. Pat. No. 6,336,903, to Bardy, issued Jan. 8, 2002; U.S. Pat. No. 6,368,284, to Bardy, issued Apr. 9, 2002; U.S. Pat. No. 6,398,728, to Bardy, issued Jun. 2, 2002; U.S. Pat. No. 6,411,840, to Bardy, issued Jun. 25, 2002; and U.S. Pat. No. 6,440,066, to Bardy, issued Aug. 27, 2002, the disclosures of which are incorporated by reference. Patient data evaluation can be defined to be performed by either the patient collection device 17 or the server 18.
  • [0022]
    Finally, conditions occurring in the collected patient data can trigger one or more alert notifications that provide external indicators of the condition occurrences. Alert notification can be defined to be performed by either the server 18, patient collection device 17, or one or more other devices either operating as part of or as an adjunct to the internetwork 22.
  • [0023]
    In a further embodiment, patient data is safeguarded against unauthorized disclosure to third parties, including during collection, assembly, evaluation, transmission, and storage, to protect patient privacy and comply with recently enacted medical information privacy laws, such as the Health Insurance Portability and Accountability Act (HIPAA) and the European Privacy Directive. At a minimum, patient health information that identifies a particular individual with health- and medical-related information is treated as protectable, although other types of sensitive information in addition to or in lieu of specific patient health information could also be protectable.
  • [0024]
    Preferably, the server 18 is a server-grade computing platform configured as a uni-, multi- or distributed processing system, and the clients 19 a-b and remote clients 20 a-d are general-purpose computing workstations, such as a personal desktop or notebook computer. In addition, the data collection device 17, server 18, clients 19 a-b, and remote clients 20 a-d are programmable computing devices that respectively execute set of software programs 23, 24, 25, 26 and include components conventionally found in computing device, such as, for example, a central processing unit (CPU), memory, network interface, persistent storage, and various components for interconnecting these components.
  • Data Collection
  • [0025]
    Automated patient management allows a potentially enormous amount of patient data to be generated through substantially continuous monitoring and the amount and frequency of such patient data generation can be controlled through data collection management. FIG. 2 is a functional block diagram showing data collection 40 in the environment 10 of FIG. 1. The data collection process reflects the dichotomy of data collection device-versus patient data source-initiated data collection.
  • [0026]
    Patient data sources that operate autonomously from the patient are generally able to record patient data at any time and under any conditions. However, the recorded patient data accumulated by the patient data source must be periodically uploaded to free limited onboard storage and to facilitate processing and analysis. In one embodiment, schedules can be associated with a subset of the interfaced patient data sources to provide data collection device-initiated patient data collection. Alternatively, a schedule can also be provided to initiate prompted retrieval of patient data by the remotely managed patient. For example, the patient might be instructed to complete a measurement, such as by using an inductive wand on a legacy repeater to interrogate an implanted medical device or sensor or to take a weight or blood pressure reading. The patient could be sent a message or an indicator light or signal on the data collection device 17 could be turned on as a reminder. Other forms of prompted data retrieval are possible. A schedule might be appropriate for a patient data source, such as an implanted cardiac pulse generator, where patient data may be collected on a daily or weekly basis. The schedule can either be built into the data collection device 17 or can be provided by the server 18, based on configuration options selected by the clinician. The data collection device attempts to collect patient data at a scheduled interval by sending requests 41 to the associated patient data source, which returns patient data 42. In the absence of expected patient data receipt, the data collection device 17 can implement a follow-up scheme with the patient data source, if possible, to investigate delayed or missing patient data, or by sending a message or other communication to the patient 11, clinician or authorized third party as a compliance notification.
  • [0027]
    Scheduled data collection might not be appropriate for all patient data sources 12-16. For example, a battery powered weight scale that uses radio frequency telemetry to communicate with a data collection device 17 would normally be turned off to extend battery life. Ordinarily, such a device would communicate with the data collection device 17 only after use by the patient and would otherwise be in a standby or sleep state. Such devices frequently operate in a send-only mode and may therefore be incapable of receiving incoming messages. The patient data source asynchronously sends patient data 42 to the data collection device 17 to provide patient data source-initiated patient data collection. In one embodiment, frequencies can be associated with a subset of the interfaced patient data sources to allow the data collection device 17 to track or limit the receipt of patient data. In the absence of expected patient data receipt, the data collection device 17 can implement a follow-up scheme with the patient data source, if possible, to investigate delayed or missing patient data, or by sending a message or other communication to the patient 11, clinician or authorized third party as a compliance notification.
  • [0028]
    Finally, collected patient data 43 is uploaded by the data collection device 17 to the server 18 either upon receipt or, in a further embodiment, after a delay to allow patient data 42 from multiple patient data sources to accumulate. The server 18 stores the uploaded patient data 43 in the database 21 as collected patient data.
  • Collected Patient Data Coordination
  • [0029]
    Each clinician may have different needs for the display and collection of patient data. For example, an cardiologist might need to review different arrangements of patient data than an electrophysiologist. Moreover, both the cardiologist and electrophysiologist might have different data collection needs in terms of timing and the types of information required. As a result, clinician data display and collection needs must be coordinated. FIG. 3 is a process flow diagram showing collected patient data coordination 50 in the environment 10 of FIG. 1. The process involves balancing and coordinating individual clinician needs, while ensuring efficient patient data retrieval and processing.
  • [0030]
    In one embodiment, accommodations for clinician-specific display, clinician-specific control, and clinician coordination requirements are provided using the server 18. Generally, patient data is collected from patient data sources 12-16 by data collection devices 17 for eventual upload to the server 18. Once received, the server 18 stores the collected patient data into the database 21 to be made available for clinician use. In a further embodiment, the collected patient data is also analyzed by the server 18 to determine patient wellness, device status, and similar information.
  • [0031]
    Clinician-specific display requirements 51 provide customizable views of the patient data to meet particular clinician display needs. To accommodate these needs, a set of individual displays of the patient data are provided. Each display defines the presentation format and form of physical media used to display the patient data. In one embodiment, clinicians are provided with summary patient information presented on a single viewable Web page and detailed patient information presented on separate, linked-in viewable Web pages. Additionally, the clinician can customize the displays set by creating new or by modifying existing displays based on individual preferences. Other clinician-specific displays are possible.
  • [0032]
    Clinician-specific control requirements 52 specify the types of patient data that are to be collected and the associated periodicities with which those types of patient data will be collected. To accommodate these needs, a set of controls are provided. Each control defines the types of patient data required and the periodicity with which the patient data will be collected from an associated patient data source 12-16. For example, a schedule can be defined to provide automated retrieval of patient data. Alternatively, a frequency can be defined to facilitate on-demand retrieval of patient data, where the frequency indicates a maximum allowable delay for expected patient data receipt. Unlike displays, which generally can be shared by multiple clinicians without interference or conflict, controls typically capture clinical aspects of particular interest to an individual clinician. For instance, a cardiologist following a patient with a history of congestive heart failure might need to collect certain types of physiological measurements taken at precise intervals, yet such patient data may be of lesser interest to other clinicians. In a further embodiment, clinician-specific controls can be defined for a subset of authorized clinicians, which can include a just single clinician or multiple clinicians. Other types of clinician-specific controls are possible.
  • [0033]
    Finally, clinician coordination requirements 53 reconcile competing data display and collection needs. For example, the data collection periodicity of one clinician might exceed the periodicity of another clinician, which would require that the competing data collection needs be reviewed and, if possible or practicable, merged. To accommodate these needs, clinicians are notified when their data display or collection requirements are in conflict with the needs of other clinicians. If the conflicting needs cannot be reconciled, either through automatic or manual means, the clinicians can be notified, such as when patient data is received ahead of schedule due to the scheduling settings of another clinician. In a further embodiment, the data collection requirements for a plurality of clinicians can be merged to minimize communications overhead and to efficiently aggregate those data collection needs occurring within proximal time spans. Other types of clinician coordination are possible.
  • Collected Patient Data Display Settings
  • [0034]
    Clinician data display, collection and coordination needs are addressed through a set of display settings maintained by the server 18. FIG. 4 is a data flow diagram showing collected patient data display settings 60 for use in the environment 10 of FIG. 1. The settings specify displays 61, controls 62, and coordinations 63 that respectively accommodate clinician-specific display, clinician-specific control, and clinician coordination requirements.
  • [0035]
    In one embodiment, a set of individual displays 61 of the patient data are provided for presenting various views of the patient data, formatted, for instance, for viewing as Web pages, in hard copy, and in other forms of physical media. Individual customizable displays 64 are provided as viewable presentations of the patient data and other information to meet specific clinician needs, such as further described below with reference to FIG. 5. Other displays are possible.
  • [0036]
    In a further embodiment, the displays 61 can be customized to map to the specific needs of a particular clinician or interest, for example, by medical subspecialty, practice affiliation, organizational affiliation, referring role, following role, or billing entity. Other types of mappings are possible. In addition, absent express permission, clinicians are not ordinarily allowed to access other clinician displays 64 to safeguard patient privacy and to comply with applicable medical information privacy laws. However, special permissions and exceptions to the displays 61 could also be provided to allow authorized access.
  • [0037]
    In a still further embodiment, access control to the displays 61 could be provided as a hierarchy of permissions. For instance, where the collected patient data is maintained in an electronic medical records (EMR) system or similar secure data repository, access to the displays 61 could initially be limited to only those clinicians formally affiliated with the organization or entity responsible for the EMR system. Additional layers of permissions can be added as other clinicians are authorized access. Other forms of access control are possible.
  • [0038]
    A set of controls 62 are also provided to specify the types of patient data 65 that are to be collected and the associated periodicities 66 with which those types of patient data will be collected. Patient data types 65 include physiological measures, parametric data, and environmental parameters. Other patient data types are possible. Periodicities 66 include schedules and frequencies that respectively specify requested and on-demand data collection. Other periodicities are also possible.
  • [0039]
    Finally, a set of coordinations 63 are provided to coordinate the different needs of the clinicians, for example, by reconciling and merging patient data collection where possible or practicable. Individual coordinated needs are recorded as coordinations 67. Conflicts between competing data collection needs can be resolved by aggregating data collection needs, where feasible, for instance, where separate schedules for the same patient data source can be safely merged into a single schedule. Alternatively, a clinician can filter out patient data that is being collected more frequently than required, where the needs of the competing clinician cannot be reconciled. Other coordinations are possible.
  • Sample User Interface
  • [0040]
    In one embodiment, clinician-customizable displays are provided as viewable pages in a Web-based format, although other types of formats, as well as physical media, are possible. FIG. 5 is a screen diagram 80 showing, by way of example, a patient data display 81, generated by the server 18 of FIG. 1. The patient data display 81 can be viewed via a Web browser executing on the clients 19 a-b, remote clients 20 a-d, or other compatible computing systems. Moreover, although described with reference to a viewable Web page, patient data displays can also include other formats and physical media. The patient data display 81 includes both patient-identifying information and statistics 82, clinician-specific patient data 83, and device-related parametric and event data 84. Other types of information can also be included.
  • [0041]
    In a further embodiment, each clinician is provided with a set of summary patient information that is displayed on a single viewable page, with more detailed patient information that is displayed on separately viewable pages navigable from the summary page. By default, the contents of the summary page and detailed pages are chosen to be specific to the medical needs of generic classes of clinicians, such as cardiologists, but can also be customized to suit the specific needs of a particular clinician or interest, for example, by medical subspecialty, practice affiliation, organizational affiliation, referring role, following role, or billing entity. In addition, special permissions and exceptions could also be provided. Thus, an authorized clinician can choose from a set of default page types or can create a page type based on their personal preferences. For example, an electrophysiologist responsible for the management of an implanted defibrillator would see summary information that would provide information on the device status, such as battery, leads, and so forth, plus information on past arrhythmias and current therapy settings. Detailed pages would allow the electrophysiologist to viewing settings, histograms, trends, and captured electrocardiograms in greater detail. Similarly, a heart failure specialist would have a different interest in the medical data received from the same patient. The summary information would include measurements and trends in weight and blood pressure, medication, and information from the implanted device that could give an insight into their heart failure status, such as activity, heart rate variability, and percent pacing. Finally, a specialist in diabetes would have still other interests in the medical data, as would an internist or sleep specialist. The common data gathered from the implanted and external medical devices and sensors can be organized, wherein the information needed by a clinician to monitor the medical conditions in which they have an interest are available in summary form with detailed information provided in detailed pages. Information in which they are not interest or in which they lack a sufficient background to interpret need not be displayed and can be filtered or screened.
  • Hierarchically Structured Patient Data Displays
  • [0042]
    In one embodiment, patient data displays are defined on an individual clinician basis. In a further embodiment, the displays can be structured in a hierarchy of related displays that enable management of the overall flow of patient data between a group of cooperating clinicians. FIG. 6 is a functional block diagram showing, by way of example, hierarchically structured patient data displays 100 provided in the environment 10 of FIG. 1, in accordance with a further embodiment. Although described with reference to a set of viewable Web pages, hierarchical structurings of heterogeneous formats and physical media are possible, such as a combination of viewable Web pages, hardcopies, and files.
  • [0043]
    The hierarchical structuring includes a set of levels 102, 104, 108. The levels reflect degrees of separation from a topmost, root patient data display 101, which includes a complete set of patient data, consisting of patient data A, B and C, for use by a managing clinician. The complete set of patient data can be logically divided into two subsets respectively including patient data A and C and patient data B. These subsets of patient data can respectively be viewed on child patient data displays 103 and 105. Similarly, the partial subset of patient data A B can be further logically divided into a subset that only includes patient data A. This subset of patient data can be viewed on grandchild patient data display 107. Thus, through the hierarchical structuring, access to and routing of the patient data can be managed for a larger group of clinicians. Other arrangements and organizations cooperative patient data sharing are possible.
  • Server
  • [0044]
    The server acts as the central hub for coordinated patient data collection and display. FIG. 7 is a functional block diagram 120 showing a server 121 for managing coordination of collected patient data in an automated patient management system for use in the environment 10 of FIG. 1. The server 121 includes storage 126 and database 127 and can be configured to coordinate the displaying of patient data between a plurality of clients 19 a-b, remote clients 20 a-d, and other compatible computing systems. Other server functions are possible.
  • [0045]
    At a minimum, the server 121 includes a displayer 122. The displayer 122 provides collected and processed patient data through a set of displays 129 presenting various views of the patient data. The displayer 122 provides a set of controls 130 that specify the types of patient data 131 that are to be collected and the associated periodicities 132 with which those types of patient data will be collected. Finally, the displayer 122 provides a set of coordinations 133 that record reconciliations of different clinician needs for patient data collection and display where possible or practicable.
  • [0046]
    In a further embodiment, the server 121 further includes a collector 123, evaluator 124, and notifier 125. The collector 123 maintains a list of devices and sensors 128 for all patient data sources 12-16, which can be used by a clinician to create schedules 138 and maximum frequencies 139 to manage the collection of patient data by interfaced data collection devices. The collector 123 collects patient data 135 received from the data collection devices, which are stored as patient data sets 134 in the database 127. The collector 123 can execute a follow-up scheme, for example, by sending follow-up requests 137 to patient data sources, if possible, that have not sent expected collected patient data, or by sending a message or other communication to the patient 11, clinician or authorized third party as a compliance notification.
  • [0047]
    The evaluator 124 evaluates the collected patient data 135 against a complete set of alert conditions. One or more triggers are associated with the alert conditions and occurrences of alert condition set off the associated triggers. The same alert conditions can be evaluated by both the server 121 and one or more of the data collection devices.
  • [0048]
    The notifier 125 provides alert notifications. Alert notifications are assigned to notification schemes that are executed upon the detection of an associated trigger. The notification schemes can be organized into one or more levels of alerts. By way of example, alert notifications 164 can include a Web page update, phone or pager call, E-mail, SMS, text or “Instant” message, as well as a message to the patient send through the data collection device 17 and simultaneous direct notification to emergency services and to the clinician. Other alert notifications are possible.
  • [0049]
    While the invention has been particularly shown and described as referenced to the embodiments thereof, those skilled in the art will understand that the foregoing and other changes in form and detail may be made therein without departing from the spirit and scope of the invention.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US3832339 *22 Jun 197127 Aug 1974Ciba Geigy AgPolyazo pigments of the 2-hydroxynaphthalene-3-carboxylic acidarylide series
US4009721 *23 Apr 19761 Mar 1977Pacer S.N.C. Of Cerchiai Vanna & C.Artificial pacemaker
US4142533 *28 Oct 19766 Mar 1979Research CorporationMonitoring system for cardiac pacers
US4197856 *10 Apr 197815 Apr 1980Northrop Robert BUltrasonic respiration/convulsion monitoring apparatus and method for its use
US4531527 *23 Apr 198230 Jul 1985Survival Technology, Inc.Ambulatory monitoring system with real time analysis and telephone transmission
US4686999 *10 Apr 198518 Aug 1987Tri Fund Research CorporationMulti-channel ventilation monitor and method
US4750495 *5 Jun 198714 Jun 1988Medtronic, Inc.Oxygen sensing pacemaker
US4803625 *30 Jun 19867 Feb 1989Buddy Systems, Inc.Personal health monitor
US4809697 *14 Oct 19877 Mar 1989Siemens-Pacesetter, Inc.Interactive programming and diagnostic system for use with implantable pacemaker
US4852570 *9 Feb 19891 Aug 1989Levine Alfred BComparative medical-physical analysis
US4899758 *2 Aug 198813 Feb 1990Regents Of The University Of MinnesotaMethod and apparatus for monitoring and diagnosing hypertension and congestive heart failure
US4987697 *30 Oct 198929 Jan 1991Klein Gerald BHook connector
US4987897 *18 Sep 198929 Jan 1991Medtronic, Inc.Body bus medical device communication system
US5003976 *28 Sep 19882 Apr 1991Eckhard AltCardiac and pulmonary physiological analysis via intracardiac measurements with a single sensor
US5040536 *31 Jan 199020 Aug 1991Medtronic, Inc.Intravascular pressure posture detector
US5113859 *25 Jun 199019 May 1992Medtronic, Inc.Acoustic body bus medical device communication system
US5113869 *21 Aug 199019 May 1992Telectronics Pacing Systems, Inc.Implantable ambulatory electrocardiogram monitor
US5133346 *9 Dec 199128 Jul 1992Arvee Medical, IncorporatedApnea monitor data system
US5199428 *22 Mar 19916 Apr 1993Medtronic, Inc.Implantable electrical nerve stimulator/pacemaker with ischemia for decreasing cardiac workload
US5291895 *29 Dec 19928 Mar 1994Mcintyre Kevin MEvaluation of heart mechanical performance
US5301105 *8 Apr 19915 Apr 1994Desmond D. CummingsAll care health management system
US5331549 *30 Jul 199219 Jul 1994Crawford Jr John MMedical monitor system
US5335889 *12 Feb 19939 Aug 1994Hall Signs, Inc.Bracket mountable to an upright support for holding a sign
US5336245 *20 May 19929 Aug 1994Angeion CorporationStorage interrogation apparatus for cardiac data
US5390238 *15 Jun 199214 Feb 1995Motorola, Inc.Health support system
US5416695 *9 Mar 199316 May 1995Metriplex, Inc.Method and apparatus for alerting patients and medical personnel of emergency medical situations
US5421343 *17 May 19936 Jun 1995Feng; GenquanComputer network EEMPI system
US5437278 *10 Jan 19921 Aug 1995Wilk; Peter J.Medical diagnosis system and method
US5522860 *23 Dec 19944 Jun 1996Ela Medical S.A.Control of an active implantable medical device
US5591215 *17 Nov 19957 Jan 1997Telectronics Pacing Systems, Inc.Apparatus and method for detection of atrial fibrillation by ventricular stability and ventricular pacing
US5596994 *2 May 199428 Jan 1997Bro; William L.Automated and interactive behavioral and medical guidance system
US5603331 *12 Feb 199618 Feb 1997Cardiac Pacemakers, Inc.Data logging system for implantable cardiac device
US5704345 *4 Nov 19946 Jan 1998Resmed LimitedDetection of apnea and obstruction of the airway in the respiratory system
US5704366 *23 May 19946 Jan 1998Enact Health Management SystemsSystem for monitoring and reporting medical measurements
US5711297 *30 Jan 199627 Jan 1998First Opinion CorporationComputerized medical advice system and method including meta function
US5713350 *5 Sep 19963 Feb 1998Fukuda Denshi Kabushiki KaishaPatient information analysis management system and method
US5720770 *6 Oct 199524 Feb 1998Pacesetter, Inc.Cardiac stimulation system with enhanced communication and control capability
US5720771 *2 Aug 199524 Feb 1998Pacesetter, Inc.Method and apparatus for monitoring physiological data from an implantable medical device
US5724580 *20 Mar 19973 Mar 1998Qmed, Inc.System and method of generating prognosis and therapy reports for coronary health management
US5724983 *25 Mar 199610 Mar 1998New England Center Hospitals, Inc.Continuous monitoring using a predictive instrument
US5738102 *31 Jul 199614 Apr 1998Lemelson; Jerome H.Patient monitoring system
US5743267 *27 Oct 199528 Apr 1998Telecom Medical, Inc.System and method to monitor the heart of a patient
US5749907 *18 Feb 199712 May 1998Pacesetter, Inc.System and method for identifying and displaying medical data which violate programmable alarm conditions
US5749908 *18 Dec 199612 May 1998Pacesetter, Inc.Methods and apparatus for annotating data in an implantable device programmer using digitally recorded sound
US5752976 *23 Jun 199519 May 1998Medtronic, Inc.World wide patient location and data telemetry system for implantable medical devices
US5769074 *3 May 199623 Jun 1998Horus Therapeutics, Inc.Computer assisted methods for diagnosing diseases
US5772586 *4 Feb 199730 Jun 1998Nokia Mobile Phones, Ltd.Method for monitoring the health of a patient
US5772599 *9 May 199630 Jun 1998Albert Einstein Healthcare NetworkApparatus and method for monitoring a system
US5772604 *14 Mar 199730 Jun 1998Emory UniversityMethod, system and apparatus for determining prognosis in atrial fibrillation
US5778882 *24 Feb 199514 Jul 1998Brigham And Women's HospitalHealth monitoring system
US5785650 *9 Aug 199628 Jul 1998Akasaka; NoboruMedical system for at-home patients
US5785660 *28 Mar 199628 Jul 1998Pacesetter, Inc.Methods and apparatus for storing intracardiac electrograms
US5855593 *12 Jun 19975 Jan 1999Medtronic, Inc.Prioritized rule based method and apparatus for diagnosis and treatment for arrhythmias
US5860918 *21 Apr 199719 Jan 1999Hewlett-Packard CompanyRepresentation of a review of a patent's physiological parameters
US5876353 *31 Jan 19972 Mar 1999Medtronic, Inc.Impedance monitor for discerning edema through evaluation of respiratory rate
US5879375 *7 Jun 19959 Mar 1999Electric Boat CorporationImplantable device monitoring arrangement and method
US5891178 *13 May 19976 Apr 1999Pacesetter, Inc.Programmer system and associated methods for rapidly evaluating and programming an implanted cardiac device
US5897493 *30 Apr 199727 Apr 1999Health Hero Network, Inc.Monitoring system for remotely querying individuals
US5911132 *14 Oct 19978 Jun 1999Lucent Technologies Inc.Method using central epidemiological database
US6014581 *26 Mar 199811 Jan 2000Ep Technologies, Inc.Interface for performing a diagnostic or therapeutic procedure on heart tissue with an electrode structure
US6024699 *13 Mar 199815 Feb 2000Healthware CorporationSystems, methods and computer program products for monitoring, diagnosing and treating medical conditions of remotely located patients
US6038469 *10 Mar 199814 Mar 2000Ortivus AbMyocardial ischemia and infarction analysis and monitoring method and apparatus
US6047203 *17 Mar 19984 Apr 2000Nims, Inc.Physiologic signs feedback system
US6050940 *17 Jun 199718 Apr 2000Cybernet Systems CorporationGeneral-purpose medical instrumentation
US6063028 *20 Mar 199816 May 2000Luciano; Joanne SylviaAutomated treatment selection method
US6067466 *18 Nov 199823 May 2000New England Medical Center Hospitals, Inc.Diagnostic tool using a predictive instrument
US6073046 *27 Apr 19986 Jun 2000Patel; BharatHeart monitor system
US6080106 *28 Oct 199727 Jun 2000Alere IncorporatedPatient interface system with a scale
US6083248 *24 Nov 19984 Jul 2000Medtronic, Inc.World wide patient location and data telemetry system for implantable medical devices
US6093146 *5 Jun 199825 Jul 2000Matsushita Electric Works, Ltd.Physiological monitoring
US6168563 *17 Mar 19992 Jan 2001Health Hero Network, Inc.Remote health monitoring and maintenance system
US6168653 *15 May 19982 Jan 2001Filtertek, IncPressure transmission apparatus
US6171237 *30 Mar 19989 Jan 2001Boaz AvitallRemote health monitoring system
US6171256 *11 Dec 19989 Jan 2001Physio-Control Manufacturing CorporationMethod and apparatus for detecting a condition associated with acute cardiac ischemia
US6223078 *12 Mar 199924 Apr 2001Cardiac Pacemakers, Inc.Discrimination of supraventricular tachycardia and ventricular tachycardia events
US6225901 *20 Jul 19991 May 2001Cardionet, Inc.Reprogrammable remote sensor monitoring system
US6234964 *13 Mar 199822 May 2001First Opinion CorporationDisease management system and method
US6238349 *25 Jul 200029 May 2001The Research Foundation Of State University Of New YorkMethod and apparatus for noninvasive determination of cardiac performance parameters
US6246992 *14 Sep 199812 Jun 2001Health Hero Network, Inc.Multiple patient monitoring system for proactive health management
US6249705 *21 Oct 199919 Jun 2001Pacesetter, Inc.Distributed network system for use with implantable medical devices
US6250309 *21 Jul 199926 Jun 2001Medtronic IncSystem and method for transferring information relating to an implantable medical device to a remote location
US6263245 *12 Aug 199917 Jul 2001Pacesetter, Inc.System and method for portable implantable device interogation
US6336900 *12 Apr 19998 Jan 2002Agilent Technologies, Inc.Home hub for reporting patient health parameters
US6363282 *29 Oct 199926 Mar 2002Medtronic, Inc.Apparatus and method to automatic remote software updates of medical device systems
US6368284 *16 Nov 19999 Apr 2002Cardiac Intelligence CorporationAutomated collection and analysis patient care system and method for diagnosing and monitoring myocardial ischemia and outcomes thereof
US6398728 *16 Nov 19994 Jun 2002Cardiac Intelligence CorporationAutomated collection and analysis patient care system and method for diagnosing and monitoring respiratory insufficiency and outcomes thereof
US6411840 *16 Nov 199925 Jun 2002Cardiac Intelligence CorporationAutomated collection and analysis patient care system and method for diagnosing and monitoring the outcomes of atrial fibrillation
US6416471 *15 Apr 19999 Jul 2002Nexan LimitedPortable remote patient telemonitoring system
US6512949 *12 Jul 199928 Jan 2003Medtronic, Inc.Implantable medical device for measuring time varying physiologic conditions especially edema and for responding thereto
US6682032 *7 Sep 200227 Jan 2004Scott F. BradleeBanana bunch support and suspension device
US6904320 *14 Feb 20027 Jun 2005Pacesetter, Inc.Sleep apnea therapy device using dynamic overdrive pacing
US20030055679 *9 Apr 199920 Mar 2003Andrew H. SollEnhanced medical treatment system
US20030128126 *4 Jan 200210 Jul 2003Burbank Jeffrey H.Method and apparatus for error warning with multiple alarm levels and types
US20040103001 *26 Nov 200227 May 2004Mazar Scott ThomasSystem and method for automatic diagnosis of patient health
US20040117204 *17 Dec 200217 Jun 2004Cardiac Pacemakers, Inc.Repeater device for communications with an implantable medical device
US20040122488 *23 Dec 200224 Jun 2004Cardiac Pacemakers, Inc.Method and apparatus for enabling data communication between an implantable medical device and a patient management system
US20050055242 *12 Apr 200410 Mar 2005Bryan BelloSystem and method for medical data tracking, analysis and reporting for healthcare system
US20050065567 *31 Aug 200424 Mar 2005Cardiac Pacemakers, Inc.Therapy control based on cardiopulmonary status
US20060080140 *9 Oct 200413 Apr 2006Epic Systems CorporationSystem and method for providing a clinical summary of patient information in various health care settings
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US78016125 Jun 200621 Sep 2010Cardiac Pacemakers, Inc.System and method for managing locally-initiated medical device interrogation
US798375918 Dec 200219 Jul 2011Cardiac Pacemakers, Inc.Advanced patient management for reporting multiple health-related parameters
US8010383 *22 Jan 200930 Aug 2011International Business Machines CorporationFiltering medical information
US804321318 Dec 200225 Oct 2011Cardiac Pacemakers, Inc.Advanced patient management for triaging health-related data using color codes
US80541782 Jun 20098 Nov 2011Cardiac Pacemakers, Inc.System and method for correlating biometric trends with a related temporal event
US836290330 Apr 200929 Jan 2013Cardiac Pacemakers, Inc.System and method for providing enhanced weight alert notification during automated patient management
US839198918 Dec 20025 Mar 2013Cardiac Pacemakers, Inc.Advanced patient management for defining, identifying and using predetermined health-related events
US854321518 Feb 201324 Sep 2013Cardiac Pacemakers, Inc.Advanced patient management for defining, identifying and using predetermined health-related events
US870622615 Sep 201022 Apr 2014Cardiac Pacemakers, Inc.System and method for managing locally-initiated medical device interrogation
US875126115 Nov 201110 Jun 2014Robert Bosch GmbhMethod and system for selection of patients to receive a medical device
US937556618 Jul 201128 Jun 2016Cardiac Pacemakers, Inc.Device for reporting heart failure status
US948084818 Jul 20111 Nov 2016Cardiac Pacemakers, Inc.Advanced patient management with environmental data
US958216427 Aug 201328 Feb 2017Gambro Lundia AbDialysis apparatus with versatile user interface and method and computer program therefor
US97730605 Sep 200626 Sep 2017Cardiac Pacemaker, Inc.System and method for providing automatic setup of a remote patient care environment
US20040122295 *18 Dec 200224 Jun 2004John HatlestadAdvanced patient management for triaging health-related data using color codes
US20040122484 *18 Dec 200224 Jun 2004John HatlestadAdvanced patient management for defining, identifying and using predetermined health-related events
US20040122486 *18 Dec 200224 Jun 2004Stahmann Jeffrey E.Advanced patient management for acquiring, trending and displaying health-related parameters
US20070168222 *19 Jan 200619 Jul 2007Hoyme Kenneth PSystem and method for providing hierarchical medical device control for automated patient management
US20070180047 *12 Dec 20052 Aug 2007Yanting DongSystem and method for providing authentication of remotely collected external sensor measures
US20070282634 *5 Jun 20066 Dec 2007Johnson David CSystem and method for managing locally-initiated medical device interrogation
US20070299317 *13 Jun 200627 Dec 2007Hoyme Kenneth PSystem and method for programming customized data collection for an autonomous medical device
US20080059239 *5 Sep 20066 Mar 2008Gerst Kimberly SSystem and method for providing automatic setup of a remote patient care environment
US20090131917 *10 Apr 200821 May 2009Hollister IncorporatedVapor Hydrated Catheter Assembly and Method of Making Same
US20090273468 *2 Jun 20095 Nov 2009Scott Thomas MazarSystem and method for correlating biometric trends with a related temporal event
US20090278696 *30 Apr 200912 Nov 2009Cardiac Pacemakers, IncSystem and method for providing enhanced weight alert notification during automated patient management
US20100185460 *22 Jan 200922 Jul 2010Sima NadlerFiltering Medical Information
US20100222649 *2 Mar 20092 Sep 2010American Well SystemsRemote medical servicing
US20100223070 *15 Jan 20072 Sep 2010Koninklijke Philips Electronics N.V.Apparatus and method for mornitoring healthcare data
US20110004277 *15 Sep 20106 Jan 2011Cardiac Pacemakers, Inc.System and Method for Managing Locally-Initiated Medical Device Interrogation
US20140122106 *25 Oct 20131 May 2014Analyte Health, Inc.System and Method for Coordinating Administration of a Medical Test to a User
US20140122107 *25 Oct 20131 May 2014Analyte Health, Inc.System and Method for Reporting of Medical Advice
US20140122108 *25 Oct 20131 May 2014Analyte Health, Inc.System and Method for Coordinating Payment for Healthcare Services
EP2761579A4 *28 Sep 201210 Jun 2015Cognosante Holdings LlcMethods and systems for intelligent routing of health information
WO2012085687A3 *20 Dec 201116 Aug 2012France TelecomMedical record retrieval system based on sensor information and a method of operation thereof
Classifications
U.S. Classification705/3
International ClassificationG06Q10/00, G06Q50/00
Cooperative ClassificationG06Q10/06, G06Q50/24, G06Q50/22
European ClassificationG06Q50/22, G06Q10/06, G06Q50/24
Legal Events
DateCodeEventDescription
24 Jun 2005ASAssignment
Owner name: CARDIAC PACEMAKERS, INC.,MINNESOTA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOYME, KENNETH P.;SIMMS, HOWARD D.;JOHNSON, DAVID C.;ANDOTHERS;SIGNING DATES FROM 20050616 TO 20050617;REEL/FRAME:016714/0292