System and user interface supporting use of rules for processing healthcare and other claim data

[0001] This is a non-provisional application of provisional application serial No. 60/371,027 by D. Fitzgerald et al. filed Apr. 9, 2002 and of provisional application serial No. 60/372,764 by D. Fitzgerald et al. filed Apr. 12, 2002.

FIELD OF THE INVENTION

[0002] This invention concerns a system and user interface for use in determining, applying and managing rules in processing claim data for payment for provision of services to patients by a healthcare provider, for example.

BACKGROUND OF THE INVENTION

[0003] An important function performed by healthcare providers (such as hospitals, clinics or physicians) is the sending of claims to healthcare payer institutions to obtain reimbursement for provision of services to a patient. These claims may be in electronic or paper format. Paper claims typically go through a data entry process that converts them to an electronic format. The entered electronic claims are usually sorted, indexed and archived. Each claim is processed in a payer institution adjudication system. The payer adjudication system interprets the claim data and determines whether or not the claim is to be paid in full, partially paid or denied. This adjudication process may be fully automated, partially automated, or manual. The results of claim adjudication may include the issuance of a check and an explanation of benefits (EOB) to the insured and healthcare provider, or a request to send additional information. The process of reviewing claims is labor-intensive and error-prone.

[0004] In known systems, healthcare claim payer organizations provide healthcare providers with definitions of rules that are to be applied by payers in adjudicating claims submitted by healthcare providers. This means healthcare providers locally re-create and implement their own rules (that ideally mirror the payer rules) for use in creating claims and for establishing admission and treatment procedures that provide information compatible with rule requirements. However, a healthcare provider needs to interpret the rule definitions provided by a payer organization in order to implement rules locally. Further, a healthcare provider also needs to implement and apply claim processing rules derived from other sources such as from Regulatory institutions (such as a CCI—correct coding initiative rule) and from the healthcare provider itself (e.g., a rule to write-off small outstanding balances).

[0005] One known rules processing system operates as an adjunct to clinical systems to provide alerts and to help prevent medical errors. This rules processing system also provides suggestions to a user to reduce healthcare provider and payer organization costs such as by recommending a switch to cheaper alternative medications or to switch from an intravenous medication to an equivalent pill form, for example. Other rule processing systems approach rules from the claims perspective, developing claims editing applications to “scrub” claims prior to their electronic or manual submission. Another rule processing system provides a separate compliancy checking engine. In typical known rule processing systems, a healthcare provider establishes its own set of rules to address local and payer requirements using limited rule processing automation in ensuring patient claims are accurate before submission to a payer. This poses a set up, maintenance and compliance verification burden for an individual provider organization.

[0006] The known rule processing systems exhibit a number of problems that are compounded by the fragmentary, distributed and isolated nature of the rule databases employed by these systems. Specifically, problems arise in accurately trying to implement healthcare payer organization defined rules, in maintaining the rules, in processing rules employing variable format and syntax, in ensuring the latest rule versions are employed and in applying rules in a consistent manner. This results in claims that fail the edit process upon receipt by the payer and consequent disallowance by the payer. Disallowed claims cause delayed payment and negatively impact healthcare provider cash flow and patient satisfaction with the process. A system according to invention principles improves rule processing to enhance claim accuracy prior to claim submission to a healthcare payer institution.

SUMMARY OF INVENTION

[0007] A centralized rules repository maintains consistently expressed rules used to process patient claim data in supporting medical procedure eligibility verification, patient referrals, treatment authorization, data entry editing, electronic claim submission, claim status determination and electronic remittance processing. A system for managing rules used for processing claim data related to provision of healthcare to a patient includes an interface processor for acquiring data representing rules from a plurality of different sources. The system includes a rules repository for accumulating data representing acquired rules and a rules processor for initiating application of a selected rule derived from the repository to process claim data in response to a received message. A result processor for processing a result derived by the application of the selected rule to the claim data for output.

BRIEF DESCRIPTION OF THE DRAWING

[0008]FIG. 1 shows an overall claim data processing system employing rules processing, according to invention principles.

[0009]FIG. 2 shows a rules processing system used in the overall claim processing system of FIG. 1, according to invention principles

[0010]FIG. 3 shows a flowchart of a process employed in rules processing by the systems of FIGS. 1 and 2, according to invention principles.

[0011]FIG. 4 shows a user interface display image illustrating a patient claim billing record for multiple patient encounters with a healthcare provider concerning treatment of an injury, according to invention principles.

[0012]FIG. 5 shows a user interface display image illustrating a rule profile for a hospital <b>500</b> indicating rules and tests selected to be applied in processing patient claim data, according to invention principles.

[0013]FIG. 6 shows a user interface display image illustrating results of applying exemplary rules in processing claim data and identifying claim rejection reasons by description and rejection code, according to invention principles.

[0014]FIG. 7 shows a flowchart of a process employed in deriving and amending rules in response to claim adjudication results from a payer organization, according to invention principles.

[0015]FIG. 8 shows a user interface display image illustrating an exemplary rule code language common syntax format for issuing an alert in response to particular occurrences, according to invention principles.

[0016]FIG. 9 shows a user interface display image illustrating another exemplary rule code language common syntax format used in processing claim data, according to invention principles.

