FDA’s 2015 Symbiq notice strongly encouraged replacing a discontinued pump, discouraging third-party purchases

On July 31, 2015, the FDA strongly encouraged facilities to move off Hospira’s Symbiq pumps, which could be accessed remotely, and strongly discouraged buying them from third parties. In our reading, the fix for a security flaw became a purchasing and lifecycle decision.

Looking Back revisits past weeks one at a time, up to the most recent, and asks what it meant for the banks, health systems and public agencies we serve. The series was written in 2026, with the benefit of hindsight, and each article says which week it looks back on.

Two-minute summaryThe dek and the first sentence of each section, quoted from the article

On July 31, 2015, the FDA strongly encouraged facilities to move off Hospira’s Symbiq pumps, which could be accessed remotely, and strongly discouraged buying them from third parties. In our reading, the fix for a security flaw became a purchasing and lifecycle decision.

  1. The week The communication described the device.
  2. The installed base: a retired product still in clinical use The Symbiq was already on its way out.
  3. The interim: what keeping the pump in service would cost That caution named the trade-off between two patient safety risks.
  4. The market: where the pump could still be bought The notice’s line on purchasing stood out.
  5. The replacement: moving to another system The FDA’s remedy was transition. [1] Hospira was working with customers to move them to alternative systems. [1] As we read it, a replacement program for infusion pumps touches budgets, drug library builds, nurse training, integration testing and the logistics of swapping devices on live units.
  6. How the notice reached different organizations A system with central clinical engineering and a single pump standard could replace by plan.
  7. Objections, and what the record shows The FDA said it was not aware of patient adverse events or unauthorized access. [1] It still recommended discontinuing use. [1] In our reading, the FDA treated a confirmed remote path to dosing as enough.
  8. Checks a supply chain or clinical engineering leader could run These checks are our suggestions, not FDA requirements.
  9. With hindsight Congress later gave the FDA explicit cybersecurity authority over new devices.

The week

On July 31, 2015, the Food and Drug Administration issued a safety communication titled “Cybersecurity Vulnerabilities of Hospira Symbiq Infusion System.” [1] Its audience was health care facilities using the system, and it covered version 3.13 and prior versions. [1]

The communication described the device. The Symbiq is a computerized pump for continuous delivery of general infusion therapy. [1] The FDA said it is primarily used in hospitals and other acute and non-acute facilities, such as nursing homes and outpatient care centers. [1] It said the pump can communicate with a hospital information system over a wired or wireless connection. [1]

The FDA stated its purpose plainly. It said: “We strongly encourage that health care facilities transition to alternative infusion systems, and discontinue use of these pumps.” [1]

It explained the problem. The FDA said Hospira and an independent researcher confirmed that the Symbiq could be accessed remotely through a hospital’s network. [1] It said this could allow an unauthorized user to control the device and change the dosage the pump delivers, which could lead to over- or under-infusion. [1]

The FDA said that it and Hospira were not aware of any patient adverse events or unauthorized access of a Symbiq in a health care setting. [1] It said the FDA, the Department of Homeland Security’s Industrial Control Systems Cyber Emergency Response Team and Hospira were all aware of the vulnerabilities. [1]

The communication described the product’s commercial status. It said Hospira had discontinued manufacture and distribution of the Symbiq, due to unrelated issues, and was working with customers to transition to alternative systems. [1] It said that, due to recent cybersecurity concerns, the FDA strongly encourages facilities to begin transitioning “as soon as possible.” [1]

It gave interim steps. Facilities could disconnect the pump from the network, ensure unused ports were closed, and monitor and log traffic to specific ports. [1] They could contact Hospira’s technical support to change the default password used to access one port, or to close it. [1]

The FDA attached a caution to the first step. It said disconnecting the pump would have operational impacts, because drug libraries would then need to be updated manually. [1] It said manual updates to each pump “can be labor intensive and prone to entry error.” [1]

