System and method for interacting with clinical trial operational data

• US 20090319535A1
• Filed: 06/20/2008
• Published: 12/24/2009
• Est. Priority Date: 06/20/2008
• Status: Abandoned Application

• Current Assignee: BioClinica, Inc.
• Original Assignee: BioClinica, Inc.
• Inventors: Webber, Robert C., Rehm, Jeremiah
• Application Number:
  US12/214,763
• Publication Number:
  US 20090319535A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application

Abstract

The current method and system allow sharing and integrating clinical trial operational data for easy accessibility of operational data, reusable predefined field identifiers and operational data for context and tables, and centralized use of operational data for conducting clinical trials based on semantics as well as syntax for consistency. The current system and method manage a plurality of clinical trial-related applications by creating a plurality of tables stored within the shared database of the shared database system for updating and sharing among clinical trials. The tables are logically organized by a plurality of operational data, and each table contains predefined data field identifiers associated with the plurality of operational data. The current system and method configure the plurality of clinical trial-related applications associated with the plurality of operational data as a producer or a consumer of the operational data to maintain consistency among the plurality of clinical trial-related applications without requiring a format to reuse the operational data for different clinical trials. The current system and method provide a centralized clinical trial operational data hub with transactional acknowledgment recording and sequence verification. The current system and method also provide a centralized clinical trial operational data hub with approval workflow, audit trail information, and reporting.

Claims

1. A method for interacting with clinical trial operational data using a plurality of shared server interacting applications in a shared server of a shared database system, comprising:

creating a plurality of tables wherein the tables are organized by clinical trial operational data and each table has predefined data field identifiers stored in a shared database;

receiving at least one operational data from a first shared server interacting application wherein the at least one operational data is collected during a clinical trial;

accessing a first table containing its predefined data field identifiers from the shared database with the first table being identifiable with the at least one operational data;

updating the first table by associating the at least one operational data from the first shared server interacting application with the predefined data field identifiers of the first table;

receiving at least one change in operational data from a second shared server interacting application;

accessing a second table containing its predefined data field identifiers from the shared database with the second table being identifiable with the at least one change in operational data;

updating the second table by associating the at least one change in operational data from the second shared server interacting application with the predefined data field identifiers of the second table; and

interacting with the plurality of shared server interacting applications wherein the plurality of tables with the at least one change in operational data are handled;

wherein the shared database system provides consistent and reusable operational data for the plurality of shared server interacting applications.

2. The method of claim 1, further comprising the step of configuring each of the plurality of shared server interacting applications associated with the operational data as either a producer or a consumer of the operational data to maintain consistency among the plurality of shared server interacting applications for reusability of the operational data between clinical trials.

3. The method of claim 1, further comprising the steps of, prior to receiving the at least one operational data from the first shared server interacting application:

launching a user interface for the first shared server interacting application;

inputting at least one operational data from the user interface; and

displaying a first table view on the user interface of the at least one operational data associated with the predefined data field identifiers.

4. The method of claim 1, wherein the step of updating the first table by associating the at least one operational data with the predefined data field identifiers of the first table comprising adding at least one row of data under the predefined data field identifiers in column headings.

5. The method of claim 1, wherein the step of updating the second table by associating the at least one change in operational data with the predefined data field identifiers of the second table comprising at least one step selected from the group consisting of:

adding the at least one row of data;

deleting the at least one row of data; and

modifying the at least one row of data under the predefined data field identifiers of the second table in column headings.

6. The method of claim 1, wherein the step of receiving at least one operational data from the first shared server interacting application further comprising the step of receiving at least one operational data from at least one shared server interacting application selected from the group consisting of:

Clinical Trial Management Systems, Clinical Trial Management Systems, Clinical Data Management System, Electronic Data Capture, Clinical Trial Manager, Clinical Payment Manager, Laboratory Information Management Systems, Interactive Voice Response Systems, Safety Applications, eSubmission Applications, eDiary Applications, Medical Imaging Applications, other applications designed to be used in clinical trials, Statistical Analysis Systems, Customer Relationship Management, Personal Information Management System, Enterprise Resource Planning System, Manufacturing Execution Systems, financial and accounting systems, customized applications for clinical trials, and other applications provided within a business enterprise software environment.