[0017]FIG. 10 shows a user interface display image illustrating claim processing results and identifying claim rejection reasons by description and rejection code, according to invention principles.

[0018] FIGS. <b>11</b>-<b>17</b> show data records including data elements incorporated in a central data repository used in claim processing, according to invention principles.

DETAILED DESCRIPTION OF INVENTION

[0019]FIG. 1 shows an overall claim processing system employing trial adjudication to improve claim accuracy prior to claim submission to a healthcare payer institution or other entity. In the FIG. 1 system, continuously updated centralized common rules in repository <b>74</b> are employed to ensure that individual healthcare providers, as well as individual healthcare payer institutions are working with the most up-to-date version of the rules. Use of centralized rules ensures that a healthcare provider is able to comply with the latest provisions of the rules. A rule as used herein comprises a procedure (including an executable procedure or a procedure implemented with manual intervention) for determining that healthcare claim elements comply with predetermined requirements including, health plan reimbursement conditions, health plan format requirements, a reimbursement formula, reimbursement constraints and a reimbursement computation procedure. A rule also may comprise a prescribed guide, a precept, or a model for how to present, conduct or regulate an action by using a form and data or the relations between form and data. In other embodiments, the rules repositories described herein may also be arranged as a single repository or multiple repositories in a different arrangement. Further, an exception as used herein encompasses the identification of an issue and mechanism to process that issue and claim elements as used herein may comprise a portion of a claim, a complete claim, individual records of a claim and record data associated with an individual patient encounter with a healthcare service provider. In addition a window as used herein comprises an image area used for display of desired text or graphics or other content to a user and is not limited to a Microsoft or any other particular operating environment.

[0020] Centralized rules repository <b>74</b> enables consistency in consolidation and communication of rule sets across participants in the healthcare industry. Rules repository <b>74</b> contains up to date current rules for checking by unit <b>50</b> and execution by unit <b>46</b>. The rules are expressed in a standard syntax and process standard claim data identifiers and value sets to ensure compatibility with multiple application platforms and health enterprises. The system of FIG. 1 supports collecting and combining rules across multiple healthcare entities for processing healthcare patient encounter information and associated claim data to ensure claim accuracy. An encounter as used herein comprises a patient encounter with a healthcare enterprise involving patient and healthcare enterprise interaction that has a financial or transaction consequence and may include for example a patient visit, phone call, inpatient stay or outpatient treatment etc. Centralized rules repository <b>74</b> ensures that system participants stay compliant with rapidly changing rules and regulations. Further, the use of clinical event-driven application of rules when needed (rather than sequential processing after the fact) gives confidence that requested actions occur without unexpected, late or retroactive claim denials occurring. Rules change frequently and especially in response to the introduction of new technology, procedures, and medications. Repository <b>74</b> advantageously maintains effective validity dates and decommissioning dates for rules as well as a record of obsolete or out-of date rules. Further, the selection and operation of rules in processing claim data is affected by particular dates associated with a patient healthcare encounter such as an admission date, birth date, discharge date, and treatment date.

[0021] The FIG. 1 system invokes rules to automate the pre-registration, eligibility, registration authorization, claim generation, trial adjudication, claim submission, payment remittance, and post-remittance processes of a health care claim data processing cycle to provide seamless, accurate and prompt claim processing. The system facilitates coordination of employer and payer activities and ensures that pre-visit enrollee data is accurate. Thereby, if a patient uses a consumer portal (<b>24</b>) to schedule a visit or if a healthcare facility collects insurance information from a patient, medical necessity, referral and eligibility verification processing is automatically initiated. A claim is evaluated for accuracy and edited by a rule execution function <b>46</b> and adjudication unit <b>48</b>, using the applicable rules in rules repository <b>74</b>, both before the claim is completed (i.e. as individual claim elements for individual healthcare encounters post to the claim, for example) and again before the completed claim is submitted for payment. A variety of portals <b>20</b>-<b>28</b> in the FIG. 1 system are controlled and administered by interface <b>10</b> to provide claim data access to patients, payers, providers, employers and government agencies. The system facilitates healthcare provider compliance with governmental and payer rules through use of automated, rules-based editing and review systems.

[0022] The FIG. 1 system automatically employs rules from repository <b>74</b> to edit claim data to ensure claims are error free. The system also advantageously performs claim trial adjudication (pre-processing) using the rules to validate that edited collated claim data is in condition for submission for actual adjudication by a payer institution to initiate generation of payment. A failure in trial adjudication automatically initiates deficiency correction or manual intervention via scheduling of a worklist task to be performed by expert personnel. Upon successful trial adjudication, the claim data is automatically re-queued for electronic submission to the payer. Payment advice is processed electronically without manual intervention and automatically posted to an appropriate account.