The communication then addressed the market. It said the pumps were not available for purchase through Hospira, but that the FDA was aware the Symbiq was potentially available from third parties not associated with Hospira. [1] It said: “The FDA strongly discourages the purchase of the Symbiq Infusion System from these parties.” [1]

The FDA pointed to earlier warnings. It said ICS-CERT had communicated the Symbiq concerns in an advisory issued June 23, 2015 and updated July 21, 2015. [1] It referred facilities to its June 2013 safety communication on cybersecurity for medical devices and hospital networks. [1]

That 2013 communication had been addressed to manufacturers, hospitals, user facilities, health care IT staff, procurement staff and biomedical engineers. [2] It listed failure to provide timely patches and to address vulnerabilities in older device models among the issues the FDA had become aware of. [2]

For a hospital’s supply chain, clinical engineering and security leaders, the week’s notice turned a cybersecurity finding into a purchasing instruction. The rest of this piece is about that turn.

The FDA’s Symbiq notice of July 31, 2015 is remembered as a cybersecurity warning about an infusion pump. For a hospital’s chief supply chain officer, its director of clinical engineering or its CISO, it read as something else. It told them how to fix a security problem by changing what they owned and what they bought.

Our argument is that the notice made device security a procurement and lifecycle decision. The FDA’s main recommendation was a transition to alternative infusion systems, not a patch. [1] The maker had already discontinued the product. [1] The interim mitigations carried operational costs the FDA spelled out. [1] And the FDA strongly discouraged buying the pump from third parties. [1] In our reading, each of those points sits with the people who buy, track and retire equipment, as much as with security teams.

That framing places the work across supply chain, clinical engineering, pharmacy and security. It also explains why the FDA’s later work on device cybersecurity, and its later safety communications, matter to hospital buyers. [5] [6]

We take the notice in four parts:

  1. The installed base: a retired product still in clinical use.
  2. The interim: what keeping the pump in service would cost.
  3. The market: where the pump could still be bought, and why the FDA objected.
  4. The replacement: what moving to another system asked of a hospital.

The parts do not overlap. The first is about what a hospital already owned, the second about running it safely in the meantime, the third about acquiring more and the fourth about leaving it. After them we look at how the notice reached different organizations, take the objections in order and end with checks a supply chain or clinical engineering leader could run.

The installed base: a retired product still in clinical use

Retirement announced, devices still running

The Symbiq was already on its way out. The ICS-CERT advisory said Hospira had announced in 2013 that the system would be retired on May 31, 2015, and fully removed from the market by December 2015. [3] The FDA said Hospira had discontinued manufacture and distribution due to unrelated issues. [1]

Yet the FDA’s audience was “health care facilities using the Hospira Symbiq Infusion System.” [1] The notice came after the May 31, 2015 retirement date the advisory gave, and it was addressed to facilities still using the pumps. [1] [3] As we read it, that gap is the heart of the case. A manufacturer can retire a product on a date. A hospital retires it one device at a time, when budget, training and clinical schedules allow.

What the vulnerability meant for the owner

The ICS-CERT advisory, originally posted to the US-CERT secure portal library on June 23, 2015 and later released on the ICS-CERT website, described a flaw that could be exploited remotely. [3] It said exploitation, together with previously reported vulnerabilities, could let an attacker remotely control the device’s operation, potentially affecting prescribed therapy and patient safety. [3]

It said an attacker with medium skill could exploit it, and that no known public exploits specifically targeted it. [3] It said Hospira had verified the flaw existed only in the Symbiq. [3] The FDA framed the clinical risk as possible over- or under-infusion of critical therapies. [1]

For the owner, the question was not whether the flaw was severe. The FDA had answered that. The question was how many of these pumps the hospital had, where they were and what connected to them.

How the advisory scored the flaw

The June 23 advisory classified the flaw as an exposed dangerous method or function. [3] It said that, with remote access and elevated privileges, the pump could be remotely directed to perform unanticipated operations. [3] It assigned the flaw CVE-2015-3965 and a CVSS version 2 base score of 7.1. [3]

