×

Health care payment adjudication and review system

  • US 5,359,509 A
  • Filed: 10/31/1991
  • Issued: 10/25/1994
  • Est. Priority Date: 10/31/1991
  • Status: Expired due to Term
First Claim
Patent Images

1. In a networked computer processing system including first processor means for executing computer programs and having an associated storage means for storing data and one or more second processor means for executing computer programs, each second processor having an associated storage means for storing data, each of the second processor means being operably connected to the first processor means, a method for processing and adjudicating health care payment requests comprising the steps of:

  • (a) providing the first processor means with database information stored in the storage means, including;

    (a1) a current payment request database having information relating to a plurality of outstanding health care payment requests, each health care payment request having one or more payment request line items corresponding to a specific medical procedure or supply for which payment is being requested;

    (a2) a historical payment request database having information relating to a plurality of previously stored health care payment requests;

    (a3) a plurality of procedure code list files, each of the procedure code list files having information relating to a certain medical procedure or supply and created according to one or more user-defined characteristics from a predefined complete set of medical procedures and supplies; and

    (a4) a class file having information relating to classification of the predefined complete set of medical procedures and supplies and created according to a predefined set of body systems;

    (b) providing each of the second processor means with an expert-based computer program including a set of user-defined rules and knowledge database information for the expert-based computer program stored in the storage means of the second processor means;

    (c) using the first processor means to perform the steps of;

    (c1) creating a payment request list from the current request database by selecting one or more payment request line items in response to a user-specified review code;

    (c2) creating a master list file by logically combining the plurality of procedure code list files with each other in response to the user-specified review code;

    (c3) for each payment request line item in the payment request list, creating a record in a communication file containing;

    (c31) information from the current payment request database relating to the payment request line item;

    (c32) information from the historical payment request database relating to a subset of relevant payment request line items selected from the historical payment request database;

    (c33) information from the master list file relating to the procedure or supply for which payment is being requested by the payment request line item; and

    (c34) information from the class file relating to the procedure or supply for which payment is being requested by the payment request line item; and

    (c4) communicating the communication file to one or more of the second processor means;

    (d) receiving the communication file and storing the communication file in the storage means of at least one of the second processor means and executing the expert-based computer program on the second processor means to perform the following steps for each payment request line item in the communication file;

    (d2) using the set of user-defined rules and knowledge database information to determine the consistency of '"'"'the payment request line item as compared to the information from the subset of relevant payment request line items selected from the historical payment database;

    (d2) using the set of user-defined rules and knowledge database information and the information from the master list file and the class file to determine the validity of the payment request line item;

    (d3) making a decision on whether to pay the payment request line item based upon the consistency and validity of the payment request line item and the set of user-defined rules and knowledge database information;

    (d4) if the payment request line item is to be paid, determining an amount of a payment for the payment request line item based upon the consistency and validity of the payment request line item and the set of user-defined rules and knowledge database information; and

    (d5) generating an updated communication file to be communicated to the first processor means, the updated communication file including;

    (d51) the decision on whether to pay each payment request line item in the communication file;

    (d52) the amount of the payment for each payment request line item in the communication file that is to be paid; and

    (d53) one or more items of coded information representing why the payment request line item is not to be paid for each payment request line item that is not to be paid; and

    (e) receiving the updated communication file from each of the one or more second processor means and using the first processor means to update the current request database to generate the historical request database.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×