Clearinghouse Cyberattack Response: An Incident Response Guide for Medical Practices

Kevin Henry

Incident Response

Published Updated

10 minutes read
Share this article
Clearinghouse Cyberattack Response: An Incident Response Guide for Medical Practices

A cyberattack on a claims clearinghouse can disrupt billing and other connected services even when a medical practice’s own systems remain operational. This guide focuses on lessons from the Change Healthcare cyberattack, which began on February 21, 2024, and offers steps your practice can adapt for a future clearinghouse outage. The best response separates claims recovery from any investigation of possible security or privacy incidents.

How did the clearinghouse cyberattack affect medical practices?

When a clearinghouse is unavailable, practices may lose access to the services it handles, such as electronic claims submission, claim-status transactions, eligibility checks, or payment-related data. The exact impact depends on your vendor’s role and the payer connections that run through it. During the Change Healthcare disruption, CMS acknowledged effects on provider claims and payments and directed Medicare contractors to help providers change clearinghouses and accept paper claims when needed.

Operational problems can include delayed claims, slower reimbursement, gaps in claim acknowledgments, and extra work to identify which transactions were accepted. A practice may also need to manage the separate possibility that information held by the vendor was exposed. In the Change Healthcare incident, the vendor reported a breach involving protected health information (PHI); the scope and notification responsibilities depend on the specific facts and entities involved. See the CMS response to the Change Healthcare disruption and HHS’s Change Healthcare cybersecurity incident FAQs.

A vendor outage alone does not establish that your practice’s own network was compromised. Still, treat unexpected vendor messages, unusual login activity, or suspicious claims data as potential security signals and escalate them to your designated security contact.

Which claims-processing options can practices use during the disruption?

Confirm which services are unavailable before redirecting claims. Contact your clearinghouse, payers, and billing vendor through verified channels to learn what is working, what is queued, and whether claims already sent have been accepted. Keep a dated record of the instructions you receive.

  • Switch to an alternate clearinghouse. Ask payers and the replacement vendor about enrollment, testing, supported transactions, and the date the new connection can be used. Do not assume an alternate vendor can immediately process every payer or claim type.
  • Ask whether direct submission is available. Some payers may allow a practice or billing service to submit claims through a payer portal or direct electronic connection. Requirements vary. For Medicare electronic claims, CMS says providers must complete the applicable EDI enrollment before submitting directly or through a billing service or clearinghouse. Review CMS’s Medicare EDI enrollment instructions.
  • Use paper claims only when the payer or contractor permits them. CMS directed Medicare contractors to accept paper claims during the 2024 disruption when providers needed that option. That temporary response does not mean every payer accepts paper claims during every outage; verify current instructions and any filing requirements.
  • Track held and submitted claims. Maintain a secure work queue with dates of service, payer, claim status, submission route, and follow-up date. Before resubmitting after service returns, check for accepted claims to reduce the risk of duplicates.

Protect PHI in every temporary workflow. Use approved systems and secure transmission methods, limit access to staff who need the information, and avoid sending claim files through personal email or unapproved storage.

How can practices maintain clinical and operational continuity?

Activate your downtime procedures and assign a lead to coordinate clinical, billing, and patient communications. Preserve access to the information clinicians need for safe care, and prioritize urgent appointments, medication needs, referrals, and follow-up according to clinical judgment. A billing interruption should not replace clinical triage.

If staff must work on paper or in another approved downtime system, record essential details consistently and securely. Define who can create and access temporary records, where they are stored, how they will be reconciled with the electronic record, and when they will be securely retained or destroyed under your policies.

Tell patients about scheduling or administrative delays when those delays affect them, without speculating about a data breach before the facts are established. Make sure staff know where to route questions about appointments, billing, and privacy concerns. HHS advises healthcare organizations to plan for essential functions to continue even when critical systems or internet access are unavailable; its October 2026 cybersecurity newsletter discusses contingency planning and system disruption preparedness.

What steps should an incident response plan include?

A healthcare incident response plan should cover both a vendor outage and a suspected compromise of the practice’s own systems. Identify who can make operational decisions, who contacts vendors and payers, who assesses patient-safety effects, and who coordinates security, privacy, legal, and communications work.

  1. Verify and classify the incident. Confirm whether the problem is a vendor outage, a practice-system issue, or both. Identify affected services, systems, users, and time periods.
  2. Escalate and coordinate. Notify practice leadership, IT or managed security support, the privacy or security officer, and relevant vendors. Use known, verified contact information.
  3. Contain threats without disrupting care unnecessarily. If there are signs of compromise in your environment, follow your security team’s instructions to contain affected accounts or systems while preserving essential clinical operations.
  4. Preserve evidence and document decisions. Keep relevant logs, vendor notices, claim acknowledgments, staff reports, and a timeline of actions. Restrict changes that could destroy evidence until the appropriate responders advise you.
  5. Maintain essential operations. Activate the claims clearinghouse contingency plan and clinical downtime procedures, and assign staff to monitor patient-care and financial backlogs.
  6. Recover, reconcile, and review. Validate restored connections, reconcile held or rejected claims, monitor for further suspicious activity, and document lessons for plan updates and exercises.

The HIPAA Security Rule requires regulated entities to implement security incident procedures and a contingency plan for emergencies affecting systems with electronic PHI. HHS describes required contingency-plan elements, including data backup, disaster recovery, and emergency-mode operations, in its cybersecurity guidance. Its security incident procedures guidance also recommends planning roles, evidence preservation, incident scope assessment, and response testing.

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

