 |
|
|
Database Matching
Adaptive’s processes include the capability to conduct powerful database matching during the application of character recognition and manual data entry processes. Customer defined business rules allow for an almost limitless degree of flexibility, without the expense of complex programming. The results provide for a maximum degree of data accuracy while reducing costs to our customers.
Examples of applications for database matching services are:
• Provider Matching
• Member Matching
• Alias Matching
• Valid Values
• Invalid Values
• Value Substitution
• Value Insertion
Member and Provider Matching
Adaptive provides sophisticated Provider and Member matching to increase first pass adjudication rates and reduce the number of claims requiring manual adjudication as a result of member and provider validations. Member and Provider matching can substantially increase the percentage of claims that pass Auto Adjudication, minimizing the amount of human intervention required in the adjudication process, resulting in a major savings that provides an immediate ROI on the cost of Adaptive’s services.
Alias Matching
Semantic differences in database values which the customer defines as alternate and/or equivalent can be defined through alias matching. Examples of alias matching might include “Boulevard” versus the abbreviation “Blvd” in an address, or “James” versus the abbreviation “Jim”. Alias matching can provide for optimal use of resources without compromising data accuracy, further reducing cost to the customer.
Valid Values
Databases of acceptable values can be used for validation during character recognition or manual data entry. This process promotes data accuracy and can minimize or eliminate the need for additional quality control measures such as second pass keying. Customer provided files are loaded into database format and business rules are applied per customer specification.
Invalid Values
Databases of values specifically determined to be excluded from character recognition or data entry may also be used. This is often useful when the common recognition or data entry errors have been determined through experience. Preventing errors at the point of origination provides for the fastest, least expensive and most consistent means of correction.
Value Lookup and Substitution
Databases of values and their equivalents can be used for validation and substitution. An example of this might be the entry of a specific company name which would be validated against the database and returned as the stock symbol for the company. There are a variety of applications where this capability may be used to meet specific customer requirements.
Value Lookup and Plug
Databases of primary values and corresponding information may be used to increase the accuracy of data and reduce the costs of entry. An example of a practical application would be to validate an Account Number against the database, extracting the customer First Name, Last Name and Address and “plugging” the values into the corresponding fields of the data record. Often, substantial savings can be produced through the reduction of manual labor associated with key entry of the additional fields.
|
|
|
|