The advisory added a caution that applies to any score. It said impact to individual organizations “depends on many factors that are unique to each organization.” [3] It asked organizations to evaluate impact based on their operational environment and clinical use. [3] In our reading, that put the risk rating partly in the hospital’s hands. A pump on an isolated wired segment and one on a flat wireless network did not carry the same exposure, even with the same score.

Disclosure through a coordinated channel

The vulnerabilities reached hospitals through a coordinated process. The earlier advisory said ICS-CERT was reporting to notify healthcare providers of a coordinated disclosure of vulnerability information, and to provide additional defensive measures. [4] It said Hospira had identified vulnerabilities in the Symbiq, and outside researchers had identified others. [4] The FDA said Hospira and an independent researcher had confirmed the remote access path. [1]

The FDA itself said ICS-CERT had issued its Symbiq advisory on June 23, 2015. [1] In our reading, that sequence put warnings in ICS-CERT channels before the FDA’s notice. A facility watching those channels could have begun its inventory and interim steps before the FDA spoke. One that relied on the FDA alone started later.

Knowing what is installed

The notice assumed facilities could identify their Symbiq pumps and their versions. [1] The affected scope was version 3.13 and prior. [1] [3] That required an inventory with model and software version, by location.

The 2013 communication had already asked facilities to restrict unauthorized access to networked devices and to protect network components through periodic evaluation. [2] It had flagged older device models and missing patches as a known problem. [2] As we read it, a hospital that had acted on 2013 would have had a head start in 2015: a list of networked devices, with owners.

Versions as a scope boundary

The FDA’s scope was version 3.13 and prior. [1] The earlier advisory added a second boundary for a different flaw. It said Symbiq versions before 3.0 ran a vulnerable version of an embedded web server. [4]

In our reading, those boundaries made software version a field the inventory had to carry. A record that said “Symbiq pump, 4th floor” would not tell a hospital which advisory applied. A record with the version would. The 2013 communication asked anyone reporting a cybersecurity issue to state the specific model numbers and firmware versions affected. [2] The same detail served the owner.

The device and the network it relied on

The FDA said the pump could communicate with a hospital information system over wired or wireless connections. [1] The earlier advisory ICSA-15-161-01, covering the Plum A+ and Symbiq, addressed disconnection too. [4] It said drug libraries would then be updated manually, and data normally transmitted from the device to MedNet would not be available. [4]

So the pump was one end of a system. The other end was a server and a network path. In our reading, retiring the pump also meant retiring or reconfiguring that path, and the integrations that depended on it.

Where the pumps were used

The FDA said the Symbiq was primarily used in hospitals, or in other acute and non-acute settings such as nursing homes and outpatient care centers. [1] The ICS-CERT advisory said it was used only in the United States and Canada. [3]

As we read it, the range of settings mattered for reach. A health system’s hospital might have clinical engineering and a security team. Its affiliated outpatient center or a nursing home it contracts with might have neither. A notice addressed to “health care facilities” reached all of them, and not all would have the staff to act on its technical steps.

Who owned the decision

The notice addressed “health care facilities” and asked them to transition. [1] It did not say who inside a facility should decide. In our reading, the decision crossed at least four functions. Clinical engineering knew the fleet. Pharmacy owned drug libraries. Nursing used the pumps. Supply chain bought the replacements. Security understood the network exposure.

A hospital without a forum where those functions met would struggle to act on a notice like this one. The FDA strongly encouraged facilities to begin transitioning as soon as possible. [1] That phrase set an expectation without setting a date, and left the pace to each facility’s governance.

The interim: what keeping the pump in service would cost

Disconnecting from the network

The first interim step the FDA suggested was to disconnect the pump from the network. [1] It warned that this would have operational impacts. [1] Drug libraries would need manual updates to each pump, which the FDA called labor intensive and prone to entry error. [1]

