How a healthcare provider should respond to a medical device field safety notice

A field safety notice is an action request, not a routine reminder. Identify the affected devices across every site and store, keep patients safe during the work, reach the people who use the equipment and prove that every affected item was closed. This concerns United Kingdom medical device safety communications, and local nation and organisation reporting routes must be checked.

A field safety notice, or FSN, is a communication from a medical device manufacturer or its representative about a safety issue and the action customers should take. The manufacturer uses the notice to communicate a field safety corrective action, or FSCA, intended to reduce a specified risk. The MHRA: safety communications guide distinguishes a manufacturer FSN from MHRA Device Safety Information, which may supplement manufacturer advice.

Treat the notice as an action request

When a provider receives an FSN, it should log receipt, identify the product and affected identifiers, find every relevant device or stock item, alert the clinical and technical owners, and follow the notice’s immediate instructions. Some notices require use to stop. Others require an inspection, software update, revised operating instruction, patient follow-up or return to the manufacturer. The action cannot be inferred from the term FSN alone. Read the actual final notice and any current MHRA supplement. A public MHRA: field safety notices listing says recipients must act on a notice received from a manufacturer, while the published listings themselves are for information and direct product questions to the manufacturer.

The hardest part is often not reading the notice. It is proving that the organisation found the correct devices across sites and stores, kept patients safe during the work, reached people who use the equipment, and closed every affected item. A signed acknowledgement to the manufacturer is useful, but it is not proof that every device was updated or every clinician received the changed instruction. Keep those steps distinct.

Check authenticity, version and scope

Confirm who issued the notice, its date and reference, the product name, manufacturer, model, catalogue number, serial or lot range, software version and unique device identifier where given. An FSN may be revised. Check whether the email attachment is the latest version and whether the manufacturer has issued a correction or a follow-up. The MHRA: guidance for manufacturers on effective FSNs describes the information expected in a clear notice, including the problem, affected device identification, risk, actions, timescales, communication and acknowledgement route.

If an FSN arrives through an unfamiliar channel, verify it with the manufacturer’s official contact or the MHRA safety communications listing before opening untrusted attachments or changing equipment. Do not delay urgent patient protection while checking administrative details. An urgent notice may be circulated before the MHRA’s ordinary review period. The action owner should identify the risk and any immediate restriction, then confirm the notice’s authenticity and current status through a reliable route.

Read the full device description. A product family name may cover several variants, while the affected range covers only some batches. Software notices may apply to an installed version or configuration rather than a physical serial number. Implant notices may need patient-level tracing, while a diagnostic kit notice may require review of previous results. The manufacturer should explain how to identify affected devices and whether products transferred to other organisations also need the notice. If the notice is unclear or identifiers do not match local records, ask the manufacturer for clarification and record the answer.

Do not assume that a device missing from the local asset register is absent from the site. Loan equipment, evaluation units, consignment stock, theatre sets, community devices, patient-held equipment, contractor-maintained assets and stock in transit may be outside the main inventory. The search plan should reflect how the organisation actually obtains and moves devices. A no affected items response needs evidence of which inventories and departments were checked.

Find every affected device and assign a status

Match the notice against procurement records, clinical engineering inventory, ward and department lists, stock systems, loan logs, theatre trays, pharmacy or laboratory records, and manufacturer service lists as relevant. Search by all identifiers provided, not only the product name. A manufacturer may use a different naming convention from local purchasing. Record both identifiers and any mapping used. For software, identify installed build or version and hosted or stand-alone deployments. For consumables, track lots and expiry dates across stores and point-of-use cupboards.

Give each possible match a status: confirmed affected, confirmed not affected with reason, awaiting identifier check, already used or transferred, or not yet found. That prevents an unanswered item from disappearing behind a site-wide action complete flag. Record who checked the device and when. Where a physical device is quarantined, label it and prevent booking or dispatch. Where use may continue subject to a new instruction, ensure the instruction reaches the actual users and remains available at the point of care.

The MHRA manufacturer guidance says an FSN should describe recovery, quarantine, disposal or modification where relevant and should request onward transmission to organisations that received affected devices. A provider that has loaned or transferred a device should trace the destination and pass the notice on under the manufacturer’s instructions. The provider may need to involve home-care teams or patients where a device is used outside its premises. Keep a record of what was sent and what was acknowledged.

A device’s status may change several times. It may be identified, placed out of use, inspected, modified, tested and returned to clinical service. Keep the transitions with dates and evidence. Do not let a contractor’s visited site note close the whole FSN before the device’s correction and user communication are confirmed. A generic single-fault guide covers an individual fault found in use, but this page owns a manufacturer-led action across an affected device population.

