How to automate Indiana Medicaid application prep after hospital PE

We built the full Indiana Medicaid application that comes after a hospital presumptive-eligibility handoff and ran Skyvern through it. Skyvern opened one screened hospital case, entered and checked 45 approved values, prepared four follow-up records, and stopped before the penalty-of-perjury signature and submission.

This is a particularly useful Indiana workflow because temporary PE does not finish the job. The full application is what keeps the coverage path moving. A hospital can use Skyvern to turn that handoff into a reliable queue instead of asking financial counselors to re-enter every standard case by hand.

Built and tested by Skyvern

We mapped Indiana's Benefits Portal, Navigator role, separate hospital PE process, and DFR follow-up model from current state sources. Then we built an interactive Indiana training workflow and ran Skyvern from the PE handoff queue to human review.

7 sections · 45 values checked · 4 records prepared · 0 mismatches · 9 minutes 46 seconds

Open the complete Skyvern task

What your team gets

Your team gets a controlled handoff from hospital screening to a review-ready full application. The workflow records the PE handoff, prepares the standard HIP-adult case in the FSSA Benefits Portal, checks every value, stages the follow-up records, and sends the result to an authorized person.

The automation does not enter a synthetic case into Indiana's live PE portal. The state says PE is a real trained-hospital determination and forbids staff from entering information they know is false. Our tutorial starts after that separate hospital event.

How we proved it works

We used Indiana's current PE provider module, Navigator guidance, application page, policy manual, and DFR material to build the workflow. We then created one fictional uninsured adult case and gave Skyvern only the approved hospital packet.

This was a controlled test of the application-preparation workflow. It was not an authenticated FSSA Benefits Portal submission, a live PE determination, or a DFR eligibility result.

The research found a concrete hospital reason to build this system now. An Indiana bulletin says that on September 3, 2026, PE compliance moves to per-determination checks that include whether DFR receives the full application before temporary PE expires. Reverify that rule before publication, but the operating lesson is already clear: the PE-to-full-application handoff needs ownership, timing, and evidence.

From temporary PE to a full application

Indiana uses three different systems for three different jobs:

IHCP Provider Portal
Hospital makes the separate PE determination
        |
        v
FSSA Benefits Portal
Navigator prepares the full application
        |
        v
DFR Agency Portal
Hospital follows authorized case status and document requests

Do not merge those roles. The IHCP Provider Portal handles PE. The Benefits Portal handles the full application. The Agency Portal supports authorized follow-up; it is not application authority.

What you need to get started

For this tutorial, you need a Skyvern account, a fictional or approved case, a field map, the approved follow-up records, and a reviewer.

For live work, the hospital counselor needs certified Indiana Navigator status through an Application Organization, or a properly executed Authorized Representative for Health Coverage appointment. Registered Agency status by itself is not enough to complete or sign an application.

Your queue also needs the PE determination date and the deadline for the full-application handoff. Treat that as an operating clock, not a note buried in the case.

1. Start from the hospital handoff queue

Our fixture is a 45-year-old uninsured Indiana resident living alone. He has one current job, $1,600 in gross monthly income, no other benefits, and no current health coverage. He is not pregnant, disabled, institutionalized, incarcerated, Medicare-eligible, a caretaker, or a former foster youth.

The hospital has already screened the person and recorded the separate PE handoff. A certified Navigator will prepare the full application. DFR still decides whether the person qualifies for HIP or another program.

2. Keep the three Indiana roles separate

The first workflow screen records the hospital staff role, full-application path, PE handoff, determination date, and health-coverage program.

That control prevents three common mistakes:

• treating a Registered Agency user as an application Navigator;
• sending synthetic data into the live PE portal; and
• losing the full-application deadline after a temporary PE result.

If hospital staff act as an authorized representative instead, use the case-specific Indiana form with the intended Apply and Ongoing functions. Both required signatures remain outside the browser task.

3. Give Skyvern the complete approved case

The packet contains:

• applicant identity, address, and contact information;
• one-person household and tax facts;
• Indiana residence and citizenship declaration;
• the HIP route and exception answers;
• current employer, wage, hours, and $1,600 monthly income;
• the PE handoff date;
• Agency Portal release status; and
• four follow-up records.

The fixture does not include bank statements or other asset proof. Indiana says resources are not counted for HIP. Aged, blind, disabled, Medicare, and institutional cases need a different route.

4. Tell Skyvern what to do

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

