Abstract: Hospital readmissions may be prevented. Readmission is prevented by predicting the probability of a given patient to be readmitted. The probability alone may prevent readmission by educating the patient or medical professional. The probability may be predicted during a patient stay and used to generate a workflow action item to reduce the probability, to warn, to output appropriate instructions, and/or assist in avoiding readmission. The probability may be specific to a hospital, physician group, or other entity, allowing prevention to focus on past readmission causes for the given entity.

Abstract: Hospital readmissions may be prevented. Readmission is prevented by predicting the probability of a given patient to be readmitted. The probability alone may prevent readmission by educating the patient or medical professional. The probability may be predicted during a patient stay and used to generate a workflow action item to reduce the probability, to warn, to output appropriate instructions, and/or assist in avoiding readmission. The probability may be specific to a hospital, physician group, or other entity, allowing prevention to focus on past readmission causes for the given entity.

Abstract: A mechanism is provided in a data processing system to implement a feature extraction tool for graphical user interface based feature extraction. The feature extraction tool receives selection by a user of a dataset from which features are to be extracted. The feature extraction tool loads a plurality of feature definitions. The feature extraction tool generates a graphical user interface that allows the user to add features from the plurality of features to a feature file. The feature extraction tool presents the graphical user interface to the user and receives user selection of at least one feature to be added to the feature file. The feature extraction tool generates the feature file based on the user selection of the at least one feature.

Abstract: Hospital readmissions may be prevented. Readmission is prevented by predicting the probability of a given patient to be readmitted. The probability alone may prevent readmission by educating the patient or medical professional. The probability may be predicted during a patient stay and used to generate a workflow action item to reduce the probability, to warn, to output appropriate instructions, and/or assist in avoiding readmission. The probability may be specific to a hospital, physician group, or other entity, allowing prevention to focus on past readmission causes for the given entity.

Abstract: Hospital readmissions may be prevented. Readmission is prevented by predicting the probability of a given patient to be readmitted. The probability alone may prevent readmission by educating the patient or medical professional. The probability may be predicted during a patient stay and used to generate a workflow action item to reduce the probability, to warn, to output appropriate instructions, and/or assist in avoiding readmission. The probability may be specific to a hospital, physician group, or other entity, allowing prevention to focus on past readmission causes for the given entity.

Abstract: Hospital readmissions may be prevented. Readmission is prevented by predicting the probability of a given patient to be readmitted. The probability alone may prevent readmission by educating the patient or medical professional. The probability may be predicted during a patient stay and used to generate a workflow action item to reduce the probability, to warn, to output appropriate instructions, and/or assist in avoiding readmission. The probability may be specific to a hospital, physician group, or other entity, allowing prevention to focus on past readmission causes for the given entity.

Abstract: A mechanism is provided in a data processing system to implement a feature extraction tool for graphical user interface based feature extraction. The feature extraction tool receives selection by a user of a dataset from which features are to be extracted. The feature extraction tool loads a plurality of feature definitions. The feature extraction tool generates a graphical user interface that allows the user to add features from the plurality of features to a feature file. The feature extraction tool presents the graphical user interface to the user and receives user selection of at least one feature to be added to the feature file. The feature extraction tool generates the feature file based on the user selection of the at least one feature.

Abstract: Mapping of semantics in healthcare may involve accessing first transaction data in a first database, the first transaction data corresponding to a collection of a first number of fields defined for a condition using a first semantic system to store information and calculating a first distribution of information in the first transaction data. Mapping may also involve accessing second transaction data in a second database, the second transaction data corresponding to a second semantic system different than the first semantic system and the second database comprising a second number of fields using the second semantic system to store information, and calculating a second distribution of information in the second transaction data. The distributions may then be compared and a map relating the semantic systems may be generated and used to communicate between the first and second semantic systems.

Abstract: Adaptive medical data collection for medical entities may involve triggering an analysis of electronic records in response to information input into an Electronic Medical Record (EMR) of a patient. Determining a potential condition for the patient based on the analysis. Identifying additional information indicated as relevant to the potential condition of the patient, and generating a request for the identified additional information.

Abstract: Adaptive medical data collection for medical entities may involve managing content by receiving data indicating a context, identifying at least one application or knowledge base associated with the context, designating the identified application or knowledge base as active, and accessing the active application or knowledge base to provide information at an interface point for a medical professionals and a patient.

