End of Life (EOL) is the final phase of a medical device’s lifecycle, when a manufacturer stops production, sales, or support and plans for withdrawal, decommissioning, and safe disposal. For regulated devices, EOL is a controlled process that maintains traceability, post-market obligations, and patient safety until the last unit leaves service.
What is End of Life (EOL)?
End of Life (EOL) marks the deliberate retirement of a medical device, the point at which a manufacturer decides to discontinue it and manage its exit from the market and the field. It sits at the closing stage of the product lifecycle, after design, manufacturing, and the active service period.
EOL is not a single event. Teams usually separate the end of production and sale from the end of support, the service window during which spare parts, maintenance, and security updates remain available. Software has its own equivalent: IEC 62304 and IEC 82304-1 describe a retirement or decommissioning phase that closes out medical device software in a controlled way. EOL also differs from shelf life and expected service life, which describe how long a device can be stored or used, not the business and regulatory decision to wind it down.
Why End of Life (EOL) matters in medical device development
Patient safety does not end when sales do. Devices stay in clinical use for years after a manufacturer stops shipping them, so EOL has to protect the people still relying on those units. Handling it poorly creates real exposure.
Post-market obligations continue. Under EU MDR 2017/745, surveillance, vigilance, and complaint handling apply to devices on the market regardless of whether you are still selling them. Records have to be retained through the device’s lifetime per ISO 13485 and FDA quality system requirements. Connected devices and Software as a Medical Device raise the stakes further: leaving a product unpatched after end of support can turn a known cybersecurity gap into a safety issue. Get EOL wrong, and you face audit findings, field actions, and avoidable risk to patients and clinicians.
The End of Life (EOL) process
A controlled EOL follows a defined sequence rather than an abrupt cutoff:
- Decision and planning. A trigger (component obsolescence, low demand, a regulatory change, or a successor product) starts a documented EOL plan with timing, responsibilities, and risk assessment under ISO 14971.
- Notification. Communicate the discontinuation and the last date for orders to customers, distributors, and, where required, your notified body and competent authorities. A last-time-buy window lets users secure stock.
- Database and record updates. Add the commercial end date in regulatory systems such as EUDAMED and the FDA GUDID, and update technical documentation.
- Service and spare-parts wind-down. Define and publish the service life, including how long maintenance, spares, and security support continue. IEC 81001-5-1 informs how cybersecurity support is handled toward the end of support.
- Decommissioning. Retire software and connected components with secure data archiving or erasure, following IEC 62304 and IEC 82304-1 for the software side.
- Disposal. Manage physical disposal under the WEEE Directive and the safe-disposal expectations of EU MDR Annex I, accounting for contamination and the directive’s exclusions for infective or implantable devices.
Throughout, structured change control keeps the EOL traceable and audit-ready.
Common challenges and best practices
The most frequent mistake is treating EOL as a purely commercial decision. Sales stops, and the team assumes the work is done, missing the surveillance, record-retention, and disposal duties that outlive the product. Define EOL responsibilities inside the quality management system so nothing falls through.
Component obsolescence is the next trap. Suppliers discontinue parts on their own schedule, and a team without obsolescence monitoring gets caught with no last-time-buy and no qualified replacement. Track key components early and plan buffer stock or redesign.
Cybersecurity needs an explicit end-of-support date. Users have to know when patches will stop so they can plan a replacement before a connected device becomes a liability. Good practice is to set and communicate the service life up front, ideally at design time, and to design for safe disposal so EOL is already accounted for in the technical file. Retain the design history and technical documentation for the full retention period, since auditors and authorities can still ask about a discontinued device.
How SJML helps with End of Life (EOL)
SJML supports the end-of-life phase through its product lifecycle management services. That includes obsolescence management and last-time-buy planning, sustaining and sustenance engineering, value analysis and value engineering, and RMA and replacement management for units still in the field. SJML also handles regulatory sustenance, technical documentation upkeep, and structured change governance designed to minimize revalidation burden as a device is wound down. Sustainability re-engineering and total-cost-of-ownership work round out the support, so discontinuation stays controlled, compliant, and traceable.
Talk to SJML’s engineering team →
Frequently asked questions
End of life is the broad decision to discontinue a device, covering the end of production, sale, and eventual disposal. End of support is narrower: it is the date after which the manufacturer stops providing maintenance, spare parts, or security updates. A device can reach the end of sale while remaining supported in the field for several more years.
No. Under EU MDR 2017/745, post-market surveillance, vigilance, and complaint handling continue for as long as devices remain in use, not just while they are being sold. Manufacturers must keep monitoring safety, retain records, and report serious incidents until the installed base is fully retired from service.
Electronic medical devices are generally disposed of under the WEEE Directive, while EU MDR Annex I requires that devices be designed for safe disposal, with instructions in the labeling. Infective devices and active implantables fall under specific WEEE exclusions, so contamination and patient-safety handling must be addressed before any recycling or waste treatment.
IEC 62304 defines the software life cycle for medical device software through to decommissioning, and IEC 82304-1 covers the wider lifecycle of health software, including maintenance and orderly retirement. Both expect retirement to be planned, documented, and handled so that data is securely archived or erased and patient safety is preserved.
Related terms
- Obsolescence Management
- Sustaining Engineering
- Post-Market Surveillance (PMS)
- Expected Service Life
- Decommissioning
