Component based object-relational database infrastructure and user interface

• US 6,363,393 B1
• Filed: 02/22/1999
• Issued: 03/26/2002
• Est. Priority Date: 02/23/1998
• Status: Expired due to Term

• Current Assignee: Ron Ribitzky
• Original Assignee: Ron Ribitzky
• Inventors: Ribitzky, Ron
• Primary Examiner(s): Choules, Jack
• Assistant Examiner(s): LEWIS, CHERYL RENEA
• Application Number:
  US09/255,547
• Time in Patent Office: 1,128 Days
• Field of Search: 707/2, 707/3, 707/4, 707/10, 707/103, 707/102, 707/103.Y, 705/1-3, 705/4, 345/340, 345/348, 345/349, 345/762, 345/763, 345/781, 345/967, 345/968, 709/201, 709/203
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 99/00 Subject matter not provided for in other groups of this subclass
• CPC Class Codes: G16H 10/60 for patient-specific data, e.g. for electronic patient records
• CPC Class Codes: G16H 15/00 ICT specially adapted for medical reports, e.g. generation or transmission thereof
• CPC Class Codes: G16H 70/20 relating to practices or guidelines
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass
• CPC Class Codes: Y10S 707/99932 Access augmentation or optimizing
• CPC Class Codes: Y10S 707/99933 Query processing, i.e. searching
• CPC Class Codes: Y10S 707/99934 Query formulation, input preparation, or translation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99944 Object-oriented database structure
• CPC Class Codes: Y10S 715/967 Visual or iconic programming
• CPC Class Codes: Y10S 715/968 interface for database querying and retrieval

Abstract

The invention provides a system for accessing business data stored in one or more databases by a user. The system includes a means for presenting a user with a plurality of components with each component representing a discrete element of the business model, having a defined relationship with each other component, and including a plurality of information objects. Each information object represents an instance of the component business element and can be defined by a set of attributes and behaviors. The system further provides means for user selection of a first one of the plurality of components, for user selection of a first one of the plurality of information objects from the first component, and for instantiating the first information object. The user can then manipulate the first information object to cause the object to interact with any of the other components. The system then generates a report showing information objects of the other component which represent instances of the other component that are related to the first information object.

Claims

1. A system for accessing business da stored in one or more databases by a user comprising:

a) a display presenting a user with a plurality of components, each component representing a discrete element of a business model, having a defined relationship with each of a plurality of other components of the plurality of components, and including a plurality of information objects, each information object representing an instance of the component business element;

b) a user input device responsive to manipulation by a user to select a first one from among any of the plurality of components;

c) a user input device responsive to manipulation by a user to select a first one of the plurality of information objects from the first component;

d) software including control logic instantiating first information object from data stored in the one or more databases;

e) a user input device responsive to manipulation by a user to cause the first information object to interact with a second component selected from among any of a plurality of component other than the first component, the second component being selected from any one of the plurality of components other than the first component; and

f) control logic generating a report showing information objects of the second component which represent instances of the second component related to the first information object.

2. The system of claim 1, further comprising:

g) a user input device responsive to manipulation by a user to select a second information object from the set of information objects shown in the report.

3. The system of claim 2, further comprising:

h) control logic instantiating the second information object from data stored in the one or more databases.

4. The system of claim 1, wherein the plurality of components comprises at least three components.

5. The system of claim 1, wherein the plurality of components comprises at least five components.

6. The system of claim 5, wherein the components comprise client, problem, encounter, provider and service components to support a healthcare business model.

7. The system of claim 1, wherein an instantiated first information object is provided on the display and the user input device responsive to manipulation by a user to cause the first information object to interact with a second one of the plurality of components comprises a pointing device and control logic allowing the user to point to the first information object on the display and drag the first information object across the display to the second component.

8. The system of claim 7, wherein interacting a first information object with the encounter component generates a timeline report of encounters relating to the first information object.

9. The system of claim 1, further comprising a database infrastructure for implementing a relational data structure for supporting the business model, the database infrastructure comprising:

a) a relational data server for processing relational database requests;

b) an object relational server including a number of component servers at least equal to the number of components in the plurality of components, each component server corresponding to one of the plurality of comforts of business model and including means for communicating the relational data server to provide data services for its respective component;

c) a user interface server for displaying the components of the business model to a user and for supporting user manipulation of the components.

10. The system of claim 9, wherein the object-relational server further comprises a common component methods server for performing generic functions used by more than one component.

11. The system of claim 9, further comprising a document server for serving documents to the component servers.

12. The system of claim 11, wherein the document server includes means for viewing a word-processing document.

13. The system of claim 11, wherein the document server includes means for viewing a spreadsheet document.

14. The system of claim 9, further comprising a security server to authenticate users attempting to log in to the system.

15. The system of claim 9, wherein each component server includes scripts that create relational database management system tables to implement a relational data model for that component.

16. The system of claim 9, further comprising a gateway server for interfacing between the object relational server and external software applications supplying source data.

17. The system of claim 9, wherein the components comprise client, problem, encounter, provider and service components to support a healthcare business model.