Incident and Adverse-Event Reporting¶
Reporting system — instantiates Longitudinal Follow-Up Validation
A standing channel that lets anyone report a rare or severe event against a predefined catalog, so latent harms surface as signals and route straight to corrective action.
Some harms are too rare, too severe, or too unpredictable to catch on a schedule — you cannot survey your way to a one-in-a-million failure. Incident and Adverse-Event Reporting meets those by keeping an always-open intake through which any operator, user, or bystander can report a defined event when it happens, matching it against a catalog of the events that matter, and routing every credible report onward to someone who can act. Its defining character is that it is passive and event-triggered rather than scheduled and denominator-based: it does not enroll a population or compute a rate, it waits for a signal and makes sure that signal cannot die in an inbox. It is the archetype's tripwire for the harms that arrive unannounced.
Example¶
A national aviation authority runs a voluntary reporting channel modeled on the real Aviation Safety Reporting System, into which pilots, controllers, and mechanics can file a report whenever something unsafe happens — an altitude deviation, a near-miss on the taxiway, a confusing new approach chart. Reports are non-punitive by design; a filer who self-reports an honest error gains limited immunity, which is what keeps the channel full instead of empty.[1] Each report is coded against a catalog of event types the authority has decided it must not miss. Over a season, a handful of unrelated-looking reports all mention the same reconfigured intersection at one airport, where a taxiway sign is easy to misread at night. No single report is alarming; the pattern is. The channel's job is to make that pattern visible and route it to the office that can repaint the sign — closing the loop from scattered field signals to a concrete fix before the near-miss becomes a collision.
How it works¶
- Keep the intake always open and low-friction. The channel must be easier to use than to ignore, or the rarest and most important events never get filed.
- Protect the reporter. Non-punitive handling and confidentiality are load-bearing: a channel that punishes filers reports only what cannot be hidden.
- Code every report against the catalog. Each event is classified against a predefined list of what-must-not-be-missed, so genuine signals are not lost among noise and near-duplicates can be aggregated.
- Route credible signals to an owner. Every actionable report reaches someone with authority to fix, escalate, or investigate — and the loop is closed back to the reporting community.
Tuning parameters¶
- Reporting threshold — how minor an event still warrants a report; lower catches weak early signals but buries reviewers in noise.
- Reporter protection — anonymity and immunity strength; more protection lifts reporting volume but weakens follow-up traceability to the specific case.
- Catalog granularity — how finely event types are pre-classified; finer aggregates better but risks forcing novel events into stale boxes.
- Triage latency — how fast a report is reviewed and routed; faster prevents harm but costs standing reviewer capacity.
- Feedback visibility — whether reporters learn what came of their reports; visible closure sustains the reporting culture the whole channel depends on.
When it helps, and when it misleads¶
Its strength is catching the rare, the severe, and the unforeseen — signals no scheduled survey or fixed indicator would ever be aimed at, surfaced by the many eyes already in the system.
Its failure mode is that spontaneous reporting has no denominator. You see the numerator — reports filed — but not the exposure base, so you cannot compute a true rate, and under-reporting is the norm: fear, friction, and habituation all suppress filings, and a quiet channel can mean either safety or silence. It is prone to the exact biases of who bothers to report. The classic misuse is reading a low report count as a low event rate — treating the absence of complaints as evidence of safety. The guarding discipline is to treat the channel as a signal detector, not a rate estimator: use it to trigger investigation, and hand any question about true incidence to a denominator-bearing sibling.
How it implements the components¶
This channel owns the archetype's spontaneous-signal side — the machinery for catching and routing the unscheduled:
delayed_adverse_effect_watch— it is the standing watch for rare, latent, and interaction-dependent harms that appear only in live operation.sentinel_event_catalog— the predefined list of event types the system codes against and must never miss; it turns scattered reports into recognizable categories.corrective_feedback_pathway— every credible signal is routed to an owner who can act, and closure is fed back to the reporting community.
It carries no denominator, so it does not build the enrolled traceable_cohort_or_asset_linkage nor the revalidation_trigger_threshold that a denominator-bearing surveillance apparatus trips — those belong to Post-Market Surveillance Registry, which can compute the rate this channel cannot.
Related¶
- Instantiates: Longitudinal Follow-Up Validation — it is the archetype's tripwire for harms that arrive off-schedule.
- Sibling mechanisms: Post-Market Surveillance Registry · Longitudinal Cohort Study · Warranty and Failure-Return Analysis · Follow-Up Visit or Survey Protocol · Security Patch Effectiveness Monitor · Scheduled Revalidation Review
Editorial Notes¶
Form Classification¶
Form family: Monitoring, Sensing & Alerting
Rationale: The standing channel repeatedly captures actual rare or severe events against a catalog and emits signals for corrective response.
Nearest alternative: Organization, Role & Governance — An institutional service hosts reporting, but ongoing adverse-event sensing is the defining output.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Medicine & Healthcare
Origin pattern: Convergent development
Present-day reach: Multi-domain
Rationale: Standing adverse-event channels and just-culture routing are deeply institutionalized in clinical patient safety.
Related originating lineages:
- Aviation & Aeronautics — Aviation independently developed confidential occurrence and near-miss reporting systems.
- Engineering & Design — Industrial safety and quality systems materially standardized nonconformance and hazard reporting.
Review outcome: Independent reviewer agreement; high confidence.
References¶
[1] A just culture in safety science is one that separates honest error and reasonable risk-taking (which are reported and learned from, without blame) from reckless conduct (which is not excused). It is the precondition that keeps a voluntary reporting channel populated — where filing an error is punished, the channel goes silent and the harms it was meant to catch go unseen. withdrawn registry ↩