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 submitting regulatory documents, from authoring through uploading to a health authority gateway. It may continuously publish documents into a submission archive as documents become associated to the content plan and as related content or attributes are updated. It may continuously validate submission components by applying validation rules defined by a health authority to report non-conforming validation results during the publishing process. It may allow users to review and resolve validation errors and warnings by reporting information to users on an ongoing basis to help reduce end-stage reconciliation.

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 processing user requests for creating a new account in a CRM system. When a user requests to create a new account in the CRM system, an unverified account may be created in the CRM and a DCR may be sent to the MDM for verification. Users may interact with the unverified account while waiting for verification result from the MDM.

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 synchronizing data between a database system and its client applications are provided. After a regular synchronization, objects' records on a user computing device may be checked against a new sharing rule. Newly shared records may be synced down to the user computing device regardless of timestamps, and all records which the user no longer has access to may be removed from the user computing device. Consequently, data on the user computing device complies with the new sharing rule.

Abstract: Systems and methods for processing user requests for updating data in a CRM system. When a user requests to update data in the CRM system, it is determined if the requested data change involves a DCR-controlled field. If yes, the requested data change may be routed to the MDM system for validation first and the data change may not be used to update the CRM until the validation is successful. If the requested data change does not involve any DCR-controlled field, it may update the CRM immediately.

Abstract: Systems and methods for generating call reports which may allow access to the child call for each selected attendee via the group call, and enable users to capture data and make edits to detailing and sampling information unique to each attendee directly in the child call. Access to controls within the attendees section may enable mass entry of supported activities for a subset of attendees.

Abstract: Systems and methods for processing user requests for creating a new account in a CRM system. When a user requests to create a new account in the CRM system, an unverified account may be created in the CRM and a DCR may be sent to the MDM for verification. Users may interact with the unverified account while waiting for verification result from the MDM.

Abstract: Systems and methods for processing user requests for updating data in a CRM system. When a user requests to update data in the CRM system, it is determined if the requested data change involves a DCR-controlled field. If yes, the requested data change may be routed to the MDM system for validation first and the data change may not be used to update the CRM until the validation is successful. If the requested data change does not involve any DCR-controlled field, it may update the CRM immediately.

Abstract: Systems and methods for generating call reports which may allow access to the child call for each selected attendee via the group call, and enable users to capture data and make edits to detailing and sampling information unique to each attendee directly in the child call. Access to controls within the attendees section may enable mass entry of supported activities for a subset of attendees.

Abstract: Systems and methods for synchronizing data between a database system and its client applications are provided. After a regular synchronization, objects' records on a user computing device may be checked against a new sharing rule. Newly shared records may be synced down to the user computing device regardless of timestamps, and all records which the user no longer has access to may be removed from the user computing device. Consequently, data on the user computing device complies with the new sharing rule.