Systems and methods for benefit plan quality assurance and certification
A system for testing a benefit plan for quality assurance is provided. A test adjudication engine is configured to process claims in accordance with the benefit plan, each of the claims having one or more parameters. A database is configured to store the benefit plan and quality assurance data, the quality assurance data including: (a) historical claims, each historical claim having an associated historical adjudication, and (b) new claims, each new claim not having an associated historical adjudication. An interactive dashboard is configured to allow a user to batch claims for processing by the test adjudication engine, from among the historical claims and the new claims, based on the one or more parameters.
1 . A system for testing a benefit plan file for quality assurance, the system comprising:
a test adjudication engine, configured to process claims in accordance with the benefit plan file, each of the claims having one or more parameters, wherein the benefit plan file is a compiled computer object loadable onto the test adjudication engine so as to configure the test adjudication engine to process claims in accordance with the benefit plan file, and wherein the benefit plan file comprises data structures and metadata mapping execution cross-dependencies for function, transaction and service calls of benefit plan components;
a database, configured to store the benefit plan file and quality assurance data, the quality assurance data including: (a) historical claims, each historical claim having an associated historical adjudication, and (b) new claims, each new claim not having an associated historical adjudication; and
an interactive dashboard configured to:
allow a user to batch claims for processing by the test adjudication engine, from among the historical claims and the new claims, based on the one or more parameters, and
present a comparison of the adjudicated batched claims to the historical adjudications.
2 . The system of claim 1 , wherein the parameters include: claim dates, medications claimed, associated drug tier/code, and/or medical procedures claimed.
3 . The system of claim 1 , wherein the parameters include claimant parameters, including: claimant gender, claimant age, claimant medical conditions, and/or number of other claims made by claimant.
4 . The system of claim 1 , wherein the parameters include associated plan parameters, including: PNC status, associated formularies, associated group lists, associated member lists, prior authorizations, in-network or out-of-network, associated plans, associated providers, associated prescribers, associated copay schedules/rule sets, associated prescription networks, deductible schedules/rule sets, and/or out-of-pocket schedules/rule sets.
5 . The system of claim 1 , wherein the interactive dashboard is configured to allow the user to randomly batch claims for processing by the text adjudication engine.
6 . The system of claim 1 , wherein the interactive dashboard is configured to filter out expected differences between the adjudicated batched claims and the historical adjudications.
7 . The system of claim 1 , wherein the interactive dashboard is configured to compare the adjudicated batched claims to one or more baselines derived from the historical adjudications.
8 . The system of claim 1 , wherein the interactive dashboard is configured to tag claims as defining acceptable or expected differences.
9 . A method for testing a benefit plan file for quality assurance, the method comprising:
storing, in a database, the benefit plan file and quality assurance data, the quality assurance data including: (a) historical claims, each historical claim having an associated historical adjudication, and (b) new claims, each new claim not having an associated historical adjudication;
batching, via an interactive dashboard, claims for processing by a test adjudication engine, from among the historical claims and the new claims, based on one or more parameters;
processing the claims, via a test adjudication engine, in accordance with the benefit plan, wherein the benefit plan file is a compiled computer object loadable onto the test adjudication engine so as to configure the test adjudication engine to process claims in accordance with the benefit plan file, and wherein the benefit plan file comprises data structures and metadata mapping execution cross-dependencies for function, transaction and service calls of benefit plan components; and
presenting, via the interactive dashboard, a comparison of the adjudicated batched claims to the historical adjudications.
10 . The method of claim 9 , wherein the parameters include: claim dates, medications claimed, associated drug tier/code, and/or medical procedures claimed.
11 . The method of claim 9 , wherein the parameters include claimant parameters, including: claimant gender, claimant age, claimant medical conditions, and/or number of other claims made by claimant.
12 . The method of claim 9 , wherein the parameters include associated plan parameters, including: PNC status, associated formularies, associated group lists, associated member lists, prior authorizations, in-network or out-of-network, associated plans, associated providers, associated prescribers, associated copay schedules/rule sets, associated prescription networks, deductible schedules/rule sets, and/or out-of-pocket schedules/rule sets.
13 . The method of claim 9 , wherein the interactive dashboard is configured to allow the user to randomly batch claims for processing by the text adjudication engine.
14 . The method of claim 9 , wherein the interactive dashboard is configured to filter out expected differences between the adjudicated batched claims and the historical adjudications.
15 . The method of claim 9 , wherein the interactive dashboard is configured to compare the adjudicated batched claims to one or more baselines derived from the historical adjudications.
16 . The method of claim 9 , wherein the interactive dashboard is configured to tag claims as defining acceptable or expected differences.