How IM+CANS batch export works, and why double entry isn't required

Getting a completed IM+CANS assessment into Illinois HFS's provider portal does not have to mean retyping the same client's data a second time. HFS's portal accepts a bulk upload of completed assessments, and Oasys supports that bulk upload directly from a completed, signed IM+CANS, batching up to 50 assessments into one export so an admin uploads one file instead of one row per client.

Why this question matters now

The double-entry problem is the single most common complaint we hear from Illinois practices doing IM+CANS on a system that was not built for it: a clinician completes the assessment in the EHR, and then an admin opens HFS's portal and re-enters the same fields by hand, once per client, because the two systems have never talked to each other. One practice we worked with was doing this across two separate screens for every client before switching.

One clinician at a practice we built this for put it plainly:

Doing IM+CANS took several platforms and never spoke to our EHR. The benefit of having both in one system is that you can get an actual holistic view of both your care and compliance postures on a client-to-client basis.

That gap is not HFS's fault; the department built a real bulk-upload tool. It is a gap in what most EHRs export. This post walks through what the batch process actually requires, and where Oasys closes the gap versus where no EHR, including Oasys, currently can.

What does HFS actually require for submission?

HFS requires completed IM+CANS data to reach its provider portal within 10 business days of the date the assessment was completed or updated, per the department's own provider portal guidance. The portal supports both single-record entry and a bulk upload, and the bulk upload is the only version worth using past a handful of clients.

Oasys tracks the 10-business-day clock the same way it tracks the 180-day reassessment clock: against the date the assessment was actually completed and signed, not the date someone remembers to check. A compliance view sorted by how overdue a submission is turns a deadline a practice could miss into a queue an admin works down in order.

What does the batch export actually need to contain?

HFS's bulk upload expects a file matching the state's own format, not a generic export: the same information a clinician entered on the assessment itself, structured so the portal's importer can read it without manual re-keying, including identifying information tied to each client, the diagnosis codes recorded on the assessment, the relevant dates, and the assessment type (initial, reassessment, or update).

Oasys builds that batch export directly from a completed, signed IM+CANS, mapping close to 700 form fields, across the roughly 58 sections that make up the instrument including its embedded treatment-plan section, into the exact structure HFS's importer expects, and validating the required fields before the export is generated rather than after HFS rejects it. Oasys caps each export at 50 assessments per file, matching HFS's own batch limit, so an admin exporting a date range with 120 completed assessments gets three files, not one broken one.

Where does the manual step still sit?

The manual step that remains, in Oasys and in every EHR we're aware of, is the upload itself: an admin takes the exported batch file to HFS's portal and uploads it there. No EHR has a direct API or SFTP connection into that state system today.

What Oasys removes is everything before that upload: the re-keying of client data, the manual field mapping, and the guesswork about whether a given code pairing or date will pass HFS's validation. The honest way to describe this is that Oasys builds the export correctly the first time; HFS still owns the last click.

What goes wrong when a practice does this by hand?

The most common failure we've seen is not a rejected file. It is a practice quietly falling behind the 10-business-day window because entering client data twice does not scale past a handful of assessments a week, so the state-portal step gets batched into a monthly catch-up instead of happening as each assessment is signed.

Oasys's compliance tracker separates clinician-signed, supervisor-signed (or not applicable), and patient-signed status from the separate question of whether the completed assessment has actually been exported and submitted to the state, so a practice can see submission lag as its own queue rather than discovering it inside a denied claim.

The practical shape of getting submission right

Bulk upload is not a state feature Oasys turned on. It is Oasys mapping close to 700 fields into the exact structure HFS's importer expects, capping files at the state's own 50-document limit, and validating the fields HFS will check, so the file an admin uploads passes on the first try. The upload itself stays with HFS. Everything that used to be double entry does not have to be.

FAQ

Can IM+CANS be submitted to Illinois HFS in batches instead of one at a time?

Yes. HFS's provider portal supports a bulk upload of up to 50 assessments per file. Oasys generates that export directly from completed, signed IM+CANS assessments, formatted to match what HFS's portal expects.

Does Oasys support bulk upload for Illinois Medicaid assessments?

Yes. Oasys batches up to 50 completed IM+CANS assessments into a single export formatted to HFS's requirements, so an admin uploads one file per date range instead of one record at a time.

Does Oasys submit IM+CANS to the state portal automatically?

No. Oasys builds the batch export; an admin still uploads that file to HFS's portal directly. That upload step is manual in every EHR we're aware of, not unique to Oasys.

How long does a practice have to submit a completed IM+CANS?

HFS requires the data to reach its provider portal within 10 business days of the date the assessment was completed or updated. Oasys tracks that window against the actual completion date, not a manually logged reminder.

Why does double data entry happen with IM+CANS in the first place?

Because most EHRs export nothing HFS's portal can import directly, so an admin re-enters each client's data by hand on the state site. Oasys avoids that by supporting bulk upload in a format that matches what HFS's portal expects, so the manual work drops from one entry per client to one upload per date range.

Ten business days is not a long window once entry is manual. Batching the export is what makes the window survivable.