[0023] The FIG. 1 system comprises functions implemented in software applications and executable procedures for processing claim data. These functions may also be implemented in hardware or a combination of both hardware and software resident in one or more computer systems and servers and involving one or more communication networks for internal and external communication. The system processes claim data related to provision of healthcare to a patient by collating data related to a claim for a particular patient for submission to a payer. The collated claim data is submitted for pre-processing using rules to validate the collated claim data is in condition for processing to initiate generation of payment. Upon successful validation the validated claim data is submitted to a payer. The claim data is collated by data acquisition unit <b>32</b> via interface <b>10</b> for storage in data repository <b>68</b>. Repository <b>68</b> contains financial and clinical data related to healthcare encounters that are currently ongoing. Data acquisition unit <b>32</b> is able to receive both solicited and unsolicited data from multiple different sources and to request data from these sources via interface <b>10</b>. The different sources include external users (participants) subscribing to and using the FIG. 1 system and may include for example, healthcare providers, healthcare payer institutions (e.g. insurance companies, Health Maintenance Organizations—HMOs etc.), consumers, employers, and government agencies.

[0024] Data keeper unit <b>64</b> acts as a gateway and data management system governing data storage and retrieval for healthcare data repository <b>68</b> and processing requests to use repository <b>68</b> to store, modify, and retrieve data. Data keeper unit <b>64</b> also tracks data changes in repository <b>68</b> by recording time, date and nature of changes made as well as the source and identity of the author of the changes to maintain a data update audit trial. Historian unit <b>70</b> is used in archiving and maintaining older data value versions and is specifically used in archiving data records associated with patient encounters following completion of financial transactions (i.e. encounters for which no related financial transactions are outstanding) and processing for these encounters. Records of such encounters are maintained by data keeper unit <b>64</b> in repository <b>68</b>. Historian unit <b>70</b> stores archived data in archive (data warehouse) database <b>72</b>.

[0025] The collated claim data is submitted for pre-processing by trial adjudicator <b>48</b> using rules to validate the collated claim data is in condition for processing to initiate generation of payment. Trial adjudicator <b>48</b> initiates execution of a sub-set of rules executed by rule execution unit <b>46</b>. Unit <b>46</b> detects the occurrence of an event triggering application of associated rules and executes the rules associated with that event. An event may include receipt of data to add to the repository <b>68</b>, a request to execute a specified list of rules, and an event triggered by the activities of a function within the FIG. 1 system. A rule executed by unit <b>46</b> may itself generate a triggering event and initiate execution of other rules. An individual rule may contain a test resulting in assignment of a result status of “True” or “False” upon execution of a rule. An individual rule may also contain lists of actions to be performed upon a true result and alternate actions to perform upon a false result, for example. The list of actions may include, creation of worklists of tasks for automatic or manual performance, creation of logs and audit reports and accounting reports, creation of error reports, generation of claims, posting of remittances, modification of data, and other actions. Data Morpher unit <b>44</b> comprises a sub-category of actions that rules invoke to modify data in repository <b>68</b> in response to command. Unit <b>46</b> also processes and executes rules stored in the Relationship Rules Repository <b>118</b> that contains rules required and used by the Protector <b>12</b>, Translator <b>14</b>, and Transporter <b>16</b> during communication involving interface <b>10</b>.

[0026] The rules executed by trial adjudication unit <b>48</b> determine expected adjudication results when a specified set of claim data is submitted to a specified payer. Unit <b>48</b> uses rules retrieved from repository <b>74</b> (or from rule accessor <b>52</b>) via rule keeper interface <b>66</b> to predict the result of submitting a specified set of claim data to a specified payer. For this purpose the rules used by unit <b>48</b> replicate the rules used by the selected specific payer. Unit <b>48</b> identifies conditions that would lead to denial of payment and enables such conditions to be fixed (automatically or with manual intervention) before a claim is submitted to a designated payer. This procedure advantageously facilitates the creation of error-free claims using rules derived from repository <b>74</b> or using remotely accessed rules. Rules including regulatory guidelines and directives are continuously acquired for storage in repository <b>74</b> and are continuously updated and maintained in this repository via rules keeper unit <b>66</b>. Rules repository <b>74</b> incorporates healthcare data rules that employ a universal catalog of code-sets listing physician identifiers and patient relationships and govern how data is to appear in an electronic form, image or other presentation. These rules include format rules that determine data formatting and use a universal catalog of implementation guides including form UB92 requirements, electronic version 6 or ANSI 837p version 4010 requirements including selectable date formats (e.g., mm-dd-yyyy or yyyy-mm-dd, etc.). Repository <b>74</b> also includes healthcare compliancy rules that are mandated by regulators and employ a universal catalog of code-sets like diagnosis codes, correct coding initiative requirements as well as Ambulatory Patient Groups (APGs) and Diagnosis Related Groups (DRGs) patient classification systems. Repository <b>74</b> also includes lists identifying rule names, grouping sets of rules together and specifying rule sets to be executed sequentially and also includes business or other rules facilitating business operations. System connectivity rules are also retained in repository <b>74</b> and also in relationship rules repository <b>18</b> (in support of communication via interface <b>10</b>). Such connectivity rules support e-commerce communication (e.g., use FTP@2400 k baud to a certain node name) or determine a communication mode (e.g., prompt a user to e-mail to ask questions or probe a response). Other rules detect inconsistency between data fields such as data fields retaining a telephone number, zip code, address or other geographical identifier of the collated claim data.