How should practices assess and report potential PHI exposure?

Start by asking the clearinghouse or business associate for written details: what systems and dates were involved, what information may have been affected, whether the practice’s data was included, and what response or notification work the vendor will perform. Review your business associate agreement (BAA), including its terms for incident reporting and cooperation, and document your own follow-up. HHS explains that BAAs establish permitted PHI uses and require business associates to report security incidents and breaches as applicable in its Business Associates FAQs.

Work with your privacy or security officer and, as appropriate, legal counsel to conduct and document a fact-specific assessment. Identify the PHI involved, who could access it, whether it was actually acquired or viewed, and what mitigation occurred. Under the HIPAA breach notification rule, a breach of unsecured PHI is generally presumed unless the covered entity can demonstrate an applicable exception or a low probability that the PHI was compromised based on the required assessment factors. A cyberattack or outage by itself does not answer that question.

If notification is required, the covered entity is responsible for ensuring it occurs, although it may delegate notification tasks to its business associate. Individual notices generally must be sent without unreasonable delay and no later than 60 days after discovery. HHS must be notified without unreasonable delay and within 60 days for breaches affecting 500 or more individuals; breaches affecting fewer than 500 individuals may be reported to HHS annually, within 60 days after the calendar year in which they were discovered. Additional media notice rules apply to breaches affecting more than 500 residents of a state or jurisdiction. See the HHS Breach Notification Rule guidance and its incident-specific guidance on coordinating with Change Healthcare.

Do not assume that a vendor’s public announcement completes your practice’s responsibilities. Confirm in writing who will notify affected individuals, HHS, and—if applicable—the media, and retain documentation of the decision and completed notifications.

What temporary financial assistance may be available?

Ask Medicare Administrative Contractors, Medicaid agencies or managed care plans, and commercial payers whether any applicable payment flexibility or hardship process is available. Options depend on the program, payer, state, and circumstances; an advance or interim payment is not guaranteed. CMS encouraged states during the 2024 disruption to consider certain interim Medicaid payments and urged Medicare Advantage plans to consider advance funding for affected providers, but those announcements were not a universal entitlement for every practice.

Be especially careful with historical program information. CMS’s Change Healthcare-specific Medicare Accelerated and Advance Payment program stopped accepting applications after July 12, 2024. It is not a current application route for that incident. For the program’s end date and description, see CMS’s announcement closing the CHOPD payment program.

For any future disruption, contact your payers and state Medicaid agency directly, and ask about eligibility, repayment terms, documentation, and deadlines before relying on a temporary payment. Track delayed receivables and prioritize essential expenses while maintaining normal financial controls.

How can practices prepare for a prolonged clearinghouse outage?

Build redundancy before an incident. Map which clearinghouse supports each payer and transaction, keep an updated list of payer and vendor escalation contacts, and identify a workable alternate submission route. Test alternate enrollment and connectivity in advance where available, rather than waiting until a disruption to discover that a connection is not ready.

Keep a written claims clearinghouse contingency plan alongside your clinical downtime procedures. Include role assignments, approved manual workflows, secure storage and transmission requirements, patient and staff communications, claim tracking and reconciliation, and criteria for returning to normal operations. Review BAAs and vendor security and incident-notification terms, and confirm who is responsible for supplying incident details and coordinating any required notifications.

Exercise the plan with realistic scenarios, such as a multi-day outage, missing claim acknowledgments, unavailable eligibility checks, or a vendor breach notice. Make sure staff know how to escalate concerns and where to find current procedures. HHS’s incident response guidance recommends testing procedures and updating them based on exercises and real incidents.

Conclusion

A strong clearinghouse cyberattack response protects care continuity while restoring claims operations and investigating any potential PHI exposure. Prepare alternate submission routes, maintain secure downtime procedures, coordinate closely with vendors and payers, and document the decisions that support your response. For a potential breach, assess the facts and confirm who is responsible for each required notification rather than assuming the vendor has handled everything.

FAQs.

What should a medical practice do when its clearinghouse is unavailable?

Confirm the scope and expected duration with the clearinghouse through a verified contact method. Activate your contingency plan, notify affected staff, contact payers about alternate submission options, track claims that are delayed or pending, and maintain secure clinical downtime procedures if related systems are affected.

Can practices submit claims directly to payers during the disruption?

Sometimes, but the options depend on the payer, claim type, and the practice’s enrollment and technical setup. Ask each payer whether direct electronic submission, a portal, an alternate clearinghouse, or paper claims are accepted. For Medicare electronic claims, check the applicable MAC’s EDI enrollment requirements before attempting direct submission.

How should a practice respond if patient information may have been exposed?

Escalate the concern to your privacy or security officer, request written incident details from the clearinghouse, preserve relevant records, and document a fact-specific risk assessment with appropriate legal or security support. Determine whether notification is required under the HIPAA breach notification rule, and confirm in writing whether your practice or its business associate will provide any required notices.

What financial assistance is available to affected providers?

Availability depends on the payer, state, and incident. Ask Medicare contractors, Medicaid agencies or managed care plans, and commercial payers about applicable payment flexibility or hardship processes, and confirm deadlines and repayment terms. The Change Healthcare-specific Medicare CHOPD program ended on July 12, 2024, so it is not an open application option for that disruption.

Share this article

Ready to simplify HIPAA compliance?

Join thousands of organizations that trust Accountable to manage their compliance needs.

Get Started Free Today

Related Articles