SPARCS Extensions and Exceptions: Which to Request and What to Include

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

What is the difference between a SPARCS extension and an exception?

Facilities sometimes use the two words interchangeably, but the Department’s request form defines them separately, and each answers a different problem. An extension allows a facility additional time to submit its data for specified periods of non-compliance. The facility should describe what is causing the delay in submission. An exception means the facility is no longer required to meet its compliance target for data submitted to SPARCS. It applies when a facility has a valid reason for submitting fewer records than expected, or has verified that the number of records submitted is correct.^[1][2]

A simple way to remember it: an extension is for data that exists but has not yet been submitted; an exception is for data that does not exist, because activity was genuinely lower than the facility’s history would predict. Choosing the wrong one wastes time. A facility that asks for an exception while still holding unsent records will be asked to submit them first.

When should a facility request an extension?

An extension fits when records are late but will arrive. Examples include a vendor interface that failed and is being repaired, a backlog of rejected records being corrected, or a system conversion that delayed file generation. The protocol says SPARCS Coordinators can request an extension by completing the request template, and that the request needs details of the service or claim types, months and years requiring the extension, the circumstances that caused the delay and the estimated time needed to complete submission.^[2]

The request form adds that an extension request must include a reason for the delay and a detailed plan for submission, including an anticipated timeline for completion.^[1] The plan is the part that distinguishes a credible request from a hopeful one. It should say which records, what will be fixed, who will do it and by when.

When should a facility request an exception?

An exception fits when a facility’s volume is below its target for a real, explainable reason and all data have been submitted. The form lists examples of such reasons: suspension of services due to a public health emergency, staff turnover and closure for renovations.^[1] The protocol adds natural disasters and shifts in providers that affect procedure volume.^[2]

The form requires an exception request to include confirmation that the facility has submitted all data for the specified period and a specific reason for the volume shortage, if known.^[1] The protocol also notes that vendor issues are not an acceptable reason for an exception. It explains why accuracy matters: because future targets are based on each facility’s prior submissions, a facility should verify that all data are submitted and that exceptions are warranted.^[2]

An illustration: a facility closed its endoscopy suite for six weeks for a ventilation upgrade. Volume for ambulatory surgery fell below target for the affected months. After confirming that every record from the period had been submitted, the Coordinator requested an exception for ambulatory surgery for those months, giving the dates and the reason. The example is invented, but it follows the form’s requirements.

What are the timing and process rules?

Timing is strict. The form’s instructions say requests must be submitted at least three business days before the end of the month to be included in the next monthly compliance report.^[1] A request filed after that point does not change the report that is about to be produced, which can leave a facility listed as non-compliant even though the explanation was on its way.

Requests may be submitted by the designated SPARCS Coordinator or by a SPARCS Contact. Every field must be completed, and one template may be used for more than one facility if each has the same Coordinator or Contact.^[1]

The process for submitting changed in 2026. The Department’s submission page says that starting August 1, 2026, all intake and compliance requests, including exception and extension requests, non-compliance notices and questions about deadlines, must be submitted through the SPARCS Intake and Compliance ticketing system, which does not replace the Optum Help Desk for portal support and technical issues.^[3] The request form on file is dated August 31, 2022 and tells readers to email the submissions mailbox, so facilities should use the ticketing system instead.^[1][3]

How do classification changes affect requests?

Some shortfalls arise because the program changed how a code is classified, not because the facility did anything differently. The July 2026 forum described one: effective July 16, 2026, outpatient claims with revenue code 0361 (operating room services, minor surgery) are classified as ambulatory surgery, and records accepted before that date were not updated. The summary noted that compliance exceptions may be necessary to reconcile volume shortages caused by the change in classification from expanded outpatient data to ambulatory surgery.^[4]

This is a good example of why facilities should read each quarterly forum summary. A change in classification can move a facility’s volume between claim types and make a target look missed. When that happens, a clear, specific exception request that names the code and the date is likely to be easier to process than a general explanation.

Frequently asked questions

What to do next

1. Decide whether your problem is late data (extension) or lower real activity (exception).
2. Confirm that all available data have been submitted before requesting an exception.
3. Gather dates, causes and, for extensions, a completion timeline.
4. File through the ticketing system at least three business days before month end.