FDA’s 2016 device servicing review led to a line drawn at the change made, not at who made it
On July 18, 2016, the Food and Drug Administration announced a workshop on who services medical devices and whether they should be regulated. By 2024 the agency’s answer turned on the activity: in our reading, a hospital’s own engineers should classify each change, software included.
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 18, 2016, the Food and Drug Administration announced a workshop on who services medical devices and whether they should be regulated. By 2024 the agency’s answer turned on the activity: in our reading, a hospital’s own engineers should classify each change, software included.
- The week The notice named three topics.
- The definitions: six words, one line In our reading, of the six terms, only one carried a clear regulatory consequence.
- The servicers: who did the work and under what rules That left an asymmetry.
- The software line: where the hard cases are Software appeared early.
- The record: what to document and what to ask for The 2024 guidance’s sixth principle is about records.
- How the outcome reached different organizations A system with its own biomedical engineers performs servicing daily.
- Objections, in order A hospital’s engineers do not think of themselves as manufacturers.
- Checks a clinical engineering or IT leader could run Add a field to service work orders: servicing, or possible remanufacturing requiring review.
- With hindsight The workshop took place.
The week
On Monday, July 18, 2016, the Federal Register published a notice from the Food and Drug Administration announcing a public workshop. [1] Its title named six activities: refurbishing, reconditioning, rebuilding, remarketing, remanufacturing and servicing of medical devices performed by third-party entities and original equipment manufacturers. [1]
The workshop was set for October 27 and 28, 2016, at FDA’s White Oak campus in Silver Spring, Maryland. [1] The notice said it would also be webcast. [1] Registration closed on September 23, 2016, and the agency said it would select and notify presenters by September 30, 2016. [1]
The notice named three topics. They were the current regulatory environment for these activities, the definitions the agency had proposed earlier that year, and whether the activities should appropriately be regulated by the agency or by a non-governmental organization. [1] The sessions would establish working definitions, discuss benefits, challenges and failure modes, identify best practices and decide whether specific procedures were needed for each activity. [1]
The July notice built on an earlier one. On March 4, 2016, the agency had opened a docket and requested comments on entities that refurbish, recondition, rebuild, remarket, remanufacture, service and repair devices. [2] [1] The July notice said the agency took that step in part because stakeholders had expressed concerns about the quality, safety and continued effectiveness of devices subject to these activities. [1]
The March notice described those concerns. Stakeholders had said some third parties may use unqualified personnel and may not adequately document the work. [2] The agency listed possible public health issues, including ineffective recalls, disabled device safety features and improper or unexpected device operation. [2] It said manufacturers had asked for clarity on their responsibilities when a third party had altered their devices. [2]
The March notice also explained the history. It said the agency had for 20 years sought to clarify expectations under its quality system rules for entities servicing and remanufacturing devices. [2] It said that in a December 4, 1998 Federal Register document, refurbishers and servicers were excluded from the requirement to comply with the 1997 Quality System Regulation. [2]
The agency proposed six definitions in March and invited edits. [2] Service meant maintenance or repair of a finished device after distribution to return it to the safety and performance specifications set by the manufacturer, without changing its intended use. [2] Remanufacture meant any act on a finished device that significantly changes its performance, safety specifications or intended use. [2]
The other proposed terms sat between those two. Recondition, repair and refurbish described restoring a device to original or comparable specifications. [2] The proposed refurbish definition included installing certain software or hardware updates that do not change the device’s intended use. [2] Remarket described transferring a previously owned device by sale, donation, gift or lease. [2]
The March notice asked seven questions. They covered who the stakeholders are, what evidence exists of safety or performance problems, what risks and failure modes these activities introduce, and whether risks differ depending on who performs the work. [2] The agency noted that these activities are performed by manufacturers and by third parties, including hospitals. [2] It said the docket was not intended to address reprocessing of single-use or reusable devices. [2]
Interest was higher than the agency expected. On April 25, 2016, it extended the comment period to June 3, 2016, citing the unanticipated high level of interest. [3] The July notice said the agency was reviewing the comments and would use them to shape working questions for the workshop’s group discussions. [1]
The 2016 servicing review began as a dispute about who should be allowed to fix medical devices. Stakeholders had raised concerns about some third parties, and manufacturers had asked what they were responsible for when others altered their devices; third parties, including hospitals, did much of the work. [2] The July workshop notice asked directly whether these activities should be regulated by FDA or by a non-governmental body. [1]
Our argument is that the answer FDA reached did not sort people. It sorted changes. By 2024, FDA’s guidance said the designations of servicer and remanufacturer are not mutually exclusive and that an entity may meet several definitions based on the activities it performs. [5] In our reading, that put the classification decision inside every service event, including those a health system’s own engineers carry out.
We take the issue in four parts:
- The definitions: how FDA’s 2016 terms sorted activities, and which line mattered.
- The servicers: who did the work in 2016, under what rules, and what FDA concluded about them.
- The software line: why software and cybersecurity changes became the hardest cases.
- The record: what an entity would need to document, and what it would need from manufacturers.
The parts do not overlap. The first is about categories, the second about the people and organizations doing the work, the third about one class of change, and the fourth about evidence. After them we look at how the outcome reached different organizations, take the objections in order, and end with checks a clinical engineering or IT leader could run.
The definitions: six words, one line
What the six terms did
FDA’s March 2016 terms covered a range. [2] At one end, service and repair returned a device to its original specifications. [2] In the middle, recondition and refurbish restored it to original or comparable condition, with refurbish including certain software and hardware updates that do not change intended use. [2] Remarket described a transfer, not a technical act. [2]
At the far end sat remanufacture: any act that significantly changes a finished device’s performance, safety specifications or intended use. [2] That definition mirrored the regulation’s definition of a remanufacturer. [7]
Why only one line mattered legally
In our reading, of the six terms, only one carried a clear regulatory consequence. A remanufacturer is defined in the quality rules. [7] The current text of 21 CFR 820.3 says a manufacturer includes those who perform remanufacturing. [7] The 2024 guidance says remanufacturers are considered manufacturers and are regulated as such. [5]
The other terms described flavors of maintenance. FDA’s 2024 guidance later said that, for purposes other than the report Congress required, FDA does not consider remanufacturing to be a type of servicing. [5] In our reading, the six-word vocabulary of 2016 resolved into a two-way question: does this activity significantly change the device or not.
Significant change as the test
The word significant does the work. The 2024 guidance says FDA considers change to include activities that enhance the device. [5] It says activities not intended to change specifications should still be evaluated to see whether they do. [5] It says multiple changes, considered cumulatively, may significantly change the device. [5]
Those three points close common escape routes. An upgrade is a change even if it improves the device. Intent does not settle the question. A series of small modifications can add up.
The hardware questions
For changes to hardware, the 2024 guidance set out a flowchart. [5] Its questions ask whether the activity adds, removes or changes a component, part or material that directly or indirectly contacts body tissue. [5] They ask whether it adds or removes a component or changes the dimensional or performance specifications of one. [5] And they ask whether there is a new or modified risk, or a change in performance or safety specifications. [5]
Each question, if answered yes, leads to the same follow-up: is there a significant change to device performance or safety specifications. [5] In our reading, the flowchart turns a judgment into a sequence of recorded answers, which is what makes it useful for a service department.
Remarketing and used equipment
FDA’s 2016 term remarket covered transferring a previously owned device by sale, donation, gift or lease. [2] For health systems, that is the resale of retired equipment and the purchase of refurbished equipment. The 2016 inquiry put those transactions in the same review as servicing. [1]
A hospital buying a refurbished device would want to know which activities the seller performed and how they were classified. If the refurbishment significantly changed the device, the refurbisher was a remanufacturer with manufacturer duties. [5] [7] That is our application of the definitions to a purchase decision, not a rule FDA wrote for buyers.
Reprocessing kept separate
The March 2016 notice said its docket was not intended to address reprocessing of single-use or reusable devices. [2] The 2024 guidance defined reprocessing separately, as validated processes that render a previously used or contaminated device fit for a subsequent single use on a patient. [5]
That separation matters for hospitals because reprocessing is also done on site. The 2024 guidance said it is not intended to address reprocessed single-use devices. [5] In our reading, the servicing and remanufacturing analysis covers maintenance and modification, not the reprocessing of devices between uses.
Intended use
The guidance’s first principle asks whether there is a change to intended use. [5] It says servicing exists to return a device to its original intended use, so any change to intended use should be evaluated to determine whether the activity is remanufacturing. [5]
For a hospital, intended-use changes can arise without any hardware work. Reconfiguring a device for a patient population or a setting its labeling does not cover is a use question. The guidance’s principle would bring such a change into the remanufacturing analysis if it altered the device’s intended use. That application is our reading.
Marketing submissions
The guidance’s third principle adds a separate question. Whether or not a change is remanufacturing, it should be evaluated for whether a new marketing submission, such as a 510(k), is required. [5] Changes that meet the remanufacturing definition can trigger the need for a submission, depending on the device’s classification. [5]
In our reading, that principle explains why the line matters so much. On one side sits routine maintenance. On the other sits a potential premarket obligation, with all that a manufacturer must do to meet it.
The servicers: who did the work and under what rules
The 1998 exclusion
The March 2016 notice recalled a December 4, 1998 Federal Register document. [2] That document excluded refurbishers and servicers from the requirement to comply with the 1997 Quality System Regulation. [2] It also noted that device regulations require manufacturers to establish and maintain servicing instructions and procedures. [2]
That left an asymmetry. The manufacturer had duties about how its device should be serviced. In our reading, a servicer that was not remanufacturing had no quality system duties under FDA’s rule after the 1998 exclusion. FDA’s 2016 questions were, in part, about whether that should change. [1]
Radiation-emitting devices
The March notice described one area with more specific rules. It said manufacturers of diagnostic x-ray systems must provide assembly instructions adequate to assure compliance with performance standards. [2] Assemblers must then assemble, install, adjust and test certified components according to those instructions, under 21 CFR 1020.30(d). [2]
The notice also said manufacturers of laser products must provide instructions for assembly, operation and maintenance, including maintenance schedules. [2] The July notice said the March request for comments included radiation-emitting devices subject to the electronic product radiation control provisions. [1] For an imaging department, the servicing question therefore sat on top of existing duties tied to manufacturer instructions.
Hospitals as servicers
FDA named hospitals among the third parties that perform these activities. [2] Its 2018 report described workshop panels that included manufacturers, independent service organizations, and members representing hospital end users and engineers. [4]
For a health system, that means its clinical engineering department is a servicer in FDA’s vocabulary. So is any contractor it hires to maintain imaging equipment, infusion pumps or monitors. The 2016 question of whether servicers should be regulated was, for health systems, a question about themselves.
The other regulators in the room
FDA’s report described a second layer of oversight. It said the Centers for Medicare & Medicaid Services is involved in the regulation of maintenance and repair through conditions for federal payment. [4] It cited the hospital condition that facilities, supplies and equipment be maintained to ensure an acceptable level of safety and quality. [4]
The report described CMS’s position on maintenance methods. It said CMS stated in 2011 that alternate equipment maintenance methods were not permitted and hospitals must follow manufacturers’ recommended techniques, even if they altered frequency. [4] It said CMS’s 2013 guidance clarified that a hospital may in certain circumstances adjust maintenance, inspection and testing frequency based on a risk-based assessment by qualified personnel. [4]
In our reading, that dual structure explains why the servicer debate was hard to settle at FDA alone. A hospital’s maintenance program answered to CMS conditions and to accreditors. FDA’s question was whether to add a federal device-quality layer on top.
Who decides inside a hospital
The servicing question crosses two departments. Clinical engineering maintains devices; information technology and security manage networks, accounts and patches. FDA’s 2018 report observed that many manufacturers, health care establishments and third-party servicers lack the necessary cybersecurity expertise for servicing. [4] The 2024 guidance’s software list mixes engineering and security tasks in one list. [5]
In our reading, a hospital needs one owner for the classification decision on connected devices, with input from both departments. Without that, a security patch can be applied by IT without the engineering review, or an engineering change can expose a network path IT never assessed. The guidance does not prescribe an organizational model; this is our inference from its content.
Hospitals as adverse event reporters
Hospitals also feed FDA’s evidence. The 2018 report described medical device reports submitted by mandatory reporters, which it listed as manufacturers, importers and device user facilities, and by voluntary reporters. [4] A hospital is a device user facility in that scheme.
The report explained the limits of that data. It said reports may be incomplete, inaccurate, untimely, unverified or biased, and that the incidence of an event cannot be determined from the reporting system alone. [4] In our reading, that is part of why FDA could not find sufficient evidence either way: the system was not built to measure service quality.
What FDA concluded about servicers
The 2018 report gave FDA’s answer. It said the currently available objective evidence was not sufficient to conclude whether there is a widespread public health concern related to servicing, including by third parties, that would justify additional burdensome regulation. [4] It said the objective evidence indicated that many original manufacturers and third parties provide high quality, safe and effective servicing. [4]
It reached two more conclusions. It said a majority of comments, complaints and adverse event reports alleging inadequate servicing actually pertained to remanufacturing. [4] And it said the continued availability of third parties to service and repair devices is critical to the functioning of the U.S. health care system. [4]
How many servicers
The report tried to count. It said the precise number of entities servicing devices in the United States is not known. [4] Using a commercial business database and a sample check, it estimated the number of firms performing device servicing at between 16,520 and 20,830. [4] That range is FDA’s estimate, built on industry classification codes and an extrapolated capture rate. [4]
What FDA said it would do instead
Rather than new regulation, the report listed four actions. They were to promote quality management principles, clarify the difference between servicing and remanufacturing, strengthen cybersecurity practices associated with servicing, and foster evidence development. [4] The report also suggested a public-private forum, such as a collaborative community, if there was sufficient interest. [4]
The second action became the 2024 guidance. [6] The third is the subject of our next part.
The software line: where the hard cases are
Software in the 2016 definitions
Software appeared early. FDA’s proposed definition of refurbish in March 2016 included installation of certain software and hardware updates that do not change the device’s intended use. [2] That placed some software work on the maintenance side of the line from the start.
The question was which updates. A manufacturer’s security patch, a configuration change by hospital staff and a third party’s replacement operating system are different acts. The 2016 definition did not distinguish them. [2]
The 2018 report on cybersecurity
The report devoted one of its four actions to cybersecurity. [4] It said failure to maintain cybersecurity can compromise device functionality, data availability or integrity, and expose other connected devices or networks. [4] It said this may have the potential to result in patient illness, injury or death. [4]
The report named the servicer’s specific problem. It said servicing by entities other than the manufacturer raises cybersecurity challenges related to the servicer’s need, in many cases, for privileged access to perform diagnostic, maintenance and repair functions. [4] It also said servicers may play an important role in reducing risk by ensuring the latest security patches and software updates have been installed. [4]
The report was direct about capability. It said many manufacturers, health care establishments and third-party servicers lack the cybersecurity expertise, policies and practices needed for appropriate resilience in servicing. [4] That is FDA’s statement, not ours.
The 2024 guidance’s separate track for software
The 2024 guidance treated software differently from hardware. It said its flowchart and risk approach should not be applied to software changes. [5] It said many software changes are likely remanufacturing because of their effect on software architecture, requirements, unresolved anomalies and other key characteristics. [5] It said the probability of software failure cannot be determined using traditional statistical methods. [5]
Instead, FDA listed software activities that are likely not remanufacturing because they generally do not significantly change performance or safety specifications. [5] The list includes implementing updates and upgrades authorized, approved or provided by the manufacturer; running software-based hardware diagnostics; and assessing for viruses, malware and other cybersecurity issues. [5]
The list continues. It includes reinstalling the manufacturer’s software to restore specifications, reverting to a previous configuration, installing cybersecurity updates authorized by the manufacturer, and turning connectivity features on or off consistent with intended use. [5] It also includes data backup and recovery, assessing software inventory, collecting system logs, managing user accounts and accessing diagnostic and repair information. [5]
What falls outside the list
The guidance said other activities involving software changes are likely to significantly change a device’s specifications, such that the activity is likely remanufacturing. [5] An entity that believes a particular software change does not significantly change specifications should adequately document its decision-making. [5] Any software change that significantly modifies intended use would be remanufacturing. [5]
In our reading, that creates a default. Inside the list, a hospital IT or clinical engineering team is servicing. Outside it, the team should assume it may be remanufacturing unless it can show otherwise on paper.
Why this lands on hospital security teams
The listed activities read like a security operations checklist: malware assessment, authorized patches, connectivity settings, account management, log collection, backup. [5] A hospital security team doing that work on a connected device is, in FDA’s terms, performing activities that are likely servicing. [5]
The risk is in the unlisted work. A security team that installs a third-party endpoint agent on a device workstation, applies an operating system patch the manufacturer has not authorized, or changes network services may be outside the list. The guidance does not name those examples; they are our illustrations of activities its default would reach.
The guidance’s cybersecurity item carries a qualifier. It lists installing cybersecurity updates that are authorized by the manufacturer. [5] Its footnote said the cybersecurity field rapidly evolves and pointed to FDA’s website for updates on requirements. [5] In our reading, the word authorized makes the manufacturer’s patch policy part of the hospital’s classification decision.
Authorization as a document
The first item on FDA’s software list covers activities performed on behalf of, or otherwise explicitly authorized by, the manufacturer that return or maintain the device’s specifications and intended use. [5] The second covers updates and upgrades authorized, approved or otherwise provided by the manufacturer. [5]
Both items depend on proof of authorization. A hospital that applies a patch because a manufacturer’s security bulletin approves it should keep the bulletin, the version it covers and the date. A hospital that relies on a service technician’s verbal assurance has nothing to show. In our reading, the authorization record is the evidence that keeps a software change on the servicing side.
Older devices
The software default bears hardest on devices whose manufacturers no longer issue updates. A hospital with an aging device running an outdated operating system faces a choice. It can isolate the device, accept the risk, or change the software in ways the manufacturer has not authorized.
The guidance’s list gives a hospital several tools that are likely servicing: turning connectivity features on or off consistent with intended use, managing user accounts, collecting logs and assessing for malware. [5] In our reading, network isolation and account control, which do not alter the device’s software, keep a hospital on the servicing side while it plans a replacement. Changes to the device’s own software outside the list would need the documented analysis the guidance describes. [5]
Privileged access as an architecture question
The report’s point about privileged access has an architecture consequence. [4] A servicer who needs administrator rights on a device needs a path to the device. That path, whether a vendor’s remote connection or a local account, is part of the hospital’s attack surface.
FDA’s report described recommended approaches from the security field, including limiting privileged access, requiring authentication and controls before software or firmware updates, and restricting updates to authenticated code. [4] A health system that applies those controls to its own engineers and its contractors is building the access model the report described.
The record: what to document and what to ask for
Documented decisions
The 2024 guidance’s sixth principle is about records. FDA recommends that the rationale for a determination be documented in sufficient detail, including reference to supporting verification and validation data. [5] The documentation should specify why the activities do or do not significantly change performance or safety specifications or intended use. [5]
The guidance allows reuse. If an entity previously determined an activity was not remanufacturing and performs the identical activity on the same version or model, the documentation could reference the earlier determination. [5] That makes a library of classification decisions, by device model and activity, a practical asset.
The guidance said why. Effective documentation can facilitate decision-making, help evaluate information such as adverse events, and help an entity justify its decisions in an FDA inspection or when the information is requested. [5]
Risk assessment method
The fifth principle asks entities to use a risk-based approach, such as one consistent with ISO 14971, when assessing whether an activity is remanufacturing. [5] An activity is likely remanufacturing when a risk-based assessment identifies new risks or significant modifications to known risks. [5]
For a clinical engineering department, that is a familiar method in an unfamiliar use. Departments that already apply risk-based maintenance planning, as the CMS guidance described in FDA’s report allows in some circumstances, have the vocabulary. [4] The new use is applying it to the classification of a change, not to the frequency of a check.
Parts and components
The fourth principle covers components. Entities should assess the dimensional and performance specifications of components, parts and materials. [5] Deviations from the manufacturer’s specifications may significantly change performance or safety and may require engineering analysis, verification or validation testing. [5]
The report had heard about parts. Its review of comments listed the availability and use of quality replacement parts among the issues influencing service quality. [4] A hospital buying non-original parts would need records that the parts meet the relevant specifications.
What manufacturers should provide
The record depends on information the hospital does not control. FDA’s report listed access to device-specific service information as an issue, noting that not all specifications are available in labeling or measurable with general test equipment. [4]
The 2024 guidance addressed that gap. It said unintentional remanufacturing can occur when entities lack the instructions needed to return a device to its specifications. [5] It encouraged manufacturers, as an industry best practice, to provide servicing instructions for reusable devices. [5]
It listed what labeling should include, as applicable. The list starts with key performance and safety specifications and critical technical specifications, such as dimensions and electrical characteristics. [5] It continues with recommended maintenance activities and schedule, troubleshooting and acceptance testing, and error codes and alarms. [5] It ends with servicing warnings and the version number and release date of software. [5] The guidance said its recommendations are not intended to encourage disclosure of trade secrets or confidential commercial information. [5]
Quality management principles
The report’s first action was to promote quality management principles among servicers. [4] It listed what such principles help ensure: that services meet customer needs, that risk management identifies and mitigates hazards, and that personnel are qualified and trained. [4] It added that replacement parts should meet the design requirements, that servicing should be documented, and that technical and service manuals should be accurate and available. [4]
None of these is a regulatory requirement for a servicer under the report. [4] Each is, in our reading, a sensible test for a hospital’s own department or a contractor it hires. A contractor that cannot show training records, parts provenance and service documentation would struggle to support the classification decisions the 2024 guidance asks for. [5]
Procurement as the lever
A hospital’s best moment to obtain that information is before purchase. The guidance’s list gives procurement teams a specific request, grounded in FDA’s own recommendations. [5] In our reading, a hospital that buys a device without the servicing information the guidance describes has made later classification decisions harder for itself.
How the outcome reached different organizations
A large health system with in-house clinical engineering
A system with its own biomedical engineers performs servicing daily. Under the 2024 guidance’s approach, its exposure is in the activities that go beyond restoring original specifications. [5] It would need a classification step in its work order process and a library of prior decisions by device model.
A community hospital relying on contractors
A smaller hospital that contracts servicing still owns the device and its patients’ safety. The contractor may be a third-party servicer, and the guidance’s definitions would apply to the contractor’s activities. [5] The hospital would want its contract to require the contractor to classify and document changes and to share those records.
An ambulatory network with connected devices
An ambulatory network with infusion pumps, imaging and monitoring devices across sites faces the software line directly. Its IT team may manage device workstations alongside office computers. The guidance’s software list would govern which of those activities stay on the servicing side. [5]
A public or academic medical center
A public hospital or a university medical center performs the same servicing as any other hospital and answers to the same CMS conditions described in FDA’s report. [4] It may also run research that modifies devices for study use. Such modifications would raise the guidance’s intended-use and significant-change questions. [5] Research device rules are outside this article, and institutions should take that question to counsel and their review boards.
An independent service organization
For a third-party servicer, the 2018 report’s conclusion that servicing is critical to the health system was significant. [4] The guidance’s default for software changes is the constraint. [5] A servicer offering security hardening for older devices would need to show why each step is listed, authorized or documented as not significant.
A device manufacturer
For manufacturers, the guidance offered clarity and a request. Clarity, because the line between their responsibilities and others’ was better defined. [5] A request, because FDA encouraged them to provide servicing information, including software version details. [5]
Manufacturers also carry the authorization role. Because two items on FDA’s software list turn on what the manufacturer authorizes, a manufacturer’s patch and update policy shapes what its hospital customers can do without crossing the line. [5] In our reading, clear and timely authorizations from manufacturers would reduce the number of documented exceptions hospitals have to write.
Objections, in order
1. Hospitals are not manufacturers
A hospital’s engineers do not think of themselves as manufacturers. The guidance does not say they are by default. It says an entity may meet multiple definitions based on the activities it performs. [5] A hospital performing only servicing remains a servicer. The objection applies only to the activities that cross the line.
2. The guidance is not binding
Correct. FDA guidance describes the agency’s current thinking and does not establish legally enforceable responsibilities unless it cites a statute or regulation. [5] But the definition of remanufacturer is in the regulation. [7] The guidance explains how FDA reads it.
3. The evidence did not show a problem
The 2018 report said evidence was not sufficient to conclude there is a widespread public health concern related to servicing. [4] That conclusion supported not regulating servicers more. It did not say remanufacturing was harmless; the report said complaints and reports alleging bad servicing pertained to remanufacturing. [4]
4. Security patches cannot wait for manufacturer authorization
This objection has force for hospitals facing active threats. The guidance lists manufacturer-authorized cybersecurity updates as likely not remanufacturing. [5] An unauthorized patch is not automatically remanufacturing either; the guidance asks the entity to document its reasoning if it believes the change is not significant. [5] In our reading, the guidance leaves a documented path, not a prohibition.
5. The definitions are too vague to apply
The word significant invites dispute. FDA’s response was a set of principles, a flowchart for hardware and a list for software. [5] Those tools will not resolve every case. They make it possible to show reasoning, which is what the documentation principle asks for. [5]
6. Manufacturers will withhold service information
The guidance encourages disclosure but does not require it. [5] Hospitals that need the information will have to ask for it, ideally before purchase. FDA’s list gives them a defined request. [5]
7. More rules would raise costs and reduce competition
FDA’s report summarized the position the American College of Clinical Engineering presented at the workshop. [4] The report said the college’s position was that, because of existing oversight, further regulation would be redundant, and that unnecessary further regulation would bring higher health care costs, decreased competition and reduced service choices that could delay patient care. [4] In our reading, FDA’s conclusion not to impose additional burdensome requirements was consistent with that view. [4] The cost concern remains relevant to how hospitals implement classification: a process heavy enough to slow repairs would carry its own patient risk.
Checks a clinical engineering or IT leader could run
Activity classification step
Add a field to service work orders: servicing, or possible remanufacturing requiring review. Route the second category to a named reviewer.
Software change register
Record every software or firmware change on a medical device, who made it, whether the manufacturer authorized it and which item on FDA’s software list it falls under, if any. [5]
Decision library
Keep classification decisions by device model and activity, with supporting evidence, so identical activities can reference earlier determinations. [5]
Privileged access inventory
List every account and remote path with administrative access to connected medical devices, including vendors’ and contractors’. The 2018 report named privileged access as a servicing security challenge. [4]
Procurement checklist
Add the 2024 guidance’s labeling list to device purchase requirements: specifications, maintenance schedule, troubleshooting and acceptance testing, error codes, servicing warnings and software version information. [5]
Manufacturer authorizations
Keep each manufacturer security bulletin or written approval that authorizes a patch or update, with the device models and software versions it covers. FDA’s list depends on authorization for two of its items. [5]
Used and refurbished equipment
Before buying refurbished equipment, ask the seller which activities it performed and whether it treated any as remanufacturing. Record the answer with the purchase file. The 2016 inquiry covered remarketing alongside servicing. [2]
Downtime and isolation plans
For each connected device that cannot be patched, record the compensating steps taken, such as network isolation or disabled connectivity features, and confirm they are consistent with intended use. FDA lists turning connectivity features on or off consistent with intended use as likely not remanufacturing. [5]
Contractor terms
Require service contractors to classify their activities, document decisions and share records with the hospital.
With hindsight
The workshop took place. FDA’s 2018 report said it held the public workshop on October 27 and 28, 2016, with introductory stakeholder presentations followed by four sessions. [4] It said comments received in advance were consistent with views expressed during the workshop. [4]
Congress then asked for a report. The Food and Drug Administration Reauthorization Act became law on August 18, 2017. [4] Its section 710 charged the Secretary, acting through the Commissioner, to issue a report on the continued quality, safety and effectiveness of devices with respect to servicing. [4]
FDA published that report in May 2018. [4] It concluded that the available objective evidence was not sufficient to conclude whether there was a widespread public health concern that would justify additional burdensome regulation of servicing. [4] It found that a majority of complaints alleging bad servicing pertained to remanufacturing, and that third-party servicing is critical to the health care system. [4] It committed to clarifying the difference between servicing and remanufacturing. [4]
The clarification took the form of guidance. The 2024 Federal Register notice said that in December 2018 FDA issued a white paper titled Evaluating Whether Activities are Servicing or Remanufacturing, opened a public docket and held a public workshop on the distinction. [6] It said the white paper set out guiding principles, a flowchart and a complementary approach for software. [6] A draft guidance appeared on June 24, 2021, according to the same notice. [6] FDA announced the final guidance on May 10, 2024. [6] The notice said the final version added contextual examples, clarified its application to manufacturers and to entities acting for them, and added a section on regulatory requirements for remanufacturers. [6]
The guidance kept the line at significant change. The notice said FDA focuses on activities likely to be remanufacturing and that the determination affects the applicability and enforcement of requirements under the Federal Food, Drug, and Cosmetic Act. [6] It said FDA has consistently enforced requirements, including registration and listing and adverse event reporting, on entities engaged in remanufacturing. [6]
The underlying rule changed form but kept the definition. The 2024 guidance noted that FDA published a final rule on February 2, 2024, amending the quality system regulation, effective February 2, 2026, and renaming it the Quality Management System Regulation. [5] As checked on November 16, 2026, 21 CFR 820.3 incorporates ISO 13485 definitions and retains FDA’s own definition of remanufacturer. [7]
The current text also says a manufacturer includes those who perform remanufacturing, as checked on the same date. [7] So the regulatory consequence of crossing the line is the same in 2026 as in the 2016 definitions FDA proposed. [2] [7]
What held up from 2016 was FDA’s instinct to define activities. The six terms of the March notice became, in the 2024 guidance, a set of definitions that kept service and remanufacture as the operative pair. [2] [5] The proposed definition of remanufacture in 2016 and the guidance’s definition in 2024 are close to word for word. [2] [5]
What did not happen was regulation of servicers as such. The question the July 2016 notice posed, whether servicing should be regulated by FDA or a non-governmental organization, was answered in 2018, in our reading, with neither. [1] [4] FDA chose guidance, voluntary quality principles and clarification of an existing line. [4]
What grew was the software question. The 2016 definitions mentioned software updates in passing. [2] The 2024 guidance gave software its own section and its own default. [5] For health systems whose security teams manage connected devices, that is the part of the 2016 review that reaches furthest into daily work, as of November 16, 2026.
Spotted an error? Tell us and we will check it and correct the article where needed.