Methodology

Project scope

The project tracks U.S. federal, state, district, and future territorial law and policy concerning genetic information, genomic data, biological samples, genetic testing, and related uses. Coverage is not comprehensive and expands through source review.

Inclusion criteria

A record must have an identifiable jurisdiction, authoritative source, record type, legal or policy status, and a direct connection to a controlled genetics or genomics topic. Candidate records remain outside the verified dataset until a human reviewer checks the primary source.

Exclusion criteria

The tracker excludes unsupported claims, duplicate records, secondary summaries presented as legal authority, and candidate changes that have not completed review. General privacy or health laws may be excluded until their application to genetic information is documented.

Source hierarchy

1. Enacted statutory text
2. Legislature or government bill page
3. Official regulation
4. Official agency guidance
5. Court opinion
6. Official government archive
7. Credible legal or policy secondary source
8. News reporting when necessary for context

NHGRI provenance

The complete NHGRI Genome Statute and Legislation Database is included in the combined Policy Records directory. Its original state, primary link, topic, status, and summary are preserved. Local topic mappings support search and do not establish legal equivalence.

These entries identify NHGRI as their source and display the retrieval timestamp. NHGRI’s source page was last updated February 8, 2024. Current legal decisions should always use the linked primary source.

Status vocabulary

All records use the NHGRI status vocabulary: Approved, Died, Enacted, Passed House, Passed Senate, Statute, Pending, and Introduced. Record type remains separate so statutes, regulations, policies, and legislation retain their substantive form.

Research and review process

1. Locate an official government source.
2. Determine the jurisdiction, record type, status, dates, and scope.
3. Draft a factual summary separately from plain-language interpretation.
4. Assign controlled topic tags and document uncertainty.
5. Run schema and controlled-vocabulary validation.
6. Complete human source and summary review before publication.

Uncertainty and absence

“No specific law identified” describes a dataset finding, not a definitive conclusion that no law exists. Legal coverage can depend on definitions, exceptions, effective dates, preemption, enforcement, and the facts of a particular situation.

Corrections and versioning

Corrections create a record-history entry and increment the record version when the substantive public record changes. Dataset releases will receive stable version identifiers. Future releases may be archived with checksums and a DOI.

Automation boundary

Future monitors may identify candidate changes from Congress.gov, the Federal Register, state legislatures, state codes, and agency notices. Automated systems must not rewrite legal summaries or publish legal conclusions without human review.