Make the clinical risk decision explicit

The manufacturer describes the hazard and proposed corrective action. The provider must apply that information to its patients and services. Does the device support life-sustaining care, diagnosis, monitoring, treatment or mobility? Is it already in use? What alternatives exist? Can the device be isolated without interrupting essential care? Does the notice mention patients who have already been treated or implanted? Clinical engineering, the medical device safety officer and the relevant clinical lead should coordinate an immediate decision under local governance.

An FSN may prescribe stopping use, or it may allow continued use with a mitigation until a fix is available. Do not substitute a local guess for the manufacturer’s instruction. If the notice’s proposed action is unclear or impracticable in a particular clinical setting, contact the manufacturer and escalate through the provider’s patient safety process. An MHRA Device Safety Information message may give additional or different advice. The MHRA safety communications guide explains that such messages can supplement manufacturer FSNs and target the users who need to act.

The risk decision must also address service continuity. Removing a device can create harm if no safe substitute exists. Record the clinical mitigation, affected departments, alternative equipment, monitoring and review point. If the device remains in use under a temporary instruction, make that instruction visible to every user and every shift. A purchase order for replacement equipment is not a current clinical control. If patient follow-up is recommended, keep the patient-identifying work in appropriate clinical systems and link only necessary status metadata to the equipment action record.

Distribute the notice to the real users

An email to one department head does not prove the notice reached the people who use the device. Build a distribution list from the confirmed affected locations, user groups and shifts. Include clinical engineering, procurement, stores, specialist departments, community teams and third-party service providers where their work is affected. Send the core action in plain language with a link to the full notice, the affected identifiers, the deadline and a named contact. Ask each owner to report what devices they checked and what action they completed.

The MHRA manufacturer FSN guidance asks the manufacturer to tell recipients to pass the notice to everyone who needs awareness and to organisations that received affected devices. That instruction should become a local cascade plan, with proof of acknowledgement and action. A read-and-acknowledge record may be needed when the notice changes how a device is used. A technical correction and a user instruction are different tasks, and both may be required.

Use a defined owner for each site or department. A central safety officer can coordinate, but local managers know which devices are deployed, who is on leave and which agency staff use them. Check the out-of-hours service. If an urgent notice arrives on a Friday, waiting for Monday’s standard governance meeting may be too late. The organisation’s device safety process should have a route for immediate decisions, escalation and temporary control.

If the manufacturer asks for a response form, return it accurately. A response that says not affected should follow a documented search, not a quick assumption. A response that says action complete should mean all affected items have been addressed under the notice. Save the submitted form and any manufacturer acknowledgement. Keep a separate local completion record, because the form may not capture every device, user, patient or service decision.

Carry out the correction and verify it worked

The action might be return, exchange, software patch, configuration change, inspection, calibration, revised instructions or patient follow-up. Assign competent people and the correct environment for the work. A patch may require clinical downtime and validation. A replacement component may change service or calibration status. A recalled implant cannot be treated like unused stock. Follow the manufacturer and any MHRA supplement for the exact product. Record why a device was excluded if it appears in the product family but not the affected range.

For each affected device, capture the action performed, technician, date, part or software version, test result and current use status. If the manufacturer or its contractor performs the work, obtain a device-specific report. A generic certificate saying all devices completed is weak if the local inventory shows an unlocated unit. Reconcile the action list with the original affected-device list and investigate exceptions. Test the modified device as required before return to clinical use and document who accepted it.

The MHRA guidance for manufacturers describes the manufacturer’s field safety corrective action strategy and monitoring of effectiveness. The provider has its own closure question: did every applicable item and user receive the specified action? A completion percentage can help coordinate work, but it should never hide a critical device still in use without mitigation. Record open exceptions with a reason, owner and decision on continued use.

Check for a later version of the notice or a follow-up FSN. A manufacturer may change the affected range or the corrective instruction after initial distribution. Maintain version history and assess whether devices previously marked unaffected are newly in scope. Keep the original notice and later update linked so staff know which instruction is current. If the manufacturer sends a second effectiveness check, answer from the actual device records.

Handle incidents separately from the notice workflow

An FSN may be issued because of an incident elsewhere, but its arrival does not itself prove that a patient in your organisation was harmed. Conversely, a local adverse incident involving the device may need reporting even when the provider has already responded to the FSN. The MHRA: Yellow Card medical device reporting says healthcare professionals in England, Wales and Northern Ireland should report adverse device incidents through Yellow Card in line with their organisation’s policy. Scotland has a separate professional reporting route. Retain the device where possible if investigation may be needed, following clinical safety and infection control arrangements.

