SYSTEM AND METHOD FOR MEETING PAYER PROTOCOLS

• US 20080288280A1
• Filed: 05/15/2007
• Published: 11/20/2008
• Est. Priority Date: 05/15/2007
• Status: Abandoned Application

• Current Assignee: General Electric Company
• Original Assignee: General Electric Company
• Inventors: Bonissone, Piero Patrone, Subbu, Rajesh Venkat, Xue, Feng, Cheetham, William Estel, Ammer, Mary J., Belcher, Deborah J., Scholz, Bernhard Joseph
• Application Number:
  US11/748,611
• Publication Number:
  US 20080288280A1
• Time in Patent Office: Days
• US Class Current: 705/2
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G16H 70/60 relating to pathologies

Abstract

A system and method for processing healthcare service data is herein disclosed. The system comprising a decision engine in communication with a process manager and a knowledge source. The decision engine receives at least one protocol from the knowledge source that is derived by automated learning and applies the at least one protocol to healthcare service data and transmits a response to the process manager such that the response is indicative of a next workflow step to be taken.

Claims

1. A method of processing healthcare service data to determine if additional content data is required, the method comprising:

receiving healthcare service data;

receiving at least one protocol from at least one knowledge source comprising at least one protocol derived by automated learning from historical healthcare service data;

applying the at least one protocol to the healthcare service data to determine if additional content data is required to meet the at least one protocol;

generating a response indicative of the content data required to meet the at least one protocol, upon determining that additional content data is required; and

generating a response indicative of the next workflow step, upon determining that no additional content data is required.

2. The method of claim 1 further comprising producing an indication of a next workflow step to be taken in processing the healthcare service data.

3. The method of claim 2 further comprising:

applying at least one protocol to the healthcare service data to determine if the healthcare service data meets basic protocol requirements;

upon determining that the protocol does not meet basic protocol requirements, producing an indication of insufficient healthcare service data.

4. The method of claim 3 further comprising:

applying at least one protocol to the healthcare service data to determine if additional authorization is required; and

upon determining that additional authorization is required, producing an indication indicative of the additional authorization required.

5. The method of claim 4 further comprising:

applying at least one protocol to the healthcare service data to determine if additional content data is required;

providing an indication of the next workflow step if no additional content data is required; and

providing an indication of the required content data if additional content data is required.

6. The method of claim 5 further comprising:

providing an indication of the type of content data that is required if the type of required content data is known; and

providing a generic indication that content data is required if the type of required content data is not known.

7. The method of claim 1 wherein the healthcare service data comprises at least:

care delivery organization identification data, service data, and payer identification data.

8. A decision engine for use in conjunction with an automated system including a process manager for processing healthcare service data for a healthcare data transaction, the decision engine comprising:

a knowledge source in communication with at least one database of stored historical healthcare service data, the knowledge source identifying at least one protocol derived by automated learning from historical healthcare service data, the protocol defining a content data requirement for a healthcare data transaction; and

a means for applying at least one protocol to the healthcare service data, the means for applying being in communication with the knowledge source and in communication with the process manager such that healthcare service data is received from the process manager, the means for applying determining any required additional healthcare service or content data and transmitting a response indicative of the required additional content data to the process manager.

9. The decision engine of claim 8 wherein the knowledge source comprises a case-based reasoning module.

10. The decision engine of claim 9 wherein the case-based reasoning module processes the historical healthcare service data to identify matched cases, analyzing the matched cases, and identifying protocols based on the analysis of the matched cases.

11. The decision engine of claim 10 wherein the case-based reasoning module identifies strict match cases and identifies similarity matched cases.

12. The decision engine of claim 10 wherein the case-based reasoning module create new protocols and modifies existing protocols based on the analyzed matched cases.

13. The decision engine of claim 8 wherein the knowledge source identifies at least one protocol using a statistical analysis of the historical healthcare service data.

14. The decision engine of claim 8 wherein the knowledge source codifies at least one protocol using fuzzy logic.

15. The decision engine of claim 8 wherein the knowledge source codifies at least one protocol using a decision tree.

16. The decision engine of claim 8 wherein the at least one protocol identifies the required content data by identifying at least one symbol associated with the content data.

17. The decision engine of claim 16 wherein the symbol associated with the content data is a LOINC code.

18. A healthcare data management system for processing healthcare service data to identify required content data to be sent to a payer, the system comprising:

an input device facilitating the entry of healthcare service data to be used in a healthcare data transaction;

a process manager in communication with the input device, the process manager receiving the healthcare service data;

a knowledge source in communication with at least one database of healthcare service data, the knowledge source identifying at least one protocol by automated learning from the healthcare service data, the protocol defining a content data requirement;

a decision engine in communication with the process manager and in communication with the knowledge source such that the decision engine receives the healthcare service data from the process manager, receives at least one protocol from the knowledge source, applies the at least one protocol to the healthcare service data to produce a response indicative of required content data, and transmits the response to the process manager; and

an output device in communication with the process manager such that the output device receives the response from the process manager and indicates a workflow step to be performed in accordance with the response.

19. The system of claim 18 wherein the knowledge source further comprises a knowledge database, the knowledge database comprising a plurality of protocols.

20. The system of claim 19 wherein the knowledge database comprises protocols defined by at least one payer, at least one care delivery organization, and at least one third party.

21. The system of claim 19 wherein the knowledge source comprises a case-based reasoning module.

22. The system of claim 18 wherein the response indicates a workflow step to be performed.

23. The system of claim 22 wherein the indication of a workflow step comprises the visual display of a manual action to be taken.