Filovara
EN
WorkspaceScreen a plot free
GuidesWorkflow guide

Run a DDS technical preflight

Map confirmed facts to versioned DDS fields and surface missing or conflicting data.

A preflight is useful only when each output can be traced to confirmed facts, source references, and a mapping version. Missing information must remain visible instead of being filled by inference.

A practical preparation workflow

  1. 1

    Select confirmed case facts and the mapping version.

  2. 2

    Evaluate required fields deterministically.

  3. 3

    Resolve issues with new evidence and rerun explicitly.

What to check

  • Required field presence
  • Conflicting confirmed facts
  • Code confirmation needs
  • Source and mapping version
Keep this limitation visible

DDS Preflight is a technical check and does not guarantee TRACES or regulator acceptance.