[0027] Rules archiving unit <b>76</b> in conjunction with unit <b>66</b>, dates and time stamps rules to be archived and stores obsolete, expired or older version rules in archive (rules warehouse) database <b>78</b>. Archived rules are accessible and usable to determine an outcome based on submission of particular claim data for adjudication using rules in force at a date in the past, for example. Repository <b>74</b> contains adjudication rules acquired from payer institution participants and rules that are established from previous transactions with payers. Repository <b>74</b> also contains rules developed by the system and by authorized participants that add automated processes to the system. Pattern creator unit <b>38</b> creates specialized rules that define surveillance research processes and rule maker unit <b>56</b> is used to create general purpose rules.

[0028] Unit <b>48</b> uses rules in repository <b>74</b> derived from external rule sources (such as rules <b>62</b> owned by a payer institution <b>60</b>) by rule accessor <b>52</b> via interface <b>10</b> and data network <b>58</b>. Network <b>58</b> may comprise a conventional network such a LAN (local area network), WAN (wide area network) or the Internet or alternatively may comprise a network service such as a clearinghouse or other service used by a healthcare payer or a healthcare provider to facilitate data and rule (e.g., payer rules <b>62</b>) acquisition for claim adjudication. Payer rules <b>62</b> are rules promulgated by a payer <b>60</b> that are not accessible through the automated process managed by Rule acquisition unit <b>54</b>. Rather rules <b>62</b> are manually determined through manual acquisition processes and are parsed and analyzed by Rule acquisition unit <b>54</b> by using a user interface provided by rule maker unit <b>56</b>. The Rule Maker <b>56</b> user interface supports manual creation, review and update of rules including those acquired via unit <b>54</b>. Unit <b>56</b> also prompts a user with lists of available tests and actions and guides the user through the process of constructing and editing rules prior to storing the edited rules in Rules Repository <b>74</b>.

[0029] Rule acquisition unit <b>54</b> accumulates rule data based on adjudication outcomes of prior claim submissions to payer institutions and through documentation and other information provided by payers that do not provide access to their proprietary programmed rule sets to external users. Unit <b>54</b> retrieves payer generated information bulletins from payer websites and other sources and analyzes this material to identify information representing new rules for incorporation in repository <b>74</b> and to identify rules that have expired. Further, individual payer institutions may use Payer Portal <b>22</b> to communicate rule information via interface <b>10</b> to acquisition unit <b>54</b> which incorporates them using rule keeper unit <b>66</b> in repository <b>74</b>. Unit <b>54</b> also receives new rules following user manual data entry and processing via a user interface provided by rule maker <b>56</b> based on information acquired from payers by rules gatherer service <b>80</b>. Payers forward updated rule information to service <b>80</b> in advance of implementing a new rule or rule version, for example. Service <b>80</b> supports user creation of implementable definitions of these new or updated rules using Rule Maker user interface <b>56</b> for incorporation in rules repository <b>74</b>. Service <b>80</b> also monitors claim rejection issues and rates of adjudication success and failure and supports adjustment or creation of rules to resolve identified issues. Rule Checker unit <b>50</b> monitors rules in repository <b>74</b> and identifies and indicates to a user those rules that are incomplete or contain incorrect syntax. Unit <b>50</b> also reports combinations of rules that are mutually inconsistent. Further, in response to identification of a predetermined exception condition during claim data processing by rule execution unit <b>46</b> and trial adjudication unit <b>48</b>, exception tracker function <b>42</b> employs a sub-set of rules managing the processing and reporting of an identified exception condition. Exception tracker function <b>42</b> may be invoked by rule execution unit <b>46</b> in response to execution of a particular rule or upon a particular result of executing a rule. Upon determination of an exception condition, function <b>42</b> may schedule manual intervention, via a user interface or a worklist or by communicating a report or message to a recipient, for example.

[0030] Trial adjudicator <b>48</b> uses rule accessor <b>52</b> to submit claim data for trial adjudication by remotely located rules. These remotely located rules may be maintained (and owned) by a different entity (such as a payer institution) to the owner of the FIG. 1 system. A payer who owns such rules establishes a procedure for receiving claim data for trial adjudication and responds with a report indicating how the submitted claim data would be adjudicated using the payer owned rules.

[0031]FIG. 2 shows a rules processing system including server based rule functions (specifically rule functions <b>18</b>, <b>46</b>, <b>50</b>, <b>52</b>, <b>54</b>, <b>56</b>) used in the overall claim processing system of FIG. 1. As previously described, unit <b>46</b> executes rules derived from repository <b>74</b> via interface <b>66</b> in processing patient claim data. The rules in repository <b>74</b> are derived from external rule sources (such as rules <b>62</b> owned by a payer institution <b>60</b>—FIG. 1) by rule accessor <b>52</b> via interface <b>10</b> and data network <b>58</b> (FIG. 1). Rule acquisition unit <b>54</b> parses and analyzes acquired rules (derived by rules gatherer service <b>80</b> and manual entry and other means) using a user interface provided by rule maker unit <b>56</b> in the manner previously described in connection with FIG. 1. Relationship Rules Repository <b>18</b> contains rules required and used by the Protector <b>12</b>, Translator <b>14</b>, and Transporter <b>16</b> during communication involving interface <b>10</b> and other rules used in establishing communication.