That caution named the trade-off between two patient safety risks. A networked pump could be reached by an attacker. A disconnected pump depended on staff loading the right library by hand.

As we read it, the decision to disconnect belonged with pharmacy and nursing leaders as much as with security. It changed how medication safety software reached the bedside.

Closing ports and changing passwords

The other steps the FDA suggested were technical. Facilities could ensure unused ports were closed, including those for file transfer and telnet. [1] They could monitor and log traffic attempting to reach the pump on three named ports. [1] They could contact Hospira’s technical support to change the default password for one port, or close it. [1]

Advisory ICSA-15-161-01 had already reported that, according to Hospira, the remaining Symbiq systems had file transfer and telnet ports closed during a recent service visit. [4] The June 23 advisory said Hospira was working directly with Symbiq customers to update the pump configuration to close access ports. [3]

Those statements show that the interim depended on the manufacturer’s service channel. A hospital could not change the default password on its own. It needed Hospira’s support, under whatever service terms it had.

Default credentials as a supply issue

One interim step concerned a default password used to access a port on the pump. [1] The 2013 communication had listed, among known problems, hard-coded passwords and documented service accounts in service manuals. [2] It had recommended that manufacturers avoid hard-coded passwords and limit public access to passwords used for technical device access. [2]

In our reading, a default credential is a property of the product as shipped. The buyer inherits it on delivery. That makes credential handling a question for the purchase evaluation, before a device is ever connected.

Network segmentation

The ICS-CERT advisory recommended segmentation, firewalled zones and isolation of medical devices from the Internet and untrusted systems. [3] It encouraged a risk assessment based on each facility’s clinical use of the pump. [3]

Those steps take network engineering time and change control. As we read it, they also needed a clear owner. A pump on a clinical network segment managed by IT, maintained by clinical engineering and used by nursing could fall between budgets.

Risk assessment by clinical use

The ICS-CERT advisory asked asset owners to perform a risk assessment by examining their specific clinical use of the pump in their environment. [3] It reminded organizations to perform impact analysis and risk assessment before deploying defensive measures. [3]

In our reading, that instruction cut both ways. A defensive step that broke a clinical workflow could create a new risk. A pump used for high-alert infusions in critical care and one used for routine fluids on a general ward might justify different interim choices, and different replacement priority.

A hypothetical trade-off

Consider, as an illustration, a hospital with a few dozen Symbiq pumps that updates its drug library monthly. Disconnecting them means a staff member visits each pump each month to load the new library, and confirms it loaded correctly.

If the library changes because a concentration or a dose limit has changed, any pump missed or loaded wrongly runs on old limits. That is the entry-error risk the FDA described. [1] Against it sits the network risk the FDA also described: a remote user changing a dosage. [1] The hospital’s choice is between two safety risks with different owners. Either way, the cost recurs until the pumps are replaced.

The cost no one priced

The notice did not estimate the cost of interim measures, and neither did the advisories. It named the burden qualitatively: labor intensive manual updates, operational impacts and risk of entry error. [1] [3]

That burden recurred for as long as the pumps stayed in service. Each library update meant a trip to each disconnected pump. The longer replacement took, the more those visits cost, and the more chances there were for an entry error.

Reporting what the hospital sees

The notice asked for problem reports. It encouraged voluntary reports through MedWatch and told personnel at facilities subject to user facility reporting requirements to follow their own procedures. [1] It noted that manufacturers must comply with the Medical Device Reporting regulations. [1]

The 2013 communication had listed what the FDA wanted in a cybersecurity report. [2] It asked for a point of contact, when and how the issue was found, the affected model numbers and firmware versions and the number of devices. [2] It also asked whether function was compromised and how, and what abnormal behavior was observed. [2] In our reading, a hospital could answer those questions only if its inventory and logs were in order before anything went wrong.

Monitoring as evidence

