Abstract: A system and method for managing healthcare information is disclosed. The data servers each include a data manager that comprises a controller, a grid engine, applications, an application manager and a user interface engine. The controller manages the core functions and the transmission of data between data manager components. The grid engine manages information sent between data servers. The applications are applications that are created by the user or downloaded as third-party applications. The application manager manages the creation and communication between applications. The user interface engine generates user interfaces for displaying the applications and collecting clinical trial data.

Abstract: A system and method for managing patient consent. A data access manager includes a controller, a lookup module, a clinical authorization engine, a logging/auditing unit, a user profile engine, a report module and a user interface engine. The controller manages the core functions and the transmission of data between the data access manager components. The lookup module enables a user to query patient data. The clinical authorization engine authorizes access to patient data. The logging/auditing unit logs and monitors user activity. The user profile engine accesses and updates user profile information. The patient profile engine accesses and updates patient profile information. The report module generates reports related to the user activity. The user interface engine generates user interfaces for displaying the user profiles and patient information data.

Abstract: A system and method for managing healthcare information is disclosed. The data servers each include a data manager that comprises a controller, a grid engine, applications, an application manager and a user interface engine. The controller manages the core functions and the transmission of data between data manager components. The grid engine manages information sent between data servers. The applications are applications that are created by the user or downloaded as third-party applications. The application manager manages the creation and communication between applications. The user interface engine generates user interfaces for displaying the applications and collecting clinical trial data.

Abstract: A system and method for managing patient consent. A Master Matching Index (MMI) includes a collection of patient information and identifiers. An MMI adapter is coupled to the MMI for sending queries to the MMI for a health related entity. The MMI adapter comprises a data access manager that includes a lookup module, an authorization engine, an auditing module, a report module and a user interface engine. The user profile engine generates and updates user profile information. The lookup module enables a user to query patient information. The authorization engine determines whether the user has authorization to access patient information. The auditing module logs and monitors user activity. The report module generates reports related to user activity. The user interface engine generates user interfaces for displaying the user profiles, patient profiles and patient data.

Abstract: A system and method for scheduling or managing receipt of healthcare services are disclosed. A centralized service management module is coupled to one or more client devices and to one or more service providers, such as healthcare providers or insurance providers. The centralized service management module receives an interaction, such as an appointment request, from a client device or a service provider associated with healthcare services. The centralized service management module associates a service provider with the interaction based on a stored user profile. The interaction is then transmitted by the centralized service management module to the associated service provider, which provides data associated with a healthcare product or service associated with the interaction to the centralized service management module. The data is stored in the user profile and transmitted, buy the centralized service management module, to a client device using a communication protocol specified by the user profile.

Abstract: A system and method for managing healthcare information is disclosed. The data servers each include a data manager that comprises a controller, a grid engine, applications, an application manager and a user interface engine. The controller manages the core functions and the transmission of data between data manager components. The grid engine manages information sent between data servers. The applications are applications that are created by the user or downloaded as third-party applications. The application manager manages the creation and communication between applications. The user interface engine generates user interfaces for displaying the applications and collecting clinical trial data.

Abstract: A system and method for accessing health care data are disclosed. A data retrieval service module is coupled to a client device and to one or more data sources, such as medical data sources, a master patient index or additional data retrieval service modules. The data retrieval service module receives a data request from the client device and transmits the data request to the one or more data sources. The data retrieval service module then receives data associated with the data request from die one or more data sources and generates catalog by aggregating data from multiple data sources. The catalog is then transmitted from the data retrieval service module to the client device, allowing the client device to access data obtained from various data sources.

Abstract: A health information services provider (HISP) application includes a controller, a transaction engine, a data encryption engine, an authentication engine, a user interface engine and a registration engine. The controller manages the core functions and transmission to the different components of the HISP application. The transaction engine routes messages and requests for joining a grid. The data encryption engine encrypts or decrypts messages. The authentication engine verifies messages. The user interface engine generates a user interface for exchanging healthcare information between providers. The registration engine registers providers to exchange healthcare information with other providers.