[0032]FIG. 3 shows a flowchart of a process employed by the system of FIG. 1 in claim processing. In step <b>303</b>, after the start at step <b>300</b>, units <b>52</b> and <b>54</b> (FIG. 1) intermittently interrogate multiple different sources to acquire, new rules and updates of existing rule held in repository <b>74</b>. The different sources include, payer organizations, messages provided by payer organizations, payer organization websites, regulatory guidelines and a source of rules created in response to previously identified claim data deficiencies. In step <b>307</b> unit <b>56</b> initiates generation of user interface display images supporting creation of a rule for use in processing healthcare claim data. Specifically, unit <b>56</b> initiates generation of displayed image windows including prompt elements permitting user selection of a rule or a test to be performed on claim data as part of a created rule. The test is selected from available predetermined tests. Another image element permits user identification of a source of claim data to be processed by a created rule and a further image element supports user initiation of validation of a created rule to verify the created rule complies with predetermined criteria. An additional image element supports generation of text hints for display to a user to guide a user in creating a rule. Unit <b>56</b> also initiates generation of a window including a prompt element permitting user selection of a resultant action to be performed in response to application of a created rule to claim data and a window for displaying the created rule.

[0033] In step <b>309</b>, rule maker <b>56</b> derives a rule based on information concerning outcomes of previous adjudication of other sets of claim data. This outcome information is acquired by service <b>80</b> from payers or from monitoring claim rejection issues and rates of adjudication success and failure and supports adjustment or creation of rules to resolve identified issues. An individual rule may contain one or more tests to identify a true condition and initiate an associated first set of actions or a false condition and initiate an associated second set of actions. A rule test condition may be simple or complex involving a combination of tests linked with logical operators (e.g., “and,” “or,” “not”). Individual linked tests results are logically combined to provide an overall test true or false result. Unit <b>66</b> in step <b>311</b> assigns a time period of validity to both a rule and individual test components incorporated by the individual rule. Rules and tests are stored together with associated time and date stamp indicators of duration of validity in repository <b>74</b>. In step <b>315</b>, rules repository <b>74</b> also associates a particular rule with an event including, for example, (a) the generation of a record for incorporation in claim data for a patient, (b) the detection of a record addition to claim data for a patient, (c) the detection of a record addition to a patient billing record, (d) the detection of a change in a patient billing record and (e) the detection of a change in claim data for a patient.

[0034] Unit <b>56</b>, in step <b>317</b>, parses and transforms data representing acquired and derived rules to a syntax suitable for storage in repository <b>74</b>. For this purpose, unit <b>56</b> parses data representing acquired rules in converting the acquired rules to a common syntax using predetermined identifiers and predetermined value sets. FIG. 8 shows a user interface display image illustrating an exemplary rule code language common syntax format for a rule used to process claim data of a hospital (<b>870</b>) to issue an alert in response to particular occurrences. Specifically, a rule <b>860</b> employs a common If-EndIf statement language syntax. This is used identify occurrences of both Occurrence code <b>41</b> and Value Code <b>30</b> (items <b>863</b> and <b>867</b> respectively) in claim representative data and to initiate generation of a warning message to a user in response to such an identification. Similarly, FIG. 9 shows a user interface display image illustrating another exemplary rule code language common syntax format used in processing claim data. Specifically, a rule <b>790</b> employs a multi-level common nested If-EndIf statement language syntax. This is used to identify whether there is a secondary procedure code in claim representative data that indicates a claim entry is associated with an injury due to a vehicular accident. If no such procedure code is present the rule adds procedure code P01.09 as well as a procedure date equal to the admission date. The “x” counter (i.e., x=0 statement of line 1 of rule <b>790</b>) ensures that this routine is run once.

[0035] Units <b>52</b> and <b>54</b> in step <b>319</b> accumulate data representing acquired and derived rules in repository <b>74</b> via rule interface unit <b>66</b>. Rule checker <b>50</b>, in step <b>321</b>, validates acquired and derived rules to verify the rules are internally consistent, formatted in a desired syntax and are not inconsistent with other rules in repository <b>74</b>. In step <b>323</b> unit <b>56</b> manages update of rules repository <b>74</b> and maintains a record of a first date of validity of a rule, a last date of validity of a rule and a date identifying when a rule is changed. In response to receiving a message identifying an event in step <b>325</b>, unit <b>46</b> in step <b>327</b> initiates application of a particular rule associated with the event (see step <b>315</b>) to process collated claim data derived from data repository <b>68</b> and related to a claim of a particular patient. However, unit <b>46</b> examines rule validity periods and does not execute a rule or test component at a time and date falling outside of a period of validity. FIG. 4 shows a user interface display image illustrating a claim billing record for a particular patient (the patient is identified by item <b>420</b>). The billing record includes collated claim data for multiple patient encounters <b>402</b>, <b>404</b> and <b>406</b> with a healthcare provider concerning treatment of an injury.

