eduKateSG · Why Science?
Decide whether work restores a device or creates a significant change
Use FDA’s 2024 guidance through intended use, performance and safety specifications, components, software, calibration, risk, testing, records and regulatory responsibility.
Medical devices need maintenance, repair and replacement parts across their useful lives. Most work aims to restore safe operation, yet some activities change the device enough to become remanufacturing with different regulatory responsibilities.
FDA’s May 2024 final guidance clarifies the boundary. The decisive question is what the activity does to intended use, performance or safety specifications, assessed for the complete device and work performed.
Did you know? Calling a company a servicer does not make every activity servicing. The same organization can perform ordinary maintenance on one device and remanufacturing on another if the technical change crosses the regulatory definition.
This guide supports engineering-change and regulatory literacy. It does not classify a specific repair or business.
Chapter index
Chapters 1–9: definitions, device baseline and activity scope
- 1. The May 2024 guidance is final
- 2. Remanufacturing has a regulatory definition
- 3. Servicing maintains or restores function
- 4. The entity name does not decide the activity
- 5. The whole activity is evaluated
- 6. Intended use changes point toward remanufacturing
- 7. Performance changes need significance assessment
- 8. Safety specifications include risk controls
- 9. Component replacement needs technical comparison
Chapters 10–17: change significance, testing and regulatory duties
- 10. Software changes can alter intended behaviour
- 11. Calibration is bounded by specifications
- 12. Sterilization and reprocessing can be implicated
- 13. Risk-based questions organize the decision
- 14. Records support a defensible classification
- 15. Remanufacturers have manufacturer obligations
- 16. Service labeling can support safe useful life
- 17. A complete activity receipt makes the boundary reproducible
Servicing and remanufacturing separate at the point where work significantly changes performance, safety specifications or intended use. FDA’s guidance clarifies whether activities on medical devices are likely servicing or remanufacturing and explains existing responsibilities. This keeps maintenance records from hiding design-level changes.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about the may 2024 guidance is final? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for the may 2024 guidance is final. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the may 2024 guidance is final, its identifier or version context, and one limit that must remain visible.
FDA’s May 2024 final guidance gives a risk-based framework for that boundary. It includes processing, conditioning, renovating, repackaging, restoring or other acts that significantly change performance or safety specifications or intended use. It also connects engineering evidence to regulatory responsibility.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about remanufacturing has a regulatory definition? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for remanufacturing has a regulatory definition. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for remanufacturing has a regulatory definition, its identifier or version context, and one limit that must remain visible.
A replaced part can look similar yet change calibration, control or safety behaviour. Servicing generally returns a device to the original manufacturer’s safety and performance specifications and intended use. Labels and service instructions help preserve safe performance over useful life.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about servicing maintains or restores function? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for servicing maintains or restores function. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for servicing maintains or restores function, its identifier or version context, and one limit that must remain visible.
The conclusion depends on the complete activity, device and resulting specifications. An original manufacturer, hospital, independent servicer or other party can perform work whose classification depends on what it does. A documented rationale lets another reviewer retrace the classification.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about the entity name does not decide the activity? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for the entity name does not decide the activity. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for the entity name does not decide the activity, its identifier or version context, and one limit that must remain visible.
Servicing and remanufacturing separate at the point where work significantly changes performance, safety specifications or intended use. Parts, software, calibration, materials, tools and combined steps should be considered together rather than isolated by job title. This keeps maintenance records from hiding design-level changes.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about the whole activity is evaluated? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for the whole activity is evaluated. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for the whole activity is evaluated, its identifier or version context, and one limit that must remain visible.
CHAPTER 6 OF 17 · Compare specifications
6. Intended use changes point toward remanufacturing
FDA’s May 2024 final guidance gives a risk-based framework for that boundary. Changing indications, users, use environment, anatomical site or fundamental purpose can change intended use. It also connects engineering evidence to regulatory responsibility.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about intended use changes point toward remanufacturing? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for intended use changes point toward remanufacturing. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for intended use changes point toward remanufacturing, its identifier or version context, and one limit that must remain visible.
CHAPTER 7 OF 17 · Compare specifications
7. Performance changes need significance assessment
A replaced part can look similar yet change calibration, control or safety behaviour. Output, accuracy, precision, speed, energy, alarms or control behaviour should be compared with original specifications and risk. Labels and service instructions help preserve safe performance over useful life.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about performance changes need significance assessment? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for performance changes need significance assessment. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for performance changes need significance assessment, its identifier or version context, and one limit that must remain visible.
CHAPTER 8 OF 17 · Compare specifications
8. Safety specifications include risk controls
The conclusion depends on the complete activity, device and resulting specifications. Protective limits, interlocks, electrical isolation, biocompatibility, sterility and essential performance can be affected by work. A documented rationale lets another reviewer retrace the classification.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about safety specifications include risk controls? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for safety specifications include risk controls. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for safety specifications include risk controls, its identifier or version context, and one limit that must remain visible.
CHAPTER 9 OF 17 · Assess risk and evidence
9. Component replacement needs technical comparison
Servicing and remanufacturing separate at the point where work significantly changes performance, safety specifications or intended use. Form, fit, function, material, tolerance, supplier, software and life characteristics help show whether a replacement preserves specifications. This keeps maintenance records from hiding design-level changes.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about component replacement needs technical comparison? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for component replacement needs technical comparison. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for component replacement needs technical comparison, its identifier or version context, and one limit that must remain visible.
CHAPTER 10 OF 17 · Assess risk and evidence
10. Software changes can alter intended behaviour
FDA’s May 2024 final guidance gives a risk-based framework for that boundary. Firmware, configuration, cybersecurity controls and algorithms require controlled assessment, verification and validation. It also connects engineering evidence to regulatory responsibility.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about software changes can alter intended behaviour? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for software changes can alter intended behaviour. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for software changes can alter intended behaviour, its identifier or version context, and one limit that must remain visible.
CHAPTER 11 OF 17 · Assess risk and evidence
11. Calibration is bounded by specifications
A replaced part can look similar yet change calibration, control or safety behaviour. Restoring calibration to validated ranges differs from changing ranges, methods or control logic in ways that alter device performance. Labels and service instructions help preserve safe performance over useful life.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about calibration is bounded by specifications? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for calibration is bounded by specifications. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for calibration is bounded by specifications, its identifier or version context, and one limit that must remain visible.
CHAPTER 12 OF 17 · Assess risk and evidence
12. Sterilization and reprocessing can be implicated
The conclusion depends on the complete activity, device and resulting specifications. Changes to reusable devices or instructions can affect cleaning, disinfection, sterilization, materials and useful life. A documented rationale lets another reviewer retrace the classification.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about sterilization and reprocessing can be implicated? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for sterilization and reprocessing can be implicated. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for sterilization and reprocessing can be implicated, its identifier or version context, and one limit that must remain visible.
CHAPTER 13 OF 17 · Document the decision
13. Risk-based questions organize the decision
Servicing and remanufacturing separate at the point where work significantly changes performance, safety specifications or intended use. FDA’s guidance uses considerations and examples to evaluate whether the activity significantly changes specifications or intended use. This keeps maintenance records from hiding design-level changes.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about risk-based questions organize the decision? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for risk-based questions organize the decision. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for risk-based questions organize the decision, its identifier or version context, and one limit that must remain visible.
CHAPTER 14 OF 17 · Document the decision
14. Records support a defensible classification
FDA’s May 2024 final guidance gives a risk-based framework for that boundary. Work orders, incoming condition, instructions, parts, software versions, tests, deviations and release decisions should preserve what changed. It also connects engineering evidence to regulatory responsibility.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about records support a defensible classification? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for records support a defensible classification. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. If a field is missing, write “not shown” and follow the official documentation rather than inventing a value.
Evidence checkpoint
Record the evidence object for records support a defensible classification, its identifier or version context, and one limit that must remain visible.
CHAPTER 15 OF 17 · Document the decision
15. Remanufacturers have manufacturer obligations
A replaced part can look similar yet change calibration, control or safety behaviour. An entity performing remanufacturing is subject to applicable manufacturer regulatory requirements, including registration, listing, labeling and quality-system duties. Labels and service instructions help preserve safe performance over useful life.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about remanufacturers have manufacturer obligations? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for remanufacturers have manufacturer obligations. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Before comparing two records, check that their object types, methods, versions and units really align.
Evidence checkpoint
Record the evidence object for remanufacturers have manufacturer obligations, its identifier or version context, and one limit that must remain visible.
CHAPTER 16 OF 17 · Document the decision
16. Service labeling can support safe useful life
The conclusion depends on the complete activity, device and resulting specifications. FDA recommends service information that helps entities maintain quality, safety and effectiveness without enabling unsafe modifications. A documented rationale lets another reviewer retrace the classification.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about service labeling can support safe useful life? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for service labeling can support safe useful life. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Finish by naming one supported statement and one stronger statement that still needs another evidence layer.
Evidence checkpoint
Record the evidence object for service labeling can support safe useful life, its identifier or version context, and one limit that must remain visible.
CHAPTER 17 OF 17 · Document the decision
17. A complete activity receipt makes the boundary reproducible
Servicing and remanufacturing separate at the point where work significantly changes performance, safety specifications or intended use. Record device and original specifications, entity, requested work, parts and software, intended use, performance and safety assessment, risks, tests, classification rationale, labels and release. This keeps maintenance records from hiding design-level changes.
Try this
Evidence question: Which official rule, guidance passage, label, report or record supports the point about a complete activity receipt makes the boundary reproducible? Answer in three parts: identify the visible field or file, explain how it bears on the question, and state the boundary of that evidence. Preserve the database’s own object names and accession rather than flattening everything into the word ‘data’.
Try this: Record the device, identifier, version, date, result and one limit for a complete activity receipt makes the boundary reproducible. Turn the result into a compact claim-evidence-reasoning note, then ask a partner to retrace it. Keep the identifier, retrieval date and source page in the note so the route can be repeated.
Evidence checkpoint
Record the evidence object for a complete activity receipt makes the boundary reproducible, its identifier or version context, and one limit that must remain visible.
Contents · Previous chapter · Continue at the Science Learning Hub
A repair decision is credible when the original specification and final device can be compared
The servicing-remanufacturing boundary protects useful maintenance while keeping significant changes under manufacturer controls. The record should let another reviewer reconstruct parts, software, risks, tests and the final rationale.
Save the device, model, UDI and baseline specifications, original intended use, incoming condition, requesting party, entity and facility, work order, procedures, parts and suppliers, software and configuration, calibration, sterilization or reprocessing effects, risk assessment, verification and validation, performance and safety results, deviations, classification decision, regulatory obligations, label changes and release approval.
| Reading object | What it can support | Question to keep visible |
|---|---|---|
| Baseline specification | Defines original safety and performance | Which controlled version? |
| Activity record | Shows parts, software and steps | What changed? |
| Risk assessment | Evaluates significance and controls | Could harm or intended use change? |
| Release decision | Classifies and approves the result | Which tests support it? |
Sources and next reading
Substantive resource claims in this article were checked against the primary pages below. A structured record is a route into evidence; it does not by itself prove a scientific conclusion. Recheck the live record, evidence labels and release context before using it in assessed work or research.
For a classroom enquiry, save a short research receipt containing the question, search terms, selected object, exact identifier, version, access date and the evidence boundary you observed. Add the file or page that supports each statement. This small routine turns browsing into accountable science learning and gives a teacher, classmate or future analyst a route they can independently follow.
Before sharing the conclusion, ask another reader to retrace the route without verbal hints. If they reach a different version, file or interpretation, improve the receipt and narrow the claim. Reproducibility begins with this practical check. It teaches careful reading, supports fair collaboration and keeps uncertainty visible while evidence moves from an online service into notes, analysis and a final explanation.
A useful final review separates five questions. What object was found? Which organisation or repository maintains it? What exact evidence was inspected? Which statement does that evidence support? What remains uncertain? Answer each question in one sentence, then connect every answer to a visible field, file or source page. This review catches common mistakes: citing a collection when a file supplied the value, treating the newest release as the analysed release, confusing permission with scientific suitability, or turning a discovery count into a conclusion. It also gives students a calm way to improve work. A missing detail becomes a next research step instead of an invitation to guess. When the route is complete, the final explanation can stay simple because the identifiers, dates, versions, limitations and supporting evidence are already organised underneath it.
Primary sources
- FDA Remanufacturing and Servicing Overview — accessed 25 October 2026.
- FDA Remanufacturing Final Guidance — accessed 25 October 2026.
- FDA Quality and Compliance — accessed 25 October 2026.
- FDA QMSR Overview — accessed 25 October 2026.
- FDA Reprocessing Information for Manufacturers — accessed 25 October 2026.