A pre-purchase recall and field-safety workflow for buyers and biomedical teams, current as of September 2026. It is not legal advice, and it makes no claim about the recall status of any unit offered for sale.
A recall check is one of the few pieces of due diligence that a buyer can perform completely independently, in a few minutes, without the seller’s help. That makes it unusual: most verification depends on documents only the seller holds, while this one depends on public records. The consequence is simple ¡ª if a recall check is not done before purchase, it is not a gap in the seller’s paperwork, it is a gap in the buyer’s process.
Recalls are a buyer-side check, not a seller favor
Public recall and safety-notice systems exist so that anyone can check a device’s regulatory history. Buyers are the party with the incentive to look, and the check is cheap enough that it belongs in every used-equipment purchase rather than only in high-value ones.
It also changes the negotiation. A unit covered by an open field action is not necessarily unsellable; it may simply require a remedy before it can be placed into service. Establishing that before purchase turns a latent liability into a priced, planned task.
Where to search
| Source | What it covers | How to use it |
|---|---|---|
| National device recall systems (FDA-type registries) | Recalls and field corrections for devices placed on that market | Search by product, model or manufacturer, and record the event number and date |
| Open data interfaces | Structured recall records that can be searched and filtered | Useful for screening a product family before a detailed check |
| Regional authorities and competent bodies | Notices that apply to other markets | Relevant when the device came from, or will be used in, that market |
| Manufacturer field-safety notices | Corrections that may not be classed as recalls | Check the manufacturer’s own notice channel for the model |
| Regulatory databases for adverse events | Reported events, which are not findings of fault | Read as signals to investigate, not as conclusions |
Worded loosely, each of these answers a different question: has the product been the subject of a corrective action, has a specific unit been the subject of one, and have problems been reported. A complete check touches at least the first two.
A worked example of why status matters
Public recall records show how status and scope interact. A search of the FDA’s open recall data for intra-aortic balloon pump products returns, among others, an event initiated on 17 October 2022 concerning short battery run-times. The affected product list for that event includes more than one console family, and it includes entries explicitly described as refurbished units. Two lessons follow from a record like that: the check must be run against the exact model rather than the brand, and a refurbished unit is not automatically outside the scope of a field action.
This example is illustrative of the method rather than a statement about any particular listing. Its value is in showing what the records look like and what has to be matched.
Matching serial and lot to the notice
Finding an event is only half the check. The other half is establishing whether the specific unit is affected, which depends on how the notice defines its scope.
- Model-level scope: all units of a model or configuration are covered; match the model and any variant detail.
- Lot or batch scope: specific production lots are covered; the unit’s lot marking has to be read from the device or its packaging.
- Serial-level scope: individual serial numbers are named; the serial must be obtained from the seller before purchase.
- Date or software scope: units produced or updated within a range are covered; the manufacture date or software version decides it.
Where the notice is serial-specific and the seller will not provide the serial before payment, that is a finding in itself. The buyer cannot complete the check, and the purchase should be structured accordingly.
Interpreting classes and status
Recall classifications describe the severity of the issue and the urgency of the response, not whether a unit is safe to use. What matters for a purchase decision is the current status of the event and its remedy: whether the corrective action is open, completed for this unit, or superseded. A unit whose remedy has been completed by an authorised party may be perfectly usable; a unit with an open action needs the remedy before it enters service.
Adverse-event databases sit alongside recalls and answer a different question. Reports indicate that someone reported a problem; they are not findings that the device caused it. They are useful for screening a model’s history and for deciding what to inspect, not for concluding that a unit is unsafe.
Documenting the check
| Log field | What to record |
|---|---|
| Device identity | Model, variant, serial and manufacture date, as supplied by the seller |
| Sources searched | Each database or notice channel consulted, with the date searched |
| Results | Event numbers, dates and the scope of any action found |
| Assessment | Whether the unit appears to fall within scope, and on what basis |
| Action | Remedy required, who performs it, and the evidence to obtain afterwards |
| Reviewer | Who performed the check and when |
The check becomes more valuable when it is repeated after purchase. Field actions are issued during a device’s life, so a unit that was clear at purchase can be affected later ¡ª which is why the same identity data should be held in your asset register and monitored, not filed with the purchase paperwork and forgotten.
Questions buyers ask
Is a device with a past recall safe to buy?
That depends on the current status and the remedy, not on the fact that an event exists. Establish whether an action is open for this unit and what completing it requires, then decide.
Do adverse-event reports mean the device is faulty?
No. Reports are accounts of problems, not determinations of cause. They are useful as screening signals that tell you what to inspect or ask about.
How often should the check be repeated?
Before purchase, at acceptance, and periodically during the device’s life ¡ª because new actions are issued after the unit enters service. The identity data recorded at purchase is what makes the later checks possible.
Run the check before you buy, record what you found, and repeat it during the device’s life. If you are evaluating a unit and want its documentation, ask HHG for the records and serial details, or browse the current listings. Related reading: managing medical equipment recalls ¡ª and use your own acceptance procedure to check the unit during the first days after delivery.