[0036]FIG. 5 shows a user interface display image illustrating a rule profile <b>502</b> for a hospital <b>500</b> indicating rules and tests selected to be applied in processing patient claim data. The rules and tests are specified to be applied to data in individual claim element fields identified in column <b>530</b> and described in column <b>532</b>. Initially, claim data is parsed to identify whether a claim contains particular characteristics (e.g., whether the claim is covered under Medicare or Medicaid plans). The identified characteristics are interpreted to derive values for two data elements, Receiver ID <b>504</b> and Service Type <b>506</b>. For example, pre-defined categories of claims include, Medicare part A (Receiver ID=C, e.g. item <b>508</b>), Medicare part B (Receiver ID=CB, e.g. item <b>510</b>) or Medicaid (Receiver ID=D, e.g. item <b>512</b>). Service Types include, “REG” (item <b>516</b>) to indicate a predetermined standard set of rules and tests are to be applied, “###” (item <b>518</b>) indicating Service Type is not specified and that a predetermined default set of rules and tests are to be applied, and “N/A” (item <b>514</b>) to indicate reports that are not associated with claims needing processing. Other Service Types <b>506</b> and Receiver ID <b>504</b> elements may be used and those described are merely exemplary. Data elements <b>504</b> and <b>506</b> are used to determine which rules and tests to apply to individual claim element fields identified in column <b>530</b> for a particular category (<b>504</b>) and service type (<b>506</b>) of claim.

[0037] The rules and tests that are applicable to claim element fields <b>530</b> for a particular category <b>504</b> and service type <b>506</b> of claim, include a requirement test identified under column headers R (e.g. item <b>520</b>) and a validation test identified under column headers V (item <b>524</b>). An entry in column R adjacent to a particular claim element field <b>530</b> identifies an action to be taken if the particular claim element field <b>530</b> does not contain a value. An entry in column V adjacent to a particular claim element field <b>530</b> identifies an action to be taken if the particular claim element field <b>530</b> value does not conform to predetermined test criteria. Exemplary action identifiers listed in column R include, “E” indicating an error is to be declared if no value is present, “2” indicating the field is to be cleared if it contains a value, “H” indicating the claim is to be Held if no value is present and “W” indicating a warning message to a user is to be generated if no value is present. Similarly, exemplary action identifiers listed in column V include, “E” indicating an error is to be declared if a detected value fails validation tests or rules, “2” indicating the field is to be cleared if it contains a value, “H” indicating the claim is to be Held if a detected value fails validation tests or rules, and “W” indicating a warning message to a user is to be generated if a detected value fails validation tests or rules. These actions are exemplary only and others are also employed. Therefore, for example, if an admission date field <b>530</b> contains no value in a Medicare (part A) claim with a REG service type, an Error is generated. Further, if an admission date field does contain a value in a Medicare (part A) claim with a REG service type, and the detected value fails validation tests and rules, an error is generated.

[0038]FIG. 6 shows a user interface display image illustrating results of applying rules in processing claim data and identifying claim rejection reasons by description and rejection code. Specifically, errors <b>651</b> and <b>653</b>, for example, (error codes sc00018 and sc00019) indicate a claim data admission date value is out of range or is invalid, respectively. These errors prompt warning messages for Medicare part B category claims with Service Types “REG”, “###” and “N/A” as previously discussed.

[0039]FIG. 10 shows a user interface display image illustrating claim processing results of applying validation rules in step <b>327</b> and identifying claim rejection reasons by description and rejection code. Specifically, line <b>600</b> indicates error list heading labels defining columns comprising, an error code sequence, an error code identifier and level, an error code sub-identifier, error description text and cleared errors identifying errors that have been corrected (none in this example). Lines <b>602</b>-<b>617</b> list results of applying validation rules to claim data for a patient. The results list identifies 7 claim rejection reasons comprising, an invalid revenue code (<b>602</b>), a data format deficiency (<b>607</b>), a missing name portion (<b>609</b>), an accommodation data warning (<b>611</b>), a revenue code related warning (<b>613</b>), a procedure code related warning (<b>615</b>) and accommodation or ancillary data warning (<b>617</b>).

[0040] Continuing with step <b>329</b> of FIG. 3, unit <b>46</b> processes a result derived by application of selected rules to claim data to provide an output. Unit <b>46</b>, in response to a result derived by application of a rule, may schedule a task to be performed by a healthcare worker, initiate creation of an error report, initiate creation of a record of a result of applying rules to edit claim data, or initiate creation of an accounting report. Unit <b>46</b> may also initiate, generation of a claim, sending of a remittance, scheduling of review of claim data to be performed by a healthcare worker or generation of an alert message to a user to indicate a deficiency in claim data likely to result in claim denial. The process of FIG. 3 ends at step <b>331</b>.

[0041]FIG. 7 shows a flowchart of a process employed in deriving and amending rules in response to claim adjudication results from a payer organization. In step <b>760</b> collated claim data related to a healthcare claim for a particular patient is submitted by a healthcare provider to a payer organization. The payer organization examines whether the submitted claim complies with payer predetermined requirements and rules associated with the particular patient health plan in step <b>763</b>. The payer issues to the patient and healthcare provider an explanation of benefits statement following adjudication of the submitted claim using the payer rules in step <b>767</b>. In step <b>769</b>, a service (e.g., service <b>80</b> of FIG. 1) evaluates the received explanation of benefits, and uses this explanation in monitoring claim rejection issues and rates of adjudication success and failure and in providing information for use in adjusting existing rules in repository <b>74</b> or in creating new rules to resolve identified issues. In step <b>771</b>, new or updated rules are maintained in repository <b>74</b> and applied to claim data prior to submission of the claim data to a payer organization to improve claim processing efficiency and to reduce rejection and denial rates.

