Abstract: A method for generating a user interface for analyzing a patient-specific electronic medical or health record that includes a problem list includes the steps of grouping related potential problems into problem list categories, grouping a subset of the problems into clusters within the categories, mapping, using a computer, entries in the problem list with a respective description in an interface terminology, associating one or more of other medical data, e.g., medication, lab results, procedures, imaging results, past medical history or surgeries, notes, vital signs, or allergy data in the record with at least one problem, receiving a request corresponding to a problem or problem list category or to other medical data, identifying non-problem data in the record grouped in a cluster with the requested data, and modifying a user interface to display the identified data separate from other similar medical data included in the electronic medical or health record.

Abstract: A method for generating a user interface for analyzing a patient-specific electronic medical or health record that includes a problem list includes the steps of grouping related potential problems into problem list categories, grouping a subset of the problems into clusters within the categories, mapping, using a computer, entries in the problem list with a respective description in an interface terminology, associating one or more of other medical data, e.g., medication, lab results, procedures, imaging results, past medical history or surgeries, notes, vital signs, or allergy data in the record withdf at least one problem, receiving a request corresponding to a problem or problem list category or to other medical data, identifying non-problem data in the record grouped in a cluster with the requested data, and modifying a user interface to display the identified data separate from other similar medical data included in the electronic medical or health record.

Abstract: A system and method for problem list categorization and management in an electronic health or medical record includes matching each entry in the list with an interface terminology concept, grouping related concepts together into one or more categories, and grouping entries into one or more nested sets of problems. Groupings are accomplished by analyzing semantic distances between concept elements to determine which entries are duplicates according to the interface terminology and which are different but related to sufficiently similar concepts. Certain elements will be sufficiently related that they are nested or clustered within a single problem list element. Others are different enough to merit different elements but classification within a common category of problems.

Abstract: A system and method for receiving and processing patient medical information for integration into third party applications, including patient medical records, billing systems, and reporting systems. The method may be implemented as a software as a service application separate from the middle tier application server or other computer system implementing the third party application. In addition, the system may operate in a stateless environment in which the computer system running the SaaS application may not retain the patient medical information or data relating to a patient history interview state.

Abstract: A method for generating a user interface for analyzing a patient-specific electronic medical or health record that includes a problem list includes the steps of grouping related potential problems into problem list categories, grouping a subset of the problems into clusters within the categories, mapping, using a computer, entries in the problem list with a respective description in an interface terminology, associating one or more of other medical data, e.g., medication, lab results, procedures, imaging results, past medical history or surgeries, notes, vital signs, or allergy data in the record with at least one problem, receiving a request corresponding to a problem or problem list category or to other medical data, identifying non-problem data in the record grouped in a cluster with the requested data, and modifying a user interface to display the identified data separate from other similar medical data included in the electronic medical or health record.

Abstract: A system and method for generating local deployments of ontological mappings includes comparing a customizable version of an ontological mapping with a reference version and determining differences in the mappings. The differences may be used to generate a local instantiation to record the user's preferences, the local instantiation being retained on the user's computer system or accessible only by the user or a system administrator, i.e., not accessible by an unrelated user. The local instantiation then exhibits permanence, remaining accessible by the user to manually or automatically update the most recent ontological mapping to incorporate the user's mappings.

Abstract: A method for generating orders for a care plan through a problem list in an electronic medical record or an electronic health record includes the steps of mapping, using a computer, entries in a problem list with a respective concept in an interface terminology, analyzing, by a computer, each mapped entry to determine related problem list entries, grouping related entries into one or more categories, and aggregating a plurality of care plans relevant to one of the categories. Care plans may include medications and labs, and each care plan entry also may be coded with an external terminology, such as RxNorm or LOINC.

Abstract: A system and method for problem list categorization and management in an electronic health or medical record includes matching each entry in the list with an interface terminology concept, grouping related concepts together into one or more categories, and grouping entries into one or more nested sets of problems. Groupings are accomplished by analyzing semantic distances between concept elements to determine which entries are duplicates according to the interface terminology and which are different but related to sufficiently similar concepts. Certain elements will be sufficiently related that they are nested or clustered within a single problem list element. Others are different enough to merit different elements but classification within a common category of problems.

Abstract: A system and method for receiving and processing patient medical information for integration into third party applications, including patient medical records, billing systems, and reporting systems. The method may be implemented as a software as a service application separate from the middle tier application server or other computer system implementing the third party application. In addition, the system may operate in a stateless environment in which the computer system running the SaaS application may not retain the patient medical information or data relating to a patient history interview state.