US8628470B1 - Disease management system and method including medication therapy self-management - Google Patents

Disease management system and method including medication therapy self-management Download PDF

Info

Publication number
US8628470B1
US8628470B1 US13/236,996 US201113236996A US8628470B1 US 8628470 B1 US8628470 B1 US 8628470B1 US 201113236996 A US201113236996 A US 201113236996A US 8628470 B1 US8628470 B1 US 8628470B1
Authority
US
United States
Prior art keywords
patient
therapy
passes control
health
pain
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
US13/236,996
Inventor
Edwin C. Iliff
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Healthways SC LLC
Original Assignee
Clinical Decision Support LLC
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Family has litigation
First worldwide family litigation filed litigation Critical https://patents.darts-ip.com/?family=21911437&utm_source=google_patent&utm_medium=platform_link&utm_campaign=public_patent_search&patent=US8628470(B1) "Global patent litigation dataset” by Darts-ip is licensed under a Creative Commons Attribution 4.0 International License.
Application filed by Clinical Decision Support LLC filed Critical Clinical Decision Support LLC
Priority to US13/236,996 priority Critical patent/US8628470B1/en
Assigned to SUNTRUST BANK, AS ADMINISTRATIVE AGENT reassignment SUNTRUST BANK, AS ADMINISTRATIVE AGENT SECURITY AGREEMENT Assignors: CLINICAL DECISION SUPPORT, LLC, HEALTHHONORS, LLC, Healthways, Inc.
Application granted granted Critical
Publication of US8628470B1 publication Critical patent/US8628470B1/en
Assigned to HEALTHWAYS SC, LLC reassignment HEALTHWAYS SC, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: AMERICAN HEALTHWAYS SERVICES, LLC, ASCENTIA HEALTH CARE SOLUTIONS, L.L.C., CLINICAL DECISION SUPPORT, LLC, HEALTHWAYS HAWAII, LLC, HEALTHWAYS HEALTH SUPPORT, LLC, HEALTHWAYS HEALTHTRENDS, LLC, HEALTHWAYS INTERNATIONAL, INC., HEALTHWAYS INTERNATIONAL, S.A.R.L, HEALTHWAYS ORNISH, LLC, HEALTHWAYS QUITNET, LLC, HEALTHWAYS WHOLEHEALTH NETWORKS, INC., Healthways, Inc., POPULATION HEALTH SUPPORT, LLC
Assigned to CLINICAL DECISION SUPPORT, LLC, Healthways, Inc., HEALTHHONORS, LLC reassignment CLINICAL DECISION SUPPORT, LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: SUNTRUST BANK, AS ADMINISTRATIVE AGENT
Assigned to FIRST OPINION CORPORATION reassignment FIRST OPINION CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ILIFF, EDWIN C.
Assigned to CLINICAL DECISION SUPPORT, LLC reassignment CLINICAL DECISION SUPPORT, LLC ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: FIRST OPINION CORPORATION
Assigned to WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT reassignment WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINISTRATIVE AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BACTES IMAGING SOLUTIONS, INC., BACTES IMAGING SOLUTIONS, LLC, HEALTHWAYS SC, LLC, LUCID GLOBAL, INC., QH ACQUISITION SUB, LLC, SHARECARE, INC.
Assigned to ABC FUNDING, LLC, AS AGENT reassignment ABC FUNDING, LLC, AS AGENT SECURITY INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: BACTES IMAGING SOLUTIONS, INC., BACTES IMAGING SOLUTIONS, LLC, HEALTHWAYS SC, LLC, LUCID GLOBAL, INC., QH ACQUISITION SUB, LLC, SHARECARE, INC.
Anticipated expiration legal-status Critical
Assigned to HEALTHWAYS SC, LLC, LUCID GLOBAL, INC., SHARECARE, INC. reassignment HEALTHWAYS SC, LLC RELEASE BY SECURED PARTY (SEE DOCUMENT FOR DETAILS). Assignors: ABC FUNDING, LLC, AS AGENT
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/60ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices
    • G16H40/67ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the operation of medical equipment or devices for remote operation
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H20/00ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
    • G16H20/10ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance relating to drugs or medications, e.g. for ensuring correct administration to patients
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H50/00ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/20ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for computer-aided diagnosis, e.g. based on medical expert systems
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H50/00ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
    • G16H50/30ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for calculating health indices; for individual health risk assessment
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H80/00ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/20ICT specially adapted for the handling or processing of patient-related medical or healthcare data for electronic clinical trials or questionnaires
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H15/00ICT specially adapted for medical reports, e.g. generation or transmission thereof
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H70/00ICT specially adapted for the handling or processing of medical references
    • G16H70/20ICT specially adapted for the handling or processing of medical references relating to practices or guidelines
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H70/00ICT specially adapted for the handling or processing of medical references
    • G16H70/60ICT specially adapted for the handling or processing of medical references relating to pathologies
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02ATECHNOLOGIES FOR ADAPTATION TO CLIMATE CHANGE
    • Y02A90/00Technologies having an indirect contribution to adaptation to climate change
    • Y02A90/10Information and communication technologies [ICT] supporting adaptation to climate change, e.g. for weather forecasting or climate simulation
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S128/00Surgery
    • Y10S128/92Computer assisted medical diagnostics
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10STECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S128/00Surgery
    • Y10S128/92Computer assisted medical diagnostics
    • Y10S128/925Neural network

Definitions

  • the present invention generally relates to medical knowledge systems, and more specifically, to systems for computerized long-term management of patient diseases.
  • Diagnosis means finding the cause of the patient's problem; treating is the application of the best therapy available. However, not all diseases can be completely cured by a treatment regime.
  • Diseases such as asthma and diabetes may require a regular schedule of treatment, termed therapy, for the duration of a patient's life.
  • therapy for the duration of a patient's life.
  • the disease is managed rather than cured.
  • Disease management may be defined as managing a patient with a known diagnosis with the intention of providing patient education and monitoring to prevent symptom flare ups and acute episodes of the disease in order to eliminate costly medical intervention and promote patient well being.
  • the therapy portion of disease management must be custom-tailored to the response of a particular patient since diseased patients may respond differently to the same treatment, e.g., a prescribed dosage and pharmaceuticals.
  • Disease management can involve coordinating care for patients across the entire health care continuum from birth to death. Disease management has a program available for every part of everyone's life, including prevention, diagnosis, treatment and rehabilitation. The process involves managing not only the patient with a particular disease, but also the healthy patient. Too often, providers focuses on providing intensive and costly services to patients with acute episodes of disease. Disease management advocates seek a greater focus on preventive, comprehensive care to improve the health of the entire population. In a sense, disease management attempts to take the practice of medicine out of the hands of physicians and puts it into the hands of patients.
  • an automated system for encoding a subjective experience of a patient's pain comprising a software function configured to encode a subjective description of a patient's pain to represent a degree or description of pain; and a pain code array, wherein the pain code array comprises encoded numeric values representing a plurality of different aspects of subjective patient descriptions of pain.
  • a computerized method for encoding a description of a patient's pain into a pain code array comprising storing a set of aspect words in a data storage, wherein the aspect words correspond to an aspect of pain; receiving one or more aspect words from a patient that describe a pain of the patient; encoding the received aspect words into subcodes; and combining the subcodes into a pain code array.
  • an automated method for decoding a description of pain from a pain code array comprising retrieving a pain code array containing one or more subcodes from a storage location of the pain code array; and decoding the subcodes of the pain code array into subjective aspect words.
  • a computer usable medium having computer readable program code embodied therein for representing a description of a pain in a digitized form for adjusting therapy, the computer readable code comprising instructions for storing a listing of aspect words describing a pain experienced by a patient; receiving a selection of an aspect word from the listing of aspect words; and converting the received aspect word into an integer subcode that represents the received aspect word.
  • a computerized medical diagnosis method comprising encoding a patient's subjective perception of pain into a pain code; and indexing a database of diseases with the pain code thereby diagnosing a disease.
  • FIG. 1 is a block diagram of an automated medical diagnosis, treatment, disease management and information system of the present invention.
  • FIG. 2 a is a diagram of a configuration of components of the system shown in FIG. 1 .
  • FIG. 2 b is a diagram of a configuration of components of the server computer shown in FIGS. 1 and 2 a.
  • FIG. 3 is a block diagram of a portion of the processes and database files utilized by the system of FIG. 1 .
  • FIGS. 4 a , 4 b , 4 c and 4 d are a flowchart of the top-level process performed by the system of FIG. 1 .
  • FIG. 5 is a flowchart of the Disease Management Module process shown in FIG. 4 d and performed by the system of FIG. 1 .
  • FIG. 6 is a flowchart of the Open Session process shown in FIG. 5 .
  • FIG. 7 is a flowchart of the Health Assessment process shown in FIG. 5 .
  • FIG. 8 is a flowchart of the Significant Symptom Filter process shown in FIG. 7 .
  • FIG. 9 is a flowchart of the Severity Assessment function shown in FIG. 8 .
  • FIG. 10 is a flowchart of the Initial Health Assessment process shown in FIG. 7 .
  • FIG. 11 is a flowchart of the Current Health Assessment process shown in FIG. 7 .
  • FIG. 12 is a flowchart of the Correlation Assessment function shown in FIG. 11 .
  • FIG. 13 is a flowchart of the Critical Curve Assessment process shown in FIG.
  • FIG. 14 is a flowchart of the Therapy Optimization process shown in FIG. 5 .
  • FIG. 15 is a flowchart of the Therapy Adjustment Based on Subjective Health Data process shown in FIG. 14 .
  • FIG. 16 is a flowchart of the Therapy Adjustment Based on Objective Health Data process shown in FIG. 14 .
  • FIG. 17 is a flowchart of the Patient Consent Level function shown in FIGS. 15 and 16 .
  • FIG. 18 is a flowchart of the Close Session process shown in FIG. 5 .
  • FIGS. 19 a and 19 b are flowcharts of the Question Versions feature utilized by the Disease Management Module process shown in FIGS. 1 and 5 .
  • FIG. 20 is a flowchart of the Preview Mode feature utilized by the Disease Management Module process shown in FIGS. 1 and 5 .
  • FIG. 21 is a flowchart of the No-Response feature utilized by the Disease Management Module process shown in FIGS. 1 and 5 .
  • FIG. 22 a is a flowchart of a function utilized by the Disease Management Module process shown in FIGS. 4 d and 5 and/or the Diagnostic process shown in FIG. 4 d in generating a PQRST (pain code) array entry for a patient.
  • PQRST pain code
  • FIG. 22 b is a flowchart of a function utilized by the Diagnostic process shown in FIG. 4 d in retrieving a diagnosis using the PQRST (pain code) array entry stored for a patient in FIG. 22 a.
  • PQRST pain code
  • FIG. 23 is a graph of an exemplary critical curve plotting health measurements over time for a particular disease.
  • DMO Disease Management Order
  • TPL Therapeutic Alteration Permission Level
  • a disease management module (DMM) 80 and several other high-level service modules 82 perform automated medical services for the users of the medical management system 100 .
  • the service modules 82 may include Diagnosis, Treatment Table, Automated Demand Management, Audio/Visual/Image Library, and Author Access.
  • the DMM 80 handles tasks associated with Disease Management (DM); its major goals are to promote patient well-being, to educate patients, and to reduce costly medical intervention.
  • the user may be a patient 114 or an assistant for a patient. Throughout this document, the words user and patient are used interchangeably. However, it will be understood that the user may be acting as a proxy for the patient. If this is the case, the user is registered as an assistant for the patient. Appropriate registration and login processes, described herein below, are utilized by the system 100 for either the patient or the assistant.
  • the modules 80 and 82 are supported by an Operating System and support software 88 , by a number of databases 84 , and by a computing environment 90 of an embedding computer hardware platform 110 .
  • the entire computer hardware-software-communications complex is operated and maintained by a support staff All application tasks of the DMM 80 are fully automated.
  • External contact of the DMM with patients, physicians, clinics, pharmacies, laboratories, and so on are handled by automated communications systems using appropriate media and methods of the computing environment 90 , such as interactive voice response (IVR), direct modem-to-modem access, or access via the Internet 102 .
  • the patient 114 utilizes a computer 116 and monitor 118 , a telephone 124 , or other components, some of which are described in conjunction with FIG. 2 a below, to communicate with the system computer platform 110 .
  • the system 100 includes a network “cloud” 102 , which may represent a local area network (LAN), a wide area network (WAN), the Internet, or another connection service.
  • LAN local area network
  • WAN wide area network
  • Internet the Internet
  • the system programs and databases may reside on a group of servers 108 that are preferably interconnected by a LAN 106 and a gateway 104 to the network 102 .
  • the system programs and databases may reside on a single server 110 that utilizes network interface hardware and software 112 .
  • the system servers 108 / 110 store the modules 80 and 82 ( FIG. 1 ).
  • the network 102 may connect to a user computer 116 , for example, by use of a modem or by use of a network interface card.
  • the user 114 at the computer 116 may utilize a browser 120 to remotely access the system programs using a keyboard and/or pointing device and a visual display, such as the monitor 118 .
  • the browser 120 is not utilized when the system programs are executed in a local mode on the computer 116 .
  • a video camera 122 may be optionally connected to the computer 116 to provide visual input, such as visual symptoms or signs. Furthermore, clinical sounds could be picked up by the video camera or separate microphone (not shown).
  • Various other devices may be used to communicate with the system servers 108 / 110 . If the servers are equipped with voice recognition or DTMF hardware, the user can communicate with the system program by use of the telephone 124 .
  • a telephonic embodiment is described in Applicant's application entitled “Computerized Medical Diagnostic and Treatment Advice System,” U.S. application Ser. No. 08/176,041, filed Dec. 29, 1993, which has issued as U.S. Pat. No. 5,660,176, and is hereby incorporated by reference.
  • connection devices for communicating with the system servers 108 / 110 include a portable personal computer 126 with a modem or wireless connection interface, a cable interface device 128 connected to a visual display 130 , or a satellite dish 132 connected to a satellite receiver 134 and a television 136 .
  • a portable personal computer 126 with a modem or wireless connection interface a cable interface device 128 connected to a visual display 130
  • a satellite dish 132 connected to a satellite receiver 134 and a television 136 .
  • Other ways of allowing communication between the user 114 and the system servers 108 / 110 are envisioned.
  • a diagram of one embodiment of a server computer 110 shows several possible interconnections to the network.
  • a Script Engine is used, which reads a medical diagnostic script file and uses its codes to perform interview actions, such as outputting a question to a patient and inputting an answer.
  • the scripts may also collect the answers from the patient, evaluate the answers, issue a diagnosis, and update the patient's medical record.
  • the script engine may also reside in the user computer 116 ( FIG. 2 a ).
  • the script engine may be stored on the hard drive or a CD-ROM, and is loaded into the main memory or a cache for execution.
  • the components of a presently preferred server computer 110 of the computerized medical system 100 of the present invention are shown in FIG. 2 b .
  • the server computer 110 includes a plurality of components within an enclosure.
  • a telephone line 156 interfaces the public telephone network 158 to the computer 110 via a modem 160 .
  • the telephone network 158 may connect to the network 102 , which has connections with the system server(s) 108 / 110 .
  • the computer 110 may connect to the network 102 by use of a network interface card 164 .
  • the hardware and system software are assembled with two basic concepts in mind: portability to other operating systems and the use of industry standard components. In this way, the system can be more flexible and will allow free market competition to continually improve the product, while, at the same time, decreasing costs. While specific hardware and software may be referenced, it will be understood that a panoply of different components could be used in the present system.
  • the computer 110 preferably is a personal computer with an Intel Pentium microprocessor 170 .
  • Other computers such as an Apple Macintosh, an Amiga, a Digital Equipment Corporation VAX, or an IBM mainframe, could also be utilized.
  • the modem 160 or the network interface card 164 connects to an industry standard architecture (ISA) or a peripheral component interconnect (PCI) bus 162 .
  • ISA industry standard architecture
  • PCI peripheral component interconnect
  • the bus 162 interconnects the microprocessor 170 with a plurality of peripherals through controller circuits (chips or boards).
  • the computer bus 162 has a plurality of peripherals connected to it through adapters or controllers.
  • a video adapter board 172 preferably at SVGA or better resolution, interconnects to a video monitor 118 .
  • a serial communication circuit 176 interfaces with a pointing device, such as a mouse 178 .
  • a parallel communication circuit may be used in place of circuit 176 in another embodiment.
  • a keyboard controller circuit 180 interfaces with a keyboard 182 .
  • a 500 Mb or greater hard disk drive 184 and an optional CD-ROM drive 186 are preferably attached to the bus 162 .
  • the hard disk 184 stores database files such as the patient files, DM files, other system files, and binary support files.
  • the CD-ROM drive 186 also stores database files and binary support files.
  • a main memory 190 connects to the microprocessor 170 .
  • the computer 110 may operate under the Windows 95 operating system 192 .
  • the memory 190 executes a diagnostic script engine (not shown) and a disease management module (DMM) process 220 .
  • DMM disease management module
  • Portions of the disease management module process software may be written in Borland Delphi Pascal, version II, and other portions may be written in Microsoft ‘C’, version 7.0.
  • the database is implemented with Microsoft Foxpro or another database program such as a SQL-compatible relational database program.
  • the medical management system 100 utilizes several principal processes and related databases.
  • a set of patient/assistant login processes 200 , 210 and 212 is used by the system 100 to identify a patient who has previously registered into the system in one of three ways: 1) by prompting for a patient identification number (PIN) in process 200 ; 2) identify an assistant who has previously registered into the system by prompting for an assistant identification number (AIN) in process 210 ; or 3) identify a patient, having an assistant, who has previously registered into the system by prompting for the patient identification number in process 212 .
  • One of a set of processes 202 , 214 or 216 is used to register a patient or assistant. If the user is the patient, a patient registration process is used by the system to register new or first-time patients in process 200 .
  • an assistant registration process is used by the system to register new or first-time assistants in process 214 . Then, if the patient is not already registered, an assisted patient registration process is used by the system to register the patient in process 216 .
  • the system provides a choice of processes.
  • the primary process of concern in the current embodiment is the DMM process 220 that manages a disease or condition of the patient.
  • the DMM process 220 may access the laboratory test of choice database 260 or imaging modality of choice database 258 in the course of disease management and a treatment table 250 to obtain current treatment information for a particular disease or diagnosis.
  • Associated with these processes are a patient and assistant enrollment database 240 , a consultation history database 242 , a patient response database 244 , a medical history objects database 246 , a patient medication database 248 , a pending database 252 , and a patient medical history database 254 .
  • These databases include an electronic medical record for each patient that is registered with the medical system 100 .
  • the electronic medical record contains all the information about each patient.
  • a permissions database 256 , a diseases database 262 and other DM specific databases 264 will be described herein below.
  • other choices are added to access other medical information processes.
  • a telephone number used to access the system 100 via the telephone may vary in various embodiments of the system. If the sponsoring agency or hospital wishes to provide access to the medical management system 100 at no cost to the caller, then a toll-free (e.g., 800, 888 or other number) service number can be used. If the sponsoring agency or hospital wishes to recover the costs of running the system 100 from the caller, it may use a pay-per-call or premium charge number (e.g., 900 service). “Current Procedural Terminology” (CPT-4) codes are available to describe and bill third party payers for telephone consultations.
  • CPT-4 Current Procedural Terminology
  • CPT-4 codes are the most widely accepted nomenclature for reporting physician services to insurance companies. If access is provided to the system 100 via the Internet or other network, an appropriate web address (or addresses) is provided to the user.
  • the user 114 desiring medical advice dials the telephone number for the system 100 on the telephone 124 ( FIG. 2 a ).
  • the user may be the patient or may be an “assistant”, e.g., parent, relative, or friend, that is helping the patient.
  • the user may access the system 100 though the user computer 116 , such as through the Internet as previously described.
  • the system 100 answers the call automatically and greets the caller 114 with an introductory greeting message by playing back a speech file stored on the system hard drive by use of a voice processing board, such as a D/41D available from Dialogic.
  • a voice processing board such as a D/41D available from Dialogic.
  • a greeting message is displayed to the user on the visual display 118 .
  • the system 100 communicates with the user 114 either by the telephone or by messages displayed on the visual display. Subsequent steps in the process or function flowcharts will only describe one form of user communication for brevity purposes.
  • the system 100 asks each patient who calls the system a series of “initial screening questions.” These questions are designed to identify patients who are critically ill; they are not designed to identify the patient's problem. The initial screening questions enable the system to filter out patients who require immediate medical attention.
  • any patient found to be critically ill is instructed to dial the emergency response telephone number “911” at state 309 or will be automatically connected to the nearest emergency medical services system in the patient's area.
  • the session is terminated by process 300 at state 310 .
  • the system may provide the patient with a menu of emergency medical procedures at state 311 .
  • the user may need to initiate emergency procedures immediately.
  • the menu of emergency medical procedures provides several choices to the user. If the user presses touch tone key “1” or speaks the word “one” into the telephone mouthpiece, process 300 branches to state 312 wherein well known CPR (cardiopulmonary resuscitation) information is recited. If the user has a speakerphone capability associated with the telephone 124 being used, the user may be able to listen to and perform the instructions given by the system 100 in a hands-free manner away from the telephone.
  • CPR cardiopulmonary resuscitation
  • process 300 branches to state 313 wherein well known Heimlich Hug information for choking is recited.
  • state 313 the session ends at state 314 .
  • process 300 moves to a decision state 315 to determine if the user is the actual patient. If so, process 300 proceeds to a decision state 316 to determine if the patient has previously registered or ever consulted with the system 100 , i.e., is not a new or first-time caller. If so, the system 100 verifies the patient's identification and retrieves their medical record at the patient login process 200 . At the completion of process 200 , process 300 proceeds through off-page connector C 317 to state 344 ( FIG. 4 d ).
  • process 300 proceeds through off-page connector C 317 to state 344 on FIG. 4 d.
  • process 300 proceeds through off-page connector A 318 to a decision state 320 on FIG. 4 b .
  • an “assistant” may interact with the system on behalf of the patient.
  • the assistant registration record is identical to the patient registration record in structure, but three fields have special significance for an assistant: ASST_PERM, ASST_EXP, and RELATIONS.
  • the ASST_PERM field is a Boolean flag that can only be set true off-line by the system administrator who has verified, through separate means, that a relationship exists between a patient and an assistant. The relationships are one-to-many, i.e., a patient may have one or more assistants, and an assistant may be related to more than one patient.
  • the ASST_PERM flag may also be constrained by the ASST_EXP field, which contains a timestamp for the expiration of the ASST_PERM attribute. If the ASST_PERM flag is true, then the RELATIONS pointers will point to one or more patient records for whom this assistant is a “permanent assistant;” otherwise the RELATIONS field will be empty.
  • the medical information gathered during an assisted consultation is written to the patient's medical record if the following three conditions are met:
  • any new medical information gathered on this patient will be saved to the Pending file 252 ( FIG. 3 ) for off-line verification by the system administrator.
  • the system 100 establishes at state 315 whether the user is the patient, or an assistant. If the user is not the patient, then the system asserts that the user is an assistant and, at decision state 320 , determines if the assistant is registered. If the assistant is not already registered with the system, the system enrolls the new assistant at the assistant registration process 214 . If the assistant is already registered with the system 100 , process 300 performs the assistant login process 210 . At the completion of either process 214 or process 210 , process 300 advances to a decision state 321 .
  • process 300 performs the assisted patient login process 212 .
  • process 300 proceeds through off-page connector B 327 to a decision state 334 on FIG. 4 c.
  • process 300 determines if the patient's date of birth is in the patient's medical record. If so, process 300 proceeds through off-page connector C 317 to state 344 on FIG. 4 d . If not, the system 100 attempts to get the patient's date of birth. Moving to state 335 , the system 100 asks the assistant if the patient's date of birth is known. If so, process 300 advances to state 336 to request the patient's date of birth. At state 337 , the system 100 recites the patient's date of birth obtained at state 336 . At a decision state 338 , the assistant determines if the date of birth is correct as recited by the system 100 .
  • process 300 loops back to state 336 to request the patient's date of birth again. If the patient's date of birth is correct, as determined at state 338 , process 300 flags the date of birth for saving in the patient's medical record at state 339 , and proceeds to state 344 on FIG. 4 d.
  • process 300 proceeds to state 340 wherein the system requests the assistant to provide an approximate age of the patient.
  • the age is an important parameter used by the DMM process 220 , the diagnostic module and the treatment table 250 .
  • the system 100 recites the patient's approximate age obtained at state 340 .
  • the assistant determines if the age is correct as recited by the system 100 . If not, process 300 loops back to state 340 to request the patient's approximate age again.
  • the system 100 advises the assistant at state 343 to get the patient's actual date of birth before the next consultation, and proceeds to state 344 on FIG. 4 d .
  • the system 100 uses the approximate age in the session during the diagnostic module and the treatment table 250 .
  • the system 100 presents the user with a system selection menu.
  • the caller is asked to select from among six choices: diagnostic system, treatment table, disease management, audio/visual/image library, automated demand management, or end session as described below:
  • the system 100 gives the patient the option of selecting another complaint.
  • the system gives the patient the option of selecting another treatment.
  • the system 100 gives the patient the option of selecting another audio clip, video, or image.
  • the system 100 gives the patient the option of receiving advice for another problem.
  • the system 100 loops back to state 344 and again provides the system selection menu for the user. If the user chooses the End Session selection at state 344 , the system 100 moves to a decision state 345 .
  • the system 100 determines if process 280 , process 250 , process 220 , or process 284 did not occur in Information mode, i.e., did occur in either Real mode or Pending Mode, and examines a symbol table associated for the current patient to determine if any of the configured memory variables are past medical history conditions that need to be saved to the patient's medical history file. If both conditions are true at state 345 , the system 100 advances to a decision state 346 to determine if the consultation is being performed in Real mode. If not, the consultation is being performed in Pending mode, and the system 100 then writes any new patient information obtained during the consultation to the Pending file 252 at state 347 .
  • decision state 346 proves to be true, i.e., Real mode
  • the system 100 asks the patient at state 348 to grant permission to save the datum to the patient's medical history file and to confirm that the datum is correct.
  • the system 100 may have learned that the patient has been diagnosed as being HIV positive. The system 100 will ask, “May I record the information about your HIV diagnosis in your medical record?” If the patient responds “yes”, then the system 100 will ask, “Please verify that your diagnosis for HIV was positive, is this correct?” If the patient responds “yes”, then the system 100 writes the diagnosis, and a score indicative of system accuracy to the patient's medical history file. After confirmation, each data item is stored in the patient's file in the patient medical history database 254 ( FIG. 3 ).
  • the process 300 moves to a decision state 349 .
  • the system 100 Before the system 100 ends the consultation with the patient, it presents a summary of all the advice it has given. In a telephonic session, the patient is asked to write down and repeat back the key points. The system 100 then gives the patient the option of receiving a summary of the consultation session and specific recommendations provided by the system via facsimile, electronic mail (E-mail) or a mail service, such as first-class mail. If a fax or E-mail is desired, process 300 moves to a decision state 350 to determine if information to send the summary and recommendations is available in the system.
  • E-mail electronic mail
  • a mail service such as first-class mail.
  • process 300 asks the patient for the information, e.g., a fax number, E-mail address or mail address, at state 352 .
  • the patient also has the option to send a summary of the consultation to his or her health care provider or specialist.
  • process 300 adds the transcript of the current telephone session to a fax queue or an E-mail queue, as desired, for subsequent transmission.
  • the session is terminated at state 353 .
  • the present invention includes a computer program called a Disease Management Module (DMM).
  • the disease management module is one of several high-level service modules that perform automated medical services for the users of the medical management system 100 .
  • disease management means the continuing medical care of a patient who has been diagnosed with a specified health problem called a disease.
  • the DDM may continue care throughout a patient's lifetime.
  • the DMM performs disease management in a fully automated manner, using periodic interactive dialogs with the patient to obtain health state measurements from the patient, to evaluate and assess the progress of the patient's disease, to review and adjust therapy to optimal levels, and to give the patient medical advice for administering treatment and handling symptom flare-ups and acute episodes of the disease.
  • the goal of the disease management module is to promote patient health in an automated manner that reduces costly medical intervention.
  • DMM software Various features of the DMM software are specifically designed to accumulate and use patient-specific information, so that disease management can be tailored more to each individual case.
  • the module manages a given patient over time, it builds a profile of the case, in the form of the frequency and reasons for the patient's contacts with the DMM, the patient's subjective understanding of the disease, the patient's objective response to various medical treatments, and the patient's preferences in treatment. The module then uses that knowledge to adjust its internal procedures, so that they adapt more to the specific patient.
  • the DMM When a patient is first admitted to DM, the DMM runs a registration procedure that verifies the patient's medical history, initializes the initial therapy for the patient's disease, and sets up a schedule for patient contacts. For every registered DM patient, the DMM conducts periodic automated sessions with the patient. During each session, the DMM obtains and updates the patient's medical history with the latest health measurements, analyzes and assesses patient health as needed, adjusts therapy as needed, and gives the patient appropriate medical advice. At the end of each session, the DMM schedules the next session. Ultimately, the DMM discharges patients by moving them from the disease management state to another state such as to the medical care of a human physician, to the care of the diagnostic module of the medical system, or to a normal health state with the appropriate follow-up health checkups.
  • the DMM module is now summarized here in terms of its overall features, so as to put the features into the overall context. Each feature will be further described herein below.
  • the DMM In all of its contacts with patients, the DMM must insure that it complies with a large number of permissions, consents, and authorizations granted by various agents and agencies.
  • the DMM uses the Permissions database to manage these control data.
  • Scripts are special computer programs capable of outputting text and questions to a patient, waiting for a response from the patient, recording the response, and taking further action based on the response.
  • the development and use of scripts has been described in U.S. application Ser. No. 08/893,402, filed Jul. 11, 1997, issued as U.S. Pat. No. 5,935,060, entitled “Computerized Medical Diagnostic and Treatment Advice System including List Based Processing”, and in U.S. application Ser. No. 08/893,912, filed Jul. 11, 1997, issued as U.S. Pat. No. 6,022,315, entitled “Computerized Medical Diagnostic and Treatment Advice System including Network Access”, both of which are hereby incorporated by reference.
  • a normal online dialog with a patient takes the general form of a sequence of questions asked by a script, and answers provided by the patient. As the script runs, it considers the patient's current status, selects a question, and presents the question to the patient. The patient responds, the script analyzes the response, selects another question, and so on until the session is normally terminated.
  • a script Preview Mode for the DMM allows the patient to answer a question in a “look ahead” mode, to see what the consequences of a given response would be, without formally selecting the response.
  • Abnormal script terminations can be handled by the DMM in an intelligent, proactive manner using a No-Response function. If a patient suddenly fails to respond in the middle of a dialog, this function can use all that is known about the patient, the patient's location, and the disease being managed to respond proactively, including—if necessary—the ability to contact the patient's nearest emergency assistance facility or to call 911 for the patient.
  • the DMM performs all of its contact with patients in the form of Disease Management sessions, which are regularly scheduled, online dialogs with the patient.
  • a DM session can be initiated by either the patient calling the medical system (inbound), or by the system calling the patient (outbound). Every DM session consists of four major tasks performed in the following sequence: Open Session, Health Assessment, Therapy Optimization, and Close Session.
  • the Open Session task initializes data and registers patients.
  • the task uses the patient's health history and the disease being managed to establish the assessment health parameters that are to be measured and tracked, including relevant thresholds, limits, ranges, and critical values. It also gives patients instructions on how to observe symptoms, perform health measurements, assess their health, and prospectively trend their disease.
  • the Health Assessment task obtains health measurements from the patient for the interval since the last session, encodes symptom descriptions using a PQRST Array, and calculates various relevant health counts, patterns, and trends. It analyzes health state using a Correlation Assessment function and a Critical Curve Assessment function.
  • the Correlation Assessment function uses a Subjective-Objective Correlation Factor (SOCF), a statistical measure of how well a given patient can assess his/her own disease state and progress, to assess the patient's health based on subjective data.
  • SOCF Subjective-Objective Correlation Factor
  • the PQRST Array is an encoding scheme used to convert subjective descriptions of pain symptoms into a DMM-wide digitized pain code.
  • the Critical Curve is a time-plot of specified health parameters that the DMM can compare to standard critical curves to detect or predict rapid deterioration of patient health.
  • the Health Assessment task decides what action to take for the patient, such as referring the patient out of the system, to seek human medical attention; or referring the patient to the diagnostic module process for diagnosis of a new symptom; or proceeding to the next task to determine the next therapy step for the patient.
  • the third task of the DM session is Therapy Optimization, whose express goal is to adjust therapy step by step in a manner that balances the risks and benefits, maximizes efficacy and minimizes adverse side effects, and converges to an optimum therapy for this patient over the long term.
  • the task selects one of several possible therapies from a treatment table, adjusts dosages in small steps as controlled by a Patient Consent Level function, presents the risks and benefits to the patient, and lets the patient accept or reject the recommendation. If the patient rejects, the task computes the next best therapy, and the next, until it reaches a limit that is stored in the Permissions database. In all of its work, the task consults a Therapeutic Alteration Permission Level (TAPL) to determine how much authority it has to modify therapy automatically. If the task has too little authority to recommend a therapy, or if the patient rejects all therapy suggestions, the task refers the patient to a human physician.
  • TAPL Therapeutic Alteration Permission Level
  • the final task of the DM session stores all of the assessment measurements, parameters, and decision factors in the patient's medical history database.
  • the task also processes the therapy changes that the patient accepted, issues relevant instructions to the patient, and finally reschedules the patient for the next session.
  • the task initiates processes to output various session logs and reports requested during the session, and finally, the DMM saves the relevant data and terminates the current DM session.
  • the DMM is now done with this patient until the next session repeats the process.
  • Process 220 comprises the executable portion of the Disease Management Module (DMM), which conducts an on-line, interactive dialog with a patient for the purpose of managing a known disease of the patient.
  • DMM Disease Management Module
  • Process 220 consists of four processes 404 , 406 , 408 , and 410 .
  • a DM session starts when control is passed to program 220 at the start node 402 .
  • process 220 invokes process 404 , which performs initialization, file opening, and registration functions as described in conjunction with FIG. 6 below.
  • process 220 When process 404 returns control to process 220 , process 220 next invokes process 406 , which inputs health measurements from the patient, analyzes them, and assesses the patient's current health state. When process 406 returns control to process 220 , process 220 next invokes process 408 , which computes an optimum next therapy step that is accepted by the patient. When process 408 returns control to process 220 , process 220 next invokes process 410 , which outputs various reports, saves session data, and closes working files. When process 410 returns control to process 220 , process 220 passes control to step 412 . Step 412 returns control to the process that invoked process 220 at node 402 .
  • Process 404 establishes the data needed to conduct a DM session. It registers patients that are new to the DMM and loads existing data for patients that have previously conducted DM sessions. Finally, process 404 creates a Disease Management Order(DMO) record, in which the cumulative decisions made by the DMM during this DM session are stored. The DMO is further described in section Disease Management Order.
  • Process 404 receives control at the start node 430 .
  • process 220 passes control to decision 432 , which looks up the patient's identification in the DM register to see whether the patient is a registered, i.e. has conducted previous DM sessions. If the patient is not registered, process 404 passes control to step 434 , otherwise to step 452 , which will be described later in this section.
  • Step 434 is the first of seven successive steps 434 , 436 , 438 , 440 , 442 , 444 , 446 that register a patient for Disease Management.
  • Step 434 outputs messages to greet and inform the patient that s/he is about to begin registration for DM.
  • step 436 inputs the name of the disease to be managed.
  • step 438 interviews the patient to input data required to conduct Disease Management, including the name of a representative that can speak for the patient, the name and location of the patient's physician, names and telephones emergency facilities near the patient, and so on.
  • step 440 creates a record for the new patient in the DM registry.
  • step 442 establishes the patient as a registered DM patient.
  • step 444 creates a new data record for use by the DMM in the patient's database.
  • step 446 creates a new data record for session data in the session database.
  • Step 446 completes the registration of the patient as a new DM patient.
  • control goes to step 448 , which creates a new creates a Disease Management Order (DMO) record, in which the cumulative decisions made by the DMM during this DM session are stored.
  • step 448 initializes the DMO to indicate that this patient is a newly registered DM patient and needs an initial health assessment.
  • process 404 passes control to step 450 , which returns control to the process that called process 404 .
  • DMO Disease Management Order
  • Step 452 retrieves the patient's medical record from the patient database.
  • control passes to step 454 , which loads the last DM session data for this patient from the session database.
  • control passes to step 456 , which confirms that the last session terminated normally and sets appropriate control data if it did not.
  • control passes to step 458 , which initializes the DMO to indicate that this patient needs a current health assessment in subsequent processing.
  • control passes to step 450 , which returns control to the process that called process 404 .
  • Process 406 performs the health assessment for the DM session. It is basically a staging process that invokes other processes that perform health assessment of the patient.
  • Process 406 receives control at start node 480 .
  • process 406 invokes process 482 , which is named the Significant Symptom Filter and will be described below in conjunction with FIG. 8 .
  • process 406 passes control to the test 484 , which tests the DMO record code to determine whether this patient is a new DM registrant or a returning DM patient.
  • process 406 invokes node 488 , which assesses the health of newly registered patients and will be described below in conjunction with FIG. 10 .
  • process 406 invokes node 490 , which performs the health assessment for returning DM patients and will be described below in conjunction with FIG. 11 .
  • process 406 returns control at node 492 .
  • Process 482 applies several tests to the patients current symptoms to classify the patient's current health state, decide on specific assessment needs and their reasons, and forward this assessment to subsequent DM processes. These needs are saved in the patient's DMO, which is then processed by subsequent DMM routines. The DMO record is described later in section Disease Management Order.
  • Process 482 receives control at start node 510 . From there, it passes control to test node 512 , which represents the first filter by asking the patient whether s/he is having any significant symptoms at present. If the patient is not having significant symptoms, s/he can be assessed by automated means, and therefore process 482 passes control to step 544 . Step 544 which sets the DMO record code to indicate that this patient's health needs to be further assessed by subsequent routines. The control returns via node 526 .
  • process 482 needs to determine whether or not the patient has a symptom related to the disease being managed. To do this, process 482 passes control first to step 514 , which inputs the symptom from the patient and looks it up in a table of related symptoms, and next to test 516 , which branches to node 520 if the symptom is related to the disease being managed, and branches to node 530 otherwise. This completes the second filter, which has now identified patients with and without significant related symptoms.
  • process 482 invokes the Severity Assessment function 520 to further classify the related symptom as mild or severe. For patients with severe related symptoms, process 482 passes control to step 522 , which sets the DMO record to indicate the findings so far. From step 522 , control returns via node 526 . But if at test 520 , the symptom is judged to be mild, then process 482 passes control to node 524 , which sets the DMO record to indicate need for normal health assessment. From node 524 , process 482 returns control via node 526 .
  • process 482 needs to determine whether or not the patient has a side effect related to the current therapy of the patient. To do this, process 482 passes control first to step 530 , which looks up the patient's symptom in a table of side effects of the current therapy. Process 482 next passes control to test 532 , which is a filter that determines side effect symptoms. If the patient's symptom is a side effect, process 482 invokes the Severity Assessment function 520 to classify the side effect as mild or severe. For mild side effects, process 482 passes control to node 536 , which sets the DMO record to be assessed by subsequent processing. For severe side effects, process 482 passes control first to step 534 , which marks the DMO record to refer the patient out of the system to a human physician, and then returns to the calling process via node 526 .
  • Process 482 invokes the Severity Assessment function 520 to classify the symptom as mild or severe. For mild symptoms, process 482 passes control to node 542 , which sets the DMO record flag to force a special discussion with the patient after all DM processing is performed, and notes the reasons for the discussion. Then process 482 passes control first to node 544 which sets the DMO record to force subsequent health assessment and next to node 526 , which returns to the process that called process 482 . For severe unrelated symptoms, process 482 passes control first to step 540 , which marks the DMO record to refer the patient out of the system to a human physician, and then returns to the calling process via node 526 .
  • Severity Assessment function 520 uses a number of criteria to decide whether a given symptom is to be considered mild or severe for the DM assessment purposes.
  • Function 520 receives control at start node 560 , where it begins a sequence of 6 consecutive steps and then returns the computed result.
  • function 520 passes control to node 562 , which asks the patient to rank the symptom's severity on a scale of 0 to 10.
  • function 520 passes control to node 564 , which obtains the absolute severity scale of the symptom itself from the symptoms database. Different symptoms have different severity scales, and the patient's ranking is now matched to that of the symptom.
  • function 520 passes control to node 566 , which normalizes the patient's ranking, so that it is expressed in terms of the symptom's severity scale.
  • function 520 passes control to node 568 , which uses the Sensitivity Factor Set to adjust the normalized severity ranking up or down, depending on the current sensitivity setting of the DMM. Thus, the higher the Sensitivity, the more conservative the system is in its assessments. At the lowest Sensitivity setting, all symptoms severity ratings will be considered mild.
  • function 520 passes control to node 570 , which converts the final adjusted ranking into 2 classifications, mild or severe.
  • function 520 passes control to node 572 , which returns a code for either “mild” or “severe” to the calling process.
  • Process 488 performs a health assessment for patients who are having their first Disease Management session.
  • Process 488 receives control at node 600 .
  • Process 488 then passes control to node 602 , which loads the health assessment specifications for the disease being managed from the disease database. These specifications include various parameters to be used in Disease Management sessions, such as patient instructions, choices of therapies, permissions required, and so on. After these values are obtained, process 488 passes control to node 604 , which initializes a DM session segment in the patient's medical history and the sessions database.
  • process 488 passes control to node 606 , which conducts an initial health interview to ask the patient for a subjective assessment of current health, for any objective health measurements the patient may have available, any pre-existing therapy or side effects, and so on. Then process 488 passes control to node 608 , which returns control to the calling process.
  • Process 490 obtains current health data from the patient in three forms: subjective (i.e. as perceived or felt by the patient), objective (i.e. as measured by the patient, typically with an instrument), and side effects noted by the patient. These health measurements are then used to analyze the current health state.
  • Process 490 receives control at node 620 . From node 620 , process 490 passes control to test 622 , which examines the current DMO record of the patient to determine what processing has been done and what needs to be done. If the DMO record code does not indicate that a health assessment is required, process 490 passes control to node 634 , which returns control to the calling process.
  • process 490 passes control to a sequence of 5 steps that obtain various health assessments.
  • process 490 passes control to step 624 , which asks the patient for a subjective assessment of the patient's current health state.
  • process 490 passes control to step 626 , which asks the patient for objective health measurements of the patient's current health state.
  • process 490 passes control to step 628 , which asks the patient for any current side effects.
  • process 490 invokes the Correlation Assessment function 630 . This function is described in conjunction with FIG. 12 .
  • process 490 passes invokes the Critical Curve Assessment function 640 . This function is described in conjunction with FIG. 13 .
  • process 490 passes control to step 632 , which returns control to the calling process.
  • This function computes and standardizes the SOCF for recently added data, computes other assessment parameters and statistics, and updates the patient medical history. Finally, it invokes the health assessment function again to fill in data gaps for the interval since the last session.
  • Process 630 receives control at start node 650 . Then process 630 passes control to step 652 , which obtains any new health data that have been added to the patient's medical history since the last DM session. Then process 630 passes control to step 654 , which computes new points on the raw SOCF time plot by taking the ratio of subjective to objective measurement for the same time and updating the raw SOCF time plot array with the new points. Then process 630 passes control to step 656 , which applies standard statistical normalization and curve-fitting techniques to normalize the raw SOCF points and obtain a single current SOCF that is high in patients whose subjective assessment tends to match their objective health measurements, and low in patients whose subjective assessments tend to be inaccurate by comparison with their objective health measurements.
  • Step 656 also computes other parameters used in the rest of the DM session, such as the slope and slope trend for the most recent 3 data points and the difference between patient's measurements and normal measurements. Step 656 also determines whether there are large gaps in the patient's health data, that need to be filled retroactively in by an interval assessment. Step 656 sets the DMO code appropriately to call for another assessment. Then process 630 passes control to step 658 , which updates the patient's medical history with the computed assessment parameters. Then process 630 passes control to test 660 , which determines whether the patient's health is to be assessed again for missing interval data. If test 660 determines that no further assessment is required, process 630 passes control to terminal node 662 , which returns control to the calling process.
  • other parameters used in the rest of the DM session such as the slope and slope trend for the most recent 3 data points and the difference between patient's measurements and normal measurements. Step 656 also determines whether there are large gaps in the patient's health data, that need to be filled retroactively in by
  • test 630 passes control to test 664 .
  • Test 664 determines the type of data to be re-assessed for the interval. If test 664 determines that objective data are available, process 630 invokes Health Assessment process 490 , passing a parameter that asks for both subjective and objective patient health data to be assessed for the interval. Then process 630 passes control to terminal node 674 , which returns control to the calling process. If test 664 determines that objective data are not available, process 630 invokes Health Assessment process 490 , passing a parameter that asks for only subjective patient health assessments to be obtained for the interval. Then process 630 passes control to terminal node 672 , which returns control to the calling process.
  • Critical Curve Assessment is a DMM process for monitoring patient health for significant deterioration.
  • a critical curve is defined as a plot of a health measurement against time that is used to identify significant changes in health state.
  • the Critical Curve Assessment process selects a disease- and patient-specific health parameter, plots it as a critical curve, updates the critical curve as a normal part of continuing DM sessions, and takes specific action if the patient's critical curve exhibits specific critical points, slopes, and slope trends. The process is based on comparing the patient's critical curve to standard, disease-specific critical curves.
  • a constant, high ordinate value indicates good health; a declining curve indicates declining health; a sharp drop in the curve indicates a health crisis.
  • the “critical point” on the curve is a point that predicts a significant decline in health.
  • FIG. 23 An example of a generic critical curve is shown in FIG. 23 , which contains a point circled as the “critical point”.
  • the slope of the curve i.e. the line tangent to the curve at the critical point
  • the rate of slope change may also be negative, indicating that the slope of the curve is decreasing even more, predicts a rapidly deteriorating health state.
  • these three critical test items are typically referred to in the DMM processes as the critical point, slope, and trend. They are calculated using the last three health measurement points. For critical curves with sufficient data points, curve fitting techniques can also be used.
  • the DMM has a database of diseases 262 ( FIG. 3 ) that contains standard critical curves for various diseases, patient populations, and health parameters.
  • the Critical Curve Assessment process extracts the appropriate disease data set, selects an appropriate health parameter to be used, adapts it for the current patient, and saves it as the standard curve for the current patient in the patient's medical history 254 ( FIG. 3 ).
  • the Critical Curve Assessment process obtains current data from the patient, plots them on the patient's critical curve, and uses curve-fitting and pattern matching techniques to compare the patient's actual CC to the patient's standard CC.
  • This comparison enables the DMM to detect key points and trends on the patient's curve, such as the “critical point” that predicts a significant impending health decline.
  • the Critical Curve Assessment method orders alterations in therapy that will prevent the predicted deterioration, or sets a flag to refer the patient to a health care provider.
  • Both objective and subjective health data are used to plot the CC, especially if the Subjective-Objective Correlation Factor (SOCF) is high (which means that the patient knows his/her disease process well and the DMM can rely on the patient's responses more and more).
  • SOCF Subjective-Objective Correlation Factor
  • homeostasis is a state of dynamic equilibrium of the body. This equilibrium is maintained by various internal control mechanisms that force certain system parameters to remain within a desired range. Using these homeostatic mechanisms, the body is able to tolerate disease up to a certain point, at which time progression of the disease begins to accelerate. Good examples of this are:
  • the Critical Curve describes the patient's health state during a bout with disease.
  • the curve plots the patient's health state against time, starting initially at a (high) normal state of health and descending—as the disease progresses—to a lower state of health.
  • a normal, disease-free patient will have a fairly steady plot at a high level of health.
  • the initial part of the curve is asymptotic to normal health because the healthy body can often resist disease for some time by using reserve capacities and internal defense mechanisms.
  • the health curve begins to descend at a steeper and steeper angle, as reserves are used up and the disease is established and produces secondary effects. At some critical point, the curve steepens so dramatically that the patient's condition may deteriorate quickly.
  • the DMM can recommend a change in therapy or consultation with the patient's health caregiver. If confirmation of the change of the health state is required, the DMM reenter feature allows the DMM system to confirm its hypothesis before making recommendations.
  • the DMM monitors the patient's periodic contacts and health state reports. When the trend line indicates that the patient's health curve is reaching the critical point, the DMM can change the therapy and/or notify the patient's physician. Since patients can go for months successfully managing their disease, this Curve analysis approach can save a significant number of unnecessary physician visits, yet inform the physician and the patient at once when a change in health state indicates that the critical point is being approached.
  • the system measures the tidal volume and peak flow rates over time. If it is found that small changes in tidal volume make large differences in the patient's impression of the severity of their disease (compared to the changes made previously in this patient), the patient is on the steep part of the curve. A flag is set and significant intervention is necessary.
  • the therapeutic alteration permission level is set low, then the patient is referred to his physician, and the patient's doctor receives a report, frequently a fax, e-mail or downloads about the new developments. If the therapeutic alteration level is set high, then therapeutic optimization may occur before the patient sees his physician. A report is sent to the physician and the patient may or may not have to be seen.
  • Chronic obstructive pulmonary disease slowly destroys lung tissue.
  • many physiologic parameters have the same response to changes, being able to compensate up to a point, and then, after that reserve capacity is gone, very small changes in the disease state produce very large changes in the expression of the progression of the disease in the patient its early phase, the patient with chronic obstructive pulmonary disease loses only reserve lung capacity, so there is no significant change in the resting health state.
  • a threshold is reached beyond which smaller and smaller time increments (and progression of the disease process) will produce more and more profound deterioration in the patient's ability to blow off carbon dioxide and oxygenate the blood.
  • even a very small change in chronic obstructive pulmonary disease results in respiratory failure.
  • the Critical Curve Assessment function 640 will be described. This function has two phases. The first phase (starting at node 702 ) updates the patient's critical curve with health measurements added to the patient's medical history since the last critical curve assessment. The second phase (starting at node 712 ) compares the patient's actual critical curve to the standard critical curve used for this patient. If a patient is at (or is approaching) a critical part of the curve, this suggests the possibility of rapid deterioration of the disease being managed, and the patient is referred to a human physician for consultation.
  • Process 640 receives control at start node 700 . Then process 640 passes control to step 702 , which updates the patient's actual critical curve with new health measurements. Next, process 640 passes control to step 704 , which analyzes the patient's updated critical curve to obtain the latest critical curve point, slope, and 3-point trend. Next process 640 passes control to step 706 , which saves the patient's critical curve data in the patient medical history. Next, process 640 passes control to test 708 , which examines the DMO record code to see whether the patient's critical points should be assessed. If the patient's critical points should not be assessed, process 640 passes control to terminal node 710 , which returns control to the calling process. If the test 708 indicates that health assessment is needed, process 640 passes control to step 712 .
  • Step 712 begins the assessment phase of process 640 .
  • Step 712 retrieves or computes the working data needed to use the critical curve to assess patient health.
  • Working data include the patient's latest actual health point and slope, the matching point and slope on the patient's standard critical curve, and the thresholds used to rule the patient as critical for each set.
  • process 640 passes control to test 714 .
  • Test 714 begins a sequence of steps that examine the patient's critical point. If test 714 finds that the patient's latest health point is not available or cannot be matched on the standard curve, process 640 passes control to terminal node 716 which passes control to the calling process. If test 714 determines that the latest health point is available, then process 640 passes control to step 718 which compares the difference between the actual and standard critical health points. Then process 640 passes control to test 720 . If test 720 finds that the patient does meet or exceed the critical point threshold, process 640 passes control to step 722 , which sets the DMO record to refer the patient to a human physician for consultation. Then process 640 passes control to terminal node 724 , which returns control to the calling process. If test 720 finds that the patient does not meet the critical point threshold, process 640 passes control to test 726 .
  • Test 726 begins a sequence of steps that examine the patient's critical slope. If test 726 determines that the critical slope is not available, process 640 passes control to terminal node 724 which returns control to the calling process. If test 726 determines that the actual slope is available, process 640 passes control to 728 , which compares the difference between the actual and standard critical slopes. Then process 640 passes control to test 730 . If test 730 determines that the patient is below the critical slope threshold, process 640 passes control to node 724 , which returns control to the calling process. If test 730 determines that the patient does meet or exceed the critical slope threshold, process 640 passes control to node 732 , which sets the DMO record to refer the patient to a human physician for consultation. Then process 640 passes control to node 724 , which returns control to the calling process.
  • the Therapy Optimization consists of a set of processes that review and adjust patient therapy from session to session, with a long-term goal of maximizing efficacy, minimizing adverse side effects, and maintain patient cooperation and acceptance of the recommended therapy.
  • the Therapy Optimization processes select therapy parameters from medical treatment tables and track patient-specific efficacy by reviewing subjective and objective patient health data from session to session.
  • the Therapy Optimization process selects from multiple therapies. It seeks to minimize side effects by offering the patient the choice of alternate therapies, and by adjusting therapy dosage levels until the patient finds the appropriate comfort level. Disagreements between the DMM and the patient are resolved by referring the patient to a human physician for face-to-face consultation and advice.
  • Therapy Optimization is guided and controlled by the Therapy Optimization Permission Level (TAPL), a DMM-global variable that specifies the amount of autonomy that the DMM has to alter therapy.
  • TAPL Therapy Optimization Permission Level
  • the Therapy Optimization process reviews and adjusts (to the extent the TAPL allows it) the patient's treatment to achieve the best combination of several subgoals of the overall goal of restoring normal health.
  • the Therapy Optimization process also seeks to minimize treatment side effects.
  • the DMM will gradually titrate the dose of a medication until the benefit/side effect ratio is maximized.
  • the overall idea is to achieve the desired physiological changes with the fewest side effects.
  • Initial treatment is selected from a treatment table based on disease, age, and sex.
  • the different formulation, dosing, administering methods and timing are, in effect, a matter of trial and error for a specific patient.
  • the Therapy Optimization task compares the patient's current therapy to the treatment table to detect and analyze differences. If a new treatment is available, the patient and the healthcare giver are notified, and the therapy may be altered, depending on the TAPL.
  • the Function can select the initial therapy, review the patient's current therapy, adjust various parameters of the therapy, and monitor the effect of these changes.
  • Therapy parameters that can be changed include drug class, type, brand, dose, route, mode of drug administration, formulation, timing, and frequency. As each of these is modified, the patient's health data and side effects are checked to see if the current modification of therapy makes the patient better, and so on. Each therapy parameter is sequentially altered on a trial and error basis to find the overall best combination of therapy parameters.
  • the DMM adjusts a patient's therapy, it adjusts the DM session schedule appropriately, typically instructing the patient to re-enter the system within a few iterations of therapy or dosage.
  • Process 408 performs the therapy phase of the DM session. This phase computes the next best therapy step that is accepted by the patient, using two major subordinate processes and a loop that tries various therapies until the patient accepts one.
  • the general goal of process 408 is to select therapy steps in a manner that optimizes therapy over the long term, by maximizing efficacy, minimizing side effects, and adjusting therapy types and modalities to meet the patient's comfort level.
  • Process 408 receives control at start node 760 . Then, process 408 passes control to test 762 , which tests whether the patient provided current objective health measurements during the earlier part of this DM session.
  • process 408 passes control to test 782 , which tests whether the patient entered a subjective assessment of his/her health during the earlier part of the DM session. If test 782 finds that the patient provided a subjective health assessment, process 408 invokes process 790 . Process 790 adjusts the therapy based on current subjective health data. Process 790 is detailed below in conjunction with FIG. 15 . When process 790 returns control, process 408 passes control to terminal node 792 , which returns control to the calling process. If test 782 finds that the patient did not provide a current subjective health assessment, process 408 passes control to 784 , which sets the DMO record to refer the patient to a human physician for consultation. Then, process 408 passes control to terminal node 786 , which returns control to the calling process.
  • process 408 passes control to step 764 , which initializes a loop that will try various therapies until the patient accepts one or until the number of retries is exhausted, whichever occurs first. Step 764 obtains the maximum number of therapy permitted from the permissions database for this patient. Then, process 408 invokes process 770 . Process 770 selects the next best therapy from the treatment table for this patient and offers it to the patient who can accept or modify or reject it. Process 770 is further described below in conjunction with FIG. 16 . When process 770 returns control, process 408 passes control to test 772 . If test 772 determines that the patient accepted the therapy recommended, process 408 passes control to terminal node 780 , which returns control to the calling process.
  • process 408 passes control to test 774 . If test 774 determines that the loop retry count is greater than one, process 408 passes control to step 776 . Step 776 reduces the loop retry count by 1 and then process 408 invokes process 770 again for another iteration of the loop. If test 774 determines that the retry count is 1, then process 408 passes control to step 778 . Step 778 sets the DMO record to refer the patient to a human physician for consultation. Then, process 408 passes control to terminal node 780 , which returns control to the calling process.
  • Process 790 computes the next best therapy for this patient, based only on the patient's subjective assessments of his/her health.
  • Process 790 uses the Subjective-Objective Correlation Factor (SOCF) which is described below in the section Subjective-Objective Correlation Factor.
  • SOCF Subjective-Objective Correlation Factor
  • the SOCF indicates how reliable this patient is in subjectively assessing his/her disease, and process 790 relies on the SOCF in computing the next therapy step.
  • Process 790 receives control at start node 810 . Then, process 790 passes control to test 812 . If test 812 determines that the patient does not need therapy adjustment, i.e. that the DMO record of this patient has already been completed for an approved therapy, process 790 passes control to terminal node 814 which returns control to the calling process. If test 812 determines that this patient requires therapy optimization, process 790 passes control to test 816 . Test 816 determines (by asking the patient or by obtaining the patient's saved response if the patient has already been asked) whether the patient is having any current symptoms. If test 816 finds that the patient is symptom-free, process 790 passes control to test 818 .
  • process 790 passes control to node 826 , which sets the DMO record to maintain the same therapy, e.g. the same dose in the case of a drug-based therapy. Then, process 790 passes control to terminal node 824 , which returns control to the calling process.
  • test 818 determines that the current TAPL setting does permit therapy adjustments, process 790 passes control to test 820 . If test 820 determines that the patient does not want to try to reduce the dose, process 790 passes control to step 826 , which sets the DMO record to maintain the same therapy. Then, process 790 passes control to terminal node 824 , which returns control to the calling process. If test 820 determines that the patient wants to reduce the dose, process 790 passes control to step 822 , which looks up the next lower dosage level in the treatment table and sets the DMO record to decrease the dose. Then, process 790 passes control to terminal node 824 , which returns control to the calling process.
  • process 790 passes control to test 830 . If test 830 finds that the TAPL does not permit changes in therapy, process 790 passes control to step 832 . Step 832 sets the DMO record to refer the patient to a human physician for consultation. Then, process 790 passes control to terminal node 833 returns control to the calling process. If test 830 finds that the TAPL does permit changes in therapy, process 790 passes control to step 834 .
  • Step 834 begins that phase of process 790 which computes the next therapy step for a patient who is having symptoms, but has only reported current subjective health assessments.
  • Step 834 uses the current SOCF from the patient's medical history, modifies it by the current Sensitivity Factor Set to adjust it to the sensitivity being used for this patient, and then classifies the patient's current SOCF as “high” or “low” for the purpose at hand. If test 834 classifies the patient's SOCF as high, the patient's subjective health assessment is reliable, and process 790 passes control to step 838 which looks up in the treatment table how much the therapy (i.e. dose in the example drawn) can be increased for a patient with a high SOCF, and what the associated benefits and risks are.
  • the therapy i.e. dose in the example drawn
  • process 790 invokes function 840 .
  • test 834 deems the SOCF as low, process 790 passes control to step 836 , which obtains the dose and risk/benefit factors for unreliable patients. In either case, process 790 continues by invoking function 840 .
  • the Patient Consent Level function 840 presents a recommended therapy to the patient and obtains a consent of the patient to the therapy as recommended or to some variation of it; the patient may also reject the recommended therapy entirely. Function 840 is described below in conjunction with FIG. 17 .
  • Step 842 sets the DMO record to indicate the next therapy with an increased dose, and with an appropriate change in schedule for a sooner DM session. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
  • Step 846 sets the DMO record to indicate that the same therapy is to be continued. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
  • Step 848 sets the DMO record to indicate the next therapy with a reduced dose. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
  • test 850 consults the current Sensitivity Factor Set to see whether process 790 should try the next best therapy or should refer the patient to a human physician. If test 850 determines that other therapies may be tried, process 790 passes control to node 852 , which sets the DMO record to indicate that the patient rejected the recommended therapy. Then, process 790 passes control to terminal node 844 , which returns control to the calling process. If test 850 determines that the patient should be referred, process 790 passes control to node 854 , which sets the DMO record to refer the patient to a human physician. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
  • Process 770 computes the next best therapy for this patient, based on the patient's current objective health measurements.
  • the process receives control at start node 870 .
  • process 770 passes control to test 872 .
  • Test 872 compares health assessment parameters to determine whether the patient's objective health data meet or exceed various thresholds.
  • Test 872 first compares the patient's current health measurement to an absolute threshold for that measurement, to see if the measurement itself is in acceptable range.
  • Test 872 next compares the slope of the last two health measurements, to see if the patient's health is deteriorating at a rate that exceeds a threshold.
  • Test 872 next compares the change in the slopes of the last three measurements, to see if the patient's rate of change of health is getting worse more and more rapidly. If any one of these thresholds is met or exceeded, process 770 passes control to step 874 , which sets the DMO to refer the patient to a human physician. Then, process 770 passes control to terminal node 876 , which returns control to the calling process.
  • test 872 determines that all of the patient's current health statistics are below threshold, process 770 passes control to test 878 .
  • Test 878 begins that phase of process 770 which computes the next recommended therapy for this patient.
  • Test 878 compares the current patient health measurements to those of the previous DM session, to classify the patient's change of health state as “better, same, or worse” for the purpose of computing the next therapy step.
  • test 878 determines that the patient is worse than the last time, process 770 passes control to test 880 .
  • Test 880 determines (from the treatment table) whether the current therapy dose can be increased. If test 880 determines that the dose can be increased, process 770 passes control to node 882 , which sets the DMO to increase the dose. Then, process 770 passes control to test 896 . If test 880 determines that the dose can not be increased, process 770 passes control to node 884 , which sets the DMO to continue therapy with the same dose. Then, process 770 passes control to test 896 .
  • test 878 determines that the patient is in the same health as the last time, process 770 passes control to test 892 .
  • Test 892 determines whether the patient's current health measurements are in normal limits. If test 892 determines that the patient's current health data are normal, process 770 passes control to step 890 . Step 890 sets the DMO to decrease the dose. Then process 770 passes control to 896 . If test 892 determines that the patient's current health data are outside normal limits, process 770 passes control to test 880 . Test 880 has been described above for process 770 .
  • test 770 passes control to test 886 . If test 886 determines (by consulting the treatment table) that the current dose can be reduced, process 770 passes control to step 890 . Step 890 has been described above for process 770 . If test 886 determines that the current dose can not be reduced, process 770 passes control to step 888 , which sets the DMO to continue therapy with the same dose. Then, process 770 passes control to test 896 .
  • Test 896 determines whether the TAPL setting for this patient allows the DMO as computed so far by process 770 . If test 896 determines that the TAPL allows the DMO as written, process 870 invokes the Patient Consent Level function 840 , which presents a recommended therapy to the patient and obtains a consent of the patient to the therapy as recommended or to some variation of it; the patient may also reject the recommended therapy entirely. Function 840 is described below in conjunction with FIG. 17 . If function 840 returns the result that the patient accepts the recommended therapy (perhaps at some modified level), process 770 passes control to terminal node 898 , which returns control to the calling process. If function 840 returns the result that the patient rejects the recommended therapy entirely, process 770 passes control to test 900 .
  • Test 900 consults the current Sensitivity Factor Set to see whether process 770 should try the next best therapy or should refer the patient to a human physician. If test 900 determines that other therapies may be tried, process 770 passes control to node 902 , which sets the DMO record to indicate that the patient rejected the recommended therapy. Then, process 770 passes control to terminal node 904 , which returns control to the calling process. If test 900 determines that the patient should consult a physician, process 770 passes control to node 906 , which sets the DMO record to refer the patient to a human physician. Then, process 770 passes control to terminal node 904 which returns control to the calling process.
  • process 770 passes control to step 908 , which sets the DMO record to refer the patient to a human physician. Then, process 770 passes control to terminal node 904 which returns control to the calling process.
  • Function 840 presents a recommended therapy to the patient and obtains the consent of the patient to the therapy, either exactly as recommended by the DMM, or as adjusted to some variation of it, based on the patient's responses. The patient may also reject the recommended therapy entirely.
  • Function 840 receives control at starting node 920 . Then process 840 passes control to step 922 , which outputs the therapy as recommended in the DMO to the patient. Next, process 840 passes control to step 924 , which presents the risks and benefits to the patient. Next, process 840 passes control to step 926 , which presents other therapy choices to the patient.
  • process 840 passes control to step 928 , which asks the patient to agree to the recommended therapy, or to some version of the therapy.
  • process 840 passes control to step 930 , which updates the DMO to record the choices offered, warnings given, and consent level received, with suitable date and time stamps.
  • process 840 passes control to step 932 , which computes a function result to be returned to the calling process.
  • the consent level granted by the patient may have several values. The four values used in the flowcharts assume a drug therapy, and are: (1) ok to increase dosage; (2) ok to keep dosage at same level; (3) ok to reduce dosage; and (4) reject this therapy.
  • process 840 passes control to terminal node 934 , which returns control to the calling process.
  • Process 410 is the last process executed for every DM session. It is specifically responsible for processing the Disease Management Order (DMO), which contains the complete set of tests made and reasons therefore, the next therapy step recommended, consent given by the patient, and various associated orders, such as to fax a prescription to the patient's pharmacy, to order a test from a laboratory, to prepare a report for the patient's physician, to send printed instructions to the patient, and so on.
  • DMO Disease Management Order
  • process 410 is also generally responsible for logging all events that occurred during the DM session, storing all relevant data, closing all applicable files, scheduling the next DM session, and finally bidding the patient farewell to indicate that the current DM session is terminated.
  • Process 410 receives control at start node 950 .
  • process 410 passes control to test 952 , which logs the therapy ordered by the DMO in the patient's medical history. Then process 410 passes control to test 954 , which determines whether the DMO contains special orders to be processed. If test 954 determines that the DMO has no special therapy orders, process 410 passes control to step 972 , which schedules the next DM session as specified in the current therapy schedule of the patient. Then, process 410 passes control to node 962 . Processing from node 962 is described below for process 410 . If test 954 determines that the DMO has special orders, process 410 passes control to step 956 , which schedules the next DM session as ordered by the DMO.
  • process 410 passes control to step 958 , which prepares and sends various notices and reports to various contacts. These notifications and the contacts that receive them are controlled by the Regulatory, Sharing, and other authorization fields that are maintained in the Permissions database.
  • process 410 passes control to step 960 , which informs the patient about the next therapy step and gives the patient instructions as ordered by the DMO and as permitted by the Permissions database.
  • process 410 passes control to step 962 .
  • Step 962 informs the patient's physician about the DM session and about the therapy ordered by the DMM. While the patient's physician is always entitled to all information generated for the patient, the physician may specify the notices sent and the detail reported. The physician's current requirements and limitations for notification are stored in the permissions database, and may be modified by the physician using processes outside of the DMM.
  • process 410 passes control to step 964 , which informs the patient about the actions taken by the DMM software, to the extent permitted in the Permissions database. This step allows the system to tell the patient what it is doing and why, which can gain the patient's confidence and help the patient to make better decisions in future sessions. This feedback is an important element of the long-term therapy optimization that is one of the hallmarks of this invention.
  • Step 964 also reviews all special flags set to discuss new symptoms with the patient.
  • process 410 passes control to step 966 , which saves all relevant data in various suitable main and backup storage locations.
  • process 410 passes control to step 968 , which closes all applicable data files and releases all temporary computing system resources allocated to the DM session.
  • process 410 passes control to terminal node 970 , which returns control to the calling process.
  • the Question Versions feature of the DMM allows several different versions of the same question to be written into a script, and defers the decision which version to use until run-time.
  • the feature uses a global data item called the Question Version Index (QVI) to select the desired version of the question from the script at run time.
  • QVI Question Version Index
  • the Question Version feature can be visualized as a “Question Roller”: a multi-faceted cylinder with one different version of the question written on each face. To ask a question, the cylinder is rolled to display the face that contains the desired question text. If each question of a set is written on a separate cylinder, and all cylinders are rolled in unison to display the same face, as specified by a global control element, the entire question set of the script can be adjusted or “rolled” as one unit, so that the script as a whole can be adjusted or fine-tuned to ask different versions of the question at different levels.
  • One use of the Question Versions feature is to be able to globally adjust the sensitivity and selectivity of the language used by the entire DMM, using a DMM-global QVI that controls the linguistic sensitivity.
  • the Question Roller is turned or ratcheted one way to increase the sensitivity and the opposite way to increase the selectivity.
  • each question version differs only slightly in wording and sensitivity. In some cases, the only difference is a comma (a pause) or an intonation of the voice, such as:
  • the DMM can ask the same question in various forms written for a 3rd grader, for a high school student, for a college graduate, or for a health care provider.
  • the DMM can adapt output to the patient's communication needs, which may involve a range of decisions based on what is currently known about the patient, such as what natural language to use, what the level of understanding is, what grammar to use (e.g., are we addressing the patient, the patient's relative, or the patient's doctor?), and what medical details to disclose.
  • the DMM can consult the patient's medical history to determine the level of the language, education, and intelligence that the patient can understand. If no indicator is present, a mini language IQ test can be given as part of the Initial Health Assessment task to establish the QVI to use with the patient.
  • the DMM can adjust the question level dynamically, based on the patient responses or requests.
  • a patient who is getting confused or lost may ask the DMM to give more detailed instructions on how to respond to questions.
  • the DMM can react by altering the QVI to select more appropriate question versions.
  • the DMM can respond by adjusting the QVI. In this manner, the DMM learns about the patient's current and past use of the DMM and can modify itself to adapt to the patient's natural language, education, medical knowledge, and medical sensitivity required.
  • the Question Version feature is implemented in software by allowing script authors to collect different versions of a question into a “version group,” in which each version of the question is associated with a different QVI.
  • the DMM uses the Sensitivity Factor Set to establish a global QVI to specify the current question version to be used with the current patient by all scripts.
  • a DMM process (such as the script engine) needs to output a question, it uses the global QVI to find and retrieve the desired question from the script's question group. Questions that do not require different versions are written as a version group with only one question, which acts as the default question. This default question is also used when there is no question in the version group for the current global QVI.
  • This Question Version design allows questions versions to be written for a wide range of QVIs, without having to write a version for each QVI.
  • a simple script can just have one question version; as the script improves, additional question versions are added. For example, the first script might be written in English, and later upgraded to add Spanish versions of each question.
  • the Question Version feature is implemented in the form of a Question Version Index and two separate functions Set QVI and Select Question.
  • FIGS. 19 a and 19 b these elements are shown as follows:
  • QVI Global Version Index
  • Set QVI is process 1000 ;
  • Process 1001 Select Question process is shown as process 1001 .
  • the current setting of the Global Version Index 1020 determines which one of several different question versions is selected and output to the patient.
  • Data element 1020 is stored as a control field in the permissions database 256 ( FIG. 3 ), and is changed by process 1000 and used by process 1001 .
  • Process 1000 is a DMM-global system service routine that sets and updates data element 1020 periodically.
  • Process 1000 receives control at starting node 1002 .
  • process 1000 passes control to step 1004 , which identifies the patient whose data element 1020 is to be set.
  • process 1000 passes control to step 1006 , which retrieves the current value of the patient's data element 1020 .
  • process 1000 passes control to step 1008 , which computes the new value of the data element 1020 .
  • Step obtains the level of sensitivity desired from the current Sensitivity Factor Set, and obtains other parameters from the patient medical history, such as the level of patient's education, the level of language understood, and the QVI settings used in past DM sessions.
  • step 1008 computes a new QVI value
  • process 1000 passes control to step 1010 , which stores the new value in the patient's data element 1020 . This completes the action of updating the patient's data element 1020 . Then process 1000 passes control to terminal node 1012 , which returns control to the calling process.
  • Process 1001 is a DMM-global routine that uses the Global Version Index 1020 to select one question from a set of questions.
  • Process 1001 receives control at starting node 1022 . Then process 1001 passes control to step 1024 , which loads the applicable question set from the current script's data area.
  • process 1001 passes control to step 1026 , which obtains the current value of the Question Version Index 1020 from the patient's permission file. Then process 1001 passes control to test 1028 . Test 1028 determines whether the question version selected by the QVI is in the question set obtained in step 1024 . If test 1028 determines that the desired version is in the question set, process 1001 passes control to step 1030 , which retrieves the question with the desired question level from the set. Then process 1001 passes control to step 1034 , which returns the question selected from the set as a function result to the caller. Then process 1001 passes control to terminal node 1036 , which returns control to the calling process.
  • process 1001 passes control to step 1032 , which retrieves the default question from the set. Then process 1001 passes control to step 1034 , which returns the question selected from the set as a function result to the caller. Then process 1001 passes control to terminal node 1036 , which returns control to the calling process.
  • Preview Mode is a DMM script run-time mode that allows the patient to “look ahead,” that is to examine the consequences of a response before “officially” giving the response. In effect, the patient can say—at any point in a script—“let me see what this answer would do”.
  • One use of Preview Mode is to let the patient suspend an ongoing dialog to see what a pending question means. Knowing the consequences of a response is helpful in clarifying the impact or focus of a question. Thus, in a printed flowchart or procedure, one good way to find the best path is to look ahead to see what the consequences (or recommendations) would be of answering a question a certain way.
  • Preview Mode Another uses of Preview Mode is to let the script explicitly warn the patient that a particular question involves serious consequences, and to use Preview Mode so that the patient can consider the effect of each response. For example, one response may begin action to contact the patient's physician, or to transfer the patient to an emergency facility. If the script can warn the patient about this consequence, the patient can preview these responses without activating them, and can alter the direction of the script dialog.
  • Process 1060 receives control at start node 1062 . Then process 1060 passes control to test 1064 . If test 1064 determines that there are no further questions to be asked, process 1060 passes control to terminal node 1066 , which terminates the Preview Mode. If test 1064 determines that is a question to be asked, process 1060 passes control to step 1068 , which outputs the question to the patient.
  • process 1060 passes control to step 1070 , which outputs the set of responses to the patient. Then process 1060 passes control to step 1072 , which inputs a response from the patient, together with an indicator that the patient does or does not want to preview the script's actions for this response. Then process 1060 passes control to test 1074 . If test 1074 determines that the patient has responded with the preview indicator set, process 1060 passes control to step 1076 . Step 1076 retrieves the preview information that is coded into the script (as part of the normal question and response texts) and outputs it to the patient, so that the patient sees or hears a description of what the selected response would do in “real” mode.
  • a preview text might tell the patient that “A YES response will increase your daily medication dose for the next 2 weeks”.
  • process 1060 passes control to step 1068 , which asks the same question again, as described above for step 1068 . But if test 1074 determines that the patient has responded without the preview indicator, process 1060 passes control to step 1078 . Step 1078 performs the actions normally scripted for the response given. Then process 1060 passes control to test 1064 , which determines whether there is a next question to be asked, as described above for test 1064 .
  • Every DMM dialog with a patient is controlled by a script.
  • the script selects a question and outputs it to the patient, and the patient inputs a response.
  • the script analyzes the response, selects another question, and outputs it to the patient.
  • This question-response-question-response dialog continues until the session is terminated normally.
  • all scripts are designed to invoke the No-Response (NR) feature, which is responsible for taking appropriate continuation action for the script.
  • the NR feature is a DMM software mechanism that is triggered when a timeout condition is signaled by the operating system.
  • the NR mechanism can take any number of actions that have been pre-arranged by the script and can be changed as the script runs.
  • the NR actions can range from a silent entry in the DM sessions log all the way to using health data from the patient medical history and medication and symptom data from the disease database to contact a responsible neighbor of the patient, or a nearby emergency response facility.
  • the NR feature is of special value in the context of the DMM, which has detailed medical information about a patient from previous sessions, and in the context of the First Opinion Support System, which has extensive relevant databases indexed by geographic location around the world (e.g., emergency rooms, 911 agencies, paramedics). Because of what the system knows about a patient, the NR feature can take very situation-specific actions. A very simple example would be a 60-year old man consulting for chest pain: sudden failure to respond to a question would suggest a cardiac arrest and could initiate emergency actions, including calling the patient's local 911 agency.
  • process 1100 shows only those portions of a script's steps that are relevant to the No-Response Feature. Other steps of the scripts are omitted for clarity.
  • Process 1100 receives control at start node 1102 , which represents the generic start node of any script. Then process 1100 passes control to step group 1104 .
  • Step group 1104 represents all of the script's actions that do not involve the NR Feature. If the script terminates as part of one of these steps, process 1100 passes control to terminating node 1106 , which terminates the script.
  • process 1100 passes control to step 1108 .
  • Step 1108 sets up the NR parameters needed later, if the patient should fail to respond.
  • the source of these parameters is the patient's medical history 254 , which contains the relevant information to be used if the patient fails to respond, such as the patient's disease, health state, medications being taken, physician, nearest emergency facility, and so on.
  • Step 1108 stores the NR parameters as a data set 264 .
  • process 1100 passes control to step 1112 , which outputs the actual question to the patient.
  • process 1100 passes control to test 1114 . Details of step 1114 vary with operating system and hardware platform, but the typical action is to set a timeout flag for a specified wait time, yield control to the operating system, and regain control when the operating system returns a response or the wait time has expired.
  • process 1100 passes control to step group 1104 , where the normal script's actions continue. If test 1114 receives a timeout, process 1100 passes control to step 1116 . Step 1116 retrieves the patient-, disease-, and location-specific NR data from the data sets 264 and 254 and performs the NR actions requested. When step 1116 has performed the NR actions, process 1100 passes control to terminal node 1116 , which represents the generic termination of a script due to a timeout.
  • the PQRST Array feature describes a set of software processes and data that work together to encode a patient's description of pain into a “pain code”, which is a specially formatted array of integers. Encoding is done in a manner that preserves the subjective information, so that it is possible to decode a pain code by using the array integers to recover the original words used to describe the pain.
  • a pain code is composed of subcodes; each subcode identifies one well-defined detail aspect of the experience of pain such as location, sensation, frequency, etc.
  • the pain subcodes are arranged into a specific sequence or format that is known to all software processes that manipulate the pain code.
  • the sequence used to encode the aspects is itself prefixed as a number to the sequence, so that so that the first aspect of the array always identifies the coding scheme that is used for the array. This makes the PQRST Array flexible and extensible, since various encoding schemes can be used to meet various needs. Any software process that needs to decode a PQRST in the future simply examines the first aspect code and knows from its value which decoding scheme to use for the rest of the aspects.
  • the PQRST Array feature permits encoding of a patient's report of pain into digital form that is suitable for software processes. For example, a patient's complaint that “when I bend my right arm or rotate my wrist, even slightly, the elbow area hurts really bad, with a sort of gritty or grinding sound, but there is no bleeding” may be encoded by letting the patient select from standard descriptor words (e.g. gritty, tight, numb) and converting the selected words into an integer array something like (7, 2, 3, 8, 5, 970612, 2, 13). This array represents the numeric value of various aspects of pain such as location, repeatability, quality, or a date such as 970612. For any given aspect, the number represents some degree or description of the pain. Thus, if the fourth aspect number represents Sounds-Associated-With-Movement, the subcode value 8 may represent “gritty/grinding noise associated with joint movement”.
  • Process 1140 comprises the steps required to create a PQRST Array that represents the digitized form of a patient's subjective description of pain.
  • Process 1140 is described here assuming that the patient is on-line and can interactively enter subjective pain description details when prompted by process 1140 .
  • Process 1140 receives control from a calling process at start step 1142 .
  • Step 1142 is the beginning of a loop that encodes pain aspects entered by the patient into a matching set of pain subcodes.
  • Step 1142 allocates space for a PQRST Array that will contain the subcodes.
  • process 1140 passes control to step 1144 , which establishes the next pain aspect to be encoded.
  • process 1140 passes control to step 1146 , which retrieve a list of standard aspect words from database 1150 and outputs them to the patient in a format of a pick list, i.e. a list that the patient can examine and from which the patient can pick one of the aspect words.
  • step 1146 retrieves a list of standard aspect words from database 1150 and outputs them to the patient in a format of a pick list, i.e. a list that the patient can examine and from which the patient can pick one of the aspect words.
  • process 1140 passes control to step 1152 , which asks the patient to select the aspect word from the pick list that best matches the patient's subjective description of the pain aspect being encoded.
  • process 1140 passes control to step 1154 , which converts the aspect word selected by the patient into an integer that identifies that aspect word. This integer is the subcode for the current aspect. It can be simply the index position of the selected aspect word in the pick list.
  • process 1140 passes control to step 1156 , which inserts the subcode integer into the PQRST Array, at the index position that represents the aspect being encoded.
  • process 1140 passes control to test 1158 , which determines whether more aspects are to be encoded. If test 1158 finds that there are more aspects to be encoded, then process 1140 passes control to step 1144 to begin another iteration of the loop just described. If test 1158 finds that there are no more aspects to be encoded, then process 1140 passes control to step 1160 , which stores or copies the PQRST Array into the appropriate data set, such as the patient's medical history 254 . Next, process 1140 passes control to step 1162 . Step 1162 returns control to the calling process.
  • Process 1170 is an example of the steps required to use a PQRST Array as an index to retrieve a specific diagnosis from a table of diseases.
  • This example assumes that a list of diseases (or disease sets, where there is more than one disease for a given pain code) has been indexed by pain code and stored into a database of diseases 262 .
  • This example also assumes that there is a software process for accessing the database that can retrieve elements of the database when given an access key.
  • a database access mechanism is a suitably formatted Structured Query Language (SQL) statement; another example is a simple array of disease names or pointer that is accessed using the index position of each element.
  • SQL Structured Query Language
  • Process 1170 receives control at start node 1172 . Then process 1170 passes control to step 1174 , which loads a copy of the PQRST Array to be used to select the diagnosis from database 262 . Next, process 1170 passes control to step 1176 , which converts the DMM pain code into an access key that is formatted as required by the process that accesses database 262 . Next, process 1170 passes control to step 1178 , which uses the access key to retrieve the record matching the pain code from database 262 . Next, process 1170 passes control to terminal node 1180 , which returns control to the calling process.
  • DMO Disease Management Order
  • the Disease Management Order is a data record that is attached to the patient at the beginning of a DM session, travels with the patient from process to process, and is used at the end of the session (by the Close Sessions process) to implement the decisions and orders issued by the various processes during the session.
  • the DMO record contains numerous fields and is stored in the sessions area of the DM-specific databases 264 ( FIG. 3 ).
  • DMO Dynamic Metal-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Oxide-Ox
  • DMO Downlink Assessment
  • the Correlation Assessment process requires additional health data for the interval between session, it can invoke Health Assessment again to obtain missing data ( FIG. 12 , node 660 ).
  • the process sets the DMO Code to “optimize therapy” and the patient is shunted out of the assessment cycle.
  • the DMO is to track various reasons for decisions made, which can be used by the Close Sessions process to issue detailed reports of what the DM processes learned about the patient.
  • the Therapy Adjustment processes can refer the patient to a physician for different reasons ( FIG. 14 , nodes 778 and 784 ; FIG. 15 , nodes 832 , 854 ).
  • the DMO code is set to “refer to MD”, but the DMO Reason field is set to indicate a different reason.
  • the key use of the DMO is to represent “doctor's orders”, i.e. to accumulate all of the orders issued during the session, so that they can be implemented when the session is terminated ( FIG. 18 , node 956 ).
  • the Permissions Database 256 ( FIG. 3 ) is a collection of all of the software elements that control access to DMM data and actions taken by DMM processes. This database supports the DMM safety, security, reliability, control, and management features in the form of passwords, access rights, need-to-know and right-to-know clearances, disclosure authorizations, consents, constraints, limits, thresholds, and so on.
  • the Permissions Database is the interface through which a human staff of medical and software experts can specify and control what automatic actions the DMM can and cannot perform. Since permissions govern the actions of all DMM processes, the Permissions Database can be used to dynamically configure the system to run in various modes, ranging from fully automatic to totally non-automatic, where the DMM has to ask permission for every detail step to be taken. The latter mode is especially useful for experimental, test, problem tracking, or system auditing uses.
  • Regulatory Permissions are data sets that insure compliance of the DMM with all applicable regulatory, licensing, and legal requirements and restrictions of the many jurisdictions in which it operates.
  • the Regulatory Permission data sets are organized by jurisdiction, and specify for each jurisdiction which data fields can be disclosed to what agency.
  • the Regulatory Permissions feature addresses a very complex issue that is typically ignored by other automated medical systems, namely that such systems may be deemed to be practicing medicine in and across controlling jurisdictions, even across international borders, and must therefore meet a large number of various medical practice constrains and licensing regulations. This feature allows the DMM to comply with the law in its actions and in its contacts with patients, physicians, health care management organizations, government agencies, and so on.
  • DMM-global DMM-global, and can be used wherever they are applicable.
  • One example is in the Close Session process ( FIG. 18 , nodes 958 - 964 ) which must consider the legal requirements and prohibitions regarding disclosure of confidential medical data before distributing notices, instructions, and reports about the DM session or the patient.
  • Sharing Permissions are used to manage disclosure of individual medical data items. Every data field in the patient medical history is associated with an access control field that specifies whether or not the medical data item can be disclosed to the patient, to various agents or agencies, and to other software objects with specific access authorizations. Sharing Permissions are used by the DMM Close Session process ( FIG. 18 , nodes 958 , 960 ) to decide what medical data items can be disclosed (i.e. “shared”). in its messages and reports to patients, patient agents, physicians, laboratories, pharmacies, health care management organizations, or government agencies.
  • Sharing Permissions is to prevent a diagnosis from being disclosed to the patient under circumstances when it would be inappropriate ( FIG. 18 , node 964 ).
  • TPL Therapy Alteration Permission Level
  • the Therapy Alteration Permission Level is a data set that specifies the various levels of authority the DMM has to change patient therapy.
  • the TAPL defines the degree of autonomy that the DMM has to manage a patient's disease without prior human approval.
  • the DMM consults the access control field of that data item to see which sharing permission level is required for it. Then the DMM consults the Permissions database to verify that the requesting agency has access permission at the specified level.
  • the TAPL requires DMM to notify a physician whenever the DMM determines that the patient could benefit from a change in therapy, and to obtain permission before adjusting therapy in any way.
  • the least restrictive TAPL setting allows the DMM to automatically change a patient's treatment without human intervention. TAPL settings between these extremes require various degrees of prior notification and approval for different therapeutic interventions.
  • the TAPL is used by all DMM functions that change patient therapy or give advice to that effect ( FIG. 15 , node 830 ; FIG. 16 , node 896 ).
  • Meta Data Array a system data structure used to record, track, analyze, and report medical problems can best be visualized as a two-dimensional grid or array called the Meta Data Array.
  • This array lists the causes of disease (e.g., trauma, infection, allergy) along one dimension (the abscissa or x-axis) labeled as CAUSE and lists the anatomic systems or organs affected by disease (e.g., cardiovascular, respiratory, nervous) along a second dimension (the ordinate or y-axis) labeled as ANATOMY.
  • a given disease can then be seen as the cell in the Meta Data Array that is at the intersection of the applicable Cause and Anatomy dimensions.
  • both the Cause and Anatomy axes are, of course, extensively subdivided.
  • the infection cause is subdivided into bacterial and viral; bacterial is broken down into gram positive and gram negative; gram positive is further broken down into streptococcus, and so on, to the point where the system can identify ultimate causes such as “meningococcal gram negative bacterial infection.”
  • the Anatomy dimension can obviously also be subdivided into organ structures, organs, tissues, cells, and so forth.
  • the additional patient data extends the Meta Data Array along a time dimension to form a Meta Data Cube.
  • the time axis is also referred to as the “Z” axis.
  • the Meta Data Cube is an internal data structure that supports various meta functions. The details vary, depending on which medical system module is performing which type of meta analysis, but all of the following examples apply:
  • Meta Functions are medically-oriented software objects that operate at a global level of the entire medical management system and its various modules. They observe, record, track, and analyze patient interactions with the system to:
  • Meta Functions automate that aspect of the human physician that sees a patient as a total, complex bio-mechanism that is malfunctioning and requires corrective measures over a time span. They give the DMM the powerful ability to analyze patient health as a whole, to develop long-term medical diagnoses, therapies, advice, and management strategies.
  • the Frequency Meta Function uses the Sequential Summing Meta Function to analyze the frequency of consultations regarding the same disease.
  • the Anatomic Meta Function analyzes patient complaints based on the anatomic organ system involved.
  • the Cause-Effect Chaining Meta Function traces a disease back to its cause(s) and then forward to other disease(s).
  • the Area Meta Function and the Volumetric Meta Function analyze changes in disease parameters over time.
  • the Critical Curve Meta Function monitors patient health for significant deterioration by comparing it to a standard curve for the disease being managed.
  • the Interval Meta evaluates the time intervals between consultations for the same disease.
  • the Reliability Meta assesses the probability of data reliability and integrity.
  • Meta Functions described for disease management use the same “Meta Data Cube” data structure described in Applicant's patent entitled “Computerized Medical Diagnostic and Treatment Advice System,” U.S. Pat. No. 5,660,176.
  • DM has different objectives, it examines different data elements of the cube along different axes.
  • metal refers to the overall nature of these functions, which focus on manipulating health data not at a detailed level but at a level of long-term time trends, global patterns, statistical distributions, and other summary relationships.
  • function here refers to the various computational and analytical techniques used, which employ classic and fuzzy logic, arithmetic, geometry, trigonometry, analytical geometry, calculus, statistics, probability, domain mappings, transforms (Laplace, Fourier), heuristics, recursion, and so on.
  • Meta functions are implemented and embodied in the form of suitable data and process structures such as databases, tables, arrays, modules, objects, scripts, lists, subroutines, procedures, functions, and so on.
  • the Sequential Summing (SS) Meta function detects and integrates the effect of one patient accessing separate modules of the entire medical management system, such as the diagnostic module and the DMM, because separate sessions—when combined—may represent a significant change or deterioration in the patient.
  • the SS Meta function analyzes the combined effect of the separate modules, and may make a recommendation based on this global analysis.
  • the SS Meta uses pre-set thresholds for different combinations of the system modules being summed.
  • the thresholds are contained in an internal table that lists all of the module combinations such as medical diagnosis+disease management, medical diagnosis+medical audio/video/image library, medical diagnosis+treatment table consultation, and so on.
  • the SS Meta function would use the proper values from the table at medical diagnosis+disease management+medical audio/video/image library for Asthma to calculate a threshold to trigger special recommendations.
  • threshold was not reached in any one module, when the consultations for asthma in the diagnostic, disease management and audio/video/image library consultations are combined and considered together, threshold is reached.
  • the Frequency Meta function reviews the number of times that a patient has consulted the system and makes recommendations based on that consultation frequency.
  • the function calculates how many times the patient has interacted with the system for the same complaint or disease, medical audio text consultation or treatment table consultation, uses the Sequential Summing Meta function to analyze the combined effect of the consultations, and may make a recommendation based on this global analysis.
  • a threshold is established for the number of consultations (inbound as well as outbound) per unit of time.
  • the threshold is different for each disease and is modified by the sensitivity factor set. If this threshold is reached, the Frequency Meta function makes a recommendation. That is, the fact alone that the patient has had a certain number of symptom occurrences of a given type may trigger a recommendation from the Frequency Meta functions.
  • the Interval Meta function analyzes the time intervals between each interaction for the same disease to detect trends that may signify a problem. For example, if the function were to discover that the patient's interactions with the system are occurring closer and closer together, the function could make a recommendation based on this fact alone.
  • the sequential summing series method is used.
  • the interval between consultations is plotted and a meta recommendation is made if the intervals are getting shorter
  • the Cause Meta function is a DM background task that looks for disease or cause patterns that may help to identify root causes.
  • the function monitors and analyzes the patient's use of various system modules.
  • the Cause Meta function identifies a sequential summing series in decreasing intervals of time between medical diagnosis, disease management, medical audio text library, treatment table consultation and all their combinations. For example, assume that a patient has consulted the system on several occasions with complaints manifesting in different parts of the body, and that during each session, the medical diagnosis module has (properly) attributed each separate problem to being caused by infection.
  • the Cause Meta function detects such a series of consultations, and—if they reach a preset threshold per unit time—alerts the system that the root cause may lie in the patient's immune system. If the system is caring for a patient with multiple episodes of trauma, the Cause Meta function will help the system to consider the possibility that the patient is abusing drugs or alcohol.
  • the Anatomic Meta function analyzes patient contacts with the medical system from a viewpoint of a single organ or anatomic system of the body.
  • the function looks for different diseases being managed that may impact the same anatomic system.
  • the function automates the aspect of DM that—when different diseases all affect the same organ—it is often essential to monitor and frequently measure the functioning of that organ.
  • the Anatomic Meta function recognizes that these problems all involve the gastrointestinal tract, and may cause the system to adjust its recommendations based on that additional information.
  • the Anatomic Meta function detects the need for such special monitoring. Based on some internal, preset thresholds, the Anatomic Meta analysis may cause disease management system to recommend an evaluation of the impacted organ functions. In the example above, for a patient being managed for diabetes and hypertension, the Anatomic Meta analysis could cause the medical management system to recommend a serum creatinine, a test of kidney function, at appropriate intervals.
  • the Cause vs. Anatomic Meta function coordinates an interaction between the Cause Meta and Anatomic Meta functions. As the Cause Meta and Anatomy Meta functions interact more closely, their interaction is described here.
  • the Cause/Anatomy cells are stacked along the time or Z-axis, which tracks the moment in time when intersection of the cause and anatomic system, i.e., making the diagnosis actually occurred in the patient.
  • the Meta Data Cube represents a summation of the patient's interaction with the system over time. Although much of the patient's past history is stored using ICD-9-CM codes, as well as conventional text strings in the fields of the patient's medical record, this technique allows very useful analyses to be done.
  • the system may be able to assign a cause to a problem without knowing the anatomic system involved, and that the system may indicate what organ or organ system is involved without knowing the cause of the patient's problem. For example, a six-year-old child who complains of muscle aches, headache, runny nose, and joint aching most likely has a viral infection, but it is hard to ascribe a specific organ system in which it is being manifested.
  • diabetes can be represented by or at the intersection of an endocrine and the vascular system.
  • another way to visualize the disease process in diabetes is to go one step further as follows. Whenever the medical management system realizes that another disease process (like diabetes) affects the vascular system, then “vascular” as a CAUSE of further disease is searched.
  • the Chaining Meta function automates the analysis of the medical fact that certain diseases produce pathologic changes in other organs of the body, meaning that a disease can cause and be caused by other diseases.
  • the Chaining Meta function looks at a given disease as both cause and effect, and performs three analyses for a given disease D:
  • the Chaining Meta analysis traces the total impact of disease on the body. It uses the Cause Meta function (which is used to detect the immediate, single cause of a complaint or disease) to recursively find remote causes and diseases. Given a starting disease, the Chaining Meta analysis uses the Meta Data Cube to detect patterns that let the analysis go backward in the cause chain to detect other possible problems in a patient. In this way, it does the analysis needed to detect related problems that have so far been masked or have not yet surfaced.
  • causes Meta function which is used to detect the immediate, single cause of a complaint or disease
  • An internal Cause-Effect table used by the Cause-Effect Meta function contains fundamental medical knowledge of anatomic systems, their relationships, their diseases, and disease causality chains. This table identifies patterns that need to be explored for root causes and secondary disease.
  • a second table, used in controlling the processing of the causality chains, contains other data such as probability of occurrence, seriousness of the secondary diseases, and possible therapeutic windows.
  • the result of the Chaining Meta computation is a list of diseases to check for and monitor in the current patient. These results are useful in:
  • An example of area meta can be described as plotting pain or discomfort against time and then integrating the area under the curve to look at the total amount of suffering or discomfort. This is important because many patients, particularly with incurable illness, such as terminal cancer patients, are in continuous pain but they are isolated, do not see their doctor regularly, or their physician does not appreciate how much the patient is suffering. They tend to “chase the pain,” and never catch up. Here, once a threshold of suffering as been met, the patient could get narcotic analgesics or have their dose increased.
  • the Volumetric Meta function performs analysis based on the (3-dimensional) product of Disease ⁇ Anatomy ⁇ Time and makes recommendations based on pre-set thresholds.
  • the word “volumetric” refers to the Meta Data Cube analysis method used, in which a smoking history appears as the volume enclosed by the three axes P (Poison), R (Respiratory System), and Z (Time). For example, a patient who has smoked two packs of cigarettes daily for 30 years is deemed to have a history of 60 pack-years impacting the respiratory system.
  • volumetric analysis is significant in many disease processes. Thus, the patient with a smoking volume of 60 pack-years has accumulated significant damage to the respiratory system. The longer this has been going on, the larger the volume, the more poison has impacted the functioning of the respiratory system, and the more likely certain diagnoses or therapies will be.
  • volumetric analysis is the long-term damage that diabetes causes in the microvascular circulation.
  • volumetric Meta function involves various internal disease management tables that list volumetric products for various diseases as well as their threshold parameters. These thresholds (as modified dynamically by the sensitivity factor set) control special actions and analyses of the system. When an applicable threshold is reached, the system performs special analyses and then issues internal alerts to look for possible evidence of damage being done to the applicable organ system(s) and to make special recommendations for the patient.
  • the Reliability Meta function looks at the reliability of all of a patient's data items to see if the patient's care is inadequate.
  • the function can recommend the re-evaluation of a patient if it finds that the (separate or combined) probabilities of a diagnosis are below a reliability threshold (modified by the sensitivity factor set).
  • the function uses internal Reliability Indicators, associated with every data item, that track the probability that the data item reflects the actual health of the patient at the time for which it was recorded. These Reliability Indicators are established for every data item in the medical management system when it is first established, and remain associated with it throughout its life in the system.
  • the system may ask the patient:
  • the idea is that if a headache specialist made the diagnosis after a full and complete workup including imaging (MRI) of the brain, lumbar puncture, EEG, etc., the probability that the diagnosis is correct is very high. This will be recorded in the Reliability Indicators and associated with the diagnosis data item. If the reliability is too low, the patient will be scheduled for re-evaluation at a higher level or standard of care, which will invoke more precise and more thorough questioning.
  • MRI imaging
  • EEG EEG

Abstract

A method and system for patient medication therapy self-management. The system performs medication therapy self-management in a fully automated manner, using periodic interactive dialogs with a patient to obtain health state measurements from the patient. The system and method utilizes a computer usable medium having computer readable program code embodied therein for representing a description of a pain in a digitized form allowing the patient to directly interact with the program code via the periodic dialogs. The system and method utilizes a therapy alteration permission level (TAPL) limiting the possible self-adjustments available to the patient to change the patient's therapy. Via the interactive dialogs, the patient self-selects aspect words concerning the patient's current pain allowing the program code to adjust the patient's medication therapy within the TAPL.

Description

RELATED APPLICATIONS
This application is a continuation of application Ser. No. 11/933,077 filed Oct. 31, 2007, now pending, which is a divisional of application Ser. No. 10/261,919, filed Oct. 1, 2002, which is a divisional of application Ser. No. 09/818,187, filed Mar. 26, 2001, now abandoned, which is a divisional of application Ser. No. 09/042,075, filed Mar. 13, 1998, now U.S. Pat. No. 6,234,964, which claims the benefit of provisional Application No. 60/040,522, filed Mar. 13, 1997, all of which are hereby incorporated by reference.
FIELD OF THE INVENTION
The present invention generally relates to medical knowledge systems, and more specifically, to systems for computerized long-term management of patient diseases.
DESCRIPTION OF THE RELATED TECHNOLOGY
Health is the ground upon which we lead our lives. Medicine is composed of diagnosis and treatment. Diagnosis means finding the cause of the patient's problem; treating is the application of the best therapy available. However, not all diseases can be completely cured by a treatment regime.
Diseases such as asthma and diabetes may require a regular schedule of treatment, termed therapy, for the duration of a patient's life. In this case, the disease is managed rather than cured. Disease management may be defined as managing a patient with a known diagnosis with the intention of providing patient education and monitoring to prevent symptom flare ups and acute episodes of the disease in order to eliminate costly medical intervention and promote patient well being. The therapy portion of disease management must be custom-tailored to the response of a particular patient since diseased patients may respond differently to the same treatment, e.g., a prescribed dosage and pharmaceuticals.
Since disease management creates reoccurring expenses to society, there is a tremendous desire to reduce costs. One must understand a capitated healthcare system in the extreme to see why the goal is worth achieving. Advocates of a fully capitated system say that everyone will win. Taken to the extreme no one will ever get sick, and doctors will be paid for never seeing patients because there wouldn't be any patients. In a fully capitated system, every person in the world pays a predetermined amount per person per month to health maintenance organizations whose sole purpose is to keep you healthy. This is an admirable goal, but impossible to achieve. However, a realizable goal is to automate the way diseases are managed.
The entire concept of disease management, carried to the extreme, is to visualize a doctor following a patient around for 24 hours a day. Of course, this is an unobtainable solution for the vast majority of the population. To reduce costs, the doctor's knowledge must be disseminated to the general public and one approach might be to not require the physical presence of the doctor at the site of the patient.
Much of medicine is algorithmic. That is, the diagnosis follows a sequence of steps to isolate the cause of the problem. Advanced cardiac life support (ACLS) and advanced trauma life support (ATLS) have shown how much care can be improved by setting standards. Some standards may be translated into medicinal algorithms, which can help set the standard of care for physicians. The concept of telephone medical advice has been proven by nationwide poison control centers, and physicians, particularly pediatricians, have practiced medicine over the telephone since it was invented. In fact, the very first words uttered over the telephone were an appeal for help, for Alexander Graham Bell had just spilled battery acid (for the batteries for the telephone) and said, “Come here, Mr. Watson, I need you” on Mar. 7, 1876. Today's so-called telemedicine remains a one-to-one relationship. The phenomenon of telemedicine depends, in part, on best-practice guidelines helping make the practice of medicine consistent.
Disease management is nothing less than the redesign of the practice of medicine. The problem with medicine was mostly one of information and arrangement of that information. Because of the development of the personal computer and standards, advances can now be made in disease management. In the past, doctors have been the repository of medical information and the ones to “arrange” it so that it had clinical meaning. But these functions can now be performed in an automated way using the “lever” of telecommunication and computer technologies.
Disease management can involve coordinating care for patients across the entire health care continuum from birth to death. Disease management has a program available for every part of everyone's life, including prevention, diagnosis, treatment and rehabilitation. The process involves managing not only the patient with a particular disease, but also the healthy patient. Too often, providers focuses on providing intensive and costly services to patients with acute episodes of disease. Disease management advocates seek a greater focus on preventive, comprehensive care to improve the health of the entire population. In a sense, disease management attempts to take the practice of medicine out of the hands of physicians and puts it into the hands of patients.
Almost all “knowledge based” clinical reasoning could be performed better and more reliability by computers. Technology will drive the democratization of medicine. A system that can automate the practice of medicine, especially in disease management, and which encourages and trains patients to play a major beneficial role in their medical health care is highly desired. Such a system should give a sustainable, substantive, and significant competitive advantage in a capitated health care marketplace. Such a system should be able to automatically identify very critical points in any disease process so that intervention is clinically, economically and humanistically maximized.
SUMMARY OF THE INVENTION
In one embodiment, there is an automated system for encoding a subjective experience of a patient's pain, the system comprising a software function configured to encode a subjective description of a patient's pain to represent a degree or description of pain; and a pain code array, wherein the pain code array comprises encoded numeric values representing a plurality of different aspects of subjective patient descriptions of pain.
In another embodiment, there is a computerized method for encoding a description of a patient's pain into a pain code array, the method comprising storing a set of aspect words in a data storage, wherein the aspect words correspond to an aspect of pain; receiving one or more aspect words from a patient that describe a pain of the patient; encoding the received aspect words into subcodes; and combining the subcodes into a pain code array.
In another embodiment, there is an automated method for decoding a description of pain from a pain code array, the method comprising retrieving a pain code array containing one or more subcodes from a storage location of the pain code array; and decoding the subcodes of the pain code array into subjective aspect words.
In another embodiment, there is a computer usable medium having computer readable program code embodied therein for representing a description of a pain in a digitized form for adjusting therapy, the computer readable code comprising instructions for storing a listing of aspect words describing a pain experienced by a patient; receiving a selection of an aspect word from the listing of aspect words; and converting the received aspect word into an integer subcode that represents the received aspect word.
In another embodiment, there is a computerized medical diagnosis method, comprising encoding a patient's subjective perception of pain into a pain code; and indexing a database of diseases with the pain code thereby diagnosing a disease.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram of an automated medical diagnosis, treatment, disease management and information system of the present invention.
FIG. 2 a is a diagram of a configuration of components of the system shown in FIG. 1.
FIG. 2 b is a diagram of a configuration of components of the server computer shown in FIGS. 1 and 2 a.
FIG. 3 is a block diagram of a portion of the processes and database files utilized by the system of FIG. 1.
FIGS. 4 a, 4 b, 4 c and 4 d are a flowchart of the top-level process performed by the system of FIG. 1.
FIG. 5 is a flowchart of the Disease Management Module process shown in FIG. 4 d and performed by the system of FIG. 1.
FIG. 6 is a flowchart of the Open Session process shown in FIG. 5.
FIG. 7 is a flowchart of the Health Assessment process shown in FIG. 5.
FIG. 8 is a flowchart of the Significant Symptom Filter process shown in FIG. 7.
FIG. 9 is a flowchart of the Severity Assessment function shown in FIG. 8.
FIG. 10 is a flowchart of the Initial Health Assessment process shown in FIG. 7.
FIG. 11 is a flowchart of the Current Health Assessment process shown in FIG. 7.
FIG. 12 is a flowchart of the Correlation Assessment function shown in FIG. 11.
FIG. 13 is a flowchart of the Critical Curve Assessment process shown in FIG.
FIG. 14 is a flowchart of the Therapy Optimization process shown in FIG. 5.
FIG. 15 is a flowchart of the Therapy Adjustment Based on Subjective Health Data process shown in FIG. 14.
FIG. 16 is a flowchart of the Therapy Adjustment Based on Objective Health Data process shown in FIG. 14.
FIG. 17 is a flowchart of the Patient Consent Level function shown in FIGS. 15 and 16.
FIG. 18 is a flowchart of the Close Session process shown in FIG. 5.
FIGS. 19 a and 19 b are flowcharts of the Question Versions feature utilized by the Disease Management Module process shown in FIGS. 1 and 5.
FIG. 20 is a flowchart of the Preview Mode feature utilized by the Disease Management Module process shown in FIGS. 1 and 5.
FIG. 21 is a flowchart of the No-Response feature utilized by the Disease Management Module process shown in FIGS. 1 and 5.
FIG. 22 a is a flowchart of a function utilized by the Disease Management Module process shown in FIGS. 4 d and 5 and/or the Diagnostic process shown in FIG. 4 d in generating a PQRST (pain code) array entry for a patient.
FIG. 22 b is a flowchart of a function utilized by the Diagnostic process shown in FIG. 4 d in retrieving a diagnosis using the PQRST (pain code) array entry stored for a patient in FIG. 22 a.
FIG. 23 is a graph of an exemplary critical curve plotting health measurements over time for a particular disease.
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT
The following detailed description of the preferred embodiments presents a description of certain specific embodiments to assist in understanding the claims. However, the present invention can be embodied in a multitude of different ways as defined and covered by the claims. Reference is now made to the drawings wherein like numerals refer to like parts throughout.
The detailed description is organized into the following sections:
1. System Overview
2. System Processes and Databases
3. Top-level System Process Flow
4. Disease Management Overview
5. Disease Management Module
6. Open Session
7. Health Assessment
8. Significant Symptom Filter
9. Severity Assessment
10. Initial Health Assessment
11. Current Health Assessment
12. Correlation Assessment
13. Critical Curve Assessment
14. Therapy Optimization
15. Therapy Adjustment (Subjective)
16. Therapy Adjustment (Objective)
17. Patient Consent Level
18. Close Session
19. Question Versions
20. Preview Mode Feature
21. No-Response Feature
22. The PQRST Array
23. Disease Management Order (DMO)
24. Permissions Database
25. Regulatory Permissions
26. Sharing Permissions
27. Therapeutic Alteration Permission Level (TAPL)
28. Meta Structures
29. Meta Functions
30. Benefits of Disease Management
System Overview
Referring to FIG. 1, a computerized knowledge-based medical management system 100 will be described. A disease management module (DMM) 80 and several other high-level service modules 82 perform automated medical services for the users of the medical management system 100. The service modules 82 may include Diagnosis, Treatment Table, Automated Demand Management, Audio/Visual/Image Library, and Author Access. The DMM 80 handles tasks associated with Disease Management (DM); its major goals are to promote patient well-being, to educate patients, and to reduce costly medical intervention. The user may be a patient 114 or an assistant for a patient. Throughout this document, the words user and patient are used interchangeably. However, it will be understood that the user may be acting as a proxy for the patient. If this is the case, the user is registered as an assistant for the patient. Appropriate registration and login processes, described herein below, are utilized by the system 100 for either the patient or the assistant.
The modules 80 and 82 are supported by an Operating System and support software 88, by a number of databases 84, and by a computing environment 90 of an embedding computer hardware platform 110. The entire computer hardware-software-communications complex is operated and maintained by a support staff All application tasks of the DMM 80 are fully automated. External contact of the DMM with patients, physicians, clinics, pharmacies, laboratories, and so on (collectively 92) are handled by automated communications systems using appropriate media and methods of the computing environment 90, such as interactive voice response (IVR), direct modem-to-modem access, or access via the Internet 102. The patient 114 utilizes a computer 116 and monitor 118, a telephone 124, or other components, some of which are described in conjunction with FIG. 2 a below, to communicate with the system computer platform 110.
Referring to FIG. 2 a, a block diagram of one embodiment of the medical management system 100 will be described. The system 100 includes a network “cloud” 102, which may represent a local area network (LAN), a wide area network (WAN), the Internet, or another connection service.
The system programs and databases may reside on a group of servers 108 that are preferably interconnected by a LAN 106 and a gateway 104 to the network 102. Alternatively, the system programs and databases may reside on a single server 110 that utilizes network interface hardware and software 112. The system servers 108/110 store the modules 80 and 82 (FIG. 1).
The network 102 may connect to a user computer 116, for example, by use of a modem or by use of a network interface card. The user 114 at the computer 116 may utilize a browser 120 to remotely access the system programs using a keyboard and/or pointing device and a visual display, such as the monitor 118. Alternatively, the browser 120 is not utilized when the system programs are executed in a local mode on the computer 116. A video camera 122 may be optionally connected to the computer 116 to provide visual input, such as visual symptoms or signs. Furthermore, clinical sounds could be picked up by the video camera or separate microphone (not shown).
Various other devices may be used to communicate with the system servers 108/110. If the servers are equipped with voice recognition or DTMF hardware, the user can communicate with the system program by use of the telephone 124. A telephonic embodiment is described in Applicant's application entitled “Computerized Medical Diagnostic and Treatment Advice System,” U.S. application Ser. No. 08/176,041, filed Dec. 29, 1993, which has issued as U.S. Pat. No. 5,660,176, and is hereby incorporated by reference. Other connection devices for communicating with the system servers 108/110 include a portable personal computer 126 with a modem or wireless connection interface, a cable interface device 128 connected to a visual display 130, or a satellite dish 132 connected to a satellite receiver 134 and a television 136. Other ways of allowing communication between the user 114 and the system servers 108/110 are envisioned.
Referring to FIG. 2 b, a diagram of one embodiment of a server computer 110 shows several possible interconnections to the network. To “play” a script, a special program called a Script Engine is used, which reads a medical diagnostic script file and uses its codes to perform interview actions, such as outputting a question to a patient and inputting an answer. The scripts may also collect the answers from the patient, evaluate the answers, issue a diagnosis, and update the patient's medical record. The script engine may also reside in the user computer 116 (FIG. 2 a). The script engine may be stored on the hard drive or a CD-ROM, and is loaded into the main memory or a cache for execution.
The components of a presently preferred server computer 110 of the computerized medical system 100 of the present invention, are shown in FIG. 2 b. The server computer 110 includes a plurality of components within an enclosure. A telephone line 156 interfaces the public telephone network 158 to the computer 110 via a modem 160. The telephone network 158 may connect to the network 102, which has connections with the system server(s) 108/110. Alternatively, the computer 110 may connect to the network 102 by use of a network interface card 164.
The hardware and system software are assembled with two basic concepts in mind: portability to other operating systems and the use of industry standard components. In this way, the system can be more flexible and will allow free market competition to continually improve the product, while, at the same time, decreasing costs. While specific hardware and software may be referenced, it will be understood that a panoply of different components could be used in the present system.
The computer 110 preferably is a personal computer with an Intel Pentium microprocessor 170. Other computers, such as an Apple Macintosh, an Amiga, a Digital Equipment Corporation VAX, or an IBM mainframe, could also be utilized. The modem 160 or the network interface card 164 connects to an industry standard architecture (ISA) or a peripheral component interconnect (PCI) bus 162. The bus 162 interconnects the microprocessor 170 with a plurality of peripherals through controller circuits (chips or boards).
The computer bus 162 has a plurality of peripherals connected to it through adapters or controllers. A video adapter board 172, preferably at SVGA or better resolution, interconnects to a video monitor 118. A serial communication circuit 176 interfaces with a pointing device, such as a mouse 178. A parallel communication circuit may be used in place of circuit 176 in another embodiment. A keyboard controller circuit 180 interfaces with a keyboard 182. A 500 Mb or greater hard disk drive 184 and an optional CD-ROM drive 186 are preferably attached to the bus 162. The hard disk 184 stores database files such as the patient files, DM files, other system files, and binary support files. The CD-ROM drive 186 also stores database files and binary support files.
A main memory 190 connects to the microprocessor 170. In one embodiment, the computer 110 may operate under the Windows 95 operating system 192. The memory 190 executes a diagnostic script engine (not shown) and a disease management module (DMM) process 220. Portions of the disease management module process software may be written in Borland Delphi Pascal, version II, and other portions may be written in Microsoft ‘C’, version 7.0. Furthermore, in one embodiment, the database is implemented with Microsoft Foxpro or another database program such as a SQL-compatible relational database program.
System Processes and Databases
Referring to FIG. 3, a portion of the processes, files, and databases utilized by the medical management system 100 will be described. Except for the DMM process, a Permissions database, an Imaging Modality database, a Laboratory Test database, a Diseases database, and other DM specific databases which are described herein below, these processes, files, and databases were described in Applicant's patent entitled “Computerized Medical Diagnostic and Treatment Advice System,” U.S. Pat. No. 5,660,176.
The medical management system 100 utilizes several principal processes and related databases. A set of patient/assistant login processes 200, 210 and 212 is used by the system 100 to identify a patient who has previously registered into the system in one of three ways: 1) by prompting for a patient identification number (PIN) in process 200; 2) identify an assistant who has previously registered into the system by prompting for an assistant identification number (AIN) in process 210; or 3) identify a patient, having an assistant, who has previously registered into the system by prompting for the patient identification number in process 212. One of a set of processes 202, 214 or 216 is used to register a patient or assistant. If the user is the patient, a patient registration process is used by the system to register new or first-time patients in process 200. If the user is not the patient, an assistant registration process is used by the system to register new or first-time assistants in process 214. Then, if the patient is not already registered, an assisted patient registration process is used by the system to register the patient in process 216.
Once a user has logged in or registered, the system provides a choice of processes. The primary process of concern in the current embodiment is the DMM process 220 that manages a disease or condition of the patient. The DMM process 220 may access the laboratory test of choice database 260 or imaging modality of choice database 258 in the course of disease management and a treatment table 250 to obtain current treatment information for a particular disease or diagnosis. Associated with these processes are a patient and assistant enrollment database 240, a consultation history database 242, a patient response database 244, a medical history objects database 246, a patient medication database 248, a pending database 252, and a patient medical history database 254. These databases include an electronic medical record for each patient that is registered with the medical system 100. The electronic medical record contains all the information about each patient. A permissions database 256, a diseases database 262 and other DM specific databases 264 will be described herein below. In another embodiment, other choices are added to access other medical information processes.
Top-Level System Process Flow
Referring to FIGS. 4 a, 4 b, 4 c and 4 d, the top level flow 300 of the medical management system software will be described. A telephone number used to access the system 100 via the telephone may vary in various embodiments of the system. If the sponsoring agency or hospital wishes to provide access to the medical management system 100 at no cost to the caller, then a toll-free (e.g., 800, 888 or other number) service number can be used. If the sponsoring agency or hospital wishes to recover the costs of running the system 100 from the caller, it may use a pay-per-call or premium charge number (e.g., 900 service). “Current Procedural Terminology” (CPT-4) codes are available to describe and bill third party payers for telephone consultations. They are a listing of the descriptive terms and identifying codes for reporting medical services and procedures. CPT-4 codes are the most widely accepted nomenclature for reporting physician services to insurance companies. If access is provided to the system 100 via the Internet or other network, an appropriate web address (or addresses) is provided to the user.
Beginning at a start state 302, the user 114 (FIG. 1) desiring medical advice dials the telephone number for the system 100 on the telephone 124 (FIG. 2 a). The user may be the patient or may be an “assistant”, e.g., parent, relative, or friend, that is helping the patient. Alternatively, the user may access the system 100 though the user computer 116, such as through the Internet as previously described. Moving to state 304, the system 100 answers the call automatically and greets the caller 114 with an introductory greeting message by playing back a speech file stored on the system hard drive by use of a voice processing board, such as a D/41D available from Dialogic. Alternatively, if the user is using the browser 120 (FIG. 2 a) or other user interface on the Internet 102, a greeting message is displayed to the user on the visual display 118. Thus the system 100 communicates with the user 114 either by the telephone or by messages displayed on the visual display. Subsequent steps in the process or function flowcharts will only describe one form of user communication for brevity purposes.
Proceeding at state 306, the system 100 asks each patient who calls the system a series of “initial screening questions.” These questions are designed to identify patients who are critically ill; they are not designed to identify the patient's problem. The initial screening questions enable the system to filter out patients who require immediate medical attention.
Moving to decision state 308, any patient found to be critically ill is instructed to dial the emergency response telephone number “911” at state 309 or will be automatically connected to the nearest emergency medical services system in the patient's area. The session is terminated by process 300 at state 310. The following are examples of initial screening questions:
? IS THIS A MEDICAL EMERGENCY?
? ARE YOU HAVING DIFFICULTY BREATHING?
? ARE YOU EXPERIENCING SEVERE PAIN OR PRESSURE IN YOUR CHEST?
If the system determines that the patient is experiencing a medical emergency, it may provide the patient with a menu of emergency medical procedures at state 311. In situations where the patient or the caller for the patient is far from the nearest emergency help, e.g., a rural setting, the user may need to initiate emergency procedures immediately. The menu of emergency medical procedures provides several choices to the user. If the user presses touch tone key “1” or speaks the word “one” into the telephone mouthpiece, process 300 branches to state 312 wherein well known CPR (cardiopulmonary resuscitation) information is recited. If the user has a speakerphone capability associated with the telephone 124 being used, the user may be able to listen to and perform the instructions given by the system 100 in a hands-free manner away from the telephone. If the caller presses touch tone key “2” or speaks the word “two” into the telephone mouthpiece, process 300 branches to state 313 wherein well known Heimlich Hug information for choking is recited. At the completion of either state 312 or state 313, the session ends at state 314.
If the patient is determined at state 308 not to have a medical emergency, i.e., the system 100 is satisfied that no immediately life threatening condition is present, process 300 moves to a decision state 315 to determine if the user is the actual patient. If so, process 300 proceeds to a decision state 316 to determine if the patient has previously registered or ever consulted with the system 100, i.e., is not a new or first-time caller. If so, the system 100 verifies the patient's identification and retrieves their medical record at the patient login process 200. At the completion of process 200, process 300 proceeds through off-page connector C 317 to state 344 (FIG. 4 d). If the patient is not registered, as determined at decision state 316, the system 100 proceeds to the patient registration process 202 for a new patient. At the completion of process 202, process 300 proceeds through off-page connector C 317 to state 344 on FIG. 4 d.
If the user is not the patient, as determined at state 315, process 300 proceeds through off-page connector A 318 to a decision state 320 on FIG. 4 b. There will be times when the patient may not be able to use the system 100 directly, e.g., due to injury, weakness or altered level of consciousness. In these cases, an “assistant” may interact with the system on behalf of the patient.
An assistant registers with the system through the assistant registration process 214. The assistant registration record is identical to the patient registration record in structure, but three fields have special significance for an assistant: ASST_PERM, ASST_EXP, and RELATIONS. The ASST_PERM field is a Boolean flag that can only be set true off-line by the system administrator who has verified, through separate means, that a relationship exists between a patient and an assistant. The relationships are one-to-many, i.e., a patient may have one or more assistants, and an assistant may be related to more than one patient. The ASST_PERM flag may also be constrained by the ASST_EXP field, which contains a timestamp for the expiration of the ASST_PERM attribute. If the ASST_PERM flag is true, then the RELATIONS pointers will point to one or more patient records for whom this assistant is a “permanent assistant;” otherwise the RELATIONS field will be empty.
The medical information gathered during an assisted consultation is written to the patient's medical record if the following three conditions are met:
(a) the assistant's ASST_PERM flag is True
(b) the ASST_EXP timestamp has not been reached
(c) the assistant has a relationship pointer to the patient record
If any of these conditions are not met, then any new medical information gathered on this patient will be saved to the Pending file 252 (FIG. 3) for off-line verification by the system administrator.
The system 100 establishes at state 315 whether the user is the patient, or an assistant. If the user is not the patient, then the system asserts that the user is an assistant and, at decision state 320, determines if the assistant is registered. If the assistant is not already registered with the system, the system enrolls the new assistant at the assistant registration process 214. If the assistant is already registered with the system 100, process 300 performs the assistant login process 210. At the completion of either process 214 or process 210, process 300 advances to a decision state 321.
If the patient is not already registered with the system 100, as determined at decision state 321, then the system allows the assistant to register a new patient at the assisted patient registration process 216. However, if the patient is already registered with the system 100, as determined at state 321, process 300 performs the assisted patient login process 212. At the completion of process 216 or process 212, process 300 proceeds through off-page connector B 327 to a decision state 334 on FIG. 4 c.
At decision state 334, process 300 determines if the patient's date of birth is in the patient's medical record. If so, process 300 proceeds through off-page connector C 317 to state 344 on FIG. 4 d. If not, the system 100 attempts to get the patient's date of birth. Moving to state 335, the system 100 asks the assistant if the patient's date of birth is known. If so, process 300 advances to state 336 to request the patient's date of birth. At state 337, the system 100 recites the patient's date of birth obtained at state 336. At a decision state 338, the assistant determines if the date of birth is correct as recited by the system 100. If not, process 300 loops back to state 336 to request the patient's date of birth again. If the patient's date of birth is correct, as determined at state 338, process 300 flags the date of birth for saving in the patient's medical record at state 339, and proceeds to state 344 on FIG. 4 d.
If the patient's date of birth is not known, as determined at state 335, process 300 proceeds to state 340 wherein the system requests the assistant to provide an approximate age of the patient. The age is an important parameter used by the DMM process 220, the diagnostic module and the treatment table 250. At state 341, the system 100 recites the patient's approximate age obtained at state 340. At a decision state 342, the assistant determines if the age is correct as recited by the system 100. If not, process 300 loops back to state 340 to request the patient's approximate age again. If the patient's approximate age is correct, as determined at state 342, the system 100 advises the assistant at state 343 to get the patient's actual date of birth before the next consultation, and proceeds to state 344 on FIG. 4 d. The system 100 uses the approximate age in the session during the diagnostic module and the treatment table 250.
At state 344 on FIG. 4 d, the system 100 presents the user with a system selection menu. Here, the caller is asked to select from among six choices: diagnostic system, treatment table, disease management, audio/visual/image library, automated demand management, or end session as described below:
    • A. Diagnostic System: The system starts an evaluation process 280 at a menu, where it asks the patient to begin identification of the complaint.
    • B. Treatment Table: The system takes the patient to the treatment table process 250 at a menu, where it asks the patient to select a treatment selection method.
    • C. Disease Management: The system starts the DMM process 220 where it first determines if the patient has previously used the Disease Management Module. This process is described in detail below.
    • D. Audio/Visual/Image Library: The system starts a Audio/Visual/Image Library process 282 which lets a patient hear medical sounds, see medical videos, or see medical photographs or other images.
    • E. Automated Demand Management: The system starts an Automated Demand Management process 284 to help the patient determine if a physician should be seen, and if so, who should be seen and when they should be visited.
    • F. End Session: The system performs several steps and then terminates the session.
At the exit point of the evaluation process 280, the system 100 gives the patient the option of selecting another complaint. At the end of the treatment table process 250, the system gives the patient the option of selecting another treatment. At the end of the audio/visual/image library process 282, the system 100 gives the patient the option of selecting another audio clip, video, or image. At the end of the automated demand process 284, the system 100 gives the patient the option of receiving advice for another problem.
At the completion of the evaluation process 280, the treatment table process 250, the disease management module process 220, the audio/visual/image library process 282, or the automated demand management process 284, the system 100 loops back to state 344 and again provides the system selection menu for the user. If the user chooses the End Session selection at state 344, the system 100 moves to a decision state 345. At decision state 345, the system 100 determines if process 280, process 250, process 220, or process 284 did not occur in Information mode, i.e., did occur in either Real mode or Pending Mode, and examines a symbol table associated for the current patient to determine if any of the configured memory variables are past medical history conditions that need to be saved to the patient's medical history file. If both conditions are true at state 345, the system 100 advances to a decision state 346 to determine if the consultation is being performed in Real mode. If not, the consultation is being performed in Pending mode, and the system 100 then writes any new patient information obtained during the consultation to the Pending file 252 at state 347.
If decision state 346 proves to be true, i.e., Real mode, for each past medical condition that needs to be saved, the system 100 asks the patient at state 348 to grant permission to save the datum to the patient's medical history file and to confirm that the datum is correct. For example, during a consultation for cough, the system 100 may have learned that the patient has been diagnosed as being HIV positive. The system 100 will ask, “May I record the information about your HIV diagnosis in your medical record?” If the patient responds “yes”, then the system 100 will ask, “Please verify that your diagnosis for HIV was positive, is this correct?” If the patient responds “yes”, then the system 100 writes the diagnosis, and a score indicative of system accuracy to the patient's medical history file. After confirmation, each data item is stored in the patient's file in the patient medical history database 254 (FIG. 3).
At the completion of either updating the patient medical history database 254 at state 348, or state 345 proves to be false, or at the completion of state 347, the process 300 moves to a decision state 349. Before the system 100 ends the consultation with the patient, it presents a summary of all the advice it has given. In a telephonic session, the patient is asked to write down and repeat back the key points. The system 100 then gives the patient the option of receiving a summary of the consultation session and specific recommendations provided by the system via facsimile, electronic mail (E-mail) or a mail service, such as first-class mail. If a fax or E-mail is desired, process 300 moves to a decision state 350 to determine if information to send the summary and recommendations is available in the system. If not, process 300 asks the patient for the information, e.g., a fax number, E-mail address or mail address, at state 352. The patient also has the option to send a summary of the consultation to his or her health care provider or specialist. Proceeding to state 351, process 300 adds the transcript of the current telephone session to a fax queue or an E-mail queue, as desired, for subsequent transmission. At the completion of state 351 or if process 300 determined at state 349 that the session transcript was not to be sent, the session is terminated at state 353.
Disease Management Overview
The present invention includes a computer program called a Disease Management Module (DMM). The disease management module is one of several high-level service modules that perform automated medical services for the users of the medical management system 100. In this context, disease management (DM) means the continuing medical care of a patient who has been diagnosed with a specified health problem called a disease. The DDM may continue care throughout a patient's lifetime. The DMM performs disease management in a fully automated manner, using periodic interactive dialogs with the patient to obtain health state measurements from the patient, to evaluate and assess the progress of the patient's disease, to review and adjust therapy to optimal levels, and to give the patient medical advice for administering treatment and handling symptom flare-ups and acute episodes of the disease. The goal of the disease management module is to promote patient health in an automated manner that reduces costly medical intervention.
Various features of the DMM software are specifically designed to accumulate and use patient-specific information, so that disease management can be tailored more to each individual case. As the module manages a given patient over time, it builds a profile of the case, in the form of the frequency and reasons for the patient's contacts with the DMM, the patient's subjective understanding of the disease, the patient's objective response to various medical treatments, and the patient's preferences in treatment. The module then uses that knowledge to adjust its internal procedures, so that they adapt more to the specific patient.
When a patient is first admitted to DM, the DMM runs a registration procedure that verifies the patient's medical history, initializes the initial therapy for the patient's disease, and sets up a schedule for patient contacts. For every registered DM patient, the DMM conducts periodic automated sessions with the patient. During each session, the DMM obtains and updates the patient's medical history with the latest health measurements, analyzes and assesses patient health as needed, adjusts therapy as needed, and gives the patient appropriate medical advice. At the end of each session, the DMM schedules the next session. Ultimately, the DMM discharges patients by moving them from the disease management state to another state such as to the medical care of a human physician, to the care of the diagnostic module of the medical system, or to a normal health state with the appropriate follow-up health checkups.
The DMM module is now summarized here in terms of its overall features, so as to put the features into the overall context. Each feature will be further described herein below.
In all of its contacts with patients, the DMM must insure that it complies with a large number of permissions, consents, and authorizations granted by various agents and agencies. The DMM uses the Permissions database to manage these control data.
To conduct online interactive dialogs with patients (or their agents), the DMM uses scripts. Scripts are special computer programs capable of outputting text and questions to a patient, waiting for a response from the patient, recording the response, and taking further action based on the response. The development and use of scripts has been described in U.S. application Ser. No. 08/893,402, filed Jul. 11, 1997, issued as U.S. Pat. No. 5,935,060, entitled “Computerized Medical Diagnostic and Treatment Advice System including List Based Processing”, and in U.S. application Ser. No. 08/893,912, filed Jul. 11, 1997, issued as U.S. Pat. No. 6,022,315, entitled “Computerized Medical Diagnostic and Treatment Advice System including Network Access”, both of which are hereby incorporated by reference.
A normal online dialog with a patient takes the general form of a sequence of questions asked by a script, and answers provided by the patient. As the script runs, it considers the patient's current status, selects a question, and presents the question to the patient. The patient responds, the script analyzes the response, selects another question, and so on until the session is normally terminated.
A script Preview Mode for the DMM allows the patient to answer a question in a “look ahead” mode, to see what the consequences of a given response would be, without formally selecting the response. Abnormal script terminations can be handled by the DMM in an intelligent, proactive manner using a No-Response function. If a patient suddenly fails to respond in the middle of a dialog, this function can use all that is known about the patient, the patient's location, and the disease being managed to respond proactively, including—if necessary—the ability to contact the patient's nearest emergency assistance facility or to call 911 for the patient.
The DMM performs all of its contact with patients in the form of Disease Management sessions, which are regularly scheduled, online dialogs with the patient. A DM session can be initiated by either the patient calling the medical system (inbound), or by the system calling the patient (outbound). Every DM session consists of four major tasks performed in the following sequence: Open Session, Health Assessment, Therapy Optimization, and Close Session.
The Open Session task initializes data and registers patients. The task uses the patient's health history and the disease being managed to establish the assessment health parameters that are to be measured and tracked, including relevant thresholds, limits, ranges, and critical values. It also gives patients instructions on how to observe symptoms, perform health measurements, assess their health, and prospectively trend their disease.
The Health Assessment task obtains health measurements from the patient for the interval since the last session, encodes symptom descriptions using a PQRST Array, and calculates various relevant health counts, patterns, and trends. It analyzes health state using a Correlation Assessment function and a Critical Curve Assessment function. The Correlation Assessment function uses a Subjective-Objective Correlation Factor (SOCF), a statistical measure of how well a given patient can assess his/her own disease state and progress, to assess the patient's health based on subjective data. The PQRST Array is an encoding scheme used to convert subjective descriptions of pain symptoms into a DMM-wide digitized pain code. The Critical Curve is a time-plot of specified health parameters that the DMM can compare to standard critical curves to detect or predict rapid deterioration of patient health.
Finally, the Health Assessment task decides what action to take for the patient, such as referring the patient out of the system, to seek human medical attention; or referring the patient to the diagnostic module process for diagnosis of a new symptom; or proceeding to the next task to determine the next therapy step for the patient.
The third task of the DM session is Therapy Optimization, whose express goal is to adjust therapy step by step in a manner that balances the risks and benefits, maximizes efficacy and minimizes adverse side effects, and converges to an optimum therapy for this patient over the long term. The task selects one of several possible therapies from a treatment table, adjusts dosages in small steps as controlled by a Patient Consent Level function, presents the risks and benefits to the patient, and lets the patient accept or reject the recommendation. If the patient rejects, the task computes the next best therapy, and the next, until it reaches a limit that is stored in the Permissions database. In all of its work, the task consults a Therapeutic Alteration Permission Level (TAPL) to determine how much authority it has to modify therapy automatically. If the task has too little authority to recommend a therapy, or if the patient rejects all therapy suggestions, the task refers the patient to a human physician.
The final task of the DM session, Close Session, stores all of the assessment measurements, parameters, and decision factors in the patient's medical history database. The task also processes the therapy changes that the patient accepted, issues relevant instructions to the patient, and finally reschedules the patient for the next session. Then the task initiates processes to output various session logs and reports requested during the session, and finally, the DMM saves the relevant data and terminates the current DM session. The DMM is now done with this patient until the next session repeats the process.
Disease Management Module
Referring to FIG. 5, the process 220 will be described. Process 220 comprises the executable portion of the Disease Management Module (DMM), which conducts an on-line, interactive dialog with a patient for the purpose of managing a known disease of the patient. Process 220 consists of four processes 404, 406, 408, and 410. A DM session starts when control is passed to program 220 at the start node 402. From the start node 402, process 220 invokes process 404, which performs initialization, file opening, and registration functions as described in conjunction with FIG. 6 below. When process 404 returns control to process 220, process 220 next invokes process 406, which inputs health measurements from the patient, analyzes them, and assesses the patient's current health state. When process 406 returns control to process 220, process 220 next invokes process 408, which computes an optimum next therapy step that is accepted by the patient. When process 408 returns control to process 220, process 220 next invokes process 410, which outputs various reports, saves session data, and closes working files. When process 410 returns control to process 220, process 220 passes control to step 412. Step 412 returns control to the process that invoked process 220 at node 402.
Open Session
Referring to FIG. 6, the process 404 will be described. Process 404 establishes the data needed to conduct a DM session. It registers patients that are new to the DMM and loads existing data for patients that have previously conducted DM sessions. Finally, process 404 creates a Disease Management Order(DMO) record, in which the cumulative decisions made by the DMM during this DM session are stored. The DMO is further described in section Disease Management Order. Process 404 receives control at the start node 430. Next, process 220 passes control to decision 432, which looks up the patient's identification in the DM register to see whether the patient is a registered, i.e. has conducted previous DM sessions. If the patient is not registered, process 404 passes control to step 434, otherwise to step 452, which will be described later in this section.
Step 434 is the first of seven successive steps 434, 436, 438, 440, 442, 444, 446 that register a patient for Disease Management. Step 434 outputs messages to greet and inform the patient that s/he is about to begin registration for DM. Next, step 436 inputs the name of the disease to be managed. Next, step 438 interviews the patient to input data required to conduct Disease Management, including the name of a representative that can speak for the patient, the name and location of the patient's physician, names and telephones emergency facilities near the patient, and so on. Next, step 440 creates a record for the new patient in the DM registry. Next, step 442 establishes the patient as a registered DM patient. Next, step 444 creates a new data record for use by the DMM in the patient's database. Next, step 446 creates a new data record for session data in the session database. Step 446 completes the registration of the patient as a new DM patient. After step 446, control goes to step 448, which creates a new creates a Disease Management Order (DMO) record, in which the cumulative decisions made by the DMM during this DM session are stored. Step 448 initializes the DMO to indicate that this patient is a newly registered DM patient and needs an initial health assessment. After step 448, process 404 passes control to step 450, which returns control to the process that called process 404.
Continuing now to describe process 404 at step 452. Step 452 retrieves the patient's medical record from the patient database. After step 452, control passes to step 454, which loads the last DM session data for this patient from the session database. After step 454, control passes to step 456, which confirms that the last session terminated normally and sets appropriate control data if it did not. After step 456, control passes to step 458, which initializes the DMO to indicate that this patient needs a current health assessment in subsequent processing. After step 458, control passes to step 450, which returns control to the process that called process 404.
Health Assessment
Referring to FIG. 7, the process 406 will be described. Process 406 performs the health assessment for the DM session. It is basically a staging process that invokes other processes that perform health assessment of the patient. Process 406 receives control at start node 480. After node 480, process 406 invokes process 482, which is named the Significant Symptom Filter and will be described below in conjunction with FIG. 8. When process 482 returns control, process 406 passes control to the test 484, which tests the DMO record code to determine whether this patient is a new DM registrant or a returning DM patient. For new patients, process 406 invokes node 488, which assesses the health of newly registered patients and will be described below in conjunction with FIG. 10. For current patients, process 406 invokes node 490, which performs the health assessment for returning DM patients and will be described below in conjunction with FIG. 11. After health assessment for new or returning patients is completed, process 406 returns control at node 492.
Significant Symptom Filter
Referring to FIG. 8, the process 482 will be described. Process 482 applies several tests to the patients current symptoms to classify the patient's current health state, decide on specific assessment needs and their reasons, and forward this assessment to subsequent DM processes. These needs are saved in the patient's DMO, which is then processed by subsequent DMM routines. The DMO record is described later in section Disease Management Order.
Process 482 receives control at start node 510. From there, it passes control to test node 512, which represents the first filter by asking the patient whether s/he is having any significant symptoms at present. If the patient is not having significant symptoms, s/he can be assessed by automated means, and therefore process 482 passes control to step 544. Step 544 which sets the DMO record code to indicate that this patient's health needs to be further assessed by subsequent routines. The control returns via node 526.
If, at node 512, the patient is currently having significant symptoms, then process 482 needs to determine whether or not the patient has a symptom related to the disease being managed. To do this, process 482 passes control first to step 514, which inputs the symptom from the patient and looks it up in a table of related symptoms, and next to test 516, which branches to node 520 if the symptom is related to the disease being managed, and branches to node 530 otherwise. This completes the second filter, which has now identified patients with and without significant related symptoms.
If, at node 516, the patient does have a related symptom, process 482 invokes the Severity Assessment function 520 to further classify the related symptom as mild or severe. For patients with severe related symptoms, process 482 passes control to step 522, which sets the DMO record to indicate the findings so far. From step 522, control returns via node 526. But if at test 520, the symptom is judged to be mild, then process 482 passes control to node 524, which sets the DMO record to indicate need for normal health assessment. From node 524, process 482 returns control via node 526.
If, at node 516, the patient does not have a related symptom, process 482 needs to determine whether or not the patient has a side effect related to the current therapy of the patient. To do this, process 482 passes control first to step 530, which looks up the patient's symptom in a table of side effects of the current therapy. Process 482 next passes control to test 532, which is a filter that determines side effect symptoms. If the patient's symptom is a side effect, process 482 invokes the Severity Assessment function 520 to classify the side effect as mild or severe. For mild side effects, process 482 passes control to node 536, which sets the DMO record to be assessed by subsequent processing. For severe side effects, process 482 passes control first to step 534, which marks the DMO record to refer the patient out of the system to a human physician, and then returns to the calling process via node 526.
If, at test 532, the patient's symptom is not a side effect, the symptom is a significant symptom unrelated to either the disease being managed or to the therapy being applied. Process 482 invokes the Severity Assessment function 520 to classify the symptom as mild or severe. For mild symptoms, process 482 passes control to node 542, which sets the DMO record flag to force a special discussion with the patient after all DM processing is performed, and notes the reasons for the discussion. Then process 482 passes control first to node 544 which sets the DMO record to force subsequent health assessment and next to node 526, which returns to the process that called process 482. For severe unrelated symptoms, process 482 passes control first to step 540, which marks the DMO record to refer the patient out of the system to a human physician, and then returns to the calling process via node 526.
Severity Assessment
Referring to FIG. 9, the Severity Assessment function 520 will be described. This function uses a number of criteria to decide whether a given symptom is to be considered mild or severe for the DM assessment purposes. Function 520 receives control at start node 560, where it begins a sequence of 6 consecutive steps and then returns the computed result. First, function 520 passes control to node 562, which asks the patient to rank the symptom's severity on a scale of 0 to 10. Next, function 520 passes control to node 564, which obtains the absolute severity scale of the symptom itself from the symptoms database. Different symptoms have different severity scales, and the patient's ranking is now matched to that of the symptom. Therefor, next, function 520 passes control to node 566, which normalizes the patient's ranking, so that it is expressed in terms of the symptom's severity scale. Next, function 520 passes control to node 568, which uses the Sensitivity Factor Set to adjust the normalized severity ranking up or down, depending on the current sensitivity setting of the DMM. Thus, the higher the Sensitivity, the more conservative the system is in its assessments. At the lowest Sensitivity setting, all symptoms severity ratings will be considered mild. Next, function 520 passes control to node 570, which converts the final adjusted ranking into 2 classifications, mild or severe. It is important to note that this final step can, in other contexts, classify the final ranking into any number of gradations; but for the current assessment purpose, the symptom must be classified as mild or severe. Next, function 520 passes control to node 572, which returns a code for either “mild” or “severe” to the calling process.
Initial Health Assessment
Referring to FIG. 10, the process 488 will be described. This process performs a health assessment for patients who are having their first Disease Management session. Process 488 receives control at node 600. Process 488 then passes control to node 602, which loads the health assessment specifications for the disease being managed from the disease database. These specifications include various parameters to be used in Disease Management sessions, such as patient instructions, choices of therapies, permissions required, and so on. After these values are obtained, process 488 passes control to node 604, which initializes a DM session segment in the patient's medical history and the sessions database. Then, process 488 passes control to node 606, which conducts an initial health interview to ask the patient for a subjective assessment of current health, for any objective health measurements the patient may have available, any pre-existing therapy or side effects, and so on. Then process 488 passes control to node 608, which returns control to the calling process.
Current Health Assessment
Referring to FIG. 11, the process 490 will be described. This process obtains current health data from the patient in three forms: subjective (i.e. as perceived or felt by the patient), objective (i.e. as measured by the patient, typically with an instrument), and side effects noted by the patient. These health measurements are then used to analyze the current health state. Process 490 receives control at node 620. From node 620, process 490 passes control to test 622, which examines the current DMO record of the patient to determine what processing has been done and what needs to be done. If the DMO record code does not indicate that a health assessment is required, process 490 passes control to node 634, which returns control to the calling process. If a health assessment is required, process 490 passes control to a sequence of 5 steps that obtain various health assessments. First, process 490 passes control to step 624, which asks the patient for a subjective assessment of the patient's current health state. Next, process 490 passes control to step 626, which asks the patient for objective health measurements of the patient's current health state. Next, process 490 passes control to step 628, which asks the patient for any current side effects. Next, process 490 invokes the Correlation Assessment function 630. This function is described in conjunction with FIG. 12. Next, process 490 passes invokes the Critical Curve Assessment function 640. This function is described in conjunction with FIG. 13. Next, process 490 passes control to step 632, which returns control to the calling process.
Correlation Assessment
Referring to FIG. 12, the process 630 will be described.
This function computes and standardizes the SOCF for recently added data, computes other assessment parameters and statistics, and updates the patient medical history. Finally, it invokes the health assessment function again to fill in data gaps for the interval since the last session.
Process 630 receives control at start node 650. Then process 630 passes control to step 652, which obtains any new health data that have been added to the patient's medical history since the last DM session. Then process 630 passes control to step 654, which computes new points on the raw SOCF time plot by taking the ratio of subjective to objective measurement for the same time and updating the raw SOCF time plot array with the new points. Then process 630 passes control to step 656, which applies standard statistical normalization and curve-fitting techniques to normalize the raw SOCF points and obtain a single current SOCF that is high in patients whose subjective assessment tends to match their objective health measurements, and low in patients whose subjective assessments tend to be inaccurate by comparison with their objective health measurements. Step 656 also computes other parameters used in the rest of the DM session, such as the slope and slope trend for the most recent 3 data points and the difference between patient's measurements and normal measurements. Step 656 also determines whether there are large gaps in the patient's health data, that need to be filled retroactively in by an interval assessment. Step 656 sets the DMO code appropriately to call for another assessment. Then process 630 passes control to step 658, which updates the patient's medical history with the computed assessment parameters. Then process 630 passes control to test 660, which determines whether the patient's health is to be assessed again for missing interval data. If test 660 determines that no further assessment is required, process 630 passes control to terminal node 662, which returns control to the calling process. If test 660 determines that another round of health assessment is required, process 630 passes control to test 664. Test 664 determines the type of data to be re-assessed for the interval. If test 664 determines that objective data are available, process 630 invokes Health Assessment process 490, passing a parameter that asks for both subjective and objective patient health data to be assessed for the interval. Then process 630 passes control to terminal node 674, which returns control to the calling process. If test 664 determines that objective data are not available, process 630 invokes Health Assessment process 490, passing a parameter that asks for only subjective patient health assessments to be obtained for the interval. Then process 630 passes control to terminal node 672, which returns control to the calling process.
Critical Curve Assessment
Critical Curve Assessment is a DMM process for monitoring patient health for significant deterioration. A critical curve is defined as a plot of a health measurement against time that is used to identify significant changes in health state. The Critical Curve Assessment process selects a disease- and patient-specific health parameter, plots it as a critical curve, updates the critical curve as a normal part of continuing DM sessions, and takes specific action if the patient's critical curve exhibits specific critical points, slopes, and slope trends. The process is based on comparing the patient's critical curve to standard, disease-specific critical curves. A constant, high ordinate value indicates good health; a declining curve indicates declining health; a sharp drop in the curve indicates a health crisis. The “critical point” on the curve is a point that predicts a significant decline in health.
An example of a generic critical curve is shown in FIG. 23, which contains a point circled as the “critical point”. Referring to FIG. 23, it will be noted that, at the critical point, the slope of the curve (i.e. the line tangent to the curve at the critical point) is sharply negative, which predicts that the next health measurement will be lower than the critical point. Moreover, at the critical point, the rate of slope change may also be negative, indicating that the slope of the curve is decreasing even more, predicts a rapidly deteriorating health state. For brevity, these three critical test items are typically referred to in the DMM processes as the critical point, slope, and trend. They are calculated using the last three health measurement points. For critical curves with sufficient data points, curve fitting techniques can also be used.
The DMM has a database of diseases 262 (FIG. 3) that contains standard critical curves for various diseases, patient populations, and health parameters. The Critical Curve Assessment process extracts the appropriate disease data set, selects an appropriate health parameter to be used, adapts it for the current patient, and saves it as the standard curve for the current patient in the patient's medical history 254 (FIG. 3). As the DMM periodically dialogs with the patient, the Critical Curve Assessment process obtains current data from the patient, plots them on the patient's critical curve, and uses curve-fitting and pattern matching techniques to compare the patient's actual CC to the patient's standard CC. This comparison enables the DMM to detect key points and trends on the patient's curve, such as the “critical point” that predicts a significant impending health decline. When the curve approaches this critical point, the Critical Curve Assessment method orders alterations in therapy that will prevent the predicted deterioration, or sets a flag to refer the patient to a health care provider. Both objective and subjective health data are used to plot the CC, especially if the Subjective-Objective Correlation Factor (SOCF) is high (which means that the patient knows his/her disease process well and the DMM can rely on the patient's responses more and more).
Homeostasis
The concept of homeostasis, as described by Claude Bernard, is helpful in understanding the concepts behind the Critical Curve and its analysis. Briefly, homeostasis is a state of dynamic equilibrium of the body. This equilibrium is maintained by various internal control mechanisms that force certain system parameters to remain within a desired range. Using these homeostatic mechanisms, the body is able to tolerate disease up to a certain point, at which time progression of the disease begins to accelerate. Good examples of this are:
    • the bicarbonate buffering system for maintenance of blood pH,
    • the oxyhemoglobin disassociation curve, and
    • the deterioration of a patient with chronic obstructive pulmonary disease.
      The Critical Curve
The Critical Curve (CC) describes the patient's health state during a bout with disease. The curve plots the patient's health state against time, starting initially at a (high) normal state of health and descending—as the disease progresses—to a lower state of health.
A normal, disease-free patient will have a fairly steady plot at a high level of health. The initial part of the curve is asymptotic to normal health because the healthy body can often resist disease for some time by using reserve capacities and internal defense mechanisms. After the initial phase, the health curve begins to descend at a steeper and steeper angle, as reserves are used up and the disease is established and produces secondary effects. At some critical point, the curve steepens so dramatically that the patient's condition may deteriorate quickly.
Many physiologic parameters have a characteristic response to change, being able to compensate up to a point, and then responding with very large changes in signal findings to small changes in the progression of the disease. It is very important to know where the patient is on the Critical Curve, because if the expression of the disease in this patient is about to accelerate significant intervention is required. When there is an indication or even a suspicion that the patient's condition is approaching the steep area of the health curve, the DMM can recommend a change in therapy or consultation with the patient's health caregiver. If confirmation of the change of the health state is required, the DMM reenter feature allows the DMM system to confirm its hypothesis before making recommendations.
Critical Curve Analysis
For a patient with a known disease, who is managing the disease at home with suitable maintenance therapy, the DMM monitors the patient's periodic contacts and health state reports. When the trend line indicates that the patient's health curve is reaching the critical point, the DMM can change the therapy and/or notify the patient's physician. Since patients can go for months successfully managing their disease, this Curve analysis approach can save a significant number of unnecessary physician visits, yet inform the physician and the patient at once when a change in health state indicates that the critical point is being approached.
Obviously, it is best to use an easily quantifiable parameter as a marker for the progression of the disease in question to embody this curve, but if the subjective-objective correlation is high in a given patient, their subjective evaluation can accomplish the same thing.
The system measures the tidal volume and peak flow rates over time. If it is found that small changes in tidal volume make large differences in the patient's impression of the severity of their disease (compared to the changes made previously in this patient), the patient is on the steep part of the curve. A flag is set and significant intervention is necessary.
If the therapeutic alteration permission level is set low, then the patient is referred to his physician, and the patient's doctor receives a report, frequently a fax, e-mail or downloads about the new developments. If the therapeutic alteration level is set high, then therapeutic optimization may occur before the patient sees his physician. A report is sent to the physician and the patient may or may not have to be seen.
It is this analysis and the recognition of this relationship that constitutes the “curve” analysis of the health state.
EXAMPLE Chronic Obstructive Pulmonary Disease
We will discuss chronic obstructive pulmonary disease as an example. Chronic obstructive pulmonary disease slowly destroys lung tissue. As mentioned, many physiologic parameters have the same response to changes, being able to compensate up to a point, and then, after that reserve capacity is gone, very small changes in the disease state produce very large changes in the expression of the progression of the disease in the patient its early phase, the patient with chronic obstructive pulmonary disease loses only reserve lung capacity, so there is no significant change in the resting health state. After the reserve tissue has been destroyed, a threshold is reached beyond which smaller and smaller time increments (and progression of the disease process) will produce more and more profound deterioration in the patient's ability to blow off carbon dioxide and oxygenate the blood. Ultimately, even a very small change in chronic obstructive pulmonary disease results in respiratory failure.
When we start to see larger and larger decrements to pulmonary function plotted against time, the patient is reaching the critical part of the curve. Significant intervention is necessary and should be started as soon as possible.
The Critical Curve Assessment process is especially effective in the DMM setting because the DMM:
is fully automated,
tracks patient health through time,
has various modules that track and correlate patient contacts,
knows the patient (history, Subjective-Objective Correlation Factor)
has access to databases of medical knowledge,
can analyze disease progress using mathematical trend analysis, and
can select alternate therapies as required by altered conditions.
Referring to FIG. 13, the Critical Curve Assessment function 640 will be described. This function has two phases. The first phase (starting at node 702) updates the patient's critical curve with health measurements added to the patient's medical history since the last critical curve assessment. The second phase (starting at node 712) compares the patient's actual critical curve to the standard critical curve used for this patient. If a patient is at (or is approaching) a critical part of the curve, this suggests the possibility of rapid deterioration of the disease being managed, and the patient is referred to a human physician for consultation.
Process 640 receives control at start node 700. Then process 640 passes control to step 702, which updates the patient's actual critical curve with new health measurements. Next, process 640 passes control to step 704, which analyzes the patient's updated critical curve to obtain the latest critical curve point, slope, and 3-point trend. Next process 640 passes control to step 706, which saves the patient's critical curve data in the patient medical history. Next, process 640 passes control to test 708, which examines the DMO record code to see whether the patient's critical points should be assessed. If the patient's critical points should not be assessed, process 640 passes control to terminal node 710, which returns control to the calling process. If the test 708 indicates that health assessment is needed, process 640 passes control to step 712.
Step 712 begins the assessment phase of process 640. Step 712 retrieves or computes the working data needed to use the critical curve to assess patient health. Working data include the patient's latest actual health point and slope, the matching point and slope on the patient's standard critical curve, and the thresholds used to rule the patient as critical for each set. When step 712 has computed these working data, process 640 passes control to test 714.
Test 714 begins a sequence of steps that examine the patient's critical point. If test 714 finds that the patient's latest health point is not available or cannot be matched on the standard curve, process 640 passes control to terminal node 716 which passes control to the calling process. If test 714 determines that the latest health point is available, then process 640 passes control to step 718 which compares the difference between the actual and standard critical health points. Then process 640 passes control to test 720. If test 720 finds that the patient does meet or exceed the critical point threshold, process 640 passes control to step 722, which sets the DMO record to refer the patient to a human physician for consultation. Then process 640 passes control to terminal node 724, which returns control to the calling process. If test 720 finds that the patient does not meet the critical point threshold, process 640 passes control to test 726.
Test 726 begins a sequence of steps that examine the patient's critical slope. If test 726 determines that the critical slope is not available, process 640 passes control to terminal node 724 which returns control to the calling process. If test 726 determines that the actual slope is available, process 640 passes control to 728, which compares the difference between the actual and standard critical slopes. Then process 640 passes control to test 730. If test 730 determines that the patient is below the critical slope threshold, process 640 passes control to node 724, which returns control to the calling process. If test 730 determines that the patient does meet or exceed the critical slope threshold, process 640 passes control to node 732, which sets the DMO record to refer the patient to a human physician for consultation. Then process 640 passes control to node 724, which returns control to the calling process.
Therapy Optimization
Therapy Optimization consists of a set of processes that review and adjust patient therapy from session to session, with a long-term goal of maximizing efficacy, minimizing adverse side effects, and maintain patient cooperation and acceptance of the recommended therapy. The Therapy Optimization processes select therapy parameters from medical treatment tables and track patient-specific efficacy by reviewing subjective and objective patient health data from session to session. The Therapy Optimization process selects from multiple therapies. It seeks to minimize side effects by offering the patient the choice of alternate therapies, and by adjusting therapy dosage levels until the patient finds the appropriate comfort level. Disagreements between the DMM and the patient are resolved by referring the patient to a human physician for face-to-face consultation and advice. Therapy Optimization is guided and controlled by the Therapy Optimization Permission Level (TAPL), a DMM-global variable that specifies the amount of autonomy that the DMM has to alter therapy. The TAPL is described in a separate section below.
After the patient health state has been assessed, the Therapy Optimization process reviews and adjusts (to the extent the TAPL allows it) the patient's treatment to achieve the best combination of several subgoals of the overall goal of restoring normal health. The Therapy Optimization process also seeks to minimize treatment side effects. To the extent allowed by the current TAPL setting, the DMM will gradually titrate the dose of a medication until the benefit/side effect ratio is maximized. The overall idea is to achieve the desired physiological changes with the fewest side effects. Initial treatment is selected from a treatment table based on disease, age, and sex. Due to the wide range of responses to treatments by different patients, once a drug has been selected as the therapy for a given disease, the different formulation, dosing, administering methods and timing are, in effect, a matter of trial and error for a specific patient. To review therapy, the Therapy Optimization task compares the patient's current therapy to the treatment table to detect and analyze differences. If a new treatment is available, the patient and the healthcare giver are notified, and the therapy may be altered, depending on the TAPL. To maximize the therapeutic result and minimize side effects, the Function can select the initial therapy, review the patient's current therapy, adjust various parameters of the therapy, and monitor the effect of these changes.
Therapy parameters that can be changed include drug class, type, brand, dose, route, mode of drug administration, formulation, timing, and frequency. As each of these is modified, the patient's health data and side effects are checked to see if the current modification of therapy makes the patient better, and so on. Each therapy parameter is sequentially altered on a trial and error basis to find the overall best combination of therapy parameters. When the DMM adjusts a patient's therapy, it adjusts the DM session schedule appropriately, typically instructing the patient to re-enter the system within a few iterations of therapy or dosage.
Side effect minimization is a special goal of the Therapy Optimization process, which seeks to reduce the undesirable side effects of therapy. This task illustrates the complex, trial-and-error methods used by the DMM to Therapy Optimization feature. Example 1: In cancer patients there is a point at which patients receiving chemotherapy decide that the side effects are not worth the slowing of the progression of the disease. At that point, one “backs off” (decreases the dosage), knowing that any further increase will be futile. The process becomes more complicated if multiple drugs are involved, but the same relationships hold. Example 2: Albuterol-metered dose inhalers help the wheezing of asthma patients, but at a certain patient-specific dose, the side effects get so bad, that the patient cannot tolerate them. At that point, the dosage is backed off in small steps to get the best ratio of efficacy to side effects.
Referring to FIG. 14, the Therapy Optimization process 408 will be described. Process 408 performs the therapy phase of the DM session. This phase computes the next best therapy step that is accepted by the patient, using two major subordinate processes and a loop that tries various therapies until the patient accepts one. The general goal of process 408 is to select therapy steps in a manner that optimizes therapy over the long term, by maximizing efficacy, minimizing side effects, and adjusting therapy types and modalities to meet the patient's comfort level. Process 408 receives control at start node 760. Then, process 408 passes control to test 762, which tests whether the patient provided current objective health measurements during the earlier part of this DM session. If test 762 finds that the patient did not provide current objective health data, process 408 passes control to test 782, which tests whether the patient entered a subjective assessment of his/her health during the earlier part of the DM session. If test 782 finds that the patient provided a subjective health assessment, process 408 invokes process 790. Process 790 adjusts the therapy based on current subjective health data. Process 790 is detailed below in conjunction with FIG. 15. When process 790 returns control, process 408 passes control to terminal node 792, which returns control to the calling process. If test 782 finds that the patient did not provide a current subjective health assessment, process 408 passes control to 784, which sets the DMO record to refer the patient to a human physician for consultation. Then, process 408 passes control to terminal node 786, which returns control to the calling process.
If test 762 finds that the patient did provide current objective health data, process 408 passes control to step 764, which initializes a loop that will try various therapies until the patient accepts one or until the number of retries is exhausted, whichever occurs first. Step 764 obtains the maximum number of therapy permitted from the permissions database for this patient. Then, process 408 invokes process 770. Process 770 selects the next best therapy from the treatment table for this patient and offers it to the patient who can accept or modify or reject it. Process 770 is further described below in conjunction with FIG. 16. When process 770 returns control, process 408 passes control to test 772. If test 772 determines that the patient accepted the therapy recommended, process 408 passes control to terminal node 780, which returns control to the calling process.
If test 772 determines that the patient rejected the therapy recommended, process 408 passes control to test 774. If test 774 determines that the loop retry count is greater than one, process 408 passes control to step 776. Step 776 reduces the loop retry count by 1 and then process 408 invokes process 770 again for another iteration of the loop. If test 774 determines that the retry count is 1, then process 408 passes control to step 778. Step 778 sets the DMO record to refer the patient to a human physician for consultation. Then, process 408 passes control to terminal node 780, which returns control to the calling process.
Therapy Adjustment (Subjective)
Referring to FIG. 15, the process 790 will be described. Process 790 computes the next best therapy for this patient, based only on the patient's subjective assessments of his/her health. Process 790 uses the Subjective-Objective Correlation Factor (SOCF) which is described below in the section Subjective-Objective Correlation Factor. The SOCF indicates how reliable this patient is in subjectively assessing his/her disease, and process 790 relies on the SOCF in computing the next therapy step.
Process 790 receives control at start node 810. Then, process 790 passes control to test 812. If test 812 determines that the patient does not need therapy adjustment, i.e. that the DMO record of this patient has already been completed for an approved therapy, process 790 passes control to terminal node 814 which returns control to the calling process. If test 812 determines that this patient requires therapy optimization, process 790 passes control to test 816. Test 816 determines (by asking the patient or by obtaining the patient's saved response if the patient has already been asked) whether the patient is having any current symptoms. If test 816 finds that the patient is symptom-free, process 790 passes control to test 818. If test 818 determines that the current DMM TAPL setting does not permit therapy adjustments, process 790 passes control to node 826, which sets the DMO record to maintain the same therapy, e.g. the same dose in the case of a drug-based therapy. Then, process 790 passes control to terminal node 824, which returns control to the calling process.
If test 818 determines that the current TAPL setting does permit therapy adjustments, process 790 passes control to test 820. If test 820 determines that the patient does not want to try to reduce the dose, process 790 passes control to step 826, which sets the DMO record to maintain the same therapy. Then, process 790 passes control to terminal node 824, which returns control to the calling process. If test 820 determines that the patient wants to reduce the dose, process 790 passes control to step 822, which looks up the next lower dosage level in the treatment table and sets the DMO record to decrease the dose. Then, process 790 passes control to terminal node 824, which returns control to the calling process.
If test 816 finds that the patient is having current symptoms, process 790 passes control to test 830. If test 830 finds that the TAPL does not permit changes in therapy, process 790 passes control to step 832. Step 832 sets the DMO record to refer the patient to a human physician for consultation. Then, process 790 passes control to terminal node 833 returns control to the calling process. If test 830 finds that the TAPL does permit changes in therapy, process 790 passes control to step 834.
Step 834 begins that phase of process 790 which computes the next therapy step for a patient who is having symptoms, but has only reported current subjective health assessments. Step 834 uses the current SOCF from the patient's medical history, modifies it by the current Sensitivity Factor Set to adjust it to the sensitivity being used for this patient, and then classifies the patient's current SOCF as “high” or “low” for the purpose at hand. If test 834 classifies the patient's SOCF as high, the patient's subjective health assessment is reliable, and process 790 passes control to step 838 which looks up in the treatment table how much the therapy (i.e. dose in the example drawn) can be increased for a patient with a high SOCF, and what the associated benefits and risks are. Then, process 790 invokes function 840. Alternatively, if test 834 deems the SOCF as low, process 790 passes control to step 836, which obtains the dose and risk/benefit factors for unreliable patients. In either case, process 790 continues by invoking function 840.
The Patient Consent Level function 840 presents a recommended therapy to the patient and obtains a consent of the patient to the therapy as recommended or to some variation of it; the patient may also reject the recommended therapy entirely. Function 840 is described below in conjunction with FIG. 17.
When function 840 returns control, if function 840 returns the result that the patient consents to an increased dose, process 790 passes control to step 842. Step 842 sets the DMO record to indicate the next therapy with an increased dose, and with an appropriate change in schedule for a sooner DM session. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
When function 840 returns control, if function 840 returns the result that the patient consents to continue therapy with the same dose, process 790 passes control to step 846. Step 846 sets the DMO record to indicate that the same therapy is to be continued. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
When function 840 returns control, if function 840 returns the result that the patient consents to a reduced dose, process 790 passes control to step 848. Step 848 sets the DMO record to indicate the next therapy with a reduced dose. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
When function 840 returns control, if function 840 returns the result that the patient rejects the recommended therapy at any level, process 790 passes control to test 850. Test 850 consults the current Sensitivity Factor Set to see whether process 790 should try the next best therapy or should refer the patient to a human physician. If test 850 determines that other therapies may be tried, process 790 passes control to node 852, which sets the DMO record to indicate that the patient rejected the recommended therapy. Then, process 790 passes control to terminal node 844, which returns control to the calling process. If test 850 determines that the patient should be referred, process 790 passes control to node 854, which sets the DMO record to refer the patient to a human physician. Then, process 790 passes control to terminal node 844 which returns control to the calling process.
Therapy Adjustment (Objective)
Referring to FIG. 16, the process 770 will be described. Process 770 computes the next best therapy for this patient, based on the patient's current objective health measurements. The process receives control at start node 870. Then, process 770 passes control to test 872. Test 872 compares health assessment parameters to determine whether the patient's objective health data meet or exceed various thresholds. Test 872 first compares the patient's current health measurement to an absolute threshold for that measurement, to see if the measurement itself is in acceptable range. Test 872 next compares the slope of the last two health measurements, to see if the patient's health is deteriorating at a rate that exceeds a threshold. Test 872 next compares the change in the slopes of the last three measurements, to see if the patient's rate of change of health is getting worse more and more rapidly. If any one of these thresholds is met or exceeded, process 770 passes control to step 874, which sets the DMO to refer the patient to a human physician. Then, process 770 passes control to terminal node 876, which returns control to the calling process.
If test 872 determines that all of the patient's current health statistics are below threshold, process 770 passes control to test 878. Test 878 begins that phase of process 770 which computes the next recommended therapy for this patient. Test 878 compares the current patient health measurements to those of the previous DM session, to classify the patient's change of health state as “better, same, or worse” for the purpose of computing the next therapy step.
If test 878 determines that the patient is worse than the last time, process 770 passes control to test 880. Test 880 determines (from the treatment table) whether the current therapy dose can be increased. If test 880 determines that the dose can be increased, process 770 passes control to node 882, which sets the DMO to increase the dose. Then, process 770 passes control to test 896. If test 880 determines that the dose can not be increased, process 770 passes control to node 884, which sets the DMO to continue therapy with the same dose. Then, process 770 passes control to test 896.
If test 878 determines that the patient is in the same health as the last time, process 770 passes control to test 892. Test 892 determines whether the patient's current health measurements are in normal limits. If test 892 determines that the patient's current health data are normal, process 770 passes control to step 890. Step 890 sets the DMO to decrease the dose. Then process 770 passes control to 896. If test 892 determines that the patient's current health data are outside normal limits, process 770 passes control to test 880. Test 880 has been described above for process 770.
If test 878 determines that the patient is better than the last time, process 770 passes control to test 886. If test 886 determines (by consulting the treatment table) that the current dose can be reduced, process 770 passes control to step 890. Step 890 has been described above for process 770. If test 886 determines that the current dose can not be reduced, process 770 passes control to step 888, which sets the DMO to continue therapy with the same dose. Then, process 770 passes control to test 896.
Test 896 determines whether the TAPL setting for this patient allows the DMO as computed so far by process 770. If test 896 determines that the TAPL allows the DMO as written, process 870 invokes the Patient Consent Level function 840, which presents a recommended therapy to the patient and obtains a consent of the patient to the therapy as recommended or to some variation of it; the patient may also reject the recommended therapy entirely. Function 840 is described below in conjunction with FIG. 17. If function 840 returns the result that the patient accepts the recommended therapy (perhaps at some modified level), process 770 passes control to terminal node 898, which returns control to the calling process. If function 840 returns the result that the patient rejects the recommended therapy entirely, process 770 passes control to test 900. Test 900 consults the current Sensitivity Factor Set to see whether process 770 should try the next best therapy or should refer the patient to a human physician. If test 900 determines that other therapies may be tried, process 770 passes control to node 902, which sets the DMO record to indicate that the patient rejected the recommended therapy. Then, process 770 passes control to terminal node 904, which returns control to the calling process. If test 900 determines that the patient should consult a physician, process 770 passes control to node 906, which sets the DMO record to refer the patient to a human physician. Then, process 770 passes control to terminal node 904 which returns control to the calling process.
If test 896 determines that the TAPL does not allow the recommended therapy, process 770 passes control to step 908, which sets the DMO record to refer the patient to a human physician. Then, process 770 passes control to terminal node 904 which returns control to the calling process.
Patient Consent Level
Referring to FIG. 17, the Patient Consent Level function 840 will be described. Function 840 presents a recommended therapy to the patient and obtains the consent of the patient to the therapy, either exactly as recommended by the DMM, or as adjusted to some variation of it, based on the patient's responses. The patient may also reject the recommended therapy entirely. Function 840 receives control at starting node 920. Then process 840 passes control to step 922, which outputs the therapy as recommended in the DMO to the patient. Next, process 840 passes control to step 924, which presents the risks and benefits to the patient. Next, process 840 passes control to step 926, which presents other therapy choices to the patient. Next, process 840 passes control to step 928, which asks the patient to agree to the recommended therapy, or to some version of the therapy. Next, process 840 passes control to step 930, which updates the DMO to record the choices offered, warnings given, and consent level received, with suitable date and time stamps. Next, process 840 passes control to step 932, which computes a function result to be returned to the calling process. The consent level granted by the patient may have several values. The four values used in the flowcharts assume a drug therapy, and are: (1) ok to increase dosage; (2) ok to keep dosage at same level; (3) ok to reduce dosage; and (4) reject this therapy. Next, process 840 passes control to terminal node 934, which returns control to the calling process.
Close Session
Referring to FIG. 18, the Close Session process 410 will be described. Process 410 is the last process executed for every DM session. It is specifically responsible for processing the Disease Management Order (DMO), which contains the complete set of tests made and reasons therefore, the next therapy step recommended, consent given by the patient, and various associated orders, such as to fax a prescription to the patient's pharmacy, to order a test from a laboratory, to prepare a report for the patient's physician, to send printed instructions to the patient, and so on. Aside from implementing the DMO details, process 410 is also generally responsible for logging all events that occurred during the DM session, storing all relevant data, closing all applicable files, scheduling the next DM session, and finally bidding the patient farewell to indicate that the current DM session is terminated.
Process 410 receives control at start node 950. Next, process 410 passes control to test 952, which logs the therapy ordered by the DMO in the patient's medical history. Then process 410 passes control to test 954, which determines whether the DMO contains special orders to be processed. If test 954 determines that the DMO has no special therapy orders, process 410 passes control to step 972, which schedules the next DM session as specified in the current therapy schedule of the patient. Then, process 410 passes control to node 962. Processing from node 962 is described below for process 410. If test 954 determines that the DMO has special orders, process 410 passes control to step 956, which schedules the next DM session as ordered by the DMO. Next, process 410 passes control to step 958, which prepares and sends various notices and reports to various contacts. These notifications and the contacts that receive them are controlled by the Regulatory, Sharing, and other authorization fields that are maintained in the Permissions database. Next, process 410 passes control to step 960, which informs the patient about the next therapy step and gives the patient instructions as ordered by the DMO and as permitted by the Permissions database. Next, process 410 passes control to step 962.
Step 962 informs the patient's physician about the DM session and about the therapy ordered by the DMM. While the patient's physician is always entitled to all information generated for the patient, the physician may specify the notices sent and the detail reported. The physician's current requirements and limitations for notification are stored in the permissions database, and may be modified by the physician using processes outside of the DMM. Next, process 410 passes control to step 964, which informs the patient about the actions taken by the DMM software, to the extent permitted in the Permissions database. This step allows the system to tell the patient what it is doing and why, which can gain the patient's confidence and help the patient to make better decisions in future sessions. This feedback is an important element of the long-term therapy optimization that is one of the hallmarks of this invention. Step 964 also reviews all special flags set to discuss new symptoms with the patient. Next, process 410 passes control to step 966, which saves all relevant data in various suitable main and backup storage locations. Next, process 410 passes control to step 968, which closes all applicable data files and releases all temporary computing system resources allocated to the DM session. Next, process 410 passes control to terminal node 970, which returns control to the calling process.
Question Versions
The Question Versions feature of the DMM allows several different versions of the same question to be written into a script, and defers the decision which version to use until run-time. The feature uses a global data item called the Question Version Index (QVI) to select the desired version of the question from the script at run time.
The Question Version feature can be visualized as a “Question Roller”: a multi-faceted cylinder with one different version of the question written on each face. To ask a question, the cylinder is rolled to display the face that contains the desired question text. If each question of a set is written on a separate cylinder, and all cylinders are rolled in unison to display the same face, as specified by a global control element, the entire question set of the script can be adjusted or “rolled” as one unit, so that the script as a whole can be adjusted or fine-tuned to ask different versions of the question at different levels.
One use of the Question Versions feature is to be able to globally adjust the sensitivity and selectivity of the language used by the entire DMM, using a DMM-global QVI that controls the linguistic sensitivity. Thus, when the sensitivity or selectivity of questions needs to be altered, the Question Roller is turned or ratcheted one way to increase the sensitivity and the opposite way to increase the selectivity. For this use, each question version differs only slightly in wording and sensitivity. In some cases, the only difference is a comma (a pause) or an intonation of the voice, such as:
    • Is this absolutely the worst headache that you can imagine anyone having?
    • Is this the worst headache that you can imagine anyone having?
    • Is this the worst headache you have ever had?
    • Is this one of your worst headaches?
Another use of the Question Version feature is to write script questions aimed at different levels of patient education, intelligence, disease understanding, or medical expertise. For example, the DMM can ask the same question in various forms written for a 3rd grader, for a high school student, for a college graduate, or for a health care provider. Thus, the DMM can adapt output to the patient's communication needs, which may involve a range of decisions based on what is currently known about the patient, such as what natural language to use, what the level of understanding is, what grammar to use (e.g., are we addressing the patient, the patient's relative, or the patient's doctor?), and what medical details to disclose. The DMM can consult the patient's medical history to determine the level of the language, education, and intelligence that the patient can understand. If no indicator is present, a mini language IQ test can be given as part of the Initial Health Assessment task to establish the QVI to use with the patient.
Yet another use of the Question Version feature is to allow the DMM to adjust the question level dynamically, based on the patient responses or requests. Thus, a patient who is getting confused or lost may ask the DMM to give more detailed instructions on how to respond to questions. The DMM can react by altering the QVI to select more appropriate question versions. On the other hand, as the patient learns during a session, s/he may later request fewer instructions and a faster communications mode. Again, the DMM can respond by adjusting the QVI. In this manner, the DMM learns about the patient's current and past use of the DMM and can modify itself to adapt to the patient's natural language, education, medical knowledge, and medical sensitivity required.
The Question Version feature is implemented in software by allowing script authors to collect different versions of a question into a “version group,” in which each version of the question is associated with a different QVI. At run-time, the DMM uses the Sensitivity Factor Set to establish a global QVI to specify the current question version to be used with the current patient by all scripts. When a DMM process (such as the script engine) needs to output a question, it uses the global QVI to find and retrieve the desired question from the script's question group. Questions that do not require different versions are written as a version group with only one question, which acts as the default question. This default question is also used when there is no question in the version group for the current global QVI.
This Question Version design allows questions versions to be written for a wide range of QVIs, without having to write a version for each QVI. A simple script can just have one question version; as the script improves, additional question versions are added. For example, the first script might be written in English, and later upgraded to add Spanish versions of each question.
The Question Version feature is implemented in the form of a Question Version Index and two separate functions Set QVI and Select Question. In FIGS. 19 a and 19 b, these elements are shown as follows:
Global Version Index (QVI) is data item 1020;
Set QVI is process 1000;
Select Question process is shown as process 1001.
The current setting of the Global Version Index 1020 determines which one of several different question versions is selected and output to the patient. Data element 1020 is stored as a control field in the permissions database 256 (FIG. 3), and is changed by process 1000 and used by process 1001.
Process 1000 is a DMM-global system service routine that sets and updates data element 1020 periodically. Process 1000 receives control at starting node 1002. Then process 1000 passes control to step 1004, which identifies the patient whose data element 1020 is to be set. Then process 1000 passes control to step 1006, which retrieves the current value of the patient's data element 1020. Then process 1000 passes control to step 1008, which computes the new value of the data element 1020. Step obtains the level of sensitivity desired from the current Sensitivity Factor Set, and obtains other parameters from the patient medical history, such as the level of patient's education, the level of language understood, and the QVI settings used in past DM sessions. After step 1008 computes a new QVI value, process 1000 passes control to step 1010, which stores the new value in the patient's data element 1020. This completes the action of updating the patient's data element 1020. Then process 1000 passes control to terminal node 1012, which returns control to the calling process.
Process 1001 is a DMM-global routine that uses the Global Version Index 1020 to select one question from a set of questions. Process 1001 receives control at starting node 1022. Then process 1001 passes control to step 1024, which loads the applicable question set from the current script's data area.
Then process 1001 passes control to step 1026, which obtains the current value of the Question Version Index 1020 from the patient's permission file. Then process 1001 passes control to test 1028. Test 1028 determines whether the question version selected by the QVI is in the question set obtained in step 1024. If test 1028 determines that the desired version is in the question set, process 1001 passes control to step 1030, which retrieves the question with the desired question level from the set. Then process 1001 passes control to step 1034, which returns the question selected from the set as a function result to the caller. Then process 1001 passes control to terminal node 1036, which returns control to the calling process. If test 1028 determines that the desired version is not in the question set, process 1001 passes control to step 1032, which retrieves the default question from the set. Then process 1001 passes control to step 1034, which returns the question selected from the set as a function result to the caller. Then process 1001 passes control to terminal node 1036, which returns control to the calling process.
Preview Mode
Preview Mode is a DMM script run-time mode that allows the patient to “look ahead,” that is to examine the consequences of a response before “officially” giving the response. In effect, the patient can say—at any point in a script—“let me see what this answer would do”. One use of Preview Mode is to let the patient suspend an ongoing dialog to see what a pending question means. Knowing the consequences of a response is helpful in clarifying the impact or focus of a question. Thus, in a printed flowchart or procedure, one good way to find the best path is to look ahead to see what the consequences (or recommendations) would be of answering a question a certain way. Another uses of Preview Mode is to let the script explicitly warn the patient that a particular question involves serious consequences, and to use Preview Mode so that the patient can consider the effect of each response. For example, one response may begin action to contact the patient's physician, or to transfer the patient to an emergency facility. If the script can warn the patient about this consequence, the patient can preview these responses without activating them, and can alter the direction of the script dialog.
Referring to FIG. 20, the process 1060 will be described. This process shows only those steps of a DM session that handle the Preview Mode feature, which is involved in the steps that ask the patient a question and process the response. Other steps of a DM session that are not concerned with the Preview Mode are omitted for clarity. Process 1060 receives control at start node 1062. Then process 1060 passes control to test 1064. If test 1064 determines that there are no further questions to be asked, process 1060 passes control to terminal node 1066, which terminates the Preview Mode. If test 1064 determines that is a question to be asked, process 1060 passes control to step 1068, which outputs the question to the patient. Then process 1060 passes control to step 1070, which outputs the set of responses to the patient. Then process 1060 passes control to step 1072, which inputs a response from the patient, together with an indicator that the patient does or does not want to preview the script's actions for this response. Then process 1060 passes control to test 1074. If test 1074 determines that the patient has responded with the preview indicator set, process 1060 passes control to step 1076. Step 1076 retrieves the preview information that is coded into the script (as part of the normal question and response texts) and outputs it to the patient, so that the patient sees or hears a description of what the selected response would do in “real” mode. For example, a preview text might tell the patient that “A YES response will increase your daily medication dose for the next 2 weeks”. After the preview text is output to the patient, process 1060 passes control to step 1068, which asks the same question again, as described above for step 1068. But if test 1074 determines that the patient has responded without the preview indicator, process 1060 passes control to step 1078. Step 1078 performs the actions normally scripted for the response given. Then process 1060 passes control to test 1064, which determines whether there is a next question to be asked, as described above for test 1064.
No-Response Feature
Every DMM dialog with a patient is controlled by a script. During a normal session, the script selects a question and outputs it to the patient, and the patient inputs a response. The script analyzes the response, selects another question, and outputs it to the patient. This question-response-question-response dialog continues until the session is terminated normally. However, when a patient unexpectedly fails to respond in the middle of the dialog, all scripts are designed to invoke the No-Response (NR) feature, which is responsible for taking appropriate continuation action for the script. The NR feature is a DMM software mechanism that is triggered when a timeout condition is signaled by the operating system. The NR mechanism can take any number of actions that have been pre-arranged by the script and can be changed as the script runs. The NR actions can range from a silent entry in the DM sessions log all the way to using health data from the patient medical history and medication and symptom data from the disease database to contact a responsible neighbor of the patient, or a nearby emergency response facility.
One use of the NR feature is to perform a medical disease- and patient-specific evaluation of the failure of the patient to respond. Obviously, in certain patients with certain diseases (e.g. heart problems, head injury, diabetes) the patient's sudden failure to respond in the middle of a normal dialog may indicate any number of possibilities. The NR feature is of special value in the context of the DMM, which has detailed medical information about a patient from previous sessions, and in the context of the First Opinion Support System, which has extensive relevant databases indexed by geographic location around the world (e.g., emergency rooms, 911 agencies, paramedics). Because of what the system knows about a patient, the NR feature can take very situation-specific actions. A very simple example would be a 60-year old man consulting for chest pain: sudden failure to respond to a question would suggest a cardiac arrest and could initiate emergency actions, including calling the patient's local 911 agency.
Referring to FIG. 21, the process 1100 is described. Note that process 1100 shows only those portions of a script's steps that are relevant to the No-Response Feature. Other steps of the scripts are omitted for clarity. Process 1100 receives control at start node 1102, which represents the generic start node of any script. Then process 1100 passes control to step group 1104. Step group 1104 represents all of the script's actions that do not involve the NR Feature. If the script terminates as part of one of these steps, process 1100 passes control to terminating node 1106, which terminates the script. When one of the steps in step group 1104 wants to ask a question of the patient, process 1100 passes control to step 1108. Step 1108 sets up the NR parameters needed later, if the patient should fail to respond. The source of these parameters is the patient's medical history 254, which contains the relevant information to be used if the patient fails to respond, such as the patient's disease, health state, medications being taken, physician, nearest emergency facility, and so on. Step 1108 stores the NR parameters as a data set 264. Then process 1100 passes control to step 1112, which outputs the actual question to the patient. Then process 1100 passes control to test 1114. Details of step 1114 vary with operating system and hardware platform, but the typical action is to set a timeout flag for a specified wait time, yield control to the operating system, and regain control when the operating system returns a response or the wait time has expired. If test 1114 receives a response, process 1100 passes control to step group 1104, where the normal script's actions continue. If test 1114 receives a timeout, process 1100 passes control to step 1116. Step 1116 retrieves the patient-, disease-, and location-specific NR data from the data sets 264 and 254 and performs the NR actions requested. When step 1116 has performed the NR actions, process 1100 passes control to terminal node 1116, which represents the generic termination of a script due to a timeout.
PQRST Array
Sir Thomas Lewis said that pain is “known to us by experience and described by illustration”. The ability to encode the subjective experience of pain into a standard and repeatable format is an essential asset to any system of automated medicine. Many diagnostic sessions begin with a patient reporting some type of pain to a physician in the form of a chief complaint; a thorough description of pain can quickly suggest as well as eliminate many diagnoses, using a table lookup or database access mechanism.
The PQRST Array feature describes a set of software processes and data that work together to encode a patient's description of pain into a “pain code”, which is a specially formatted array of integers. Encoding is done in a manner that preserves the subjective information, so that it is possible to decode a pain code by using the array integers to recover the original words used to describe the pain.
A pain code is composed of subcodes; each subcode identifies one well-defined detail aspect of the experience of pain such as location, sensation, frequency, etc. The pain subcodes are arranged into a specific sequence or format that is known to all software processes that manipulate the pain code. The sequence used to encode the aspects is itself prefixed as a number to the sequence, so that so that the first aspect of the array always identifies the coding scheme that is used for the array. This makes the PQRST Array flexible and extensible, since various encoding schemes can be used to meet various needs. Any software process that needs to decode a PQRST in the future simply examines the first aspect code and knows from its value which decoding scheme to use for the rest of the aspects.
The PQRST Array feature permits encoding of a patient's report of pain into digital form that is suitable for software processes. For example, a patient's complaint that “when I bend my right arm or rotate my wrist, even slightly, the elbow area hurts really bad, with a sort of gritty or grinding sound, but there is no bleeding” may be encoded by letting the patient select from standard descriptor words (e.g. gritty, tight, numb) and converting the selected words into an integer array something like (7, 2, 3, 8, 5, 970612, 2, 13). This array represents the numeric value of various aspects of pain such as location, repeatability, quality, or a date such as 970612. For any given aspect, the number represents some degree or description of the pain. Thus, if the fourth aspect number represents Sounds-Associated-With-Movement, the subcode value 8 may represent “gritty/grinding noise associated with joint movement”.
The “PQRST” label is adapted from the classic mnemonic used by medical students for the basic aspects of pain, which are: P=Provocative/Palliative (what brings it on, makes it worse, or makes it better); Q=Quality (sharp or dull); R=Region (head or chest, etc.); S=Severity (mild to agonizing); and T=Timing (when the pain started). These aspects represent a starting point for the PQRST Array, which is extensible to include other useful subjective descriptors of illness, with many additional aspects associated with the pain such as Cause (infection, trauma), Mass (mole, lump), Size (fingertip, golf ball), Sensation (tickling, pulsing) and objective associations (color, smell, discharge).
To encode a description of pain into a pain code, a process
    • uses a set of pre-defined aspects (i.e. facets, elements, dimensions) of pain,
    • uses a set of pre-defined aspect words defined for each aspect,
    • obtains the applicable aspect word from the patient
    • encodes all aspect words into subcodes
    • formats the subcodes as a physical data item (the PQRST Array)
    • stores the PQRST Array in memory or on disk
    • uses the address of the storage location as a pointer
To manipulate a pain code as a whole, a program
    • passes the pointer to the PQRST Array
    • uses the pointer to access the PQRST Array, if necessary
To decode a pain code, a program reverses the encoding process:
    • uses the pointer to locate the PQRST Array in memory or storage
    • retrieves the PQRST ARRAY from memory or disk
    • retrieves each subcode
    • decodes each subcode into its subjective aspect word
    • outputs the aspect words as the subjective description.
Referring to FIG. 22 a, the process 1140 will be described. Process 1140 comprises the steps required to create a PQRST Array that represents the digitized form of a patient's subjective description of pain. Process 1140 is described here assuming that the patient is on-line and can interactively enter subjective pain description details when prompted by process 1140. Process 1140 receives control from a calling process at start step 1142. Step 1142 is the beginning of a loop that encodes pain aspects entered by the patient into a matching set of pain subcodes. Step 1142 allocates space for a PQRST Array that will contain the subcodes. Next, process 1140 passes control to step 1144, which establishes the next pain aspect to be encoded. Next, process 1140 passes control to step 1146, which retrieve a list of standard aspect words from database 1150 and outputs them to the patient in a format of a pick list, i.e. a list that the patient can examine and from which the patient can pick one of the aspect words. Next, process 1140 passes control to step 1152, which asks the patient to select the aspect word from the pick list that best matches the patient's subjective description of the pain aspect being encoded. Next, process 1140 passes control to step 1154, which converts the aspect word selected by the patient into an integer that identifies that aspect word. This integer is the subcode for the current aspect. It can be simply the index position of the selected aspect word in the pick list. Next, process 1140 passes control to step 1156, which inserts the subcode integer into the PQRST Array, at the index position that represents the aspect being encoded. Next, process 1140 passes control to test 1158, which determines whether more aspects are to be encoded. If test 1158 finds that there are more aspects to be encoded, then process 1140 passes control to step 1144 to begin another iteration of the loop just described. If test 1158 finds that there are no more aspects to be encoded, then process 1140 passes control to step 1160, which stores or copies the PQRST Array into the appropriate data set, such as the patient's medical history 254. Next, process 1140 passes control to step 1162. Step 1162 returns control to the calling process.
Referring to FIG. 22 b, the process 1170 will be described. Process 1170 is an example of the steps required to use a PQRST Array as an index to retrieve a specific diagnosis from a table of diseases. This example assumes that a list of diseases (or disease sets, where there is more than one disease for a given pain code) has been indexed by pain code and stored into a database of diseases 262. This example also assumes that there is a software process for accessing the database that can retrieve elements of the database when given an access key. One obvious example of such a database access mechanism is a suitably formatted Structured Query Language (SQL) statement; another example is a simple array of disease names or pointer that is accessed using the index position of each element. Process 1170 receives control at start node 1172. Then process 1170 passes control to step 1174, which loads a copy of the PQRST Array to be used to select the diagnosis from database 262. Next, process 1170 passes control to step 1176, which converts the DMM pain code into an access key that is formatted as required by the process that accesses database 262. Next, process 1170 passes control to step 1178, which uses the access key to retrieve the record matching the pain code from database 262. Next, process 1170 passes control to terminal node 1180, which returns control to the calling process.
Disease Management Order (DMO)
The Disease Management Order is a data record that is attached to the patient at the beginning of a DM session, travels with the patient from process to process, and is used at the end of the session (by the Close Sessions process) to implement the decisions and orders issued by the various processes during the session. The DMO record contains numerous fields and is stored in the sessions area of the DM-specific databases 264 (FIG. 3). One key field of the DMO, named Code, typically contains the next processing to be performed for the patient.
One use for the DMO is to signal special processing required for a patient. For example, to flag a new patient for a one-time requirement to conduct an initial interview, the Open Session process sets the DMO Code field to “assess initial health” (FIG. 6, node 448). The DM session process then continues into Health Assessment, which examines the DMO Code and shunts the patient into the Initial Health Assessment process 488 (FIG. 7).
Another use for the DMO is to repeat processes as needed. For example, if the Correlation Assessment process requires additional health data for the interval between session, it can invoke Health Assessment again to obtain missing data (FIG. 12, node 660). When the process has enough data, it sets the DMO Code to “optimize therapy” and the patient is shunted out of the assessment cycle.
Another use of the DMO is to track various reasons for decisions made, which can be used by the Close Sessions process to issue detailed reports of what the DM processes learned about the patient. For example, the Therapy Adjustment processes can refer the patient to a physician for different reasons (FIG. 14, nodes 778 and 784; FIG. 15, nodes 832, 854). In each case, the DMO code is set to “refer to MD”, but the DMO Reason field is set to indicate a different reason.
Finally, the key use of the DMO is to represent “doctor's orders”, i.e. to accumulate all of the orders issued during the session, so that they can be implemented when the session is terminated (FIG. 18, node 956).
Permission Database
The Permissions Database 256 (FIG. 3) is a collection of all of the software elements that control access to DMM data and actions taken by DMM processes. This database supports the DMM safety, security, reliability, control, and management features in the form of passwords, access rights, need-to-know and right-to-know clearances, disclosure authorizations, consents, constraints, limits, thresholds, and so on. The Permissions Database is the interface through which a human staff of medical and software experts can specify and control what automatic actions the DMM can and cannot perform. Since permissions govern the actions of all DMM processes, the Permissions Database can be used to dynamically configure the system to run in various modes, ranging from fully automatic to totally non-automatic, where the DMM has to ask permission for every detail step to be taken. The latter mode is especially useful for experimental, test, problem tracking, or system auditing uses.
Three tables of the Permissions Database are relevant to the operation of the DMM processes described above; they are described under their respective section headings below: Regulatory Permissions, Sharing Permissions, and Therapy Alteration Permission Level (TAPL).
Regulatory Permissions
Regulatory Permissions are data sets that insure compliance of the DMM with all applicable regulatory, licensing, and legal requirements and restrictions of the many jurisdictions in which it operates. The Regulatory Permission data sets are organized by jurisdiction, and specify for each jurisdiction which data fields can be disclosed to what agency. The Regulatory Permissions feature addresses a very complex issue that is typically ignored by other automated medical systems, namely that such systems may be deemed to be practicing medicine in and across controlling jurisdictions, even across international borders, and must therefore meet a large number of various medical practice constrains and licensing regulations. This feature allows the DMM to comply with the law in its actions and in its contacts with patients, physicians, health care management organizations, government agencies, and so on.
Regulatory Permissions are DMM-global, and can be used wherever they are applicable. One example is in the Close Session process (FIG. 18, nodes 958-964) which must consider the legal requirements and prohibitions regarding disclosure of confidential medical data before distributing notices, instructions, and reports about the DM session or the patient.
Sharing Permissions
Sharing Permissions are used to manage disclosure of individual medical data items. Every data field in the patient medical history is associated with an access control field that specifies whether or not the medical data item can be disclosed to the patient, to various agents or agencies, and to other software objects with specific access authorizations. Sharing Permissions are used by the DMM Close Session process (FIG. 18, nodes 958, 960) to decide what medical data items can be disclosed (i.e. “shared”). in its messages and reports to patients, patient agents, physicians, laboratories, pharmacies, health care management organizations, or government agencies.
Another use of Sharing Permissions is to prevent a diagnosis from being disclosed to the patient under circumstances when it would be inappropriate (FIG. 18, node 964).
Therapy Alteration Permission Level (TAPL)
The Therapy Alteration Permission Level (TAPL) is a data set that specifies the various levels of authority the DMM has to change patient therapy. The TAPL defines the degree of autonomy that the DMM has to manage a patient's disease without prior human approval. Whenever a patient medical history data item is requested by (say) a government agency or an insurance company, the DMM consults the access control field of that data item to see which sharing permission level is required for it. Then the DMM consults the Permissions database to verify that the requesting agency has access permission at the specified level.
At its most restrictive level, the TAPL requires DMM to notify a physician whenever the DMM determines that the patient could benefit from a change in therapy, and to obtain permission before adjusting therapy in any way. The least restrictive TAPL setting allows the DMM to automatically change a patient's treatment without human intervention. TAPL settings between these extremes require various degrees of prior notification and approval for different therapeutic interventions. The TAPL is used by all DMM functions that change patient therapy or give advice to that effect (FIG. 15, node 830; FIG. 16, node 896).
Meta Structures
Meta Data Array
For the purpose of discussing the medical management system meta functions, a system data structure used to record, track, analyze, and report medical problems can best be visualized as a two-dimensional grid or array called the Meta Data Array. This array lists the causes of disease (e.g., trauma, infection, allergy) along one dimension (the abscissa or x-axis) labeled as CAUSE and lists the anatomic systems or organs affected by disease (e.g., cardiovascular, respiratory, nervous) along a second dimension (the ordinate or y-axis) labeled as ANATOMY. A given disease can then be seen as the cell in the Meta Data Array that is at the intersection of the applicable Cause and Anatomy dimensions.
In implementation, both the Cause and Anatomy axes are, of course, extensively subdivided. Thus, for example, the infection cause is subdivided into bacterial and viral; bacterial is broken down into gram positive and gram negative; gram positive is further broken down into streptococcus, and so on, to the point where the system can identify ultimate causes such as “meningococcal gram negative bacterial infection.” The Anatomy dimension can obviously also be subdivided into organ structures, organs, tissues, cells, and so forth.
Meta Data Cube
As the medical management system has more contacts with a given patient, the additional patient data extends the Meta Data Array along a time dimension to form a Meta Data Cube. The time axis is also referred to as the “Z” axis.
The Meta Data Cube is an internal data structure that supports various meta functions. The details vary, depending on which medical system module is performing which type of meta analysis, but all of the following examples apply:
    • Several episodes of the same complaint (Frequency Meta)
    • Several infections in different anatomic systems (Cause Meta)
    • Different complaints in the same anatomic system (Anatomy Meta)
    • Long-term patient history, e.g., smoking habits over 35 years (Volumetric Meta)
    • Chronic disease history, e.g., five years of Asthma or Malaria attacks
    • Short-term disease progress, e.g., three days of gastrointestinal pain, headaches, vomiting
      Meta Functions
Meta Functions are medically-oriented software objects that operate at a global level of the entire medical management system and its various modules. They observe, record, track, and analyze patient interactions with the system to:
evaluate a patient's use of the system,
look for patterns or relationships that may signify a problem,
“step back” to look at the patient's overall interaction with the system,
analyze a patient's current session in the context of past sessions.
Meta Functions automate that aspect of the human physician that sees a patient as a total, complex bio-mechanism that is malfunctioning and requires corrective measures over a time span. They give the DMM the powerful ability to analyze patient health as a whole, to develop long-term medical diagnoses, therapies, advice, and management strategies.
The Frequency Meta Function uses the Sequential Summing Meta Function to analyze the frequency of consultations regarding the same disease. The Anatomic Meta Function analyzes patient complaints based on the anatomic organ system involved. The Cause-Effect Chaining Meta Function traces a disease back to its cause(s) and then forward to other disease(s). The Area Meta Function and the Volumetric Meta Function analyze changes in disease parameters over time. The Critical Curve Meta Function monitors patient health for significant deterioration by comparing it to a standard curve for the disease being managed. The Interval Meta evaluates the time intervals between consultations for the same disease. The Reliability Meta assesses the probability of data reliability and integrity.
The Meta Functions described for disease management use the same “Meta Data Cube” data structure described in Applicant's patent entitled “Computerized Medical Diagnostic and Treatment Advice System,” U.S. Pat. No. 5,660,176. However, since DM has different objectives, it examines different data elements of the cube along different axes.
The word “meta” refers to the overall nature of these functions, which focus on manipulating health data not at a detailed level but at a level of long-term time trends, global patterns, statistical distributions, and other summary relationships. The word “function” here refers to the various computational and analytical techniques used, which employ classic and fuzzy logic, arithmetic, geometry, trigonometry, analytical geometry, calculus, statistics, probability, domain mappings, transforms (Laplace, Fourier), heuristics, recursion, and so on.
Meta functions are implemented and embodied in the form of suitable data and process structures such as databases, tables, arrays, modules, objects, scripts, lists, subroutines, procedures, functions, and so on.
A. Sequential Summing Meta
The Sequential Summing (SS) Meta function detects and integrates the effect of one patient accessing separate modules of the entire medical management system, such as the diagnostic module and the DMM, because separate sessions—when combined—may represent a significant change or deterioration in the patient. The SS Meta function analyzes the combined effect of the separate modules, and may make a recommendation based on this global analysis.
The SS Meta uses pre-set thresholds for different combinations of the system modules being summed. The thresholds are contained in an internal table that lists all of the module combinations such as medical diagnosis+disease management, medical diagnosis+medical audio/video/image library, medical diagnosis+treatment table consultation, and so on.
For example, if the Medical Diagnosis module was consulted for wheezing and diagnosed as Asthma, and the DM module was later used for Asthma management, and the Medical Audio/Video/Image library module was consulted several times for pre-recorded messages on Asthma, the SS Meta function would use the proper values from the table at medical diagnosis+disease management+medical audio/video/image library for Asthma to calculate a threshold to trigger special recommendations. Thus, even though threshold was not reached in any one module, when the consultations for asthma in the diagnostic, disease management and audio/video/image library consultations are combined and considered together, threshold is reached.
B. Frequency Meta
The Frequency Meta function reviews the number of times that a patient has consulted the system and makes recommendations based on that consultation frequency. The function calculates how many times the patient has interacted with the system for the same complaint or disease, medical audio text consultation or treatment table consultation, uses the Sequential Summing Meta function to analyze the combined effect of the consultations, and may make a recommendation based on this global analysis.
When a patient is admitted to the medical management system, for each disease being managed, a threshold is established for the number of consultations (inbound as well as outbound) per unit of time. The threshold is different for each disease and is modified by the sensitivity factor set. If this threshold is reached, the Frequency Meta function makes a recommendation. That is, the fact alone that the patient has had a certain number of symptom occurrences of a given type may trigger a recommendation from the Frequency Meta functions.
C. Internal Meta
The Interval Meta function analyzes the time intervals between each interaction for the same disease to detect trends that may signify a problem. For example, if the function were to discover that the patient's interactions with the system are occurring closer and closer together, the function could make a recommendation based on this fact alone.
The sequential summing series method is used. The interval between consultations is plotted and a meta recommendation is made if the intervals are getting shorter
D. Cause Meta
The Cause Meta function is a DM background task that looks for disease or cause patterns that may help to identify root causes. The function monitors and analyzes the patient's use of various system modules.
The Cause Meta function identifies a sequential summing series in decreasing intervals of time between medical diagnosis, disease management, medical audio text library, treatment table consultation and all their combinations. For example, assume that a patient has consulted the system on several occasions with complaints manifesting in different parts of the body, and that during each session, the medical diagnosis module has (properly) attributed each separate problem to being caused by infection. The Cause Meta function detects such a series of consultations, and—if they reach a preset threshold per unit time—alerts the system that the root cause may lie in the patient's immune system. If the system is caring for a patient with multiple episodes of trauma, the Cause Meta function will help the system to consider the possibility that the patient is abusing drugs or alcohol.
E. Anatomic Meta
The Anatomic Meta function analyzes patient contacts with the medical system from a viewpoint of a single organ or anatomic system of the body. The function looks for different diseases being managed that may impact the same anatomic system. The function automates the aspect of DM that—when different diseases all affect the same organ—it is often essential to monitor and frequently measure the functioning of that organ.
For example, if a patient consults the medical diagnostic module on three different occasions for abdominal pain, vomiting, and diarrhea, the Anatomic Meta function recognizes that these problems all involve the gastrointestinal tract, and may cause the system to adjust its recommendations based on that additional information.
For example, diabetes mellitus and hypertension both cause slow and progressive deterioration of kidney function. The Anatomic Meta function detects the need for such special monitoring. Based on some internal, preset thresholds, the Anatomic Meta analysis may cause disease management system to recommend an evaluation of the impacted organ functions. In the example above, for a patient being managed for diabetes and hypertension, the Anatomic Meta analysis could cause the medical management system to recommend a serum creatinine, a test of kidney function, at appropriate intervals.
F. Cause vs. Anatomic Meta
The Cause vs. Anatomic Meta function coordinates an interaction between the Cause Meta and Anatomic Meta functions. As the Cause Meta and Anatomy Meta functions interact more closely, their interaction is described here.
As the patient uses the medical management system over time, the Cause/Anatomy cells are stacked along the time or Z-axis, which tracks the moment in time when intersection of the cause and anatomic system, i.e., making the diagnosis actually occurred in the patient.
The Meta Data Cube represents a summation of the patient's interaction with the system over time. Although much of the patient's past history is stored using ICD-9-CM codes, as well as conventional text strings in the fields of the patient's medical record, this technique allows very useful analyses to be done.
It is important to note that the system may be able to assign a cause to a problem without knowing the anatomic system involved, and that the system may indicate what organ or organ system is involved without knowing the cause of the patient's problem. For example, a six-year-old child who complains of muscle aches, headache, runny nose, and joint aching most likely has a viral infection, but it is hard to ascribe a specific organ system in which it is being manifested.
Interestingly, while in the diagnostic module, and while finding multiple problems occurring in the same module, a different pattern is produced in disease management. For example, diabetes can be represented by or at the intersection of an endocrine and the vascular system. But another way to visualize the disease process in diabetes is to go one step further as follows. Whenever the medical management system realizes that another disease process (like diabetes) affects the vascular system, then “vascular” as a CAUSE of further disease is searched.
G. Causal Chaining Meta
The Chaining Meta function automates the analysis of the medical fact that certain diseases produce pathologic changes in other organs of the body, meaning that a disease can cause and be caused by other diseases. For example, the Chaining Meta function looks at a given disease as both cause and effect, and performs three analyses for a given disease D:
    • 1. Find the root cause of D.
    • 2. Find other diseases caused by D.
    • 3. Repeat steps 1 and 2 recursively to find other root causes and other diseases caused by D.
Thus, the Chaining Meta analysis traces the total impact of disease on the body. It uses the Cause Meta function (which is used to detect the immediate, single cause of a complaint or disease) to recursively find remote causes and diseases. Given a starting disease, the Chaining Meta analysis uses the Meta Data Cube to detect patterns that let the analysis go backward in the cause chain to detect other possible problems in a patient. In this way, it does the analysis needed to detect related problems that have so far been masked or have not yet surfaced.
An internal Cause-Effect table used by the Cause-Effect Meta function contains fundamental medical knowledge of anatomic systems, their relationships, their diseases, and disease causality chains. This table identifies patterns that need to be explored for root causes and secondary disease. A second table, used in controlling the processing of the causality chains, contains other data such as probability of occurrence, seriousness of the secondary diseases, and possible therapeutic windows.
The result of the Chaining Meta computation is a list of diseases to check for and monitor in the current patient. These results are useful in:
    • insuring that side effects of disease are not missed,
    • not overlooking disease management therapy needed to stabilize a patient,
    • confirming a cause by verifying other effects (headache is consistent with Appendicitis),
    • negating a cause by not finding required effects (lack of Plasmodia in blood denies Malaria).
      H. Area Meta
An example of area meta can be described as plotting pain or discomfort against time and then integrating the area under the curve to look at the total amount of suffering or discomfort. This is important because many patients, particularly with incurable illness, such as terminal cancer patients, are in continuous pain but they are isolated, do not see their doctor regularly, or their physician does not appreciate how much the patient is suffering. They tend to “chase the pain,” and never catch up. Here, once a threshold of suffering as been met, the patient could get narcotic analgesics or have their dose increased.
I. Volumetric Meta
The Volumetric Meta function performs analysis based on the (3-dimensional) product of Disease×Anatomy×Time and makes recommendations based on pre-set thresholds. The word “volumetric” refers to the Meta Data Cube analysis method used, in which a smoking history appears as the volume enclosed by the three axes P (Poison), R (Respiratory System), and Z (Time). For example, a patient who has smoked two packs of cigarettes daily for 30 years is deemed to have a history of 60 pack-years impacting the respiratory system.
Volumetric analysis is significant in many disease processes. Thus, the patient with a smoking volume of 60 pack-years has accumulated significant damage to the respiratory system. The longer this has been going on, the larger the volume, the more poison has impacted the functioning of the respiratory system, and the more likely certain diagnoses or therapies will be.
Another example of volumetric analysis is the long-term damage that diabetes causes in the microvascular circulation.
The software implementation of the Volumetric Meta function involves various internal disease management tables that list volumetric products for various diseases as well as their threshold parameters. These thresholds (as modified dynamically by the sensitivity factor set) control special actions and analyses of the system. When an applicable threshold is reached, the system performs special analyses and then issues internal alerts to look for possible evidence of damage being done to the applicable organ system(s) and to make special recommendations for the patient.
J. Reliability Meta
The Reliability Meta function looks at the reliability of all of a patient's data items to see if the patient's care is inadequate. The function can recommend the re-evaluation of a patient if it finds that the (separate or combined) probabilities of a diagnosis are below a reliability threshold (modified by the sensitivity factor set).
The function uses internal Reliability Indicators, associated with every data item, that track the probability that the data item reflects the actual health of the patient at the time for which it was recorded. These Reliability Indicators are established for every data item in the medical management system when it is first established, and remain associated with it throughout its life in the system.
For example, if a patient tells the system that he has a history of migraine headaches, the system may ask the patient:
    • Who made the diagnosis of migraine (patient, friend, nurse, physician, or neurologist)?
    • What tests were run, by whom, on what tissue, with what results?
    • Who confirmed the tests, how, in what context?
The idea, of course, is that if a headache specialist made the diagnosis after a full and complete workup including imaging (MRI) of the brain, lumbar puncture, EEG, etc., the probability that the diagnosis is correct is very high. This will be recorded in the Reliability Indicators and associated with the diagnosis data item. If the reliability is too low, the patient will be scheduled for re-evaluation at a higher level or standard of care, which will invoke more precise and more thorough questioning.
Benefits of Disease Management
The benefits of the medical management system and the Disease Management Module are as follows:
Benefits to Patients
    • faster, easier, cheaper medical services
    • medical service accessible at off hours, from home, when needed
    • medical service accessible in remote locations, poor communities
    • the latest, best, tested, updated medical services
    • patients can take their time, can repeat sessions, can browse
    • patients have a complete medical history on file
Benefits to Health Care Providers
    • reduces trivial, inappropriate, useless contacts with patients
    • hones doctor's diagnostic skills/experience
    • doctor can compare own opinion to others
    • repeat patients offer better, continuous medical records
    • providers can access more medical data resources
    • computer supports access to statistics, databases, decision-making, scheduling
    • history of sessions and diseases is available
    • providers can justify advice/actions based on logged responses
    • can compare patients across/along populations
    • have large database of cases
      Benefits to Health Care Managers
    • saves costs of trivial contacts
    • tracks contacts
    • statistical information and projections
    • profiles doctor/hospital practices
    • session logs reduce legal liability and exposure
    • ensures compliance with policies
    • standardizes advice and treatment
      Benefits to Health Care Regulators
    • actions of HMOs, Physicians can be reviewed and assessed
    • medical records are available for critiques
    • can verify compliance with regulations
      Benefits to Health Care Teachers
    • medical practice can be simulated on large patient populations
    • aids study of medicine
    • case studies can be compared
    • case handling can be repeated, with changes
While the above detailed description has shown, described, and pointed out the fundamental novel features of the invention as applied to various embodiments, it will be understood that various omissions and substitutions and changes in the form and details of the system illustrated may be made by those skilled in the art, without departing from the spirit of the invention.

Claims (16)

The invention claimed is:
1. A patient medication therapy self-management method, utilizing a non-transitory computer readable medium, operating a computer readable program code, configured to provide therapy according to patient self-assessed pain, the computer readable code comprising instructions that are executed by a computer device or processor, causing the processor to perform the steps of:
storing, in a data storage accessible to the program code,
(a) a listing of aspect words describing a pain and at least one of a degree or description of the pain; and
(b) a therapy alteration permission level (TAPL) limiting available therapy changes;
receiving, via direct interactive dialog between the patient and the computer device or processor, a patient self-selection of an aspect word from the listing of aspect words, the self-selection describing a pain experienced by the patient, the computer device or processor providing an interface configured to engage the patient in the direct interactive dialog;
converting the received aspect word into an integer subcode that represents the received aspect word; and
altering the patient's therapy within the limitations of the TAPL based on at least one of the integer subcodes.
2. The method of claim 1, wherein the listing of aspect words further includes at least one of provocative, quality, region, severity, and timing.
3. The method of claim 1, wherein the TAPL further includes a limitation applicable to at least one of: a maximum and minimum dosage change associated with a current therapy of the patient, a drug class, a drug type, a drug brand, a dose, a route, a mode of drug administration, a formulation, a timing, and a frequency.
4. The method of claim 1, wherein the available therapy changes further include at least one of: an increased dosage, a decreased dosage, a new treatment, a drug class, a drug type, a drug brand, a dose, a route, a mode of drug administration, a formulation, a timing, and a frequency.
5. The method of claim 1, wherein the integer subcode that represents the received aspect word further identifies at least one of location, sensation, or frequency.
6. The method of claim 1, wherein the medication therapy self-management further includes therapy changes based on a subjective patient description of pain factored by a subjective objective correlation factor (SOCF).
7. The method of claim 4, wherein the available therapy changes further include an increase or decrease of dosage in conformance with a treatment table factored by a subjective objective correlation factor (SOCF).
8. The method of claim 4, wherein the new treatment further includes an additional or substitute therapy type.
9. A system for patient medication therapy self-management, the system comprising:
a computer readable medium having non-transitory computer readable program code embodied therein for providing therapy according to patient self-assessed pain, the computer readable program code executed by a computer device or processor;
a data storage accessible to the program code, the data storage configured to store;
(a) a listing of aspect words describing a pain and at least one of a degree or description of the pain;
(b) a therapy alteration permission level (TAPL) limiting available therapy changes;
(c) a patient self-selection of an aspect word from the listing of aspect words, the self-selection received via direct interactive dialog between the patient and the computer device or processor, the computer device or processor providing an interface configured to engage the patient in the direct interactive dialog, the self-selection describing a pain experienced by the patient; and
(d) a conversion of the received patient self-selection of an aspect word into an integer subcode, the subcode representing the received aspect word;
wherein the computer device or processor alters the patient's therapy within the limitations of the TAPL based on at least one of the integer subcodes.
10. The system of claim 9, wherein the listing of aspect words further includes at least one of provocative, quality, region, severity, and timing.
11. The system of claim 9, wherein the TAPL further includes a limitation applicable to at least one of: a maximum and minimum dosage change associated with a current therapy of the patient, a drug class, a drug type, a drug brand, a dose, a route, a mode of drug administration, a formulation, a timing, and a frequency.
12. The system of claim 9, wherein the available therapy changes further include at least one of: an increased dosage, a decreased dosage, a new treatment, a drug class, a drug type, a drug brand, a dose, a route, a mode of drug administration, a formulation, a timing, and a frequency.
13. The system of claim 9, wherein the integer subcode that represents the received aspect word further identifies at least one of location, sensation, or frequency.
14. The system of claim 9, wherein the medication therapy self-management further includes therapy changes based on a subjective patient description of pain factored by a subjective objective correlation factor (SOCF).
15. The system of claim 12, wherein the available therapy changes further include an increase or decrease of dosage in conformance with a treatment table factored by a subjective objective correlation factor (SOCF).
16. The system of claim 12, wherein the new treatment further includes an additional or substitute therapy type.
US13/236,996 1997-03-13 2011-09-20 Disease management system and method including medication therapy self-management Expired - Fee Related US8628470B1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US13/236,996 US8628470B1 (en) 1997-03-13 2011-09-20 Disease management system and method including medication therapy self-management

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
US4052297P 1997-03-13 1997-03-13
US09/042,075 US6234964B1 (en) 1997-03-13 1998-03-13 Disease management system and method
US09/818,187 US20010012913A1 (en) 1997-03-13 2001-03-26 Disease management system and method including correlation assessment
US10/261,919 US7297108B2 (en) 1997-03-13 2002-10-01 Disease management system and method including analysis of disease specific changes
US11/933,077 US8066636B2 (en) 1997-03-13 2007-10-31 Disease management system and method including pain code
US13/236,996 US8628470B1 (en) 1997-03-13 2011-09-20 Disease management system and method including medication therapy self-management

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US11/933,077 Continuation US8066636B2 (en) 1997-03-13 2007-10-31 Disease management system and method including pain code

Publications (1)

Publication Number Publication Date
US8628470B1 true US8628470B1 (en) 2014-01-14

Family

ID=21911437

Family Applications (18)

Application Number Title Priority Date Filing Date
US09/042,075 Expired - Lifetime US6234964B1 (en) 1997-03-13 1998-03-13 Disease management system and method
US09/818,187 Abandoned US20010012913A1 (en) 1997-03-13 2001-03-26 Disease management system and method including correlation assessment
US10/261,919 Expired - Fee Related US7297108B2 (en) 1997-03-13 2002-10-01 Disease management system and method including analysis of disease specific changes
US10/368,681 Expired - Lifetime US6770029B2 (en) 1997-03-13 2003-02-13 Disease management system and method including correlation assessment
US11/927,630 Expired - Fee Related US8740790B2 (en) 1997-03-13 2007-10-29 Disease management system and method
US11/929,472 Expired - Fee Related US8682694B2 (en) 1997-03-13 2007-10-30 Disease management system and method including permission database
US11/929,609 Expired - Fee Related US8060378B2 (en) 1997-03-13 2007-10-30 Disease management system and method including question version
US11/929,836 Abandoned US20080052130A1 (en) 1997-03-13 2007-10-30 Disease management system and method including therapy optimization
US11/933,098 Expired - Fee Related US7769600B2 (en) 1997-03-13 2007-10-31 Disease management system and method
US11/933,077 Expired - Fee Related US8066636B2 (en) 1997-03-13 2007-10-31 Disease management system and method including pain code
US11/933,205 Expired - Fee Related US8663104B2 (en) 1997-03-13 2007-10-31 Disease management system and method including therapeutic alterations permission level
US11/930,778 Expired - Fee Related US8630875B2 (en) 1997-03-13 2007-10-31 Disease management system and health assessment method
US11/932,811 Expired - Fee Related US8727976B2 (en) 1997-03-13 2007-10-31 Disease management system operating on a network
US11/930,792 Expired - Fee Related US8727979B2 (en) 1997-03-13 2007-10-31 Disease management system and method including significant symptom filtering
US11/933,167 Expired - Fee Related US7993267B2 (en) 1997-03-13 2007-10-31 Disease management system including a no response method
US11/933,150 Expired - Fee Related US8392217B2 (en) 1997-03-13 2007-10-31 Disease management system and method including preview mode
US13/196,173 Abandoned US20120029935A1 (en) 1997-03-13 2011-08-02 Disease management system including a no response method
US13/236,996 Expired - Fee Related US8628470B1 (en) 1997-03-13 2011-09-20 Disease management system and method including medication therapy self-management

Family Applications Before (17)

Application Number Title Priority Date Filing Date
US09/042,075 Expired - Lifetime US6234964B1 (en) 1997-03-13 1998-03-13 Disease management system and method
US09/818,187 Abandoned US20010012913A1 (en) 1997-03-13 2001-03-26 Disease management system and method including correlation assessment
US10/261,919 Expired - Fee Related US7297108B2 (en) 1997-03-13 2002-10-01 Disease management system and method including analysis of disease specific changes
US10/368,681 Expired - Lifetime US6770029B2 (en) 1997-03-13 2003-02-13 Disease management system and method including correlation assessment
US11/927,630 Expired - Fee Related US8740790B2 (en) 1997-03-13 2007-10-29 Disease management system and method
US11/929,472 Expired - Fee Related US8682694B2 (en) 1997-03-13 2007-10-30 Disease management system and method including permission database
US11/929,609 Expired - Fee Related US8060378B2 (en) 1997-03-13 2007-10-30 Disease management system and method including question version
US11/929,836 Abandoned US20080052130A1 (en) 1997-03-13 2007-10-30 Disease management system and method including therapy optimization
US11/933,098 Expired - Fee Related US7769600B2 (en) 1997-03-13 2007-10-31 Disease management system and method
US11/933,077 Expired - Fee Related US8066636B2 (en) 1997-03-13 2007-10-31 Disease management system and method including pain code
US11/933,205 Expired - Fee Related US8663104B2 (en) 1997-03-13 2007-10-31 Disease management system and method including therapeutic alterations permission level
US11/930,778 Expired - Fee Related US8630875B2 (en) 1997-03-13 2007-10-31 Disease management system and health assessment method
US11/932,811 Expired - Fee Related US8727976B2 (en) 1997-03-13 2007-10-31 Disease management system operating on a network
US11/930,792 Expired - Fee Related US8727979B2 (en) 1997-03-13 2007-10-31 Disease management system and method including significant symptom filtering
US11/933,167 Expired - Fee Related US7993267B2 (en) 1997-03-13 2007-10-31 Disease management system including a no response method
US11/933,150 Expired - Fee Related US8392217B2 (en) 1997-03-13 2007-10-31 Disease management system and method including preview mode
US13/196,173 Abandoned US20120029935A1 (en) 1997-03-13 2011-08-02 Disease management system including a no response method

Country Status (12)

Country Link
US (18) US6234964B1 (en)
EP (1) EP0966719A1 (en)
JP (1) JP2002512712A (en)
CN (2) CN1604111A (en)
AU (4) AU762361B2 (en)
CA (1) CA2284168A1 (en)
ID (1) ID23390A (en)
IL (2) IL131873A0 (en)
NZ (1) NZ337954A (en)
TW (1) TW424188B (en)
UA (1) UA64743C2 (en)
WO (1) WO1998040835A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140107461A1 (en) * 2012-10-15 2014-04-17 ClinicalBox, Inc. Adaptive Medical Testing

Families Citing this family (626)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7624028B1 (en) 1992-11-17 2009-11-24 Health Hero Network, Inc. Remote health monitoring and maintenance system
US5307263A (en) 1992-11-17 1994-04-26 Raya Systems, Inc. Modular microprocessor-based health monitoring system
US20010011224A1 (en) 1995-06-07 2001-08-02 Stephen James Brown Modular microprocessor-based health monitoring system
US6968375B1 (en) * 1997-03-28 2005-11-22 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US9215979B2 (en) * 1992-11-17 2015-12-22 Robert Bosch Healthcare Systems, Inc. Multi-user remote health monitoring system
AU1766201A (en) 1992-11-17 2001-05-30 Health Hero Network, Inc. Method and system for improving adherence with a diet program or other medical regimen
US5660176A (en) * 1993-12-29 1997-08-26 First Opinion Corporation Computerized medical diagnostic and treatment advice system
US6206829B1 (en) 1996-07-12 2001-03-27 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
US5935060A (en) 1996-07-12 1999-08-10 First Opinion Corporation Computerized medical diagnostic and treatment advice system including list based processing
USRE43433E1 (en) 1993-12-29 2012-05-29 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US6680999B1 (en) * 1995-08-15 2004-01-20 Mumps Audiofax, Inc. Interactive telephony system
WO1998029790A2 (en) 1996-12-30 1998-07-09 Imd Soft Ltd. Medical information system
CA2284168A1 (en) 1997-03-13 1998-09-17 First Opinion Corporation Disease management system
US6082776A (en) * 1997-05-07 2000-07-04 Feinberg; Lawrence E. Storing personal medical information
US6597392B1 (en) * 1997-10-14 2003-07-22 Healthcare Vision, Inc. Apparatus and method for computerized multi-media data organization and transmission
US7885822B2 (en) * 2001-05-09 2011-02-08 William Rex Akers System and method for electronic medical file management
US7956894B2 (en) * 1997-10-14 2011-06-07 William Rex Akers Apparatus and method for computerized multi-media medical and pharmaceutical data organization and transmission
US6449355B1 (en) * 1997-12-19 2002-09-10 Mediaone Group, Inc. Method and system for providing assistance to users of a service
US6546545B1 (en) * 1998-03-05 2003-04-08 American Management Systems, Inc. Versioning in a rules based decision management system
US8882666B1 (en) 1998-05-08 2014-11-11 Ideal Life Inc. Personal health monitoring and/or communication system
DE19824787C2 (en) * 1998-06-03 2000-05-04 Paul Pere Procedure for secure access to data in a network
US6872187B1 (en) 1998-09-01 2005-03-29 Izex Technologies, Inc. Orthoses for joint rehabilitation
DE19842046A1 (en) * 1998-09-14 2000-03-16 Siemens Ag Medical analysis data generation system
JP2002531884A (en) * 1998-11-30 2002-09-24 ノボ ノルディスク アクティーゼルスカブ Method and system for assisting a user in self-treatment involving multiple actions
WO2000033236A1 (en) * 1998-11-30 2000-06-08 Health Hero Network, Inc. System and method for improving a risk for a monitored client
JP4487054B2 (en) * 1998-12-17 2010-06-23 バイオフィリア研究所有限会社 Lower limb function training device
US20090076857A1 (en) * 1999-02-19 2009-03-19 Cerner Innovation, Inc. Systems and methods for managing patient pharmaceutical care
US6223165B1 (en) 1999-03-22 2001-04-24 Keen.Com, Incorporated Method and apparatus to connect consumer to expert
US7647234B1 (en) * 1999-03-24 2010-01-12 Berkeley Heartlab, Inc. Cardiovascular healthcare management system and method
US7107253B1 (en) * 1999-04-05 2006-09-12 American Board Of Family Practice, Inc. Computer architecture and process of patient generation, evolution and simulation for computer based testing system using bayesian networks as a scripting language
AUPP962599A0 (en) 1999-04-07 1999-04-29 Liberty Financial Pty Ltd Application apparatus and method
US20100198755A1 (en) * 1999-04-09 2010-08-05 Soll Andrew H Enhanced medical treatment
US7593952B2 (en) * 1999-04-09 2009-09-22 Soll Andrew H Enhanced medical treatment system
US20070021979A1 (en) * 1999-04-16 2007-01-25 Cosentino Daniel L Multiuser wellness parameter monitoring system
US7945451B2 (en) * 1999-04-16 2011-05-17 Cardiocom, Llc Remote monitoring system for ambulatory patients
US7577475B2 (en) 1999-04-16 2009-08-18 Cardiocom System, method, and apparatus for combining information from an implanted device with information from a patient monitoring apparatus
US8438038B2 (en) * 1999-04-16 2013-05-07 Cardiocom, Llc Weight loss or weight management system
US6290646B1 (en) * 1999-04-16 2001-09-18 Cardiocom Apparatus and method for monitoring and communicating wellness parameters of ambulatory patients
US20060030890A1 (en) * 1999-04-16 2006-02-09 Cosentino Daniel L System, method, and apparatus for automated interactive verification of an alert generated by a patient monitoring device
US8419650B2 (en) 1999-04-16 2013-04-16 Cariocom, LLC Downloadable datasets for a patient monitoring system
US6270457B1 (en) * 1999-06-03 2001-08-07 Cardiac Intelligence Corp. System and method for automated collection and analysis of regularly retrieved patient information for remote patient care
US7134996B2 (en) * 1999-06-03 2006-11-14 Cardiac Intelligence Corporation System and method for collection and analysis of patient information for automated remote patient care
US6312378B1 (en) * 1999-06-03 2001-11-06 Cardiac Intelligence Corporation System and method for automated collection and analysis of patient information retrieved from an implantable medical device for remote patient care
US7429243B2 (en) * 1999-06-03 2008-09-30 Cardiac Intelligence Corporation System and method for transacting an automated patient communications session
US7650291B2 (en) * 1999-06-23 2010-01-19 Koninklijke Philips Electronics N.V. Video visitation system and method for a health care location
US7454360B2 (en) * 1999-06-23 2008-11-18 Visicu, Inc. Order evaluation system for use in a healthcare location
US7454359B2 (en) * 1999-06-23 2008-11-18 Visicu, Inc. System and method for displaying a health status of hospitalized patients
US7256708B2 (en) * 1999-06-23 2007-08-14 Visicu, Inc. Telecommunications network for remote patient monitoring
US7321862B2 (en) * 1999-06-23 2008-01-22 Visicu, Inc. System and method for patient-worn monitoring of patients in geographically dispersed health care locations
US7475019B2 (en) * 1999-11-18 2009-01-06 Visicu, Inc. System and method for physician note creation and management
US7467094B2 (en) * 1999-06-23 2008-12-16 Visicu, Inc. System and method for accounting and billing patients in a hospital environment
US7433827B2 (en) 1999-06-23 2008-10-07 Visicu, Inc. System and method for displaying a health status of hospitalized patients
US8175895B2 (en) * 1999-06-23 2012-05-08 Koninklijke Philips Electronics N.V. Remote command center for patient monitoring
US7315825B2 (en) * 1999-06-23 2008-01-01 Visicu, Inc. Rules-based patient care system for use in healthcare locations
US7991625B2 (en) * 1999-06-23 2011-08-02 Koninklijke Philips Electronics N.V. System for providing expert care to a basic care medical facility from a remote location
US7411509B2 (en) * 1999-06-23 2008-08-12 Visicu, Inc. System and method for observing patients in geographically dispersed health care locations
US7395216B2 (en) 1999-06-23 2008-07-01 Visicu, Inc. Using predictive models to continuously update a treatment plan for a patient in a health care location
US7416537B1 (en) 1999-06-23 2008-08-26 Izex Technologies, Inc. Rehabilitative orthoses
CA2314517A1 (en) * 1999-07-26 2001-01-26 Gust H. Bardy System and method for determining a reference baseline of individual patient status for use in an automated collection and analysis patient care system
US6221011B1 (en) * 1999-07-26 2001-04-24 Cardiac Intelligence Corporation System and method for determining a reference baseline of individual patient status for use in an automated collection and analysis patient care system
CA2314513A1 (en) * 1999-07-26 2001-01-26 Gust H. Bardy System and method for providing normalized voice feedback from an individual patient in an automated collection and analysis patient care system
US6754883B2 (en) * 1999-08-24 2004-06-22 Ge Medical Systems Information Technologies, Inc. Modular analysis and standardization system
US20030195774A1 (en) * 1999-08-30 2003-10-16 Abbo Fred E. Medical practice management system
WO2001024098A2 (en) * 1999-09-13 2001-04-05 Healinx A message and program system supporting communication
US6454705B1 (en) * 1999-09-21 2002-09-24 Cardiocom Medical wellness parameters management system, apparatus and method
US6611846B1 (en) * 1999-10-30 2003-08-26 Medtamic Holdings Method and system for medical patient data analysis
US20040078236A1 (en) * 1999-10-30 2004-04-22 Medtamic Holdings Storage and access of aggregate patient data for analysis
US6876991B1 (en) 1999-11-08 2005-04-05 Collaborative Decision Platforms, Llc. System, method and computer program product for a collaborative decision platform
US6411840B1 (en) 1999-11-16 2002-06-25 Cardiac Intelligence Corporation Automated collection and analysis patient care system and method for diagnosing and monitoring the outcomes of atrial fibrillation
US6368284B1 (en) * 1999-11-16 2002-04-09 Cardiac Intelligence Corporation Automated collection and analysis patient care system and method for diagnosing and monitoring myocardial ischemia and outcomes thereof
US6336903B1 (en) 1999-11-16 2002-01-08 Cardiac Intelligence Corp. Automated collection and analysis patient care system and method for diagnosing and monitoring congestive heart failure and outcomes thereof
US6398728B1 (en) * 1999-11-16 2002-06-04 Cardiac Intelligence Corporation Automated collection and analysis patient care system and method for diagnosing and monitoring respiratory insufficiency and outcomes thereof
US8369937B2 (en) 1999-11-16 2013-02-05 Cardiac Pacemakers, Inc. System and method for prioritizing medical conditions
US6440066B1 (en) * 1999-11-16 2002-08-27 Cardiac Intelligence Corporation Automated collection and analysis patient care system and method for ordering and prioritizing multiple health disorders to identify an index disorder
US6632429B1 (en) 1999-12-17 2003-10-14 Joan M. Fallon Methods for treating pervasive development disorders
US6510340B1 (en) * 2000-01-10 2003-01-21 Jordan Neuroscience, Inc. Method and apparatus for electroencephalography
RU2286711C2 (en) 2000-02-14 2006-11-10 Фёрст Опинион Корпорэйшн System and method for automatic diagnostics
CN1531702A (en) * 2000-02-14 2004-09-22 巴克斯特国际公司 Method and system for providing user specific information via communications network
US6893396B2 (en) * 2000-03-01 2005-05-17 I-Medik, Inc. Wireless internet bio-telemetry monitoring system and interface
US20010047281A1 (en) * 2000-03-06 2001-11-29 Keresman Michael A. Secure on-line authentication system for processing prescription drug fulfillment
US6383136B1 (en) * 2000-03-06 2002-05-07 Charlyn Jordan Health analysis and forecast of abnormal conditions
US7542913B1 (en) * 2000-03-08 2009-06-02 Careguide, Inc. System and method of predicting high utilizers of healthcare services
US7379885B1 (en) * 2000-03-10 2008-05-27 David S. Zakim System and method for obtaining, processing and evaluating patient information for diagnosing disease and selecting treatment
US20020049612A1 (en) * 2000-03-23 2002-04-25 Jaeger Scott H. Method and system for clinical knowledge management
EP1267708A4 (en) * 2000-03-29 2006-04-12 Univ Virginia Method, system, and computer program product for the evaluation of glycemic control in diabetes from self-monitoring data
JP2004502995A (en) * 2000-04-13 2004-01-29 ホスピタルケアオンラインドットコム インク Remote patient management
US20030036683A1 (en) * 2000-05-01 2003-02-20 Kehr Bruce A. Method, system and computer program product for internet-enabled, patient monitoring system
US7367950B1 (en) * 2000-05-13 2008-05-06 Omegawave, Llc Distributed apparatus and method for non-invasive measurement of functional state and adaptive response
US20010050088A1 (en) * 2000-06-09 2001-12-13 Gary Leeds Method for prevention/rehabilitation customization
EP1294272B1 (en) * 2000-06-22 2007-08-15 Fridolin Voegeli System for maintenance and management of health
US6742895B2 (en) * 2000-07-06 2004-06-01 Alan L. Robin Internet-based glaucoma diagnostic system
JP2004504038A (en) 2000-07-13 2004-02-12 ザ ジョンズ ホプキンス ユニバーシティー スクール オブ メディシン Detection and treatment of polycystic kidney disease
JP2002032484A (en) * 2000-07-14 2002-01-31 Nec Corp System and method for health management and recording medium with recorded program for health management
US8924236B2 (en) * 2000-07-20 2014-12-30 Marfly 1, LP Record system
US20030050803A1 (en) * 2000-07-20 2003-03-13 Marchosky J. Alexander Record system
WO2002008941A1 (en) * 2000-07-20 2002-01-31 Marchosky J Alexander Patient-controlled automated medical record, diagnosis, and treatment system and method
EP1304956A4 (en) * 2000-08-02 2004-04-14 Healthshore Inc Online medical evaluation and treatment system, method and portal
US20070053895A1 (en) 2000-08-14 2007-03-08 Fallon Joan M Method of treating and diagnosing parkinsons disease and related dysautonomic disorders
IL138123A0 (en) * 2000-08-28 2001-10-31 Accuramed 1999 Ltd Medical decision support system and method
US20020120471A1 (en) * 2000-08-30 2002-08-29 Healtheheart, Inc. Patient analysis and research system and associated methods
AU2001286901A1 (en) * 2000-08-30 2002-03-13 Healtheheart, Inc. Patient analysis and risk reduction system and associated methods including the use of patient monitored data
WO2002019245A2 (en) * 2000-08-30 2002-03-07 Healtheheart, Inc. Patient analysis and risk reduction system and associated methods
US7447643B1 (en) 2000-09-21 2008-11-04 Theradoc.Com, Inc. Systems and methods for communicating between a decision-support system and one or more mobile information devices
WO2002025528A1 (en) 2000-09-21 2002-03-28 Theradoc.Com, Inc. Systems and methods for manipulating medical data via a decision support system
JP2004533660A (en) * 2000-10-18 2004-11-04 ジヨンソン・アンド・ジヨンソン・コンシユーマー・カンパニーズ・インコーポレーテツド Intelligent performance-based product recommendation system
US7734480B2 (en) * 2000-11-13 2010-06-08 Peter Stangel Clinical care utilization management system
US7860729B2 (en) * 2000-11-13 2010-12-28 Peter Stangel Clinical care utilization management system
US8030002B2 (en) 2000-11-16 2011-10-04 Curemark Llc Methods for diagnosing pervasive development disorders, dysautonomia and other neurological conditions
JP2002189809A (en) * 2000-12-21 2002-07-05 Kyoukosan Kk Managing method for function recovery exercise and muscular strength intensifying exercise
US6551243B2 (en) * 2001-01-24 2003-04-22 Siemens Medical Solutions Health Services Corporation System and user interface for use in providing medical information and health care delivery support
GB2372923B (en) 2001-01-29 2005-05-25 Hewlett Packard Co Audio user interface with selective audio field expansion
GB2374501B (en) 2001-01-29 2005-04-13 Hewlett Packard Co Facilitation of clear presenentation in audio user interface
GB2374772B (en) 2001-01-29 2004-12-29 Hewlett Packard Co Audio user interface
GB2376123B (en) 2001-01-29 2004-06-30 Hewlett Packard Co Facilitation of speech recognition in user interface
US7756722B2 (en) * 2001-02-01 2010-07-13 Georgetown University Clinical management system from chronic illnesses using telecommunication
US20020133402A1 (en) 2001-03-13 2002-09-19 Scott Faber Apparatus and method for recruiting, communicating with, and paying participants of interactive advertising
CA2378605A1 (en) * 2001-03-14 2002-09-14 Peakcare, Llc Method for prevention/rehabilitation customization
EP1397068A2 (en) * 2001-04-02 2004-03-17 Therasense, Inc. Blood glucose tracking apparatus and methods
US7353023B1 (en) * 2001-04-02 2008-04-01 At&T Delaware Intellectual Property, Inc. Method and apparatus for delivering messages to wireless devices
US8396720B2 (en) * 2001-04-05 2013-03-12 Numoda Technologies, Inc. Patient diagnosis using triage protocols that have customized messages at exit points
JP4498636B2 (en) 2001-04-27 2010-07-07 日本サーモスタット株式会社 Thermostat device
US7526112B2 (en) 2001-04-30 2009-04-28 Chase Medical, L.P. System and method for facilitating cardiac intervention
US20070214002A1 (en) * 2001-04-30 2007-09-13 Smith James C System for outpatient treatment of chronic health conditions
US7327862B2 (en) * 2001-04-30 2008-02-05 Chase Medical, L.P. System and method for facilitating cardiac intervention
US7103578B2 (en) * 2001-05-25 2006-09-05 Roche Diagnostics Operations, Inc. Remote medical device access
US6974328B2 (en) * 2001-06-08 2005-12-13 Noyo Nordisk Pharmaceuticals, Inc. Adaptive interactive preceptored teaching system
US7179226B2 (en) * 2001-06-21 2007-02-20 Animas Corporation System and method for managing diabetes
US20030013946A1 (en) * 2001-06-28 2003-01-16 Boehringer Ingelheim International Gmbh System and method for assisting in diagnosis, therapy and/or monitoring of a functional lung disease
US20030149592A1 (en) * 2001-07-12 2003-08-07 Roman Linda L. Patient qualifying and selection process
US20030125609A1 (en) * 2001-08-03 2003-07-03 Robert Becker Method for reliable measurement in medical care and patient self monitoring
US7716069B2 (en) * 2001-08-06 2010-05-11 Ulrich Medical Concepts Inc System and method for implementing medical risk algorithms at the point of care
AUPR724701A0 (en) * 2001-08-24 2001-09-20 Medivision (Intl) Pty Ltd Method and system for assisting a professional person to advise a client
DE10143712A1 (en) * 2001-08-30 2003-04-10 Europroteome Ag Process, computer system and computer program product for data evaluation
US6704403B2 (en) * 2001-09-05 2004-03-09 Ingenio, Inc. Apparatus and method for ensuring a real-time connection between users and selected service provider using voice mail
DE10148838C2 (en) * 2001-10-04 2003-07-31 Siemens Ag Method and device for remotely monitoring an effect of a medicament
US7904314B2 (en) * 2001-10-17 2011-03-08 Siemens Medical Solutions Usa, Inc. System and method for ordering patient specific healthcare services
US7051012B2 (en) * 2001-10-22 2006-05-23 Siemens Medical Solutions Health Services Corporation User interface system for maintaining organization related information for use in supporting organization operation
WO2003036590A1 (en) 2001-10-26 2003-05-01 Concordant Rater Systems Llc Computer system and method for training, certifying or monitoring human clinical raters
DE10247459A1 (en) * 2001-10-31 2003-07-03 Caterpillar Inc Health information analysis method and system
NL1019277C2 (en) * 2001-11-01 2003-05-07 Vivici Device for making a diagnosis.
US20030171660A1 (en) * 2001-11-13 2003-09-11 Foster Thomas V. System and method for obtaining patient information
US6991464B2 (en) * 2001-12-28 2006-01-31 Expert Clinical Systems, Inc. Web-based medical diagnostic and training system
EP1492439A2 (en) * 2002-01-04 2005-01-05 Canswers LLC Systems and methods for predicting disease behavior
US7730063B2 (en) * 2002-12-10 2010-06-01 Asset Trust, Inc. Personalized medicine service
US6997717B2 (en) 2002-03-20 2006-02-14 University Of Iowa Research Foundation Method and system for point of need continuing education delivery
US20060089853A1 (en) * 2002-03-29 2006-04-27 Daniel Gauvin Multi-agent distributed environment for a hierarchical medical environment
EP1352607A1 (en) * 2002-04-10 2003-10-15 Siemens Aktiengesellschaft Method and system for monitoring the course of progress of a medical treatment
EP1498067A1 (en) * 2002-04-25 2005-01-19 Matsushita Electric Industrial Co., Ltd. Dosage determination supporting device, injector, and health management supporting system
US7117158B2 (en) * 2002-04-25 2006-10-03 Bilcare, Inc. Systems, methods and computer program products for designing, deploying and managing interactive voice response (IVR) systems
US7080098B2 (en) * 2002-05-02 2006-07-18 Smirniotopoulos James G Medical multimedia database system
US7865371B2 (en) * 2002-05-10 2011-01-04 Shen Michael Y Management of information flow and workflow in medical imaging services
JP4310964B2 (en) * 2002-05-22 2009-08-12 コニカミノルタホールディングス株式会社 Image forming apparatus
EP1351181B1 (en) 2002-06-10 2003-10-29 Medvantis Medical Services GmbH Computer system and method for acquiring data to determine the progression of a chronic disease
AU2003204745A1 (en) * 2002-06-17 2004-01-15 Shigeo Takizawa Rehabilitation device
DE10227542A1 (en) * 2002-06-20 2004-01-15 Merck Patent Gmbh Process and system for recording and analyzing clinical pictures and their causes as well as for determining suitable therapy proposals
US20040078221A1 (en) * 2002-07-16 2004-04-22 Yi-Yun Chen MediCAD Chinese medical system
FR2843215B1 (en) * 2002-07-30 2017-02-10 Voluntis METHOD AND SYSTEM FOR ESTABLISHING A VIRTUAL PLATFORM FOR ENABLING OPERATORS TO EXCHANGE INFORMATION REGARDING PATHOLOGY MANAGEMENT
US20030088365A1 (en) * 2002-08-01 2003-05-08 Robert Becker System and method of drug development for selective drug use with individual, treatment responsive patients, and applications of the method in medical care
NL1021322C2 (en) * 2002-08-22 2004-02-24 Antromed B V Information system based on mobile Internet involves users employing mobile-cellular telephones on basis of previously determined payment conditions to obtain access to premium Internet site, preferably an I-mode system or similar
US7835926B1 (en) 2002-08-29 2010-11-16 Telehealth Broadband Llc Method for conducting a home health session using an integrated television-based broadband home health system
US10009577B2 (en) 2002-08-29 2018-06-26 Comcast Cable Communications, Llc Communication systems
US7185282B1 (en) * 2002-08-29 2007-02-27 Telehealth Broadband, Llc Interface device for an integrated television-based broadband home health system
US20060278242A1 (en) * 2005-03-23 2006-12-14 Mcglennen Ronald C Apparatus and methods for medical testing
US8594948B2 (en) * 2002-09-18 2013-11-26 Ronald C. McGlennen Apparatus and methods for medical testing
US8744868B2 (en) * 2002-10-08 2014-06-03 Omnicare, Inc. Method for storing and reporting pharmacy data
US20040087836A1 (en) * 2002-10-31 2004-05-06 Green Michael R. Computer system and method for closed-loop support of patient self-testing
EP1579357A4 (en) * 2002-11-22 2007-09-05 John D Bixler Autism treatment system and method
US20040103001A1 (en) * 2002-11-26 2004-05-27 Mazar Scott Thomas System and method for automatic diagnosis of patient health
CN1745390A (en) * 2002-12-03 2006-03-08 美国西门子医疗解决公司 Systems and methods for automated extraction and processing of billing information in patient records
US7189204B2 (en) 2002-12-04 2007-03-13 Cardiac Pacemakers, Inc. Sleep detection using an adjustable threshold
US20040111278A1 (en) * 2002-12-06 2004-06-10 Brown Gary C. Method of quantifying loss of quality of life resulting from personal injury for tort cases
US20040111293A1 (en) * 2002-12-09 2004-06-10 Catherine Firanek System and a method for tracking patients undergoing treatment and/or therapy for renal disease
US7890341B2 (en) * 2002-12-09 2011-02-15 Baxter International Inc. System and a method for providing integrated access management for peritoneal dialysis and hemodialysis
US7187790B2 (en) * 2002-12-18 2007-03-06 Ge Medical Systems Global Technology Company, Llc Data processing and feedback method and system
US20040122787A1 (en) * 2002-12-18 2004-06-24 Avinash Gopal B. Enhanced computer-assisted medical data processing system and method
US20040122707A1 (en) * 2002-12-18 2004-06-24 Sabol John M. Patient-driven medical data processing system and method
US20040122706A1 (en) * 2002-12-18 2004-06-24 Walker Matthew J. Patient data acquisition system and method
US20040122719A1 (en) * 2002-12-18 2004-06-24 Sabol John M. Medical resource processing system and method utilizing multiple resource type data
US20040122704A1 (en) * 2002-12-18 2004-06-24 Sabol John M. Integrated medical knowledge base interface system and method
US20040120558A1 (en) * 2002-12-18 2004-06-24 Sabol John M Computer assisted data reconciliation method and apparatus
US20040122709A1 (en) * 2002-12-18 2004-06-24 Avinash Gopal B. Medical procedure prioritization system and method utilizing integrated knowledge base
US20040122705A1 (en) * 2002-12-18 2004-06-24 Sabol John M. Multilevel integrated medical knowledge base system and method
US7490085B2 (en) * 2002-12-18 2009-02-10 Ge Medical Systems Global Technology Company, Llc Computer-assisted data processing system and method incorporating automated learning
US20040122703A1 (en) * 2002-12-19 2004-06-24 Walker Matthew J. Medical data operating model development system and method
US20050043609A1 (en) * 2003-01-30 2005-02-24 Gregory Murphy System and method for facilitating cardiac intervention
WO2004068406A2 (en) 2003-01-30 2004-08-12 Chase Medical, L.P. A method and system for image processing and contour assessment
US7848935B2 (en) * 2003-01-31 2010-12-07 I.M.D. Soft Ltd. Medical information event manager
US8620678B2 (en) * 2003-01-31 2013-12-31 Imd Soft Ltd. Medical information query system
US7230529B2 (en) * 2003-02-07 2007-06-12 Theradoc, Inc. System, method, and computer program for interfacing an expert system to a clinical information system
US20040172284A1 (en) * 2003-02-13 2004-09-02 Roche Diagnostics Corporation Information management system
CN1759400A (en) * 2003-03-10 2006-04-12 西门子医疗健康服务公司 A preventive care health maintenance information system
US7647116B2 (en) * 2003-03-13 2010-01-12 Medtronic, Inc. Context-sensitive collection of neurostimulation therapy data
US7182738B2 (en) 2003-04-23 2007-02-27 Marctec, Llc Patient monitoring apparatus and method for orthosis and other devices
US7463928B2 (en) * 2003-04-25 2008-12-09 Medtronic, Inc. Identifying combinations of electrodes for neurostimulation therapy
US7780595B2 (en) 2003-05-15 2010-08-24 Clinical Decision Support, Llc Panel diagnostic method and system
US7290016B2 (en) * 2003-05-27 2007-10-30 Frank Hugh Byers Method and apparatus for obtaining and storing medical history records
US20050010444A1 (en) * 2003-06-06 2005-01-13 Iliff Edwin C. System and method for assisting medical diagnosis using an anatomic system and cause matrix
US20050010416A1 (en) * 2003-07-09 2005-01-13 Gensym Corporation System and method for self management of health using natural language interface
US8034294B1 (en) 2003-07-15 2011-10-11 Ideal Life, Inc. Medical monitoring/consumables tracking device
US7591801B2 (en) 2004-02-26 2009-09-22 Dexcom, Inc. Integrated delivery device for continuous glucose sensor
US8571880B2 (en) 2003-08-07 2013-10-29 Ideal Life, Inc. Personal health management device, method and system
US8412541B2 (en) * 2003-08-14 2013-04-02 Edda Technology, Inc. Method and system for intelligent qualitative and quantitative analysis for medical diagnosis
US7575553B2 (en) * 2003-09-18 2009-08-18 Cardiac Pacemakers, Inc. Methods and systems for assessing pulmonary disease
US8606356B2 (en) 2003-09-18 2013-12-10 Cardiac Pacemakers, Inc. Autonomic arousal detection system and method
US8002553B2 (en) * 2003-08-18 2011-08-23 Cardiac Pacemakers, Inc. Sleep quality data collection and evaluation
US7887493B2 (en) 2003-09-18 2011-02-15 Cardiac Pacemakers, Inc. Implantable device employing movement sensing for detecting sleep-related disorders
US7662101B2 (en) 2003-09-18 2010-02-16 Cardiac Pacemakers, Inc. Therapy control based on cardiopulmonary status
US20050065815A1 (en) * 2003-09-19 2005-03-24 Mazar Scott Thomas Information management system and method for an implantable medical device
US20050066335A1 (en) * 2003-09-23 2005-03-24 Robert Aarts System and method for exposing local clipboard functionality towards external applications
US9984377B2 (en) 2003-10-06 2018-05-29 Yellowpages.Com Llc System and method for providing advertisement
US7428497B2 (en) 2003-10-06 2008-09-23 Utbk, Inc. Methods and apparatuses for pay-per-call advertising in mobile/wireless applications
US7366683B2 (en) 2003-10-06 2008-04-29 Utbk, Inc. Methods and apparatuses for offline selection of pay-per-call advertisers
US7424442B2 (en) 2004-05-04 2008-09-09 Utbk, Inc. Method and apparatus to allocate and recycle telephone numbers in a call-tracking system
US8029454B2 (en) * 2003-11-05 2011-10-04 Baxter International Inc. High convection home hemodialysis/hemofiltration and sorbent system
US7346203B2 (en) * 2003-11-19 2008-03-18 General Electric Company Methods and apparatus for processing image data to aid in detecting disease
US20070014452A1 (en) * 2003-12-01 2007-01-18 Mitta Suresh Method and system for image processing and assessment of a state of a heart
US8548822B2 (en) * 2003-12-19 2013-10-01 Stryker Leibinger Gmbh & Co., Kg Reactive workflow system and method
US20050143671A1 (en) * 2003-12-31 2005-06-30 Ge Medical Systems Information Technologies, Inc. Alarm notification system and device having voice communication capability
JP4861616B2 (en) * 2004-01-06 2012-01-25 株式会社東芝 HEALTHCARE SUPPORT SYSTEM AND HEALTHCARE SUPPORT DEVICE
WO2005067375A2 (en) * 2004-01-09 2005-07-28 Imd-Soft, Ltd. Clinical data database system and method for a critical care and/or hospital environment
US20060143022A1 (en) * 2004-01-13 2006-06-29 Betty Bird Consumer care management method and system
US7333643B2 (en) 2004-01-30 2008-02-19 Chase Medical, L.P. System and method for facilitating cardiac intervention
US20050182653A1 (en) * 2004-02-12 2005-08-18 Joseph Urban System and method for improving and promoting compliance to a therapeutic regimen
WO2005079417A2 (en) * 2004-02-17 2005-09-01 Bodybio Inc. Integrating individualized clinical test results and nutritional treatment
US7488290B1 (en) * 2004-02-19 2009-02-10 Cardiac Pacemakers, Inc. System and method for assessing cardiac performance through transcardiac impedance monitoring
US8025624B2 (en) 2004-02-19 2011-09-27 Cardiac Pacemakers, Inc. System and method for assessing cardiac performance through cardiac vibration monitoring
US8808228B2 (en) 2004-02-26 2014-08-19 Dexcom, Inc. Integrated medicament delivery device for use with continuous analyte sensor
WO2009048462A1 (en) 2007-10-09 2009-04-16 Dexcom, Inc. Integrated insulin delivery system with continuous glucose sensor
US20050192844A1 (en) * 2004-02-27 2005-09-01 Cardiac Pacemakers, Inc. Systems and methods for automatically collecting, formatting, and storing medical device data in a database
US20050246185A1 (en) * 2004-04-29 2005-11-03 Brown Richard L Business process for delivering health behavior prevention services
US8428968B2 (en) * 2004-05-10 2013-04-23 Epic Systems Corporation Interactive system for patient access to electronic medical records
US7329226B1 (en) 2004-07-06 2008-02-12 Cardiac Pacemakers, Inc. System and method for assessing pulmonary performance through transthoracic impedance monitoring
US7223234B2 (en) 2004-07-10 2007-05-29 Monitrix, Inc. Apparatus for determining association variables
WO2006007735A1 (en) * 2004-07-21 2006-01-26 Medcap Medical Electronic Data Capturing Gmbh Quality control system and method
US8313433B2 (en) * 2004-08-06 2012-11-20 Medtronic Minimed, Inc. Medical data management system and process
US20060036440A1 (en) * 2004-08-10 2006-02-16 Daniel Kunkel Biowaves technology
US7584103B2 (en) * 2004-08-20 2009-09-01 Multimodal Technologies, Inc. Automated extraction of semantic content and generation of a structured document from speech
US20130304453A9 (en) * 2004-08-20 2013-11-14 Juergen Fritsch Automated Extraction of Semantic Content and Generation of a Structured Document from Speech
US8086462B1 (en) * 2004-09-09 2011-12-27 At&T Intellectual Property Ii, L.P. Automatic detection, summarization and reporting of business intelligence highlights from automated dialog systems
US20060059014A1 (en) * 2004-09-14 2006-03-16 Eli Dancy Interactive system for confirming the sexual health status of an individual
US7716071B2 (en) * 2004-10-04 2010-05-11 Liana Gold System and method for managing a patient with chronic disease
US9081879B2 (en) 2004-10-22 2015-07-14 Clinical Decision Support, Llc Matrix interface for medical diagnostic and treatment advice system and method
US20060089539A1 (en) * 2004-10-25 2006-04-27 Saul Miodownik Integrated messages from multiple patient care devices
US20060101335A1 (en) * 2004-11-08 2006-05-11 Pisciottano Maurice A Method and apparatus for generating and storing data and for generating a narrative report
EP1819278A4 (en) 2004-11-15 2009-04-08 Izex Technologies Inc Instrumented orthopedic and other medical implants
US8308794B2 (en) 2004-11-15 2012-11-13 IZEK Technologies, Inc. Instrumented implantable stents, vascular grafts and other medical devices
US20060136270A1 (en) * 2004-12-02 2006-06-22 Morgan John D Medical claim data transfer to medical deposit box and/or medical visit record
WO2006060626A2 (en) * 2004-12-02 2006-06-08 Healthright, Inc. Medical claim data transfer to medical deposit box and/or medical visit record
US8204771B1 (en) 2004-12-16 2012-06-19 Cerner Innovation, Inc. Computerized method and system for updating a task list from an action item documentation view
US7612679B1 (en) 2004-12-28 2009-11-03 Cerner Innovation, Inc. Computerized method and system for providing alerts from a multi-patient display
US8273018B1 (en) 2004-12-28 2012-09-25 Cerner Innovation, Inc. Computerized method for establishing a communication between a bedside care location and a remote care location
CA2594926A1 (en) 2005-01-13 2006-07-20 Welch Allyn, Inc. Vital signs monitor
US8374887B1 (en) * 2005-02-11 2013-02-12 Emily H. Alexander System and method for remotely supervising and verifying pharmacy functions
US7979308B2 (en) 2005-03-03 2011-07-12 Utbk, Inc. Methods and apparatuses for sorting lists for presentation
US8652039B2 (en) * 2005-03-02 2014-02-18 Siemens Medical Solutions Usa, Inc. Guiding differential diagnosis through information maximization
US20060247606A1 (en) * 2005-03-09 2006-11-02 Batch Richard M System and method for controlling access to features of a medical instrument
US20060264714A1 (en) * 2005-03-23 2006-11-23 Mcglennen Ronald C Apparatus and methods for medical testing
US8484048B2 (en) * 2005-03-23 2013-07-09 Cincinnati Children's Hospital Medical Center Automated system and method for prioritization of waiting patients
JP2006309465A (en) * 2005-04-27 2006-11-09 Sense It Smart Corp Dental health management system, oral cavity information analyzing device, dental disease analyzing method and program
US8781847B2 (en) * 2005-05-03 2014-07-15 Cardiac Pacemakers, Inc. System and method for managing alert notifications in an automated patient management system
US20100063840A1 (en) * 2005-05-03 2010-03-11 Hoyme Kenneth P System and method for managing coordination of collected patient data in an automated patient management system
US20060253300A1 (en) * 2005-05-03 2006-11-09 Somberg Benjamin L System and method for managing patient triage in an automated patient management system
US8251904B2 (en) 2005-06-09 2012-08-28 Roche Diagnostics Operations, Inc. Device and method for insulin dosing
US20060287885A1 (en) * 2005-06-21 2006-12-21 Frick W V Treatment management system
FR2887663A1 (en) * 2005-06-24 2006-12-29 Ippm Holding Sa METHOD AND INFORMATION SYSTEM FOR GENERATING OPTIMIZATION DATA OF MEDICAL TREATMENT, AND EQUIPMENT IMPLEMENTED THEREIN
EP1946231A1 (en) * 2005-06-24 2008-07-23 IPPM Holding SA Method and system for generating data for optimizing a medical treatment, and equipment used in this system
WO2007014307A2 (en) * 2005-07-27 2007-02-01 Medecision, Inc. System and method for health care data integration and management
US7464042B2 (en) * 2005-07-28 2008-12-09 Roberto Beraja Medical professional monitoring system and associated methods
US8392210B2 (en) * 2005-07-28 2013-03-05 Roberto Beraja Medical claims fraud prevention system and associated methods
US8583454B2 (en) 2005-07-28 2013-11-12 Beraja Ip, Llc Medical claims fraud prevention system including photograph records identification and associated methods
US8751264B2 (en) 2005-07-28 2014-06-10 Beraja Ip, Llc Fraud prevention system including biometric records identification and associated methods
US8392211B2 (en) * 2005-07-28 2013-03-05 Roberto Beraja Medical claims fraud prevention system including patient call initiating feature and associated methods
US8392212B2 (en) * 2005-07-28 2013-03-05 Roberto Beraja Medical claims fraud prevention system including patient identification interface feature and associated methods
US20160328812A9 (en) * 2005-07-28 2016-11-10 Roberto Beraja Medical decision system including question mapping and cross referencing system and associated methods
US8392213B2 (en) * 2005-07-28 2013-03-05 Roberto Beraja Medical claims fraud prevention system including historical patient locating feature and associated methods
US7685000B1 (en) 2005-08-10 2010-03-23 Matria Healthcare, Inc. Predictive modeling system and method for disease management
US8566121B2 (en) * 2005-08-29 2013-10-22 Narayanan Ramasubramanian Personalized medical adherence management system
US20070061166A1 (en) * 2005-08-29 2007-03-15 Narayanan Ramasubramanian Techniques for improving loss ratios
US20080058282A1 (en) 2005-08-30 2008-03-06 Fallon Joan M Use of lactulose in the treatment of autism
US8831735B2 (en) * 2005-08-31 2014-09-09 Michael Sasha John Methods and systems for semi-automatic adjustment of medical monitoring and treatment
US9089713B2 (en) * 2005-08-31 2015-07-28 Michael Sasha John Methods and systems for semi-automatic adjustment of medical monitoring and treatment
US20080194922A1 (en) * 2005-09-07 2008-08-14 Holden James F Potentiation for medical therapies
US7711583B2 (en) * 2005-10-05 2010-05-04 Medco Health Solutions, Inc. System and method for clinical strategy for therapeutic pharmacies
US20070122780A1 (en) * 2005-10-31 2007-05-31 Behavioral Health Strategies Of Utah, Llc Systems and methods for support of behavioral modification coaching
US20090006419A1 (en) * 2005-11-07 2009-01-01 Eric Savitsky System and Method for Personalized Health Information Delivery
US8468029B2 (en) * 2005-11-17 2013-06-18 The Invention Science Fund I, Llc Subscriptions for assistance related to health
US7693857B2 (en) * 2005-11-17 2010-04-06 International Business Machines Corporation Clinical genomics merged repository and partial episode support with support abstract and semantic meaning preserving data sniffers
US10042980B2 (en) 2005-11-17 2018-08-07 Gearbox Llc Providing assistance related to health
US8532938B2 (en) * 2005-11-17 2013-09-10 The Invention Science Fund I, Llc Testing-dependent administration of a nutraceutical
US20070112592A1 (en) 2005-11-17 2007-05-17 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Payments in providing assistance related to health
US20070118416A1 (en) * 2005-11-18 2007-05-24 Developmental Disabilities Association Of Vancouver-Richmond Method and system for planning
US20070129967A1 (en) * 2005-12-05 2007-06-07 Thompson Stephen C Automated method for medical care management
WO2007081732A2 (en) * 2006-01-04 2007-07-19 Gordon, Linda, Susan Electronic disease management system
JP5292104B2 (en) * 2006-01-05 2013-09-18 ユニバーシティ オブ バージニア パテント ファウンデーション Computer-implemented method, system, and computer program for evaluating blood glucose variability in diabetes from self-monitoring data
US10468125B1 (en) 2006-03-02 2019-11-05 Emerge Clinical Solutions, LLC System and method for diagnosis and treatment of cardiac episodes
US20070260631A1 (en) * 2006-03-09 2007-11-08 Microsoft Corporation Embedded decision support
US10115172B2 (en) 2006-04-07 2018-10-30 Koninklijke Philips N.V. Self-adaptive care plan goal modules
US8712539B2 (en) 2006-04-12 2014-04-29 Medtronic, Inc. Rule-based stimulation program search
US7774067B2 (en) * 2006-04-12 2010-08-10 Medtronic, Inc. Autogeneration of neurostimulation therapy program groups
US20070276197A1 (en) * 2006-05-24 2007-11-29 Lifescan, Inc. Systems and methods for providing individualized disease management
US7831423B2 (en) * 2006-05-25 2010-11-09 Multimodal Technologies, Inc. Replacing text representing a concept with an alternate written form of the concept
US7505951B2 (en) * 2006-05-30 2009-03-17 Motorola, Inc. Hierarchical state machine generation for interaction management using goal specifications
US7797672B2 (en) * 2006-05-30 2010-09-14 Motorola, Inc. Statechart generation using frames
US7657434B2 (en) * 2006-05-30 2010-02-02 Motorola, Inc. Frame goals for dialog system
JP2009541800A (en) * 2006-06-22 2009-11-26 マルチモダル テクノロジーズ,インク. Speech recognition method
JP2008027093A (en) * 2006-07-20 2008-02-07 Olympus Medical Systems Corp Medical practice support method and medical practice support device
US8758019B2 (en) * 2006-08-03 2014-06-24 James W. Suzansky Multimedia game based system and process for medical, safety and health improvements
JP4793186B2 (en) * 2006-09-07 2011-10-12 日本精工株式会社 3-axis drive
US7590550B2 (en) 2006-09-08 2009-09-15 American Well Inc. Connecting consumers with service providers
US8788279B2 (en) * 2006-10-18 2014-07-22 Yescorp, Inc. Information management and communications system for communication between patients and healthcare providers
US9317855B2 (en) 2006-10-24 2016-04-19 Yellowpages.Com Llc Systems and methods to provide voice connections via local telephone numbers
US8473868B1 (en) * 2006-10-27 2013-06-25 Arris Group, Inc. System and method for reverse hierarchical navigation within a user interface
US8666761B2 (en) * 2006-11-01 2014-03-04 Walgreen Co. System and method for an integrated disease management system
US8666763B2 (en) * 2006-11-01 2014-03-04 Walgreen Co. System and method for a lifestyle management system
RU2009120968A (en) * 2006-11-03 2010-12-10 Конинклейке Филипс Электроникс Н.В. (Nl) INTEGRATED ASSESSMENTS, PERFORMANCE SEQUENCE AND REPORTING
CN109147915A (en) * 2006-11-09 2019-01-04 皇家飞利浦电子股份有限公司 Patient health care network guided encounter
US20080126118A1 (en) * 2006-11-24 2008-05-29 General Electric Company, A New York Corporation Systems, methods and apparatus for a network application framework system
US8540517B2 (en) * 2006-11-27 2013-09-24 Pharos Innovations, Llc Calculating a behavioral path based on a statistical profile
US8540515B2 (en) * 2006-11-27 2013-09-24 Pharos Innovations, Llc Optimizing behavioral change based on a population statistical profile
US8540516B2 (en) * 2006-11-27 2013-09-24 Pharos Innovations, Llc Optimizing behavioral change based on a patient statistical profile
US20080126123A1 (en) * 2006-11-29 2008-05-29 General Electric Company Customizing healthcare information
TWI360416B (en) * 2006-12-14 2012-03-21 Ind Tech Res Inst Apparatus of cardiopulmonary resuscitator
US20080147364A1 (en) * 2006-12-15 2008-06-19 Motorola, Inc. Method and apparatus for generating harel statecharts using forms specifications
US20080154513A1 (en) * 2006-12-21 2008-06-26 University Of Virginia Patent Foundation Systems, Methods and Computer Program Codes for Recognition of Patterns of Hyperglycemia and Hypoglycemia, Increased Glucose Variability, and Ineffective Self-Monitoring in Diabetes
US8451825B2 (en) 2007-02-22 2013-05-28 Utbk, Llc Systems and methods to confirm initiation of a callback
US20080262869A1 (en) * 2007-01-22 2008-10-23 National Consolidated Technologies, Llc Automated System and Method for Medical Care Selection
US8224670B2 (en) * 2007-01-25 2012-07-17 Cerner Innovation, Inc. Graphical user interface for visualizing person centric infection risk
US20080189133A1 (en) * 2007-02-01 2008-08-07 Asset Health, Inc. Health care education systems
US9754077B2 (en) 2007-02-22 2017-09-05 WellDoc, Inc. Systems and methods for disease control and management
US10860943B2 (en) 2007-02-22 2020-12-08 WellDoc, Inc. Systems and methods for disease control and management
US10872686B2 (en) 2007-02-22 2020-12-22 WellDoc, Inc. Systems and methods for disease control and management
US7894651B2 (en) * 2007-03-02 2011-02-22 Mela Sciences, Inc. Quantitative analysis of skin characteristics
US11062795B2 (en) * 2007-03-02 2021-07-13 Enigami Systems, Inc. Healthcare data system
US20080221923A1 (en) * 2007-03-07 2008-09-11 Upmc, A Corporation Of The Commonwealth Of Pennsylvania Medical information management system
US20080228040A1 (en) * 2007-03-16 2008-09-18 Arthur Solomon Thompson International medical expert diagnosis
US20080234943A1 (en) * 2007-03-20 2008-09-25 Pinaki Ray Computer program for diabetes management
US8758245B2 (en) * 2007-03-20 2014-06-24 Lifescan, Inc. Systems and methods for pattern recognition in diabetes management
US20080235053A1 (en) * 2007-03-20 2008-09-25 Pinaki Ray Communication medium for diabetes management
US20090088981A1 (en) * 2007-04-26 2009-04-02 Neville Thomas B Methods And Systems Of Dynamic Screening Of Disease
AU2008245433A1 (en) * 2007-04-30 2008-11-06 Clinical Decision Support, Llc Arbiter system and method of computerized medical diagnosis and advice
WO2008144481A1 (en) 2007-05-18 2008-11-27 Institute For Molecular Medicine, Inc. Measurement and uses of oxidative status
US8709709B2 (en) 2007-05-18 2014-04-29 Luoxis Diagnostics, Inc. Measurement and uses of oxidative status
WO2008154312A1 (en) 2007-06-08 2008-12-18 Dexcom, Inc. Integrated medicament delivery device for use with continuous analyte sensor
US9277019B2 (en) 2007-06-18 2016-03-01 Yellowpages.Com Llc Systems and methods to provide communication references to connect people for real time communications
EP2562664B1 (en) * 2007-06-27 2020-11-25 Roche Diabetes Care GmbH System for determining an insulin delivery and communicating a dose in automated pancreas software
ES2733350T3 (en) 2007-06-27 2019-11-28 Hoffmann La Roche System for medical diagnosis, treatment and prognosis for requested events and procedure
WO2009015466A1 (en) * 2007-07-27 2009-02-05 The Hospital For Sick Children A medical vital sign indication tool, system and method
US7836001B2 (en) * 2007-09-14 2010-11-16 Palo Alto Research Center Incorporated Recommender system with AD-HOC, dynamic model composition
US20090187425A1 (en) * 2007-09-17 2009-07-23 Arthur Solomon Thompson PDA software robots leveraging past history in seconds with software robots
JP2009075927A (en) * 2007-09-21 2009-04-09 Fujifilm Corp Medical report preparing system, medical report preparing device, and medical report preparing method
US8527296B2 (en) * 2007-09-26 2013-09-03 Fujifilm Corporation Medical information processing system, medical information processing method, and computer readable medium
EP2210226A4 (en) * 2007-10-12 2013-11-06 Patientslikeme Inc Self-improving method of using online communities to predict health-related outcomes
US20090112625A1 (en) * 2007-10-25 2009-04-30 Doherty Holly S Systems and Methods for Obtaining and Preserving Health Care Information
TWI377046B (en) * 2007-10-31 2012-11-21 Netown Corp A telemedicine device and system
US20090119130A1 (en) * 2007-11-05 2009-05-07 Zebadiah Kimmel Method and apparatus for interpreting data
US8447778B2 (en) 2007-11-15 2013-05-21 Siemens Medical Solutions Usa, Inc. Adaptively optimizing order entry system
US20090150877A1 (en) * 2007-12-07 2009-06-11 Roche Diagnostics Operations, Inc. Data driven communication protocol grammar
US9717896B2 (en) 2007-12-18 2017-08-01 Gearbox, Llc Treatment indications informed by a priori implant information
US8636670B2 (en) 2008-05-13 2014-01-28 The Invention Science Fund I, Llc Circulatory monitoring systems and methods
US20090287120A1 (en) 2007-12-18 2009-11-19 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Circulatory monitoring systems and methods
US8645424B2 (en) 2007-12-19 2014-02-04 Sam Stanley Miller System for electronically recording and sharing medical information
US20090164248A1 (en) * 2007-12-21 2009-06-25 Providence Medical Group, A Division Of Providence Health System System and Method for Patient Management/Communication with Intervention
US20090164237A1 (en) * 2007-12-21 2009-06-25 Providence Medical Group, A Division Of Providence Health System - Oregon System and Method for Patient Management/Communication
US20090164249A1 (en) * 2007-12-21 2009-06-25 Providence Medical Group, A Division Of Providence Health System - Oregon System and Method for Patient Management/Communication with Filtering
US20090171884A1 (en) * 2007-12-28 2009-07-02 Wright Steven C System and method for web-based case management
US20090171696A1 (en) * 2008-01-02 2009-07-02 David Joseph Allard System and method for patient portal with clinical decision intelligence
WO2009103107A1 (en) * 2008-02-18 2009-08-27 Inspirovate Pty Ltd Interactive personal portable data management system
US8658163B2 (en) 2008-03-13 2014-02-25 Curemark Llc Compositions and use thereof for treating symptoms of preeclampsia
US20090234181A1 (en) * 2008-03-14 2009-09-17 Institute For Music And Neurologic Function Assessment Tool For Storing and Sharing Music Therapy Patient Records
US20090240522A1 (en) * 2008-03-20 2009-09-24 Harmonex, Inc. Computer aided intake and assessment system
US20090240127A1 (en) * 2008-03-20 2009-09-24 Lifescan, Inc. Methods of determining pre or post meal time slots or intervals in diabetes management
US20090248437A1 (en) * 2008-03-27 2009-10-01 General Electric Company Systems and methods utilizing nfc technology to implement an on-demand portable medical record
WO2009126553A2 (en) * 2008-04-08 2009-10-15 The Quantum Group, Inc. Dynamic integration of disparate health-related processes and data
US20090259492A1 (en) * 2008-04-09 2009-10-15 Strategic Medical, Llc Remote Consultation System and Method
US8084025B2 (en) 2008-04-18 2011-12-27 Curemark Llc Method for the treatment of the symptoms of drug and alcohol addiction
WO2009134862A2 (en) * 2008-04-29 2009-11-05 University Of Miami System and method for using interactive voice-recognition to automate a patient-centered best practice approach to disease evaluation and management
WO2009146238A1 (en) * 2008-05-01 2009-12-03 Chacha Search, Inc. Method and system for improvement of request processing
US8799010B2 (en) * 2008-05-07 2014-08-05 Unitedhealth Group Incorporated Telehealth scheduling and communications network
US20090287487A1 (en) * 2008-05-14 2009-11-19 General Electric Company Systems and Methods for a Visual Indicator to Track Medical Report Dictation Progress
WO2009148803A2 (en) * 2008-05-15 2009-12-10 Soar Biodynamics, Ltd. Methods and systems for integrated health systems
US9320780B2 (en) 2008-06-26 2016-04-26 Curemark Llc Methods and compositions for the treatment of symptoms of Williams Syndrome
US20090326339A1 (en) * 2008-06-26 2009-12-31 Microsoft Corporation Connected healthcare devices with real-time and proactive capture and relay of contextual information
US20090324730A1 (en) * 2008-06-26 2009-12-31 Fallon Joan M Methods and compositions for the treatment of symptoms of complex regional pain syndrome
EP2318035B1 (en) 2008-07-01 2019-06-12 Curemark, Llc Methods and compositions for the treatment of symptoms of neurological and mental health disorders
US8311854B1 (en) 2008-07-01 2012-11-13 Unicor Medical, Inc. Medical quality performance measurement reporting facilitator
US8216786B2 (en) 2008-07-09 2012-07-10 Celera Corporation Genetic polymorphisms associated with cardiovascular diseases, methods of detection and uses thereof
US9280863B2 (en) * 2008-07-16 2016-03-08 Parata Systems, Llc Automated dispensing system for pharmaceuticals and other medical items
US10776453B2 (en) * 2008-08-04 2020-09-15 Galenagen, Llc Systems and methods employing remote data gathering and monitoring for diagnosing, staging, and treatment of Parkinsons disease, movement and neurological disorders, and chronic pain
US8600777B2 (en) * 2008-08-28 2013-12-03 I.M.D. Soft Ltd. Monitoring patient conditions
JP5219700B2 (en) * 2008-09-01 2013-06-26 オムロンヘルスケア株式会社 Biometric index management device
WO2010033816A1 (en) * 2008-09-18 2010-03-25 Ingenix, Inc. Apparatus, system and method for graphically displaying natural history of disease progression
TWI400664B (en) * 2008-09-23 2013-07-01 Univ Chang Gung A system of knowledge management and self-health care counseling for chronic health care
US20100092447A1 (en) 2008-10-03 2010-04-15 Fallon Joan M Methods and compositions for the treatment of symptoms of prion diseases
KR20100039705A (en) * 2008-10-08 2010-04-16 삼성전자주식회사 Method and apparatus for managing patient
US20100114604A1 (en) * 2008-10-31 2010-05-06 Joseph Bernstein Authorization Process for High Intensity Medical Interventions
US9408537B2 (en) * 2008-11-14 2016-08-09 At&T Intellectual Property I, Lp System and method for performing a diagnostic analysis of physiological information
US8224956B2 (en) * 2008-11-21 2012-07-17 The Invention Science Fund I, Llc Hypothesis selection and presentation of one or more advisories
US8260729B2 (en) * 2008-11-21 2012-09-04 The Invention Science Fund I, Llc Soliciting data indicating at least one subjective user state in response to acquisition of data indicating at least one objective occurrence
US20100131607A1 (en) * 2008-11-21 2010-05-27 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Correlating data indicating subjective user states associated with multiple users with data indicating objective occurrences
US8260912B2 (en) * 2008-11-21 2012-09-04 The Invention Science Fund I, Llc Hypothesis based solicitation of data indicating at least one subjective user state
US8239488B2 (en) * 2008-11-21 2012-08-07 The Invention Science Fund I, Llc Hypothesis development based on user and sensing device data
US8224842B2 (en) * 2008-11-21 2012-07-17 The Invention Science Fund I, Llc Hypothesis selection and presentation of one or more advisories
US8180890B2 (en) * 2008-11-21 2012-05-15 The Invention Science Fund I, Llc Hypothesis based solicitation of data indicating at least one subjective user state
US8180830B2 (en) * 2008-11-21 2012-05-15 The Invention Science Fund I, Llc Action execution based on user modified hypothesis
US8244858B2 (en) * 2008-11-21 2012-08-14 The Invention Science Fund I, Llc Action execution based on user modified hypothesis
US20100131334A1 (en) * 2008-11-21 2010-05-27 Searete Llc, A Limited Liability Corporation Of The State Of Delaware Hypothesis development based on selective reported events
EP2370948A4 (en) * 2008-12-03 2012-12-26 Healthagen Llc Platform for connecting medical information to services for medical care
US9918635B2 (en) 2008-12-23 2018-03-20 Roche Diabetes Care, Inc. Systems and methods for optimizing insulin dosage
CA2747332C (en) * 2008-12-23 2015-01-27 F. Hoffmann-La Roche Ag Management method and system for implementation, execution, data collection, and data analysis of a structured collection procedure which runs on a collection device
US10437962B2 (en) * 2008-12-23 2019-10-08 Roche Diabetes Care Inc Status reporting of a structured collection procedure
US20120011125A1 (en) 2008-12-23 2012-01-12 Roche Diagnostics Operations, Inc. Management method and system for implementation, execution, data collection, and data analysis of a structured collection procedure which runs on a collection device
US9117015B2 (en) 2008-12-23 2015-08-25 Roche Diagnostics Operations, Inc. Management method and system for implementation, execution, data collection, and data analysis of a structured collection procedure which runs on a collection device
US8849458B2 (en) * 2008-12-23 2014-09-30 Roche Diagnostics Operations, Inc. Collection device with selective display of test results, method and computer program product thereof
WO2010075446A1 (en) * 2008-12-23 2010-07-01 Soar Biodynamics, Ltd. Methods and systems for prostate health monitoring
US10456036B2 (en) 2008-12-23 2019-10-29 Roche Diabetes Care, Inc. Structured tailoring
US20100169115A1 (en) * 2008-12-31 2010-07-01 Tamis Robert H System for matching individuals with health care providers and methods thereof
KR101694930B1 (en) 2009-01-06 2017-01-10 큐어론 엘엘씨 Compositions and methods for the treatment or prevention of staphylococcus aureus infections and for the eradication or reduction of staphylococcus aureus on surfaces
KR101694931B1 (en) 2009-01-06 2017-01-10 큐어론 엘엘씨 Compositions and methods for the treatment or the prevention oral infections by e. coli
US8812244B2 (en) 2009-01-26 2014-08-19 EOS Health, Inc. Personalized wireless-based interactive diabetes treatment
US20100191544A1 (en) * 2009-01-27 2010-07-29 Adam Bosworth Protocol Authoring for a Health Coaching Service
EP2401718A4 (en) * 2009-02-26 2014-03-12 I M D Soft Ltd Decision support
WO2010101898A2 (en) 2009-03-02 2010-09-10 Florida Atlantic University Apparatus and method for managing interaction-based services
US20100235181A1 (en) * 2009-03-11 2010-09-16 Thomas Loser Methods for making complex therapeutic clinical decisions
US9056050B2 (en) 2009-04-13 2015-06-16 Curemark Llc Enzyme delivery systems and methods of preparation and use
US8315885B2 (en) * 2009-04-14 2012-11-20 Baxter International Inc. Therapy management development platform
CA2758481C (en) 2009-04-30 2018-03-20 Patientslikeme, Inc. Systems and methods for encouragement of data submission in online communities
US20100280838A1 (en) * 2009-05-01 2010-11-04 Adam Bosworth Coaching Engine for a Health Coaching Service
EP2433232A1 (en) 2009-05-20 2012-03-28 Koninklijke Philips Electronics N.V. Biomarkers based on sets of molecular signatures
EP2437655A1 (en) * 2009-06-03 2012-04-11 Cardiac Pacemakers, Inc. System and method for monitoring cardiovascular pressure
US20100312581A1 (en) * 2009-06-08 2010-12-09 Peter James Wachtell Process and system for efficient allocation of medical resources
US20100324932A1 (en) * 2009-06-19 2010-12-23 Roche Diagnostics Operations, Inc. Methods and systems for advising people with diabetes
BRPI1015922A2 (en) * 2009-06-30 2016-04-26 Lifescan Inc systems and methods for testing analytes
US8296163B2 (en) 2009-08-11 2012-10-23 Fishman Marc L Method and system for medical treatment review
US20110060604A1 (en) * 2009-09-04 2011-03-10 Bangara Suresh C Method of documenting patients' clinical status across multiple diagnostic dimensions
US20110077954A1 (en) * 2009-09-25 2011-03-31 Cerner Innovation, Inc. Therapy reconciliation for venue transition
WO2011048812A1 (en) * 2009-10-21 2011-04-28 オリンパスメディカルシステムズ株式会社 Medical work supporting system
US9511125B2 (en) 2009-10-21 2016-12-06 Curemark Llc Methods and compositions for the treatment of influenza
US20110099024A1 (en) * 2009-10-28 2011-04-28 Christine Lee Healthcare management system
US20110112850A1 (en) * 2009-11-09 2011-05-12 Roberto Beraja Medical decision system including medical observation locking and associated methods
US8165897B2 (en) * 2009-11-09 2012-04-24 Roberto Beraja Medical decision system including interactive protocols and associated methods
US20120232931A1 (en) * 2009-11-16 2012-09-13 Koninklijke Philips Electronics N.V. Patient monitoring system
US8560479B2 (en) 2009-11-23 2013-10-15 Keas, Inc. Risk factor coaching engine that determines a user health score
US20110141116A1 (en) * 2009-12-16 2011-06-16 Baxter International Inc. Methods and apparatus for displaying flow rate graphs and alarms on a dialysis system
US20110184247A1 (en) * 2010-01-25 2011-07-28 Contant Olivier M Comprehensive management of human health
US9750896B2 (en) * 2010-02-05 2017-09-05 Deka Products Limited Partnership Infusion pump apparatus, method and system
KR20230145240A (en) 2010-02-18 2023-10-17 가부시키가이샤 한도오따이 에네루기 켄큐쇼 Semiconductor device
US9000914B2 (en) 2010-03-15 2015-04-07 Welch Allyn, Inc. Personal area network pairing
US9330234B1 (en) * 2010-04-13 2016-05-03 West Corporation Method, apparatus and computer program to provide access to client records and data resources
US20110269735A1 (en) 2010-04-19 2011-11-03 Celera Corporation Genetic polymorphisms associated with statin response and cardiovascular diseases, methods of detection and uses thereof
US9930297B2 (en) 2010-04-30 2018-03-27 Becton, Dickinson And Company System and method for acquiring images of medication preparations
CN103140854A (en) * 2010-06-16 2013-06-05 苹穆德有限公司 Method and apparatus for soliciting an expert opinion from a care provider and managing health management protocols
US8532933B2 (en) 2010-06-18 2013-09-10 Roche Diagnostics Operations, Inc. Insulin optimization systems and testing methods with adjusted exit criterion accounting for system noise associated with biomarkers
US8907782B2 (en) 2010-06-30 2014-12-09 Welch Allyn, Inc. Medical devices with proximity detection
US8957777B2 (en) 2010-06-30 2015-02-17 Welch Allyn, Inc. Body area network pairing improvements for clinical workflows
CA2805713C (en) 2010-07-16 2023-08-15 Navya Network, Inc. Treatment related quantitative decision engine
US8725539B2 (en) * 2010-09-07 2014-05-13 Premier Health Care Services Inc. Systems and methods for providing a continuum of care
US9002773B2 (en) 2010-09-24 2015-04-07 International Business Machines Corporation Decision-support application and system for problem solving using a question-answering system
US8959102B2 (en) 2010-10-08 2015-02-17 Mmodal Ip Llc Structured searching of dynamic structured document corpuses
US20120108651A1 (en) 2010-11-02 2012-05-03 Leiden University Medical Center (LUMC) Acting on Behalf of Academic Hospital Leiden (AZL) Genetic polymorphisms associated with venous thrombosis and statin response, methods of detection and uses thereof
CN107007253B (en) 2010-11-11 2020-09-01 卓尔医学产品公司 Medical system
US20120173151A1 (en) 2010-12-29 2012-07-05 Roche Diagnostics Operations, Inc. Methods of assessing diabetes treatment protocols based on protocol complexity levels and patient proficiency levels
TWI451354B (en) * 2011-01-07 2014-09-01 Univ Taipei Medical A high performance and integrated nosocomial infection surveillance and early detection system and method thereof
US10098584B2 (en) 2011-02-08 2018-10-16 Cardiac Pacemakers, Inc. Patient health improvement monitor
CA2827542A1 (en) 2011-02-17 2012-08-23 Eon Medical Ltd. System and method for performing an automatic and remote trained personnel guided medical examination
CN107115123B (en) 2011-02-17 2022-08-02 泰拓卡尔有限公司 System and method for remotely adjusting sound collection sensor parameters
JP5788963B2 (en) * 2011-02-21 2015-10-07 パナソニック インテレクチュアル プロパティ コーポレーション オブアメリカPanasonic Intellectual Property Corporation of America Data processing apparatus, data processing system, and data processing method
SG10201403561WA (en) 2011-02-28 2014-09-26 Luoxis Diagnostics Inc Method and apparatus for measuring oxidation-reduction potential
WO2012129507A1 (en) 2011-03-24 2012-09-27 WellDoc, Inc. Adaptive analytical behavioral and health assistant system and related method of use
US9043217B2 (en) 2011-03-31 2015-05-26 HealthSpot Inc. Medical kiosk and method of use
US9626650B2 (en) 2011-04-14 2017-04-18 Elwha Llc Cost-effective resource apportionment technologies suitable for facilitating therapies
US10445846B2 (en) 2011-04-14 2019-10-15 Elwha Llc Cost-effective resource apportionment technologies suitable for facilitating therapies
GB2503852B (en) 2011-04-21 2018-12-12 Curemark Llc Compounds for the treatment of neuropsychiatric disorders
CN102244671A (en) * 2011-04-28 2011-11-16 大连亿创天地科技发展有限公司 Internet-based video diagnosis and treatment system for doctor
US20120290310A1 (en) * 2011-05-12 2012-11-15 Onics Inc Dynamic decision tree system for clinical information acquisition
US8755938B2 (en) 2011-05-13 2014-06-17 Roche Diagnostics Operations, Inc. Systems and methods for handling unacceptable values in structured collection protocols
US8766803B2 (en) 2011-05-13 2014-07-01 Roche Diagnostics Operations, Inc. Dynamic data collection
US9153142B2 (en) 2011-05-26 2015-10-06 International Business Machines Corporation User interface for an evidence-based, hypothesis-generating decision support system
US8702238B2 (en) 2011-06-23 2014-04-22 Orca Health, Inc. Interactive medical diagnosing with portable consumer devices
US9772270B2 (en) 2011-08-16 2017-09-26 Elwha Llc Devices and methods for recording information on a subject's body
US9286615B2 (en) * 2011-08-16 2016-03-15 Elwha Llc Devices and methods for recording information on a subject's body
US8599009B2 (en) 2011-08-16 2013-12-03 Elwha Llc Systematic distillation of status data relating to regimen compliance
US9443061B2 (en) 2011-08-16 2016-09-13 Elwha Llc Devices and methods for recording information on a subject's body
US8601030B2 (en) 2011-09-09 2013-12-03 International Business Machines Corporation Method for a natural language question-answering system to complement decision-support in a real-time command center
US9924907B2 (en) * 2011-09-30 2018-03-27 Google Technology Holdings LLC Method and system for identifying location of a touched body part
US10446266B1 (en) 2011-10-03 2019-10-15 Emerge Clinical Solutions, LLC System and method for optimizing nuclear imaging appropriateness decisions
MX2014004399A (en) * 2011-10-10 2015-03-05 Abbvie Biotechnology Ltd Managing healthcare services.
EP2766866A4 (en) * 2011-10-14 2015-06-17 Univ Pennsylvania Discharge decision support system for post acute care referral
US9977864B2 (en) 2011-10-28 2018-05-22 Jeffrey S. Melcher Electronic health record system and method
US20140058755A1 (en) 2011-11-23 2014-02-27 Remedev, Inc. Remotely-executed medical diagnosis and therapy including emergency automation
CN102521501A (en) * 2011-12-07 2012-06-27 南京毗邻医疗科技有限公司 Simulation doctor system of intelligent medicine based on composite diagnosis and treatment template
US9384322B2 (en) 2011-12-12 2016-07-05 The Cleveland Clinic Foundation Storing structured and unstructured clinical information for information retrieval
US8818810B2 (en) 2011-12-29 2014-08-26 Robert Bosch Gmbh Speaker verification in a health monitoring system
US20130197933A1 (en) * 2012-01-26 2013-08-01 Affiliated Computer Services, Inc. Healthcare and Medical Information Management System
US10839046B2 (en) 2012-03-23 2020-11-17 Navya Network, Inc. Medical research retrieval engine
JP2013200592A (en) * 2012-03-23 2013-10-03 Fujifilm Corp Medical information retrieval device, method, and program
US20130268203A1 (en) * 2012-04-09 2013-10-10 Vincent Thekkethala Pyloth System and method for disease diagnosis through iterative discovery of symptoms using matrix based correlation engine
KR20150013146A (en) 2012-04-19 2015-02-04 로익스 다이어그노스틱스, 아이엔씨. Multiple layer gel
US8974115B2 (en) 2012-04-27 2015-03-10 Kinsa, Inc. Temperature measurement system and method
US10350278B2 (en) 2012-05-30 2019-07-16 Curemark, Llc Methods of treating Celiac disease
TWI582719B (en) * 2012-06-05 2017-05-11 長庚大學 Silver and wisdom family medical module and care service integration system platform
CN103565521B (en) * 2012-07-20 2016-06-22 数伦计算机技术(上海)有限公司 A kind of diabetes, cardiovascular and cerebrovascular disease monitoring and treatment system
EP2885759A4 (en) 2012-08-15 2016-02-10 Healthspot Inc Veterinary kiosk with integrated veterinary medical devices
US9232894B2 (en) 2012-08-27 2016-01-12 Koninklijke Philips N.V. Remote patient management system
TWI467521B (en) * 2012-08-30 2015-01-01 Chun Shin Ltd System and method for learning clinical diagnosis
US20140081659A1 (en) 2012-09-17 2014-03-20 Depuy Orthopaedics, Inc. Systems and methods for surgical and interventional planning, support, post-operative follow-up, and functional recovery tracking
EP2885636B1 (en) 2012-10-23 2018-02-14 Aytu BioScience, Inc. Methods and systems for measuring oxidation-reduction potential of a biological sample
US9171048B2 (en) 2012-12-03 2015-10-27 Wellclub, Llc Goal-based content selection and delivery
US9395234B2 (en) 2012-12-05 2016-07-19 Cardiocom, Llc Stabilizing base for scale
EP2936257A4 (en) 2012-12-18 2018-01-03 Coney, Lillie, Bruce Secure healthcare management and communication system
US9503902B1 (en) 2014-08-06 2016-11-22 Lillie Bruce Coney Proximity-based system that secures linked IP enabled devices
US20140180853A1 (en) * 2012-12-20 2014-06-26 Wal-Mart Stores, Inc. Framework for Generating a Personalized Item List
CN103020778A (en) * 2012-12-21 2013-04-03 中国人民解放军第三军医大学第二附属医院 Standardized therapy management system used for hematological malignancy patients
US9801541B2 (en) 2012-12-31 2017-10-31 Dexcom, Inc. Remote monitoring of analyte measurements
US9351670B2 (en) 2012-12-31 2016-05-31 Abbott Diabetes Care Inc. Glycemic risk determination based on variability of glucose levels
US9730620B2 (en) 2012-12-31 2017-08-15 Dexcom, Inc. Remote monitoring of analyte measurements
US10383580B2 (en) 2012-12-31 2019-08-20 Abbott Diabetes Care Inc. Analysis of glucose median, variability, and hypoglycemia risk for therapy guidance
US20140200908A1 (en) * 2013-01-16 2014-07-17 International Business Machines Corporation Integration into mobile applications designed to encourage medication adherence of a healthcare survey that compensates users for participation
US9256962B2 (en) 2013-01-23 2016-02-09 Orca Health Inc. Personalizing medical conditions with augmented reality
CN103164616A (en) * 2013-02-02 2013-06-19 杭州卓健信息科技有限公司 Intelligent hospital guide system and intelligent hospital guide method
US11735026B1 (en) * 2013-02-04 2023-08-22 C/Hca, Inc. Contextual assessment of current conditions
US10665348B1 (en) 2015-05-18 2020-05-26 C/Hca, Inc. Risk assessment and event detection
US10642958B1 (en) 2014-12-22 2020-05-05 C/Hca, Inc. Suggestion engine
US10672251B1 (en) * 2014-12-22 2020-06-02 C/Hca, Inc. Contextual assessment of current conditions
US9779611B1 (en) 2015-05-18 2017-10-03 HCA Holdings, Inc. Contextual assessment of current conditions
US8751039B1 (en) 2013-02-22 2014-06-10 Remedev, Inc. Remotely-executed medical therapy device
WO2014133993A1 (en) * 2013-02-27 2014-09-04 Interactive Intelligence, Inc. System and method for remote management and detection of client complications
US20140278449A1 (en) * 2013-03-12 2014-09-18 ZocDoc, Inc. Method and apparatus for guiding patients toward healthcare goals
US9445445B2 (en) 2013-03-14 2016-09-13 Dexcom, Inc. Systems and methods for processing and transmitting sensor data
EP3409201A1 (en) 2013-03-15 2018-12-05 Abbott Diabetes Care, Inc. System and method to manage diabetes based on glucose median, glucose variability, and hypoglycemic risk
US9858390B2 (en) * 2013-03-28 2018-01-02 Jacob Barhak Reference model for disease progression
EP2997536A4 (en) * 2013-05-17 2017-02-15 The Regents of the University of California Systems and methods for automatically evaluating medical patient symptoms and providing tailored prescriptions
US9955869B2 (en) * 2013-06-04 2018-05-01 Purdue Pharma L.P. System and method for supporting health management services
US20140364702A1 (en) 2013-06-06 2014-12-11 Valeriy Nasedkin Apparatus and method for functional state and/or performance assessment and training program adjustment
US20150006192A1 (en) 2013-06-26 2015-01-01 WellDoc, Inc. Systems and methods for clinical decision-making
US11361857B2 (en) 2013-06-26 2022-06-14 WellDoc, Inc. Systems and methods for creating and selecting models for predicting medical conditions
US20150019237A1 (en) * 2013-07-15 2015-01-15 Covidien Lp Holistic patient advisory system, method, and software
WO2015009385A1 (en) 2013-07-19 2015-01-22 Dexcom, Inc. Time averaged basal rate optimizer
WO2015021208A1 (en) * 2013-08-06 2015-02-12 Gamgee, Inc. Apparatus and methods for assisting and informing patients
US20150046174A1 (en) * 2013-08-12 2015-02-12 Orca Health, Inc. Computer-aided medical diagnosing and prescriptions
US9679247B2 (en) 2013-09-19 2017-06-13 International Business Machines Corporation Graph matching
US10276264B2 (en) 2013-10-08 2019-04-30 Mohan Kutty Electronic health record system and method
EP3910648A1 (en) * 2014-07-16 2021-11-17 Parkland Center for Clinical Innovation Client management tool system and method
US10028147B1 (en) 2014-08-06 2018-07-17 Bruce Corporation Dynamic defenses to secure a proximity-based communication system of linked wireless-enabled devices
BR112017004547B1 (en) 2014-09-08 2022-04-26 Becton, Dickinson And Company System for the preparation of a pharmaceutical compound and for the evaluation and verification of said preparation
JP2017533495A (en) * 2014-09-10 2017-11-09 アセンシア・ダイアベティス・ケア・ホールディングス・アーゲーAscensia Diabetes Care Holdings AG Smart logging for the management of health related issues
US20160092648A1 (en) * 2014-09-25 2016-03-31 George Mitchell Angelos Risk management system directed to health care environments and methods of using the same
US20180004904A1 (en) * 2014-10-24 2018-01-04 Qualdocs Medical, Llc Systems and methods for clinical decision support and documentation
KR20160080958A (en) * 2014-12-30 2016-07-08 삼성전자주식회사 Terminal for User, Driving Method of Terminal for Uer and Computer Readable Recording Medium
MX2017008947A (en) * 2015-01-10 2017-11-15 Dullen Deborah Method and apparatus for the measurement of autonomic function for the diagnosis and validation of patient treatments and outcomes.
US20160259899A1 (en) * 2015-03-04 2016-09-08 Expeda ehf Clinical decision support system for diagnosing and monitoring of a disease of a patient
EP3098739A1 (en) * 2015-05-26 2016-11-30 Hill-Rom Services, Inc. Healthcare communication system
WO2016193879A1 (en) * 2015-05-29 2016-12-08 Yeachareddy Kaushik Method and system for providing remote healthcare solution to a user in real-time
CN105118002A (en) * 2015-07-30 2015-12-02 芜湖卫健康物联网医疗科技有限公司 Five-step-method grading diagnosis system and method
CN106611095A (en) * 2015-10-16 2017-05-03 完全优诊所 Health classification apparatus
CA3002096C (en) 2015-12-28 2023-08-01 Dexcom, Inc. Systems and methods for remote and host monitoring communications
US10558785B2 (en) 2016-01-27 2020-02-11 International Business Machines Corporation Variable list based caching of patient information for evaluation of patient rules
US10528702B2 (en) 2016-02-02 2020-01-07 International Business Machines Corporation Multi-modal communication with patients based on historical analysis
US10395330B2 (en) 2016-02-17 2019-08-27 International Business Machines Corporation Evaluating vendor communications for accuracy and quality
US10437957B2 (en) 2016-02-17 2019-10-08 International Business Machines Corporation Driving patient campaign based on trend patterns in patient registry information
US10685089B2 (en) 2016-02-17 2020-06-16 International Business Machines Corporation Modifying patient communications based on simulation of vendor communications
US11037658B2 (en) 2016-02-17 2021-06-15 International Business Machines Corporation Clinical condition based cohort identification and evaluation
US10565309B2 (en) 2016-02-17 2020-02-18 International Business Machines Corporation Interpreting the meaning of clinical values in electronic medical records
US10937526B2 (en) 2016-02-17 2021-03-02 International Business Machines Corporation Cognitive evaluation of assessment questions and answers to determine patient characteristics
US10825555B2 (en) * 2016-03-11 2020-11-03 Safe Lane Health, Inc. Systems and methods for managing a database during an examination
US20190096531A1 (en) * 2016-03-16 2019-03-28 Aayuv Technologies Private Limited System and method of preventive health management for assessing an individual's health through consolidation and digitization of medical records
US10311388B2 (en) 2016-03-22 2019-06-04 International Business Machines Corporation Optimization of patient care team based on correlation of patient characteristics and care provider characteristics
US10923231B2 (en) 2016-03-23 2021-02-16 International Business Machines Corporation Dynamic selection and sequencing of healthcare assessments for patients
EP3223181B1 (en) 2016-03-24 2019-12-18 Sofradim Production System and method of generating a model and simulating an effect on a surgical repair site
CA3133253A1 (en) 2016-03-31 2017-10-05 Dexcom, Inc. Systems and methods for display device and sensor electronics unit communication
US9899038B2 (en) 2016-06-30 2018-02-20 Karen Elaine Khaleghi Electronic notebook system
WO2018057742A1 (en) * 2016-09-21 2018-03-29 Ava Health Technologies, Inc. Platform for assessing and treating individuals by sourcing information from groups of resources
CA3039682A1 (en) * 2016-10-12 2018-04-19 Becton, Dickinson And Company Integrated disease management system
US20200118686A1 (en) * 2017-04-06 2020-04-16 Akili Interactive Labs, Inc. Distributed network for the secured collection, analysis, and sharing of data across platforms
EP3624678B1 (en) * 2017-05-19 2022-08-17 Boston Scientific Scimed Inc. Systems and methods for assessing the health status of a patient
US10485454B2 (en) 2017-05-24 2019-11-26 Neuropath Sprl Systems and methods for markerless tracking of subjects
US11432773B2 (en) * 2017-05-24 2022-09-06 Neuropath Sprl Monitoring of diagnostic indicators and quality of life
CN109147930A (en) * 2017-06-28 2019-01-04 京东方科技集团股份有限公司 Divide and examines dialogue method, divides and examine conversational device and system
US10852264B2 (en) 2017-07-18 2020-12-01 Boston Scientific Scimed, Inc. Systems and methods for analyte sensing in physiological gas samples
US20190043501A1 (en) * 2017-08-02 2019-02-07 Elements of Genius, Inc. Patient-centered assistive system for multi-therapy adherence intervention and care management
CA3072427C (en) * 2017-08-08 2023-12-05 Fresenius Medical Care Holdings, Inc. Systems and methods for treating and estimating progression of chronic kidney disease
CN111246797A (en) 2017-10-24 2020-06-05 德克斯康公司 Pre-attached analyte sensors
US11331022B2 (en) 2017-10-24 2022-05-17 Dexcom, Inc. Pre-connected analyte sensors
US10635521B2 (en) 2017-12-15 2020-04-28 International Business Machines Corporation Conversational problem determination based on bipartite graph
CA3090216A1 (en) * 2018-01-31 2019-08-08 Curelator, Inc. Early feedback of disease factors to improve patient quality of life, engagement and persistence
US10235998B1 (en) 2018-02-28 2019-03-19 Karen Elaine Khaleghi Health monitoring system and appliance
WO2019195146A1 (en) * 2018-04-03 2019-10-10 Boston Scientific Scimed, Inc. Systems and methods for diagnosing and/or monitoring disease
US20210202065A1 (en) * 2018-05-17 2021-07-01 Ieso Digital Health Limited Methods and systems for improved therapy delivery and monitoring
US11177039B2 (en) 2018-05-22 2021-11-16 International Business Machines Corporation Assessing a treatment service based on a measure of trust dynamics
US11033740B2 (en) 2018-05-22 2021-06-15 Boston Scientific Neuromodulation Corporation Adaptive electrical neurostimulation treatment to reduce pain perception
EP3796969A1 (en) 2018-05-22 2021-03-31 Boston Scientific Neuromodulation Corporation Adaptive chronic pain relief via implanted electrical neurostimulation
US10943674B2 (en) 2018-05-22 2021-03-09 International Business Machines Corporation Updating a clinical trial participation status based on a measure of trust dynamics
US10964433B2 (en) 2018-05-22 2021-03-30 International Business Machines Corporation Assessing a medical procedure based on a measure of trust dynamics
US10957434B2 (en) 2018-05-22 2021-03-23 International Business Machines Corporation Updating a prescription status based on a measure of trust dynamics
US11557398B2 (en) 2018-05-22 2023-01-17 International Business Machines Corporation Delivering a chemical compound based on a measure of trust dynamics
US11004563B2 (en) * 2018-05-22 2021-05-11 International Business Machines Corporation Adaptive pain management and reduction based on monitoring user conditions
CN109036506B (en) * 2018-07-25 2023-04-18 平安科技(深圳)有限公司 Internet medical inquiry supervision method, electronic device and readable storage medium
CN109308945A (en) * 2018-09-17 2019-02-05 辽宁智飞科技有限公司 Discrete stages data processing and method for tracing and system
CN109524069B (en) * 2018-11-09 2021-09-10 南京医渡云医学技术有限公司 Medical data processing method and device, electronic equipment and storage medium
US11621081B1 (en) * 2018-11-13 2023-04-04 Iqvia Inc. System for predicting patient health conditions
WO2020112825A1 (en) 2018-11-27 2020-06-04 Boston Scientific Scimed, Inc. Systems and methods for detecting a health condition
WO2020112147A1 (en) * 2018-11-30 2020-06-04 National Cheng Kung University Method of an interactive health status assessment and system thereof
US10978209B2 (en) * 2018-11-30 2021-04-13 National Cheng Kung University Method of an interactive health status assessment and system thereof
US11894139B1 (en) 2018-12-03 2024-02-06 Patientslikeme Llc Disease spectrum classification
EP3899515B1 (en) 2018-12-18 2023-01-25 Boston Scientific Scimed Inc. Systems and methods for measuring kinetic response of chemical sensor elements comprising graphene varactors
CN109887611A (en) * 2019-02-13 2019-06-14 北京大学第三医院(北京大学第三临床医学院) A kind of medical management system and mobile terminal
US10559307B1 (en) 2019-02-13 2020-02-11 Karen Elaine Khaleghi Impaired operator detection and interlock apparatus
RU2720733C1 (en) * 2019-02-28 2020-05-13 Михаил Михайлович Михайлов System of remote interaction between attending physician and user
US11514339B2 (en) * 2019-04-24 2022-11-29 Optum, Inc. Machine-learning based recommendation engine providing transparency in generation of recommendations
CN114126693A (en) 2019-05-16 2022-03-01 瑞思迈私人有限公司 Bidirectional communication in medical devices
US10735191B1 (en) 2019-07-25 2020-08-04 The Notebook, Llc Apparatus and methods for secure distributed communications and data access
WO2021046386A1 (en) * 2019-09-05 2021-03-11 Michael Lindemann Measuring spatial working memory using mobile-optimized software tools
TWI730437B (en) * 2019-10-02 2021-06-11 亞法貝德生技股份有限公司 Method of using a teaching appliance used to experience the recruitment processes of human subjects in clinical trials
EP3848940A1 (en) * 2020-01-08 2021-07-14 Koninklijke Philips N.V. A system and method for triggering an action based on a disease severity or affective state of a subject
US11309091B2 (en) 2020-03-18 2022-04-19 Kinsa Inc. Systems and methods for contagious illness surveillance and outbreak detection
US11580424B2 (en) 2020-04-06 2023-02-14 International Business Machines Corporation Automatically refining application of a hierarchical coding system to optimize conversation system dialog-based responses to a user
US20230197289A1 (en) * 2020-04-29 2023-06-22 Laurence Richard Olivier Epidemic Monitoring System
CN111563891B (en) * 2020-05-09 2023-09-26 吾征智能技术(北京)有限公司 Disease prediction system based on color cognition
US20230215566A1 (en) * 2020-05-26 2023-07-06 Empowr-Me Llc, D/B/A Healthintel Llc System and method for automated diagnosis
US11541009B2 (en) 2020-09-10 2023-01-03 Curemark, Llc Methods of prophylaxis of coronavirus infection and treatment of coronaviruses
US20220122700A1 (en) * 2020-10-20 2022-04-21 LiveBeyond Predictive Electronic Healthcare Record Systems and Methods for the Developing World
KR20230116794A (en) 2020-10-30 2023-08-04 레스메드 피티와이 엘티디 Two-way communication in medical devices
CN112259183B (en) * 2020-11-11 2023-08-08 北京嘉和海森健康科技有限公司 Method and device for extracting patient health time axis based on electronic medical record
CN116762011A (en) * 2020-12-02 2023-09-15 贝克曼库尔特有限公司 Detection of probability of developing sepsis
US20230317291A1 (en) * 2021-02-05 2023-10-05 Parkland Center For Clinical Innovation Clinical Contextual Insight and Decision Support Visualization Tool
US20220384036A1 (en) * 2021-06-01 2022-12-01 Vital Connect, Inc. Scalable architecture system for clinician defined analytics
US20230041745A1 (en) * 2021-08-06 2023-02-09 Nuance Communications, Inc. Telehealth Assistance System and Method

Citations (213)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3970996A (en) 1973-02-28 1976-07-20 Perfect Liberty Apparatus for collecting medical data
US4051522A (en) 1975-05-05 1977-09-27 Jonathan Systems Patient monitoring system
US4220160A (en) 1978-07-05 1980-09-02 Clinical Systems Associates, Inc. Method and apparatus for discrimination and detection of heart sounds
US4290114A (en) 1976-07-01 1981-09-15 Sinay Hanon S Medical diagnostic computer
US4315309A (en) 1979-06-25 1982-02-09 Coli Robert D Integrated medical test data storage and retrieval system
US4337377A (en) 1980-01-10 1982-06-29 Riper Wilbur E Van Biologic apparatus
US4428381A (en) 1981-03-13 1984-01-31 Medtronic, Inc. Monitoring device
US4458693A (en) 1981-03-13 1984-07-10 Medtronic, Inc. Monitoring system
US4465077A (en) 1981-11-12 1984-08-14 Howard Schneider Apparatus and method of determining fertility status
US4531527A (en) 1982-04-23 1985-07-30 Survival Technology, Inc. Ambulatory monitoring system with real time analysis and telephone transmission
US4606352A (en) 1984-07-13 1986-08-19 Purdue Research Foundation Personal electrocardiogram monitor
US4712562A (en) 1985-01-08 1987-12-15 Jacques J. Ohayon Outpatient monitoring systems
US4731726A (en) 1986-05-19 1988-03-15 Healthware Corporation Patient-operated glucose monitor and diabetes management system
US4733354A (en) 1984-11-23 1988-03-22 Brian Potter Method and apparatus for automated medical diagnosis using decision tree analysis
US4770189A (en) 1986-09-02 1988-09-13 Industrial Technology Research Institute Real time multitask electronic stethoscopy system
US4803625A (en) 1986-06-30 1989-02-07 Buddy Systems, Inc. Personal health monitor
US4825869A (en) 1987-09-28 1989-05-02 Telectronics N.V. System for automatically performing a clinical assessment of an implanted pacer based on information that is telemetrically received
US4838275A (en) 1985-11-29 1989-06-13 Lee Arnold St J Home medical surveillance system
US4839822A (en) 1987-08-13 1989-06-13 501 Synthes (U.S.A.) Computer system and method for suggesting treatments for physical trauma
EP0320749A2 (en) 1987-12-09 1989-06-21 ARCH DEVELOPMENT CORPORATION, The University of Chicago Portable medical history-taking device
US4858121A (en) 1986-12-12 1989-08-15 Medical Payment Systems, Incorporated Medical payment system
US4868763A (en) 1986-02-21 1989-09-19 Hitachi, Ltd. Knowledge-based system having plural processors
US4933873A (en) 1988-05-12 1990-06-12 Healthtech Services Corp. Interactive patient assistance device
US4945476A (en) 1988-02-26 1990-07-31 Elsevier Science Publishing Company, Inc. Interactive system and method for creating and editing a knowledge base for use as a computerized aid to the cognitive process of diagnosis
US4962491A (en) 1988-10-13 1990-10-09 Schaeffer Theodore S Medicament dispenser and medical information storage apparatus
US4974607A (en) 1987-08-20 1990-12-04 Satoru Miwa System for centralized management of medical data
US4975840A (en) 1988-06-17 1990-12-04 Lincoln National Risk Management, Inc. Method and apparatus for evaluating a potentially insurable risk
US5012411A (en) 1985-07-23 1991-04-30 Charles J. Policastro Apparatus for monitoring, storing and transmitting detected physiological information
US5012815A (en) 1989-02-02 1991-05-07 Yale University Dynamic spectral phonocardiograph
US5018526A (en) * 1989-02-28 1991-05-28 Gaston Johansson Fannie Apparatus and method for providing a multidimensional indication of pain
US5019974A (en) * 1987-05-01 1991-05-28 Diva Medical Systems Bv Diabetes management system and apparatus
US5023785A (en) 1987-11-16 1991-06-11 Becton & Dickinson Co. Hematology - diagnosis apparatus employing expert system technology
US5030948A (en) 1988-09-19 1991-07-09 Rush Charles T Multiple characteristic sensitive addressing schema for a multiple receiver data processing network
EP0447710A1 (en) 1990-03-19 1991-09-25 Takeshi Makitsubo Electrocardiographic data transmission system
US5054493A (en) 1986-01-31 1991-10-08 Regents Of The University Of Minnesota Method for diagnosing, monitoring and treating hypertension
US5084819A (en) 1988-11-10 1992-01-28 Response Technologies Inc. Data collection, analysis, and response system and method
US5099424A (en) 1989-07-20 1992-03-24 Barry Schneiderman Model user application system for clinical data processing that tracks and monitors a simulated out-patient medical practice using data base management software
US5113869A (en) 1990-08-21 1992-05-19 Telectronics Pacing Systems, Inc. Implantable ambulatory electrocardiogram monitor
US5126957A (en) 1989-09-29 1992-06-30 Health Tech Services Corp. Interactive medication delivery system
EP0531889A2 (en) 1991-09-11 1993-03-17 Hewlett-Packard Company Data processing system and method for automatically performing prioritized nursing diagnoses from patient assessment data
US5196682A (en) 1986-06-30 1993-03-23 Wang Laboratories, Inc. Infrared optical card having an opaque case for hiding internal components
US5228449A (en) 1991-01-22 1993-07-20 Athanasios G. Christ System and method for detecting out-of-hospital cardiac emergencies and summoning emergency assistance
US5235510A (en) 1990-11-22 1993-08-10 Kabushiki Kaisha Toshiba Computer-aided diagnosis system for medical use
US5241621A (en) 1991-06-26 1993-08-31 Digital Equipment Corporation Management issue recognition and resolution knowledge processor
US5255187A (en) 1990-04-03 1993-10-19 Sorensen Mark C Computer aided medical diagnostic method and apparatus
US5257627A (en) 1991-11-14 1993-11-02 Telmed, Inc. Portable non-invasive testing apparatus
US5263123A (en) 1990-09-10 1993-11-16 Hitachi Engineering Co., Ltd. Fuzzy backward reasoning system and expert system utilizing the same
US5265613A (en) 1992-04-03 1993-11-30 Telmed, Inc. Portable non-invasive testing apparatus with logarithmic amplification
US5299121A (en) 1992-06-04 1994-03-29 Medscreen, Inc. Non-prescription drug medication screening system
US5307263A (en) 1992-11-17 1994-04-26 Raya Systems, Inc. Modular microprocessor-based health monitoring system
US5337752A (en) 1992-05-21 1994-08-16 Mcg International, Inc. System for simultaneously producing and synchronizing spectral patterns of heart sounds and an ECG signal
US5347632A (en) 1988-07-15 1994-09-13 Prodigy Services Company Reception system for an interactive computer network and method of operation
US5357427A (en) 1993-03-15 1994-10-18 Digital Equipment Corporation Remote monitoring of high-risk patients using artificial intelligence
US5377258A (en) 1993-08-30 1994-12-27 National Medical Research Council Method and apparatus for an automated and interactive behavioral guidance system
US5390238A (en) 1992-06-15 1995-02-14 Motorola, Inc. Health support system
US5389078A (en) * 1993-10-06 1995-02-14 Sims Deltec, Inc. Programmable infusion pump for administering medication to patients
EP0643360A2 (en) 1993-09-10 1995-03-15 Toa Medical Electronics Co., Ltd. Clinical test result display apparatus
US5415167A (en) 1992-01-10 1995-05-16 Wilk; Peter J. Medical system and associated method for automatic diagnosis and treatment
US5418888A (en) 1992-06-04 1995-05-23 Alden; John L. System for revelance criteria management of actions and values in a rete network
US5421343A (en) 1992-04-03 1995-06-06 Feng; Genquan Computer network EEMPI system
US5435324A (en) 1992-08-21 1995-07-25 Compass Information Services, Inc. Apparatus for measuring psychotherapy outcomes
US5437278A (en) 1992-01-10 1995-08-01 Wilk; Peter J. Medical diagnosis system and method
US5442728A (en) 1988-05-12 1995-08-15 Healthtech Services Corp. Interactive patient assistance device for storing and dispensing a testing device
US5441047A (en) 1992-03-25 1995-08-15 David; Daniel Ambulatory patient health monitoring techniques utilizing interactive visual communication
US5463548A (en) 1990-08-28 1995-10-31 Arch Development Corporation Method and system for differential diagnosis based on clinical and radiological information using artificial neural networks
US5464012A (en) 1993-09-13 1995-11-07 Hewlett-Packard Company Patient alarm detection using target mode
US5471382A (en) 1994-01-10 1995-11-28 Informed Access Systems, Inc. Medical network management system and process
US5473537A (en) 1993-07-30 1995-12-05 Psychresources Development Company Method for evaluating and reviewing a patient's condition
US5481647A (en) 1991-03-22 1996-01-02 Raff Enterprises, Inc. User adaptable expert system
US5482035A (en) 1993-03-19 1996-01-09 Instrumentarium Corporation Method for monitoring the condition of a patient
US5486999A (en) 1994-04-20 1996-01-23 Mebane; Andrew H. Apparatus and method for categorizing health care utilization
DE4430164A1 (en) 1994-08-25 1996-02-29 Uthe Friedrich Wilhelm Interactive computer based system for medical diagnostics
US5501229A (en) 1994-08-01 1996-03-26 New England Medical Center Hospital Continuous monitoring using a predictive instrument
US5517405A (en) 1993-10-14 1996-05-14 Aetna Life And Casualty Company Expert system for providing interactive assistance in solving problems such as health care management
US5519433A (en) 1991-11-20 1996-05-21 Zing Systems, L.P. Interactive television security through transaction time stamping
US5533522A (en) 1989-10-30 1996-07-09 Feng; Genquan Method of and arrangement for optimizing disease diagnosis
US5541977A (en) 1993-03-11 1996-07-30 At&T Corp. Method and apparatus for preventing wireless fraud
US5544649A (en) 1992-03-25 1996-08-13 Cardiomedix, Inc. Ambulatory patient health monitoring techniques utilizing interactive visual communication
US5555169A (en) 1992-05-20 1996-09-10 Hitachi, Ltd. Computer system and method for converting a conversational statement to computer command language
US5553609A (en) 1995-02-09 1996-09-10 Visiting Nurse Service, Inc. Intelligent remote visual monitoring system for home health care service
US5572421A (en) 1987-12-09 1996-11-05 Altman; Louis Portable medical questionnaire presentation device
US5583758A (en) 1992-06-22 1996-12-10 Health Risk Management, Inc. Health care management system for managing medical treatments and comparing user-proposed and recommended resources required for treatment
US5584291A (en) 1993-03-26 1996-12-17 Instrumentarium, Oy Method for recognizing and identifying emergency situations in an anesthesia system by means of a self-organizing map
US5590648A (en) * 1992-11-30 1997-01-07 Tremont Medical Personal health care system
US5594638A (en) 1993-12-29 1997-01-14 First Opinion Corporation Computerized medical diagnostic system including re-enter function and sensitivity factors
DE4430184C2 (en) 1993-09-03 1997-01-30 Fette Wilhelm Gmbh Axial thread rolling head
US5601435A (en) 1994-11-04 1997-02-11 Intercare Method and apparatus for interactively monitoring a physiological condition and for interactively providing health related information
US5619991A (en) 1995-04-26 1997-04-15 Lucent Technologies Inc. Delivery of medical services using electronic data communications
US5633910A (en) 1994-09-13 1997-05-27 Cohen; Kopel H. Outpatient monitoring system
EP0720663B1 (en) 1993-01-20 1997-06-11 Delot Process S.A. Method for dimensioning an electroplating enclosure with a magnetic wiping device for electroplated metallurgical products
US5642731A (en) 1990-01-17 1997-07-01 Informedix, Inc. Method of and apparatus for monitoring the management of disease
US5642936A (en) 1996-01-29 1997-07-01 Oncormed Methods for identifying human hereditary disease patterns
US5659793A (en) 1994-12-22 1997-08-19 Bell Atlantic Video Services, Inc. Authoring tools for multimedia application development and network delivery
US5660176A (en) 1993-12-29 1997-08-26 First Opinion Corporation Computerized medical diagnostic and treatment advice system
US5672154A (en) 1992-08-27 1997-09-30 Minidoc I Uppsala Ab Method and apparatus for controlled individualized medication
US5678562A (en) 1995-11-09 1997-10-21 Burdick, Inc. Ambulatory physiological monitor with removable disk cartridge and wireless modem
US5692220A (en) 1993-09-02 1997-11-25 Coulter Corporation Decision support system and method for diagnosis consultation in laboratory hematopathology
US5692501A (en) 1993-09-20 1997-12-02 Minturn; Paul Scientific wellness personal/clinical/laboratory assessments, profile and health risk managment system with insurability rankings on cross-correlated 10-point optical health/fitness/wellness scales
US5694939A (en) 1995-10-03 1997-12-09 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Autogenic-feedback training exercise (AFTE) method and system
US5703786A (en) 1995-08-14 1997-12-30 Profile Systems, Llc Medication dispensing and timing system utilizing time reference message
US5704366A (en) 1994-05-23 1998-01-06 Enact Health Management Systems System for monitoring and reporting medical measurements
US5711297A (en) 1993-12-29 1998-01-27 First Opinion Corporation Computerized medical advice system and method including meta function
US5720502A (en) 1996-11-08 1998-02-24 Cain; John R. Pain location and intensity communication apparatus and method
US5724025A (en) 1993-10-21 1998-03-03 Tavori; Itzchak Portable vital signs monitor
US5724983A (en) 1994-08-01 1998-03-10 New England Center Hospitals, Inc. Continuous monitoring using a predictive instrument
US5732397A (en) 1992-03-16 1998-03-24 Lincoln National Risk Management, Inc. Automated decision-making arrangement
US5733313A (en) * 1996-08-01 1998-03-31 Exonix Corporation RF coupled, implantable medical device with rechargeable back-up power source
US5746204A (en) 1995-12-07 1998-05-05 Carbon Based Corporation Disease indicator analysis system
US5769074A (en) 1994-10-13 1998-06-23 Horus Therapeutics, Inc. Computer assisted methods for diagnosing diseases
US5772585A (en) 1996-08-30 1998-06-30 Emc, Inc System and method for managing patient medical records
US5778882A (en) * 1995-02-24 1998-07-14 Brigham And Women's Hospital Health monitoring system
US5788640A (en) 1995-10-26 1998-08-04 Peters; Robert Mitchell System and method for performing fuzzy cluster classification of stress tests
US5794208A (en) 1996-03-01 1998-08-11 Goltra; Peter S. Creating and using protocols to create and review a patient chart
US5800347A (en) 1995-11-03 1998-09-01 The General Hospital Corporation ROC method for early detection of disease
US5802495A (en) 1996-03-01 1998-09-01 Goltra; Peter Phrasing structure for the narrative display of findings
US5809476A (en) 1994-03-23 1998-09-15 Ryan; John Kevin System for converting medical information into representative abbreviated codes with correction capability
US5812984A (en) 1996-05-13 1998-09-22 Goltra; Peter S. Method for entering information into an electronic patient chart, and protocol auto-negative capabilities
US5822715A (en) 1997-01-10 1998-10-13 Health Hero Network Diabetes management system and method for controlling blood glucose
US5823949A (en) 1996-03-01 1998-10-20 Goltra; Peter S. Intelligent prompting
US5828943A (en) 1994-04-26 1998-10-27 Health Hero Network, Inc. Modular microprocessor-based diagnostic measurement apparatus and method for psychological conditions
US5832448A (en) 1996-10-16 1998-11-03 Health Hero Network Multiple patient monitoring system for proactive health management
US5835900A (en) 1992-10-05 1998-11-10 Expert Systems Publishing Co. Computer-implemented decision management system with dynamically generated questions and answer choices
US5839430A (en) 1996-04-26 1998-11-24 Cama; Joseph Combination inhaler and peak flow rate meter
US5862304A (en) 1990-05-21 1999-01-19 Board Of Regents, The University Of Texas System Method for predicting the future occurrence of clinically occult or non-existent medical conditions
US5879163A (en) 1996-06-24 1999-03-09 Health Hero Network, Inc. On-line health education and feedback system using motivational driver profile coding and automated content fulfillment
US5887133A (en) 1997-01-15 1999-03-23 Health Hero Network System and method for modifying documents sent over a communications network
US5897493A (en) 1997-03-28 1999-04-27 Health Hero Network, Inc. Monitoring system for remotely querying individuals
US5899855A (en) 1992-11-17 1999-05-04 Health Hero Network, Inc. Modular microprocessor-based health monitoring system
US5903211A (en) * 1997-02-07 1999-05-11 Althin Medical, Inc. Medical treatment device with a user interface adapted for home or limited care environments
US5908383A (en) 1997-09-17 1999-06-01 Brynjestad; Ulf Knowledge-based expert interactive system for pain
US5909679A (en) 1996-11-08 1999-06-01 At&T Corp Knowledge-based moderator for electronic mail help lists
US5911132A (en) 1995-04-26 1999-06-08 Lucent Technologies Inc. Method using central epidemiological database
US5918603A (en) 1994-05-23 1999-07-06 Health Hero Network, Inc. Method for treating medical conditions using a microprocessor-based video game
US5933136A (en) 1996-12-23 1999-08-03 Health Hero Network, Inc. Network media access control system for encouraging patient compliance with a treatment plan
US5935060A (en) 1996-07-12 1999-08-10 First Opinion Corporation Computerized medical diagnostic and treatment advice system including list based processing
US5940801A (en) 1994-04-26 1999-08-17 Health Hero Network, Inc. Modular microprocessor-based diagnostic measurement apparatus and method for psychological conditions
US5951300A (en) 1997-03-10 1999-09-14 Health Hero Network Online system and method for providing composite entertainment and health information
US5960403A (en) 1992-11-17 1999-09-28 Health Hero Network Health management process control system
US5970463A (en) 1996-05-01 1999-10-19 Practice Patterns Science, Inc. Medical claims integration and data analysis system
US5974389A (en) 1996-03-01 1999-10-26 Clark; Melanie Ann Medical record management system and process with improved workflow features
US5976082A (en) 1996-06-17 1999-11-02 Smithkline Beecham Corporation Method for identifying at risk patients diagnosed with congestive heart failure
US5987519A (en) 1996-09-20 1999-11-16 Georgia Tech Research Corporation Telemedicine system using voice video and data encapsulation and de-encapsulation for communicating medical information between central monitoring stations and remote patient monitoring stations
US5997476A (en) 1997-03-28 1999-12-07 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US6001060A (en) 1996-06-04 1999-12-14 Regents Of The University Of California Video data representation of physiological data
US6022315A (en) 1993-12-29 2000-02-08 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
US6032119A (en) 1997-01-16 2000-02-29 Health Hero Network, Inc. Personalized display of health information
US6032678A (en) 1997-03-14 2000-03-07 Shraga Rottem Adjunct to diagnostic imaging systems for analysis of images of an object or a body part or organ
US6059724A (en) 1997-02-14 2000-05-09 Biosignal, Inc. System for predicting future health
WO2000032088A1 (en) 1998-11-30 2000-06-08 Novo Nordisk A/S A medical system and a method of controlling the system for use by a patient for medical self treatment
US6081786A (en) 1998-04-03 2000-06-27 Triangle Pharmaceuticals, Inc. Systems, methods and computer program products for guiding the selection of therapeutic treatment regimens
US6101478A (en) 1997-04-30 2000-08-08 Health Hero Network Multi-user remote health monitoring system
US6106459A (en) 1996-03-29 2000-08-22 Clawson; Jeffrey J. Method and system for the entry protocol of an emergency medical dispatch system
US6117073A (en) 1998-03-02 2000-09-12 Jones; Scott J. Integrated emergency medical transportation database system
US6149585A (en) 1998-10-28 2000-11-21 Sage Health Management Solutions, Inc. Diagnostic enhancement method and apparatus
US6151586A (en) 1996-12-23 2000-11-21 Health Hero Network, Inc. Computerized reward system for encouraging participation in a health management program
US6161095A (en) 1998-12-16 2000-12-12 Health Hero Network, Inc. Treatment regimen compliance and efficacy with feedback
US6168563B1 (en) 1992-11-17 2001-01-02 Health Hero Network, Inc. Remote health monitoring and maintenance system
US6177940B1 (en) 1995-09-20 2001-01-23 Cedaron Medical, Inc. Outcomes profile management system for evaluating treatment effectiveness
US6186145B1 (en) 1994-05-23 2001-02-13 Health Hero Network, Inc. Method for diagnosis and treatment of psychological and emotional conditions using a microprocessor-based virtual reality simulator
US6189029B1 (en) 1996-09-20 2001-02-13 Silicon Graphics, Inc. Web survey tool builder and result compiler
US6196970B1 (en) 1999-03-22 2001-03-06 Stephen J. Brown Research data collection and analysis
US6206829B1 (en) 1996-07-12 2001-03-27 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
CN1291749A (en) 2000-11-16 2001-04-18 上海交通大学 Intelligent system for domestic remote medical monitor and consultation
US6230142B1 (en) 1997-12-24 2001-05-08 Homeopt, Llc Health care data manipulation and analysis system
US6234964B1 (en) 1997-03-13 2001-05-22 First Opinion Corporation Disease management system and method
US6240393B1 (en) 1998-06-05 2001-05-29 Health Pro Network, Inc. Aggregating and pooling weight loss information in a communication system with feedback
US6247002B1 (en) 1996-12-11 2001-06-12 Sony Corporation Method and apparatus for extracting features characterizing objects, and use thereof
US6246975B1 (en) 1996-10-30 2001-06-12 American Board Of Family Practice, Inc. Computer architecture and process of patient generation, evolution, and simulation for computer based testing system
US6248065B1 (en) 1997-04-30 2001-06-19 Health Hero Network, Inc. Monitoring system for remotely querying individuals
US6270455B1 (en) 1997-03-28 2001-08-07 Health Hero Network, Inc. Networked system for interactive communications and remote monitoring of drug delivery
WO2001061616A2 (en) 2000-02-14 2001-08-23 First Opinion Corporation Automated diagnostic system and method
JP3202047B2 (en) 1991-11-25 2001-08-27 株式会社オキシーテック Large depth transducer sensitivity measurement system
US20010039503A1 (en) 2000-04-28 2001-11-08 Chan Bryan K. Method and system for managing chronic disease and wellness online
US6330426B2 (en) 1994-05-23 2001-12-11 Stephen J. Brown System and method for remote education using a memory card
US6334778B1 (en) 1994-04-26 2002-01-01 Health Hero Network, Inc. Remote psychological diagnosis and monitoring system
US20020029157A1 (en) 2000-07-20 2002-03-07 Marchosky J. Alexander Patient - controlled automated medical record, diagnosis, and treatment system and method
WO2002039250A2 (en) 2000-11-13 2002-05-16 Siemens Medical Solutions Usa, Inc. A system and method for navigating patient medical information
WO2002042876A2 (en) 2000-11-22 2002-05-30 Recare, Inc. Systems and methods for integrating disease management into a physician workflow
US20020148477A1 (en) 2001-04-17 2002-10-17 Lg Electronics Inc. System and method of performing medical diagnosis in real time
US20020186818A1 (en) 2000-08-29 2002-12-12 Osteonet, Inc. System and method for building and manipulating a centralized measurement value database
US20030069753A1 (en) 1992-11-17 2003-04-10 Brown Stephen J. Multi-user remote health monitoring system with biometrics support
WO2003040879A2 (en) 2001-11-02 2003-05-15 Siemens Medical Solutions Usa, Inc. Patient data mining with population-based analysis
US6597392B1 (en) 1997-10-14 2003-07-22 Healthcare Vision, Inc. Apparatus and method for computerized multi-media data organization and transmission
US6598035B2 (en) 1995-11-17 2003-07-22 International Business Machines Corporation Object oriented rule-based expert system framework mechanism
US6601055B1 (en) 1996-12-27 2003-07-29 Linda M. Roberts Explanation generation system for a diagnosis support tool employing an inference system
US20030181790A1 (en) 2000-05-18 2003-09-25 Daniel David Methods and apparatus for facilitated, hierarchical medical diagnosis and symptom coding and definition
US20040017475A1 (en) 1997-10-14 2004-01-29 Akers William Rex Apparatus and method for computerized multi-media data organization and transmission
US20040019259A1 (en) 1992-11-17 2004-01-29 Brown Stephen J. Remote monitoring and data management platform
US6687685B1 (en) 2000-04-07 2004-02-03 Dr. Red Duke, Inc. Automated medical decision making utilizing bayesian network knowledge domain modeling
CN1477581A (en) 2003-07-01 2004-02-25 南京大学 Predictive modelling method application to computer-aided medical diagnosis
US6725209B1 (en) 1993-12-29 2004-04-20 First Opinion Corporation Computerized medical diagnostic and treatment advice system and method including mental status examination
US20040107116A1 (en) 1992-11-17 2004-06-03 Health Hero Network, Inc. Networked health information system for monitoring food intake
US20040116780A1 (en) 1992-11-17 2004-06-17 Brown Stephen J. Method and system for improving adherence with a diet program or other medical regimen
US20040199409A1 (en) 1992-11-17 2004-10-07 Brown Stephen J. Remote health monitoring and maintenance system
US20050010444A1 (en) 2003-06-06 2005-01-13 Iliff Edwin C. System and method for assisting medical diagnosis using an anatomic system and cause matrix
US20050010088A1 (en) 2003-05-15 2005-01-13 Iliff Edwin C. Panel diagnostic method and system
US20050060194A1 (en) 2003-04-04 2005-03-17 Brown Stephen J. Method and system for monitoring health of an individual
US6900807B1 (en) 2000-03-08 2005-05-31 Accenture Llp System for generating charts in a knowledge management tool
US20050177391A1 (en) 2001-10-23 2005-08-11 Hideki Shimizu Health management system and health management program
US20050228883A1 (en) 1997-03-28 2005-10-13 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20050234306A1 (en) 2002-06-20 2005-10-20 Martin Schulte Method and system for detecting and analyzing clinical pictures and the causes thereof and for determining proposals for appropriate therapy
US20050273359A1 (en) 2004-06-03 2005-12-08 Young David E System and method of evaluating preoperative medical care and determining recommended tests based on patient health history and medical condition and nature of surgical procedure
US20060135859A1 (en) 2004-10-22 2006-06-22 Iliff Edwin C Matrix interface for medical diagnostic and treatment advice system and method
US7076437B1 (en) 1999-10-29 2006-07-11 Victor Levy Process for consumer-directed diagnostic and health care information
US20060241975A1 (en) 1992-11-17 2006-10-26 Health Hero Network, Inc. Multi-user remote health monitoring system with biometrics support
US7305348B1 (en) 1996-02-20 2007-12-04 Health Hero Network, Inc. Aggregating and pooling health related information in a communication system with feedback
JP4056561B2 (en) 1995-06-01 2008-03-05 ビドリエラ・モンテレイ,エセ・ア・デ・セ・ウベ Method and apparatus for decorating bottles or similar articles
US7399276B1 (en) 2003-05-08 2008-07-15 Health Hero Network, Inc. Remote health monitoring system
US20080262557A1 (en) 2007-04-19 2008-10-23 Brown Stephen J Obesity management system
US20090007924A1 (en) 2007-04-30 2009-01-08 Iliff Edwin C Arbiter system and method of computerized medical diagnosis and advice
US20090037220A1 (en) 2004-07-28 2009-02-05 National University Of Ireland Galway Portable medical monitoring and diagnostic system
US20090240156A1 (en) 2002-09-20 2009-09-24 Angel Medical Systems, Inc. Hiearchical communication system for a chronically implanted medical device
US20100022902A1 (en) 2008-07-25 2010-01-28 Brian Bruce Lee Virtual Physician Acute Myocardial Infarction Detection System and Method

Family Cites Families (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US599424A (en) * 1898-02-22 Charles mactaggart
US555169A (en) * 1896-02-25 To john klein
US464122A (en) * 1891-12-01 Crate
CH581904A5 (en) * 1974-08-29 1976-11-15 Centre Electron Horloger
US4237344A (en) * 1979-04-20 1980-12-02 Hospital Communication Systems, Inc. Rapid response health care communications system
US4464122A (en) * 1982-12-02 1984-08-07 Berkeley Fuller Health potential summary and incentive system
US4748600A (en) * 1986-08-22 1988-05-31 Aprex Corporation Interactive drug dispenser
US4966147A (en) * 1989-04-24 1990-10-30 Eitan Yaniv Method for the diagnosis of allergic rhinitis
US5084828A (en) * 1989-09-29 1992-01-28 Healthtech Services Corp. Interactive medication delivery system
JP2575218B2 (en) * 1989-12-05 1997-01-22 良太郎 初井 High-speed labor-saving medical examination device
US5263158A (en) * 1990-02-15 1993-11-16 International Business Machines Corporation Method and system for variable authority level user access control in a distributed data processing system having multiple resource manager
US7941326B2 (en) 2001-03-14 2011-05-10 Health Hero Network, Inc. Interactive patient communication development system for reporting on patient healthcare management
US20070299321A1 (en) 1992-11-17 2007-12-27 Brown Stephen J Method and apparatus for remote health monitoring and providing health related information
US5507277A (en) * 1993-01-29 1996-04-16 Aradigm Corporation Lockout device for controlled release of drug from patient-activateddispenser
CA2115878A1 (en) 1993-08-27 1995-02-28 Paul D. Cumming Automated system and method for eliciting confidential information from a patient
US5833599A (en) * 1993-12-13 1998-11-10 Multum Information Services Providing patient-specific drug information
US5405292A (en) * 1993-12-20 1995-04-11 Deere & Company Harvester shield
CA2125300C (en) * 1994-05-11 1999-10-12 Douglas J. Ballantyne Method and apparatus for the electronic distribution of medical information and patient services
JPH08117210A (en) 1994-09-30 1996-05-14 Asahi Denshi Kk Method and apparatus for evaluating intelligent and mental functions
JPH08164127A (en) 1994-12-13 1996-06-25 Agency Of Ind Science & Technol Fatigue feeling-measuring instrument
US5623656A (en) 1994-12-15 1997-04-22 Lucent Technologies Inc. Script-based data communication system and method utilizing state memory
US5666492A (en) * 1995-01-17 1997-09-09 Glaxo Wellcome Inc. Flexible computer based pharmaceutical care cognitive services management system and method
US5842175A (en) * 1995-04-28 1998-11-24 Therassist Software, Inc. Therapy system
US5626627A (en) * 1995-07-27 1997-05-06 Duke University Electroconvulsive therapy method using ICTAL EEG data as an indicator of ECT seizure adequacy
US5657236A (en) * 1995-08-14 1997-08-12 Profile Systems, Llc Medication dispensing and timing system utilizing patient communicator with internal clock
US5850344A (en) * 1995-08-14 1998-12-15 Profile Systems, Llc Medication dispensing and timing system
US5628530A (en) * 1995-12-12 1997-05-13 Info Tec Llc Method and system for collectively tracking demographics of starter drug samples
US5842871A (en) * 1995-12-20 1998-12-01 Educational Insights, Inc. Electronic testing system for use by multiple students
US5676138A (en) * 1996-03-15 1997-10-14 Zawilinski; Kenneth Michael Emotional response analyzer system with multimedia display
US7590549B2 (en) 1996-12-23 2009-09-15 Health Hero Network, Inc. Network media access control system for encouraging patient compliance with a treatment plan
US6076166A (en) * 1997-01-17 2000-06-13 Philips Electronics North America Corporation Personalizing hospital intranet web sites
US5902234A (en) * 1997-04-10 1999-05-11 Webb; Nicholas J. Medical communication system for ambulatory home-care patients
US6108665A (en) * 1997-07-03 2000-08-22 The Psychological Corporation System and method for optimizing behaviorial health care collection
US6067523A (en) * 1997-07-03 2000-05-23 The Psychological Corporation System and method for reporting behavioral health care data
US5984685A (en) * 1998-08-06 1999-11-16 The Children's Mercy Hospital Medical action system
US8521546B2 (en) 1998-09-25 2013-08-27 Health Hero Network Dynamic modeling and scoring risk assessment
US7555470B2 (en) 1999-03-22 2009-06-30 Health Hero Network, Inc. Research data collection and analysis
US6440066B1 (en) * 1999-11-16 2002-08-27 Cardiac Intelligence Corporation Automated collection and analysis patient care system and method for ordering and prioritizing multiple health disorders to identify an index disorder
US6757558B2 (en) * 2000-07-06 2004-06-29 Algodyne, Ltd. Objective pain measurement system and method
US20070015447A1 (en) * 2001-01-16 2007-01-18 Waddell John L Vibration stabilizing guide wheel
US8127140B2 (en) * 2005-01-21 2012-02-28 Nec Corporation Group signature scheme
US8758238B2 (en) 2006-08-31 2014-06-24 Health Hero Network, Inc. Health related location awareness

Patent Citations (336)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3970996A (en) 1973-02-28 1976-07-20 Perfect Liberty Apparatus for collecting medical data
US4051522A (en) 1975-05-05 1977-09-27 Jonathan Systems Patient monitoring system
US4290114A (en) 1976-07-01 1981-09-15 Sinay Hanon S Medical diagnostic computer
US4220160A (en) 1978-07-05 1980-09-02 Clinical Systems Associates, Inc. Method and apparatus for discrimination and detection of heart sounds
US4315309A (en) 1979-06-25 1982-02-09 Coli Robert D Integrated medical test data storage and retrieval system
US4337377A (en) 1980-01-10 1982-06-29 Riper Wilbur E Van Biologic apparatus
US4428381A (en) 1981-03-13 1984-01-31 Medtronic, Inc. Monitoring device
US4458693A (en) 1981-03-13 1984-07-10 Medtronic, Inc. Monitoring system
US4465077A (en) 1981-11-12 1984-08-14 Howard Schneider Apparatus and method of determining fertility status
US4531527A (en) 1982-04-23 1985-07-30 Survival Technology, Inc. Ambulatory monitoring system with real time analysis and telephone transmission
US4606352A (en) 1984-07-13 1986-08-19 Purdue Research Foundation Personal electrocardiogram monitor
US4733354A (en) 1984-11-23 1988-03-22 Brian Potter Method and apparatus for automated medical diagnosis using decision tree analysis
US4712562A (en) 1985-01-08 1987-12-15 Jacques J. Ohayon Outpatient monitoring systems
US5012411A (en) 1985-07-23 1991-04-30 Charles J. Policastro Apparatus for monitoring, storing and transmitting detected physiological information
US4838275A (en) 1985-11-29 1989-06-13 Lee Arnold St J Home medical surveillance system
US5054493A (en) 1986-01-31 1991-10-08 Regents Of The University Of Minnesota Method for diagnosing, monitoring and treating hypertension
US4868763A (en) 1986-02-21 1989-09-19 Hitachi, Ltd. Knowledge-based system having plural processors
US4731726A (en) 1986-05-19 1988-03-15 Healthware Corporation Patient-operated glucose monitor and diabetes management system
US4803625A (en) 1986-06-30 1989-02-07 Buddy Systems, Inc. Personal health monitor
US5196682A (en) 1986-06-30 1993-03-23 Wang Laboratories, Inc. Infrared optical card having an opaque case for hiding internal components
US4770189A (en) 1986-09-02 1988-09-13 Industrial Technology Research Institute Real time multitask electronic stethoscopy system
US4858121A (en) 1986-12-12 1989-08-15 Medical Payment Systems, Incorporated Medical payment system
US5019974A (en) * 1987-05-01 1991-05-28 Diva Medical Systems Bv Diabetes management system and apparatus
US4839822A (en) 1987-08-13 1989-06-13 501 Synthes (U.S.A.) Computer system and method for suggesting treatments for physical trauma
US4974607A (en) 1987-08-20 1990-12-04 Satoru Miwa System for centralized management of medical data
US4825869A (en) 1987-09-28 1989-05-02 Telectronics N.V. System for automatically performing a clinical assessment of an implanted pacer based on information that is telemetrically received
US5023785A (en) 1987-11-16 1991-06-11 Becton & Dickinson Co. Hematology - diagnosis apparatus employing expert system technology
US5572421A (en) 1987-12-09 1996-11-05 Altman; Louis Portable medical questionnaire presentation device
EP0320749A2 (en) 1987-12-09 1989-06-21 ARCH DEVELOPMENT CORPORATION, The University of Chicago Portable medical history-taking device
US4945476A (en) 1988-02-26 1990-07-31 Elsevier Science Publishing Company, Inc. Interactive system and method for creating and editing a knowledge base for use as a computerized aid to the cognitive process of diagnosis
US4933873A (en) 1988-05-12 1990-06-12 Healthtech Services Corp. Interactive patient assistance device
US5442728A (en) 1988-05-12 1995-08-15 Healthtech Services Corp. Interactive patient assistance device for storing and dispensing a testing device
US4975840A (en) 1988-06-17 1990-12-04 Lincoln National Risk Management, Inc. Method and apparatus for evaluating a potentially insurable risk
US5347632A (en) 1988-07-15 1994-09-13 Prodigy Services Company Reception system for an interactive computer network and method of operation
US5030948A (en) 1988-09-19 1991-07-09 Rush Charles T Multiple characteristic sensitive addressing schema for a multiple receiver data processing network
US4962491A (en) 1988-10-13 1990-10-09 Schaeffer Theodore S Medicament dispenser and medical information storage apparatus
US5084819A (en) 1988-11-10 1992-01-28 Response Technologies Inc. Data collection, analysis, and response system and method
US5012815A (en) 1989-02-02 1991-05-07 Yale University Dynamic spectral phonocardiograph
US5018526A (en) * 1989-02-28 1991-05-28 Gaston Johansson Fannie Apparatus and method for providing a multidimensional indication of pain
US5099424A (en) 1989-07-20 1992-03-24 Barry Schneiderman Model user application system for clinical data processing that tracks and monitors a simulated out-patient medical practice using data base management software
US5126957A (en) 1989-09-29 1992-06-30 Health Tech Services Corp. Interactive medication delivery system
US5533522A (en) 1989-10-30 1996-07-09 Feng; Genquan Method of and arrangement for optimizing disease diagnosis
US5642731A (en) 1990-01-17 1997-07-01 Informedix, Inc. Method of and apparatus for monitoring the management of disease
EP0447710A1 (en) 1990-03-19 1991-09-25 Takeshi Makitsubo Electrocardiographic data transmission system
US5255187A (en) 1990-04-03 1993-10-19 Sorensen Mark C Computer aided medical diagnostic method and apparatus
US5862304A (en) 1990-05-21 1999-01-19 Board Of Regents, The University Of Texas System Method for predicting the future occurrence of clinically occult or non-existent medical conditions
US5113869A (en) 1990-08-21 1992-05-19 Telectronics Pacing Systems, Inc. Implantable ambulatory electrocardiogram monitor
US5622171A (en) 1990-08-28 1997-04-22 Arch Development Corporation Method and system for differential diagnosis based on clinical and radiological information using artificial neural networks
US5463548A (en) 1990-08-28 1995-10-31 Arch Development Corporation Method and system for differential diagnosis based on clinical and radiological information using artificial neural networks
US5263123A (en) 1990-09-10 1993-11-16 Hitachi Engineering Co., Ltd. Fuzzy backward reasoning system and expert system utilizing the same
US5235510A (en) 1990-11-22 1993-08-10 Kabushiki Kaisha Toshiba Computer-aided diagnosis system for medical use
US5228449A (en) 1991-01-22 1993-07-20 Athanasios G. Christ System and method for detecting out-of-hospital cardiac emergencies and summoning emergency assistance
US5481647A (en) 1991-03-22 1996-01-02 Raff Enterprises, Inc. User adaptable expert system
US5241621A (en) 1991-06-26 1993-08-31 Digital Equipment Corporation Management issue recognition and resolution knowledge processor
US5404292A (en) 1991-09-11 1995-04-04 Hewlett-Packard Company Data processing system and method for automatically performing prioritized nursing diagnoses from patient assessment data
EP0531889A2 (en) 1991-09-11 1993-03-17 Hewlett-Packard Company Data processing system and method for automatically performing prioritized nursing diagnoses from patient assessment data
US5257627A (en) 1991-11-14 1993-11-02 Telmed, Inc. Portable non-invasive testing apparatus
US5519433A (en) 1991-11-20 1996-05-21 Zing Systems, L.P. Interactive television security through transaction time stamping
JP3202047B2 (en) 1991-11-25 2001-08-27 株式会社オキシーテック Large depth transducer sensitivity measurement system
US5415167A (en) 1992-01-10 1995-05-16 Wilk; Peter J. Medical system and associated method for automatic diagnosis and treatment
US5437278A (en) 1992-01-10 1995-08-01 Wilk; Peter J. Medical diagnosis system and method
US5732397A (en) 1992-03-16 1998-03-24 Lincoln National Risk Management, Inc. Automated decision-making arrangement
US5441047A (en) 1992-03-25 1995-08-15 David; Daniel Ambulatory patient health monitoring techniques utilizing interactive visual communication
US5544649A (en) 1992-03-25 1996-08-13 Cardiomedix, Inc. Ambulatory patient health monitoring techniques utilizing interactive visual communication
US5421343A (en) 1992-04-03 1995-06-06 Feng; Genquan Computer network EEMPI system
US5265613A (en) 1992-04-03 1993-11-30 Telmed, Inc. Portable non-invasive testing apparatus with logarithmic amplification
US5555169A (en) 1992-05-20 1996-09-10 Hitachi, Ltd. Computer system and method for converting a conversational statement to computer command language
US5337752A (en) 1992-05-21 1994-08-16 Mcg International, Inc. System for simultaneously producing and synchronizing spectral patterns of heart sounds and an ECG signal
US5418888A (en) 1992-06-04 1995-05-23 Alden; John L. System for revelance criteria management of actions and values in a rete network
US5299121A (en) 1992-06-04 1994-03-29 Medscreen, Inc. Non-prescription drug medication screening system
US5390238A (en) 1992-06-15 1995-02-14 Motorola, Inc. Health support system
US5583758A (en) 1992-06-22 1996-12-10 Health Risk Management, Inc. Health care management system for managing medical treatments and comparing user-proposed and recommended resources required for treatment
US5953704A (en) 1992-06-22 1999-09-14 Health Risk Management, Inc. Health care management system for comparing user-proposed and recommended resources required for treatment
US5435324A (en) 1992-08-21 1995-07-25 Compass Information Services, Inc. Apparatus for measuring psychotherapy outcomes
US5672154A (en) 1992-08-27 1997-09-30 Minidoc I Uppsala Ab Method and apparatus for controlled individualized medication
US5835900A (en) 1992-10-05 1998-11-10 Expert Systems Publishing Co. Computer-implemented decision management system with dynamically generated questions and answer choices
US20060189853A1 (en) 1992-11-17 2006-08-24 Health Hero Network, Inc. Method and system for improving adherence with a diet program or other medical regimen
US20040199409A1 (en) 1992-11-17 2004-10-07 Brown Stephen J. Remote health monitoring and maintenance system
US5960403A (en) 1992-11-17 1999-09-28 Health Hero Network Health management process control system
US5307263A (en) 1992-11-17 1994-04-26 Raya Systems, Inc. Modular microprocessor-based health monitoring system
US20060178914A1 (en) 1992-11-17 2006-08-10 Health Hero Network, Inc. Remote health monitoring and maintenance system
US20060241975A1 (en) 1992-11-17 2006-10-26 Health Hero Network, Inc. Multi-user remote health monitoring system with biometrics support
US20060247951A1 (en) 1992-11-17 2006-11-02 Health Hero Network, Inc. Universal serial bus (USB) based remote health monitoring
US6168563B1 (en) 1992-11-17 2001-01-02 Health Hero Network, Inc. Remote health monitoring and maintenance system
US5899855A (en) 1992-11-17 1999-05-04 Health Hero Network, Inc. Modular microprocessor-based health monitoring system
US20030069753A1 (en) 1992-11-17 2003-04-10 Brown Stephen J. Multi-user remote health monitoring system with biometrics support
US20040019259A1 (en) 1992-11-17 2004-01-29 Brown Stephen J. Remote monitoring and data management platform
US20040107116A1 (en) 1992-11-17 2004-06-03 Health Hero Network, Inc. Networked health information system for monitoring food intake
US20060287889A1 (en) 1992-11-17 2006-12-21 Health Hero Network, Inc. Multi-user remote health monitoring system with biometrics support
US20060100910A1 (en) 1992-11-17 2006-05-11 Health Hero Network, Inc. Interactive video based remote health monitoring system
US20040117210A1 (en) 1992-11-17 2004-06-17 Health Hero Network Networked remote patient monitoring with handheld devices
US20060010014A1 (en) 1992-11-17 2006-01-12 Health Hero Network, Inc. Remote health monitoring and maintenance system
US20040117209A1 (en) 1992-11-17 2004-06-17 Health Hero Network Patient control of health-related data in a remote patient monitoring system
US20040117208A1 (en) 1992-11-17 2004-06-17 Health Hero Network Messaging to remote patients in a networked health-monitoring system
US20060004611A1 (en) 1992-11-17 2006-01-05 Health Hero Network, Inc. Remote health monitoring and maintenance system
US20060285736A1 (en) 1992-11-17 2006-12-21 Health Hero Network, Inc. Multi-user remote health monitoring system with biometrics support
US20040116780A1 (en) 1992-11-17 2004-06-17 Brown Stephen J. Method and system for improving adherence with a diet program or other medical regimen
US20040117207A1 (en) 1992-11-17 2004-06-17 Health Hero Network, Inc. Report generation in a networked health-monitoring system
US7297109B2 (en) 1992-11-17 2007-11-20 Health Hero Network, Inc. Method and system for improving adherence with a diet program or other medical regimen
US20050256739A1 (en) 1992-11-17 2005-11-17 Brown Stephen J Radio frequency based remote health monitoring
US7264591B2 (en) 1992-11-17 2007-09-04 Health Hero Netowrk, Inc. System and method for monitoring air flow from a person
US20050086083A1 (en) 1992-11-17 2005-04-21 Brown Stephen J. User monitoring
US7223235B2 (en) 1992-11-17 2007-05-29 Health Hero Network, Inc. System and method for monitoring blood pressure from a person
US7223236B2 (en) 1992-11-17 2007-05-29 Health Hero Network, Inc. System and method for monitoring user-related data from a person
US5590648A (en) * 1992-11-30 1997-01-07 Tremont Medical Personal health care system
EP0720663B1 (en) 1993-01-20 1997-06-11 Delot Process S.A. Method for dimensioning an electroplating enclosure with a magnetic wiping device for electroplated metallurgical products
US5541977A (en) 1993-03-11 1996-07-30 At&T Corp. Method and apparatus for preventing wireless fraud
US5357427A (en) 1993-03-15 1994-10-18 Digital Equipment Corporation Remote monitoring of high-risk patients using artificial intelligence
US5482035A (en) 1993-03-19 1996-01-09 Instrumentarium Corporation Method for monitoring the condition of a patient
US5584291A (en) 1993-03-26 1996-12-17 Instrumentarium, Oy Method for recognizing and identifying emergency situations in an anesthesia system by means of a self-organizing map
US5473537A (en) 1993-07-30 1995-12-05 Psychresources Development Company Method for evaluating and reviewing a patient's condition
US5722418A (en) 1993-08-30 1998-03-03 Bro; L. William Method for mediating social and behavioral processes in medicine and business through an interactive telecommunications guidance system
US5377258A (en) 1993-08-30 1994-12-27 National Medical Research Council Method and apparatus for an automated and interactive behavioral guidance system
US5596994A (en) 1993-08-30 1997-01-28 Bro; William L. Automated and interactive behavioral and medical guidance system
US5692220A (en) 1993-09-02 1997-11-25 Coulter Corporation Decision support system and method for diagnosis consultation in laboratory hematopathology
DE4430184C2 (en) 1993-09-03 1997-01-30 Fette Wilhelm Gmbh Axial thread rolling head
US5675760A (en) 1993-09-10 1997-10-07 Toa Medical Electronics Co., Ltd. Apparatus and method for displaying normalized clinical test data
EP0643360A2 (en) 1993-09-10 1995-03-15 Toa Medical Electronics Co., Ltd. Clinical test result display apparatus
US5464012A (en) 1993-09-13 1995-11-07 Hewlett-Packard Company Patient alarm detection using target mode
US5692501A (en) 1993-09-20 1997-12-02 Minturn; Paul Scientific wellness personal/clinical/laboratory assessments, profile and health risk managment system with insurability rankings on cross-correlated 10-point optical health/fitness/wellness scales
US5389078A (en) * 1993-10-06 1995-02-14 Sims Deltec, Inc. Programmable infusion pump for administering medication to patients
US5517405A (en) 1993-10-14 1996-05-14 Aetna Life And Casualty Company Expert system for providing interactive assistance in solving problems such as health care management
US5724025A (en) 1993-10-21 1998-03-03 Tavori; Itzchak Portable vital signs monitor
US7300402B2 (en) 1993-12-29 2007-11-27 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US20080052119A1 (en) 1993-12-29 2008-02-28 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US6725209B1 (en) 1993-12-29 2004-04-20 First Opinion Corporation Computerized medical diagnostic and treatment advice system and method including mental status examination
US6071236A (en) 1993-12-29 2000-06-06 First Opinion Corporation Method of determining mental health status in a computerized medical diagnostic system
US6641532B2 (en) 1993-12-29 2003-11-04 First Opinion Corporation Computerized medical diagnostic system utilizing list-based processing
US7306560B2 (en) 1993-12-29 2007-12-11 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system including network access
US20030163299A1 (en) 1993-12-29 2003-08-28 Iliff Edwin C. Computerized medical diagnostic and treatment advice system
US5660176A (en) 1993-12-29 1997-08-26 First Opinion Corporation Computerized medical diagnostic and treatment advice system
US5868669A (en) 1993-12-29 1999-02-09 First Opinion Corporation Computerized medical diagnostic and treatment advice system
US20080051640A1 (en) 1993-12-29 2008-02-28 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US20080052318A1 (en) 1993-12-29 2008-02-28 Clinical Decision Support, Llc Computerized medical diagnostic system utilizing list-based processing
US5594638A (en) 1993-12-29 1997-01-14 First Opinion Corporation Computerized medical diagnostic system including re-enter function and sensitivity factors
US5711297A (en) 1993-12-29 1998-01-27 First Opinion Corporation Computerized medical advice system and method including meta function
US6748353B1 (en) 1993-12-29 2004-06-08 First Opinion Corporation Authoring language translator
US20080051638A1 (en) 1993-12-29 2008-02-28 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system including network access
US20080059247A1 (en) 1993-12-29 2008-03-06 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US5910107A (en) 1993-12-29 1999-06-08 First Opinion Corporation Computerized medical diagnostic and treatment advice method
US20010053875A1 (en) 1993-12-29 2001-12-20 Iliff Edwin C. Computerized medical diagnostic system utilizing list-based processing
US7297111B2 (en) 1993-12-29 2007-11-20 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US6270456B1 (en) 1993-12-29 2001-08-07 First Opinion Corporation Computerized medical diagnostic system utilizing list-based processing
US20080162393A1 (en) 1993-12-29 2008-07-03 Clinical Decision Support, Llc Computerized medical diagnostic and treatment advice system
US20040249778A1 (en) 1993-12-29 2004-12-09 Iliff Edwin C. Computerized medical diagnostic and treatment advice system and method including mental status examination
US5724968A (en) 1993-12-29 1998-03-10 First Opinion Corporation Computerized medical diagnostic system including meta function
US6022315A (en) 1993-12-29 2000-02-08 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
US6113540A (en) 1993-12-29 2000-09-05 First Opinion Corporation Computerized medical diagnostic and treatment advice system
US5471382A (en) 1994-01-10 1995-11-28 Informed Access Systems, Inc. Medical network management system and process
US5809476A (en) 1994-03-23 1998-09-15 Ryan; John Kevin System for converting medical information into representative abbreviated codes with correction capability
US5486999A (en) 1994-04-20 1996-01-23 Mebane; Andrew H. Apparatus and method for categorizing health care utilization
US5940801A (en) 1994-04-26 1999-08-17 Health Hero Network, Inc. Modular microprocessor-based diagnostic measurement apparatus and method for psychological conditions
US5828943A (en) 1994-04-26 1998-10-27 Health Hero Network, Inc. Modular microprocessor-based diagnostic measurement apparatus and method for psychological conditions
US6334778B1 (en) 1994-04-26 2002-01-01 Health Hero Network, Inc. Remote psychological diagnosis and monitoring system
US6260022B1 (en) 1994-04-26 2001-07-10 Health Hero Network, Inc. Modular microprocessor-based diagnostic measurement apparatus and method for psychological conditions
US20080109172A1 (en) 1994-05-23 2008-05-08 Brown Stephen J Diabetes management system
US6330426B2 (en) 1994-05-23 2001-12-11 Stephen J. Brown System and method for remote education using a memory card
US20060234202A1 (en) 1994-05-23 2006-10-19 Health Hero Network, Inc. System and method for monitoring a physiological condition
US5732709A (en) 1994-05-23 1998-03-31 Enact Health Management Systems System for monitoring and reporting medical measurements
US5704366A (en) 1994-05-23 1998-01-06 Enact Health Management Systems System for monitoring and reporting medical measurements
US6186145B1 (en) 1994-05-23 2001-02-13 Health Hero Network, Inc. Method for diagnosis and treatment of psychological and emotional conditions using a microprocessor-based virtual reality simulator
US5918603A (en) 1994-05-23 1999-07-06 Health Hero Network, Inc. Method for treating medical conditions using a microprocessor-based video game
US20040219500A1 (en) 1994-05-23 2004-11-04 Brown Stephen J System and method for remote education using a memory card
US5501229A (en) 1994-08-01 1996-03-26 New England Medical Center Hospital Continuous monitoring using a predictive instrument
US5724983A (en) 1994-08-01 1998-03-10 New England Center Hospitals, Inc. Continuous monitoring using a predictive instrument
DE4430164A1 (en) 1994-08-25 1996-02-29 Uthe Friedrich Wilhelm Interactive computer based system for medical diagnostics
US5633910A (en) 1994-09-13 1997-05-27 Cohen; Kopel H. Outpatient monitoring system
US6248063B1 (en) 1994-10-13 2001-06-19 Horus Therapeutics, Inc. Computer assisted methods for diagnosing diseases
US5769074A (en) 1994-10-13 1998-06-23 Horus Therapeutics, Inc. Computer assisted methods for diagnosing diseases
US5601435A (en) 1994-11-04 1997-02-11 Intercare Method and apparatus for interactively monitoring a physiological condition and for interactively providing health related information
US6144837A (en) 1994-11-04 2000-11-07 Health Hero Network, Inc. Method and apparatus for interactively monitoring a physiological condition and for interactively providing health-related information
US5659793A (en) 1994-12-22 1997-08-19 Bell Atlantic Video Services, Inc. Authoring tools for multimedia application development and network delivery
US5553609A (en) 1995-02-09 1996-09-10 Visiting Nurse Service, Inc. Intelligent remote visual monitoring system for home health care service
US5778882A (en) * 1995-02-24 1998-07-14 Brigham And Women's Hospital Health monitoring system
US5911132A (en) 1995-04-26 1999-06-08 Lucent Technologies Inc. Method using central epidemiological database
US5619991A (en) 1995-04-26 1997-04-15 Lucent Technologies Inc. Delivery of medical services using electronic data communications
JP4056561B2 (en) 1995-06-01 2008-03-05 ビドリエラ・モンテレイ,エセ・ア・デ・セ・ウベ Method and apparatus for decorating bottles or similar articles
US20050080652A1 (en) 1995-06-07 2005-04-14 Brown Stephen J. User-based health monitoring
US7258666B2 (en) 1995-06-07 2007-08-21 Health Hero Network, Inc. System and methods for monitoring a patient's heart condition
US5703786A (en) 1995-08-14 1997-12-30 Profile Systems, Llc Medication dispensing and timing system utilizing time reference message
US6177940B1 (en) 1995-09-20 2001-01-23 Cedaron Medical, Inc. Outcomes profile management system for evaluating treatment effectiveness
US5694939A (en) 1995-10-03 1997-12-09 The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration Autogenic-feedback training exercise (AFTE) method and system
US5788640A (en) 1995-10-26 1998-08-04 Peters; Robert Mitchell System and method for performing fuzzy cluster classification of stress tests
US5800347A (en) 1995-11-03 1998-09-01 The General Hospital Corporation ROC method for early detection of disease
US5678562A (en) 1995-11-09 1997-10-21 Burdick, Inc. Ambulatory physiological monitor with removable disk cartridge and wireless modem
US6598035B2 (en) 1995-11-17 2003-07-22 International Business Machines Corporation Object oriented rule-based expert system framework mechanism
US5746204A (en) 1995-12-07 1998-05-05 Carbon Based Corporation Disease indicator analysis system
US5642936A (en) 1996-01-29 1997-07-01 Oncormed Methods for identifying human hereditary disease patterns
US7305348B1 (en) 1996-02-20 2007-12-04 Health Hero Network, Inc. Aggregating and pooling health related information in a communication system with feedback
US5974389A (en) 1996-03-01 1999-10-26 Clark; Melanie Ann Medical record management system and process with improved workflow features
US5794208A (en) 1996-03-01 1998-08-11 Goltra; Peter S. Creating and using protocols to create and review a patient chart
US5823949A (en) 1996-03-01 1998-10-20 Goltra; Peter S. Intelligent prompting
US5802495A (en) 1996-03-01 1998-09-01 Goltra; Peter Phrasing structure for the narrative display of findings
US6106459A (en) 1996-03-29 2000-08-22 Clawson; Jeffrey J. Method and system for the entry protocol of an emergency medical dispatch system
US5839430A (en) 1996-04-26 1998-11-24 Cama; Joseph Combination inhaler and peak flow rate meter
US5970463A (en) 1996-05-01 1999-10-19 Practice Patterns Science, Inc. Medical claims integration and data analysis system
US5812984A (en) 1996-05-13 1998-09-22 Goltra; Peter S. Method for entering information into an electronic patient chart, and protocol auto-negative capabilities
US6001060A (en) 1996-06-04 1999-12-14 Regents Of The University Of California Video data representation of physiological data
US5976082A (en) 1996-06-17 1999-11-02 Smithkline Beecham Corporation Method for identifying at risk patients diagnosed with congestive heart failure
US5879163A (en) 1996-06-24 1999-03-09 Health Hero Network, Inc. On-line health education and feedback system using motivational driver profile coding and automated content fulfillment
US6849045B2 (en) 1996-07-12 2005-02-01 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
US6206829B1 (en) 1996-07-12 2001-03-27 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
US5935060A (en) 1996-07-12 1999-08-10 First Opinion Corporation Computerized medical diagnostic and treatment advice system including list based processing
US7344496B2 (en) 1996-07-12 2008-03-18 Clinical Decision Support, Llc Computerized medical diagnostic system utilizing list-based processing
US20040059200A1 (en) 1996-07-12 2004-03-25 Iliff Edwin C. Computerized medical diagnostic system utilizing list-based processing
US6482156B2 (en) 1996-07-12 2002-11-19 First Opinion Corporation Computerized medical diagnostic and treatment advice system including network access
US5733313A (en) * 1996-08-01 1998-03-31 Exonix Corporation RF coupled, implantable medical device with rechargeable back-up power source
US5772585A (en) 1996-08-30 1998-06-30 Emc, Inc System and method for managing patient medical records
US5987519A (en) 1996-09-20 1999-11-16 Georgia Tech Research Corporation Telemedicine system using voice video and data encapsulation and de-encapsulation for communicating medical information between central monitoring stations and remote patient monitoring stations
US6189029B1 (en) 1996-09-20 2001-02-13 Silicon Graphics, Inc. Web survey tool builder and result compiler
US20060253303A1 (en) 1996-10-16 2006-11-09 Brown Stephen J Multiple patient monitoring system for proactive health management
US5832448A (en) 1996-10-16 1998-11-03 Health Hero Network Multiple patient monitoring system for proactive health management
US6246992B1 (en) 1996-10-16 2001-06-12 Health Hero Network, Inc. Multiple patient monitoring system for proactive health management
US6246975B1 (en) 1996-10-30 2001-06-12 American Board Of Family Practice, Inc. Computer architecture and process of patient generation, evolution, and simulation for computer based testing system
US5909679A (en) 1996-11-08 1999-06-01 At&T Corp Knowledge-based moderator for electronic mail help lists
US5720502A (en) 1996-11-08 1998-02-24 Cain; John R. Pain location and intensity communication apparatus and method
US6247002B1 (en) 1996-12-11 2001-06-12 Sony Corporation Method and apparatus for extracting features characterizing objects, and use thereof
US6151586A (en) 1996-12-23 2000-11-21 Health Hero Network, Inc. Computerized reward system for encouraging participation in a health management program
US5933136A (en) 1996-12-23 1999-08-03 Health Hero Network, Inc. Network media access control system for encouraging patient compliance with a treatment plan
US6601055B1 (en) 1996-12-27 2003-07-29 Linda M. Roberts Explanation generation system for a diagnosis support tool employing an inference system
US6167362A (en) 1997-01-10 2000-12-26 Health Hero Network, Inc. Motivational tool for adherence to medical regimen
US7167818B2 (en) 1997-01-10 2007-01-23 Health Hero Network, Inc. Disease simulation system and method
US5822715A (en) 1997-01-10 1998-10-13 Health Hero Network Diabetes management system and method for controlling blood glucose
US7392167B2 (en) 1997-01-10 2008-06-24 Health Hero Network, Inc. Disease simulation system and method
US6233539B1 (en) 1997-01-10 2001-05-15 Health Hero Network, Inc. Disease simulation system and method
US20080108888A1 (en) 1997-01-10 2008-05-08 Brown Stephen J Diabetes care management system
US6379301B1 (en) 1997-01-10 2002-04-30 Health Hero Network, Inc. Diabetes management system and method for controlling blood glucose
US5956501A (en) 1997-01-10 1999-09-21 Health Hero Network, Inc. Disease simulation system and method
US5887133A (en) 1997-01-15 1999-03-23 Health Hero Network System and method for modifying documents sent over a communications network
US6032119A (en) 1997-01-16 2000-02-29 Health Hero Network, Inc. Personalized display of health information
US20050027562A1 (en) 1997-01-16 2005-02-03 Brown Stephen J. Personalized display of health information
US5903211A (en) * 1997-02-07 1999-05-11 Althin Medical, Inc. Medical treatment device with a user interface adapted for home or limited care environments
US6059724A (en) 1997-02-14 2000-05-09 Biosignal, Inc. System for predicting future health
US20060089969A1 (en) 1997-03-10 2006-04-27 Health Hero Network, Inc. System and method for modifying documents sent over a communications network
US5951300A (en) 1997-03-10 1999-09-14 Health Hero Network Online system and method for providing composite entertainment and health information
US6375469B1 (en) 1997-03-10 2002-04-23 Health Hero Network, Inc. Online system and method for providing composite entertainment and health information
US20030036686A1 (en) 1997-03-13 2003-02-20 Iliff Edwin C. Disease management system and method including analysis of disease specific changes
US7297108B2 (en) 1997-03-13 2007-11-20 Clinical Decision Support, Llc Disease management system and method including analysis of disease specific changes
US20080052116A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system and method
US20080059232A1 (en) 1997-03-13 2008-03-06 Clinical Decision Support, Llc Disease management system and method including question version
US20080052132A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system and method including therapeutic alterations permission level
US7769600B2 (en) 1997-03-13 2010-08-03 Clinical Decision Support Disease management system and method
US20080052123A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system and method including preview mode
US20010012913A1 (en) 1997-03-13 2001-08-09 Iliff Edwin C. Disease management system and method including correlation assessment
US6770029B2 (en) 1997-03-13 2004-08-03 First Opinion Corporation Disease management system and method including correlation assessment
US20080045811A1 (en) 1997-03-13 2008-02-21 Clinical Decision Support, Llc Disease management system and method including significant symptom filtering
US20080051641A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support , Llc Disease management system including a no response method
US20030153819A1 (en) 1997-03-13 2003-08-14 Iliff Edwin C. Disease management system and method including correlation assessment
US20080052121A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system operating on a network
US20080052130A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc. Disease management system and method including therapy optimization
US20080052118A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system and method including permission database
US20080052120A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system and health assessment method
US6234964B1 (en) 1997-03-13 2001-05-22 First Opinion Corporation Disease management system and method
US20080052122A1 (en) 1997-03-13 2008-02-28 Clinical Decision Support, Llc Disease management system and method
US6032678A (en) 1997-03-14 2000-03-07 Shraga Rottem Adjunct to diagnostic imaging systems for analysis of images of an object or a body part or organ
US7320030B2 (en) 1997-03-28 2008-01-15 Health Hero Network, Inc. Remote health monitoring apparatus using scripted communications
US5897493A (en) 1997-03-28 1999-04-27 Health Hero Network, Inc. Monitoring system for remotely querying individuals
US7252636B2 (en) 1997-03-28 2007-08-07 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US5997476A (en) 1997-03-28 1999-12-07 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US7516192B2 (en) 1997-03-28 2009-04-07 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060252089A1 (en) 1997-03-28 2006-11-09 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20050228883A1 (en) 1997-03-28 2005-10-13 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060294233A1 (en) 1997-03-28 2006-12-28 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US6270455B1 (en) 1997-03-28 2001-08-07 Health Hero Network, Inc. Networked system for interactive communications and remote monitoring of drug delivery
US6968375B1 (en) 1997-03-28 2005-11-22 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US6368273B1 (en) 1997-03-28 2002-04-09 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20050273509A1 (en) 1997-03-28 2005-12-08 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060253576A1 (en) 1997-03-28 2006-11-09 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US6381577B1 (en) 1997-03-28 2002-04-30 Health Hero Network, Inc. Multi-user remote health monitoring system
US7310668B2 (en) 1997-03-28 2007-12-18 Health Hero Network, Inc. Remotely monitoring an individual using scripted communications
US20060253574A1 (en) 1997-03-28 2006-11-09 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060287931A1 (en) 1997-03-28 2006-12-21 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060247979A1 (en) 1997-03-28 2006-11-02 Health Hiro Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060271404A1 (en) 1997-03-28 2006-11-30 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US20060235722A1 (en) 1997-03-28 2006-10-19 Health Hero Network, Inc. Networked system for interactive communication and remote monitoring of individuals
US6101478A (en) 1997-04-30 2000-08-08 Health Hero Network Multi-user remote health monitoring system
US6248065B1 (en) 1997-04-30 2001-06-19 Health Hero Network, Inc. Monitoring system for remotely querying individuals
US5908383A (en) 1997-09-17 1999-06-01 Brynjestad; Ulf Knowledge-based expert interactive system for pain
US6597392B1 (en) 1997-10-14 2003-07-22 Healthcare Vision, Inc. Apparatus and method for computerized multi-media data organization and transmission
US20040017475A1 (en) 1997-10-14 2004-01-29 Akers William Rex Apparatus and method for computerized multi-media data organization and transmission
US6230142B1 (en) 1997-12-24 2001-05-08 Homeopt, Llc Health care data manipulation and analysis system
US6117073A (en) 1998-03-02 2000-09-12 Jones; Scott J. Integrated emergency medical transportation database system
US6081786A (en) 1998-04-03 2000-06-27 Triangle Pharmaceuticals, Inc. Systems, methods and computer program products for guiding the selection of therapeutic treatment regimens
US6240393B1 (en) 1998-06-05 2001-05-29 Health Pro Network, Inc. Aggregating and pooling weight loss information in a communication system with feedback
US6149585A (en) 1998-10-28 2000-11-21 Sage Health Management Solutions, Inc. Diagnostic enhancement method and apparatus
WO2000032088A1 (en) 1998-11-30 2000-06-08 Novo Nordisk A/S A medical system and a method of controlling the system for use by a patient for medical self treatment
US6161095A (en) 1998-12-16 2000-12-12 Health Hero Network, Inc. Treatment regimen compliance and efficacy with feedback
US6196970B1 (en) 1999-03-22 2001-03-06 Stephen J. Brown Research data collection and analysis
US20040193377A1 (en) 1999-03-22 2004-09-30 Brown Stephen J. Research data collection and analysis
US7076437B1 (en) 1999-10-29 2006-07-11 Victor Levy Process for consumer-directed diagnostic and health care information
US6764447B2 (en) 2000-02-14 2004-07-20 First Opinion Corporation Automated diagnostic system and method including alternative symptoms
US6767325B2 (en) 2000-02-14 2004-07-27 First Opinion Corporation Automated diagnostic system and method including synergies
US6569093B2 (en) 2000-02-14 2003-05-27 First Opinion Corporation Automated diagnostic system and method including disease timeline
US20020068857A1 (en) 2000-02-14 2002-06-06 Iliff Edwin C. Automated diagnostic system and method including reuse of diagnostic objects
US6468210B2 (en) 2000-02-14 2002-10-22 First Opinion Corporation Automated diagnostic system and method including synergies
US6475143B2 (en) 2000-02-14 2002-11-05 First Opinion Corporation Automated diagnostic system and method including encoding patient data
US6817980B2 (en) 2000-02-14 2004-11-16 First Opinion Corporation Automated diagnostic system and method including disease timeline
US20040199332A1 (en) 2000-02-14 2004-10-07 Iliff Edwin C. Automated diagnostic system and method
WO2001061616A2 (en) 2000-02-14 2001-08-23 First Opinion Corporation Automated diagnostic system and method
US6524241B2 (en) 2000-02-14 2003-02-25 First Opinion Corporation Automated diagnostic system and method including multiple diagnostic modes
US6527713B2 (en) 2000-02-14 2003-03-04 First Opinion Corporation Automated diagnostic system and method including alternative symptoms
US6746399B2 (en) 2000-02-14 2004-06-08 First Opinion Corporation Automated diagnostic system and method including encoding patient data
US6730027B2 (en) 2000-02-14 2004-05-04 First Opinion Corporation Automated diagnostic system and method including multiple diagnostic modes
US6900807B1 (en) 2000-03-08 2005-05-31 Accenture Llp System for generating charts in a knowledge management tool
US6687685B1 (en) 2000-04-07 2004-02-03 Dr. Red Duke, Inc. Automated medical decision making utilizing bayesian network knowledge domain modeling
US20010039503A1 (en) 2000-04-28 2001-11-08 Chan Bryan K. Method and system for managing chronic disease and wellness online
US20030181790A1 (en) 2000-05-18 2003-09-25 Daniel David Methods and apparatus for facilitated, hierarchical medical diagnosis and symptom coding and definition
US20020029157A1 (en) 2000-07-20 2002-03-07 Marchosky J. Alexander Patient - controlled automated medical record, diagnosis, and treatment system and method
US20020186818A1 (en) 2000-08-29 2002-12-12 Osteonet, Inc. System and method for building and manipulating a centralized measurement value database
WO2002039250A2 (en) 2000-11-13 2002-05-16 Siemens Medical Solutions Usa, Inc. A system and method for navigating patient medical information
CN1291749A (en) 2000-11-16 2001-04-18 上海交通大学 Intelligent system for domestic remote medical monitor and consultation
WO2002042876A2 (en) 2000-11-22 2002-05-30 Recare, Inc. Systems and methods for integrating disease management into a physician workflow
US20020148477A1 (en) 2001-04-17 2002-10-17 Lg Electronics Inc. System and method of performing medical diagnosis in real time
US6903657B2 (en) 2001-04-17 2005-06-07 Lg Electronics Inc. System and method of performing medical diagnosis in real time
US7259681B2 (en) 2001-04-17 2007-08-21 Lg Electronics Inc. System and method of performing medical diagnosis in real time
US20050177391A1 (en) 2001-10-23 2005-08-11 Hideki Shimizu Health management system and health management program
WO2003040964A2 (en) 2001-11-02 2003-05-15 Siemens Medical Solutions Usa, Inc. Patient data mining for diagnosis and projections of patient states
WO2003040989A2 (en) 2001-11-02 2003-05-15 Siemens Medical Solutions Usa, Inc. Patient data mining, presentation, exploration, and verification
WO2003040879A2 (en) 2001-11-02 2003-05-15 Siemens Medical Solutions Usa, Inc. Patient data mining with population-based analysis
WO2003040990A2 (en) 2001-11-02 2003-05-15 Siemens Medical Solutions Usa, Inc. Patient data mining for quality adherence
WO2003040965A2 (en) 2001-11-02 2003-05-15 Siemens Corporate Research, Inc. Patient data mining
US20050234306A1 (en) 2002-06-20 2005-10-20 Martin Schulte Method and system for detecting and analyzing clinical pictures and the causes thereof and for determining proposals for appropriate therapy
US20090240156A1 (en) 2002-09-20 2009-09-24 Angel Medical Systems, Inc. Hiearchical communication system for a chronically implanted medical device
US20050060194A1 (en) 2003-04-04 2005-03-17 Brown Stephen J. Method and system for monitoring health of an individual
US20080269571A1 (en) 2003-05-08 2008-10-30 Brown Stephen J Remote health monitoring system
US7399276B1 (en) 2003-05-08 2008-07-15 Health Hero Network, Inc. Remote health monitoring system
US20050010088A1 (en) 2003-05-15 2005-01-13 Iliff Edwin C. Panel diagnostic method and system
US7780595B2 (en) 2003-05-15 2010-08-24 Clinical Decision Support, Llc Panel diagnostic method and system
US20050010444A1 (en) 2003-06-06 2005-01-13 Iliff Edwin C. System and method for assisting medical diagnosis using an anatomic system and cause matrix
CN1477581A (en) 2003-07-01 2004-02-25 南京大学 Predictive modelling method application to computer-aided medical diagnosis
US20050273359A1 (en) 2004-06-03 2005-12-08 Young David E System and method of evaluating preoperative medical care and determining recommended tests based on patient health history and medical condition and nature of surgical procedure
US20090037220A1 (en) 2004-07-28 2009-02-05 National University Of Ireland Galway Portable medical monitoring and diagnostic system
US20060135859A1 (en) 2004-10-22 2006-06-22 Iliff Edwin C Matrix interface for medical diagnostic and treatment advice system and method
US20080262557A1 (en) 2007-04-19 2008-10-23 Brown Stephen J Obesity management system
US20090007924A1 (en) 2007-04-30 2009-01-08 Iliff Edwin C Arbiter system and method of computerized medical diagnosis and advice
US20100022902A1 (en) 2008-07-25 2010-01-28 Brian Bruce Lee Virtual Physician Acute Myocardial Infarction Detection System and Method

Non-Patent Citations (255)

* Cited by examiner, † Cited by third party
Title
"Can Telecommunications Help Solve America's Heath Care Problems?" Summary, Arthur D. Little, Inc., Acorn Park, Cambridge MA Jul. 1992.
"Center Develops New System for Disease Management" Memorial Sloan-Kerrering Cancer Center, http://www.mskcc.org/document/cn950601.htm (1997).
"Harvard Community Health Plan Testing Computerized Service that ANswers Health-Care Questions," Technical Computing, 6(9), Aug. 1991.
"Netscape & Sun Announce Javascript the Open, Cross-Platform Object Scripting Language for Enterprise Networks and the Internet", Press Release, Dec. 4, 1995, web at http://java.sun.com/pr/1995/12/pr951204-03.html. (10 pages).
"Physician's Database Manager" and "Iliad", The Alpha Media Catalog, Advertisement, Oct. 1993.
"System helps doctors keep up to date", New York Times, p. 18, Jul. 13, 1991.
"Telecommunications: Can it Help Solve America's Health Care Problems?", pp. 1-16, Arthur D. Little, Inc., Acorn Park, Cambridge MA, Jul. 1992.
Alere LLC's Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9 (b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 20 pages.
Alere, LLC's Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 4, 2009, 10 pages.
Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 23 pages.
Alere, LLC's Objections and Answers to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Feb. 11, 2009, 30 pages.
Alere, LLC's Objections and Answers to Plaintiff's Second Set of Interrogatories (Nos. 9-10), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 2, 2009, 10 pages.
Alere's Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Dec. 9, 2008, 29 pages.
Alere's Answer to First Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 22, 2009, 32 pages.
Alere's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 6, 2009, 28 pages.
Alere's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 8, 2009, 30 pages.
Alexander G., Health Risk Appraisal, Intern Electro J Health Edu., 2000 3(Special): 122-137.
Applied Medical Informatics, Inc., "Medical House Call(TM) Interactive Home Medical Guide & Symptom Analysis", Applied Medical Informatics, 1995, pp. 24-Jan, Salt Lake City, UT.
Applied Medical Informatics, Inc., "Medical House Call™ Interactive Home Medical Guide & Symptom Analysis", Applied Medical Informatics, 1995, pp. 24-Jan, Salt Lake City, UT.
AU Office Action dated Jul. 1, 2005 in Australian Patent Application No. 2003235078, filed Aug. 19, 2003.
Australian Office Action dated Nov. 10, 2008 for Australian Patent Application No. 20077201421, filed Mar. 13, 1998.
Ball et al. Eds. Computers in Health Care: Aspects of the Computer-based Patient Record, Springer Verlag, 1992, pp. 1-336.
Barnett et al., A compute-based medical information system for ambulatory care, Proc. IEEE, 1979, Issue 67, pp. 1226-1237.
Barr et al., (Eds.) The Handbook of Artificial Intelligence, HeurisTech Press, 1982, vol. II, Chapter VII, pp. 175-222.
Becher, Ernst, "Fernmeldeweesen für soziale Dienste inEntwicklungsländern," NTZ, 33:304, 1980.
Belzer et al., "Encyclopedia of Computer Science and Technology", Marcel Dekker, Inc. NY (1978) pp. 78-79 annd 114-15.
Bergman, "Computers make 'house calls' to patients; Harvard Community Health Plan offers computerized information service to patients," J American Hospital Association, 67(10): 5, May 20, 1993.
Bischoff, A Knowledge Based System for Assisting in Differential Diagnosis of Chemically Dependent/Mentally III Patients, Computers in Human Services, 1992, vol. 8, Nos. 3/4, pp. 143-151.
Bortolan et al., The role of patient history in a decision support system, IEE, Computers in Cardiology, Sep. 1990, Proceedings, pp. 357-360.
Bouhaddou et al., "Iliad and Medical House Call: evaluating the impact of common sense knowledge on the diagnostic accuracy of a medical expert system", AMIA, Inc., pp. 742-746, 1995.
Bouhaddou et al., An interactive patient information and education system (Medical HouseCall) based on a physician expert system (Iliad), Medinfo, 1995, vol. Pt 2, Issue 8, pp. 1181-1185, Vancouver, Canada.
Bowden, K.F. et al., Information Processing, 71:1398-1406, 1972, "Data structures for general practice records."
Brown et al., Information Infrastructure Task Force, The National Information Infrastructure: Agenda for Action, Sep. 15, 1993, pp. 26.
CA Office Action dated Apr. 15, 2008 in Canadian Patent Application No. 2,284,168, filed Mar. 13, 1998.
CA Office Action dated Feb. 13, 2006, in Canadian Patent Application No. 2,284,168, filed Mar. 13, 1998.
Chinese Office Action dated Feb. 26, 2010 in Chinese Patent Application No. 200410057537.8, filed Mar. 13, 1998.
Chinese Office Action dated Jul. 10, 2009 in Chinese Patent Application No. 200410057537.8, filed Mar. 13, 1998.
Christine, The Future of Health Care Technologies, HighBeam Research, Risk Management, Nov. 1, 1992, 1-3.
Cimino, James J. et al., "DXplain: An interactive knowledge base for assistance in medical diagnostic decisions.", IEEE/Ninth Annual Conference of the Engineering in Medicine and Biology Society, 1987.
CN Office Action dated Jan. 4, 2008 in Chinese Patent Application No. 200410057537.8, filed Mar. 13, 1998.
CN Office Action dated May 18, 2007 in Chinese Patent Application No. 200410057537.8, filed Mar. 13, 1998.
Collen, Machine diagnosis from a multiphasic screening program, Proceedings of 5th IBM Medical Symposium at 131, 1963.
Common Carrier Week 8, Home Education and Health Benefits said to be underestimated, Warren Publishing Inc., Jan. 20, 1992, 9(3): 1-3.
Complaint, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 4, 2008, 14 pages.
Conrath, David W. et al., "A preliminary evaluation of alternative telecommunication systems for the delivery of primary health care to remote areas.", IEEE Transactions on Communications, COM-23(10):1119-1126, 1975.
Cope, For well-connected in study, computer's diagnosis is just a phone call away, Minneapolis Star-Tribune, Mar. 1992, pp. 03E.
Creative Strategies International (CSI), The Emerging Self-Help Healthcare Market—Microcomputer Applications, 1984, pp. 130.
Crossman, Confused? Take two aspirin and call up advisor, New Jersey Record, Apr. 1992, pp. B02.
Currid, Cheryl, "Risky Business: doctors, lawyers shy away from computer technology", PC Week, Sep. 17, 1990.
Curtin et al., "Disease Management Information System: Design, Development, Testing, and Clinical Application for Caner Management", Abstract http://ascobeta.infostreet.com/prof/me/html/abstracts/hre/m—1509.htm (1997).
Dahmer, J., "Anamnese und Befund", Georg Thieme Verlag, 1981, pp. 22-25, 44-47, 292-295 and 371-375.
Dahmer. J, Der Denkprozess "Vom Symptom zur Diagnose", Anamnese und Befund, Georg Thieme Verlag, 1981, p. 3.
Dawson, Sun, Microsoft battles over Net computing, Multichannel News, Nov. 1996.
Declaration of Goutam Patniak in Support of Defendant of Counterclaimant Alere, LLC's Motion to Compel Plaintiff Healthways, Inc.'s Response to Interrogatory No. 2, or Preclude Healthway's Future Disclosure of or Reliance on Any Commercial Embodiments, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 27, 2009, 4 pages.
Defendant-Counterclaimant Alere, LLC's Agreed Motion for Leave to Replace its Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b) and Exhibit 3 to its Opposition with Redacted Versions, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 30, 2009, 3 pages.
Defendant-Counterclaimant Alere, LLC's ALternative Motion for Leave to File First Amended Answer and Couterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 3 pages.
Defendant-Counterclaimant Alere, LLC's Memorandum in Support of its Alternative Motion for Leave to File First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24 2009, 17 pages.
Defendant-Counterclaimant Alere, LLC's Unopposed Motion for Leave to Replace its Memorandum in Support of its Alternative Motion for Leave to File First Amended Answer and Counterclaims and First Amended Answer and Counterclaims with Redacted Versions, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 30, 2009, 3 pages.
Doheny, Kathleen, "Hack Attack", LA Times Magazine, p. 8, Aug. 4, 1991.
Ellis et al., Health Education using Microcomputer: Initial Acceptability, Preventive Medicine, Jan. 1981, 10(1): 77-84.
Ellis et al., Health Education Using Microcomputers II: One Year in the Clinic; Preventive Medicine, 1982, 11:212-224.
EP Office Action dated Jan. 10, 2006 in European Patent Application No. 98911601.7, filed Mar. 13, 1998.
European Office Action dated Jan. 18, 2010 for European Patent Application No. 98911601.7, filed Mar. 13, 1998.
Evans, C. Edward, A Computer in the Waiting Room: Who Needs the Doctor?, Can Fam Phys., Apr. 1984, 30: 869-876.
Exhibit 1 to Alere's Answer to First Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 22, 2009, 2 pages.
Exhibit 1 to Declaration of Goutam Patnaik in Support of Defendant and Counterclaimant Alere, LLC's Motion to Compel Plaitiff Healthways, Inc.'s Response to Interrogatory No. 2, or Preclude Healthway's Future Disclosure of or Reliance on Any Commercial Embodiments, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 27, 2009, 2 pages.
Exhibit 1 to Defendant-Counterclaimant Alere, LLC's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24 2009, 2 pages.
Exhibit 10 to Alere, LLC's Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12 (c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 5 pages.
Exhibit 1-1 to Alere, Llc's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 83 pages.
Exhibit 12 to Alere, LLC's Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 4, 2009, 2 pages.
Exhibit 1-2 to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLCc, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 87 pages.
Exhibit 12 to Plaintiff's Opening Brief on Claim Construction, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Apr. 20, 2010, 12 pages.
Exhibit 13 to Alere, LLC's Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 4, 2009, 5 pages.
Exhibit 13 to Plaintiff's Opening Brief on Claim Construction, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Apr. 20, 2010, 12 pages.
Exhibit 14 to Alere, LLC's Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 4, 2009, 6 pages.
Exhibit 14 to Plaintiff's Opening Brief on Claim Construction, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Apr. 20, 2010, 6 pages.
Exhibit 15 to Alere, LLC's Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 4, 2009, 2 pages.
Exhibit 16 to Alere, LLC's Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 4, 2009, 3 pages.
Exhibit 2 to Alere, LLC's Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 4 pages.
Exhibit 2 to Alere's Answer to First Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 22, 2009, 5 pages.
Exhibit 2 to Defendant-Couterclaimant Alere, LLC's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24 2009, 5 pages.
Exhibit 3 to Alere, LLC's Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Alere, LLC's First Supplemental Objections and Responses to Plaintiff's Second Set of Interrogatories (No. 9-10), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 62 pages.
Exhibit 3 to Alere's Answer to Firsts Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 22, 2009, 6 pages.
Exhibit 3 to Declaration of Goutam Patnaik in Support of Defendant and Counterclaimant Alere, LLC's Motion to Compel Plaintiff Healthways, Inc.'s Response to Interrogatory No. 2, or Preclude Healthway's Future Disclosure of or Reliance on Any Commercial Embodiments, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 27, 2009, 3 pages.
Exhibit 3 to Defendant-Counterclaimant Alere, LLC's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24 2009, 6 pages.
Exhibit 4 to Alere's Answer to First Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 22, 2009, 2 pages.
Exhibit 4 to Declaration of Goutam Patniak in Support of Defendant and Counterclaimant Alere, LLC's Motion to Compel Plaintiff Healthways, Inc.'s Response to Interogatory No. 2, or Preclude Healthway's Future Disclosure of or Reliance on Any Commercial Embodiments, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 27, 2009, 9 pages.
Exhibit 4 to Defendant-Counterclaimant Alere, LLC's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 2 pages.
Exhibit 5 to Alere's Answer to First Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 22, 2009, 3 pages.
Exhibit 5 to Declaration of Goutam Patniak in Support of Defendant and Counterclaimant Alere, LLC's Motion to Compel Plaintiff Healthways, Inc.'s Response to Interrogatory No. 2, or Preclude Healthway's Future Disclosure of or Reliance on Any Commercial Embodiments, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 27, 2009, 3 pages.
Exhibit 5 to Defendant-Counterclaimant Alere, LLC's First Amended Answer and Couterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 3 pages.
Exhibit 8 to Alere, LLC's Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 3 pages.
Exhibit 9 to Alere, LLC's Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 8 pages.
Exhibit A to Defendant-Counterclaimant Alere, LLC's Agreed Motion for Leave to Replace its Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b) and Exhibit 3 to its Opposition with Redacted Versions, Alere, LLC's Opposition to Plaintiff's Partial Motion for Judgement of the Pleadings Pursuant to Rule 12(c) and Rule 9(b) Redacted,Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 21 pages.
Exhibit A to Defendant-Counterclaimant Alere, LLC's Alternative Motion for Leave to File First Amended Answer and Counterclaims, Defendant-Counteclaimant Alere, LLC's First Amended Answer and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 126 pages.
Exhibit A to Defendant-Counterclaimant Alere, LLC's Unopposed Motion for Leave to Replace its Memorandum in Support of its Alternative Motion for Leave to File First Amended Answer and Couterclaims and First Amended Answer and Counterclaims with Redacted Versions, Defendant-Counterclaimant Alrere, LLC's Memorandum in Support of its Alternative Motion for Leave to File First Amended Answer and Counterclaims, Redacted, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24 2009, 18 pages.
Exhibit A, Part 1 to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 15 pages.
Exhibit A, Part 1 to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 15 pages.
Exhibit A, Part 1 to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 15 pages.
Exhibit A, Part 2 to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 15 pages.
Exhibit A, Part 2 to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 15 pages.
Exhibit A, Part 2 to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 15 pages.
Exhibit A, Part 3 to Joint Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 17 pages.
Exhibit A, Part 3 to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 17 pages.
Exhibit A, Part 3 to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 17 pages.
Exhibit B to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 18 pages.
Exhibit B to Defendant-Counterclaimant Alere, LLC's Agreed Motion for Leave to Replace its Opposition to Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b) and Exhibit 3 to its Opposition with Redacted Versions, Alere, LLC's First Supplemental Objections and Responses to Plaintiff's Second Set of Interrogatories (No. 9-10) Redacted, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 63 pages.
Exhibit B to Defendant-Counterclaimant Alere, LLC's Unopposed Motion for Leave to Replace its Memorandum in Support of its Alternative Motion for Leave to File First Amended Answer and Counterclaims and First Amended Answer and Counterclaims with Redacted Versions, Defendant-Counterclaimant Alere, LLC's First Amended Answer and Counterclaims, Redacted, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 24, 2009, 127 pages.
Exhibit B to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 24 pages.
Exhibit B to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 24 pages.
Exhibit B to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 24 pages.
Exhibit C to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 4, 2008, 14 pages.
Exhibit C to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 8 pages.
Exhibit C to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 7 pages.
Exhibit C to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 8 pages.
Exhibit D to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 15 pages.
Exhibit D to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 3 pages.
Exhibit D to Memorandum of Law in Support of Plaintiffs Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 31, 2009, 3 pages.
Exhibit D to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 8 pages.
Exhibit D to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 8 pages.
Exhibit E to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 12 pages.
Exhibit E to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 8 pages.
Exhibit E to Memorandum of Law in Support of Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 31, 2009, 3 pages.
Exhibit E to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 8 pages.
Exhibit E to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 8 pages.
Exhibit F to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 61 pages.
Exhibit F to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 7 pages.
Exhibit F to Memorandum of Law in Support of Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 31, 2009, 3 pages.
Exhibit F to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 7 pages.
Exhibit F to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 7 pages.
Exhibit G to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 31 pages.
Exhibit G to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 7 pages.
Exhibit G to Memorandum of Law in Support of Plaintiff's Partial Motion for Judgment on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 31, 2009, 2 pages.
Exhibit G to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 7 pages.
Exhibit G to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 7 pages.
Exhibit H to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 13 pages.
Exhibit H to Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 9 pages.
Exhibit H to Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 9 pages.
Exhibit H to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 9 pages.
Exhibit I to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 9 pages.
Exhibit J to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 22 pages.
Exhibit J to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 9 pages.
Exhibit K to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 41 pages.
Exhibit K to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 6 pages.
Exhibit L to Alere, LLC's First Supplemental Objections and Responses to Plaintiff's First Set of Interrogatories (Nos. 1-8), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Mar. 3, 2009, 18 pages.
Exhibit L to Second Revised Joint Claim Construction Statement, Healthways Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009. 5 pages.
Fallon et al., A Primer for Writing Medical Data Base for the Clinical Decision Support System, ed. Schande', et al. Computers and Brains, Progress in Brain Research, 33: 155-175.
Federal Register, National Telecommunications and Information Administration, DOC—Administration Policy Statement, Notices, Sep. 21, 1993, Fed. Reg., 58(181): 49025-49036.
Fielding J., Appraising the Health of Health Risk Appraisal, Am J Pub Health, Apr. 1982, 72(4): 337-340.
First Amended Complaint, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 15, 2009, 15 pages.
First Opinion Corporation, Canadian Trademark Application File History TMA447,669, registered Sep. 15, 1995 for the Trademark/Servicemark: First Opinion, pp. 51.
Fisehr et al., "Great Expectations: Expectation-based reasoning in Medical Diagnosis, " Proceedings of the 12th Annual Symposium on Computer Applications in Medical Care, Nov. 6, 1988, pp. 38-42.
Frenger, Paul, "Advanced techniques used to create a telephone medical consultation service", ISA, pp. 103-107, 1983.
Frenger, Paul, "Details of a database management system for a telephone medical consultation service." IEEE Frontiers of Computers in Medicine, 1982.
Freudenheim, Milt, "Computer says take 2 asprin", The New York Times, Business and Health, p. D2, Jun. 25, 1991.
Gale et al., Medical Diagnosis From Student to Clinician, (1983) pp. 1-22.
Gardner, Integrated Computer Systems for Monitoring of the Critically III, Proceedings of 1st Annual Symposium on Computer Application in Medical Care, Washington, D.C., IEEE Computer Society, 1997, pp. 301-302.
Gini et al., "A Serial Model for Computer Assisted Medical Diagnosis", Int J Bio-Med Comp. (1980) 11: 99-113.
Gobard, Gary A., Class Notes, Tulane Medicine, Tulane University Medical Center, 1430 Tulane Avenue, New Orleans, LA 70112-2699, p. 22, Jun. 1991.
Goetz et al., Health Risk Appraisal: The Estimation of Risk, Health Promotion at the Worksite, Mar.-Apr. 1980, 95 (2): 119-126.
Gome, Amanda, "A picture of success", Herald-Sun, p. 13, Nov. 19, 1991.
Gorry et al., Decision analysis at the basis for computer-aided management of acute renal failure, Am. J. Med., Oct. 1973, vol. 3, Issue 55, pp. 473-484.
Gorry, G. Anthony, "FA6.3 Automating Judgemental decision making in medicine", Bulletin of the Operations Research Society of America, 19(2), 1971.
Haug et al., Decision Support in Medicine: Examples from the HELP System, Computers and Biomedical Research, 1994, 27: 396-418.
Healthways, Inc.'s Third Supplemental Response to Defendant and Counterclaimant Alere, LLC's First Set of Interrogatories and Exhibit E, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Oct. 28, 2009, 14 pages.
Henderson, A Trainable Pattern Classifier for Medical Questionnaires, Annals of Biomed Engin., Jan. 27, 1972, 1: 115-133.
Hile et al., "Reliability of an Automated Decision Support System for Behavioral Treatment Planning: Preliminary Results from the Mental Retardation-Expert", Computes in Human Services (1994) 10(4): 19-29.
Husdon et al., "Human-Computer Interaction in a Medical Decision Support System", IEEE Computer Society Press, 2:429-435, 1989.
International Preliminary Examination Report dated Jun. 11, 1999 in OCT/US98/04685, filed Mar. 13, 1998.
International Search Report dated Aug. 12, 1998 in PCT/US98/04865, filed Mar. 13, 1998.
Japanese Decision on Appeal dated Jul. 7, 2009 for Japanese Patent Application No. 539802/98, filed Mar. 13, 1998.
Japanese Office Action dated Sep. 3, 2009 for Japanese Patent Application No. 2008-097100, filed Mar. 13, 1998.
Johnson et al., Psychological Systems Questionnaire: An Objective Personality Test designed for on-line computer Presentation, Scoring, and Interpretation, Behav Res Meth Instrument., 1979, 11(2): 257-260.
Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 10, 2009, 60 pages.
JP Office Action dated Apr. 24, 2007, in Japanese Patent Application No. 539802/98, filed Mar. 13, 1998.
JP Office Action dated Aug. 18, 2008 in Japanese Patent Application No. 539802/98 (under Appeal No. 2008-005314).
JP Office Action dated Feb. 27, 2007 in Japanese Patent Application No. 506146/98, filed Jul. 11, 1997.
Kerr, Jennifer, "Phone is link to health-care information", San Diego Union-Tribune, p. A3, Sunday, Jul. 18, 1993.
Koska, Mary T., Primary Care: Hospitals Begin to Target Community Needs, Hospitals, Apr. 5, 1990, 64(7): 24-28.
Lai, Abstraction models at system level for interactive multimedia scripting, Master's Thesis, Massachusetts Institute of Technology, May 1995, Boston.
Larsson et al., "An Expert System Interface for an Identification Program," Automatica, Pergamon Press Ltd., Oxford, GB., 27(6): 919-930, 1991.
Laughlin, Michael J., ed., "Telecommunications may offer poor a 'road' to healthcare", Computer in Health Care, pp. 32-37, Nov. 1992.
Levin, Carol, "Patient, heal thyself", PC Magazine p. 32, Mar. 16, 1993.
Lunin, Lois F., On Speaking Terms With the Computer, Information Today, Feb. 1992, 9(2): 19-20.
Magnet, Who's winning the information revolution, Fortune, Nov. 30, 1992, vol. 12, Issue 126, pp. 110-117.
Malcolm et al., Computer-Assisted Diagnosis of Alcoholism, Computers in Human Services, 1989, 5(3/4): 163-170.
Mallory, Jim, "Computers now giving medical advice", Newsbytes, American Association for the Advancement of Science, Panel Discussion, Feb. 19, 1992.
Mallya et al., Correlation in rheumatoid arthritis of concentrations of plasma C3d, serum rheumatoid factor, immune complexes and C-reactive protein with each other and with clinical features of disease activity., Clin. Exp. Immunol., 1982, Issue 48, pp. 747-753.
Markoff, Making the PC come alive, New York Times, Sep. 1995.
McDonald et al., "Health in the Information Age: The Emergence of Health Oriented Telecommunication Applications", Environmental Science and Policy Institute, 1992.
McNish, David A., EMED Electronic Medical Database, DMC Software Packaging and Manual, DMC Software Company., 1987, 7 pages.
Medical Computer Consultants' Consortium, Inc. "Disease State Management Software System Product Description", http://www.mc3co.com/DMSS.htm (1997).
Memorandum in Support of Defendant and Counterclaimant Alere, LLC's Motion to Compel Plaintiff Healthways Inc.'s Response to Interrogatory No. 2, or Preclude Healthway's Future Disclosure of or Reliance on Any Commercial Embodiments, Healthways, Inc. v. Alere, LLC, U.S. District County for the Northern District of Illinois, Case No. 08CV06337, Mar. 27, 2009, 20 pages.
Memorandum of Law in Support of Plaintiff's Motion to Dismiss under Rule 12(b)(6) or Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Dec. 29, 2008, 9 pages.
Memorandum of Law in Support of Plaintiff's Partial Motion for Judgement on the Pleadings Pursuant to Rule 12(c) and Rule 9(b), Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Aug. 31, 2009, 12 pages.
Miller et al., The Computerized Carroll Rating Scale, Indiana University School of Medicine, 1985, pp. 344-347.
Miller, Dial 1-900 for doctor, Newsweek, Oct. 1991.
Okada, Medical data base system with an ability of automated diagnosis, Computer Programs in Biomedicine, Sep. 197, vol. 3, Issue 7, pp. 13-170.
Olson et al., 21st century learning and health care in the home: creating a national telecommunications network, IAF/CRI, Jan. 1992.
Oneil, et al., "Diagnostic Support in the Oxford System of Medicine", Conference Paper, IEEE Coll, on Computer Based Diagnosis, p. 8/1-4, 1989.
Partin, A Preliminary Conceptual Framework for the Design, Development, and Use of Client-Oriented Information Systems in Health, J Med Sys. 1987, 11(2/3): 205-217.
Patel et al., A Computer-based Automated, Telephonic Systems to Monitor Patient Progress in the Home Setting, J Med Sys., 1992 16(2/3): 101-112.
Paueker et al., Towards the simulation of clinical cognition: taking a present illness by computer, Am. J. Med., Jun. 1976, vol. 7, Issue 60, pp. 981-996.
Plaintiff's Amended Reply to Alere Medical Inc.'s Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Feb. 10, 2009, 11 pages.
Plaintiff's Opening Brief on Claim Construction, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Apr. 20, 2010, 33 pages.
Plaintiff's Reply to Alere's Couterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Dec. 29, 2008, 10 pages.
Plaintiff's Reply to Alere's First Amended Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 9, 2009, 11 pages.
Plaintiff's Reply to Alere's Medical Inc.'s Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Feb. 10, 2009, 11 pages.
Replacement exhibit 1 to Alere's Answer to First Amended Complaint and Counterclaims, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Jan. 23, 2009, 4 pages.
Replacement Statement and Explanation dated Nov. 21, 2009 from Request for Ex Parte Reexamination of U.S. Patent No. 90/009594, filed Nov. 21, 2009.
Reply Memorandum in Support of Plaintiff's Partial Motion for Judgment on the Pleadings Pursuant to Rule 12(C) and Rule 9(B), Healthway's Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337.
Request for Ex Parte Reexamination filed Oct. 8, 2009 of USP 6,113,540, issued Sep. 5, 2000.
Revised Joint Claim Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Sep. 4, 2009, 58 pages.
Riordan, Patents: Prodigy's patent is being debated as a possible threat to Sun Microsystems' Java language, New York Times, Feb. 1996.
Roberts, Dr. Schueler's home medical advisor 2.0, Compute!, Oct. 1992, Issue 145, pp. 106.
Rose, J. ed., "Progress of Cybernetics, vol. 2. Cybernetics and Industry, Social and Economic Consequences, Cybernetics and Artifacts," Proceedings of the First International Congress of Cybernetics, London, Gordon and Breach Science Publishers, pp. 803-811, 1969.
Rymon, et al., "Progressive Horizon Planning-Planning Exploratory-Corrective Behavior", IEEE Transactions on Systems, Man, and Cybernetics, 23(6):1551-1560, Nov./Dec. 1993.
Sacks, Terry, "Pocket computer may cure technology-shy physicians", San Diego Union-Tribune, p. E-16, Mar. 24, 1992.
Salvans, P. Ferrer and Alonso L. Vallès, "An epidemiologic approach to computerized medical diagnosis-AEDMI program", Computer Biol. Med., 20(6): 433-443, 1990.
San Diego Emergency Physicians Society, Meeting Minutes, Regular Oct. 1991 Meeting, P.O. Box 16685, San Diego, CA 92176, first page.
Schild, W. et al., "Computer-aided diagnosis with an application to endocrinology", IBM J. Res. Develop., 22 (5):518-532, 1978.
Second Revised Joint Claimant Construction Statement, Healthways, Inc. v. Alere, LLC, U.S. District Court for the Northern District of Illinois, Case No. 08CV06337, Nov. 6, 2009, 63 pages.
Shannon, "Peripherals; advice on a disk: the doctor is really in", New York Times, Jul. 14, 1992 at C7.
Shannon, "Peripherals; Doctor, I have this funny pain . . . ", New York Times, Nov. 3, 1992.
Shannon, Peripherals; choosing a college, New York Times, Jan. 1989.
Shapiro, Encyclopedia of Artificial Intelligence, 2nd Edition, vol. 2, pp. 916-926, John Wiley & Sons, Inc., 1992.
Shneidermann, Ben, Touch Screens now offer Compelling Uses, IEEE Software, 1991, pp. 93-94.
Shortlife, Edward H., "Consultation system for physicians: the role of artificial intelligence techinques", Expert Systems and Al Applications, pp. 323-333, 1980.
Shortliffe et al., A model of Inexact Reasoning in Medicine, 1975, (shortened/edited version) Mathematical Biosciences, 11: 233-262.
Sloane, L., "For round-the-clock diagnosis, just pick up your telephone", New York Times, p. 16, Jul. 13, 1991.
Smothers, R. "New video technology lets doctors examine patients many miles away", New York Times, Sep. 16, 1992.
Starr et al., "A microcomputer-based medical expert system shell using a weight/threshold decision mechanism", Proc. of the 13th Annual Northeast Bioengineering Conference, Mar. 12-13, 1987, pp. 279-281.
Starr et al., "Gycon: A Microcomputer Based Gynecological Consultant", Proceed Inter Comp Symposium, Dec. 17-19, 1986, Tainan, Taiwan R.O.C. pp. 1678-1684.
Stead et al., Computer-Assisted Interview of Patients with Functional Headache, Arch Intern Med., 1972, 129:950-955.
Stearn et al., A statistical analysis of subjective and objective methods of evaluating fabric handle Part 2: Relationship between subjective and objective measurements, Journal of the Textile Machinery Society of Japan, 1988, vol. 2, Issue 34, pp. 39-46.
Szolovits et al., "Artificial Intelligence in Medical Diagnosis", Ann Intern Med., Jan. 1988, 108(1): 80-87; (pp. 1-12).
Szolovits et al., Categorical and probabilistic reasoning in medical diagnosis, Artificial Intelligence, Aug. 1978, vol. 1&2, Issue 11, pp. 115-144.
Szolovits et al., Guardian Angel: Patient-Centered Health Information Systems, May 1994, MIT Laboratory for Computer Science, TR-604, pp. 40.
Tedesco, Microsoft, Intel and Sun advance NC visions, Broadcasting & Cable, Nov. 1996.
Templeton, Medical software that makes house calls, Business Week, Jun. 1992, Issue 3720.
The National Information Infrastructure: Agenda for Action, U.S. Government Paper, 1993, pp. 42.
Thorpe, William C. et al., "A microcomputer-based interactive cough sound analysis system", Computer Methods and Programs in Biomedicine, Section II, Systems and programs, 36:33-43, 1991.
Vaughn et al., Effective algorithm-based triage and self-care protocols: quality medicine at lower costs, Ann. Emerg. Med., Jan. 1980, vol. 1, Issue 9, pp. 31-36.
Wagner, J et al., "A knowledge-based system for interactive medical diagnosis encoding", Conference Paper of Expert Systems and Decision Support in Medicine, 33rd Annual Meeting of the GMDS EFMI Special Topic Meeting, pp. 449-465, Sep. 1998.
Walmsley et al., Normal "Anion Gap" (Hyperchloremic) Acidosis, Case Reports, Clin Chem., 1985, 31(2): 309-313.
Walz, Nancy, Computer system aims to wipe out medical paperwork:, The Associated Press, Business News, Jun. 25, 1991.
Warner, Knowledge sectors for logical processing of patient data in the help system, Proc. IEEE, 1978.
Waterman, A Guide to Expert Systems, Addison-Wesley Publishing Co., pp. 46-47 and 272-288, 1986.
Weinstock, Edward, "An Apple a Day", Cover, Avant-Garde, 1984.
Weinstock, Edward, An Apple a Day . . . ™, Computer Program Manual, Avant-Garde Publishing Corporation, 1984, pp. 47.
Weiss et al., Glaucoma Consultation by Computer, Comput Biol Med.., Pergamon Press, 1978, 8: 25-40.
Werner et al., "Interlocutor: Conferring with an Expert Diagnostic Consultant in Geriatric Psychiatry", Conference Paper, IEEE Engineering in Medicine and Biology, 3 pages, 1989.
Wijkstra et al., Relation of lung function, maximal inspiratory pressure, dyspnoea and quality of life with exercise capacity in patients with chronic obstructive pulmonary disease, Thorax, May 1994, vol. 5, Issue 49, pp. 468-472.
Written Opinion (Rule 66) dated Dec. 15, 1998 in PCT/US98/04865, filed Mar. 13, 1998.
Zallen, Member-centered managed care and the new media, ed. Linda M. Harris, in Health and the Mew Media, 1995.

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140107461A1 (en) * 2012-10-15 2014-04-17 ClinicalBox, Inc. Adaptive Medical Testing

Also Published As

Publication number Publication date
US20080052120A1 (en) 2008-02-28
NZ337954A (en) 2001-09-28
US20080051639A1 (en) 2008-02-28
AU2010238555A1 (en) 2010-11-18
AU2003235078A1 (en) 2003-09-11
AU6552498A (en) 1998-09-29
US8630875B2 (en) 2014-01-14
AU2007201421A1 (en) 2007-04-19
IL131873A (en) 2006-06-11
IL131873A0 (en) 2001-03-19
EP0966719A1 (en) 1999-12-29
US8663104B2 (en) 2014-03-04
US6770029B2 (en) 2004-08-03
US20080052132A1 (en) 2008-02-28
US20120029935A1 (en) 2012-02-02
US20080052116A1 (en) 2008-02-28
US8727979B2 (en) 2014-05-20
US20080052118A1 (en) 2008-02-28
US20080052122A1 (en) 2008-02-28
US7769600B2 (en) 2010-08-03
UA64743C2 (en) 2004-03-15
US8727976B2 (en) 2014-05-20
AU2007201421B2 (en) 2010-07-29
US20030036686A1 (en) 2003-02-20
US20080051641A1 (en) 2008-02-28
US8740790B2 (en) 2014-06-03
US20080052123A1 (en) 2008-02-28
US20080052121A1 (en) 2008-02-28
CN1604111A (en) 2005-04-06
US8066636B2 (en) 2011-11-29
US20080045811A1 (en) 2008-02-21
US20030153819A1 (en) 2003-08-14
US7993267B2 (en) 2011-08-09
US6234964B1 (en) 2001-05-22
CA2284168A1 (en) 1998-09-17
WO1998040835A1 (en) 1998-09-17
AU762361B2 (en) 2003-06-26
US8392217B2 (en) 2013-03-05
US8682694B2 (en) 2014-03-25
US8060378B2 (en) 2011-11-15
CN1252877A (en) 2000-05-10
US20010012913A1 (en) 2001-08-09
US20080059232A1 (en) 2008-03-06
ID23390A (en) 2000-04-20
JP2002512712A (en) 2002-04-23
US7297108B2 (en) 2007-11-20
US20080052130A1 (en) 2008-02-28
TW424188B (en) 2001-03-01

Similar Documents

Publication Publication Date Title
US8628470B1 (en) Disease management system and method including medication therapy self-management
JP4897057B2 (en) Computerized medical advice system
US7300402B2 (en) Computerized medical diagnostic and treatment advice system
MXPA99008372A (en) Disease management system

Legal Events

Date Code Title Description
AS Assignment

Owner name: SUNTRUST BANK, AS ADMINISTRATIVE AGENT, GEORGIA

Free format text: SECURITY AGREEMENT;ASSIGNORS:HEALTHWAYS, INC.;CLINICAL DECISION SUPPORT, LLC;HEALTHHONORS, LLC;REEL/FRAME:028349/0418

Effective date: 20120608

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: HEALTHHONORS, LLC, TENNESSEE

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SUNTRUST BANK, AS ADMINISTRATIVE AGENT;REEL/FRAME:039405/0507

Effective date: 20160731

Owner name: HEALTHWAYS, INC., TENNESSEE

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SUNTRUST BANK, AS ADMINISTRATIVE AGENT;REEL/FRAME:039405/0507

Effective date: 20160731

Owner name: CLINICAL DECISION SUPPORT, LLC, TENNESSEE

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:SUNTRUST BANK, AS ADMINISTRATIVE AGENT;REEL/FRAME:039405/0507

Effective date: 20160731

Owner name: HEALTHWAYS SC, LLC, TENNESSEE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HEALTHWAYS, INC.;AMERICAN HEALTHWAYS SERVICES, LLC;HEALTHWAYS INTERNATIONAL, INC.;AND OTHERS;REEL/FRAME:039657/0024

Effective date: 20160731

AS Assignment

Owner name: CLINICAL DECISION SUPPORT, LLC, TENNESSEE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:FIRST OPINION CORPORATION;REEL/FRAME:041646/0324

Effective date: 20090730

Owner name: FIRST OPINION CORPORATION, CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ILIFF, EDWIN C.;REEL/FRAME:041652/0103

Effective date: 19990508

AS Assignment

Owner name: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS ADMINIS

Free format text: SECURITY INTEREST;ASSIGNORS:SHARECARE, INC.;LUCID GLOBAL, INC.;HEALTHWAYS SC, LLC;AND OTHERS;REEL/FRAME:041817/0636

Effective date: 20170309

AS Assignment

Owner name: ABC FUNDING, LLC, AS AGENT, MASSACHUSETTS

Free format text: SECURITY INTEREST;ASSIGNORS:SHARECARE, INC.;LUCID GLOBAL, INC.;HEALTHWAYS SC, LLC;AND OTHERS;REEL/FRAME:042380/0225

Effective date: 20170511

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: SHARECARE, INC., GEORGIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ABC FUNDING, LLC, AS AGENT;REEL/FRAME:056807/0581

Effective date: 20210701

Owner name: LUCID GLOBAL, INC., GEORGIA

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ABC FUNDING, LLC, AS AGENT;REEL/FRAME:056807/0581

Effective date: 20210701

Owner name: HEALTHWAYS SC, LLC, TENNESSEE

Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:ABC FUNDING, LLC, AS AGENT;REEL/FRAME:056807/0581

Effective date: 20210701

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20220114