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 -5720: Inconsistent A1005 Item

Edit -5720 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 A1005 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 7 items: A1005A, A1005B, A1005C, A1005D, A1005E, A1005X, and more. The iQIES error guide v2.4 has no entry for this edit effective after 2026-03-31; its last entry is quoted below.

What CMS's data specification says about -5720

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

(a) At least one active item from A1005A to A1005Y must equal [1]. (b) If A1005A=[1], then all active items from A1005B through A1005E must equal [0], and A1005Y must equal [0]. (c) If A1005B=[1] or A1005C=[1] or A1005D=[1] or A1005E=[1], then A1005A must equal [0] and A1005Y must equal [0]. (d) If A1005X=[1], then A1005Y must equal [0]. (e) If A1005Y=[1], then all active items from A1005A to A1005X must equal [0].

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

What the iQIES error message for -5720 says

CMS's OASIS Error Message Reference Guide v2.4 (Excel, posted 2026-02-05) has no entry for -5720 with an effective end date after 2026-03-31, although the data specifications V3.02.0 still list the edit as current. The guide's last entries for -5720, copied in full with the dates CMS gives:

-5720a(ended 2026-03-31)

Error ID
-5720a
Severity
Fatal
Type
Consistency
Error message
Inconsistent A1005 Item: At least one active item A1005A through A1005Y must be checked [1].
Potential cause
At least one Ethnicity item must be checked (A1005A through A1005Y).
Tips
Provide a valid response for A1005A through A1005E and ensure that at least one of these items is checked [1].
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2026-03-31

-5720b(ended 2026-03-31)

Error ID
-5720b
Severity
Fatal
Type
Consistency
Error message
Inconsistent A1005 Item: If A1005A is checked (1), then all active items from A1005B through A1005E and A1005Y must not be checked (0)
Potential cause
The value submitted in the Ethnicity items A1005B through A1005E or A1005Y is not consistent with the value submitted in item A1005A (No, not of Hispanic, Latino/a, or Spanish origin).
Tips
IF A1005A is checked [1],THEN items A1005B through A1005E and A1005Y must be unchecked
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2026-03-31

-5720c(ended 2026-03-31)

Error ID
-5720c
Severity
Fatal
Type
Consistency
Error message
Inconsistent A1005 Item: If any item A1005B through A1005E is checked (1), then A1005A and A1005Y must not be checked (0).
Potential cause
The value submitted in the Ethnicity items A1005A and A1005Y is not consistent with the value submitted in A1005B through A1005E
Tips
IF any items A1005B through A1005E is checked [1],THEN A1005AAND A1005Y must be unchecked [0].
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2026-03-31

-5720d(ended 2026-03-31)

Error ID
-5720d
Severity
Fatal
Type
Consistency
Error message
Inconsistent A1005 Item: If A1005X is checked (1), then A1005Y must not be checked (0).
Potential cause
The value submitted in Ethnicity item A1005Y (declines to respond) is not consistent with the value submitted in item A1005X (Unable to respond).
Tips
IF A1005X is checked [1],THEN A1005Y must be unchecked [0].
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2026-03-31

-5720e(ended 2026-03-31)

Error ID
-5720e
Severity
Fatal
Type
Consistency
Error message
Inconsistent A1005 Item: If A1005Y is checked (1), then all active items A1005A through A1005X must not be checked (0).
Potential cause
The values submitted in Ethnicity items A1005A through A1005X are not consistent with the value submitted in item A1005Y (Declines to Respond).
Tips
IF A1005Y is checked [1],THEN items A1005A through A1005X must be unchecked [].
Action
Make appropriate corrections to the records and resubmit.
Effective start date
2023-01-01
Effective end date
2026-03-31

Items this edit checks

CMS's Item List for -5720 names 7 items.

Item IDDescription (CMS)Item page
A1005AEthnicity: No, Not Hispanic, Latino/a, SpanishA1005
A1005BEthnicity: Yes, Mex, Mex Amer, Chicano/aA1005
A1005CEthnicity: Yes, Puerto RicanA1005
A1005DEthnicity: Yes, CubanA1005
A1005EEthnicity: Yes, Another Hispanic/Latino/SpanishA1005
A1005XEthnicity: Patient unable to respondA1005
A1005YEthnicity: Patient declines to respondA1005

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 -5720 fatal or a warning?

Fatal. CMS lists edit -5720 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 -5720?

CMS's Item List for edit -5720 names 7 items: A1005A, A1005B, A1005C, A1005D, A1005E, A1005X, A1005Y. The full list with descriptions is in the table above.

How do I fix OASIS edit -5720?

CMS's OASIS Error Message Reference Guide v2.4 has no entry for -5720 effective after 2026-03-31. Its last entry, -5720e, gave this action: "Make appropriate corrections to the records and resubmit." The data specifications V3.02.0 still list the edit as current, so the edit text above is the rule to meet.

Which records does edit -5720 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_5720.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.