Managing protocol amendments in electronically recorded clinical trials

• US 8,065,347 B1
• Filed: 12/21/2007
• Issued: 11/22/2011
• Est. Priority Date: 12/21/2006
• Status: Active Grant

• Current Assignee: CinPhone PLC, ClinPhone Plc (Parexel International Corporation)
• Original Assignee: ClinPhone Plc (Parexel International Corporation)
• Inventors: Wijnker, Dennis, DeMeyer, Chris, Kochanski, Dennis, Dixon, Ron, Lowe, Nathan, Iriumi, Hayato
• Primary Examiner(s): Trujillo; James
• Assistant Examiner(s): Spieler; William
• Application Number:
  US11/963,767
• Time in Patent Office: 1,432 Days
• Field of Search: 707/806, 707/941, 707/705, 707/999.1, 707/809
• US Class Current: 707/806
• CPC Class Codes: G06F 16/217 Database tuning G06F16/2282 takes precedence; database performance monitoring G06F11/3409
• CPC Class Codes: G16H 10/20 for electronic clinical trials or questionnaires
• CPC Class Codes: G16H 40/67 for remote operation

Abstract

A clinical trial management system and associated methods are provided to manage individual clinical trials running under multiple protocols at once. The disclosure allows clinical trials to be amended during the course of the study with reduced risk of loss of time or data. Patients may be started under one clinical trial protocol and be moved to another upon approval from the doctor or hospital managing their involvement in the study. In an embodiment, patient data is not moved or altered during a change in protocol to provide a more secure clinical trial system.

Claims

1. A clinical trial management system comprising:

a central processor for accepting clinical trial data comprising first clinical trial data and second clinical trial data;

at least one database for storing the clinical trial data;

at least one set of metadata defining a first version of a protocol for a single clinical trial, wherein the central processor uses the at least one set of metadata to manage at least some of the clinical trial data; and

a staging and publishing module for accepting an additional set of metadata defining a second version of the protocol for the single clinical trial,

wherein;

the staging and publishing module adds data elements associated with the additional set of metadata to the at least one database, and

the central processor concurrently manages the first clinical trial data for the single clinical trial according to at least one set of metadata of the at least one set of metadata defining the first version of the protocol and the second clinical trial data for the single clinical trial according to the additional set of metadata defining the second version of the protocol.

2. The clinical trial management system of claim 1, wherein:

the staging and publishing module comprises software instructions executed on the central processor.

3. The clinical trial management system of claim 2, wherein the staging and publishing module is capable of comparing the at least one set of metadata defining the first version of the protocol to the additional set of metadata defining the second version of the protocol and generating a report defining differences between the first version and the second version.

6. The clinical trial management system of claim 1, wherein the added data elements comprise data collected for patients.

7. The clinical trial management system of claim 1, wherein the central processor concurrently manages the accepted clinical trial data for the single clinical trial by:

determining at least one patient associated with the accepted clinical trial data; and

instructing the at least one database to store the accepted clinical trial data based, at least in part, on whether the at least one patient is associated with the first version or the second version of the protocol.

4. A method of concurrently managing multiple versions of a clinical trial protocol for a single clinical trial, the steps of the method comprising:

storing a first metadata file defining a first version of the protocol for the single clinical trial, wherein the first version defines at least one clinical data element to be stored in a database;

accepting at least one data element for storage as defined by the first metadata file;

accepting a second metadata file defining a second version of the protocol for the single clinical trial;

updating the database to store at least one clinical data element according to the second version;

tracking an association of each patient of a set of patients in the single clinical trial with the first or second version of the protocol;

determining whether a first patient of the set of patients is associated with the first or second version of the protocol; and

storing data regarding the first patient of the set of patients according to the first version or the second version according to the association tracked for the first patient.

5. The method of claim 4, wherein the step of updating the database maintains all of the at least one clinical data element definitions of the first version.

8. A method of staging a second version of a clinical trial protocol in a single clinical trial associated with a first version of the clinical trial protocol for the single clinical trial, the steps of the method comprising:

retrieving a first metadata file defining the first version of the protocol for the single clinical trial;

accepting a second metadata file defining the second version of the protocol for the single clinical trial;

comparing the first metadata file to the second metadata file; and

generating a report of differences between the first and second metadata files.

9. A method of migrating patient records from a first version of a clinical trial protocol to a second version of the protocol for a single clinical trial, wherein a patient record includes at least one data store having at least one original data element and at least one metadata table defining the at least one data store and having at least one reference to the at least one data store, the steps of the method comprising:

adding a new data element to the at least one data store as required by the second version;

updating the at least one metadata table as required by the second version;

running, in response to updating the at least one metadata table, queries and derivations as required by the second version;

wherein the steps of adding, updating, and running preserve the at least one original data element in the at least one data store.

10. The method of migrating patient records of claim 9, wherein the step of updating the at least one metadata table includes adding an additional reference to the data store.

11. The method of migrating patient records of claim 9, wherein the step of updating the at least one metadata table includes changing the at least one reference to refer to the new data element.

12. The method of migrating patient records of claim 9, wherein the at least one metadata table comprises definitional entries and reference entries referring to the at least one data store'"'"'s at least one data element;

and

the step of updating the at least one metadata table preserves definitional entries.

13. The method of migrating patient records of claim 9, wherein the at least one reference to the at least one data store comprises a pointer.