How to Respond to a Cyberattack Causing a Pharmacy Claims Outage
How should pharmacy staff report and contain a suspected cyberattack?
Report unusual system behavior, suspicious messages, unexpected claim responses, or a sudden claims adjudication failure through your pharmacy’s incident-reporting process. Notify the pharmacist in charge, designated security or IT contact, and management promptly. Record what happened and when, but do not investigate by opening suspicious files or using potentially compromised systems.
If a device appears infected, follow the incident response team’s instructions to isolate it from the network. CISA recommends isolating affected systems and cautions against powering them off unless disconnecting them is not possible, since shutdown can destroy evidence held in memory. Use a separate, trusted phone or other out-of-band channel to communicate if instructed. CISA and MS-ISAC Ransomware Guide
Do not enter patient or payment information into a system suspected of compromise. Preserve relevant alerts, error messages, and transaction records according to your organization’s instructions. HIPAA requires covered entities and business associates to identify and respond to suspected or known security incidents, mitigate harmful effects when practicable, and document incidents and outcomes. HHS guidance on HIPAA security incident procedures
An outage alone does not establish that protected health information was breached. Refer suspected exposure to your privacy or security lead for assessment; notification obligations depend on the circumstances and whether unsecured protected health information was involved. HHS Breach Notification Rule guidance
How do you activate pharmacy downtime procedures?
Use your organization’s pharmacy downtime procedures and follow the assigned roles for the pharmacist in charge, technicians, IT, and management. A covered entity’s HIPAA contingency planning must include procedures that enable critical business processes to continue in emergency mode while protecting electronic protected health information. The specific workflow should come from your organization’s tested plan, not an improvised workaround. HHS ransomware and HIPAA guidance
Confirm which systems are unavailable before switching workflows. The claims processor may be down while the prescription system remains usable, or a cyberattack may make multiple systems unsafe. Only use systems that the incident response team has approved; do not reconnect devices or restore from backups until authorized personnel confirm they are safe.
If staff must use a manual prescription workflow, record the information your approved downtime form requires, such as the patient and prescription identifiers, prescriber, time, action taken, and claim status. Keep paper records secure, restrict access, and avoid placing patient information on unsecured notes or personal devices. Mark each prescription clearly so staff can distinguish work completed manually from transactions still awaiting processing.
How should prescriptions be prioritized to protect patient care?
Have the pharmacist assess clinical urgency rather than prioritizing by insurance response or convenience. Consider the risk of delaying therapy, the patient’s remaining supply, the medication’s time sensitivity, and whether a prescriber or another care setting needs to be contacted. Escalate urgent clinical concerns to the pharmacist in charge and contact the prescriber when clarification or an alternative plan is needed.
Use the pharmacist’s judgment and applicable state law and organizational policy when deciding whether a prescription can be dispensed during the outage. An outage does not by itself authorize an exception to prescription, controlled-substance, or documentation requirements. If the prescription cannot be safely or lawfully completed through the downtime process, explain the delay and help the patient identify the appropriate next step.
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free TodayWhat approved options can pharmacies use when claims processing is unavailable?
Start with the pharmacy help desk escalation path in your downtime plan. Contact the claims switch, payer or pharmacy benefit manager (PBM), and other designated support contacts using verified contact information. Ask whether the issue is a local connection problem, a processor outage, or a broader incident, and obtain approved instructions for handling affected claims.
Use an alternate claims processor only if your organization and payer or PBM have approved that route and the system is trusted. Do not send patient information through an unapproved service, bypass claim edits, create a false approval, or repeatedly resubmit a transaction when its status is unknown. Keep a record of the response and any transaction reference supplied by the processor.
If claims cannot be adjudicated, follow the payer’s and pharmacy’s approved process for holding the claim or handling a patient-pay transaction. Explain any available self-pay option and its terms before proceeding; do not promise that insurance will reimburse the patient later unless the plan or payer confirms that. Keep the prescription and claim documentation needed for held claim reprocessing once the appropriate systems are available.
How should staff communicate outage impacts and payment options to patients?
Give patients a clear, factual update: claims processing is unavailable, what that means for their prescription, and what the pharmacy can do next. Avoid guessing about when service will return or telling patients that a claim has been paid or approved when it has not.
Explain any pharmacy-approved payment choices, including the amount due and whether the pharmacy has confirmed a path for later insurance submission. If the patient pays out of pocket, provide the applicable receipt and explain that later reimbursement depends on the plan’s rules; do not guarantee payment by the insurer. If a prescription is delayed, direct clinical questions to the pharmacist and, when appropriate, coordinate with the prescriber.
Use approved communication channels and share only the information needed to assist the patient. If the incident may have exposed protected health information, refer questions about possible privacy impact to the designated privacy or security contact rather than speculating. HHS guidance describes notification requirements for breaches of unsecured protected health information; whether they apply requires an assessment of the facts. HHS Breach Notification Rule guidance
How should pharmacies reconcile and reprocess claims after service is restored?
Wait for authorized technical staff and the claims processor to confirm that the relevant systems are available and safe to use. Follow the processor’s recovery instructions; service appearing online does not establish that every held transaction has been completed or that systems affected by a cyberattack are ready for use.
Compare the downtime log, prescriptions dispensed, and processor transaction history. Identify which claims were never submitted, which were rejected, and which received an accepted response. Reprocess held claims according to payer or PBM instructions, verifying each response before trying again so staff do not create duplicate transactions or assume an unresolved claim was paid.
Complete transaction reconciliation by matching each prescription and payment outcome to its record. Investigate unmatched, duplicate, rejected, or uncertain claims; correct errors using the processor’s approved process; and document the resolution. Escalate discrepancies that cannot be resolved through the pharmacy’s normal workflow to the payer, PBM, switch, or pharmacy help desk.
In short, protect patient care with a controlled downtime workflow, use only approved claims and payment options, communicate uncertainty clearly, and reconcile every held transaction after systems are confirmed safe and available.
FAQs
What should pharmacy staff do first during a suspected cyberattack?
Report it immediately through the pharmacy’s incident process, notify the pharmacist in charge and designated security or IT contact, and follow instructions to isolate suspected affected devices. Avoid using systems that may be compromised. CISA recommends isolating affected systems and warns that powering them off can destroy evidence unless disconnecting them is not possible. CISA and MS-ISAC Ransomware Guide
How can a pharmacy process prescriptions during a claims outage?
Follow the pharmacy’s approved downtime procedures and have the pharmacist assess clinical urgency and applicable requirements. Use a manual workflow only if authorized, keep required records secure, and contact the payer or PBM for instructions on holding or handling claims. Do not treat an unavailable claims response as an approval.
What should patients know if insurance claims cannot be submitted?
Tell patients that the pharmacy cannot confirm insurance coverage or claim payment while processing is unavailable. Explain the available pharmacy-approved options, any amount due, and that later reimbursement for a self-pay purchase depends on the patient’s plan. Do not promise reimbursement unless the plan or payer confirms it.
How can pharmacies confirm all held claims are processed after recovery?
Reconcile the downtime log and dispensing records against the claims processor’s transaction history. Verify the final response for each held claim, resolve rejected, duplicate, or unmatched transactions, and document the outcome. Follow payer or PBM instructions for reprocessing, and escalate claims with uncertain status rather than resubmitting them blindly.
Table of Contents
- How should pharmacy staff report and contain a suspected cyberattack?
- How do you activate pharmacy downtime procedures?
- How should prescriptions be prioritized to protect patient care?
- What approved options can pharmacies use when claims processing is unavailable?
- How should staff communicate outage impacts and payment options to patients?
- How should pharmacies reconcile and reprocess claims after service is restored?
- FAQs
Ready to simplify HIPAA compliance?
Join thousands of organizations that trust Accountable to manage their compliance needs.
Get Started Free Today