Incomplete data processing

If the software processes only part of the relevant data — for example because a configuration setting excludes a source, or a step in the pipeline is skipped — downstream documentation may be based on an incomplete picture. In regulatory work, an incomplete dataset can be as misleading as an incorrect one.

Hazardous situation: Regulatory submissions are produced based on incomplete data because the software did not process all relevant inputs.

• Transparent search configuration. The configuration that drives each search is reviewable and editable; see Search configuration space and Searches List Page.
• Result-list transparency. Every result is visible in the Results list page before export, with sorting and filtering — see Can I sort and filter the results?.
• Integration coverage. The integration details for each connected source are documented so you can confirm what the search actually covers; see From Manual to Automated: Flinn's Search Advantage Explained.
• Cross-check critical evaluations. For high-stakes work, cross-check against the source database — see Why do I find different results when I compare the official database and Flinn?.
• Quality-check exports. Before relying on an exported file, verify it matches what is shown on screen. See Export a Search, The export function doesn't work for me and I would like to export additional data from the reports.

See also Synchronization issues with external database and External database downtime for cases where the upstream source is the limiting factor.