Chapter 23: OASIS Submission to CMS
Chapter Overview
What You'll Learn:
- OASIS Submissions tabs
- Batch validate / export / mark submitted
- How CMS iQIES upload works (manual outside Betasky)
- When assessments appear in Ready to Submit
- Sandbox blocks
- What CMS Accepted does (and does not) control
Path: Sidebar → Compliance & reporting → OASIS Submissions → /dashboard/oasis
Billing-only: hidden.
Permission: manage OASIS submissions.
Text-only.
23.1 What You See
- Title: OASIS Submissions
- Refresh Statuses
Tabs:
- Ready to Submit (n)
- Submitted (n)
- Accepted (n)
- Rejected (n)
- Pending Correction (n)
23.2 When a Row Appears (eligibility)
A submission row is created for OASIS assessments (form keys starting with oasis-) when:
- The patient has a primary payer, and
- QA has approved / the episode activation path has run for that assessment type
| Assessment | Typically becomes Ready after |
|---|---|
| SOC / Recert / ROC | QA Approve → episode activation |
| Transfer / Transfer Discharge / Discharge / Death | QA Approve |
Non-OASIS assessments are never submitted to CMS through this page.
Export also expects agency CCN in production (certification gate).
23.3 Ready to Submit — Batch Actions
Select rows, then:
| Button | What it really does |
|---|---|
| Validate Selected | Dry-run: can Betasky build the OASIS XML for each row? This is not the same as assessment Check for Errors / soft alerts |
| Export XML Batch | Download a ZIP of per-assessment XML |
| Submit Batch | Opens Confirm Submission so you can paste one CMS SUBMISSION ID after you uploaded XML in CMS iQIES |
Per row you may also see Export XML and Mark as Submitted.
Betasky does not push XML into iQIES for you. Workflow: Export XML → upload in CMS iQIES → return here and Mark as Submitted with the iQIES ID.
Mark as Submitted
Modal: Confirm Submission
- Enter CMS SUBMISSION ID (paste from iQIES as guided in the helper text)
- Confirm: Yes, Mark as Submitted
Product copy refers to CMS iQIES (not an older “state CASPER-only” story).
23.4 Soft Alerts vs Submissions Validate
| Check | Where | Blocking? |
|---|---|---|
| Check for Errors (CMS Fatal / agency / HHA plan) | Assessment / QA Review | Can block complete / proceed |
| Clinical Plausibility Alerts (soft) | Assessment | Non-blocking |
| Validate Selected | OASIS Submissions | Only whether XML export succeeds |
Do not treat Submissions Validate Selected as a substitute for Check for Errors on the form.
23.5 Sandbox Limits
In sandbox, CMS-facing actions are blocked. Banner explains submissions and XML exports are disabled. You may still see Ready rows; you cannot export/submit for real CMS work.
Blocked feature names in the sandbox modal include:
- OASIS XML Export
- OASIS XML Batch Export
- Validate OASIS Submissions
- Submit OASIS Batch to CMS
- Mark as Submitted to CMS
Use production after go-live for real submission work.
23.6 Accepted vs Operations
- Care Order Active / billing enablement is driven primarily by QA Approve, not by waiting for CMS Accepted.
- Accepted records successful CMS acceptance (staff mark after iQIES).
- Do not teach “no care or billing until CMS Accepted” as the product rule. Signed POC / medical necessity / payer rules still matter for claims separately.
23.7 Rejected / Pending Correction
Work Rejected and Pending Correction tabs:
- Correct the assessment / return through QA if required
- Use notify / force-status actions when shown
- Move back to Ready to Submit, then export and re-upload in iQIES
23.8 Common Mistakes
- Expecting Betasky to electronically submit to CMS — you export XML and upload in iQIES.
- Thinking Validate Selected replaces Check for Errors on the assessment.
- Expecting Non-OASIS assessments on this page — they do not appear.
- Trying to export/submit in sandbox.
- Waiting for CMS Accepted before scheduling — episode is Active after QA Approve.
23.9 Quick Checklist
- Production agency with CCN (not sandbox)
- OASIS (not Non-OASIS) assessments approved into Ready
- Check for Errors done on the assessment before export
- XML exported → uploaded in iQIES → marked with submission ID
- Rejected / Pending Correction worked
