Abstract: The event management system described is capable of aligning controlled content in a controlled content repository to properties of an event, e.g., event type, event topic, geographic location and product involved. When a user creates an event, controlled content associated with the event properties may be displayed so that the user may choose proper content for the event. When event content is updated in the controlled content repository, the latest version is pushed to the speaker so that only the latest version of the controlled content can be shared. Content displayed during a webinar and attendee participation data for the webinar may be tracked and stored in a CRM system.

Abstract: The event management system described is capable of aligning controlled content in a controlled content repository to properties of an event, e.g., event type, event topic, geographic location and product involved. When a user creates an event, controlled content associated with the event properties may be displayed so that the user may choose proper content for the event. When event content is updated in the controlled content repository, the latest version is pushed to the speaker so that only the latest version of the controlled content can be shared. Content displayed during a webinar and attendee participation data for the webinar may be tracked and stored in a CRM system.

Abstract: Systems and methods for providing an API for a database system. The API may be provided to enable external application developers to build applications that can support the dynamic security model of the content management system and describe the runtime properties of records in data objects. The API of may provide a record property object and/or a query describe object when returning data set in response to a query by providing information about actions an end user can take on the data records, and to provide metadata required to understand a data response.

Abstract: Systems and methods for linking HCPs from an MDM system and publication authors from a second source data system. Distances between the HCPs and the publication authors may be determined, and an HCP and a publication author may be connected if their distance is below a threshold. The connected data points may be used to train a machine learning model to determine a probability that an HCP matches a publication author. An upper bound and a lower bound may be set. Data points with the probability over the upper bound may be sent out as matches, data points below the lower bound may be disregarded as not a match, and data points between the upper bound and lower bound may be labeled for manual verification.

Abstract: Methods and systems for accessing, maintaining, analyzing, and visualizing structured data are presented. The system receives from a requesting computing device, a first request for a first hierarchical record. The system searches a first repository having first structured data. The system determines whether the first hierarchical record is present in the first structured data and creates, based on the first hierarchical record, a snapshot query criterion. The system then searches, based on the snapshot query criterion, a second repository comprising a first snapshot of the first structured data. The system determines whether a second hierarchical record at least partially matches the first hierarchical record.

Abstract: The event management system described is capable of aligning controlled content in a controlled content repository to properties of an event, e.g., event type, event topic, geographic location and product involved. When a user creates an event, controlled content associated with the event properties may be displayed so that the user may choose proper content for the event. When event content is updated in the controlled content repository, the latest version is pushed to the speaker so that only the latest version of the controlled content can be shared. Content displayed during a webinar and attendee participation data for the webinar may be tracked and stored in a CRM system.

Abstract: Systems and methods for providing an API for a database system. The API may be provided to enable external application developers to build applications that can support the dynamic security model of the content management system and describe the runtime properties of records in data objects. The API of may provide a record property object and/or a query describe object when returning data set in response to a query by providing information about actions an end user can take on the data records, and to provide metadata required to understand a data response.

Abstract: Systems and methods for exchanging clinical data among parties involved in a clinical trial. The system comprises a clinical data exchange controller, a first repository and a second repository. Repository configuration information comprises: a connection to a target repository, scope of capacities, and a rule set. Repository configuration information for the first repository is received at the first repository, and repository configuration information for the second repository is received at the second repository. When there is a change defined in the rule set happened in the first repository, a request for data transfer is sent to the clinical data exchange controller, and the clinical data exchange controller then transfers the data to the target repository based on the rule set.

Abstract: Systems and methods are provided for submitting data in a computer network. An exemplary method includes: receiving a first request to process a first data at one or more data servers; determining whether the first data includes a plurality of first set of properties; generating a second data having a plurality of second set of properties; providing a plurality of rule sets for submitting the second data; analyzing the second data to determine which of the rule sets is applicable; selecting one or more applicable rules from the rule sets; generating a plurality of third data by applying the one or more applicable rules to the second data; identifying the one or more external sources to distribute the third data; and sending the third data to the one or more external sources.

Abstract: Systems and methods for providing an API for a database system. The API may be provided to enable external application developers to build applications that can support the dynamic security model of the content management system and describe the runtime properties of records in data objects. The API of may provide a record property object and/or a query describe object when returning data set in response to a query by providing information about actions an end user can take on the data records, and to provide metadata required to understand a data response.

