OASIS-E2 Is Live: What Changed in April 2026 and What Your Software Must Handle
According to CMS’s OASIS-E2 Data Submission Specifications (v3.02.0), the new item set took effect April 1, 2026, with no grace period and no parallel submission window. Compared to the OASIS-E1 rollout, the change felt quiet: no new all-payer mandate, no full renumbering, none of the pre-launch conference buzz.
In our view, that quiet is exactly what makes OASIS-E2 risky. A loud release gets a project plan. A quiet one gets skipped. The changes are small in count but precise in placement, a renamed item, a timepoint requiring one more field, a discharge item that should no longer appear but still does. These don’t announce themselves immediately. They tend to surface three weeks later, as a rejected claim, a failed iQIES submission, or a Star Rating that stops adding up.
When Does OASIS-E2 Apply?
If M0090 (Date Assessment Completed) falls on or after April 1, 2026, that assessment must use the OASIS-E2 item set, across all assessment types: SOC, ROC, Recertification, Transfer, and Discharge. There was no phase-in period. Any hardcoded item set, outdated schema, or validation logic still pointing to E1 is the first thing to check.
What Actually Changed
M0069 (Gender) is retired. A0810 (Sex) replaces it. Field ID, coding rules, and response instructions all changed. Anything referencing the old M0069_PAT_GENDER field needs updating to A0810, or the result is a validation error or a silent data discrepancy.
A1250 (Transportation) is replaced by A1255. No longer “select all that apply,” it’s now a single-response question on whether lack of transportation interfered with appointments, work, or daily living needs in the past 12 months. It’s also no longer collected at Discharge, only SOC and ROC.
Sensory and language items now required at Resumption of Care. A1110 (Language), B0200 (Hearing), and B1000 (Vision) were SOC-only before. Under E2, they’re required at ROC too, since a patient’s senses or communication ability can change materially during a hospitalization. This is a genuine workflow change: a ROC template missing these fields produces incomplete assessments.
J1900 (Falls) guidance has tightened. Per the October 2025 Quarterly OASIS Q&As and OASIS-E1 errata, the clarified guidance centers on “intercepted falls” and how injury level should be recorded in J1900B and J1900C. Since J1900 feeds the Falls with Major Injury quality measure, and in turn HHVBP scoring and Star Ratings, outdated decision-support text can distort how injury severity gets recorded.
D0150 now accepts a dash (-) response, removing the need for the skip-logic workarounds many agencies were using for “not applicable.”
RFA 03 (Resumption of Care) gained additional data elements beyond the three sensory items above, worth confirming against older, lighter ROC templates.
Get Staffinc.io’s stories in your inbox
Join Medium for free to get updates from this writer.
O0350 (COVID-19 Vaccination Status) is retired entirely. Any rule, skip pattern, or export field tied to it needs to be disabled, not just hidden.
Where the Claim-Rejection Risk Actually Lives
None of these changes is difficult alone. The risk lives in the gap between the published spec and what the software stack still assumes. In our experience, that gap hides in a few specific places:
- Field mappings: an old item ID surviving anywhere in the EMR data model, HL7/CCD export, or billing interface turns into a data integrity issue, not a clean error.
- Templates by timepoint: a single generic template across SOC, ROC, and recertification will miss required ROC items or show items that no longer belong there.
- Validation rules: if pre-submission validation still checks E1 edits, an assessment can pass locally and still be rejected at the CMS gateway, a costlier place to catch it.
- Retired-item leakage: hiding O0350 from the clinician view while still exporting a default value can still trigger an unwanted edit.
- Discharge-specific logic: A1255’s removal from Discharge is a subtraction, not an addition, and in our experience, testing teams generally find it easier to test that a new item appears than that a retired one correctly doesn’t.
A Practical Checklist
- ROC templates include A1110, B0200, B1000, and the new RFA 03 items, without leaking into other timepoints
- A1255 present at SOC/ROC, absent at Discharge
- J1900 decision support reflects current intercepted-falls guidance
- D0150 validation accepts a dash as valid
- O0350 fully retired from forms, skip logic, and exports
- Validation engine matches current iQIES edits, not E1
- Training delivered inside the actual system, not just documented
The Big Idea
OASIS-E2 is a small release by item count, and that’s precisely why it carries more risk than a larger one. A big release gets a project plan. A small one gets treated as a documentation update instead of a software update, and that gap is where claim rejections and quality measure distortions actually happen.
FAQs
Does OASIS-E2 apply to assessments already in progress on April 1, 2026?
The determining factor is M0090. Any assessment completed on or after April 1, 2026 must use OASIS-E2, regardless of when it started.
Why was A1255 removed from Discharge?
CMS scoped the revised transportation item to SOC and ROC only. A Discharge assessment still prompting for it is leftover E1 logic that needs removing.
What happens if our validation engine still checks E1 edits?
An assessment can pass local validation and still fail at the CMS gateway under the current specification, typically a more costly place to catch the same issue.
What’s the highest-risk change for most agencies?
In our view, it’s the sensory and language items now required at ROC. Unlike a renamed field, it’s a real workflow change, and a template that wasn’t updated will generate incomplete assessments.
Staffinc builds home health compliance workflows customised from a proven base model, so item-set changes like OASIS-E2 get mapped into templates, validation, and export logic before they become a claim rejection. See how this works for home health agencies here: https://staffinc.io/us/homecare-software
