Enterprise framework and applications supporting meta-data and data traceability requirements

• US 7,016,919 B2
• Filed: 03/29/2002
• Issued: 03/21/2006
• Est. Priority Date: 03/29/2002
• Status: Expired due to Fees

• Current Assignee: Agilent Technologies, Inc.
• Original Assignee: Agilent Technologies, Inc.
• Inventors: VanSant, Mary Jane, Cotton, Todd, Konitzer, Robert, Gardner, Karen M.
• Primary Examiner(s): Gaffin, Jeffrey
• Assistant Examiner(s): Wu, Yicun
• Application Number:
  US10/112,291
• Publication Number:
  US 20030187821A1
• Time in Patent Office: 1,453 Days
• Field of Search: 707/1, 707/2, 707/3, 707/4, 707/5, 707/6, 707/7, 707/8, 707/9, 707/10, 707/104.1, 709/229, 709/202, 715/513, 715/840, 713/168, 705/59
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99948 Application of database or data structure, e.g. distributed, multimedia, or image

Abstract

An application adapted to run within an enterprise wide, web-based framework which provides reusable services and facilities such as security, meta-data management and traceability of data and a framework supporting the same. The framework supports decision making across the value chain, with an emphasis on the meta-data needed for decision making. The framework can support the activities of a virtual organization (internal or external) and the inevitable variations in data types, file formats etc. without requiring massive integration between the various sources of data involved.

Claims

1. A method of managing data within an enterprise-wide, web-based framework said method comprising the steps of:

marking up data to be managed within the framework with predefined types of meta-data;

submitting the marked up data to the framework;

assigning a unique identifier to be associated with the data and a location in which the data is to be stored;

storing the unique identifier and location for subsequent access to the data;

assigning a unique primary key to each item of meta-data associated with the data;

storing each item of meta-data with its unique primary key, type of meta-data and the unique identifier connecting the item of meta-data with the data;

providing a hierarchy of dossiers into which artifacts, defined by the meta-data stored, are classified;

defining at least one specified role, team or users;

defining which of the dossiers each user, role or team will be entitled to access;

defining a level of entitlement that each user, role and team has with regard to each dossier, wherein a level of entitlement may be selected from a read only level;

a read and edit level;

a read, edit and submit new data level;

a read, edit and export data level; and

a read, edit, submit new data and export level;

allowing a user, role or team access to only those dossiers which the user, role or team has been defined to be entitled to, and only at the entitlement level defined;

allowing users, roles or teams which are entitled to write to a dossier containing the stored meta-data linked to the submitted data to submit new versions of the data, write annotations to the data, or mark the data for deletion;

generating an event for each new version of the data, each annotation to the data, or each marking of the data for deletion;

wherein each of these functions is stored with the mete-data associated with the data and is linked to the unique identifier of the data;

storing each event with an associated time stamp;

wherein the submission of marked up data generates an event, and wherein other predefined manipulations of the data generate events; and

generating a traceability report based on the events, thereby creating a history of all events that have occurred with regard to the data.

2. The method of claim 1, further comprising the step of:

assigning a unique entitlement token to a user upon sign in for access to me framework, wherein the unique entitlement token is good only for the session, and deleting the unique entitlement token upon sign off.

3. The method of claim 1, further comprising rejecting the submitted data prior to said assigning and staring steps if all items of meta-data required by a schema defining the submission have not been entered with the data.

4. The method of claim 1, further comprising rejecting the submitted data prior to said assigning and storing steps if the user submitting the data is not entitled to submit data.

5. The method of claim 1, further comprising the step of:

preventing any overwriting, alteration, editing or deletion of the data and meta-data once the unique identifier has been stored.

6. The method of claim 1, further comprising

allowing annotations to be written with regard to the submitted data by a user with entitlement, and storing the annotations with the meta-data.

7. The method of claim 1, further comprising the step of:

searching on the stored meta-data associated with artifacts selected by a user from a dossier among those dossiers which the user is entitled to, thereby defining a subset of the data collected in the dossier.

8. The method of claim 7, further comprising the step of:

selecting a predefined template from a collection of templates; and

assembling select portions of the subset of data into the selected template.

9. The method of claim 8, further comprising the step of storing the template containing select portions of data as a new artifact, and linking the new artifact to unique identifiers of the select portions of data.

10. The method of claim 8, further comprising the step of exporting the template containing select portions of data to the users local drive.

11. The method of claim 1, wherein users, roles or teams which are entitled to write to a dossier containing the stored meta-data linked to the submitted data can submit new versions of the data, write annotations to the data, or mark the data for deletion;

wherein each of these functions generates an event, and wherein each of these functions is stored with the meta-data associated with the data and is linked to the unique identifier of the data.

12. The method of claim 11, wherein the submission of marked up data also generates an event, and wherein other predefined manipulations of the data generate events, each event being stored with an associated time stamp.

13. The method of claim 12, further comprising the step of generating a fraceability report based on the events, thereby creating a history of all events that have occurred with regard to the data.

14. A method of managing data within an enterprise-wide, web-based framework, said method comprising the steps of:

marking up data to be managed within the framework with predefined types of meta-data;

