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 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 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 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 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 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 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.

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 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 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 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.