Abstract: Adaptive medical data collection for medical entities may involve triggering an analysis of electronic records in response to information input into an Electronic Medical Record (EMR) of a patient. Determining a potential condition for the patient based on the analysis. Identifying additional information indicated as relevant to the potential condition of the patient, and generating a request for the identified additional information.

Abstract: Automatic mapping of semantics in healthcare is provided. Data sets have different semantics (e.g., Gender designated with M and F in one system and Sex designated with 1 or 2 in another system). For semantic interoperability, the semantic links between the semantic systems of different healthcare entities are created (e.g., Gender=Sex and/or 1=F and 2=M) by a processor from statistics of the data itself. The distribution of variables, values, or variables and values, with or without other information and/or logic, is used to create a map from one semantic system to another. Similar distributions of other variable and/or values are likely to be for variables and/or values with the same meaning.

Abstract: Mapping of semantics in healthcare may involve accessing first transaction data in a first database, the first transaction data corresponding to a collection of a first number of fields defined for a condition using a first semantic system to store information and calculating a first distribution of information in the first transaction data. Mapping may also involve accessing second transaction data in a second database, the second transaction data corresponding to a second semantic system different than the first semantic system and the second database comprising a second number of fields using the second semantic system to store information, and calculating a second distribution of information in the second transaction data. The distributions may then be compared and a map relating the semantic systems may be generated and used to communicate between the first and second semantic systems.

Abstract: Mapping of semantics in healthcare may involve accessing first transaction data of a first healthcare entity in a first database, the first transaction data corresponding to a collection of a first number of fields defined for a condition using a first semantic system to store information and calculating a first distribution of information in the first transaction data. Mapping may also involve accessing second transaction data of a second healthcare entity in a second database, the second transaction data corresponding to a second semantic system different than the first semantic system and the second database comprising a second number of fields using the second semantic system to store information, the second number of fields larger than the first number of fields and calculating a second distribution of information in the second transaction data. The distributions may then be compared and a map relating the semantic systems may be generated.

Abstract: Managing a medication may involve identifying an event relating to the medication. Managing a medication may also involve determining a task for a course of care of a patient due to the event relating to the medication, and providing a notification to interested parties regarding the task and the event relating to the medication.

Abstract: Workflows for medical entities are determined and evaluated by determining a plurality of medical tasks based on an analysis of a plurality of electronic medical records of a medical entity. A workflow of the medical entity is determined based on a sequence of medical tasks, the sequence determined based on the analysis of the plurality of electronic medical records, and an evaluation of the workflow is performed based on a predefined criterion.

Abstract: Patient summary generation may involve receiving a request for summary data relating to treatment of a patient over a period of time and accessing a medical record of the patient to determine at least one condition of the patient for the period of time. Summary generation may also involve determining reporting categories relating to the at least one condition, identifying elements of the medical records associated with the reporting categories, determining data of the identified elements indicative of the summary data for the at least one condition, and compiling the summary data into a summary report.

Abstract: Mapping of semantics in healthcare may involve accessing first transaction data of a first healthcare entity in a first database, the first transaction data corresponding to a collection of a first number of fields defined for a condition using a first semantic system to store information and calculating a first distribution of information in the first transaction data. Mapping may also involve accessing second transaction data of a second healthcare entity in a second database, the second transaction data corresponding to a second semantic system different than the first semantic system and the second database comprising a second number of fields using the second semantic system to store information, the second number of fields larger than the first number of fields and calculating a second distribution of information in the second transaction data. The distributions may then be compared and a map relating the semantic systems may be generated.

Abstract: Rather than modify or create, by programmers, a new workflow specifically for each healthcare provider, a workflow provider creates an abstract workflow appropriate for any or many healthcare providers. Using context about a specific healthcare provider, a computer automatically adapts the abstract workflow to the healthcare provider. Using patient context, the computer may automatically schedule tasks of the adapted workflow appropriate for the specific patient and the specific healthcare provider. The patient and healthcare provider context may be monitored for any changes that alter the workflow, and the system may reschedule the tasks as appropriate.

Abstract: Hospital readmissions may be prevented. Readmission is prevented by predicting the probability of a given patient to be readmitted. The probability alone may prevent readmission by educating the patient or medical professional. The probability may be predicted during a patient stay and used to generate a workflow action item to reduce the probability, to warn, to output appropriate instructions, and/or assist in avoiding readmission. The probability may be specific to a hospital, physician group, or other entity, allowing prevention to focus on past readmission causes for the given entity.