The FDA suggested that facilities monitor and log all traffic attempting to reach the pump on specific ports. [1] As we read it, the logs served two purposes. They could reveal an attempt. They could also show, after the fact, that the facility had acted on the notice while it moved to replacement.

The market: where the pump could still be bought

Third-party availability

The notice’s line on purchasing stood out. The FDA said the Symbiq was not available through Hospira, but was potentially available from third parties not associated with Hospira. [1] It strongly discouraged buying it from them. [1]

In our reading, that sentence recognized that devices can keep circulating after a manufacturer exits. A facility short of pumps, or looking to standardize on a fleet it already knew, could be tempted to buy more of the same.

Why that purchase mattered

A pump bought from a third party would carry the same vulnerabilities, without the manufacturer’s ongoing relationship. [1] [3] The interim steps depended on Hospira’s technical support. [1] In our reading, a buyer outside the manufacturer’s channel might not get that support on the same terms, and might not know what configuration the device arrived in.

Procurement as a control point

The 2013 communication had named procurement staff in its audience. [2] The 2015 notice gave procurement a specific recommendation: the FDA strongly discouraged buying this device from third parties. [1]

On our reading, that turned the purchasing system into a security control. A requisition for a discontinued device model, or a purchase from a seller outside the manufacturer’s channel, could be flagged before the order went out. That requires the item master to carry device model, manufacturer status and any FDA notice.

Standardization and its downside

Where a hospital standardizes on one pump model, it does so for reasons such as training and drug library management. The Symbiq notice showed the downside. When one model has a problem, the whole fleet needs to move.

As we read it, that argues for planning exit costs at the time of purchase. A buyer who negotiates a fleet should also ask what support the maker will provide after it retires the model, and on what notice.

The item master and the requisition

In our reading, the practical place to apply the FDA’s purchasing advice was the hospital’s item master: the catalog of what can be ordered. A device model under an FDA notice can carry a status that blocks or routes its requisitions. A supplier outside the manufacturer’s authorized channel can carry a status that triggers review.

That approach needs data supply chain teams may not keep by default. It needs the device’s manufacturer status, any FDA communication and a link from the purchasing record to the clinical engineering inventory. The Symbiq notice shows why each field matters. [1]

Price against support

A third-party unit may cost less than a new system. In our reading, the comparison is incomplete without the cost of support. The FDA’s interim steps assumed access to the manufacturer’s technical support for password and port changes. [1] A unit bought outside that relationship could arrive with default settings and no clear route to change them.

The total cost of a discounted unit therefore includes the interim measures it would need, the staff time to apply them and the replacement it would eventually require anyway. On the FDA’s advice, that replacement was the destination. [1]

Recording the decision not to buy

A purchasing control is easiest to defend when its reasons are written down. As we read it, a supply chain team that declined a third-party Symbiq offer, or blocked a requisition, should record the FDA notice it relied on. The record shows the control worked, and it helps the next buyer who meets the same offer.

Rentals, loaners and transfers

Pumps reach units by routes other than purchase. A hospital may rent devices during a surge, borrow them from an affiliate, or move them between sites. In our reading, each route is a way for a discouraged model to re-enter service without a purchase order.

The FDA’s advice was framed around purchases from third parties. [1] A hospital applying it in full would extend the same check to rentals and transfers. The control is the same: no device of a flagged model enters clinical use without review.

Contracts with the manufacturer

The notice pointed facilities to Hospira’s technical support for password changes and port closures. [1] The advisory said Hospira was working directly with customers on configuration. [3] In our reading, those services were the mitigation. A service contract that lapsed when the product was retired would leave the facility unable to apply them.

The replacement: moving to another system

Transition as the remedy

The FDA’s remedy was transition. [1] Hospira was working with customers to move them to alternative systems. [1] As we read it, a replacement program for infusion pumps touches budgets, drug library builds, nurse training, integration testing and the logistics of swapping devices on live units.

The replacement needed diligence too

