Trend screen: p-chart limits, run rule and CUSUM
Expected count = units × baseline proportion. SD = √(n × p0 × (1 − p0)). Limits = expected + 2 or 3 × SD. The run rule flags 2 of 3 consecutive points beyond the upper 2σ limit. The standardized CUSUM is S(t) = max(0, S(t−1) + z − k), with z = (observed − expected) ÷ SD, and it signals when S exceeds h.
Disproportionality screen and registry observed-to-expected
A ratio shows that an event is overrepresented in reports. It is not an event rate or a relative risk. An O/E flag shows more revisions than the case mix predicts. It does not show the cause.
A. Disproportionality 2×2 table (one product code)
B. Registry observed-to-expected with exact Poisson limits
Time to failure: life table with Kaplan–Meier survival
For each interval, enter the devices at risk at its start and the failures in it. Survival in the interval is 1 − (failures ÷ at risk), and cumulative survival is the product of these values. The Greenwood variance is S² × Σ [d ÷ (n × (n − d))], and the 95% interval is linear, S ± 1.96 × SE, truncated at 0% and 100%.
Signal prioritization: five-domain scale
Score each domain from 1 to 5 against the anchors, and write a rationale for each score. Scores 2 and 4 fall between the anchors shown. The example company's bands are A (20–25), B (14–19) and C (5–13). A signal with severity 5 and detectability 4 or 5 goes to Band B at least. Any urgency trigger sends it to Band A. The board may move a signal one band up or down. Either move needs a written reason, and a downward move also needs the chair's signature. Prioritization never changes a legal reporting clock.
Risk-file update: probability band and risk region
This module uses the illustrative company 5×5 matrix from Chapter 18 (Tables 18.1 and 18.2), which is not a regulatory requirement. Enter the risk-file estimate from before the signal and the post-market data, using the exposure of the affected population only. Placing a risk in a cell does not replace the written ALARP and state-of-the-art judgment.
Decision record
This module builds a printable record from the signal-record fields (Tool T-21) and the FSCA decision-record fields (Tool T-17). The record keeps the conclusion (confirmed, refuted or indeterminate) separate from the status, which is administrative. "Closed" is a status, not a finding. Write the record on the day of the decision. Later additions are new, dated entries.