US20190147995A1 - Systems and methods for clinical decision-making - Google Patents
Systems and methods for clinical decision-making Download PDFInfo
- Publication number
- US20190147995A1 US20190147995A1 US16/154,760 US201816154760A US2019147995A1 US 20190147995 A1 US20190147995 A1 US 20190147995A1 US 201816154760 A US201816154760 A US 201816154760A US 2019147995 A1 US2019147995 A1 US 2019147995A1
- Authority
- US
- United States
- Prior art keywords
- data
- provider
- patient
- computer
- decision
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT 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/60—ICT 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/67—ICT 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
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H20/00—ICT specially adapted for therapies or health-improving plans, e.g. for handling prescriptions, for steering therapy or for monitoring patient compliance
- G16H20/10—ICT 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
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/04—Inference or reasoning models
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06N—COMPUTING ARRANGEMENTS BASED ON SPECIFIC COMPUTATIONAL MODELS
- G06N5/00—Computing arrangements using knowledge-based models
- G06N5/04—Inference or reasoning models
- G06N5/048—Fuzzy inferencing
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT 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/20—ICT 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 management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT 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/60—ICT 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/63—ICT 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 local operation
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/20—ICT 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
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/50—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for simulation or modelling of medical disorders
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H50/00—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics
- G16H50/70—ICT specially adapted for medical diagnosis, medical simulation or medical data mining; ICT specially adapted for detecting, monitoring or modelling epidemics or pandemics for mining of medical data, e.g. analysing previous cases of other patients
Definitions
- the present disclosure relates generally to providing recommendations based on receiving and processing historical data. More specifically, the present disclosure relates to systems and methods for learning decision-making and providing recommendations based on the learned decision-making. In some embodiments, the recommendation may be made automatically.
- Embodiments of the present disclosure relate to, among other things, methods and systems for providing a treatment recommendation.
- Each of the embodiments disclosed herein may include one or more of the features described in connection with any of the other disclosed embodiments.
- computer-implemented methods for automatically providing a treatment recommendation, the method may include receiving historical data comprising at least one of provider data and patient data; processing, using a processor, the historical data to identify one or more patterns; generating one or more decision models from the historical data and the decision patterns; and providing one or more recommendations based on the one or more decision models.
- aspects of the method may include one or more of the following: further comprising receiving electronic feedback on at least one of the one or more recommendations; further comprising storing the electronic feedback as historical data; further comprising exchanging the electronic feedback with a third party; further comprising receiving real-time data comprising at least one of provider data and patient data; wherein the historical data comprises treatment instructions and the real-time data comprises compliance with the treatment instructions; wherein the real-time data is received from a patient's electronic device; further comprising extracting metadata from the historical data; further comprising biasing the historical data based on the metadata; wherein the processor uses one or more machine learning algorithms; wherein the generating one or more decision models comprises importing models from a library of models; further comprising accessing one or more medical records and parsing the historical data from the one or more medical records; further comprising presenting the one or more identified patterns to a provider; further comprising receiving instructions to modify the one or more decision models; further comprising providing a comparison between the one or more recommendations, a recommendation based on standard guidelines, and
- the processing device may include one or more of the following features: the method further comprising receiving electronic feedback on at least one of the one or more recommendations; and the method further comprising further comprising receiving real-time data comprising at least one of provider data and patient data.
- a non-transitory computer-readable medium storing a set of instructions that, when executed by a processor, may perform a method of providing a treatment recommendation, the method may include receiving historical data comprising at least one of provider data and patient data; processing, using a processor, the historical data to identify one or more patterns; generating one or more decision models from the historical data and the decision patterns; and providing one or more recommendations based on the one or more decision models.
- FIG. 3 is a flow diagram of an exemplary method for extracting and identifying metadata, according to an exemplary embodiment of the present disclosure
- FIG. 4 is a flow diagram of an exemplary method for selecting and applying algorithms to data, according to an exemplary embodiment of the present disclosure
- FIG. 5 is a flow diagram of an exemplary method for evaluating and modifying a recommendation, according to an exemplary embodiment of the present disclosure
- FIG. 6 is a flow diagram of an exemplary method for collecting data, according to an exemplary embodiment of the present disclosure
- FIG. 7A is flow diagram an exemplary method for electronically selecting a recommendation, according to an exemplary embodiment of the present disclosure
- FIG. 7B is a flow a flow diagram of an exemplary method for electronically presenting a clinical decision, model to a provider and a patient, according to an exemplary embodiment of the present disclosure
- FIG. 8 is a schematic diagram of an arrangement by which a clinical decision may be generated, according to an exemplary embodiment of the present disclosure.
- FIG. 9 is a simplified functional block diagram of a computer that may be configured as a host server, for example, to function as healthcare provider decision-making server, according to an exemplary embodiment of the present disclosure.
- the present disclosure is drawn to systems and methods for providing recommendations based on analyzing past decisions. More specifically, the present disclosure relates to systems and methods for analyzing historical data to learn provider decision-making, applying machine learning algorithms to generate decision models, and providing (e.g. automatically) recommendations on subsequent scenarios based on the learned decision-making.
- the provider may provide relevant information to the service, such as billing information, type of healthcare practice (e.g. pediatric, psychiatry, internal medicine, and/or surgical), and/or information about the provider's practice and preferences (e.g. proponent of surgical intervention, proponent of alternative medical therapies such as yoga and meditation).
- the service may provide confirmation of registration and/or request further information from the provider to complete registration in any suitable manner.
- the service also may provide the provider with materials to access its services, for example by providing a software application (such as a mobile application) having a graphical user interface (GUI) and/or codes to access restricted web-sites.
- GUI graphical user interface
- the software application may allow the provider to view, transmit, and receive information to and from the service via the GUI.
- the provider may designate any preferences to the service during the registration step 102 and/or any other time.
- the provider may indicate, via the GUI, that the service should only be used for patients who have a blood glucose level above, e.g. 130 mg/dL.
- the service may provide programming, such as software applications, that may be integrated with existing provider programming.
- the programming e.g. a software application
- the provider also may instruct that the service to provide selective access to patient's.
- the provider may allow a patient to selectively view information provided by the service and allow the patient to submit relevant patient data to the service, either selectively or automatically (e.g. via automatic updates from a patient's electronic device).
- the provider may allow a patient to download the service's software application to the patients electronic device and allow the patient to submit data to the service via the electronic device (e.g. a mobile device which may have a built in blood glucose monitor or heart rate monitor) either through wired of wireless communication.
- the electronic device e.g. a mobile device which may have a built in blood glucose monitor or heart rate monitor
- Historical health data may be received by the service that is relevant to the provider and the provider's patients.
- This data may be electronically transmitted by the provider and/or the patient and received by the service at step 104 .
- the data may be electronically transmitted and received by the service at step 104 in any suitable manner.
- the provider may access the software application or secure server and send or drop electronic data files via a network, e.g. the Internet so that the files may be accessed by the service.
- the provider may allow the service limited access in compliance with any healthcare privacy regulations and other applicable regulations, to any electronic medical records, patient prescription records, referral records, etc., and the service may electronically retrieve healthcare data from such electronic records (e.g. automatically).
- patient data may be electronically transmitted by a patient and may be electronically received by the service in any suitable manner.
- the patient data may be actively submitted by the patient via a software application and/or may be automatically electronically retrieved by the service from an electronic device of the patient ( FIG. 2 ) that may measure patient health values, such as heart rate, blood glucose, blood oxygen, blood pressure, activity, stress, mood, and/or sleep either periodically or continuously.
- the historical data received at step 104 may include any relevant historical data, including a clinical profile of the patient such as diseases, significant medical events (e.g. heart attack, stroke, head trauma, transplant), disease stage, lab values, patient self-reported clinical, behavioral and psycho-social data, patient's demographics, medical history, provider characteristics such as age, years of clinical practice experience, size of practice, specialty, demographics, context of a patient's visit such as date, day, time, location, duration of visit, and/or a decision which includes medication change, psycho-therapy, dose change, lifestyle modification (diet, exercise, weight loss), recommendation for lab test(s), education, and may include the reasoning behind the provider's decision(s).
- a clinical profile of the patient such as diseases, significant medical events (e.g. heart attack, stroke, head trauma, transplant), disease stage, lab values, patient self-reported clinical, behavioral and psycho-social data, patient's demographics, medical history, provider characteristics such as age, years of clinical practice experience, size of practice, specialty, demographics, context of a
- the historical data received by the service at step 104 may be stored in a database at step 106 such as a server, cloud, or any other digital memory device.
- the data may be accessed at any time by the service and may be displayed, printed, or updated in any suitable manner.
- the stored data may be organized and accessed in any suitable manner.
- the data may be electronically tagged with various identifiers, such as age, gender, clinical condition, etc.
- metadata may be extracted from the stored data ( FIG. 3 ).
- the data stored in the database at step 106 may be electronically processed in any suitable manner.
- various algorithms may be applied to the data to learn from/be trained by analyzing the data.
- machine learning algorithms and/or other higher-level algorithms e.g. supervised and unsupervised learning algorithms
- machine learning algorithms may include artificial neural networks, Bayesian statistics, case-based reason, decision trees, inductive logic processing, Gaussian process regression, Gene expression programming, Logistic model trees, stochastic modeling, statistical modeling (e.g.
- machine-learning algorithms may be applied to the data to learn the characteristics of patients for which the provider has prescribed or modified use of a drug, provided a referral to another provider, recommended a lifestyle change (e.g. exercise, diet, and/or stress management).
- a lifestyle change e.g. exercise, diet, and/or stress management.
- the machine learning algorithms applied at step 108 may detect any patterns, idiosyncrasies, or any other significant associations that may be used in generating a decision model that mimics or attempts to understand the decision-making of the provider and/or predicted behavior of the patient.
- the machine-learning algorithm may identify a patient cohort for whom components of a treatment plan may be effective, ineffective, or partially effective, such as a cholesterol-lowering drug that is ineffective for patients with neuropathy.
- any patterns identified in step 108 may be presented to the provider to improve the provider's clinical knowledge.
- the machine learning algorithm applied at step 108 may detect patient compliance with the provider's treatment plan, for example, it may be determined that 90% of the provider's patients over the age of 85 did not adhere to taking dementia drug X.
- the application of the one or more machine learning algorithms at step 108 may be processed to generate clinical decision models at step 110 .
- the models may be based on any patterns or other information learned by the machine learning algorithms.
- the models may be generated using one or more processors and may be tested with sample data that may be reviewed and automatically validated.
- existing models may be imported from databases or libraries, processed, and applied to the data processed at step 108 .
- the service may send the provider a notification that it is ready to provide clinical recommendations.
- the notification may be sent when it is determined sufficient data has been collected to provide an accurate recommendation.
- the notification may be sent after a day, a week, a month, three months, or any other period of time.
- the notification may be in any suitable form, e.g. an electronic message, alert, and/or phone call.
- the service may receive information in connection with a clinical scenario at 112 , for example, from the provider, in any suitable manner (e.g. via a software application over the Internet).
- the clinical scenario may be associated with an upcoming patient appointment, a current patient appointment, or a past patient visit.
- the service may process the information received in connection with the clinical scenario in any suitable manner.
- the clinical scenario may be submitted to the service directly by the provider or a proxy of the provider. For example, a patient may visit a physician's office and provide a nurse with information regarding the patient's reason for the visit, (e.g. onset of frequent migraines), and the nurse may record the patient's diagnostic information (e.g. weight, blood pressure, blood glucose level, and heart rate), and submit a recommendation request to the service on behalf of the physician.
- diagnostic information e.g. weight, blood pressure, blood glucose level, and heart rate
- Real-time data may be received at 118 after generating the decision models 110 or any time during method 100 .
- the real-time data may include any relevant patient and/or provider information that may be used to generate the decision model or to improve the decision model.
- real-time data may include behavioral data, demographic data, and financial data.
- the real-time data may be selectively collected or continuously collected from the provider and patients.
- the real-time data also may be obtained that is non-specific to the provider and/or the patient, such as weather conditions, current events, date, and/or season.
- This non-specific real-time data may be used to improve the accuracy the recommendation, for example, if the real-time data indicates that the temperatures for the last ten days where the patient lives have been below ⁇ 10 degrees Fahrenheit, the service may not recommend that a patient start exercising outside as it may be too cold to exercise outside. In some examples, if the service is unable to complete a decision model, real-time data may be requested to complete or improve the decision model.
- step 114 may include automatically or upon provider selection, applying one or more of the decision models to the clinical scenario received at step 112 and/or extracting discrete data values from the clinical scenario and applying the decision models to each data value separately, and then combining the decision models.
- the clinical scenario may include a patient who is a 67-year old male smoker that has type-2 diabetes, and has previously suffered a stroke. The patient may visit the provider complaining of shortness of breath. In addition, the patient may be receptive to lifestyle changes and the provider may indicate resistance to trying new drug therapies.
- One or more models may be applied to each the clinical scenario data values (e.g., patient age, diagnostic information, behavioral values, provider characteristics).
- all of the clinical scenario data values may be treated together and one or more models may be applied to all or subgroups of the data values.
- the results of applying the decision models may be further processed to detect any inconsistencies and/or errors and may be presented to the provider as a recommendation in any suitable manner for evaluation.
- the recommendation may include a recommendation based on applying the machine learning data algorithms at step 108 to learn the provider's decision-making characteristics and application of the decision models.
- the recommendations may include recommendations based on other provider decision-making characteristics, recommendations based on standard guidelines (e.g. according to the American Diabetes Association, American Medical Association, etc.), and/or any other sources.
- the service may provide a comparison of each of the recommendations and also may suggest any changes in the provider's decision-making to improve patient treatment, reduce healthcare costs, etc.
- the service may provide a rationale for each recommendation.
- the service may receive electronic feedback on the recommendation.
- the feedback may be in the form of an evaluation by the provider and/or the patient on the recommendation.
- an evaluation form soliciting feedback on the recommendation may be sent by the service for completion by the provider and/or patient.
- the evaluation may include an indication of whether or not the recommendation was followed, a rating of the recommendation, an explanation of the why the recommendation was followed or why it was not followed.
- the patient may receive a treatment plan that is tailored to the patient and the provider may quickly and easily provide a treatment plan that is in line with provider's standard of care and philosophy.
- the provider's decision may be recorded at step 120 and may be stored as historical data for use in subsequent recommendations.
- the provider's recommendation may be presented to the user in any suitable manner.
- the results of the provider's decision and/or other provider decision's may be saved and exchanged (e.g. sold and/or exchanged for other data) to a third party without including any patient identifying data.
- a pharmaceutical company may purchase data from the service on provider decisions in order to improve marketing and research and development efforts.
- health insurance companies may be interested in the provider decision data to improve healthcare services and reduce costs.
- the provider decision data also may be provided to improve standard treatment guidelines and evaluate provider adherence to standard guidelines and recommendations.
- FIG. 2 shows a flow diagram of an exemplary method 200 for data collection including automatic data collection.
- the method 200 may be used to gather and transmit health data from a provider and/or patient to a service, as shown in step 104 of FIG. 1 .
- Historical health data may be retrieved that is relevant to a provider and the provider's patients ( 202 ).
- historical health data that is relevant to the provider may be gathered.
- Such data may include various provider characteristics including, but not limited to, the provider's type of practice, specialty, age, years of experience, size of practice, location of practice, access to referrals, gender, education, type of training, access to treatments, and/or expertise.
- Historical health data that may be relevant to a patient also may be gathered at step 206 .
- Such data may be retrieved or extracted by parsing patient electronic medical records using a processor. Such parsing may include parsing of clinical data and/or psychological data. A patient's personal information (e.g. age, gender, and education), social information, and or lifestyle characteristics (e.g. diet, and exercise regimen) also may be retrieved.
- the historical data gathered at step 204 and step 206 may be organized in any suitable manner at step 208 may be stored in a database at step 210 .
- FIG. 3 is a flow diagram of an exemplary method 300 for extracting and identifying metadata.
- the metadata is extracted from the collected historical data and/or real-time data in order to rate the value of the data.
- the metadata may be used in step 108 of applying machine-learning algorithms.
- metadata may be extracted in various manners.
- descriptive statistics 302 may be used, which may include the mean, standard deviation, and/or the variance.
- Another type of metadata extraction method may include determining the availability of the historical data at step 304 . For example, it may be determined that a patient's self-monitoring blood glucose (SMBG) levels are only available on a weekly basis; whereas a patient's continuous glucose data is available (CGM) only on Thursdays.
- SMBG self-monitoring blood glucose
- the metadata based on the type of data may be extracted at step 306 , such as location specific models, and weather specific models.
- metadata based on the category type may be determined at step 308 , such as clinical, behavioral, and/or personal.
- location the location where a patient's blood glucose measurement was taken may be extracted and this category of metadata (location) may be used in the decision-making model.
- different decision models may be used to process the measurement if the measurement was taken at the patient's home versus if the measurement was taken was at a restaurant.
- certain decision-support/recommendation may be useful. Hence an appropriate model for such a decision-making may be selected.
- the source of the data also may be extracted at step 310 and the relationship/influence of the source may be determined. For example, it may be determined that the source of a first blood glucose level measurement was a highly accurate hospital device, and the source of a second blood glucose level measurement was a less accurate patient device, and therefore, the first measurement may be designated as having a greater value/be more reliable than the second measurement.
- the type of metadata may be identified at step 312 in any suitable manner, such as by parsing the metadata, and/or a rules engine to the metadata.
- the parsing/rules engine may use appropriate algorithms, such as logic based algorithms, to match data against a reference knowledge base to identify the category of the data. For example, if the data is latitude and longitude coordinates, the parsing/rules engine may be used to match the data against a category called ‘location’. In another example, if the data is had a burger and fries at noon, the parsing/rules engine may be used to match the data against a category called ‘diet’ and/or a category called ‘time’.
- FIG. 4 is a flow diagram of an exemplary method 400 for selecting and applying algorithms to data such as historical data, metadata, and/or real-time data.
- the method 400 may be used in any suitable method, for example, method 100 .
- metadata type may be discovered at step 402 in any suitable manner, for example, using the method 300 shown in FIG. 3 .
- Processing rules may be imported from databases and/or libraries at step 404 in any suitable manner.
- logic processing rules 414
- the applicable processing rules for data conversion based on the discovered metadata type may be determined.
- the data may be processed at step 408 .
- one or more models may be imported from the logic library at step 410 .
- the logic library 416 may include various models, such as category/response models, and/or stochastic models.
- One or more models may be chose for application to the processed data at step 412 and model combinator rules may be imported from a database 420 .
- the database may include model combinator rules 418 , which may include secondary sources and data on multiple diseases.
- the models may be chosen based on the model combinator 422 rules and a recommendation maybe generated from the data 424 .
- FIG. 5 is a flow diagram of an exemplary method 500 for evaluating and modifying an automatic recommendation.
- the method 500 may be used with any suitable method, for example, with method 100 .
- a provider may interact with a computer software application ( 502 ) to evaluate and provide electronic feedback on a recommended presented to the provider by the service at step 504 .
- the recommendation may include a rationale for the recommendation.
- the provider may provider corrective adjustments of the recommendation and/or the rationale at step 508 .
- the recommendation provided to the provider at step 504 may be that the patient have hip surgery and this may be based on rationale that the patient is not a good candidate for pain medication due to a severe allergic reaction to the medication.
- the provider may provide corrective adjustments to the rationale, such as providing that the patient should have hip surgery because the amount of pain the patient is suffering cannot be managed by drugs alone.
- the provider may be presented with a course of action based on an external model that is not based on processing of the provider healthcare data at step 506 .
- the service may recommend that the provider prescribe a new cocktail drug therapy that a recent study showed to be effective in 90% of all patients.
- the provider decision and/or corrective adjustments may be stored in memory.
- FIG. 6 is a flow diagram of an exemplary method 600 for automatically electronically collecting data in real-time.
- the method may include health data received in real-time from the provider 602 .
- provider prescription data 604 which may include newly prescribed, changed medication, and/or halted prescription data.
- the real-time health data also may include data regarding the provider rationale ( 606 ) for making his/her decision, such as the provider's rationale for prescribing the medication, the provider's perception of the medication, the provider's perception of the patient's lifestyle, the provider's perception of the patient's lifestyle, the provider's perception the patient's adherence to the prescription, the provider's perception of the patient's education or understanding of the prescription, the provider's perception of the patient's demographics.
- real-time health data from the patient may be received at step 610 .
- information regarding the provider patient interaction setting 608 maybe received (e.g. hospital setting or at home setting)
- the real-time data may be inputted and/or automatically sent via a software application via the Internet 618 and the data may be stored in digital memory 620 .
- FIG. 7A is a flow diagram of an exemplary method 700 for electronically receiving patient evaluations of decision models.
- the method 700 may be used in any suitable manner, for example, with method 100 for automatic clinical decision-making.
- Method 700 may be used to improve the breadth, customization, and significance of decision models, for example, the decision models generated in method 100 .
- a patient evaluation of one or more decision models may be received at step 702 .
- the evaluation may be received from a patient, such as a self-help patient by the patient interacting with a computer software application presenting clinical decision models at step 704 .
- the patient may be presented with likely courses of action and a rationale for each action. Examples of such presentations may include a medication course of action and rationale for why the medication was recommended, a lifestyle course of action and rationale for why it was recommended, and an education course of action and rationale for why it was recommended.
- the self-help patient may then make a selection at step 708 from one of the recommendations.
- the selection may be electronically stored in memory at step 712 and real-time data may be received from the self-help patient at step 710 .
- the real-time data and stored decision may be processed, for example, as shown in method 100 , to improve the models and model selections.
- a treatment plan may be generated for the self-help patient at step 714 for on-going heath-management.
- FIG. 7B is a flow a flow diagram of an exemplary method 750 for electronically presenting clinical decision model to a provider and a patient.
- a clinical decision model may be generated at step 754 in any suitable manner, such as in the manner described in step 110 .
- the provider may be presented with a clinical scenario at step 756 (e.g. a patient with high cholesterol).
- the provider may communicate the scenario, such as a clinical scenario to the service at step 758 .
- the provider may receive a recommendation from the service at step 760 along with a rationale for the recommendation.
- the recommendation may be generated in any suitable manner, such as in the manner described in step 114 .
- the provider may evaluate the recommendations at 762 and send the evaluation to the service.
- a self-help patient may be presented with a clinical scenario or symptoms (e.g., a diabetes patient may have symptoms of fatigue and headaches) and may communicate such symptoms to the service.
- the self-help patient may receive a recommendation and rationales for the recommendations from the service for evaluation.
- the patient may select one of the recommendations and may provide an evaluation of the recommendation at step 766 .
- An internal medicine physician may register with a web-based provider of clinical recommendations. During registration, the physician may provide her personal information, such as:
- the service provider may store this data and continuously receive physician data and the physician's patient's data over a period of time, thereby collecting and storing historical data on the provider's practice.
- the historical data may be continuously processed using algorithms, such as machine learning algorithms, to determine any patterns.
- the service may notify the provider that she has prescribed antibiotics to 40% of her patient's in the last week. This may indicate to the provider that there is a bacterial infection outbreak in her patient population and that she should recommend all her patients to take preventative measures to avoid being infected.
- the decision models may be generated based on the processed data and real-time data may be continuously received (e.g. the date, temperature, and physician workload).
- the service may indicate to the physician that it has obtained a sufficient amount of historical data to provide a clinical recommendation by sending her an email notification.
- the physician may then decide to receive a recommendation from the service and submit a clinical scenario to the service of a patient—
- the service may retrieve historical data on the patient indicating that he has a family history of diabetes and heart disease, is taking cholesterol medication, suffered a stroke 4 years ago, has a high-stress lifestyle, and eats cake the first Friday of every month.
- the service also may receive real-time data on the patient indicating that the patient exercises regularly, eats a healthy diet, but has minimal social interaction and receives less than five hours of sleep every night, and has been late in making his credit card payments three months in a row.
- the service also may identify patterns in the provider's historical data indicating that she rarely prescribes blood pressure medication and often instructs patients in the patient's age range to change their diet and exercise.
- Data also may be received from external sources that indicates that patients who are 50-60 and who live in New York City have a 90% adherence rate to blood pressure lowering medication.
- the service also may receive real-time data from the provider indicating that she has recently authored a research article on the benefits of avoiding carbohydrates for diabetes patients.
- the service may process the historical and real-time data and provide the physician a recommendation and its rationale based on what is determined to be the physician's likely recommendation:
- the patient has a family history of heart disease and diabetes and already exercises and has a healthy diet, therefore lifestyle change may not be effective.
- the service may provide a recommendation based on the American Medical Association, and a recommendation based on all other data sources. The physician may select the recommendation and/or provide feedback on the recommendations that may be saved by the service as historical data.
- the physician of Example 1 may receive a patient report on the patient of Example 1 prior to the patient's next visit. Prior to the visit the service may provide a report to the physician and a recommendation based on historical and real-time data:
- the patient's blood glucose and blood pressure levels have decreased.
- the patient has been coughing, and sneezing and has back pain.
- the service may provide a recommendation based on the American Medical Association, and a recommendation based on all other data sources. The physician may decide to follow the recommendation in part, but halt the medication and provide feedback on the recommendations that may be saved by the service as historical data.
- FIG. 8 is a schematic diagram of an arrangement of a system 800 by which a clinical decision may be automatically generated, according to an exemplary embodiment of the present disclosure.
- the system 800 may access decision models stored on a decision model database 870 via a network 805 , such as the Internet.
- the retrieved decision models may be used for display and/or processing by one or more provider and/or patient devices 810 , such as a mobile device 815 (e.g., mobile phone, personal digital assistant, tablet computer), tablet device 820 , a computer (laptop, desktop) 425 , kiosk 830 (e.g. kiosk at pharmacy, clinic or hospital having medical and/or prescription information), and/or any device connected to a network 805 , such as the Internet, according to an exemplary embodiment of the present disclosure.
- a mobile device 815 e.g., mobile phone, personal digital assistant, tablet computer
- tablet device 820 e.g., a computer (laptop, desktop) 425
- kiosk 830 e.g. kiosk at pharmacy
- mobile electronic device 815 may be a smartphone, a personal digital assistant (“PDA”), medical diagnostic device, or other type of mobile computing device, such as a device having a touchscreen display.
- Mobile device 815 , tablet 820 , and computer 825 each may be equipped with or include, for example, a GPS receiver for obtaining and reporting location information, e.g., GPS data, via network 805 to and from any of servers 835 and/or one or more GPS satellites 855 .
- location information e.g., GPS data
- each of user devices 810 may be implemented using any type of electronic device configured to send and receive data (e.g. clinical information) to and from a system of servers 835 over network 805 .
- the user input device(s) may include any type or combination of input/output devices, such as a display monitor, touchpad, touchscreen, microphone, camera, keyboard, and/or mouse.
- the various user devices 810 may also communicate with each other by any suitable means (e.g., via Wi-Fi, radio frequency (RF), infrared (IR), Bluetooth, Near Field Communication, or any other suitable means) to send and receive location and other information.
- a mobile device 815 may communicate with tablet device 820 or kiosk 830 .
- the user device 810 may receive information, such clinical data via the network 805 from the system of servers 835 , having one or more servers such as clinical data servers 840 , algorithm servers 845 , user interface servers 850 , and/or any other suitable servers.
- Each server may access the decision model database 870 to retrieve decision models.
- Each server may include memory, a processor, and/or a database.
- the clinical data server 840 may have a processor configured to retrieve clinical data from a provider's database and/or a patient's electronic medical record.
- the algorithm server 845 may have a database that includes various algorithms, and a processor configured to process the clinical data.
- the user interface server 850 may be configured to receive and process user input, such as clinical decision preferences.
- the satellite 855 may be configured to send and receive information to the server system 835 and user devices 810 .
- the clinical data server 840 may receive clinical data, such as data regarding the provider and the patient from the user device 810 via the network 805 or indirectly via the user interface server 850 .
- the clinical data server 840 may save the information in memory, such as a computer readable memory.
- the clinical data server 840 also may be in communication with one or more other servers, such as the algorithm server 845 and/or external servers such as servers of providers 860 and/or patients 865 (e.g. medical records servers).
- the servers may include data about provider preferences, and/or patient health history.
- the clinical data server 860 may include data from other providers and/or patients.
- the algorithm server 845 may include machine learning, and/or other suitable algorithms.
- the algorithm server 845 may be in communication with other external servers and may be updated as desired. For example, the algorithm server 845 may be updated with new algorithms, more powerful programming, and/or more data.
- the clinical data server 840 and/or the algorithm server 845 may process the information and transmit data to the model server 870 for processing.
- Each server in the system of servers 835 may each represent any of various types of servers including, but not limited to a web server, an application server, a proxy server, a network server, or a server farm.
- Each server in the system of servers 835 may be implemented using, for example, any general-purpose computer capable of serving data to other computing devices including, but not limited to, user devices 810 or any other computing device (not shown) via network 805 .
- Such a general-purpose computer can include, but is not limited to, a server device having a processor and memory for executing and storing instructions.
- the memory may include any type of random access memory (RAM) or read-only memory (ROM) embodied in a physical storage medium, such as magnetic storage including floppy disk, hard disk, or magnetic tape; semiconductor storage such as solid-state disk (SSD) or flash memory; optical disc storage; or magneto-optical disc storage.
- Software may include one or more applications and an operating system.
- Hardware can include, but is not limited to, a processor, memory, and graphical user interface display. Each server also may have multiple processors and multiple shared or separate memory components that are configured to function together within, for example, a clustered computing environment or server farm.
- FIG. 9 is a simplified functional block diagram of a computer that may be configured as a host server, for example, to function as healthcare provider decision-making server.
- FIG. 9 illustrates a network or host computer platform 900 , as may typically be used to implement a server like the clinical decision model server 870 . It is believed that those skilled in the art are familiar with the structure, programming, and general operation of such computer equipment and as a result, the drawings should be self-explanatory.
- a platform for a server 900 or the like may include a data communication interface for packet data communication 960 .
- the platform also may include a central processing unit (CPU) 920 , in the form of one or more processors, for executing program instructions.
- the platform typically includes an internal communication bus 910 , program storage, and data storage for various data files to be processed and/or communicated by the platform such as ROM 930 and RAM 940 or the like.
- the hardware elements, operating systems, and programming languages of such equipment are conventional in nature, and it is presumed that those skilled in the art are adequately familiar therewith.
- the server 900 also may include input and output ports 950 to connect with input and output devices such as keyboards, mice, touchscreens, monitors, displays, etc., and communication ports 960 .
- the various server functions may be implemented in a distributed fashion on a number of similar platforms to distribute the processing load.
- the servers may be implemented by appropriate programming of one computer hardware platform.
- Storage type media include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives and the like, which may provide non-transitory storage at any time for the software programming. All or portions of the software may at times be communicated through the Internet or various other telecommunication networks.
- Such communications may enable loading of the software from one computer or processor into another, for example, from a management server or host computer of the mobile communication network into the computer platform of a server and/or from a server to the mobile device.
- another type of media that may bear the software elements includes optical, electrical and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links.
- the physical elements that carry such waves, such as wired or wireless links, optical links, or the like, also may be considered as media bearing the software.
- terms such as computer or machine “readable medium” refer to any medium that participates in providing instructions to a processor for execution.
Abstract
Description
- This Application claims the benefit of U.S. Provisional Application No. 61/839,528, entitled “Systems and Methods for Managing Patient Conditions”, filed Jun. 26, 2013, the disclosure of which is incorporated herein by reference in its entirety.
- The present disclosure relates generally to providing recommendations based on receiving and processing historical data. More specifically, the present disclosure relates to systems and methods for learning decision-making and providing recommendations based on the learned decision-making. In some embodiments, the recommendation may be made automatically.
- Increased healthcare costs have limited patient access to appropriate care. At the same time, healthcare companies have increased provider workloads and limited physician-patient interactions. This in turn may lead to improper patient assessments and treatment. In an attempt to increase physician productivity and improve the accuracy of patient assessments, methods have been attempted to implement clinical rules and validated mathematical/statistical models based on patient diagnostic information. Some conventional methods provide patient assessment reports prior to a patient's next physician visit. These reports include data submitted by patients, such as daily blood glucose levels, dietary intake, etc. However, such methods do not provide an analysis of the data and/or or recommendations tailored to the patient and/or based on the healthcare provider's characteristics and preferences.
- Thus, a need exists for improved systems and methods for increasing healthcare provider productivity, accurately assessing a patient, and providing patient treatment consistent with the healthcare provider's treatment style and/or decision-making characteristics.
- Embodiments of the present disclosure relate to, among other things, methods and systems for providing a treatment recommendation. Each of the embodiments disclosed herein may include one or more of the features described in connection with any of the other disclosed embodiments.
- According to certain embodiments, computer-implemented methods are disclosed for automatically providing a treatment recommendation, the method may include receiving historical data comprising at least one of provider data and patient data; processing, using a processor, the historical data to identify one or more patterns; generating one or more decision models from the historical data and the decision patterns; and providing one or more recommendations based on the one or more decision models.
- Aspects of the method may include one or more of the following: further comprising receiving electronic feedback on at least one of the one or more recommendations; further comprising storing the electronic feedback as historical data; further comprising exchanging the electronic feedback with a third party; further comprising receiving real-time data comprising at least one of provider data and patient data; wherein the historical data comprises treatment instructions and the real-time data comprises compliance with the treatment instructions; wherein the real-time data is received from a patient's electronic device; further comprising extracting metadata from the historical data; further comprising biasing the historical data based on the metadata; wherein the processor uses one or more machine learning algorithms; wherein the generating one or more decision models comprises importing models from a library of models; further comprising accessing one or more medical records and parsing the historical data from the one or more medical records; further comprising presenting the one or more identified patterns to a provider; further comprising receiving instructions to modify the one or more decision models; further comprising providing a comparison between the one or more recommendations, a recommendation based on standard guidelines, and a recommendation based on external data; and wherein one of the patient data and provider data comprises demographic information.
- In another aspect, disclosed is an information processing device for providing a treatment recommendation, the device may include a processor for processing a set of instructions, and a computer-readable storage medium for storing the set of instructions, wherein the instructions, when executed by the processor, perform a method comprising receiving historical data comprising at least one of provider data and patient data; processing, using a processor, the historical data to identify one or more patterns; generating one or more decision models from the historical data and the decision patterns; and providing one or more recommendations based on the one or more decision models.
- The processing device may include one or more of the following features: the method further comprising receiving electronic feedback on at least one of the one or more recommendations; and the method further comprising further comprising receiving real-time data comprising at least one of provider data and patient data.
- In another aspect, disclosed is a non-transitory computer-readable medium storing a set of instructions that, when executed by a processor, may perform a method of providing a treatment recommendation, the method may include receiving historical data comprising at least one of provider data and patient data; processing, using a processor, the historical data to identify one or more patterns; generating one or more decision models from the historical data and the decision patterns; and providing one or more recommendations based on the one or more decision models.
- It may be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the invention, as claimed.
- The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the present disclosure and together with the description, serve to explain the principles of the disclosure.
-
FIG. 1 is flow diagram of an exemplary method for clinical decision-making, according to an exemplary embodiment of the present disclosure; -
FIG. 2 is a flow diagram of an exemplary method for data collection, according to an exemplary embodiment of the present disclosure; -
FIG. 3 is a flow diagram of an exemplary method for extracting and identifying metadata, according to an exemplary embodiment of the present disclosure; -
FIG. 4 is a flow diagram of an exemplary method for selecting and applying algorithms to data, according to an exemplary embodiment of the present disclosure; -
FIG. 5 is a flow diagram of an exemplary method for evaluating and modifying a recommendation, according to an exemplary embodiment of the present disclosure; -
FIG. 6 is a flow diagram of an exemplary method for collecting data, according to an exemplary embodiment of the present disclosure; -
FIG. 7A is flow diagram an exemplary method for electronically selecting a recommendation, according to an exemplary embodiment of the present disclosure; -
FIG. 7B is a flow a flow diagram of an exemplary method for electronically presenting a clinical decision, model to a provider and a patient, according to an exemplary embodiment of the present disclosure; -
FIG. 8 is a schematic diagram of an arrangement by which a clinical decision may be generated, according to an exemplary embodiment of the present disclosure; and -
FIG. 9 is a simplified functional block diagram of a computer that may be configured as a host server, for example, to function as healthcare provider decision-making server, according to an exemplary embodiment of the present disclosure. - The present disclosure is drawn to systems and methods for providing recommendations based on analyzing past decisions. More specifically, the present disclosure relates to systems and methods for analyzing historical data to learn provider decision-making, applying machine learning algorithms to generate decision models, and providing (e.g. automatically) recommendations on subsequent scenarios based on the learned decision-making.
-
FIG. 1 is a flow diagram of an exemplary method for providing atreatment recommendation 100. In some embodiments, the depictedmethod 100 may be used for automatic clinical decision-making. As shown inFIG. 1 , a healthcare provider (the provider), such as a physician, dentist, physical therapist, psychologist, and/or other healthcare professional may register with a service provider to receive automatic recommendations for treating apatient 102 in any suitable manner. For example, the healthcare provider may electronically communicate with a service providing clinical recommendations (the service) to indicate interest in receiving clinical recommendations. The electronic communication may be via an internal or external network, such as via the Internet and/or any other electronic network. In some embodiments, the electronic communication may be via a wired or a wireless network (e.g. Wi-Fi, Blue Tooth, and/or near field communication). During registration, the provider may provide relevant information to the service, such as billing information, type of healthcare practice (e.g. pediatric, psychiatry, internal medicine, and/or surgical), and/or information about the provider's practice and preferences (e.g. proponent of surgical intervention, proponent of alternative medical therapies such as yoga and meditation). In some examples, the service may provide confirmation of registration and/or request further information from the provider to complete registration in any suitable manner. The service also may provide the provider with materials to access its services, for example by providing a software application (such as a mobile application) having a graphical user interface (GUI) and/or codes to access restricted web-sites. In some examples, the software application may allow the provider to view, transmit, and receive information to and from the service via the GUI. The provider may designate any preferences to the service during theregistration step 102 and/or any other time. For example, the provider may indicate, via the GUI, that the service should only be used for patients who have a blood glucose level above, e.g. 130 mg/dL. In some examples, the service may provide programming, such as software applications, that may be integrated with existing provider programming. For example, the programming (e.g. a software application) provided by the service may be integrated/compatible or otherwise able to communicate with the provider's programming for electronic medical records, electronic billing, and electronic scheduling. The provider also may instruct that the service to provide selective access to patient's. For example, duringregistration 102 or at any other time, the provider may allow a patient to selectively view information provided by the service and allow the patient to submit relevant patient data to the service, either selectively or automatically (e.g. via automatic updates from a patient's electronic device). In one embodiment, the provider may allow a patient to download the service's software application to the patients electronic device and allow the patient to submit data to the service via the electronic device (e.g. a mobile device which may have a built in blood glucose monitor or heart rate monitor) either through wired of wireless communication. - Historical health data may be received by the service that is relevant to the provider and the provider's patients. This data may be electronically transmitted by the provider and/or the patient and received by the service at
step 104. The data may be electronically transmitted and received by the service atstep 104 in any suitable manner. For example, the provider may access the software application or secure server and send or drop electronic data files via a network, e.g. the Internet so that the files may be accessed by the service. In some examples, the provider may allow the service limited access in compliance with any healthcare privacy regulations and other applicable regulations, to any electronic medical records, patient prescription records, referral records, etc., and the service may electronically retrieve healthcare data from such electronic records (e.g. automatically). In other examples, patient data may be electronically transmitted by a patient and may be electronically received by the service in any suitable manner. The patient data may be actively submitted by the patient via a software application and/or may be automatically electronically retrieved by the service from an electronic device of the patient (FIG. 2 ) that may measure patient health values, such as heart rate, blood glucose, blood oxygen, blood pressure, activity, stress, mood, and/or sleep either periodically or continuously. - The historical data received at
step 104 may include any relevant historical data, including a clinical profile of the patient such as diseases, significant medical events (e.g. heart attack, stroke, head trauma, transplant), disease stage, lab values, patient self-reported clinical, behavioral and psycho-social data, patient's demographics, medical history, provider characteristics such as age, years of clinical practice experience, size of practice, specialty, demographics, context of a patient's visit such as date, day, time, location, duration of visit, and/or a decision which includes medication change, psycho-therapy, dose change, lifestyle modification (diet, exercise, weight loss), recommendation for lab test(s), education, and may include the reasoning behind the provider's decision(s). - The historical data received by the service at
step 104 may be stored in a database atstep 106 such as a server, cloud, or any other digital memory device. The data may be accessed at any time by the service and may be displayed, printed, or updated in any suitable manner. The stored data may be organized and accessed in any suitable manner. In some examples, the data may be electronically tagged with various identifiers, such as age, gender, clinical condition, etc. In another example, metadata may be extracted from the stored data (FIG. 3 ). - In addition, the data stored in the database at
step 106 may be electronically processed in any suitable manner. Instep 108, for example, various algorithms may be applied to the data to learn from/be trained by analyzing the data. In some examples, machine learning algorithms and/or other higher-level algorithms (e.g. supervised and unsupervised learning algorithms) may be applied to the data to learn and otherwise extract information from the data, such as for use in learning provider decision-making patterns and behaviors and/or patient behavioral patterns. Examples of such machine learning algorithms may include artificial neural networks, Bayesian statistics, case-based reason, decision trees, inductive logic processing, Gaussian process regression, Gene expression programming, Logistic model trees, stochastic modeling, statistical modeling (e.g. Bayesian networks, Markov models, ANOVA, etc.), and/or any other suitable algorithm or combinations of algorithms. For example, atstep 108, machine-learning algorithms may be applied to the data to learn the characteristics of patients for which the provider has prescribed or modified use of a drug, provided a referral to another provider, recommended a lifestyle change (e.g. exercise, diet, and/or stress management). - The machine learning algorithms applied at
step 108 may detect any patterns, idiosyncrasies, or any other significant associations that may be used in generating a decision model that mimics or attempts to understand the decision-making of the provider and/or predicted behavior of the patient. In another example, the machine-learning algorithm may identify a patient cohort for whom components of a treatment plan may be effective, ineffective, or partially effective, such as a cholesterol-lowering drug that is ineffective for patients with neuropathy. In some embodiments, any patterns identified instep 108 may be presented to the provider to improve the provider's clinical knowledge. For example, it may be determined atstep 108 that 83% of the provider's diabetes patients between ages 65-75 for whom the provider prescribed dementia drug X suffered headaches, and only 3% of the provider's patients adhered to a diet change. Based on these patterns the provider may stop prescribing drug X to patients between ages 65-75 and stop recommending a diet change to patients ages 18-35. In another embodiments, the machine learning algorithm applied atstep 108 may detect patient compliance with the provider's treatment plan, for example, it may be determined that 90% of the provider's patients over the age of 85 did not adhere to taking dementia drug X. - The application of the one or more machine learning algorithms at
step 108 may be processed to generate clinical decision models atstep 110. The models may be based on any patterns or other information learned by the machine learning algorithms. The models may be generated using one or more processors and may be tested with sample data that may be reviewed and automatically validated. In some embodiments, existing models may be imported from databases or libraries, processed, and applied to the data processed atstep 108. In some embodiments, atstep 110, the service may send the provider a notification that it is ready to provide clinical recommendations. The notification may be sent when it is determined sufficient data has been collected to provide an accurate recommendation. In some embodiments, the notification may be sent after a day, a week, a month, three months, or any other period of time. The notification may be in any suitable form, e.g. an electronic message, alert, and/or phone call. - The service may receive information in connection with a clinical scenario at 112, for example, from the provider, in any suitable manner (e.g. via a software application over the Internet). In some embodiments, the clinical scenario may be associated with an upcoming patient appointment, a current patient appointment, or a past patient visit. The service may process the information received in connection with the clinical scenario in any suitable manner. The clinical scenario may be submitted to the service directly by the provider or a proxy of the provider. For example, a patient may visit a physician's office and provide a nurse with information regarding the patient's reason for the visit, (e.g. onset of frequent migraines), and the nurse may record the patient's diagnostic information (e.g. weight, blood pressure, blood glucose level, and heart rate), and submit a recommendation request to the service on behalf of the physician.
- Real-time data may be received at 118 after generating the
decision models 110 or any time duringmethod 100. The real-time data may include any relevant patient and/or provider information that may be used to generate the decision model or to improve the decision model. In some embodiments, real-time data may include behavioral data, demographic data, and financial data. The real-time data may be selectively collected or continuously collected from the provider and patients. The real-time data also may be obtained that is non-specific to the provider and/or the patient, such as weather conditions, current events, date, and/or season. This non-specific real-time data may be used to improve the accuracy the recommendation, for example, if the real-time data indicates that the temperatures for the last ten days where the patient lives have been below −10 degrees Fahrenheit, the service may not recommend that a patient start exercising outside as it may be too cold to exercise outside. In some examples, if the service is unable to complete a decision model, real-time data may be requested to complete or improve the decision model. - In some examples,
step 114 may include automatically or upon provider selection, applying one or more of the decision models to the clinical scenario received atstep 112 and/or extracting discrete data values from the clinical scenario and applying the decision models to each data value separately, and then combining the decision models. For example, the clinical scenario may include a patient who is a 67-year old male smoker that has type-2 diabetes, and has previously suffered a stroke. The patient may visit the provider complaining of shortness of breath. In addition, the patient may be receptive to lifestyle changes and the provider may indicate resistance to trying new drug therapies. One or more models may be applied to each the clinical scenario data values (e.g., patient age, diagnostic information, behavioral values, provider characteristics). In addition, or alternatively, all of the clinical scenario data values may be treated together and one or more models may be applied to all or subgroups of the data values. The results of applying the decision models may be further processed to detect any inconsistencies and/or errors and may be presented to the provider as a recommendation in any suitable manner for evaluation. For example, the recommendation may include a recommendation based on applying the machine learning data algorithms atstep 108 to learn the provider's decision-making characteristics and application of the decision models. In addition, the recommendations may include recommendations based on other provider decision-making characteristics, recommendations based on standard guidelines (e.g. according to the American Diabetes Association, American Medical Association, etc.), and/or any other sources. The service may provide a comparison of each of the recommendations and also may suggest any changes in the provider's decision-making to improve patient treatment, reduce healthcare costs, etc. In some embodiments, the service may provide a rationale for each recommendation. - At
step 116, the service may receive electronic feedback on the recommendation. The feedback may be in the form of an evaluation by the provider and/or the patient on the recommendation. In some examples, an evaluation form soliciting feedback on the recommendation may be sent by the service for completion by the provider and/or patient. The evaluation may include an indication of whether or not the recommendation was followed, a rating of the recommendation, an explanation of the why the recommendation was followed or why it was not followed. In this manner, the patient may receive a treatment plan that is tailored to the patient and the provider may quickly and easily provide a treatment plan that is in line with provider's standard of care and philosophy. - The provider's decision may be recorded at
step 120 and may be stored as historical data for use in subsequent recommendations. Atstep 122, the provider's recommendation may be presented to the user in any suitable manner. In some embodiments the results of the provider's decision and/or other provider decision's may be saved and exchanged (e.g. sold and/or exchanged for other data) to a third party without including any patient identifying data. For example, a pharmaceutical company may purchase data from the service on provider decisions in order to improve marketing and research and development efforts. In another example, health insurance companies may be interested in the provider decision data to improve healthcare services and reduce costs. The provider decision data also may be provided to improve standard treatment guidelines and evaluate provider adherence to standard guidelines and recommendations. -
FIG. 2 shows a flow diagram of anexemplary method 200 for data collection including automatic data collection. Themethod 200 may be used to gather and transmit health data from a provider and/or patient to a service, as shown instep 104 ofFIG. 1 . Historical health data may be retrieved that is relevant to a provider and the provider's patients (202). Atstep 204, historical health data that is relevant to the provider may be gathered. Such data may include various provider characteristics including, but not limited to, the provider's type of practice, specialty, age, years of experience, size of practice, location of practice, access to referrals, gender, education, type of training, access to treatments, and/or expertise. Historical health data that may be relevant to a patient also may be gathered atstep 206. Such data may be retrieved or extracted by parsing patient electronic medical records using a processor. Such parsing may include parsing of clinical data and/or psychological data. A patient's personal information (e.g. age, gender, and education), social information, and or lifestyle characteristics (e.g. diet, and exercise regimen) also may be retrieved. The historical data gathered atstep 204 and step 206 may be organized in any suitable manner atstep 208 may be stored in a database atstep 210. -
FIG. 3 is a flow diagram of anexemplary method 300 for extracting and identifying metadata. In some examples, the metadata is extracted from the collected historical data and/or real-time data in order to rate the value of the data. The metadata may be used instep 108 of applying machine-learning algorithms. As shown inFIG. 3 , metadata may be extracted in various manners. For example,descriptive statistics 302 may be used, which may include the mean, standard deviation, and/or the variance. Another type of metadata extraction method may include determining the availability of the historical data atstep 304. For example, it may be determined that a patient's self-monitoring blood glucose (SMBG) levels are only available on a weekly basis; whereas a patient's continuous glucose data is available (CGM) only on Thursdays. The metadata based on the type of data may be extracted atstep 306, such as location specific models, and weather specific models. In addition, metadata based on the category type may be determined at step 308, such as clinical, behavioral, and/or personal. For example, the location where a patient's blood glucose measurement was taken may be extracted and this category of metadata (location) may be used in the decision-making model. In this example, different decision models may be used to process the measurement if the measurement was taken at the patient's home versus if the measurement was taken was at a restaurant. Based on the appropriate data category (such as a patient's location) certain decision-support/recommendation may be useful. Hence an appropriate model for such a decision-making may be selected. - The source of the data also may be extracted at
step 310 and the relationship/influence of the source may be determined. For example, it may be determined that the source of a first blood glucose level measurement was a highly accurate hospital device, and the source of a second blood glucose level measurement was a less accurate patient device, and therefore, the first measurement may be designated as having a greater value/be more reliable than the second measurement. - The type of metadata may be identified at
step 312 in any suitable manner, such as by parsing the metadata, and/or a rules engine to the metadata. The parsing/rules engine may use appropriate algorithms, such as logic based algorithms, to match data against a reference knowledge base to identify the category of the data. For example, if the data is latitude and longitude coordinates, the parsing/rules engine may be used to match the data against a category called ‘location’. In another example, if the data is had a burger and fries at noon, the parsing/rules engine may be used to match the data against a category called ‘diet’ and/or a category called ‘time’. -
FIG. 4 is a flow diagram of anexemplary method 400 for selecting and applying algorithms to data such as historical data, metadata, and/or real-time data. Themethod 400 may be used in any suitable method, for example,method 100. As shown inFIG. 4 , metadata type may be discovered atstep 402 in any suitable manner, for example, using themethod 300 shown inFIG. 3 . Processing rules may be imported from databases and/or libraries atstep 404 in any suitable manner. For example, logic processing rules (414), which may include simple logic, algorithmic logic, machine learning models, and/or mathematical models, may be imported. Atstep 406, the applicable processing rules for data conversion based on the discovered metadata type may be determined. The data may be processed atstep 408. Based on the processing rules, one or more models may be imported from the logic library atstep 410. Thelogic library 416 may include various models, such as category/response models, and/or stochastic models. One or more models may be chose for application to the processed data atstep 412 and model combinator rules may be imported from adatabase 420. For example, the database may include model combinator rules 418, which may include secondary sources and data on multiple diseases. The models may be chosen based on themodel combinator 422 rules and a recommendation maybe generated from thedata 424. -
FIG. 5 is a flow diagram of anexemplary method 500 for evaluating and modifying an automatic recommendation. Themethod 500 may be used with any suitable method, for example, withmethod 100. Inmethod 500, a provider may interact with a computer software application (502) to evaluate and provide electronic feedback on a recommended presented to the provider by the service atstep 504. The recommendation may include a rationale for the recommendation. The provider may provider corrective adjustments of the recommendation and/or the rationale atstep 508. For example, the recommendation provided to the provider atstep 504 may be that the patient have hip surgery and this may be based on rationale that the patient is not a good candidate for pain medication due to a severe allergic reaction to the medication. In this example, the provider may provide corrective adjustments to the rationale, such as providing that the patient should have hip surgery because the amount of pain the patient is suffering cannot be managed by drugs alone. In some aspects, the provider may be presented with a course of action based on an external model that is not based on processing of the provider healthcare data atstep 506. For example, the service may recommend that the provider prescribe a new cocktail drug therapy that a recent study showed to be effective in 90% of all patients. Atstep 510, the provider decision and/or corrective adjustments may be stored in memory. -
FIG. 6 is a flow diagram of anexemplary method 600 for automatically electronically collecting data in real-time. The method may include health data received in real-time from theprovider 602. For example,provider prescription data 604, which may include newly prescribed, changed medication, and/or halted prescription data. The real-time health data also may include data regarding the provider rationale (606) for making his/her decision, such as the provider's rationale for prescribing the medication, the provider's perception of the medication, the provider's perception of the patient's lifestyle, the provider's perception of the patient's lifestyle, the provider's perception the patient's adherence to the prescription, the provider's perception of the patient's education or understanding of the prescription, the provider's perception of the patient's demographics. At the same time or any other time, real-time health data from the patient may be received atstep 610. For example, updates of medical records (612) (clinical data and prescription data) andpatient lifestyle information 614 from various electronic monitoring devices, and/or the patient's psychosocial well-being data (616) such as the patient's outlook, feelings, and/or financial data. In addition, information regarding the provider patient interaction setting 608 maybe received (e.g. hospital setting or at home setting) The real-time data may be inputted and/or automatically sent via a software application via theInternet 618 and the data may be stored indigital memory 620. -
FIG. 7A is a flow diagram of anexemplary method 700 for electronically receiving patient evaluations of decision models. Themethod 700 may be used in any suitable manner, for example, withmethod 100 for automatic clinical decision-making.Method 700 may be used to improve the breadth, customization, and significance of decision models, for example, the decision models generated inmethod 100. - As shown in
FIG. 7A , a patient evaluation of one or more decision models may be received atstep 702. The evaluation may be received from a patient, such as a self-help patient by the patient interacting with a computer software application presenting clinical decision models atstep 704. For example instep 706, the patient may be presented with likely courses of action and a rationale for each action. Examples of such presentations may include a medication course of action and rationale for why the medication was recommended, a lifestyle course of action and rationale for why it was recommended, and an education course of action and rationale for why it was recommended. The self-help patient may then make a selection atstep 708 from one of the recommendations. The selection may be electronically stored in memory atstep 712 and real-time data may be received from the self-help patient atstep 710. The real-time data and stored decision may be processed, for example, as shown inmethod 100, to improve the models and model selections. In some embodiments, a treatment plan may be generated for the self-help patient atstep 714 for on-going heath-management. -
FIG. 7B is a flow a flow diagram of anexemplary method 750 for electronically presenting clinical decision model to a provider and a patient. As shown inFIG. 7B , a clinical decision model may be generated atstep 754 in any suitable manner, such as in the manner described instep 110. The provider may be presented with a clinical scenario at step 756 (e.g. a patient with high cholesterol). The provider may communicate the scenario, such as a clinical scenario to the service atstep 758. The provider may receive a recommendation from the service atstep 760 along with a rationale for the recommendation. The recommendation may be generated in any suitable manner, such as in the manner described instep 114. The provider may evaluate the recommendations at 762 and send the evaluation to the service. - In addition, or alternatively, a self-help patient may be presented with a clinical scenario or symptoms (e.g., a diabetes patient may have symptoms of fatigue and headaches) and may communicate such symptoms to the service. The self-help patient may receive a recommendation and rationales for the recommendations from the service for evaluation. The patient may select one of the recommendations and may provide an evaluation of the recommendation at
step 766. - An internal medicine physician may register with a web-based provider of clinical recommendations. During registration, the physician may provide her personal information, such as:
-
Age: 43 No. of patients: 150 Ages: 18-35: 40 36-50: 50 51-75: 40 75+: 20 Gender: Female Specialized Training: Fellowship in endocrinology; acupuncture training Years of Practice: 18 Location: New York City Practice type: Academic Hospital
The service provider may store this data and continuously receive physician data and the physician's patient's data over a period of time, thereby collecting and storing historical data on the provider's practice. The historical data may be continuously processed using algorithms, such as machine learning algorithms, to determine any patterns. The service may notify the provider that she has prescribed antibiotics to 40% of her patient's in the last week. This may indicate to the provider that there is a bacterial infection outbreak in her patient population and that she should recommend all her patients to take preventative measures to avoid being infected. The decision models may be generated based on the processed data and real-time data may be continuously received (e.g. the date, temperature, and physician workload). The service may indicate to the physician that it has obtained a sufficient amount of historical data to provide a clinical recommendation by sending her an email notification. The physician may then decide to receive a recommendation from the service and submit a clinical scenario to the service of a patient— - Weight: 200 pounds
Random Blood glucose levels: High - The service may retrieve historical data on the patient indicating that he has a family history of diabetes and heart disease, is taking cholesterol medication, suffered a stroke 4 years ago, has a high-stress lifestyle, and eats cake the first Friday of every month. The service also may receive real-time data on the patient indicating that the patient exercises regularly, eats a healthy diet, but has minimal social interaction and receives less than five hours of sleep every night, and has been late in making his credit card payments three months in a row. The service also may identify patterns in the provider's historical data indicating that she rarely prescribes blood pressure medication and often instructs patients in the patient's age range to change their diet and exercise. Data also may be received from external sources that indicates that patients who are 50-60 and who live in New York City have a 90% adherence rate to blood pressure lowering medication. The service also may receive real-time data from the provider indicating that she has recently authored a research article on the benefits of avoiding carbohydrates for diabetes patients. The service may process the historical and real-time data and provide the physician a recommendation and its rationale based on what is determined to be the physician's likely recommendation:
- Prescribe blood pressure medication and diabetes medication and modify diet to reduce carbohydrate intake.
- The patient has a family history of heart disease and diabetes and already exercises and has a healthy diet, therefore lifestyle change may not be effective.
In addition, the service may provide a recommendation based on the American Medical Association, and a recommendation based on all other data sources. The physician may select the recommendation and/or provide feedback on the recommendations that may be saved by the service as historical data. - The physician of Example 1 may receive a patient report on the patient of Example 1 prior to the patient's next visit. Prior to the visit the service may provide a report to the physician and a recommendation based on historical and real-time data:
- Reduce strength of prescription of medication, prescribe antibiotics, and muscle relaxers.
- The patient's blood glucose and blood pressure levels have decreased. The patient changed his diet, increased his exercise regime, and has moved to the beach. In addition, the patient has been coughing, and sneezing and has back pain.
In addition, the service may provide a recommendation based on the American Medical Association, and a recommendation based on all other data sources. The physician may decide to follow the recommendation in part, but halt the medication and provide feedback on the recommendations that may be saved by the service as historical data. -
FIG. 8 is a schematic diagram of an arrangement of asystem 800 by which a clinical decision may be automatically generated, according to an exemplary embodiment of the present disclosure. For example, thesystem 800 may access decision models stored on adecision model database 870 via anetwork 805, such as the Internet. The retrieved decision models may be used for display and/or processing by one or more provider and/orpatient devices 810, such as a mobile device 815 (e.g., mobile phone, personal digital assistant, tablet computer),tablet device 820, a computer (laptop, desktop) 425, kiosk 830 (e.g. kiosk at pharmacy, clinic or hospital having medical and/or prescription information), and/or any device connected to anetwork 805, such as the Internet, according to an exemplary embodiment of the present disclosure. - In the example shown in
FIG. 8 , mobileelectronic device 815 may be a smartphone, a personal digital assistant (“PDA”), medical diagnostic device, or other type of mobile computing device, such as a device having a touchscreen display.Mobile device 815,tablet 820, andcomputer 825 each may be equipped with or include, for example, a GPS receiver for obtaining and reporting location information, e.g., GPS data, vianetwork 805 to and from any ofservers 835 and/or one ormore GPS satellites 855. - However, it should be noted that each of
user devices 810, includingmobile device 815,tablet device 820,computer 825, and/orkiosk 830, may be implemented using any type of electronic device configured to send and receive data (e.g. clinical information) to and from a system ofservers 835 overnetwork 805. The user input device(s) may include any type or combination of input/output devices, such as a display monitor, touchpad, touchscreen, microphone, camera, keyboard, and/or mouse. - The
various user devices 810 may also communicate with each other by any suitable means (e.g., via Wi-Fi, radio frequency (RF), infrared (IR), Bluetooth, Near Field Communication, or any other suitable means) to send and receive location and other information. For example, amobile device 815 may communicate withtablet device 820 orkiosk 830. - The
user device 810 may receive information, such clinical data via thenetwork 805 from the system ofservers 835, having one or more servers such asclinical data servers 840,algorithm servers 845,user interface servers 850, and/or any other suitable servers. Each server may access thedecision model database 870 to retrieve decision models. Each server may include memory, a processor, and/or a database. For example, theclinical data server 840 may have a processor configured to retrieve clinical data from a provider's database and/or a patient's electronic medical record. Thealgorithm server 845 may have a database that includes various algorithms, and a processor configured to process the clinical data. Theuser interface server 850 may be configured to receive and process user input, such as clinical decision preferences. Thesatellite 855 may be configured to send and receive information to theserver system 835 anduser devices 810. - The
clinical data server 840 may receive clinical data, such as data regarding the provider and the patient from theuser device 810 via thenetwork 805 or indirectly via theuser interface server 850. Theclinical data server 840 may save the information in memory, such as a computer readable memory. - The
clinical data server 840 also may be in communication with one or more other servers, such as thealgorithm server 845 and/or external servers such as servers ofproviders 860 and/or patients 865 (e.g. medical records servers). The servers may include data about provider preferences, and/or patient health history. In addition, theclinical data server 860 may include data from other providers and/or patients. Thealgorithm server 845 may include machine learning, and/or other suitable algorithms. Thealgorithm server 845 may be in communication with other external servers and may be updated as desired. For example, thealgorithm server 845 may be updated with new algorithms, more powerful programming, and/or more data. Theclinical data server 840 and/or thealgorithm server 845 may process the information and transmit data to themodel server 870 for processing. - Each server in the system of
servers 835, includingclinical data server 840,algorithm server 845, andUI server 850 may each represent any of various types of servers including, but not limited to a web server, an application server, a proxy server, a network server, or a server farm. Each server in the system ofservers 835 may be implemented using, for example, any general-purpose computer capable of serving data to other computing devices including, but not limited to,user devices 810 or any other computing device (not shown) vianetwork 805. Such a general-purpose computer can include, but is not limited to, a server device having a processor and memory for executing and storing instructions. The memory may include any type of random access memory (RAM) or read-only memory (ROM) embodied in a physical storage medium, such as magnetic storage including floppy disk, hard disk, or magnetic tape; semiconductor storage such as solid-state disk (SSD) or flash memory; optical disc storage; or magneto-optical disc storage. Software may include one or more applications and an operating system. Hardware can include, but is not limited to, a processor, memory, and graphical user interface display. Each server also may have multiple processors and multiple shared or separate memory components that are configured to function together within, for example, a clustered computing environment or server farm. -
FIG. 9 is a simplified functional block diagram of a computer that may be configured as a host server, for example, to function as healthcare provider decision-making server.FIG. 9 illustrates a network orhost computer platform 900, as may typically be used to implement a server like the clinicaldecision model server 870. It is believed that those skilled in the art are familiar with the structure, programming, and general operation of such computer equipment and as a result, the drawings should be self-explanatory. - A platform for a
server 900 or the like, for example, may include a data communication interface forpacket data communication 960. The platform also may include a central processing unit (CPU) 920, in the form of one or more processors, for executing program instructions. The platform typically includes aninternal communication bus 910, program storage, and data storage for various data files to be processed and/or communicated by the platform such as ROM 930 andRAM 940 or the like. The hardware elements, operating systems, and programming languages of such equipment are conventional in nature, and it is presumed that those skilled in the art are adequately familiar therewith. Theserver 900 also may include input andoutput ports 950 to connect with input and output devices such as keyboards, mice, touchscreens, monitors, displays, etc., andcommunication ports 960. Of course, the various server functions may be implemented in a distributed fashion on a number of similar platforms to distribute the processing load. Alternatively, the servers may be implemented by appropriate programming of one computer hardware platform. - Program aspects of the technology may be thought of as “products” or “articles of manufacture” typically in the form of executable code and/or associated data that is carried on or embodied in a type of machine-readable medium. “Storage” type media include any or all of the tangible memory of the computers, processors or the like, or associated modules thereof, such as various semiconductor memories, tape drives, disk drives and the like, which may provide non-transitory storage at any time for the software programming. All or portions of the software may at times be communicated through the Internet or various other telecommunication networks. Such communications, for example, may enable loading of the software from one computer or processor into another, for example, from a management server or host computer of the mobile communication network into the computer platform of a server and/or from a server to the mobile device. Thus, another type of media that may bear the software elements includes optical, electrical and electromagnetic waves, such as used across physical interfaces between local devices, through wired and optical landline networks and over various air-links. The physical elements that carry such waves, such as wired or wireless links, optical links, or the like, also may be considered as media bearing the software. As used herein, unless restricted to non-transitory, tangible “storage” media, terms such as computer or machine “readable medium” refer to any medium that participates in providing instructions to a processor for execution.
- The many features and advantages of the disclosure are apparent from the detailed specification, and thus, it is intended by the appended claims to cover all such features and advantages of the disclosure which fall within the true spirit and scope of the disclosure. Further, since numerous modifications and variations will readily occur to those skilled in the art, it is not desired to limit the disclosure to the exact construction and operation illustrated and described, and accordingly.
- Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the invention being indicated by the following claims.
Claims (20)
Priority Applications (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US16/154,760 US20190147995A1 (en) | 2013-06-26 | 2018-10-09 | Systems and methods for clinical decision-making |
US16/946,616 US11361857B2 (en) | 2013-06-26 | 2020-06-29 | Systems and methods for creating and selecting models for predicting medical conditions |
US17/829,543 US11521727B2 (en) | 2013-06-26 | 2022-06-01 | Systems and methods for creating and selecting models for predicting medical conditions |
US18/053,108 US11651845B2 (en) | 2013-06-26 | 2022-11-07 | Systems and methods for creating and selecting models for predicting medical conditions |
US18/296,024 US20230238102A1 (en) | 2013-06-26 | 2023-04-05 | Systems and methods for creating and selecting models for predicting medical conditions |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US201361839528P | 2013-06-26 | 2013-06-26 | |
US14/311,736 US20150006192A1 (en) | 2013-06-26 | 2014-06-23 | Systems and methods for clinical decision-making |
US16/154,760 US20190147995A1 (en) | 2013-06-26 | 2018-10-09 | Systems and methods for clinical decision-making |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/311,736 Continuation US20150006192A1 (en) | 2013-06-26 | 2014-06-23 | Systems and methods for clinical decision-making |
Related Child Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/315,053 Continuation US9824190B2 (en) | 2007-02-22 | 2014-06-25 | Systems and methods for creating and selecting models for predicting medical conditions |
US16/857,880 Continuation US11538582B2 (en) | 2013-06-26 | 2020-04-24 | Systems and methods for creating and selecting models for predicting medical conditions |
US16/946,616 Continuation US11361857B2 (en) | 2013-06-26 | 2020-06-29 | Systems and methods for creating and selecting models for predicting medical conditions |
Publications (1)
Publication Number | Publication Date |
---|---|
US20190147995A1 true US20190147995A1 (en) | 2019-05-16 |
Family
ID=52116464
Family Applications (11)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/312,229 Active 2035-05-22 US9536053B2 (en) | 2013-06-26 | 2014-06-23 | Systems and methods for managing medication adherence |
US14/311,736 Abandoned US20150006192A1 (en) | 2013-06-26 | 2014-06-23 | Systems and methods for clinical decision-making |
US14/315,053 Active 2035-10-17 US9824190B2 (en) | 2007-02-22 | 2014-06-25 | Systems and methods for creating and selecting models for predicting medical conditions |
US15/360,209 Active 2034-07-25 US9858394B2 (en) | 2013-06-26 | 2016-11-23 | Systems and methods for managing regimen adherence |
US15/783,674 Active 2035-05-14 US10672509B2 (en) | 2007-02-22 | 2017-10-13 | Systems and methods for creating and selecting models for predicting medical conditions |
US15/789,047 Abandoned US20180166163A1 (en) | 2013-06-26 | 2017-10-20 | Systems and methods for managing regimen adherence |
US16/154,760 Abandoned US20190147995A1 (en) | 2013-06-26 | 2018-10-09 | Systems and methods for clinical decision-making |
US16/857,880 Active 2035-08-13 US11538582B2 (en) | 2013-06-26 | 2020-04-24 | Systems and methods for creating and selecting models for predicting medical conditions |
US17/108,793 Abandoned US20210151180A1 (en) | 2013-06-26 | 2020-12-01 | Systems and methods for managing regimen adherence |
US18/057,824 Pending US20230102425A1 (en) | 2013-06-26 | 2022-11-22 | Systems and methods for creating and selecting models for predicting medical conditions |
US18/188,628 Pending US20230230696A1 (en) | 2013-06-26 | 2023-03-23 | Systems and methods for managing regimen adherence |
Family Applications Before (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/312,229 Active 2035-05-22 US9536053B2 (en) | 2013-06-26 | 2014-06-23 | Systems and methods for managing medication adherence |
US14/311,736 Abandoned US20150006192A1 (en) | 2013-06-26 | 2014-06-23 | Systems and methods for clinical decision-making |
US14/315,053 Active 2035-10-17 US9824190B2 (en) | 2007-02-22 | 2014-06-25 | Systems and methods for creating and selecting models for predicting medical conditions |
US15/360,209 Active 2034-07-25 US9858394B2 (en) | 2013-06-26 | 2016-11-23 | Systems and methods for managing regimen adherence |
US15/783,674 Active 2035-05-14 US10672509B2 (en) | 2007-02-22 | 2017-10-13 | Systems and methods for creating and selecting models for predicting medical conditions |
US15/789,047 Abandoned US20180166163A1 (en) | 2013-06-26 | 2017-10-20 | Systems and methods for managing regimen adherence |
Family Applications After (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/857,880 Active 2035-08-13 US11538582B2 (en) | 2013-06-26 | 2020-04-24 | Systems and methods for creating and selecting models for predicting medical conditions |
US17/108,793 Abandoned US20210151180A1 (en) | 2013-06-26 | 2020-12-01 | Systems and methods for managing regimen adherence |
US18/057,824 Pending US20230102425A1 (en) | 2013-06-26 | 2022-11-22 | Systems and methods for creating and selecting models for predicting medical conditions |
US18/188,628 Pending US20230230696A1 (en) | 2013-06-26 | 2023-03-23 | Systems and methods for managing regimen adherence |
Country Status (1)
Country | Link |
---|---|
US (11) | US9536053B2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10748644B2 (en) | 2018-06-19 | 2020-08-18 | Ellipsis Health, Inc. | Systems and methods for mental health assessment |
WO2020236481A1 (en) * | 2019-05-17 | 2020-11-26 | Kutzko John D | Computer-implemented system and methods for predicting the health and therapeutic behavior of individuals using artificial intelligence, smart contracts and blockchain |
US11120895B2 (en) | 2018-06-19 | 2021-09-14 | Ellipsis Health, Inc. | Systems and methods for mental health assessment |
Families Citing this family (81)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US11289200B1 (en) * | 2017-03-13 | 2022-03-29 | C/Hca, Inc. | Authorized user modeling for decision support |
US10412028B1 (en) | 2013-05-24 | 2019-09-10 | HCA Holdings, Inc. | Data derived user behavior modeling |
US9536053B2 (en) * | 2013-06-26 | 2017-01-03 | WellDoc, Inc. | Systems and methods for managing medication adherence |
US11568982B1 (en) | 2014-02-17 | 2023-01-31 | Health at Scale Corporation | System to improve the logistics of clinical care by selectively matching patients to providers |
US10453562B2 (en) * | 2014-05-08 | 2019-10-22 | ProductVisionaries, LLC | Consumer-oriented biometrics data management and analysis system |
US20160154945A1 (en) * | 2014-12-01 | 2016-06-02 | Lg Cns Co., Ltd. | Method and system for changing medicine-taking schedule |
US10120979B2 (en) | 2014-12-23 | 2018-11-06 | Cerner Innovation, Inc. | Predicting glucose trends for population management |
US20160210434A1 (en) * | 2015-01-15 | 2016-07-21 | Umm Al-Qura University | Health information monitoring device and method |
US10886026B2 (en) | 2015-03-10 | 2021-01-05 | Elekta, Inc. | Adaptive treatment management system with a workflow management engine |
US20160292361A1 (en) * | 2015-04-01 | 2016-10-06 | Sean Martin | Data Collection and Recommendation System |
US20160321413A1 (en) * | 2015-04-29 | 2016-11-03 | Ims Health Incorporated | Systems and Methods for Determining Patient Adherence to Healthcare Treatment |
JP7001593B2 (en) | 2015-08-11 | 2022-01-19 | コグノア, インコーポレイテッド | Methods and devices for determining developmental progress using artificial intelligence and user input |
US10786182B2 (en) | 2015-09-09 | 2020-09-29 | The Joan and Irwin Jacobs Technion-Cornell Institute | System and method for passive remote monitoring of patients' fine motor behavior |
EP3369019A1 (en) | 2015-10-27 | 2018-09-05 | Koninklijke Philips N.V. | Pattern discovery visual analytics system to analyze characteristics of clinical data and generate patient cohorts |
US10770181B2 (en) * | 2015-12-16 | 2020-09-08 | Alegeus Technologies, Llc | Systems and methods for reducing resource consumption via information technology infrastructure |
EP3394825A4 (en) * | 2015-12-18 | 2019-08-14 | Cognoa, Inc. | Platform and system for digital personalized medicine |
US10251610B2 (en) * | 2016-01-26 | 2019-04-09 | International Business Machines Corporation | Contact tracing analytics |
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 |
US10437957B2 (en) * | 2016-02-17 | 2019-10-08 | International Business Machines Corporation | Driving patient campaign based on trend patterns in patient registry information |
US20170235884A1 (en) * | 2016-02-17 | 2017-08-17 | International Business Machines Corporation | Identifying Medical Codes Applicable to a Patient Based on Patient History and Probability Determination |
US10565309B2 (en) * | 2016-02-17 | 2020-02-18 | International Business Machines Corporation | Interpreting the meaning of clinical values in electronic medical records |
US11037658B2 (en) | 2016-02-17 | 2021-06-15 | International Business Machines Corporation | Clinical condition based cohort identification and evaluation |
US20170235886A1 (en) * | 2016-02-17 | 2017-08-17 | International Business Machines Corporation | Generating and Executing Complex Clinical Protocols on a Patient Registry |
US20170235887A1 (en) * | 2016-02-17 | 2017-08-17 | International Business Machines Corporation | Cognitive Mapping and Validation of Medical Codes Across Medical Systems |
US10395330B2 (en) | 2016-02-17 | 2019-08-27 | International Business Machines Corporation | Evaluating vendor communications for accuracy and quality |
US10685089B2 (en) | 2016-02-17 | 2020-06-16 | International Business Machines Corporation | Modifying patient communications based on simulation of vendor communications |
US10937526B2 (en) * | 2016-02-17 | 2021-03-02 | International Business Machines Corporation | Cognitive evaluation of assessment questions and answers to determine patient characteristics |
CN105701356A (en) * | 2016-02-24 | 2016-06-22 | 黄文佳 | Patient medication compliance judging method |
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 |
US10747850B2 (en) * | 2016-03-29 | 2020-08-18 | International Business Machines Corporation | Medication scheduling and alerts |
US20170286621A1 (en) * | 2016-03-29 | 2017-10-05 | International Business Machines Corporation | Evaluating Risk of a Patient Based on a Patient Registry and Performing Mitigating Actions Based on Risk |
US10748658B2 (en) * | 2016-05-13 | 2020-08-18 | WellDoc, Inc. | Database management and graphical user interfaces for measurements collected by analyzing blood |
US20200143922A1 (en) * | 2016-06-03 | 2020-05-07 | Yale University | Methods and apparatus for predicting depression treatment outcomes |
MA45536A (en) | 2016-06-30 | 2019-05-08 | Novo Nordisk As | SYSTEMS AND METHODS FOR ANALYSIS OF INSULIN DIET ADHERENCE DATA |
US11562816B2 (en) * | 2016-06-30 | 2023-01-24 | Novo Nordisk A/S | Systems and methods for analysis of insulin regimen adherence data |
US11464447B2 (en) | 2016-06-30 | 2022-10-11 | Novo Nordisk A/S | Regimen adherence measure for insulin treatment based on glucose measurements and insulin pen data |
MA45526A (en) * | 2016-06-30 | 2019-05-08 | Novo Nordisk As | SYSTEMS AND METHODS FOR THE ANALYSIS OF INSULIN REGIME MEMBERSHIP DATA |
US10885463B2 (en) * | 2016-07-08 | 2021-01-05 | Microsoft Technology Licensing, Llc | Metadata-driven machine learning for systems |
GB201613318D0 (en) * | 2016-08-02 | 2016-09-14 | Univ Oxford Innovation Ltd | System monitor and method of system monitoring |
US11222094B1 (en) | 2016-10-18 | 2022-01-11 | Express Scripts Strategie Development, Inc. | System and method for increasing medical adherence |
WO2018148365A1 (en) | 2017-02-09 | 2018-08-16 | Cognoa, Inc. | Platform and system for digital personalized medicine |
WO2018152550A1 (en) * | 2017-02-20 | 2018-08-23 | Penexa, LLC | System and method for managing treatment plans |
WO2018197442A1 (en) * | 2017-04-27 | 2018-11-01 | Koninklijke Philips N.V. | Real-time antibiotic treatment suggestion |
EP3628101B8 (en) | 2017-04-28 | 2023-07-19 | Better Therapeutics, Inc. | Method and system for managing lifestyle and health interventions |
US20180366024A1 (en) * | 2017-06-14 | 2018-12-20 | Microsoft Technology Licensing, Llc | Providing suggested behavior modifications for a correlation |
US20200227170A1 (en) * | 2017-06-15 | 2020-07-16 | Novo Nordisk A/S | Insulin titration algorithm based on patient profile |
US11355222B2 (en) * | 2017-10-05 | 2022-06-07 | Cerner Innovation, Inc. | Analytics at the point of care |
CN107767944A (en) * | 2017-10-25 | 2018-03-06 | 上海林康医疗信息技术有限公司 | A kind of slow disease patient compliance management method and system |
JP7131904B2 (en) * | 2017-12-18 | 2022-09-06 | オムロンヘルスケア株式会社 | Lifestyle management device, method and program |
US11334806B2 (en) * | 2017-12-22 | 2022-05-17 | International Business Machines Corporation | Registration, composition, and execution of analytics in a distributed environment |
US11151465B2 (en) | 2017-12-22 | 2021-10-19 | International Business Machines Corporation | Analytics framework for selection and execution of analytics in a distributed environment |
ES2914600T3 (en) * | 2018-01-30 | 2022-06-14 | Dental Monitoring | Analysis method of a representation of a dental arch |
US20190259482A1 (en) * | 2018-02-20 | 2019-08-22 | Mediedu Oy | System and method of determining a prescription for a patient |
US20190279752A1 (en) * | 2018-03-12 | 2019-09-12 | International Business Machines Corporation | Generation of adherence-improvement programs |
US11010024B2 (en) * | 2018-03-29 | 2021-05-18 | Cerner Innovation, Inc. | Intelligent user interface and application rendering |
US11250951B2 (en) * | 2018-03-30 | 2022-02-15 | Hitachi, Ltd. | Feature engineering method, apparatus, and system |
US20210233661A1 (en) * | 2018-08-31 | 2021-07-29 | Koninklijke Philips N.V. | System and method for creating guideline-based summaries for imaging exams |
EP3847669A1 (en) * | 2018-09-07 | 2021-07-14 | Informed Data Systems Inc. d/b/a One Drop | Forecasting blood glucose concentration |
CA3109754A1 (en) * | 2018-09-20 | 2020-03-26 | Medtronic Minimed, Inc. | Patient monitoring systems and related recommendation methods |
US11547799B2 (en) | 2018-09-20 | 2023-01-10 | Medtronic Minimed, Inc. | Patient day planning systems and methods |
CN109949881A (en) * | 2018-10-16 | 2019-06-28 | 陕西医链区块链集团有限公司 | A kind of big data processing method and equipment based on block chain |
US20200160949A1 (en) | 2018-11-20 | 2020-05-21 | Unitedhealth Group Incorporated | Automated electronic medical record (emr) analysis via point of care computing systems |
US10930395B2 (en) | 2018-11-23 | 2021-02-23 | Asheleigh Adeline Mowery | System for surgical decisions using deep learning |
WO2020188333A1 (en) | 2019-03-15 | 2020-09-24 | 3M Innovative Properties Company | Individualized medicine using causal models |
CN111696653A (en) * | 2019-03-15 | 2020-09-22 | 京东方科技集团股份有限公司 | Diagnosis and treatment guiding method, device and system and computer readable storage medium |
CA3134521A1 (en) | 2019-03-22 | 2020-10-01 | Cognoa, Inc. | Personalized digital therapy methods and devices |
US11449793B2 (en) * | 2019-07-03 | 2022-09-20 | Kpn Innovations, Llc. | Methods and systems for medical record searching with transmittable machine learning |
US11170898B2 (en) * | 2019-09-30 | 2021-11-09 | Kpn Innovations, Llc | Methods and systems for prioritizing user symptom complaint inputs |
US11217085B2 (en) * | 2020-03-02 | 2022-01-04 | Tetra Ventures LLC | Real time intervention platform for at-risk conduct |
US11610679B1 (en) * | 2020-04-20 | 2023-03-21 | Health at Scale Corporation | Prediction and prevention of medical events using machine-learning algorithms |
CN111840081B (en) * | 2020-06-17 | 2023-04-07 | 上海梅斯医药科技有限公司 | Medication reminding method and system and computer equipment |
EP3933850A1 (en) * | 2020-06-29 | 2022-01-05 | Koa Health B.V. | Method, apparatus and computer programs for early symptom detection and preventative healthcare |
CN111968718A (en) * | 2020-08-19 | 2020-11-20 | 上海梅斯医药科技有限公司 | Supervision reminding method and device for drug compliance |
WO2022081712A1 (en) * | 2020-10-14 | 2022-04-21 | nference, inc. | Systems and methods for retrieving clinical information based on clinical patient data |
US11393572B2 (en) * | 2020-11-03 | 2022-07-19 | Kpn Innovations, Llc. | System and method for modifying a nutrition requirement |
US20220139515A1 (en) | 2020-11-03 | 2022-05-05 | Nuance Communications, Inc. | Communication System and Method |
CN112802580A (en) * | 2021-02-05 | 2021-05-14 | 上海中医药大学附属曙光医院 | Body fat record management method and system |
CN112802579A (en) * | 2021-02-05 | 2021-05-14 | 上海中医药大学附属曙光医院 | Body fat health interaction method and system |
TWI776638B (en) * | 2021-08-17 | 2022-09-01 | 臺中榮民總醫院 | A medical care system that uses artificial intelligence technology to assist multi-disease decision-making and real-time information feedback |
Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20030161499A1 (en) * | 2002-02-28 | 2003-08-28 | Hugh Svendsen | Automated discovery, assignment, and submission of image metadata to a network-based photosharing service |
US20040015337A1 (en) * | 2002-01-04 | 2004-01-22 | Thomas Austin W. | Systems and methods for predicting disease behavior |
US20060052844A1 (en) * | 2004-09-02 | 2006-03-09 | Tom Newman | System and method for measuring modifying and reporting treatment compliance |
US20070239485A1 (en) * | 2006-02-01 | 2007-10-11 | Sroub Brian J | System and method for providing telediagnostic services |
US20100114607A1 (en) * | 2008-11-04 | 2010-05-06 | Sdi Health Llc | Method and system for providing reports and segmentation of physician activities |
US20100174553A1 (en) * | 2008-12-24 | 2010-07-08 | Medtronic Minimed, Inc. | Diabetes Therapy Management System |
US20110124996A1 (en) * | 2009-11-20 | 2011-05-26 | Roche Diagnostics Operations, Inc. | Diabetes health management systems and methods |
US20120109683A1 (en) * | 2010-10-27 | 2012-05-03 | International Business Machines Corporation | Method and system for outcome based referral using healthcare data of patient and physician populations |
US20130339042A1 (en) * | 2012-06-13 | 2013-12-19 | Healthhelp, Llc | System and method for providing a medical diagnostic concordance |
US20140058738A1 (en) * | 2012-08-21 | 2014-02-27 | International Business Machines Corporation | Predictive analysis for a medical treatment pathway |
Family Cites Families (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996012187A1 (en) | 1994-10-13 | 1996-04-25 | Horus Therapeutics, Inc. | Computer assisted methods for diagnosing diseases |
CN1604111A (en) | 1997-03-13 | 2005-04-06 | 第一咨询公司 | Disease management system and method including correlation assessment |
US20050086082A1 (en) | 1999-01-21 | 2005-04-21 | Patient Care Technologies | Portable health assistant |
EP1294441A2 (en) | 2000-06-14 | 2003-03-26 | Medtronic, Inc. | Deep computing applications in medical device systems |
DE60133653T2 (en) | 2000-08-18 | 2009-06-04 | Animas Technologies Llc | APPARATUS FOR PREDICTING HYPOGLYECURE DROPS |
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 |
GB0113435D0 (en) | 2001-06-04 | 2001-07-25 | Amersham Pharm Biotech Uk Ltd | Acridone derivatives as labels for fluorescence detection of target materials |
US20030208113A1 (en) | 2001-07-18 | 2003-11-06 | Mault James R | Closed loop glycemic index system |
MXPA04000611A (en) * | 2001-07-18 | 2005-02-17 | Wireless Generation Inc | System and method for real-time observation assessment. |
US20040199482A1 (en) | 2002-04-15 | 2004-10-07 | Wilson Scott B. | Systems and methods for automatic and incremental learning of patient states from biomedical signals |
EP1839229A4 (en) | 2004-12-30 | 2010-01-20 | Proventys Inc | Methods, systems, and computer program products for developing and using predictive models for predicting a plurality of medical outcomes, for evaluating intervention strategies, and for simultaneously validating biomarker causality |
US9526421B2 (en) * | 2005-03-11 | 2016-12-27 | Nrv-Wellness, Llc | Mobile wireless customizable health and condition monitor |
US8566121B2 (en) * | 2005-08-29 | 2013-10-22 | Narayanan Ramasubramanian | Personalized medical adherence management system |
US20100100391A1 (en) * | 2005-11-14 | 2010-04-22 | Kantilal Kasan Daya | Pharmaceutical packaging and method for delivery of same |
US20070288266A1 (en) | 2006-06-02 | 2007-12-13 | Suzanne Sysko | System and methods for chronic disease management and health assessment |
US8700430B2 (en) * | 2006-07-17 | 2014-04-15 | Walgreen Co. | Optimization of a medication therapy regimen |
US20080126130A1 (en) * | 2006-07-17 | 2008-05-29 | Walgreen Co. | Compliance With A Medication Therapy Regimen |
US7801836B2 (en) | 2006-09-27 | 2010-09-21 | Infosys Technologies Ltd. | Automated predictive data mining model selection using a genetic algorithm |
WO2008103827A1 (en) | 2007-02-22 | 2008-08-28 | Welldoc Communications, Inc. | System and method for providing treatment recommendations based on models |
US20080228699A1 (en) | 2007-03-16 | 2008-09-18 | Expanse Networks, Inc. | Creation of Attribute Combination Databases |
US8140270B2 (en) | 2007-03-22 | 2012-03-20 | National Center For Genome Resources | Methods and systems for medical sequencing analysis |
US20090030290A1 (en) | 2007-07-23 | 2009-01-29 | Kozuch Michael J | Method and apparatus for automated differentiated diagnosis of illness |
US20090247836A1 (en) * | 2008-02-28 | 2009-10-01 | Confidant Inc. | Medical System and Method for Serving Users with a Chronic Disease or Health State |
US8036915B2 (en) | 2008-07-31 | 2011-10-11 | Cosortium of Rheumatology Researchers of North America, Inc. | System and method for collecting and managing patient data |
WO2010019919A1 (en) * | 2008-08-14 | 2010-02-18 | University Of Toledo | Multifunctional neural network system and uses thereof for glycemic forecasting |
CA2680952A1 (en) * | 2008-10-01 | 2010-04-01 | Loyaltyone Us, Inc. | System and method for providing a health management program |
US20100324936A1 (en) | 2009-04-22 | 2010-12-23 | Suresh-Kumar Venkata Vishnubhatla | Pharmacy management and administration with bedside real-time medical event data collection |
US10169723B2 (en) * | 2009-11-11 | 2019-01-01 | International Business Machines Corporation | Distributed policy distribution for compliance functionality |
CN102892895B (en) * | 2010-03-11 | 2016-01-13 | 弗吉尼亚大学专利基金会 | For the method and system of the security of the insulin pump action in diabetes and other Regular Insulin delivery modality, analysis and supervision |
CN108509038B (en) * | 2010-08-09 | 2022-06-07 | 耐克创新有限合伙公司 | System and method for recording and tracking athletic activity |
US20120072231A1 (en) * | 2010-09-22 | 2012-03-22 | I.D. Therapeutics Llc | Methods, systems, and apparatus for optimizing effects of treatment with medication using medication compliance patterns |
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 |
WO2012097219A1 (en) * | 2011-01-14 | 2012-07-19 | Wake Forest University Health Sciences | Survey system for improving regimen adherence |
WO2012129507A1 (en) * | 2011-03-24 | 2012-09-27 | WellDoc, Inc. | Adaptive analytical behavioral and health assistant system and related method of use |
JP2014524791A (en) * | 2011-06-23 | 2014-09-25 | ユニバーシティ オブ ヴァージニア パテント ファウンデーション | An integrated platform for monitoring and controlling blood glucose levels in diabetics |
EP2751771A4 (en) * | 2011-08-31 | 2014-07-30 | Lifeguard Health Networks Inc | Health management system |
US20130226608A1 (en) * | 2012-02-28 | 2013-08-29 | Christopher Di Lascia | System for identifying, monitoring, influencing and rewarding healthcare behavior |
US10276260B2 (en) * | 2012-08-16 | 2019-04-30 | Ginger.io, Inc. | Method for providing therapy to an individual |
US9119529B2 (en) * | 2012-10-30 | 2015-09-01 | Dexcom, Inc. | Systems and methods for dynamically and intelligently monitoring a host's glycemic condition after an alert is triggered |
US20140249851A1 (en) * | 2013-03-04 | 2014-09-04 | Elekta Ab (Publ) | Systems and Methods for Developing and Managing Oncology Treatment Plans |
US9536053B2 (en) * | 2013-06-26 | 2017-01-03 | WellDoc, Inc. | Systems and methods for managing medication adherence |
-
2014
- 2014-06-23 US US14/312,229 patent/US9536053B2/en active Active
- 2014-06-23 US US14/311,736 patent/US20150006192A1/en not_active Abandoned
- 2014-06-25 US US14/315,053 patent/US9824190B2/en active Active
-
2016
- 2016-11-23 US US15/360,209 patent/US9858394B2/en active Active
-
2017
- 2017-10-13 US US15/783,674 patent/US10672509B2/en active Active
- 2017-10-20 US US15/789,047 patent/US20180166163A1/en not_active Abandoned
-
2018
- 2018-10-09 US US16/154,760 patent/US20190147995A1/en not_active Abandoned
-
2020
- 2020-04-24 US US16/857,880 patent/US11538582B2/en active Active
- 2020-12-01 US US17/108,793 patent/US20210151180A1/en not_active Abandoned
-
2022
- 2022-11-22 US US18/057,824 patent/US20230102425A1/en active Pending
-
2023
- 2023-03-23 US US18/188,628 patent/US20230230696A1/en active Pending
Patent Citations (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040015337A1 (en) * | 2002-01-04 | 2004-01-22 | Thomas Austin W. | Systems and methods for predicting disease behavior |
US20030161499A1 (en) * | 2002-02-28 | 2003-08-28 | Hugh Svendsen | Automated discovery, assignment, and submission of image metadata to a network-based photosharing service |
US20060052844A1 (en) * | 2004-09-02 | 2006-03-09 | Tom Newman | System and method for measuring modifying and reporting treatment compliance |
US20070239485A1 (en) * | 2006-02-01 | 2007-10-11 | Sroub Brian J | System and method for providing telediagnostic services |
US20100114607A1 (en) * | 2008-11-04 | 2010-05-06 | Sdi Health Llc | Method and system for providing reports and segmentation of physician activities |
US20100174553A1 (en) * | 2008-12-24 | 2010-07-08 | Medtronic Minimed, Inc. | Diabetes Therapy Management System |
US20110124996A1 (en) * | 2009-11-20 | 2011-05-26 | Roche Diagnostics Operations, Inc. | Diabetes health management systems and methods |
US20120109683A1 (en) * | 2010-10-27 | 2012-05-03 | International Business Machines Corporation | Method and system for outcome based referral using healthcare data of patient and physician populations |
US20130339042A1 (en) * | 2012-06-13 | 2013-12-19 | Healthhelp, Llc | System and method for providing a medical diagnostic concordance |
US20140058738A1 (en) * | 2012-08-21 | 2014-02-27 | International Business Machines Corporation | Predictive analysis for a medical treatment pathway |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10748644B2 (en) | 2018-06-19 | 2020-08-18 | Ellipsis Health, Inc. | Systems and methods for mental health assessment |
US11120895B2 (en) | 2018-06-19 | 2021-09-14 | Ellipsis Health, Inc. | Systems and methods for mental health assessment |
US11942194B2 (en) | 2018-06-19 | 2024-03-26 | Ellipsis Health, Inc. | Systems and methods for mental health assessment |
WO2020236481A1 (en) * | 2019-05-17 | 2020-11-26 | Kutzko John D | Computer-implemented system and methods for predicting the health and therapeutic behavior of individuals using artificial intelligence, smart contracts and blockchain |
Also Published As
Publication number | Publication date |
---|---|
US20150006456A1 (en) | 2015-01-01 |
US20170076064A1 (en) | 2017-03-16 |
US20150006192A1 (en) | 2015-01-01 |
US11538582B2 (en) | 2022-12-27 |
US20150006462A1 (en) | 2015-01-01 |
US20180039757A1 (en) | 2018-02-08 |
US9536053B2 (en) | 2017-01-03 |
US20230102425A1 (en) | 2023-03-30 |
US20230230696A1 (en) | 2023-07-20 |
US9824190B2 (en) | 2017-11-21 |
US9858394B2 (en) | 2018-01-02 |
US10672509B2 (en) | 2020-06-02 |
US20180166163A1 (en) | 2018-06-14 |
US20210151180A1 (en) | 2021-05-20 |
US20200251200A1 (en) | 2020-08-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20190147995A1 (en) | Systems and methods for clinical decision-making | |
US20220059236A1 (en) | Method for modeling behavior and health changes | |
US11316941B1 (en) | Remotely managing and adapting monitoring programs using machine learning predictions | |
Miller et al. | Patients’ utilization and perception of an artificial intelligence–based symptom assessment and advice technology in a British primary care waiting room: exploratory pilot study | |
Bender et al. | Pragmatic trial of health care technologies to improve adherence to pediatric asthma treatment: a randomized clinical trial | |
Martín-Lesende et al. | Impact of telemonitoring home care patients with heart failure or chronic lung disease from primary care on healthcare resource use (the TELBIL study randomised controlled trial) | |
US20200402630A1 (en) | Systems and methods for clinical decision-making | |
Walker et al. | Impact of a pharmacist-facilitated hospital discharge program: a quasi-experimental study | |
US20170109479A1 (en) | System and method for delivering digital coaching content | |
US20170076052A1 (en) | Methods and systems for dynamic management of a health condition | |
US11527314B2 (en) | Digital therapeutic systems and methods | |
Ndumele et al. | Association of state access standards with accessibility to specialists for Medicaid managed care enrollees | |
US20170177801A1 (en) | Decision support to stratify a medical population | |
KR20230113690A (en) | treatment recommendations | |
US20160117468A1 (en) | Displaying Predictive Modeling and Psychographic Segmentation of Population for More Efficient Delivery of Healthcare | |
US20230360754A1 (en) | Digital therapeutic systems and methods | |
Xie et al. | The association between electronic wearable devices and self-efficacy for managing health: a cross sectional study using 2019 HINTS data | |
Heselmans et al. | Feasibility and impact of an evidence-based electronic decision support system for diabetes care in family medicine: protocol for a cluster randomized controlled trial | |
US20240013928A1 (en) | Systems and methods of patient prioritization scores and measures | |
US20230083562A1 (en) | Ai based methods and systems for tracking chronic conditions | |
Holmes et al. | The status of patient portal use among Emergency Department patients experiencing houselessness: A large-scale single-center observational study | |
Wilkens et al. | Protocol: Study protocol: effects, costs and distributional impact of digital primary care for infectious diseases—an observational, registry-based study in Sweden | |
US11138235B1 (en) | Systems and methods for data categorization and delivery | |
Crowley | Contradictions and Opportunities in Mobile Care Management (“mCare”): An Observational Analytic Cohort Study | |
Lenert | Vantage: Exploring Variability in Inpatient Care Through Physicians’ Orders |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: WELLDOC, INC., MARYLAND Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SUDHARSAN, BHARATH;SHOMALI, MANSUR;REEL/FRAME:047101/0085 Effective date: 20140619 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |