Methods and systems for determining a priority for processing of selected database records

Embodiments of the present disclosure are directed to methods and systems for the processing of database records. Processing database records can comprise maintaining a records in a database. A subset of records from the plurality of records can be identified for further process, e.g., based on a value stored in a field of each record. Each record of the identified subset of records can be scored based on a plurality of factors related to each record of the identified subset of records. The identified subset of records can then be prioritized into an ordered list of records based on the score for each record of the identified subset of records and one or more workflows can be executed on the identified subset of records based on the ordered list of records.

FIELD OF THE DISCLOSURE

Embodiments of the present disclosure relate generally to methods and systems for managing transaction records in a database and more particularly to determining a priority for processing of selected database records.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of various embodiments disclosed herein. It will be apparent, however, to one skilled in the art that various embodiments of the present disclosure may be practiced without some of these specific details. The ensuing description provides exemplary embodiments only, and is not intended to limit the scope or applicability of the disclosure. Furthermore, to avoid unnecessarily obscuring the present disclosure, the preceding description omits a number of known structures and devices. This omission is not to be construed as a limitation of the scopes of the claims. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should however be appreciated that the present disclosure may be practiced in a variety of ways beyond the specific detail set forth herein.

While the exemplary aspects, embodiments, and/or configurations illustrated herein show the various components of the system collocated, certain components of the system can be located remotely, at distant portions of a distributed network, such as a LAN and/or the Internet, or within a dedicated system. Thus, it should be appreciated, that the components of the system can be combined in to one or more devices or collocated on a particular node of a distributed network, such as an analog and/or digital telecommunications network, a packet-switch network, or a circuit-switched network. It will be appreciated from the following description, and for reasons of computational efficiency, that the components of the system can be arranged at any location within a distributed network of components without affecting the operation of the system.

Various additional details of embodiments of the present disclosure will be described below with reference to the figures. While the flowcharts will be discussed and illustrated in relation to a particular sequence of events, it should be appreciated that changes, additions, and omissions to this sequence can occur without materially affecting the operation of the disclosed embodiments, configuration, and aspects.

FIG. 1 is a block diagram illustrating elements of an exemplary computing environment in which embodiments of the present disclosure may be implemented. More specifically, this example illustrates a computing environment 100 that may function as the servers, user computers, or other systems provided and described herein. The environment 100 includes one or more user computers, or computing devices, such as a computing device 104, a communication device 108, and/or more 112. The computing devices 104, 108, 112 may include general purpose personal computers (including, merely by way of example, personal computers, and/or laptop computers running various versions of Microsoft Corp.'s Windows® and/or Apple Corp.'s Macintosh® operating systems) and/or workstation computers running any of a variety of commercially-available UNIX® or UNIX-like operating systems. These computing devices 104, 108, 112 may also have any of a variety of applications, including for example, database client and/or server applications, and web browser applications. Alternatively, the computing devices 104, 108, 112 may be any other electronic device, such as a thin-client computer, Internet-enabled mobile telephone, and/or personal digital assistant, capable of communicating via a network 110 and/or displaying and navigating web pages or other types of electronic documents. Although the exemplary computer environment 100 is shown with two computing devices, any number of user computers or computing devices may be supported.

The system may also include one or more servers 114, 116. In this example, server 114 is shown as a web server and server 116 is shown as an application server. The web server 114, which may be used to process requests for web pages or other electronic documents from computing devices 104, 108, 112. The web server 114 can be running an operating system including any of those discussed above, as well as any commercially-available server operating systems. The web server 114 can also run a variety of server applications, including SIP (Session Initiation Protocol) servers, HTTP(s) servers, FTP servers, CGI servers, database servers, Java servers, and the like. In some instances, the web server 114 may publish operations available operations as one or more web services.

The environment 100 may also include one or more file and or/application servers 116, which can, in addition to an operating system, include one or more applications accessible by a client running on one or more of the computing devices 104, 108, 112. The server(s) 116 and/or 114 may be one or more general purpose computers capable of executing programs or scripts in response to the computing devices 104, 108, 112. As one example, the server 116, 114 may execute one or more web applications. The web application may be implemented as one or more scripts or programs written in any programming language, such as Java™, C, C#®, or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The application server(s) 116 may also include database servers, including without limitation those commercially available from Oracle®, Microsoft®, Sybase®, IBM® and the like, which can process requests from database clients running on a computing device 104, 108, 112.

The web pages created by the server 114 and/or 116 may be forwarded to a computing device 104, 108, 112 via a web (file) server 114, 116. Similarly, the web server 114 may be able to receive web page requests, web services invocations, and/or input data from a computing device 104, 108, 112 (e.g., a user computer, etc.) and can forward the web page requests and/or input data to the web (application) server 116. In further embodiments, the server 116 may function as a file server. Although for ease of description, FIG. 1 illustrates a separate web server 114 and file/application server 116, those skilled in the art will recognize that the functions described with respect to servers 114, 116 may be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters. The computer systems 104, 108, 112, web (file) server 114 and/or web (application) server 116 may function as the system, devices, or components described herein.

The environment 100 may also include a database 118. The database 118 may reside in a variety of locations. By way of example, database 118 may reside on a storage medium local to (and/or resident in) one or more of the computers 104, 108, 112, 114, 116. Alternatively, it may be remote from any or all of the computers 104, 108, 112, 114, 116, and in communication (e.g., via the network 110) with one or more of these. The database 118 may reside in a storage-area network (“SAN”) familiar to those skilled in the art. Similarly, any necessary files for performing the functions attributed to the computers 104, 108, 112, 114, 116 may be stored locally on the respective computer and/or remotely, as appropriate. The database 118 may be a relational database, such as Oracle 20i®, that is adapted to store, update, and retrieve data in response to SQL-formatted commands.

FIG. 2 is a block diagram illustrating elements of an exemplary computing device in which embodiments of the present disclosure may be implemented. More specifically, this example illustrates one embodiment of a computer system 200 upon which the servers, user computers, computing devices, or other systems or components described above may be deployed or executed. The computer system 200 is shown comprising hardware elements that may be electrically coupled via a bus 204. The hardware elements may include one or more central processing units (CPUs) 208; one or more input devices 212 (e.g., a mouse, a keyboard, etc.); and one or more output devices 216 (e.g., a display device, a printer, etc.). The computer system 200 may also include one or more storage devices 220. By way of example, storage device(s) 220 may be disk drives, optical storage devices, solid-state storage devices such as a random-access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash-updateable and/or the like.

The computer system 200 may additionally include a computer-readable storage media reader 224; a communications system 228 (e.g., a modem, a network card (wireless or wired), an infra-red communication device, etc.); and working memory 236, which may include RAM and ROM devices as described above. The computer system 200 may also include a processing acceleration unit 232, which can include a DSP, a special-purpose processor, and/or the like.

The computer-readable storage media reader 224 can further be connected to a computer-readable storage medium, together (and, optionally, in combination with storage device(s) 220) comprehensively representing remote, local, fixed, and/or removable storage devices plus storage media for temporarily and/or more permanently containing computer-readable information. The communications system 228 may permit data to be exchanged with a network and/or any other computer described above with respect to the computer environments described herein. Moreover, as disclosed herein, the term “storage medium” may represent one or more devices for storing data, including read only memory (ROM), random access memory (RAM), magnetic RAM, core memory, magnetic disk storage mediums, optical storage mediums, flash memory devices and/or other machine-readable mediums for storing information.

The computer system 200 may also comprise software elements, shown as being currently located within a working memory 236, including an operating system 240 and/or other code 244. It should be appreciated that alternate embodiments of a computer system 200 may have numerous variations from that described above. For example, customized hardware might also be used and/or particular elements might be implemented in hardware, software (including portable software, such as applets), or both. Further, connection to other computing devices such as network input/output devices may be employed.

FIG. 3 is a block diagram illustrating an exemplary environment in which a records management and processing system and data collection service can be implemented according to one embodiment of the present disclosure. As illustrated in this example, the environment 300 can include a number of different systems. Specifically, the environment 300 can include a records management and processing system 305 which can comprise a server or other computing device as described above. The records management and processing system 305 can be communicatively coupled with a communication network 310 such as the Internet or any other one or more wired or wireless, local or wide area networks. The environment 300 can also include a number of service provider systems 315A-315C each of which can comprise a server or other computing device as described above and which can also be communicatively coupled with the communication network 310. Furthermore, the environment 300 can include a number of responsible entity systems 320A-320C each of which can comprise a server or other computing device as described above and which can also be communicatively coupled with the communication network 310. It should be noted that while three service provider systems 315A-315C and three responsible entity systems 320A-320C are shown here for illustrative purposes, any number of such systems 315A-315C and 320A-320C can be present in various different implementations without departing from the scope of the present disclosure.

According to one implementation, the service provider systems 315A-315C can represent those servers or other computer systems typically associated with an entity providing a service consumer. In one embodiment, the providers of the services can comprise healthcare providers such as hospital, doctors, physical therapists, counsellors, out-patient and/or urgent care facilities, pharmacies, or other such providers while the consumer can comprise a patient. In such embodiments, the responsible party systems 320A-320C can comprise, for example, those servers or other computer systems typically associated with an entity responsible for some duties related to the delivery of and/or payment for those services. For example, responsible parties can include third-party payors including but not limited to insurance companies, Medicare, Medicaid, and/or other private, governmental, or mixed public/private entities. While described here with reference to healthcare providers and third-party payors such as insurance companies, it should be understood that various embodiments of the present disclosure are not limited to such implementations. Rather, embodiments of the present invention are believed to be equally adaptable to and useful in environments and systems which process a large volume of electronic records according to complex rules and regulations, business or financial arrangements, etc.

Regardless of the exact implementation of nature of the entities involved, the records management and processing system 305 can comprise an intermediary between a plurality of service providers systems 315A-315C and the plurality of responsible entity systems 320A-320C. As such and as will be described in greater detail below, the records management and processing system 305 can maintain a set of records related to services provided to a consumer by each or the service providers and for which at least one of the responsible entities is responsible in some way, e.g., granting approval, making a payment, providing some additional information, etc. In the normal course of processing such records and such transactions, the records management and processing system 305 may experience a delay in the handling of some records. For example, delays can be caused by data anomalies in records provided to the records management and processing system 305 by the service provider systems 315A-315C. In other cases, delays can be caused by a problem or potential problem with the handling of records or the performance of required actions by the responsible entity systems 320A-320C. In the example of the healthcare implementation described above, the records can represent, at least in part, payments to be made by the responsible entities to the service providers and thus, can represent accounts receivable for the service providers. As such, the timely completion of handling such records can directly impacts the cashflow of the service providers. Additionally, the longer processing of such records is delayed, the more likely the payments will become contested or otherwise become problematic. In other implementations, the timely processing of records by the records management and processing system 305 can be equally important for a variety of other reasons.

Accordingly, embodiments of the present disclosure are directed to methods and systems for the timely processing of records by the records management and processing system 305 exchanged between the service provider systems 315A-315C and the responsible entity systems 320A-320C. More specifically, the records management and processing system 305 can maintain a set of rules defining conditions for processing records and associated actions to affect that processing upon satisfaction of or failure to satisfy the conditions of that rule. The records management and processing system 305 can also maintain tags identifying data in a record, current status of processing of a record, or other information about the record. The records management and processing system 305 can apply the rules to the records and assign tags to the records based on the conditions defined in the applied rules. The records management and processing system 305 can then process the records according to workflows for processing the records based on the assigned tags and applied rules.

FIG. 4 is a block diagram illustrating elements of an exemplary records management and processing system according to one embodiment of the present disclosure. As illustrated in this example, the records management and processing system 305 as described above can comprise a set of records maintained in a database 405 or other repository. As noted above, each record of the set of records in the database can comprise a record of a service provided to a consumer by a service provider and can identify at least one required action by at least one responsible entity of a plurality of responsible entities. Also, as described above, the records management and processing system 305 can comprise an intermediary between systems of the plurality of service providers and systems of the plurality of responsible entities.

The records management and processing system 305 can also maintain one or more rules 410 for managing and processing the records of the database 405. Generally speaking, a rule can comprise a definition of one or more conditions and an associated one or more actions to be performed upon satisfaction, or failure to satisfy, the conditions of that rule. Accordingly, each rule 410 maintained by the records management and processing system 305 can comprise one or more conditions for processing one or more records of the set of records 405 and at least one associated action to affect processing of the one or more records upon satisfaction of or failure to satisfy the one or more conditions of the rule 410. The conditions defined in some of these rules 410 can comprise conditions to be satisfied by one or more of the responsible entities 320A-320C described above. For example, one or more rules can define timing or other conditions a payment by a third-party payor, e.g., Medicare, Medicaid, an insurance company, etc., for a service rendered by the service provider, e.g., a hospital, doctor, pharmacy, etc., to the consumer/patient. Additionally, or alternatively, conditions defined in some of the rules 410 can define parameters for data in the record. For example, rules 410 can be defined for performing checks on the values of various fields of data in the records 405 such as comparing different fields, e.g., a value of total charges relative to a value of total adjustments, etc.

To facilitate definition of the rules 410, the records management and processing system 305 can further comprise a rules definition module 415. Generally speaking, the rules definition module 415 can comprise one or more applications executed by the records management and processing system 305 and which provide a rules definition interface 420. The rules definition interface 420 can include, for example, one or more webpages or other, similar interfaces providing elements through which an authorized user, such as an administrator or manager, can select or otherwise input conditions and corresponding actions for a new or modified rule. Once defined in this manner, the new or modified rule can be saved in the set of rules 410 and made available for application by the records management and processing system 305.

The records management and processing system 305 can also maintain a set of tags 425 for managing and processing the records 405. Generally speaking, these tags 425 can comprise a flag, metadata, or other information used to describe, explain, mark, or otherwise identify records in the set of records 405. For example, the tags 425 can include, but are not limited to, tags used to identify data in a record 405, a current status of processing of the record 405, or other information about the record. As will be described, these tags 425 can be used to identify records 405 that merit additional attention and/or processing and thus, the absence of tags associated with a record can implicitly indicate that additional attention or handling is not needed for that record.

To facilitate definition and use of the tags 425, the records management and processing system 305 can further comprise a tag definition and assignment module 430. Generally speaking, the tag definition and assignment module 430 can comprise one or more applications executed by the records management and processing system 305 and which provide a tag definition and assignment interface 435. The tag definition and assignment interface 435 can include, for example, one or more webpages or other, similar interfaces providing elements through which an authorized user, such as an administrator or manager, can select or otherwise input definitions of new or modified tags. Once defined in this manner, the new or modified tag can be saved in the set of tags 430 and made available for application by the records management and processing system 305.

The records management and processing system 305 can also comprise a rules engine 440. Generally speaking, the rules engine can comprise one or more applications executed by the records management and processing system 305 and which can read and apply the rules 410 to the records 405. That is, the rules engine 440 can compare the records stored in the database 405 to the conditions for the rules 410 and, upon finding records that satisfy, or fail to satisfy as the case may be and depending upon how the condition is defined, can perform or cause to be performed the action associated with the satisfied or failed condition. These actions can include, for example, applying one or more of the tags 425 to the identified records 405 or presenting the identified records to a user and receiving an indication of the tag(s) to be applied. The tag(s) 425 applied to a record can identify or mark that record for further attention to advance the processing of that record. Thus, records that are not tagged do not require additional attention or processing outside of normal processes since they are in a condition as defined in the rules as being normal or acceptable, e.g., within defined deadlines or other time limits etc. In other words, processing can be applied to one set of records based on the tags applied while processing of another set of records can be postponed or delayed so that the first set of records can be given more attention and resources.

The rules engine 440 can apply the rules 410 to the records 405 periodically, on demand, or upon the occurrence of predefined event or the satisfaction of one or more predefined conditions. For example, the rules engine 440 can apply the rules 410 as part of a routine process performed each day, week, month, or other period, and/or may be initiated or kicked off upon request by an authorized user of the system such as a manager or supervisor. As noted above, applying the rules 410 can include tagging one or more records based on the applied rules 410. Additionally, or alternatively, tags can be applied to one or more records based on a user selection or input. For example, a user viewing a set of records can select records from that set and apply one or more tags to those selected records based on conditions the user perceives and which may or may not be defined in the rules. Thus, tagging of records can be driven by the applied rules or based on input from a user and the tags applied in either way can influence the further handling of those tagged records.

According to one embodiment and as illustrated here, the records management and processing system 305 can also comprise a workflow engine 445 and a set of predefined workflows 450. Generally speaking, a workflow 450 can comprise a set of one or more steps to be performed on or related to a record. These steps can be wholly machine executable or may, in some cases, rely on some degree of human intervention. For example, these steps can range from presenting data from a tagged record in a user interface to a human operator, such as a collector, for an action to be performed by the operator, e.g., calling a payor or performing some other follow-up action, to a completely automated process such as sending an automatically generated communication to a payor system or combinations of various such human and machine actions. The workflow engine 445 can comprise one or more applications executed by the records management and processing system 305 and which, during execution, can read the predefined workflows 450 and implement or perform the steps defined therein. The workflows 450 can comprise a set of predefined, executable steps directed to advancing the processing of the records 405 identified by the rules 405 and tagged as described above. The workflow engine 445 can execute the workflows 450 by selecting a workflow 450 based on the tags 425 for a record 405 and executing the selected workflow 450 using the information from that record and, in some cases, based on further application of one or more rules 410 related to the tags 425 applied to that record 405. Thus, the conditions and associated actions defined in the rules 410 can also be applied by the workflow engine 445 as it executes the workflows 450. The workflow engine 445 can also provide a workflow user interface 450 for viewing and managing one or more workflows for processing records.

Therefore, the rules engine 440 can apply one or more of the rules 410 to the records saved in the database 405 to identify those records which should be further processed or given further scrutiny and mark those records with one or more tags 425. In this way, those records found to be within normal or acceptable conditions according to the applied rules need not be subjected to further scrutiny and/or processing thus saving resources such as human effort, processing overhead, etc. In other words, processing of one set of records can be performed in an expedited or priority manner while processing of another set of records can be de-prioritized or postponed based on the tags applied to the records which is in turn based on the rules or input from a user.

One or more predefined workflow processes 450 can then be selected, e.g., based on the applied tags, initiated, and executed by the workflow engine 445 to further process those tagged records. The workflows 450 can be initiated automatically, e.g., triggered by the rules engine 445 upon completion of applying the tags 425, upon the occurrence of certain conditions, e.g., as defined in one or more rules 410, at a predetermined or pre-scheduled time, upon request, or in a variety of other ways without departing from the scope of the present disclosure. Processing the tagged records 405 by the workflow engine 445 can comprise performing the steps defined in the workflows 450, which can include applying the selected or additional rules 410 to the records being processed, in order to advance the handling of those records 405 by the records management and processing system 305, e.g., move an account towards payment or other resolution.

To further facilitate this processing of the records 405 the records management and processing system 305 can further include an annotation engine 460. Generally speaking, the annotation engine 460 can be adapted to add notes or other annotations to the records 405. For example, the annotation engine 460 can present an user interface 465. Through such interfaces, a user may add a note or other annotation to the record to indicate, for example, a current status of the record, an action taken on the record, an action required or to be taken on the record, etc. According to one embodiment, and to facilitate the making of such annotations, these annotations can be collected as part of a dynamic query session. As used herein, the term dynamic query session is intended to mean a process conducted by the annotation engine 460 through which information related to one or more records of interest is collected from one or more sources. These sources can be one or more users of the records processing and management system 305, the record of interest itself and/or other records in the plurality of records 405, and/or other sources accessible by the records processing and management system 405 including but not limited to users, records, and/or services of other systems such as a of other systems such as a service provider system 315, a responsible entity system 320, etc. The dynamic query session can be conducted in the form of a question-and-answer session in which questions are posed to users and/or form the basis of a database query on the records 405 or calls to systems or services of other systems. These queries are referred to as dynamic in that the answer obtained for one query can change or influence a subsequent query presented. For example, the questions to be posed or queries to be made in a session can be arranged as part of a decision tree or similar structure that can be navigated as answers or information are obtained.

To implement such a dynamic query session, the annotation engine 460 can be adapted to define and utilize a set of note templates 470. Generally speaking, each template 470 can define a dynamic query session for a particular condition on a record or set of records, e.g., a value of a field of the record, aging of the record, etc. Each template 470 can also identify one or more actions to be taken based on results of the dynamic query session, i.e., based on the answers collected. These actions can be defined, for example, in one or more rules 410 and implementing those actions can additionally, or alternatively, comprise initiating a workflow 450 as described above, for example. Each template 470 can also define a format and content for an annotation to be added to a record for which the dynamic query session is executed. The annotation can include both predefined text as well as answers or results obtained by the dynamic query session.

With multiple workflows 450 and/or work queues and rules 410 running in parallel, sub-optimal management and prioritization of records being processed may occur. Embodiments of the present disclosure are directed to prioritizing the processing of selected records 405. For example, and returning to the healthcare example described herein, embodiments may prioritize non-zero (debit balance) insurance balance AR & Denial accounts utilizing the current status of the accounts and expected outcome to maximize yield, e.g., net insurance payment amount on the account, and reduce non-yield resulting touches.

According to one embodiment, managing and processing database records 405 can comprise maintaining a plurality of records 405 in a database as described above. A subset of records 470 can be identified or selected from the plurality of records 405 by a prioritization engine 460. The identified subset of records 470 can comprise a plurality of records to be further processed by the records management and processing system 305. Identifying the subset of records 470 from the plurality of records can be based on a value stored in a field of each record of the plurality of records 405. For example, identifying a record of the subset of records can be based on the value stored in the field of the record being greater than zero, e.g., a non-zero AR balance.