Abstract: A system and method for managing patient consent. A data access manager includes a controller, a lookup module, a clinical authorization engine, a logging/auditing unit, a user profile engine, a report module and a user interface engine. The controller manages the core functions and the transmission of data between the data access manager components. The lookup module enables a user to query patient data. The clinical authorization engine authorizes access to patient data. The logging/auditing unit logs and monitors user activity. The user profile engine accesses and updates user profile information. The patient profile engine accesses and updates patient profile information. The report module generates reports related to the user activity. The user interface engine generates user interfaces for displaying the user profiles and patient information data.

Abstract: A system and method for managing healthcare information is disclosed. The data servers each include a data manager that comprises a controller, applications, an application manager, a virtual care team module, and a user interface engine. The controller manages the core functions and the transmission of data between data manager components. The applications are applications that are created by the user or downloaded as third-party applications. The application manager manages the creation and communication between applications. The virtual care team module manages the transmission of patient data between data servers. The user interface engine generates user interfaces for displaying the applications and collecting clinical trial data.

Abstract: A system and method for managing healthcare information is disclosed. The data servers each include a data manager that comprises a controller, a grid engine, applications, an application manager and a user interface engine. The controller manages the core functions and the transmission of data between data manager components. The grid engine manages information sent between data servers. The applications are applications that are created by the user or downloaded as third-party applications. The application manager manages the creation and communication between applications. The user interface engine generates user interfaces for displaying the applications and collecting clinical trial data.

Abstract: A system and method for managing healthcare information is disclosed. The data servers each include a data manager that comprises a controller, a scrubber module and a user interface engine. The controller manages the core functions and the transmission of data between data manager components. The scrubber module manages the pseudoanonymization of data and the collection of data for clinical trials. The user interface engine generates user interfaces for displaying the applications and collecting clinical trial data.

Abstract: A master matching index (MMI) is accessible to a plurality of entities connected over a network. Access to the MMI is provided via MMI adapters distributed among the entities. A distributed MMI adapter contains matching algorithms that specify how record queries from its associated entity should be compared against information in the MMI. Accordingly, an MMI may be searched for matches according to matching algorithms specified by disparate entities.

Abstract: Systems and methods for reconciling healthcare data between multiple distributed computing nodes that enable an individual node, a topic object, or an intelligent agent to determine synchronization with other nodes, comprising sending source node data to a payload generator, the source node data including difference data, an encapsulated topic object, or intelligent agent communications, generating a payload including the source node data and destination attributes, and sending the payload to a destination node, topic object, or destination intelligent agent, and using the source node data to update destination node data according to destination node, topic object, or destination intelligent agent requirements.

Abstract: Systems and methods for reconciling healthcare data between multiple distributed computing nodes that enable an individual node, a topic object, or an intelligent agent to determine synchronization with other nodes, comprising sending source node data to a payload generator, the source node data including difference data, an encapsulated topic object, or intelligent agent communications, generating a payload including the source node data and destination attributes, and sending the payload to a destination node, topic object, or destination intelligent agent, and using the source node data to update destination node data according to destination node, topic object, or destination intelligent agent requirements.

Abstract: Systems and methods for reconciling healthcare data between multiple distributed computing nodes that enable an individual node, a topic object, or an intelligent agent to determine synchronization with other nodes, comprising sending source node data to a payload generator, the source node data including difference data, an encapsulated topic object, or intelligent agent communications, generating a payload including the source node data and destination attributes, and sending the payload to a destination node, topic object, or destination intelligent agent, and using the source node data to update destination node data according to destination node, topic object, or destination intelligent agent requirements.

Abstract: A system and method for scheduling or managing receipt of healthcare services are disclosed. A centralized service management module is coupled to one or more client devices and to one or more service providers, such as healthcare providers or insurance providers. The centralized service management module receives an interaction, such as an appointment request, from a client device or a service provider associated with healthcare services. The centralized service management module associates a service provider with the interaction based on a stored user profile. The interaction is then transmitted by the centralized service management module to the associated service provider, which provides data associated with a healthcare product or service associated with the interaction to the centralized service management module. The data is stored in the user profile and transmitted, buy the centralized service management module, to a client device using a communication protocol specified by the user profile.