How to automate Illinois Medicaid application prep in ABE

We built the repetitive part of an Illinois Medicaid application as a working browser workflow and gave it to Skyvern. Starting with one approved hospital case, Skyvern entered 40 values, prepared four case records, checked its work, and stopped with the application ready for a person to review.

The point is not one faster form. It is a system that can take standard cases out of a hospital queue, do the copying and checking, and give financial counselors more time for patients, missing information, and difficult cases.

Built and tested by Skyvern

We mapped Illinois's ABE Provider Portal workflow from current state sources, built an interactive Illinois training workflow, and ran Skyvern from the hospital queue to the final human checkpoint.

7 sections · 40 values checked · 4 case records prepared · 0 mismatches · 9 minutes 28 seconds

Open the complete Skyvern task

What your team gets

Your team gets a controlled workflow for a standard Illinois ACA-adult case. It takes approved information from the hospital record, prepares the healthcare-only application, stages the case evidence, compares every entered value with its source, and sends the result to an authorized person.

Illinois adds an important control at the start: the applicant must accept the Fraud Penalty Affidavit before application entry. The automation begins after that action and stops before the final attestation and Submit.

How we proved it works

We used the state's ABE application guide, Provider Access guidance, and current Medicaid application requirements to build the field map. We then created a fictional Illinois adult case with a recent change in work hours and gave Skyvern only the approved source packet.

This was a controlled browser test, not an authenticated ABE submission. It proves that Skyvern completed the workflow we built. It does not prove access to a hospital's Provider Portal account, an eligibility result, or a production success rate.

The research changed the design in three Illinois-specific ways:

• the workflow uses the ABE Provider Portal, not a Community Partner staff account;
• it has an applicant-controlled affidavit before data entry and a second human checkpoint before submission; and
• it does not call the case hospital presumptive eligibility. Illinois currently waives broad HPE and keeps narrower pregnancy and family-planning PE paths separate.

From hospital intake to human review

The approved hospital record remains the source of truth. Skyvern moves those approved facts through the browser. It does not decide what the application should say.

Hospital assistance queue
        |
        v
Approved case facts and evidence
        |
        v
Applicant accepts the opening affidavit
        |
        v
Skyvern prepares and checks the ABE application
        |
        v
Authorized person attests, signs, and submits

That split makes the run auditable. Your source system shows what should have been entered. Skyvern's action record shows what happened. The final reviewer owns the legal action.

What you need to get started

For the tutorial, you need:

• a Skyvern account;
• one fictional or properly approved test case;
• a field map from your hospital intake to the Illinois application;
• the approved evidence linked to that case; and
• an authorized reviewer.

For production, your organization also needs the correct ABE role. Provider Portal users need the state registration, Medicaid provider ID, and Agency Security Administrator or HFS approval described in ABE Provider Access Help.

A Community Partner role is different. Illinois says Community Partners may help while the applicant uses their own account; they should not submit applications from a shared staff account. Keep those two operating models separate.

1. Choose the case and the correct Illinois path

Our fixture is one uninsured Illinois adult, age 45, living alone and applying for healthcare only. She has one job, recently lost hours, has no current insurance, and wants the state to consider a recent hospital bill.

It stays out of pregnancy, aged/blind/disabled, Medicare, long-term care, MPE, and FPPE routes. An authorized person chose that route before Skyvern started.

The first operating rule is simple: do not send every case into one large automation. Start with a standard case type. Return unusual facts and unsupported combinations to staff.

2. Confirm authority before the browser work begins

The Illinois workflow uses approved-representative authority in the Provider Portal. The applicant has already completed the opening affidavit checkpoint.

Skyvern records the prepared path, authority, affidavit status, and organization provider identifier. It does not create that authority or click an affidavit for the applicant.

If your hospital only provides Community Partner assistance, the applicant owns the ABE account and controls the submission. If the case uses an approved representative, both the applicant and representative need the required appointment signatures.

3. Give Skyvern one approved source packet

Our source packet contains:

• applicant identity, address, and contact details;
• one-person household and tax-filing facts;
• citizenship, residence, insurance, and coverage answers;
• current wages and the date the applicant's hours changed;
• a request to consider a recent medical bill; and
• four evidence records associated with the case.

Every blank in the browser has one source value beside it. If the source is missing, the workflow should stop. A guessed answer is a failed run even if the browser reaches the final page.

4. Tell Skyvern exactly where to stop

Create a Skyvern Browser Task with the Illinois workflow URL. We used this instruction:

Open the prepared hospital case and start the new application.

