October 1 update. Our PDGM and ICD-10 tools now use the FY2027 code set: 190 codes added, 30 deleted, and no existing code changed clinical group.

See what changed
Lifetime rate: $24/mo

OASIS edit -5920: Inconsistent Item

Edit -5920 is a fatal consistency edit in CMS's OASIS-E2 data specifications V3.02.0, effective for records with completion dates on or after 2026-04-01. iQIES reports it as "Inconsistent Item". A fatal edit rejects the record: "Records with fatal errors will be rejected. All fatal errors in a record must be corrected and resubmitted." It checks 3 items: J0510, J0520, J0530. CMS's action: "Make appropriate corrections to the records and resubmit."

What CMS's data specification says about -5920

CMS's OASIS-E2 Data Submission Specifications V3.02.0 (HTML edit page oe_5920.html, generated 11/05/2025) list edit -5920 with edit type Consistency and severity Fatal. The edit text, as CMS publishes it:

(a) If J0510=[0], then all active items from J0520 through J0530 must equal [^]. (b) If J0510=[1,2,3,4,8], then all active items from J0520 through J0530 must not equal [^].

CMS's overview document defines this edit type: "Consistency edits define logical constraints among multiple items."

What the iQIES error message for -5920 says

CMS's OASIS Error Message Reference Guide v2.4 (Excel, posted 2026-02-05 on the QTSO reference manuals page) has 2 current entries for this edit. Each is copied in full, with whitespace normalised:

-5920a

Error ID
-5920a
Severity
Fatal
Type
Consistency
Error message
Inconsistent Item: If J0510 Pain Effect on Sleep is equal to Does not apply [0], then all active items from J0520 through J0530 must be skipped [^].
Potential cause
The value submitted in item J0510 is not consistent with one or more values submitted for other pain related items.
Tips
If J0510 is Does Not Apply [0], then all active items from J0520 through J0530 must be skipped [^].
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2099-12-31 (CMS uses this date for an open-ended entry)

-5920b

Error ID
-5920b
Severity
Fatal
Type
Consistency
Error message
Inconsistent Item: If J0510 Pain Effect on Sleep is equal to [1,2,3,4,8], then all active items from J0520 through J0530 must not be skipped [^].
Potential cause
The value submitted in item J0510 is not consistent with one or more values submitted for other pain related items.
Tips
If J0510 has a value other than zero, [1,2,3,4,8], then all active items from J0520 through J0530 must not be skipped [^].
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2099-12-31 (CMS uses this date for an open-ended entry)

Items this edit checks

CMS's Item List for -5920 names 3 items.

Item IDDescription (CMS)Item page
J0510Pain effect on sleepJ0510
J0520Pain interference with therapy activitiesJ0520
J0530Pain interference with day-to-day activitiesJ0530

What happens to the record

CMS's overview, section 6.4, on fatal edits: "Violation of a fatal edit will result in rejection of the submission file." CMS's iQIES error message guide: "Records with fatal errors will be rejected. All fatal errors in a record must be corrected and resubmitted."

Which records this edit applies to

Data specifications version 3.02 has an effective start date of 2026-04-01 and no end date (CMS overview, Table 1). CMS selects the edit set by the record's completion date: "When a submitted record is validated by the iQIES system, its completion date is evaluated and is used to load the appropriate set of edits for the specifications in effect on that date."

Frequently asked questions

Is OASIS edit -5920 fatal or a warning?

Fatal. CMS lists edit -5920 with severity Fatal in the OASIS-E2 data specifications V3.02.0. The CMS overview states: "Violation of a fatal edit will result in rejection of the submission file." The iQIES error guide adds: "Records with fatal errors will be rejected. All fatal errors in a record must be corrected and resubmitted."

Which OASIS items can trigger edit -5920?

CMS's Item List for edit -5920 names 3 items: J0510, J0520, J0530. The full list with descriptions is in the table above.

How do I fix OASIS edit -5920?

CMS's OASIS Error Message Reference Guide v2.4 gives this action for -5920a: "Make appropriate corrections to the records and resubmit." Its tips: "If J0510 is Does Not Apply [0], then all active items from J0520 through J0530 must be skipped [^]." The guide has 2 entries for this edit (-5920a, -5920b); each is quoted above.

Which records does edit -5920 apply to?

Under version 3.02 of the data specifications, records whose completion date, item M0090_INFO_COMPLETED_DT, is on or after 2026-04-01, the effective start date CMS gives that version. Records completed earlier are checked under the version in effect on their completion date (CMS overview, Table 1 and section 3.2); the effective start date on each guide entry above is the date CMS's error guide gives that entry. The CMS overview states: "When a submitted record is validated by the iQIES system, its completion date is evaluated and is used to load the appropriate set of edits for the specifications in effect on that date."

Sources

  1. CMS, OASIS-E2 Data Submission Specifications V3.02.0 FINAL (zip): HTML edit page oe_5920.html and the Unduplicated Edits By ID Report. https://www.cms.gov/files/zip/oasis-e2-data-specs-v3-02-0-final-zip.zip (download page: https://www.cms.gov/medicare/quality/home-health/data-specifications)
  2. CMS, OASIS Data Submission Specifications Overview, Version 3.02.0, October 29, 2025 (in the same zip).
  3. CMS QTSO, OASIS Error Message Reference Guide v2.4 (Excel), posted 2026-02-05. https://qtso.cms.gov/system/files/qtso/OASIS%20Error%20Message%20Reference%20Guide%20FINAL%202.4.26.xlsx

CMS text on this page is copied from CMS's documents without rewording; whitespace is normalised, and one rendering artifact in CMS's HTML (a double quote standing in for an apostrophe) is corrected to the apostrophe in CMS's PDF report. This page is maintained by Logicly, which is not affiliated with CMS. Checked against the CMS files on 2026-10-16.