Product methodology
Recall Watch
Source contract, normalization path, entity-graph join, refresh posture, and publication limits for this Branmoor product.
Status
In service. This product has a functional preview or paid engagement surface in the current site. The full licensed product may still include private exports, alerts, APIs, or buyer-specific diligence that are not exposed publicly.
Distribution Scope
Nationwide; TN provider/vendor slice; Nashville facility exposure
Product Question
Monitors FDA recall events and affected manufacturers/products.
Primary Sources
- FDA Enforcement Reports API (openFDA) — Drug recalls with classification, reason, distribution scope
- FDA recall press releases — Narrative context, voluntary vs. mandatory framing
- openFDA NDC directory — Product identification and cross-reference with shortage data
Entity-Graph Join
`recall_id`, manufacturer name -> `irs_ein`/`frs_id`; exposure via `ccn`, `npi`, CBP/vendor joins.
Publication Rule
Branmoor does not treat raw public records as the product. A surface is publishable only when the source record is dated, normalized, source-linked, and joined to the relevant Branmoor entity identifiers with enough confidence to state the limits of the result.
Current Methodology Note
Severity classification follows FDA's own Class I/II/III taxonomy. Operational response language is templated and reviewed; the FDA primary source link is always present.
Limits
Coverage follows the underlying source. Missing state portals, gated APIs, PDF-only filings, suppressed fields, lagged agency refreshes, and entity-name ambiguity can all limit product completeness. Pending products are not marketed as live until those limits are documented on the product surface.