Hospital Intelligence Brief

What Changed in SPARCS Compliance in 2026: Ticketing, Contacts and Security Reviews

Several routines shifted this year: requests moved to a ticketing system, contact reviews became a formal biannual task and new logic now redacts personal information entered in the wrong fields.

Short answer

In 2026, SPARCS compliance and intake requests moved to a ticketing system (required from August 1, 2026), contact lists are reviewed twice a year, outpatient revenue code 0361 became an ambulatory surgery code, new CDC race and ethnicity codes were adopted, and personal information in unlabeled fields is now redacted.[1][2]

Where do SPARCS compliance and intake requests go now?

The biggest change for most compliance teams is procedural. The Department’s submission and reports pages say that starting August 1, 2026, all intake and compliance requests must be submitted through the SPARCS Intake and Compliance ticketing system. The list is broad: updates to contact information, requests for provisioning, exception and extension requests, non-compliance notices and questions about deadlines.[1][3] The ticketing site has two parts, a knowledge center holding frequently asked questions and articles, and a ticketing system for requests.[1]

The July 2026 forum added practical detail. Emails sent to the SPARCS submissions mailbox will be redirected to the ticketing site where a relevant form exists. New forms cover Optum provisioning, reactivations, facility name changes, submitter updates and Hospital Owned Data reports. The forum also advised that the subject and description fields at the end of each form can be skipped by entering “n/a” because they are not routinely used in responding to tickets.[2]

Teams should update internal procedures. A compliance analyst who still emails an extension request may find it redirected, and a request that is slow to be filed can miss the monthly report cutoff.

What does the Optum Help Desk still handle?

The ticketing system does not replace the Optum Help Desk. The Department’s pages say the help desk remains the route for SPARCS portal support, technical issues and claim rejection reports.[1] The forum summary was explicit about the division: contact Optum for portal training and claim testing, file or record rejections, interpretation of edit error reports and technical questions, and do not contact Optum for compliance questions, policy interpretation or compliance exceptions and extensions.[2]

The summary also gave ticket habits. Callers should always provide the facility’s Permanent Facility Identifier. If a facility already has an open ticket for an error report, it should update that ticket by responding to the existing thread or calling the help desk, not open another.[2] Requests for SPARCS data for research use a separate ticketing system and are not handled through either of these.[1]

What changed in codes, classification and edits?

Several technical updates took effect in July 2026. Procedure codes effective July 1, 2026 were loaded into the validation tool on July 16, 2026, and records that had been rejected incorrectly could be resubmitted. Effective July 16, revenue code 0361 (operating room services, minor surgery) was added to the list of codes classified as ambulatory surgery. Records accepted before that date were not updated retroactively, and compliance exceptions may be necessary to reconcile volume shortages caused by the change.[2]

On July 30, 2026, SPARCS began accepting version 1.3 of the CDC race and ethnicity code system. The program also reiterated that every claim needs at least one race code and one ethnicity code, a requirement covered in a separate article in this series.[2]

For analysts, the 0361 change is a reminder that counts by claim type can shift for administrative reasons. A comparison of ambulatory surgery volumes before and after July 16, 2026 should take the reclassification into account.

What is the new approach to personally identifiable information?

The forum summary reported that the program had shared information with facilities that have a pattern of submitting personally identifiable information in fields that are not designed to receive it. New SPARCS logic redacts this data. The program said this is not a remediation issue: no resubmissions are needed. It asked facilities to review their data entry policies so that notes and other details are not entered into fields that are not labeled to receive them, and pointed to a list of loops and segments that frequently contain such information in the resources section of its submission page.[2]

A new biannual review will monitor the issue, and facilities were told to expect contact in November 2026 with an updated summary of any information subject to the redaction logic. The program said its goal is to protect sensitive information without requiring changes to established business processes.[2] The practical lesson is for registration and billing teams: free-text fields are not a place for patient details that belong elsewhere.

What about security reviews and forums?

Two recurring items are worth adding to the calendar. The first is the biannual security assessment of SPARCS contacts, which began with an email in mid-August 2026 asking each facility to confirm its contact list. The second is the quarterly submitter forum, a webinar with updates and a question-and-answer session that the program hosts; its summary notes are posted on the submission page.[1][2]

The forums are where many of the changes described here were announced. A compliance team that reads each summary, even if it cannot attend, will hear about code changes, edit updates and process changes before they affect volumes or rejections.

Frequently asked questions

When did SPARCS compliance requests move to a ticketing system?

The Department’s pages say that starting August 1, 2026, all intake and compliance requests must be submitted through the SPARCS Intake and Compliance ticketing system.[1]

Should we still call the Optum Help Desk?

Yes, for portal support, technical issues, file or record rejections and interpretation of edit error reports, but not for compliance questions or exceptions and extensions.[2]

What happened to revenue code 0361?

Effective July 16, 2026, outpatient claims with revenue code 0361 are classified as ambulatory surgery. Earlier records were not reclassified.[2]

Which race and ethnicity codes does SPARCS accept now?

On July 30, 2026, SPARCS began accepting version 1.3 of the CDC race and ethnicity code system.[2]

What is the PII redaction logic?

New SPARCS logic redacts personal information that facilities enter in fields not designed to receive it. No resubmission is needed, and a biannual review is planned.[2]

What to do next

  1. Update internal instructions so compliance requests go through the ticketing system.
  2. Brief submitters on the division between ticketing and the Optum Help Desk.
  3. Review free-text entry practices in your registration and billing systems.
  4. Read the latest quarterly forum summary.

Explore Your Hospital’s Opportunities

Two Pillars can help hospital leadership investigate market, financial, operational and strategic questions using relevant organizational data, public information and a structured assessment process. A good first step is a SPARCS review that confirms your obligations, contacts and calendar, and sets up a simple routine your team can keep.

Sources

  1. New York State Department of Health, SPARCS Data Submission. Accessed October 2026.
  2. New York State Department of Health, SPARCS Quarterly Submitter Forum Summary, July 30, 2026. Accessed October 2026.
  3. New York State Department of Health, SPARCS Data Submission Compliance Reports. Accessed October 2026.

Sources checked October 2026. This guide is general information for healthcare leaders and is not legal, financial, clinical or compliance advice. Figures and rules are cited to the sources below and may have changed since they were accessed, so confirm anything you rely on against the current source. Two Pillars & Co is independent of the organizations cited. See our editorial policy.