submitting the marked up data to the framework;

assigning a unique identifier to be associated with the data and a location in which the data is to be stored;

storing the unique identifier and location for subsequent access to the data;

assigning a unique primary key to each item of meta-data associated with lie data;

storing each item of meta-data with its unique primary key, type of meta-data and the unique identifier connecting the item of meta-data with the data;

providing a hierarchy of dossiers into which artifacts, defined by the meta-data stored, are classified;

defining at least one specified role, team or users;

defining which of the dossiers each user, role or team will be entitled to access;

defining a level of entitlement that each user, role and team has with regard to each dossier, wherein a level of entitlement may be selected from a read only level;

a read and edit level;

a read, edit and submit new data level;

a read, edit and export data level; and

a read, edit, submit new data and export level;

allowing a user, role or team access to only those dossiers which the user. role or team has been defined to be entitied to, and only at the entitlement level defined;

searching on the stored meta-data associated with artifacts selected by a user from a dossier among those dossiers which the user is entitled to, thereby defining a subset of the data collected in the dossier; and

assembling select portions of the subset of data into a template, wherein the template is 21 C.F.R. 11 compliant.

15. A method of managing data within an enterprise-wide, web-based framework, said method comprising the steps of:

marking up data to be managed within the framework with predefined types of mete-data;

submitting the marked up data to the framework;

assigning a unique identifier to be associated with the data and a location in which the data is to be stored;

storing the unique identifier and location for subsequent access to the data;

assigning a unique primary key to each item of meta-data associated with the data;

storing each item of meta-data with its unique primary key, type of meta-data and the unique identifier connecting the item of meta-data with the data;

providing a hierarchy of dossiers into which artifacts, defined by the meta-data stored, are classified;

defining at least one specified role, team or users;

defining which of the dossiers each user, role or team will be entitled to access;

defining a level of entitlement that each user, role and team has with regard to each dossier, wherein a level of entitlement may be selected from a read only level;

a read and edit level;

a read, edit and submit new data level;

a read, edit and export data level; and

a read, edit, submit new data and export level;

allowing a user, role or team access to only those dossiers which the user, role or team has been defined to be entitled to, and only at the entitlement level defined;

searching on the stored meta-data associated with artifacts selected by a user from a dossier among those dossiers which the user is entitled to, thereby defining a subset of the data collected in the dossler; and

assembling select portions of the subset of data into a template, wherein the template is formatted to comply with requirements for the submission of an Investigational New Drug submission to the FDA.

16. An application adapted to run within an enterprise wide, web-based framework, said application comprising:

a schema requiring predefined types of mete-data to be marked up with new data to be submitted to the framework;

means for assigning a unique identifier to each new data submitted;

means for assigning an address outside of the framework where the new data will be stored;

means for storing the unique identifier associated with the address;

means for assigning primary keys to each item of meta-data associated with the new data and storing each item of meta data associated with its primary key, type of meta-data and a foreign key which points to the unique identifier;

means for creating a hierarchical classification of dossiers;

means for assigning data to a selected dossier;

means for defining user entitlement to each dossier created, wherein a system administrator establishes users, roles and teams and defines which of the dossiers each specific user, role or team is entitled to access;

means for preventing access to data in a dossier which a user, role or team is not entitled to access; and

means for identifying and searching on information that a user wishes to associate with data selected from a dossier that the user is entitled to, wherein said means for identifying and searching comprises means for formulating a Boolean search based on a preselected dossier or group of dossiers and one or more types of stored meta-data, annotations associated with stored meta-data or stored meta-data and said annotations.

17. The application of claim 16, further comprising:

means for generating an event each time new data is submitted and each time annotations, alterations, or new versions of the data are entered into the application;

means for linking the events to the unique identifier of the associated data; and

means for storing the events and linking unique identifiers.

18. The application of claim 17, further comprising:

means for generating a traceability report of the entire history of an artifact of data, based on searching the events generated and stored with regard to that data.

19. The application of claim 16, further comprising:

means for creating a hierarchical classification of dossiers;

means for assigning data to a selected dossier;

means for defining user entitlement to each dossier created, wherein a system administrator establishes users, roles and teams and defines which of the dossiers each specific user, role or team is entitled to access; and

means for preventing access to data in a dossier which a user, role or team is not entitled to access.

20. The application of claim 19, further comprising:

means for creating a personal dossier at the user level, which a user can create and manage and which can be shared by other users having entitlement thereto.

21. The application of claim 19, further comprising:

means for identifying and searching on information that a user wishes to associate with data selected from a dossier that the user is entitled to.

22. The application of claim 21, wherein said means for identifying and searching comprises means for performing a similarity search on meta-data associated with the data to find values within a predefined range of a search value.

23. The application of claim 21, wherein said means for identifying and searching comprises means for formulating a Boolean search based on a preselected dossier or group of dossiers and one or more types of stored meta-data, annotations associated with stored meta-data or stored meta-data and said annotations.

24. The application of claim 16, further comprising front means, said front means providing a single point of access to the application for all users.

25. The application of claim 19, further comprising means for assembling selected data into a template.

26. The application of claim 25, further comprising means for exporting the data assembled into a template from the application.