Abstract: Systems and methods for controlling commits to a search platform in a content management system. Identification information of endpoints may be passed down from endpoints to the search platform. Endpoints may be grouped based on their identification information, and commit policies may be assigned to each group of endpoints. A commit request from an endpoint to the search platform may be intercepted, its group may be determined based on the endpoint identification information, and commit policy for that group may be applied to the commit request.

Abstract: Systems and methods for controlling document access in a content management system. A user setup record may be saved for each user, and user groups may be generated based on attributes of user setup records. When a user group is stamped to a document in the content management system, all users in that user group get access to the document.

Abstract: Systems and methods for re-using content in a content management system. The content management system may have two or more repositories. A link document may be generated in a link repository for a source document in a source repository. The link document may be a copy of the source document, and synchronized to the source document in a number of different ways, dynamically or statically. When the source document is updated, the source repository may notify the link repository about the change, receive a pull request from the link repository for the change, and generate an updated link document.

Abstract: Systems and methods are provided for managing data associated with a point-in-time architecture (PTA) databases. An exemplary method includes: receiving first data from a first PTA database and second data from a second PTA database; validating one or more parameters associated with the first data and the second data; comparing the first data and the second data with one or more reference data; predicting one or more events based on the comparing; generating a data report indicating the first data and the second data leads to the predicted one or more events; performing, based on the data report, surveillance of the first data and the second data during a surveillance period and using a surveillance protocol; receiving an update to at least one of the first data, the second data, or the one or more reference data; and updating at least one of the predicted one or more events.

Abstract: The approved email generation system described is capable of producing email communications using approved email templates and content that have been aligned with information regarding user access to such content. Once the approved email has been generated, the content may be verified again for accuracy and validity before being delivered to the user. When the user accesses delivered content, the approved email generation system again verifies the content and allows the user access to only the most current version of the content available. The system provides for control of the content of electronic communications to users.

Abstract: Systems and methods for managing tenant code for a multi-tenant system. Instrumentation code may be added to the tenant code and track its performance. The tenant code may be disabled when it is determined based on information from the instrumentation code that the tenant code is misbehaving. An approximate clock may be used to determine if the running time of the tenant code exceeds a threshold.

Abstract: Systems and methods for managing regulatory information. The system comprises a submission controller, a registration controller and a submission archive controller. The submission controller may manage a submission structure, and allow users to search for documents in a content management system and add the documents to the submission structure. The registration controller may manage product registration information and health authority interactions globally, and capture, view and take actions upon product registrations. The submission archive controller may allow users to access a complete history of regulatory submissions and correspondence globally, with an easy to use interface. The three controllers reside in a single system that allows them to interact seamlessly with each other.

Abstract: Systems and methods for generating a pseudo data field in a CRM system to allow end users to generate and manage pseudo data fields for account objects in the CRM system, which may behave like actual data fields of account objects in the CRM system but live outside the CRM account. The present invention uses a data model that includes two objects to allow end users to generate and manage the pseudo data fields. One of the objects is pseudo data field configuration object, which may be used to configure the pseudo data fields that should be made available to end users. The other object is pseudo data field object which may be used to record user responses or values users use to populate the pseudo data field.

Abstract: Systems and methods for synchronizing data between a customer data management system and a data warehouse system. A data warehouse server may constantly monitor a dynamic metadata flow from the customer data management system, compare it with the metadata in the data storage device, and dynamically update the metadata in the data storage device. The data warehouse server may track activities over time and accumulate a long running history, which may include multiple versions of accounts in the customer data management system, e.g., the account as of today, the account as of yesterday, and another version that was the account two weeks ago.

Abstract: Systems and methods for synchronizing data between a customer data management system and a data warehouse system. A data warehouse server may constantly monitor a dynamic metadata flow from the customer data management system, compare it with the metadata in the data storage device, and dynamically update the metadata in the data storage device. The data warehouse server may track activities over time and accumulate a long running history, which may include multiple versions of accounts in the customer data management system, e.g., the account as of today, the account as of yesterday, and another version that was the account two weeks ago.