Each record of the identified subset of records 470 can be scored by the prioritization engine 460 based on a plurality of factors related to each record of the identified subset of records 470. According to one embodiment, the plurality of factors related to each record can comprise a current status for the record. In such cases, scoring each record of the identified subset of records can comprise determining a status score based on the current status for the record. This allows the prioritization engine 460 to add priority/urgency to accounts based on their current status. For example, the status score can be based on a pre-defined adjustable list of statuses and scores.

Additionally, or alternatively, the plurality of factors related to each record can comprise an expected yield factor. The expected yield factor can represent a probability of a benefit obtained from further processing of the record. The yield factor can be determined, for example, based on one or more models 465 trained on results of previous processing of the plurality of records. In such cases, scoring each record of the identified subset of records can comprise determining a yield score based on the yield factor. According to one embodiment, the higher the expected yield on the account from the models 465, the higher the yield score can be on the record. In the healthcare example, features the models 465 can use to calculate the expected yield can include, but are not limited to, account balance, payor category, account aging, patient demographics, payments and adjustments, patient coding, and/or others.

The plurality of factors related to each record can additionally, or alternatively, comprise a time factor representing an amount of time since a last processing of the record. In such cases, scoring each record of the identified subset of records can comprise determining a touch score based on the time factor. This allows the prioritization engine 460 to give higher weightage to the accounts that haven't been touched/revisited/processed in a long period.

Additionally, or alternatively, the plurality of factors related to each record can comprise an age factor representing a pendency period of time for the record. In such cases, scoring each record of the identified subset of records can comprise determining a discharge score based on the age factor. In the healthcare example, the longer the account ages post patient discharge, the prioritization engine 460 can add a higher weightage to the final discharge score of the record.

Scoring each record of the identified subset of records can then comprise determining a sum of the status score, the yield score, the touch score, and the discharge score for each record of the identified subset of records 470.

The identified subset of records can then be prioritized by the prioritization engine 460 into an ordered list of records based on the score for each record of the identified subset of records 470 and one or more workflows 450 can be executed on the identified subset of records based on the ordered list of records.

FIG. 5 is a flowchart illustrating an exemplary process for processing database records based on a determined priority for selected database records according to one embodiment of the present disclosure. As illustrated in this example, managing and processing database records can comprise maintaining 505 a plurality of records in a database. Each record of the plurality of records can comprise a record of a service provided to a consumer by a service provider of a plurality of service providers and can identify at least one required action by at least one responsible entity of a plurality of responsible entities.

A subset of records from the plurality of records can be identified 510. The identified 510 subset of records can comprise a plurality of records to be further processed by the records management and processing system. Identifying 510 the subset of records from the plurality of records can be based on a value stored in a field of each record of the plurality of records. For example, identifying 510 a record of the subset of records can be based on the value stored in the field of the record being greater than zero.

Each record of the identified subset of records can be scored 515 based on a plurality of factors related to each record of the identified subset of records. Additional details of an exemplary process for scoring 515 each record of the subset of records will be described below with reference to FIG. 6. The identified subset of records can then be prioritized 520 into an ordered list of records based on the score for each record of the identified subset of records and one or more workflows can be executed 525 on the identified subset of records based on the ordered list of records.

FIG. 6 is a flowchart illustrating an exemplary process for scoring of selected database records according to one embodiment of the present disclosure. It should be noted that while illustrated and described here as a sequence of processes, an order of the processes should not be inferred. Rather, these processes can be performed in various orders or in parallel depending upon the implementation. According to one embodiment, the plurality of factors related to each record can comprise a current status for the record. In such cases and as illustrated in this example, scoring each record of the identified subset of records can comprise determining 605 a status score based on the current status for the record.

Additionally, or alternatively, the plurality of factors related to each record can comprise an expected yield factor. The expected yield factor can represent a probability of a benefit obtained from further processing of the record. The yield factor can be determined, for example, based on a model trained on results of previous processing of the plurality of records. In such cases, scoring each record of the identified subset of records can comprise determining 610 a yield score based on the yield factor.

The plurality of factors related to each record can additionally, or alternatively, comprise a time factor representing an amount of time since a last processing of the record. In such cases, scoring each record of the identified subset of records can comprise determining 615 a touch score based on the time factor.

Additionally, or alternatively, the plurality of factors related to each record can comprise an age factor representing a pendency period of time for the record. In such cases, scoring each record of the identified subset of records can comprise determining 620 a discharge score based on the age factor. Scoring each record of the identified subset of records can then comprise determining 625 a sum of the status score, the yield score, the touch score, and the discharge score for each record of the identified subset of records.