Overview of Recall Notices
You can capture recall notices from manufacturers, distributors, regulatory authorities, and third-party aggregators using any of the following methods:
- Manually through the user interface
- Oracle Content Curation Service
- Capture and Validate Recall Notices REST API
- Provider REST API (used exclusively by third-party aggregators)
Expansion Recall Notices
You can capture expansion recalls from various sources such as suppliers, regulatory authorities, and third-party aggregators, when there are subsequent updates to the recall notices that were already communicated.
When manufacturers identify additional affected lots or part numbers related to a previously issued recall, they issue a new expansion recall that supplements the original communication.
Review the expansion recalls associated with their parent recalls and take appropriate decisions to manage the containment tasks.
For example, if an initial recall notice includes a part with 5 lot numbers: lot 1, lot 2, lot 3, lot 4, and lot 5, and the manufacturer later discovers additional lots (lot 6, lot 7, and lot 8) affected for the same recall reason, they issue an expansion recall including those additional lots. Similarly, part numbers can be added or expanded in the recall.
When capturing an expansion recall, the parent recall number is recorded as the recall association number in the expansion recall for reference and traceability.
- Recall notices processed through the Oracle Recall Curation Service automatically include this association number for expansion recalls.
-
Likewise, third-party aggregators or integrations with other systems can use the REST API to include the recall association number to communicate expansion recalls.
- Additionally, you can manually create an expansion recall via the user interface by copying the parent recall notice and making the necessary incremental updates.