For every section, copy each value from the Approved source packet into
the matching blank field exactly. Choose the exact matching option in
dropdowns. Save and continue after each section.

In Case documents, click Add approved copy for every listed record.
Continue to the final review.

Finish only when the page says Ready for human review and shows zero
mismatches, every document prepared, and Submission Not attempted.
Do not return to the queue.

The instruction gives Skyvern a source, a narrow job, a measurable finish line, and a hard stop. It does not ask Skyvern to judge eligibility.

5. Move through the standard ABE case

Skyvern completed the following sections:

1. Authority and application path
2. Programs requested
3. Applicant and contact information
4. Household and tax filing
5. Coverage and eligibility factors
6. Income and recent changes
7. Case documents

The recent reduction in hours matters operationally. Illinois uses electronic sources when possible, but a change that has not reached those sources may lead to a proof request. Our workflow records the current fact and keeps the supporting employer statement ready.

These are neutral training labels based on the public field map. Confirm the exact current Provider Portal screen names and branching in an authorized pilot before production.

6. Prepare only the evidence tied to this case

The fixture prepares four records: a recent pay stub, an employer hours statement, a hospital bill, and an identity/citizenship record if electronic verification cannot resolve the fact.

Illinois may verify some facts without documents or send a letter asking for different proof. The automation should not upload a universal bundle. It should respond to the case and the state's actual request.

ABE also has a post-submission proof flow. Because this tutorial stops before submission, Prepared is the honest status. It does not claim HFS received or accepted a file.

7. Send a clean application to a person

At the final screen, the workflow compared the entered application with the source packet. Skyvern reached the same human checkpoint with all 40 values matched and all four records prepared.

The final reviewer checks the facts, rights and responsibilities, electronic attestation, representative signature when required, and submission. Illinois determines eligibility, not the hospital or Skyvern.

Try the workflow yourself

Open the Illinois ABE training workflow and use the prompt above.

A successful run should enter 40 approved values, prepare four case records, report zero mismatches, and stop at Ready for human review. Test a failure path too: remove one required source value and confirm the case cannot advance.

How to scale this system

Once the standard ACA-adult case works in an authorized pilot, save it as a reusable Skyvern Workflow. Your hospital queue can start a run when a case becomes ready, pass the approved record into the workflow, and write the result back through a webhook.

Use three clear outcomes:

• Ready for human review: the source comparison passed;
• Needs attention: a fact is missing, contradictory, or out of scope; and
• Portal changed: Skyvern found an unexpected page or control.

Add pregnancy, disability, long-term care, representative, MPE, and FPPE cases only after each has its own field map, test cases, and review boundary. Use a managed Browser Profile for approved portal access and keep every run's action record.

The Business ROI

The return comes from removing repetitive entry from standard cases while financial counselors focus on patients, exceptions, and final review.

Monthly entry hours addressed =
ready applications x manual entry minutes / 60

Monthly entry cost addressed =
monthly entry hours x loaded staff cost

For example, 500 ready cases at 20 minutes of manual entry equal about 167 staff hours each month. At $35 per loaded staff hour, that is roughly $5,833 in monthly capacity. This is an illustration, not a saving measured by our synthetic test.

The better operating metric is cost per review-ready application. Track entry time, human review time, source mismatches, exception rate, proof failures, and completed cases. That tells you whether the system creates capacity without moving hidden work into the review queue.

What it takes to use this in production

Before Skyvern touches an authenticated ABE account, confirm:

• the hospital and operator have the correct Provider Portal access;
• the applicant completed the opening affidavit;
• representative or applicant-directed authority is recorded;
• protected information follows your security and retention controls;
• every entered value and case record has an approved source;
• unexpected screens and complex program routes return to staff;
• actual state requests control proof upload; and
• final attestations, signatures, and submission remain human-controlled.

Start with fictional or approved test cases. Keep submission manual while your team compares every prepared application with its source. Expand only after each case type has passed its own tests.

Skyvern can handle the browser work between a ready hospital case and ABE's human checkpoint. Your team keeps the authority, judgment, and final decision to submit.

Talk to Skyvern about automating a healthcare portal workflow

Sources

• ABE Provider Access
• ABE Provider Access Help
• Introduction to the Application for Benefits Eligibility
• Guide to ABE for Community Partners and Illinois Assisters
• Applying for Medicaid
• Illinois Medicaid Presumptive Eligibility
• Illinois federal demonstration record
• Skyvern core concepts
• Synthetic Illinois workflow used in this tutorial