System and method for storing user data in a centralized database and intelligently reducing data entry

• US 20080098000A1
• Filed: 10/23/2006
• Published: 04/24/2008
• Est. Priority Date: 10/23/2006
• Status: Abandoned Application

• Current Assignee: Adventive, Inc. (BlueTie, Inc.)
• Original Assignee: BlueTie, Inc.
• Inventors: Koretz, David A., Simpson, James, Wong, Stephen, Chamberlin, Rob
• Application Number:
  US11/584,640
• Publication Number:
  US 20080098000A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

A method and system for storing user-specific information in a centralized database and reducing data entry by intelligently determining what data is already stored in the centralized database and what data needs to be collected from the user. The method includes receiving a request from a user of a user computing system to initiate a transaction, wherein the transaction requires user-specific information in at least one associated field to complete the transaction, and receiving a request from a service provider system for the user-specific information. The method further includes providing the service provider system with the user-specific information when the user-specific information is stored in the centralized database, and, when the user-specific information is not stored in the centralized database, requesting the user-specific information from the user computing system, receiving the user-specific information from the user computing system, and storing the user-specific information received from user computing system in the centralized database.

Claims

1. A method for completing a transaction using user-specific information stored in a centralized database, the method comprising:

receiving a request from a user of a user computing system to initiate a transaction, wherein the transaction requires user-specific information in at least one associated field to complete the transaction;

receiving a request from a service provider system for the user-specific information;

providing the service provider system with the user-specific information when the user-specific information is stored in the centralized database;

requesting the user-specific information from the user computing system when the user-specific information is not stored in the centralized database;

receiving the user-specific information from the user computing system when the user-specific information is not stored in the centralized database; and

storing the user-specific information received from user computing system in the centralized database when the user-specific information is not stored in the centralized database.

2. The method of claim 1, further comprising identifying the user-specific information required for the transaction.

3. The method of claim 1, wherein a user provides the user-specific information not stored in the centralized database via the user computing system.

4. The method of claim 1, wherein the user-specific information sent to the service provider system is limited to only the user-specific information needed to complete the current transaction.

5. The method of claim 4, wherein a user is notified that user-specific information data is being transferred to the service provider system to protect their privacy and data security.

6. The method of claim 1, further comprising publishing the centralized database to a central server on a network after the user-specific information is received from the user computing system and stored in the centralized database.

7. The method of claim 1, further comprising a master list of all fields stored in the centralized database.

8. The method of claim 7, wherein the service provider system is operable to map all existing fields to the master list.

9. The method of claim 7, wherein the master list is in a standardized format.

10. The method of claim 9, wherein the standardized format is XML.

11. The method of claim 1, wherein the service provider system completes the transaction without receiving any user-specific information from the user computing system when all of the needed user-specific information is already stored in the centralized database.

12. The method of claim 11, wherein the transaction is completed without providing any of the user-specific information to the user computing system.

13. The method of claim 1, wherein a user of the user computing system chooses to have the transaction completed without receiving any user-specific information from the application provider system when all of the needed user-specific information is already stored in the centralized database.

14. A computer readable medium having stored thereon instructions for storing user-specific information in a centralized database comprising machine executable code which when executed by at least one processor, causes the processor to perform steps comprising:

receiving a request from a user of a user computing system to initiate a transaction, wherein the transaction requires user-specific information in at least one associated field to complete the transaction;

receiving a request from a service provider system for the user-specific information;

providing the service provider system with the user-specific information when the user-specific information is stored in the centralized database;

requesting the user-specific information from the user computing system when the user-specific information is not stored in the centralized database;

receiving the user-specific information from the user computing system when the user-specific information is not stored in the centralized database; and

storing the user-specific information received from user computing system in the centralized database when the user-specific information is not stored in the centralized database.

15. The computer readable medium of claim 14, further comprising machine executable code which when executed by at least one processor, causes the processor to perform a step of identifying the user-specific information required for the transaction.

16. The computer readable medium of claim 14, wherein a user provides the user-specific information not stored in the centralized database via the user computing system.

17. The computer readable medium of claim 14, wherein the user-specific information sent to the service provider system is limited to only the user-specific information needed to complete the current transaction.

18. The computer readable medium of claim 17, wherein a user is notified that user-specific information data is being transferred to the service provider system to protect their privacy and data security.

19. The computer readable medium of claim 14, further comprising machine executable code which when executed by at least one processor, causes the processor to perform a step of publishing the centralized database to a central server on a network after the user-specific information is received from the user computing system and stored in the centralized database.

20. The computer readable medium of claim 14, further comprising a master list of all fields stored in the centralized database.

21. The computer readable medium of claim 20, wherein the service provider system is operable to map all existing fields to the master list.

22. The computer readable medium of claim 20, wherein the master list is in a standardized format.

23. The computer readable medium of claim 22, wherein the standardized format is XML.

24. The computer readable medium of claim 14, wherein the service provider system completes the transaction without receiving any user-specific information from the user computing system when all of the needed user-specific information is already stored in the centralized database.

25. The computer readable medium of claim 24, wherein the transaction is completed without providing any of the user-specific information to the user computing system.

26. The computer readable medium of claim 14, wherein a user of the user computing system chooses to have the transaction completed without receiving any user-specific information from the application provider system when all of the needed user-specific information is already stored in the centralized database.

27. A system for storing user-specific information in a centralized database, the system comprising:

a user computing system operable to initiate a transaction, wherein the transaction requires user-specific information in at least one associated field to complete the transaction;

an application provider system comprising a centralized database operable to store user-specific information associated with at least one field; and

a service provider system operable to request user-specific information from the application provider system;

wherein the application provider system provides the user-specific information to the service provider system when the user-specific information is stored in the centralized database of the application provider system,

wherein the application provider system requests the user-specific information from the user computing system when the user-specific information is not stored in the centralized database;

wherein the application provider system receives the user-specific information from the user computing system when the user-specific information is not stored in the centralized database, and wherein the application provider system stores the user-specific information in the centralized database when the user-specific information is not stored in the centralized database.

28. The system of claim 27, wherein the user-specific information required for the transaction is identified.

29. The system of claim 27, wherein a user provides the user-specific information not stored in the centralized database via the user computing system.

30. The system of claim 27, wherein the user-specific information sent to the service provider system is limited to only the user-specific information needed to complete the current transaction.

31. The system of claim 30, wherein a user is notified that user-specific information data is being transferred to the service provider system to protect their privacy and data security.

32. The system of claim 27, wherein the centralized database is published to a central server on a network after the user-specific information is received from the user computing system and stored in the centralized database.

33. The system of claim 27, further comprising a master list of all fields stored in the centralized database.

34. The system of claim 33, wherein the service provider system is operable to map all existing fields to the master list.

35. The system of claim 33, wherein the master list is in a standardized format.

36. The system of claim 35, wherein the standardized format is XML.

37. The system of claim 27, wherein the service provider system completes the transaction without receiving any user-specific information from the user computing system when all of the needed user-specific information is already stored in the centralized database.

38. The system of claim 37, wherein the transaction is completed without providing any of the user-specific information to the user computing system.

39. The system of claim 27, wherein a user of the user computing system chooses to have the transaction completed without receiving any user-specific information from the application provider system when all of the needed user-specific information is already stored in the centralized database.