Stored FDA snapshot
Snapshot date: .
This date is inherited from the repository's existing dataset declaration. Recording file identities did not independently reverify or refresh the FDA corpus.
File identities recorded: . This later bookkeeping date is not a new snapshot or field-review date. Read the FDA source and its limitations.
Recorded dataset file identities
- data/fda-ai-enabled-devices.csv
773066fcedd1b166549638fc86c6517ce82311f40692e0749df8f34ce61600de- data/radiology-ai-directory.csv
101a351c985d572d033d34efca2e45891872e3ec652e7a56dbed0dcae49fd495
These hashes identify the repository files. They are not FDA attestations.
Field and guide source reviews
Profiles retain their individual source, scope and review dates. A later guide review checks only the guide's cited context; it does not refresh every linked product fact.
- How to evaluate lung CT AI: agent source review .
- Mammography AI: workflow and IT checks: agent source review .
- MRI reconstruction AI: purchasing checks: agent source review .
- Radiology AI pricing and total cost of ownership: agent source review .
Commercial availability and installed releases
The snapshot does not establish that a product is currently sold, a particular version is installed, or a licensed module is included. Check the exact current offer with the supplier. Family maps and system baselines preserve their own scope and unknowns.
Maintenance process
- Record a dated source acquisition and inspect changes to submission identity and decision context.
- Review affected facts, guide wording, families and compatibility conclusions against their own sources. Changed support requires a new review; dates are not automatically advanced.
- Record the dataset file identities, run the validation gates and qualify the exact candidate before publication.
Submit a source-backed correction with the exact FDA number, version, affected statement and supporting link. Read the editorial standards.