Evidence moves in one direction.
Approved public API
The endpoint and non-secret query are recorded.
Raw retained snapshot
The response is stored before transformation.
Schema and quality checks
Missing fields, duplicates, dates, and empty results are tested.
Normalization and review
A human gate is required where category judgment matters.
Processed artifact and manifest
Counts, files, hashes, limitations, and review state are linked.
Static publication
Only approved artifacts can supply public numeric claims.
Official sources, explicit roles.
Validation is not approval.
Automated checks confirm shape, file integrity, deterministic transforms, and claim lint. A company-role review still controls taxonomy choices, device category inclusion, and public interpretation. A pending manifest cannot provide a public chart or metric.
Files behind the public cases.
What the records cannot establish.
- Public report counts do not provide a product-use or treatment denominator.
- Record presence does not prove causality, prevalence, quality, safety, or effectiveness.
- Documentation requirements can change; ruleset sources require dated review.
- Ambiguous device identity joins remain unlinked rather than guessed.
Corrections remain visible.
A material data, method, source, or interpretation correction receives a dated changelog entry. The previous artifact stays identifiable by its manifest and hash when retention is legally and operationally appropriate.
No private intake in this release.
The public release does not collect patient records, facial or clinical images, diagnosis or treatment histories, payment-card data, private social-media data, or customer product exports.
Research and business intelligence only.
Latticepoint pages are not medical, treatment, legal, investment, or regulatory advice. Source organizations retain their own terms, licenses, and responsibility statements.