The alternatives were not automatically safer. ICS-CERT advisory ICSA-15-161-01 covered vulnerabilities in Hospira’s Plum A+ pumps as well as the Symbiq. [4] It said the researcher asserted a buffer overflow that Hospira had not validated. [4] It reported that the communication module gave unauthenticated users root privileges on one port by default. [4]

The advisory said Hospira was releasing the Plum 360, and that Hospira asserted it used a different architecture and was not vulnerable to the reported flaws. [4] In our reading, a buyer choosing a replacement in 2015 needed to test that assertion as part of evaluation. A move from one vulnerable pump to another would have spent the budget without solving the problem.

Questions for the replacement purchase

The 2013 communication described what the FDA expected of manufacturers. It recommended limiting access to trusted users, avoiding hard-coded passwords, deploying validated security patches and restricting updates to authenticated code. [2] The earlier ICS-CERT advisory listed hard-coded accounts and unauthorized configuration changes from unauthenticated devices among the Plum A+ issues. [4]

In our reading, those lists gave a buyer its evaluation criteria. A request for proposals could ask how the device authenticates users and updates, how it receives patches and how long the maker will support it.

Budget timing

The FDA strongly encouraged facilities to begin transitioning “as soon as possible.” [1] Where a hospital sets its capital plan ahead of time, a notice like this one, in our reading, forced a choice between an unplanned capital request and a longer interim period with its recurring costs. The FDA’s wording gave clinical and security leaders a basis for the request, but not a date.

Training and clinical validation

A new pump brings new screens, alarms and procedures for nurses. A transition plan, as we read it, needs training time on every unit, a drug library built and checked for the new system, and a period where staff can raise problems. Those steps take as long as they take, whatever the urgency of the notice.

Terms to put in the next contract

The 2013 communication said manufacturers should provide methods for retention and recovery after an incident, and consider incident response plans for degraded operation. [2] It recommended timely deployment of validated security patches. [2] It said: “The FDA typically does not need to review or approve medical device software changes made solely to strengthen cybersecurity.” [2]

As we read it, those points translate into contract terms a buyer could seek. They include a commitment to deliver security patches for a stated period, a process for notifying the customer of vulnerabilities, support for configuration changes after retirement and notice before a product is discontinued.

Sequencing the swap

A fleet cannot be replaced in a day. In our reading, the order of replacement should follow exposure and clinical risk. Pumps on wireless networks, or used for high-alert medications, would go first. Disconnected pumps on low-risk units could wait, with their interim measures in place.

That sequencing needs the inventory again: model, version, network connection and clinical use, by unit. [1] [3] Without it, a hospital replaces by convenience, which may leave the riskiest devices for last.

Integration and data

A new pump fleet would connect to the same hospital information systems. [1] In our reading, the transition was also an interface project. Drug libraries had to be rebuilt, server software replaced and network segments reconfigured. Each step needed testing before clinical use.

Retiring the old devices

The notice did not address disposal. As we read it, a hospital retiring Symbiq pumps needed to decide what to do with them. A device sold or donated onward could become the third-party supply the FDA discouraged others from buying. [1] The earlier ICS-CERT advisory listed wireless keys stored in plain text on the device among the vulnerabilities it reported. [4] A device leaving the hospital could carry network credentials with it.

How the notice reached different organizations

Large health systems

A system with central clinical engineering and a single pump standard could replace by plan. In our reading, its challenge was coordination across hospitals, each with its own drug library and unit schedules.

Community hospitals

A smaller hospital with a small fleet might replace faster, but with less negotiating power and fewer spare devices. In our reading, it was also a buyer that might consider a third-party seller for a quick fix, which is the purchase the FDA discouraged. [1]

Nursing homes and outpatient centers

The FDA named nursing homes and outpatient care centers among the settings where the pump was used. [1] As we read it, those facilities may lack clinical engineering staff and network segmentation. For them, the interim measures were hardest and replacement the clearest path.

Pharmacy and medication safety teams