[0042] Claim data used for trial adjudication and ultimately submitted to a payer upon amendment (if required) and validation is derived from data repository <b>68</b>. FIGS. <b>11</b>-<b>17</b> show an exemplary data record structure for data elements incorporated in central data repository <b>68</b> and used in claim processing. Specifically, FIG. 11 shows a partial patient record data structure, FIG. 12 shows a medical record data structure and FIG. 13 shows a partial payer record data structure. A charge record data structure and occurrence code data structure are presented in FIGS. 14 and 15 respectively and FIGS. 16 and 17 indicate a span code (for use in identifying service charges that are to be grouped on a single claim) and a medical condition code data structure respectively. These record structures are exemplary only and repository <b>68</b> typically contains other types of records associated with claim data such as, for example, records concerning ambulance services, rehabilitation services, treatments and other services and activities. The record structures of FIGS. <b>11</b>-<b>17</b> are individually accessible in repository <b>68</b> using a claim packet identifier (<b>800</b>, <b>900</b>, <b>920</b>, <b>940</b>, <b>960</b>, <b>980</b>, <b>830</b>), section identifier (<b>802</b>, <b>902</b>, <b>922</b>, <b>942</b>, <b>962</b>, <b>982</b>, <b>832</b>) and sequence number (<b>804</b>, <b>904</b>, <b>924</b>, <b>944</b>, <b>964</b>, <b>984</b>, <b>834</b>).

[0043] Data in an individual record data structure is field length delimited. In the patient record structure of FIG. 11, for example, a patient last name (<b>806</b>) occupies a fixed length of 20 characters, followed by a patient first name (<b>808</b>) occupying twelve characters and middle initial (<b>810</b>) occupying one character. The record structures of FIGS. <b>12</b>-<b>17</b> contain data related to other particular claim data aspects in similar predetermined fixed length fields. The medical record of FIG. 12, for example, contains an admission diagnosis code (<b>906</b>), as well as a primary diagnosis code (<b>908</b>) and other diagnosis codes (<b>910</b>). The payer record of FIG. 13 contains a source of payment code (<b>926</b>), as well as payer identifier (<b>928</b>) and payer sub-identifier (<b>930</b>). The charge record of FIG. 14 contains a service charge code (<b>946</b>), as well as a service charge revision code (<b>948</b>) and service date (<b>950</b>). The occurrence code record of FIG. 15 contains an occurrence identification code (<b>966</b>) and occurrence date (<b>968</b>). The span code record of FIG. 16 contains a span identification code (<b>986</b>), as well as a span determination start date (<b>988</b>) and end date (<b>990</b>) for use in identifying a period when the condition defined by the Span Code took place. The condition code record of FIG. 17 contains a medical condition identification code (<b>836</b>). The items referred to in connection with FIGS. <b>11</b>-<b>17</b> are described for exemplary purposes. However, other record items are shown in the record structures of FIGS. <b>11</b>-<b>14</b>. These other items are representative of the breadth of data that may be included in the various records in the repository <b>68</b> structure, for example. In an alternative embodiment, other non-fixed length data record structure or another data record structure may be employed for repository <b>68</b>.

[0044] The claim data in repository <b>68</b> is collated by data acquisition unit <b>32</b> via interface <b>10</b> from multiple different sources as previously described and stored in repository <b>68</b> via data management system <b>64</b>. A data emitter unit <b>34</b> provides claim data to an external entity (e.g., portals and participants <b>20</b>-<b>30</b>) by extracting required claim data from repository <b>68</b> and communicating it via interface <b>10</b>. Data reacher unit <b>36</b> is used by functions of the FIG. 1 system to provide read-only access to claim data stored by a remote entity and to make decisions based on this data. Further, claim data repository <b>68</b> is searchable by users <b>30</b> via external portals <b>20</b>-<b>28</b> using data search criteria created using search pattern design function <b>38</b>. Thereby a user may search for statistically significant data patterns and other data patterns in analyzing the claim data in repository <b>68</b>.

[0045] Search design function <b>38</b> employs a specialized category of rules stored in rules repository <b>74</b>. An authorized user is able to use surveillance portal <b>28</b> via interface <b>10</b> to use the specialized category of search rules to support a search of rules and claim data information. Searchable information sources include rules repository <b>74</b>, relationship rules repository <b>18</b> as well as claim data repository <b>68</b>. For this purpose, search pattern evaluator function <b>40</b>, employs a sub-set of rules executed by rule execution unit <b>46</b> to process a definition of a pattern search created by pattern design function <b>38</b>. Specifically, pattern evaluator function <b>40</b> identifies patterns in the data searched according to action steps included in the search definition and reports results to the search initiator via interface <b>10</b>. A pattern search is executable in response to occurrence of an event. An event may include, for example, a command (in response to a request by a participant), or upon detection of a change in particular data (receipt of a specific diagnosis, for example) or an event may be internally generated such as in response to expiration of a particular time period.

