Analysis dataset snapshot record
================================

StatMedAnalysis | Original downloadable worksheet | 6 November 2026

Freeze an auditable dataset version while keeping later corrections traceable.

How to use this worksheet
Identify the exact extraction query, source cutoff and derivation version. Record row
and variable counts plus an integrity digest in the approved environment. Separate the
frozen analysis snapshot from ongoing source updates. Define how justified corrections
trigger a new version and rerun.

Save a working copy and keep the original blank version. Use public, hypothetical or
aggregate information only; do not enter patient identifiers, credentials or confidential
records. Keep source evidence in your approved project workspace. Mark unresolved text
fields UNKNOWN or NOT REPORTED with a reason; never substitute zero for an unknown count.

Project/version __________________  Prepared by role/date __________________

Working fields
1. Source system and cutoff
Response/evidence: _________________________________________________________
___________________________________________________________________________

2. Extraction query or job version
Response/evidence: _________________________________________________________
___________________________________________________________________________

3. Derived-variable code revision
Response/evidence: _________________________________________________________
___________________________________________________________________________

4. Aggregate row and variable counts
Response/evidence: _________________________________________________________
___________________________________________________________________________

5. Digest and approved location
Response/evidence: _________________________________________________________
___________________________________________________________________________

6. Freeze authority and date
Response/evidence: _________________________________________________________
___________________________________________________________________________

7. Correction request and impact
Response/evidence: _________________________________________________________
___________________________________________________________________________

8. Replacement version and rerun scope
Response/evidence: _________________________________________________________
___________________________________________________________________________

Hypothetical worked case
A fictional source database receives late corrections after the manuscript analysis.
Reusing the same filename hides the change; a new snapshot version links the correction
to rerun outputs and the revised report.

Decision rule and limitations
Call a snapshot frozen only when its inputs and derivation are identifiable and
protected from silent replacement. A checksum establishes byte identity, not scientific
correctness.

Decision _______________________  Remaining uncertainty ____________________
Next action ____________________  Owner / review date ______________________
Independent check and discrepancy resolution _______________________________

Official method or reporting reference checked 6 November 2026
https://sharing.nih.gov/data-management-and-sharing-policy/planning-and-budgeting-for-data-management-and-sharing/writing-a-data-management-and-sharing-plan

This is an original planning aid, not an official checklist, validated instrument,
clinical recommendation or certificate of expert approval. Apply the referenced
guidance to the specific design and record any additional requirements.