Abstract: A system and method for extracting data from an electronic health record to provide provider and patient data similarity scoring includes: encoding a problem list for a plurality of patients with concepts from a common electronic health record ontology. In one aspect, the patients have electronic health records maintained by a plurality of providers. The system and method then may parse the concepts into a plurality of clusters or categories and determining, for each of the providers, a total number of patients that have at least one problem in a cluster or category or determining, for each patient, which of the plurality of clusters or categories correspond to at least one concept encoded in the patient's problem list. The system and method then may calculate for each pair of providers or patients, a distance between the providers or patients.

Abstract: A user interface, system and method for optimizing a patient problem list in an electronic medical record or electronic health record in which entries in the problem list are removable or otherwise editable if they were entered into the problem list longer ago than a limited duration window to which the entries are categorized. In order to determine that categorization, the problem list entries are mapped to concepts or lexicals of an interface terminology, which in turn is mapped to concepts of another terminology, and those concepts are analyzed with respect to one or more criteria used to establish the limited duration window.

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 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 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 computer-implemented system and method for identifying potential clinical trial participants from one or more databases of patient electronic health information includes analyzing the clinical trial requirements and mapping those requirements to an interface terminology, where concepts of the interface terminology include a key concept and a group of one or more additional concepts that are related in the context of the clinical trial. The method further includes mapping the patient electronic health information to the interface terminology, building a query of one or more interface terminology elements; analyzing the patient health information for matches to the one or more interface terminology elements and, if necessary, iterating the process by adding additional interface terminology elements to the query.

Abstract: A method of implementing a controlled vocabulary may include the steps of generating the controlled vocabulary by forming a list of medical terms and associated descriptions; creating a list of codes internal to the controlled vocabulary; and storing the codes, the medical terms, and the descriptions in a format suitable for use in the patient longitudinal electronic medical record environment. In addition, a sound wave may be captured as an electronic file, translated into text, and stored as a patient medical record event. The patient medical record event may be parsed for context and may be tagged with one or more source vocabularies, and a code internal to the source vocabulary may be provided. Event context and source vocabulary findings may then be used as discrete elements to add to the longitudinal patient electronic medical record environment.

Abstract: A method for implementing an interface terminology is described, the interface terminology comprising concepts and descriptions, a description being an alternative way to express a concept. The interface terminology also may include a plurality of domains, wherein each concept is unique within a domain. The method may include the steps of: storing a plurality of concepts in a database; storing a plurality of descriptions in a database; linking each description to a respective concept; storing an external code set in a database, the external code set comprising a plurality of external codes; and mapping an external code to a concept. The steps may occur via database table mapping. The method also may include deploying a front-end file, the front-end file comprises a link between the descriptions and the external code set.

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 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 searching and presenting data may include receiving a search request, storing data in an in memory database, accessing that data by one or more 64 bit processors, determining exact or approximate matches among the data to the search request, building a machine-readable data file including the search results, and serving the data file to a user's machine, where it is visible through a portal interface, which may be local or remotely served to the user's machine. The system may employ 64 bit technology in order to access and serve significant amounts of information, including mappings between code set and other data that may include mappings to one or more code sets. The system also may employ raw TCP/IP sockets to reduce latency and increase search speed.

Abstract: A method for implementing an interface terminology is described, the interface terminology comprising concepts and descriptions, a description being an alternative way to express a concept. The interface terminology also may include a plurality of domains, wherein each concept is unique within a domain. The method may include the steps of: storing a plurality of concepts in a database; storing a plurality of descriptions in a database; linking each description to a respective concept; storing an external code set in a database, the external code set comprising a plurality of external codes; and mapping an external code to a concept. The steps may occur via database table mapping. The method also may include deploying a front-end file, the front-end file comprises a link between the descriptions and the external code set.

Abstract: A method for generating and using a portable patient file may include entering data relating to a patient into a computer and storing the patient data in a medical record for the patient in a database using metadata in an adaptive data environment. The computer is configured to instantiate a file configured for import or export of the patient data, and the file is capable of transferring the patient data from the database to another database with preservation of semantic meanings associated with the patient data.

Abstract: A system and method for searching and presenting data may include receiving a search request, storing data in an in memory database, accessing that data by one or more 64 bit processors, determining exact or approximate matches among the data to the search request, building a machine-readable data file including the search results, and serving the data file to a user's machine, where it is visible through a portal interface, which may be local or remotely served to the user's machine. The system may employ 64 bit technology in order to access and serve significant amounts of information, including mappings between code set and other data that may include mappings to one or more code sets. The system also may employ raw TCP/IP sockets to reduce latency and increase search speed.

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 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 implementing an interface terminology is described, the interface terminology comprising concepts and descriptions, a description being an alternative way to express a concept. The interface terminology also may include a plurality of domains, wherein each concept is unique within a domain. The method may include the steps of: storing a plurality of concepts in a database; storing a plurality of descriptions in a database; linking each description to a respective concept; storing an external code set in a database, the external code set comprising a plurality of external codes; and mapping an external code to a concept. The steps may occur via database table mapping. The method also may include deploying a front-end file, the front-end file comprises a link between the descriptions and the external code set.