Anomaly detector in a health care system using adapter

• US 20060085361A1
• Filed: 10/14/2004
• Published: 04/20/2006
• Est. Priority Date: 10/14/2004
• Status: Abandoned Application

• Current Assignee: Trizetto Group Incorporated (Cognizant Technology Solutions Corp.)
• Original Assignee: Trizetto Group Incorporated (Cognizant Technology Solutions Corp.)
• Inventors: Hoerle, Dale E., Hensley, Jeffery K.
• Application Number:
  US10/964,902
• Publication Number:
  US 20060085361A1
• Time in Patent Office: Days
• US Class Current: 705/75
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G16H 40/40 for the management of medical equipment or devices, e.g. scheduling maintenance or upgrades
• CPC Class Codes: G16Z 99/00 Subject matter not provided for in other main groups of this subclass

Abstract

Disclosed are systems and methods which provide for monitoring an interface for software applications, for logging transactions conducted using the interface, and/or validating the transactions performed. Embodiments utilize adapters which communicate with an adapter monitor to determine the status of the adapters and/or interfaces provided using the adapters. A monitoring tool may additionally or alternatively be used to provide reporting with respect to the status of the adapters and/or interfaces provided using the adapters.

Claims

1. A method comprising:

providing a copy of transaction information communicated in an interface between a first application program and a second application program to a validation process; and

updating, by said validation process, a validation database in accordance with said transaction information.

2. The method of claim 1, wherein said interface between said first application program and said second application program is provided using at least one adapter, wherein said providing a copy of said transaction information comprises:

detecting said transaction information as said transaction information passes through said at least one adapter; and

routing a copy of said transaction information to said validation process.

3. The method of claim 1, wherein said providing a copy of said transaction information comprises:

providing a copy of information associated with each transaction implemented between said first application program and said second application program using said interface.

4. The method of claim 1, wherein said providing a copy of said transaction information comprises:

providing a copy of selected information associated with transactions implemented between said first application program and said second application program using said interface.

5. The method of claim 1, wherein said providing a copy of said transaction information comprises:

providing a copy of information associated with selected transactions implemented between said first application program and said second application program using said interface.

6. The method of claim 1, further comprising:

verifying data associated with at least one of said first application program and said second application program using said validation database.

7. The method of claim 6, wherein said verifying data comprises:

comparing data of a data field of said validation database corresponding to a data field of a database associated with said at least one of said first application program and said second application program.

8. The method of claim 6, further comprising:

performing said verifying data periodically.

9. The method of claim 8, wherein a periodicity of said performing said verifying data is a function of the data verified.

10. The method of claim 6, further comprising:

performing said verifying data in response to an event.

11. The method of claim 10, wherein said event comprises having conducted a particular transaction.

12. The method of claim 10, wherein said event comprises at least a portion of said interface showing performance degradation.

13. The method of claim 10, wherein said event comprises at least a portion of said interface having failed.

14. The method of claim 6, further comprising:

reporting anomalies with respect to said data associated with at least one of said first application program and said second application program.

15. The method of claim 1, further comprising:

mapping data fields of said validation database to data fields of databases associated with said first application program and said second application program.

16. The method of claim 15, wherein said mapping data fields comprises:

mapping at least one data field to a data field of a database associated with said first application program and a data field of a database associated with said second application program.

17. A method for validating data altered in a transaction between software applications, said method comprising:

creating a validation database containing data fields corresponding to data fields of said software applications, said database being independent of said software applications;

updating a particular data field of said validation database in accordance with a transaction conducted between said software applications, said particular data field corresponding to a data field of at least one of said software applications being altered by said transaction; and

comparing said particular data field to said data field of said at least one software application.

18. The method of claim 17, wherein said data fields of said validation database include at least one data field corresponding to both a first software application and a second software application of said software applications.

19. The method of claim. 18, further comprising:

mapping said at least one data field to a corresponding data field of said first software application and to a corresponding data field of said second software application.

20. The method of claim 17, wherein said data fields of said validation database include data fields corresponding to each data field of said software applications.

21. The method of claim 17, wherein said data fields of said validation database include data fields corresponding to a subset of data fields of said software applications.

22. The method of claim 21, wherein data fields of said subset are selected as a function of the likelihood that data stored therein will be altered in a transaction between said software applications.

23. The method of claim 21, wherein data fields of said subset are selected as a function of the likelihood that data stored therein will be anomalous.

24. The method of claim 21, wherein data fields of said subset are selected as a function of the particular transactions operable to alter data stored therein.

25. The method of claim 21, wherein data fields of said subset are selected as a function of the criticality of data stored therein.

26. The method of claim 17, wherein said updating a particular field of said validation database comprises:

monitoring transactions conducted between said software applications using a software application interface.

27. The method of claim 26, wherein said software application interface comprises a plurality of adapters interfacing said software applications.

28. The method of claim 27, further comprising:

providing, by an adapter of said plurality of adapters, an object associated said transaction conducted between said software applications to a process operable to maintain said validation database.

29. The method of claim 17, further comprising:

updating a transaction log to include information with respect to said transaction conducted between said software applications.

30. The method of claim 17, further comprising:

updating a validation log to include information with respect to said comparing said particular data field.

31. The method of claim 17, wherein said particular data field corresponds to a data field of at least another one of said software applications being altered by said transaction, wherein said comparing said particular data field comprises:

comparing said particular data field to said data field of said at least another one of said software applications.

32. The method of claim 17, further comprising:

reporting an anomaly identified through said comparing said particular data field.

33. The method of claim 32, wherein said reporting comprises:

indicating a software application likely to have been the source of said anomaly.

34. The method of claim 32, wherein said reporting comprises:

indicating an adapter of a software interface likely to have been the source of said anomaly.

35. The method of claim 32, wherein said reporting comprises:

indicating a point to which data in said data field of said at least one software application should be rolled back to in order to avoid said anomaly.

36. A system for use in validating data altered in a transaction between software applications, said system comprising:

a validation database containing data fields corresponding to data fields of said software applications, said database being independent of and not accessible to said software applications; and

a validation process in communication with said validation database, said validation process receiving information regarding a transaction between at least a first software application and a second software application of said software applications and altering data of a particular data field of said validation database in accordance with said transaction information.

37. The system of claim 36, further comprising:

a first adapter associated with said first software application; and

a second adapter associated with said second software application, said first and second adapters cooperating to provide an interface between said first and second software applications, at least one of said first and second adapters being in communication with said validation process and providing said transaction information thereto.

38. The system of claim 37, further comprising:

a third adapter associated with at least one of said first and second software applications, said third adapter being in communication with said validation process and facilitating comparison of data of said particular data field of said validation database with data of said at least one of said fist and second software applications.

39. The system of claim 36, further comprising:

a transaction log storing information regarding said transaction between said first and second software applications.

40. The system of claim 39, wherein said information is selected from the group consisting of:

transaction temporal information;

identification of a software application involved in said transaction;

identification of an interface adapter involved in said transaction;

a business process associated with said transaction;

a function associated said transaction; and

performance metrics associated with completion of said transaction.

41. The system of claim 36, further comprising:

a monitoring tool in communication with said validation process, said monitoring tool reporting information with respect to anomalies in data fields of said software applications detected by said validation process using said validation database.

42. The system of claim 36, wherein said data fields of said validation database include at least one data field corresponding to each data field of a database of each said software application.

43. The system of claim 36, wherein said data fields of said validation database include data fields corresponding to selected data fields of databases of said software applications.

44. The system of claim 36, further comprising:

a data field map correlating said data fields of said validation database with one or more corresponding data fields of databases of said software applications.