The provider’s local patient safety process should determine whether to investigate previous use, review diagnostic results, contact patients or make statutory notifications. The manufacturer notice may specifically ask for such work. Keep patient-identifiable evidence in clinical systems. The FSN tracker can record that a review was assigned and completed without exposing a patient list to a general equipment team. If a device has been transferred to another provider, alert that provider through the notice’s onward-distribution process.

Do not confuse a manufacturer FSN with an MHRA Device Safety Information message or a general recall notice. Each has its own issuer and instructions, and more than one may concern the same device. The action owner should follow the current authoritative communication and document how the instructions fit together. Where there is apparent conflict, escalate to the manufacturer and MHRA or local safety officer. Do not silently choose the easier task.

Build an evidence record that closes the loop

A useful record starts with notice metadata: issuer, reference, date, current version, affected device description, risk, required actions and deadline. Add the internal receipt date, triage decision and accountable owner. Attach the actual notice and relevant MHRA supplement. Then keep an affected-device register with model, serial or lot, location, user department, status, action and closure proof. Record the search sources, including loan and transferred stock, so a no devices found conclusion is credible.

The record should also capture the clinical decision. Which services were restricted or continued under mitigation? Who approved the decision? When did each department receive the notice? Were users trained on changed instructions? Were patients or prior results reviewed where required? Which incidents were reported through the proper route? Keep sensitive clinical data in the appropriate controlled record, with only a reference in the FSN log. The aim is a coherent trail, not one giant attachment with uncontrolled access.

Close only after reconciliation. Compare the manufacturer affected range with the procurement and asset list, the physical check results, the returned acknowledgement and the completed correction reports. Investigate missing serial numbers, devices at another site and stock transferred out. If an item cannot be found, document the search and ongoing restriction. If a manufacturer service visit is delayed, keep its interim mitigation and next review visible. A date field marked due is not a substitute for evidence of action.

Finally, learn from the notice. Did the provider receive it directly and promptly? Was contact information current? Did the asset register identify every device? Did teams know which users to brief? Were loan devices traceable? A near miss in distribution can be corrected before the next safety notice. This is a distinct information gain from an ordinary servicing record, because the task tests whether the organisation can act across its whole device population.

Worked example: an anaesthesia unit software correction

A manufacturer sends an FSN about a software condition affecting a defined version of an anaesthesia unit. The hospital safety lead logs the notice and matches model and installed software version across theatre and recovery areas. Two units are in scope. A third unit has the same product family but a newer software build, so it is recorded as excluded with evidence of its version. The clinical and engineering leads review the hazard and the manufacturer’s interim instructions. They restrict use of the affected units for the specified circumstances and arrange safe alternatives for scheduled cases.

The manufacturer schedules a patch. A trained engineer records the version installed, post-patch checks and device identifier for each unit. Clinical staff receive the revised use instructions and confirm they understand them. The hospital returns the manufacturer response form and keeps a separate local register showing both units corrected and accepted for use. The team checks whether any cases during the possible risk period need review under the notice. The example does not prescribe a specific anaesthesia control, because the manufacturer’s current FSN and the clinical service determine it.

Worked example: diagnostic reagent with possible false results

A laboratory receives an FSN concerning a particular reagent lot and potential false-negative results. The laboratory checks stock in use, unopened stock and kits distributed to satellite sites. Affected lot numbers are segregated under the manufacturer’s instructions. The laboratory lead determines which tests were performed with the affected lot during the notice’s stated period. The clinical team and laboratory quality manager review whether patients or requesting clinicians need notification or retesting, following the notice and any MHRA supplement.

A purchasing system may show zero remaining stock while earlier results still require review. This is why an FSN cannot be closed solely by returning unopened kits. The record needs lot traceability, test dates, the clinical review outcome and evidence that satellite users received the notice. Patient-identifiable results stay in the laboratory and clinical systems. The central FSN register records completion status and references the controlled review.

Questions before closure

Can you show the final notice and its current version? Has every relevant asset, stock location, loan device and transferred item been checked against the affected identifiers? Can you explain the clinical decision and any temporary use restriction? Did the actual users receive the instruction? Is the manufacturer response accurate and saved? Does each affected item have evidence of the required correction and any test before use? Were prior patients or results assessed where the notice called for it? Were local adverse incidents reported through the correct route? Are open exceptions owned and visible?

A closed notice should answer those questions with evidence. An acknowledged email is the start of the response, not its completion.

Questions people ask

Sources

• MHRA: safety communications taxonomy
• MHRA: effective field safety notices, guidance for manufacturers
• MHRA: field safety notices listing example
• MHRA: Yellow Card medical device reporting

Related: Complys for hospitals, incident reporting software, and more compliance guides.