The notice’s operational caution was about drug libraries. [1] In our reading, pharmacy informatics owned the interim burden. It built the libraries, scheduled their release and would carry the risk of manual loading errors. Its leaders belonged in the replacement decision as well as its execution.

IT and security teams

The ICS-CERT advisories asked for segmentation, firewalled zones, traffic monitoring and isolation from the Internet. [3] [4] In our reading, those tasks fell to network and security teams who may not have known the pumps were on their networks. The notice made the case for a shared inventory between IT and clinical engineering.

Boards and finance leaders

An unplanned fleet replacement is a capital decision. As we read it, the FDA notice gave management a documented basis to take to finance committees and boards. It named the risk, the recommended remedy and the cost of delay in operational terms. [1] A board asked to approve the spend could read the FDA’s own words on why it was needed.

Group buyers and distributors

Organizations that buy on behalf of several facilities can shape what reaches the bedside. In our reading, an FDA notice that discourages a purchase is information a group buyer should flag across its catalog, so that no member facility orders the device by mistake.

Refurbishers and sellers

The notice addressed third-party sellers only indirectly, by discouraging purchases from them. [1] In our reading, a reputable seller that kept offering a device the FDA told facilities to stop using would carry obvious risk. The notice did not prohibit sales.

Manufacturers’ service organizations

The notice routed password changes and port closures through Hospira’s technical support. [1] The advisory said Hospira was working directly with customers to close access ports. [3] As we read it, the maker’s service organization became part of each customer’s security operation for the life of the device. Its capacity to visit every site, and its records of what it changed, mattered to every hospital that relied on it.

Manufacturers

The 2013 communication said manufacturers are responsible for remaining vigilant about cybersecurity risks and putting mitigations in place. [2] The Symbiq case showed what happens when a product reaches end of life with known flaws. The later FDA framework speaks to that directly. [5]

Objections, and what the record shows

“There were no reported harms”

The FDA said it was not aware of patient adverse events or unauthorized access. [1] It still recommended discontinuing use. [1] In our reading, the FDA treated a confirmed remote path to dosing as enough. Waiting for harm in a dosing device would mean waiting for an injury.

“The product was already being retired”

It was. [3] The notice addressed the gap between retirement and removal. [1] Facilities still using pumps after the maker’s retirement date carried the risk until they replaced them.

“Disconnecting is enough”

Disconnecting reduced network exposure but, by the FDA’s account, created manual work and entry-error risk. [1] The FDA still recommended transition. [1] In our reading, disconnection was a bridge, not a destination.

“The FDA cannot tell hospitals what to buy”

The notice did not order anything. Its language was advice: the FDA “strongly encourages” a transition and “strongly discourages” third-party purchases. [1] As we read it, the weight came from the source. A facility that bought a device the FDA had discouraged, and then had a problem, would struggle to explain the choice.

“Replacement costs too much”

Replacement has a price. So do interim measures, by the FDA’s own description. [1] In our reading, the comparison is between a one-time cost and a recurring one that carries patient safety risk. The notice did not settle that comparison for any hospital, but it made both sides visible.

“Other pumps had flaws too”

They did. The earlier advisory reported vulnerabilities in the Plum A+ pumps, some asserted by a researcher and not validated by Hospira. [4] The FDA’s July notice addressed the Symbiq. [1] The notice paired its recommendation with the Symbiq’s discontinued status and its confirmed remote access path. [1] In our reading, a pump still supported by its maker could be mitigated and updated; one being retired could only be replaced.

“Security is IT’s problem”

The notice’s steps ran through clinical engineering, pharmacy, manufacturer support and purchasing. [1] The 2013 communication named procurement staff and biomedical engineers in its audience. [2] The record does not support treating device security as the security team’s alone.

Checks a supply chain or clinical engineering leader could run