Open the prepared hospital PE handoff case. Start the full health coverage
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 task has one job: prepare and check the application. It cannot make a PE decision, promise HIP, select a health plan, make a Fast Track payment, or sign for the applicant.

5. Prepare the full HIP-adult application

Skyvern completed:

1. Hospital role and PE handoff
2. Applicant and contact information
3. Household and tax relationships
4. HIP route and coverage checks
5. Current income and benefits
6. Proof and follow-up plan
7. Case documents

The route explicitly checks pregnancy, disability, Medicare, institutional residence, incarceration, former foster care, caretaker status, and current coverage. Any Yes that changes the prepared case should return to trained staff.

The workflow also records No for a promise of retroactive HIP coverage. Indiana's policy says HIP Basic and HIP Plus do not provide retroactive coverage. PE begins from the hospital determination date, not before it.

6. Prepare the full-application evidence

The fixture prepares two wage records, an identity/citizenship record if electronic verification cannot resolve the fact, and the hospital's PE handoff record.

These are for the full application and hospital follow-up. Indiana's PE workflow is different: it uses self-attested preliminary facts and says the qualified provider may not ask for verification documents for the PE determination.

If DFR cannot verify a full-application fact electronically, its checklist generally gives the household 13 calendar days to respond. The actual request should control the upload.

7. Stop before the applicant's decisions

Skyvern reached Ready for human review with 45 of 45 values matched, all four records prepared, and no submission attempt.

The applicant or properly appointed representative reviews the rights and responsibilities, confirms sensitive declarations, signs under penalty of perjury, and decides whether to submit. Plan, POWER Account, and Fast Track choices also stay with the applicant.

Try the workflow yourself

Open the Indiana Medicaid training workflow and use the prompt above. A successful task reaches review with 45 matching values, four prepared records, and no submission attempt.

Then test a missed handoff: remove the PE date or Navigator role from a fictional case. The workflow should stop before application entry.

How to scale this system

Start with the standard HIP-adult handoff used here. Save it as a reusable Skyvern Workflow and connect it to the hospital queue through the API.

The production queue should calculate and show:

• PE determination date;
• full-application handoff deadline;
• assigned Navigator or authorized representative;
• source packet completeness;
• Benefits Portal run status;
• DFR verification due date; and
• final human-review owner.

Use Ready for review, Needs attention, Deadline risk, and Portal changed as explicit outcomes. Connect the separate DFR Agency Portal follow-up only after the client signs the required case-status release.

Add pregnancy, disability, institutional, immigration, inmate PE, and other routes only after each has its own research, field map, test cases, and human boundary.

The Business ROI

Indiana's return has two parts: staff time recovered and fewer PE handoffs left incomplete.

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

PE handoff completion rate =
full applications received before PE expiry / PE cases requiring handoff

For example, 500 ready cases at 20 minutes of manual entry equal about 167 staff hours each month. At $35 per loaded hour, that is about $5,833 in monthly capacity. Those are illustrative inputs, not savings measured by our synthetic test.

The more important hospital dashboard should combine cost per review-ready case with the percentage of PE handoffs that reach a full application before the deadline. That measures both operating efficiency and continuity of the coverage process.

What it takes to use this in production

Before an authenticated Indiana run, confirm:

• the operator is a certified Navigator or properly appointed representative;
• live PE remains in the trained hospital process and never receives synthetic data;
• PE and full-application dates are recorded and monitored;
• Agency Portal access has the separate client release;
• every field and record has an approved source;
• protected information follows your access and retention controls;
• complex routes and unexpected screens return to staff; and
• rights, signatures, plan/payment choices, and submission remain human-controlled.

Recheck the September 3, 2026 PE compliance transition immediately before publication and again during the pilot. Start with approved test cases and keep submission manual while your team validates every prepared application.

Skyvern can handle the repeated browser work between hospital PE and the full Indiana application. Your team keeps the timing, authority, and judgment that determine whether the handoff succeeds.

Talk to Skyvern about automating a healthcare portal workflow

Sources

• Apply for Indiana Medicaid coverage
• FSSA Benefits Portal
• Indiana Navigators and Application Organizations
• Becoming an Authorized Representative
• Indiana Presumptive Eligibility provider module
• IHCP Bulletin BT2026130
• Indiana Medicaid Policy Manual
• FSSA Resource Guide
• DFR Agency Portal
• Synthetic Indiana workflow used in this tutorial