Adaptive data manager

• US 6,904,432 B2
• Filed: 11/30/2001
• Issued: 06/07/2005
• Est. Priority Date: 11/30/2001
• Status: Active Grant

• Current Assignee: Intelligent Medical Objects, Inc.
• Original Assignee: Intelligent Medical Objects, Inc.
• Inventors: Pilkington, David, Haines, David, Maldonado, Jose Jr., Charlot, Regis
• Primary Examiner(s): ALAM, SHAHID AL
• Application Number:
  US09/997,723
• Publication Number:
  US 20030200213A1
• Time in Patent Office: 1,285 Days
• Field of Search: 707/2, 707/3, 707/4, 707/9, 707/10, 707/101, 707/102, 709/217, 709/219, 709/225, 709/230, 705/8, 705/9, 705/30, 715/501.1, 715/513
• US Class Current: 1/1
• CPC Class Codes: G06F 16/25 Integrating or interfacing systems involving database management systems
• CPC Class Codes: Y10S 707/99939 Privileged access
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation

Abstract

A method for managing a back-end information storage infrastructure and a flexible development environment for data storage using a computer system. The method includes managing system resources including a relational database. Meta data models are created to model processes and to define meta data elements and their relationships by using trees and graphs. The method manages access to the data by authenticating users through a directory describing user rights, while providing management of multi-user access and concurrency. The method includes running the processes that generate instance data, storing the instance data following the meta data model, and transforming the instance data into physical views.

Claims

1. A method for managing a back-end information storage infrastructure and a flexible development environment for data storage using a computer system, comprising:

managing system resources including a relational database;

authenticating and selectively providing access to users through a directory describing predetermined user rights;

modeling processes to create a meta data model that encloses definitions of meta data elements and relationships among the elements using trees and graphs;

running the processes and generating instance data;

storing the instance data following the meta data model while providing management of multi-user access and concurrency; and

transforming the instance data into physical views.

2. A method in accordance with claim 1, further comprising optimizing the meta data model by optimally structuring the trees and graphs in the relational database.

3. A method in accordance with claim 1, wherein the relationships among the data elements are characteristic of the relationships between living organisms.

4. A method in accordance with claim 1, further comprising expanding the meta data model, as meta data expands, without effect on current applications.

5. A method in accordance with claim 2, wherein a plurality of concurrent meta data model trees with corresponding separate instance data trees are used in the same database.

6. A method in accordance with claim 1, further comprising auditing and tracking database changes with user and date information.

7. A method in accordance with claim 1, further comprising providing for import and export of both meta data model and instance data using extensible mark-up language.

8. A method in accordance with claim 1, wherein the database is an Oracle database and the transforming of instance data into a view comprises:

defining of the view by the user;

processing the view using traditional relational Oracle tables; and

allowing access of the view with any SQL enabled tool.