These checks are our suggestions, not FDA requirements. Facilities should confirm regulatory and clinical questions with their own counsel, clinical leadership and device manufacturers.

  • Device inventory: keep an inventory of networked medical devices with model, software version, location and owner.
  • Lifecycle dates: record each model’s manufacturer support and retirement dates, and plan replacement before them.
  • Notice watch: assign someone to track FDA safety communications and CISA advisories for the devices you own.
  • Purchasing flags: block or flag orders for device models under an FDA notice, and purchases from sellers outside the manufacturer’s channel.
  • Interim cost: estimate the staff time and safety risk of interim measures, such as manual library updates, when deciding how fast to replace.
  • Service terms: confirm manufacturer support for configuration and security changes continues after a product is retired.
  • Replacement diligence: ask any replacement vendor how its device authenticates users and updates, and how long it will be supported.
  • Disposal: wipe credentials and data from retired devices, and decide whether they may be resold.
  • Non-purchase routes: apply the same model checks to rentals, loaners and transfers between sites.
  • Advisory watch: include CISA advisories in the watch list, since they may precede an FDA communication.

The 2015 notice fixed a security problem by asking hospitals to change what they owned and avoid what they might buy. [1] The checks above follow that line: know the fleet, price the interim and control the purchase.

With hindsight

Congress later gave the FDA explicit cybersecurity authority over new devices. The FDA’s current guidance page says Congress added section 524B to the Federal Food, Drug, and Cosmetic Act in 2022, and that the authority took effect on March 29, 2023. [5]

Under section 524B, the sponsor of a premarket submission for a “cyber device” must include information to show reasonable assurance that the device and related systems are cybersecure. [5] The FDA lists three kinds of information this includes: a plan to address postmarket vulnerabilities, including coordinated disclosure; processes to provide reasonable assurance of cybersecurity, including postmarket updates and patches; and a software bill of materials. [5]

The FDA says the requirements do not apply to submissions made before March 29, 2023. [5] A previously authorized device becomes subject to them when a change requires a new premarket submission. [5] As we read it, that leaves an installed base of older devices, like the Symbiq in 2015, outside the statute’s premarket requirements.

The FDA’s page also answers a question the Symbiq raised. One question asks whether manufacturers are responsible for cybersecurity of devices they have deemed end-of-life or end-of-support. [5] The FDA’s answer says manufacturers must maintain processes to evaluate risks and take appropriate action for affected products that may present a risk to health. [5]

It says health care delivery organizations may need to patch or update devices or infrastructure, and recommends working closely with manufacturers on such changes. [5] It lists a final guidance on cybersecurity in medical devices, dated February 3, 2026, which supersedes a version issued June 27, 2025. [5] As checked on November 16, 2026, the page says its content is current as of November 10, 2026. [5]

The FDA kept issuing device-specific safety communications. Its cybersecurity page lists them and says facilities can reduce the risk of unauthorized access by following their recommendations. [7] The most recent entry it lists is dated January 30, 2025. [7]

That communication concerned Contec CMS8000 patient monitors and Epsimed MN-120 monitors, which it described as relabeled Contec units. [6] It reported a backdoor in the software and the transmission of patient data outside the care setting once connected to the internet. [6] For monitors relying on remote monitoring, it told facility staff to unplug the device and stop using it. [6]

It also addressed the market. The FDA said it had authorized the monitors only for wired connections, but was aware some were available with wireless capabilities without FDA authorization. [6] It told readers to use the unique device identifier to identify affected devices. [6] A July 2, 2025 update said a software patch removed networking functions entirely. [6]

What held up from 2015 is the pattern. When a device cannot be secured in place, the FDA has told facilities to stop using it, and has flagged units available from third parties or in configurations it had not authorized. [1] [6] What changed is the premarket regime for new devices. [5]

In our view, the lasting point for hospital buyers is that device security is decided at purchase and at retirement. The FDA can require more of new devices; the installed base remains the buyer’s to manage.

Spotted an error? Tell us and we will check it and correct the article where needed.

  • FDA
  • medical devices
  • infusion pumps
  • procurement
  • device lifecycle
  • ICS-CERT