SPARCS Race and Ethnicity Reporting: What Every Claim Must Carry

By Two Pillars & Co Advisory Group · Sources checked October 2026

What does SPARCS require for race and ethnicity?

Race and ethnicity are among the data elements that registration teams collect under time pressure, and among those that most often cause rejected records. The edit that triggers is technical, but the cause is usually a registration practice. The Department’s July 2026 submitter forum summary sets out the current requirements.^[1]

SPARCS requires at least one race code and one ethnicity code on every claim. Multiple race and ethnicity codes may be reported for multiracial patients. Facilities should select the codes that best describe the patient’s race and ethnic origin, and should collect and report the information as granularly as possible.^[1] The requirement is about presence and quality: a claim with no ethnicity code is incomplete, and a claim with a vague category when a more specific one is available is less useful.

How must the information be collected?

The forum summary is direct on this point. Race and ethnicity must be captured through self-reporting by the patient or by a guardian or caregiver. They cannot be assumed from a person’s physical appearance or from preferred language.^[1] A registration process that guesses, or that fills in a default to move the patient along, does not meet the standard.

When a patient declines to answer, the summary says the only options for SPARCS reporting are “other race” (R9) and “unknown ethnicity” (E9).^[1] That gives staff a clear script. The question is asked every time, the patient’s answer is recorded as given, and a declined answer is recorded using the two permitted codes. Leaving the field blank is not an option, because a blank claim will be rejected.

What changed in July 2026?

On July 30, 2026, SPARCS began accepting version 1.3 of the code system published by the Centers for Disease Control and Prevention, referred to in the summary as CDCREC1.3.^[1] Facilities and vendors that map their own registration values to SPARCS codes should check that the mapping uses the current version. A mapping built for an earlier version may send codes that no longer match, or miss new, more granular options.

The change illustrates a general point about SPARCS: code sets are updated periodically, and the forum summaries are where the program announces them. A facility that reads each summary will have time to update interfaces. One that does not may learn of a change from a spike in rejections.

Why do race and ethnicity edits trigger?

Edit P2242041 appears among the edits the program listed as most triggered. It reports that a race code was received without an ethnicity code, or the reverse. The program explained that SPARCS expects at least two iterations in the file, one carrying the race code and one the ethnicity code, and that the “R” or “E” at the start of each code must be capitalized.^[1]

An invented example shows how this happens in practice. A registration screen allows staff to skip the ethnicity question when a patient is in a hurry, and the interface sends the claim with only a race code. Every such claim is rejected. Making the ethnicity field required, and giving staff a standard script that includes the declined response, would remove the cause. The example is hypothetical, but it reflects the pattern the edit describes.

Where can you find more background?

The Department’s resources page lists older materials on race and ethnicity data, including a 2014 toolkit on improving the data and a concordance report comparing how facilities code race and ethnicity with Medicaid and vital statistics data.^[2] Those materials are dated, and a team should read them as background, not as current requirements. The current rules are in the forum summaries and the SPARCS companion guide.

For compliance staff, the practical steps are simple: make both fields required at registration, train staff on self-report and the declined response, map your system’s values to version 1.3, and watch the weekly rejection report for the edit.

Frequently asked questions

What to do next

1. Check that both fields are required at registration.
2. Train staff on self-report and on the R9 and E9 responses.
3. Confirm your mapping uses CDC version 1.3 codes.
4. Review the weekly rejection report for edit P2242041.