Reports you receive
What a de-identification report contains, and when you get it.
Every dataset ships with a de-identification report. It says exactly what was removed, how, and how the result was checked, so a lab's legal and security teams can review it before signing.
- Method and versionPipeline name, version and configuration hash; where it ran.
- Entity types removedEach entity type, the rule that found it and how it was replaced.
- Sample-based QASample size and how it was drawn, findings from human review and scans.
- Residual-risk assessmentThe method used and its conclusion for this dataset.
- Sign-offWho approved release for Quarry and for the owner, and when.
What it contains
| Section | Contents |
|---|---|
| Method and version | Pipeline name and version (matching deid_method in the manifest), configuration, and where it ran |
| Entity types removed | Each type removed, how it was detected, and how it was replaced |
| Sample-based QA | Sample size and how it was drawn; findings from human review and automated scans; what was fixed |
| Residual-risk assessment | Method, quasi-identifiers considered, generalisation applied, conclusion |
| Sign-off | Approval for release by Quarry and by the owner, with dates |
When you get it
- Before an NDA: the deal sheet says the report exists and which method was used.
- Under the sample NDA: the report for the sample.
- On delivery: the full report for the licensed dataset, as
deid-report.pdfin the delivery.
Reports are versioned with the dataset: a re-delivery after a fix comes with a new report.