Synchronized data-centric and document-centric knowledge management system for drug discovery and development

• US 20040249836A1
• Filed: 07/24/2003
• Published: 12/09/2004
• Est. Priority Date: 03/24/2003
• Status: Abandoned Application

• Current Assignee: Applied Biosystems LLC (Thermo Fisher Scientific Incorporated)
• Original Assignee: Applied Biosystems LLC (Thermo Fisher Scientific Incorporated)
• Inventors: Henderson, Scott, Reynders, John
• Application Number:
  US10/626,470
• Publication Number:
  US 20040249836A1
• Time in Patent Office: Days
• US Class Current: 707/100
• CPC Class Codes: G16H 10/20 for electronic clinical trials or questionnaires
• CPC Class Codes: G16H 70/40 relating to drugs, e.g. their side effects or intended usage

Abstract

The system maintains both a document-centric and a data-centric representation of data gathered during the ingest stage. Data ingest may be by internal instrument data capture, external data capture and/or manual data capture. Data is managed in a query-able form; communication among data processing modules is effected using XML. The system allows data to be cast to and from a variety of different domain-specific representations, for consumption by a variety of different domain-specific analysis stages.

Claims

1. A method for managing information used in the drug discovery process comprising:

receiving information from a plurality of sources;

obtaining a method to verify the integrity of the information;

converting the information to a common format that maintains synchronicity between a data-centric view of said information and a document-centric view of said information;

inputting the information in said common format to a workflow engine; and

receiving one or more outputs of said workflow engine.

2. The method of claim 1 further comprising:

archiving the information with a checksum after receiving from said plurality of sources.

3. The method of claim 1 wherein said workflow engine performs the following:

receiving a workflow comprising a set of user-defined steps for processing information;

receiving a plurality of data required for executing said workflow;

generating one or move views as specified by said workflow; and

publishing said one or more views.

4. A knowledge management data structure stored in a computer-readable memory or embodied in a carrier wave comprising:

a data object having the following attributes associated therewith;

(a) at least one workflow attribute;

(b) at least one composition attribute;

(c) at least one audit/version control attribute;

(d) at least one compliance attribute.

5. The data structure of claim 4 wherein said workflow attribute associates said data object with at least one workflow.

6. The data structure of claim 4 wherein said workflow attribute associates said data object with at least one workflow and associates said data object with at least one process step within said one workflow.

7. The data structure of claim 4 wherein said composition attribute associates said data object with at least one other data object in a belongs to relationship.

8. The data structure of claim 4 wherein said audit/version attribute associates said data object to a history log.

9. The data structure of claim 8 wherein said history log includes a timestamp indicia associated with said data object.

10. The data structure of claim 8 wherein said history log includes a digest record associated with said data object.

11. The data structure of claim 8 wherein said history log includes a pointer that said data object with at least one other data object with which said data object interacts.

12. The data structure of claim 8 wherein said history log includes an authorship authentication record associated with said data object.

13. The data structure of claim 4 wherein said compliance attribute associates said data object with at least one compliance object having associated compliance requirements.

14. The data structure of claim 13 wherein said compliance object represents said compliance requirements as a predefined schema.

15. An information entity stored in a computer-readable memory or embodied in a carrier wave comprising:

a data component to store information according to at least one predetermined data type;

said data component having at least one associated method used to perform an inquiry with respect to said stored information;

an audit component to store metadata associated with said stored information; and

an entity methods component used to perform document generation using said stored information.

16. The information entity of claim 15 wherein said information data component stores a plurality of different data types and stores a plurality of different methods used to perform inquires with respect to specified data types.

17. The information entity of claim 15 wherein said associated method performs an inquiry that transforms at least a portion of said stored information according to a predetermined method.

18. The information entity of claim 15 wherein said audit component stores audit methods used to operate upon said metadata.

19. The information entity of claim 15 wherein said audit component stores metadata that describes the manner in which the stored information has been processed.

20. The information entity of claim 15 wherein said associated method of said data component functions to provide a data-centric view of said information.

21. The information entity of claim 15 wherein said entity methods component functions to provide a document-centric view of said information.