7. The method of claim 1, further comprising the step of connecting a plurality of linked server interacting applications to the shared server via a plurality of linked servers, further comprising the steps of:

receiving a message to update at least one table;

determining if any changes occurred to the at least one table in the shared database since an immediately previous synchronization of operational data;

creating a response message with the changes in the at least one table; and

sending the response message with the changes in the at least one table during next synchronization of operational data.

8. The method of claim 7, further comprising, prior to receiving the message to update the at least one table:

accessing a configuration user interface of one of the plurality of the linked servers;

optionally configuring a discovery function to allow selection of data source information and context information;

selecting from the data source information of tables to be discovered from the shared database;

selecting from the context information of predefined data field identifiers within the selected tables to be discovered from the shared database;

enabling synchronization and selecting synchronization time interval; and

applying configuration parameters.

9. The method of claim 7, wherein the step of creating the response message with the changes in the at least one table further comprising the following steps to be performed after the discovery function is configured:

retrieving tables previously selected by an administrator from the data source information of the configuration user interface; and

retrieving rows of data within the selected tables that match with predefined data field identifiers previously selected by the administrator from the context information.

10. The method of claim 7, wherein the step of receiving a message to update at least one table further comprising the step of receiving at least one message from at least one linked server interacting application selected from the group consisting of:

Statistical Analysis Systems, Customer Relationship Management, Personal Information Management System, Enterprise Resource Planning System, financial and accounting systems, analysis and reports of information derived from the common tables that assist in management of the clinical trial process, and other business applications designed to assist in business solutions.

11. The method of claim 1, further comprising, prior to updating the first table or the second table:

reviewing approver information already stored in the shared database;

contacting a first approver with the at least one operational data;

contacting a second approver with the at least one change;

storing response information from the first approver and response information from the second approver for the at least operational data and the at least one change; and

sending the response information from the first approver and the second approver as an acknowledgment message.

13. The shared database system of claim 10, a shared server interacting application is at least one of the plurality of shared server interacting applications selected from the group consisting of:

Clinical Trial Management Systems, Clinical Trial Management Systems, Clinical Data Management System, Electronic Data Capture, Clinical Trial Manager, Clinical Payment Manager, Laboratory Information Management Systems, Interactive Voice Response Systems, Safety Applications, eSubmission Applications, eDiary Applications, Medical Imaging Applications, other applications designed to be used in clinical trials, Statistical Analysis Systems, Customer Relationship Management, Personal Information Management System, Enterprise Resource Planning System, Manufacturing Execution Systems, financial and accounting systems, customized applications for clinical trials, and other applications provided within a business enterprise software environment.

12. A shared database system for interacting with a plurality of shared server interacting applications in handling clinical trial operational data, the shared database system comprising:

a shared database having a plurality of tables stored thereon, wherein the tables are organized by a plurality of operational data and each table contains predefined data field identifiers associated with the plurality of operational data; and

a computer program for communicating with the plurality of shared server interacting applications in updating the plurality of operational data associated with the predefined data field identifiers in the plurality of tables.

14. The shared database system of claim 12, each of the plurality of tables contains the predefined data field identifiers in a column headings portion and the plurality of operational data of rows are populated under the predefined data field identifiers.

15. The shared database system of claim 12, the computer program associates each of the plurality of operational data with the predefined data field identifiers within a table, wherein the plurality of operational data is selected from the group consisting of addition, deletion, and modification of rows under the predefined data field identifiers within the table.

16. The shared database system of claim 12, the computer program further comprising an approver module for contacting at least one approver prior to updating the plurality of tables associated with the operational data under the predefined data field identifiers in the shared database.

17. A shared database system for interacting with clinical trial operational data with a plurality of linked server interacting applications via a plurality of linked servers connected to a shared server comprising:

a shared database having a plurality of tables wherein the tables are organized by a plurality of operational data and each table has predefined data field identifiers associated with the plurality of operational data;

a computer program in the shared server for executing instructions to synchronize with at least one linked server;

a linked server database in the linked server for storing the plurality of tables with the plurality of operational data received from the shared server after synchronization;

a linked server computer program in the linked server for executing instructions to synchronize with the shared server; and

a configuration user interface for an administrator to set configuration parameters between the shared server and at least one of the plurality of linked servers.

18. The shared database system of claim 17, a linked server interacting application is at least one of the plurality of linked server interacting applications selected from the group consisting of:

Statistical Analysis Systems, Customer Relationship Management, Personal Information Management System, Enterprise Resource Planning System, financial and accounting systems, analysis and reports of information derived from the common tables that assist in management of the clinical trial process, and other business applications designed to assist in business solutions.

19. The shared database system of claim 17, wherein the computer program in the shared server includes an access module for sending, receiving, and updating the plurality of tables with at least one change in operational data.

20. The shared database system of claim 17, wherein the computer program in the shared server optionally includes a discovery module and a data source module for determining the at least one change in the operational data and retrieving only selected tables and operational data matching with selected predefined data field identifiers for synchronization.

21. A computer-readable storage medium having executable instructions for causing a shared server to interact with clinical trial operational data from a plurality of shared server interacting applications, the shared server comprising computer-readable program code for causing the shared server to:

connect with the plurality of shared server interacting applications;

receive at least one change in operational data, the operational data input by a user interacting with a user interface launched for at least one of the plurality of shared server interacting applications;

detect the at least one change in the operational data from at least one table as stored in a shared database;

update the at least one table in the shared database with the at least one change in the operational data;

store the at least one table in the shared database with the at least one change in the operational data; and

receive more changes in operational data from another shared server interacting application wherein the more changes in operational data are handled; and

wherein a shared database system provides consistent and reusable operational data for the plurality of shared server interacting applications.

22. The computer-readable storage medium of claim 21, further comprising computer-readable program code for causing the shared server to configure the plurality of shared server interacting applications associated with the plurality of operational data as a producer or a consumer of the operational data to maintain consistency among the plurality of shared server interacting applications without requiring a format to reuse the plurality of operational data.

23. The computer-readable storage medium of claim 21, further comprising computer-readable program code for causing the shared server, prior to updating the at least one table in the shared database, to:

store approver information in the shared database;

review the approver information related to the at least one change in the operational data;

contact at least one approver with the at least one change in the operational data;

store approver response information regarding the at least one change in the operational data; and

send the approver response information regarding the at least one change in the operational data in an acknowledgment message;

wherein the approver information associated with each operational data is generated in a table view.

24. The computer-readable storage medium of claim 21, further comprising computer-readable program code for causing the shared server to provide consistent table views associating the plurality of operational data with predefined data field identifiers within the table.

25. The computer-readable storage medium of claim 21, further comprising a computer-readable program code for causing the shared server to:

connect with at least one linked server through which a plurality of linked server interacting applications are accessing the shared server via the at least one linked server;

synchronize with the at least one linked server to send any tables of operational data;

wait to receive an update request;

receive the update request from the at least one linked server to update one or more tables;

determine if any changes occurred to the at least one table in the shared database since a previous synchronization of operational data;

create a response message with the changes in the at least one table; and

send the response message with the changes in the at least one table during next synchronization of operational data.

26. The computer-readable storage medium of claim 25, further comprising computer-readable program code for causing the shared server to configure the plurality of linked server interacting applications associated with the plurality of operational data as a producer or a consumer of the operational data to maintain consistency among the plurality of linked server interacting applications without requiring a format to reuse the plurality of operational data.

27. The computer-readable storage medium of claim 21, further comprising computer-readable program code for causing the shared server to provide a centralized clinical trial operational data hub with transactional acknowledgment recording and sequence verification.

28. The computer-readable storage medium of claim 21, further comprising computer-readable program code for causing the shared server to provide a centralized clinical trial operational data hub with approval workflow, audit trail information and reporting.