Abstract: Health-related information is gathered from a variety of sources, and organized in a platform that is context aware. The health data is correlated and displayed using visualization tools including timelines, tasks or graphical images. Health data input sources can include healthcare providers, users, lab reports, and typically any entity that develops health related data. The health data is categorized, analyzed and processed according to individualized or context-oriented algorithms. The health data can be correlated with various contexts via users, curators, automated systems and other organizing tools. A user can view health data in relation to progress, trends and contextual data that is derived from the correlations.

Abstract: Information is organized according to context to manage large amounts of data with a useful result. Schema definitions and other structure-defining components can be defined by curators or individuals to organize information according to context, and permit presentation of the context in the form of a mapping. The map topology can also be defined by curators and individuals for forming a visual map of the context-oriented data. Such visual maps can embed applications that can use the context-oriented data as input to expand the usefulness of the context-organized data. A repository can store relationships between the contexts as established by the schema, as well as data and data structures related to linking applications or contexts in accordance with curation activity. The resulting visual map is searchable, filterable and browseable to permit useful data insights to be annunciated.

Abstract: Information is organized according to context to manage large amounts of data with a useful result. Schema definitions and other structure-defining components can be defined by curators or individuals to organize information according to context, and permit presentation of the context in the form of a mapping. The map topology can also be defined by curators and individuals for forming a visual map of the context-oriented data. Such visual maps can embed applications that can use the context-oriented data as input to expand the usefulness of the context-organized data. A repository can store relationships between the contexts as established by the schema, as well as data and data structures related to linking applications or contexts in accordance with curation activity. The resulting visual map is searchable, filterable and browseable to permit useful data insights to be annunciated.

Abstract: An improved method and system for complex and integrated application performance management which tracks end-to-end computer resource consumption of a first business application workflow in an enterprise system. The first business application workflow may include a plurality of components. The plurality of components may further include one or more component types. A second or subsequent business application workflow may be embedded or linked as a component of the first business application workflow. Resource usage information of the plurality of components (including resource usage information of underlying units of work of the plurality of components) may be correlated to determine cumulative resource usage information for the first business application workflow. The resource usage information may be displayed in a graphical user interface.

Abstract: A method and system for tracking messages in an electronic mail messaging system. The electronic mail messaging system includes a plurality of electronic mail servers, wherein each respective electronic mail server includes message tracking software that logs message information regarding messages transferred through the respective electronic mail server. For example, the electronic mail messaging system may be the Microsoft Exchange Messaging System.

Abstract: An improved method and system for complex and integrated application performance management which tracks end-to-end computer resource consumption of a first business application workflow in an enterprise system. The first business application workflow may include a plurality of components. The plurality of components may further include one or more component types. A second or subsequent business application workflow may be embedded or linked as a component of the first business application workflow. Resource usage information of the plurality of components (including resource usage information of underlying units of work of the plurality of components) may be correlated to determine cumulative resource usage information for the first business application workflow. The resource usage information may be displayed in a graphical user interface.