[0046] Interface <b>10</b> provides access by various interested participants <b>30</b> in the claim data processing operation via portals <b>20</b>-<b>28</b> for searching, viewing or initiating actions. Thereby a participant (such as a healthcare provider, payer institution representative, patient, employer or government agency) is able to access claim data, payer rules and initiate various actions such as a data correction action, for example. Specifically healthcare providers and healthcare payer representatives are able to access the system via portals <b>20</b> and <b>22</b> that provide the functions these entities respectively require. A healthcare provider, for example, is able to input financial data and associated clinical data into repository <b>68</b> and to initiate and manage claim trial adjudication and other rule-driven processes via portal <b>20</b>. Similarly, a provider is able to automatically modify its own data based on automated rules or through manual amendment and update. A provider is further able to initiate submission of validated error-free claims for payment and to initiate claim status inquiries. In addition, a provider via portal <b>20</b> is able to acquire remittance advice (i.e., information about payments made) and to automatically post acquired advice to corresponding correct accounts as well as to generate and submit secondary and tertiary claims and obtain worklists (of tasks to be performed) and reports in support of management of its business.

[0047] A payer institution is able to use portal <b>22</b> to store and maintain adjudication rules in repository <b>74</b> and to receive claim data for trial or actual (determinative) adjudication as well as to respond to claim status inquiries. A payer is further able to communicate a request for information or remittance advice and obtain worklists and reports and manage its business and revenue cycle. A consumer, such as an individual patient, covered dependent or healthcare plan subscriber with appropriate authorization is able to use consumer portal <b>24</b> to view his own claim data records and claim status and research rules governing payment. A consumer is also able to correct errors in his own demographic data or medical record and to schedule appointments via the system. A consumer is also able to obtain account balance, recent transaction records, future deposit information and request payment from a medical expense reimbursement account for items paid out of pocket.

[0048] An employer, or another plan administrator, is able to use portal <b>26</b> to manage healthcare encounter cycle business and to negotiate healthcare contracts on behalf of a group of persons (employees) and to monitor activity related to those employees. For this purpose, an employer is able to obtain, for example, a worklist or a report identifying incidence of various diagnoses, utilization of various providers, a breakdown of charges (e.g. those paid by members, contractually reduced, or denied). Thereby an employer is able to determine if plan members would benefit from an alternative health plan selection. Surveillance portal <b>28</b> enables authorized participants <b>30</b> (e.g. a regulator or researcher) to create and implement research projects to analyze stored claim data by searching for patterns or trends in the claim data of repository <b>68</b> in conjunction with rules repository <b>74</b>. Specifically, surveillance portal <b>28</b> in conjunction with search pattern design and implementation units <b>38</b> and <b>40</b> respectively, supports searches to, (<b>1</b>) generate periodic statistical reports, (<b>2</b>) detect claim fraud and abuse, and (<b>3</b>) detect outbreaks of epidemics, caused either by natural disease or by human (terrorist) activity and other searches, for example. Search results may include worklists or reports and search criteria may be stored as rules in rules repository <b>74</b>.

[0049] Interface <b>10</b> provides access by participants <b>30</b> to claim data and rule repositories <b>68</b> and <b>74</b> via portals <b>20</b>-<b>28</b> using a security function <b>12</b>, translator function <b>14</b> and transport function <b>16</b>. Security function <b>12</b> determines whether a participant is authorized to communicate with another particular participant and whether a participant is authorized to access particular data and assigns participant privileges and entitlements and maintains security and access rules. Unit <b>12</b> rejects and tracks unauthorized requests that violate security and other (e.g., HIPAA) policies. Translator function <b>14</b> converts data between the different data formats used by internal and external participants in the FIG. 1 system. For this purpose, translator <b>14</b> converts data from a first data format into an internally defined intermediate data format and from the intermediate format into a desired output data format. Transport function <b>16</b> supports communication of data and messages between internal functions of the FIG. 1 system and between internal functions and external participants. For this purpose function <b>16</b> uses relationship rules repository <b>18</b> to identify required connection protocols and methods as well as source and destination addresses. Function <b>16</b> also uses rules repository <b>18</b> in encoding data in the appropriate message format and protocol and in initiating necessary hand shaking and other routines required to implement bidirectional communication.

[0050] Relationship rules repository <b>18</b> contains information identifying the application programmer interfaces (APIs) used by participant and system software applications and the required procedure for requesting information from particular sources and providing information to particular participants. The participant API identification and related communication information is provided by individual participants for storage in repository <b>18</b>. The participants retain control over and maintain their respective communication support information. Interface <b>10</b> uses the stored predetermined API and communication information in supporting conversion of data from a first data format into an internally defined intermediate data format and from the intermediate format into a desired output data format. As a consequence, participants are able to update their own systems and to communicate with other participants regardless of the rule standards in use or whether the repositories are migrated to new platforms or radically altered in other ways. Also data format standards involved may be changed by an individual participant without impeding operation by other participants. For this purpose interface <b>10</b> uses relationship repository <b>18</b> to process the validated claim data to provide the data format, protocol, handshaking routine and submission procedure predetermined (and retained and identified in repository <b>18</b>) by the payer.

[0051] The systems, processes and user interface display formats presented in FIGS. <b>1</b>-<b>17</b> are not exclusive. Other systems, processes and user interface forms may be derived in accordance with the principles of the invention to accomplish the same objectives. The inventive principles are applicable to streamlining and automating a revenue management process in any industry or field. The principles are particularly applicable to the insurance, government and healthcare industries.