A field safety notice reports the action, not the incident

A serious incident report tells a competent authority that something happened. A field safety notice tells users what the manufacturer is doing about it. The MDR keeps these as two different documents, defined in two separate paragraphs of Article 2, and treating the notice as just a wider broadcast of the incident report misses what Article 89 actually requires it to say.

Two definitions, two jobs

Article 2(68) defines a field safety corrective action as action taken by a manufacturer, for technical or medical reasons, to prevent or reduce the risk of a serious incident in connection with a device already made available on the market. Article 2(69) defines a field safety notice as the communication the manufacturer sends to users or customers in connection with that action. Neither definition requires a serious incident to have already occurred — an FSCA can be proactive, launched on evidence that a serious incident is a risk, not only in response to one that already happened. That's a different trigger than a serious incident report, which exists to tell a competent authority about an event that already took place.

The clock starts before the action is decided

Article 87 sets the reporting clock running from the manufacturer's awareness, not from when a corrective action or notice is finalized: immediately, and no later than two days, for a serious public health threat; no later than ten days for an incident causing death or unanticipated serious deterioration in health; no later than fifteen days for other reportable incidents. Reports go in through the electronic system Article 92 establishes and are automatically routed to the competent authority of the Member State where the incident occurred or the corrective action is being carried out. A manufacturer still investigating what caused the problem, and still deciding what the corrective action will be, is already inside that clock — the report doesn't wait for the FSCA to be designed first.

What the notice has to say, not soften

Article 89(5) sets the actual content bar for the notice, and it's a drafting constraint as much as a content one: the field safety notice has to explain, in a clear manner, without understating the level of risk, the reasons for the field safety corrective action, with reference to the device malfunction and the associated risks to patients, users, or other persons, and has to clearly indicate all the actions users are to take. “Without understating the level of risk” is not incidental language sitting next to the real requirement — it is part of the requirement. A notice run through legal or communications review until the risk language reads as reassuring rather than accurate hasn't just made a tone choice; it has produced a document that no longer meets Article 89 on its own terms.

A different pairing than the correction-and-removal record

FDA's closest analog runs through a single document rather than a pair: a correction-and-removal record under 21 CFR Part 806 covers both the manufacturer's internal decision and, where required, the report to FDA, without a separate defined document for the message to users. The MDR's two-document structure — FSCA as the action, FSN as the notice about it, each with its own definition and its own content obligations — means a template built for one regulator's version doesn't map cleanly onto the other's. A checklist for the EU side has to keep the incident report, the FSCA record, and the FSN as three distinct artifacts with three distinct tests to pass, which is the structure behind the vigilance template set previewed in the launch catalog. A team with a sharper version of that structure is welcome to bring it through a template contribution.