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 facilitating dictionary migration or dictionary mapping from a first vocabulary or a first dictionary of terms to a second vocabulary includes one or more computers configured to carry out the steps of mapping a subset of the first set of terms to respective terms in an interface terminology and flagging another subset as not mapped to respective terms in the interface terminology. The system then may provide suggested mappings for the non-mapped terms, relying on user-supplied indications in order to map those terms. The system and method also may map the first dictionary terms to a reference terminology, an administrative terminology, or a clinical terminology or, conversely, may use those external terminologies to assist in mapping to the interface terminology.

Abstract: A medical classification code modeling system and method that generates visual maps in response to user queries, where the visual maps represent combinations of modifiers of an interface terminology that, taken together, map to medical classification code elements. The system and method may present multiple visual maps on the same display to permit visual analysis of multiple mapping revisions or versions. The system and method further may integrate into an electronic health record such that the user's ultimate selection of a mapping results in the corresponding medical classification code being inserted into the record of a patient at an appropriate location, such as on the patient's problem list.

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 computer-implemented system and method for post-coordination of clinically relevant searches with respect to an electronic medical ontology includes mapping the searches to elements of the ontology, determining whether the mapped elements support post-coordination and, if not, relying on a hierarchy established by a second electronic medical ontology to which the first electronic medical ontology is mapped to determine whether one or more broader elements support post-coordination. Upon identifying one or more such broader elements, the system then may present the user with attribute selections associated with each element in order to obtain the desired post-coordination terms. The resulting combination of a broader element with its relevant attributes maps to a concept in the electronic medical ontology that is fully pre-coordinated with respect to a third electronic medical ontology.

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 medical classification code modeling system and method that generates visual maps in response to user queries, where the visual maps represent combinations of modifiers of an interface terminology that, taken together, map to medical classification code elements. The system and method may present multiple visual maps on the same display to permit visual analysis of multiple mapping revisions or versions. The system and method further may integrate into an electronic health record such that the user's ultimate selection of a mapping results in the corresponding medical classification code being inserted into the record of a patient at an appropriate location, such as on the patient's problem list.

Abstract: A system and method for including a medical classification code in a computer application such as an electronic health record includes a web service configured to render as an interactive object in a portion of an application user interface. In response to a query, the web service returns an output including data, user interface components, and behavioral logic in order to update an interactive object.

Abstract: A system and process for tagging electronic documents or other electronic content with concepts mentioned, contained, or otherwise described in that content. Once tagged, the content may be searchable, indexable, and retrievable in order to provide that content to an end user or another recipient. The system may be configured to handle a considerable number of asset files and a large number of users, workflows, and access applications simultaneously. The system may auto-tag the content and also may include a user interface for confirming and updating those tags and for manually creating new or additional tags. Content may include documents such as medical documents relating to procedures, diagnoses, medications or other domains. Alternatively, the content may include information about various care providers, in order to allow a user to locate a physician meeting one or more desired criteria.

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 method for determining a sufficiency of data entry in an electronic health record includes: receiving a packet of input data from a user, the input data reflecting patient problem, history, or diagnosis information; linking data elements in the packet with interface terminology data elements; mapping the interface terminology data elements corresponding to the codified data elements to data elements in a code set; sending the mapped data elements in the sample code set to a DRG encoder or DRG web service; and receiving zero or more DRGs correspond to the mapped data elements. The results of the receiving step then are conveyed back to the user so that the user may know whether sufficient data has been entered or whether additional details are necessary.

Abstract: A system and process for record duplication analysis that relies on a multi-membership Bayesian analysis to determine the probability that records within a data set are matches. The Bayesian calculation may rely on objective data describing the data set as well as subjective assessments of the data set. In addition, a system and process for record duplication analysis may rely on the predetermination of probabilistic patterns, where the system only searches for patterns exceeding a chosen threshold.

Abstract: A system and method for keeping, organizing and managing electronic records, comprising generating a first instance of data objects comprising data elements during a first encounter, the elements comprising a first instance identifier and temporal identifiers; linking a data object to a summarization reference with a pointer; creating an additional instance of data objects also comprising data elements comprising an additional instance identifier and temporal identifiers during a later encounter; and providing continuity for the first instance data objects over time. Continuity may be provided by tracking a relationship between the first instance data object and an additional instance data object and repointing the pointer to point between the summarization reference and the additional instance data object. The additional instance data object may be a revision of the first instance data object, and tracking may occur by back-linking the revision to the first instance data object.

Abstract: A system and process for tagging electronic documents or other electronic content with concepts mentioned, contained, or otherwise described in that content. Once tagged, the content may be searchable, indexable, and retrievable in order to provide that content to an end user or another recipient. The system may be configured to handle a considerable number of asset files and a large number of users, workflows, and access applications simultaneously. The system may auto-tag the content and also may include a user interface for confirming and updating those tags and for manually creating new or additional tags. Content may include documents such as medical documents relating to procedures, diagnoses, medications or other domains. Alternatively, the content may include information about various care providers, in order to allow a user to locate a physician meeting one or more desired criteria.

Abstract: A system and method for keeping, organizing and managing electronic records, comprising generating a first instance of data objects comprising data elements during a first encounter, the elements comprising a first instance identifier and temporal identifiers; linking a data object to a summarization reference with a pointer; creating an additional instance of data objects also comprising data elements comprising an additional instance identifier and temporal identifiers during a later encounter; and providing continuity for the first instance data objects over time. Continuity may be provided by tracking a relationship between the first instance data object and an additional instance data object and repointing the pointer to point between the summarization reference and the additional instance data object. The additional instance data object may be a revision of the first instance data object, and tracking may occur by back-linking the revision to the first instance data object.

Abstract: A system and process for record duplication analysis that relies on a multi-membership Bayesian analysis to determine the probability that records within a data set are matches. The Bayesian calculation may rely on objective data describing the data set as well as subjective assessments of the data set. In addition, a system and process for record duplication analysis may rely on the predetermination of probabilistic patterns, where the system only searches for patterns exceeding a chosen threshold.

Abstract: A method for managing a back-end information storage infrastructure and a flexible development environment for data storage using a computer system. The method includes managing system resources including a relational database. Meta data models are created to model processes and to define meta data elements and their relationships by using trees and graphs. The method manages access to the data by authenticating users through several levels of authentication describing user rights, while providing management of multi-user access and concurrency. The method includes running the processes that generate instance data, storing the instance data following the meta data model, and transforming the instance data into physical views.

Abstract: A method for interfacing applications to maintain data integrity. A client service identifies new or changed data in a client application. The data is then posted to a core service in a transaction. Next, the client applications that need updating are determined. For the client applications that need updating a pending transaction directed to those client applications is stored in the queue storage. The client service for one of the client applications that needs updating searches the queue storage for the pending transaction. The client service then updates the client application that needs updating with the new or changed data.

Abstract: A system and method for keeping, organizing and managing electronic records, comprising generating a first instance of data objects comprising data elements during a first encounter, the elements comprising a first instance identifier and temporal identifiers; linking a data object to a summarization reference with a pointer; creating an additional instance of data objects also comprising data elements comprising an additional instance identifier and temporal identifiers during a later encounter; and providing continuity for the first instance data objects over time. Continuity may be provided by tracking a relationship between the first instance data object and an additional instance data object and repainting the pointer to point between the summarization reference and the additional instance data object. The additional instance data object may be a revision of the first instance data object, and tracking may occur by back-linking the revision to the first instance data object.