System and method for data storage, control and access

• US 20030208490A1
• Filed: 06/10/2002
• Published: 11/06/2003
• Est. Priority Date: 06/15/2001
• Status: Abandoned Application

• Current Assignee: PHI Technologies Incorporated, Redtop Company LLC
• Original Assignee: PHI Technologies Incorporated
• Inventors: Goldhagen, Benjamin I., Larrea, Jean-Jacques, OʼToole, Michael J., Grimmelmann, Erik K.
• Application Number:
  US10/166,118
• Publication Number:
  US 20030208490A1
• Time in Patent Office: Days
• US Class Current: 707/9
• CPC Class Codes: G06F 16/252 between a Database Management System and a front-end application
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation

Abstract

The present disclosure relates to a system and method for improved data (or information) storage, control and/or access. A system/method according to the disclosure facilitates enhanced versioning of data files, data records, information, and the like, such that subsequent data file and/or record retrieval is consistent with and reflective of ancillary conditions at the time of the data file and/or record input. The system/method provides enhanced data/information storage, control and access that have applicability in a variety of fields, including applications related to health care, mental health care, financial and accounting systems, industrial control systems, and the like.

Claims

1. A system for managing information, comprising:

a database for storage of information;

at least one user interface for accessing information contained within and for supplying information to the database;

a processor in communication with the database and responsive to input from said at least one user interface, said processor being programmed to;

a) process data entries that are submitted by way of said at least one user interface for input to said database, each said data entry being processed as a transaction;

b) effectuate irrepudiability as to each said processed transaction, such that each said processed transaction is not modifiable;

c) identify a producer responsible for submitting said processed transaction with said processed transaction in said database; and

d) version data contained within said database such that a state of said database at a point in time reflects all processed transactions, applied in sequence as of said point in time.

2. A system according to claim 1, wherein said transaction involves data entry associated with creation of a file, modification of a file or deletion of a file.

3. A system according to claim 1, wherein said processor incorporates meta-data into said transaction to identify said producer with said processed transaction.

4. A system according to claim 1, wherein said processor incorporates meta-data into said transaction to reflect information related to said transaction, said related information being selected from the group consisting of an author'"'"'s identity for said transaction, an effective date for information contained in said data entry, an attestation made by said author of said transaction, a creator'"'"'s identity for said transaction, a modality of transmission of said information to said creator, a date of transmission of said information to said creator, and an attestation by said creator.

5. A system according to claim 1, wherein said processor is further programmed to identify a chain of responsibility for information contained within said processed transaction, said chain of responsibility being incorporated as meta-data into said processed transaction.

6. A system according to claim 5, wherein said chain of responsibility includes an identification of an entity responsible for at least one of the following tasks:

acquiring said information, entering said information at the user interface, coding said information, translating said information, converting said information, and aggregating said information.

7. A system according to claim 6, wherein said entity is a human contributor, a non-human contributor, or a combination thereof.

8. A system according to claim 1, wherein said immutability of each said processed transaction permits modification of said processed transaction through controlled maintenance operations.

9. A system according to claim 1, wherein said state of said database at a point in time reflects infrastructure associated with processing of each of the processed transactions.

10. A system according to claim 9, wherein said infrastructure includes software codes, reference data and resources.

11. A system according to claim 10, wherein said reference data is selected from the group consisting of lookup tables, data input templates, data input menus, data input trees, and combinations thereof, and wherein said resources are selected from the group consisting of fonts, colors, formats, and computer hardware that includes workstations, network cards, network cables and communications links, and combinations thereof.

12. A system according to claim 10, wherein said infrastructure is associated with said processed transaction based on a unique reference or a unique pointer incorporated into said database.

13. A system according to claim 1, wherein said data entries relate to a healthcare information system, a mental healthcare information system, a behavioral health system, a financial system, an accounting system, a billing system, a design system, an inventory system, an industrial control system, a registration system or an enrollment system.

14. A system according to claim 1, wherein said data entries reflect information concerning a patient selected from the group consisting of the patient'"'"'s medical history, treatment history, treatment approach, diagnosis, demographic information, medication and combinations thereof.

15. A system according to claim 1, wherein said processor is programmed to operate a presentation manager and a data manager.

16. A system according to claim 15, wherein said presentation manager functions to dynamically generate application screens for viewing and user interaction at said at least one user interface.

17. A system according to claim 15, wherein said data manager functions to process said data entries, effectuate irrepudiability as to each said processed transaction, identify said producer responsible for submitting said processed transaction, and version data contained within said database, and further functions to:

a) manage communications with the database;

b) manage updates to the database;

c) provide local, per user caching of data; and

d) provide data consistency despite data changes effectuated during a user session.

18. A system according to claim 1, wherein said database includes at least one structured vocabulary associated with the subject matter of the data entries.

19. A method for managing information, comprising:

receiving a data file via a computer network;

processing the data file to include meta-data that reflects information concerning the producer of the data file and ancillary information required to recreate the data file at a future point in time, said processed data file defining a transaction; and

storing the transaction in a database.

20. A method according to claim 19, wherein the ancillary information is selected from the group consisting of software codes, information on which the transaction was based, data views, maximum version reference, hardware configuration and combinations thereof.

21. A method according to claim 19, wherein the ancillary information is directly incorporated in the transaction as a collection of Java objects.

22. A method according to claim 19, wherein the data file is related to health care, mental health care, a financial or accounting system, or an industrial control system.