Dependency update impact assessment
===================================

StatMedAnalysis | Original downloadable worksheet | 6 November 2026

Test whether a package upgrade changes analysis behavior or outputs.

How to use this worksheet
Record the old and proposed versions and read the relevant release notes. Identify
affected functions, defaults and numerical routines. Rebuild the same synthetic fixtures
in controlled environments and compare substantive outputs. Classify differences before
accepting the upgrade.

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. Package and versions
Response/evidence: _________________________________________________________
___________________________________________________________________________

2. Relevant release-note change
Response/evidence: _________________________________________________________
___________________________________________________________________________

3. Functions used in project
Response/evidence: _________________________________________________________
___________________________________________________________________________

4. Controlled comparison environment
Response/evidence: _________________________________________________________
___________________________________________________________________________

5. Fixture outputs before and after
Response/evidence: _________________________________________________________
___________________________________________________________________________

6. Expected versus unexplained differences
Response/evidence: _________________________________________________________
___________________________________________________________________________

7. Required code/documentation changes
Response/evidence: _________________________________________________________
___________________________________________________________________________

8. Adoption decision and rollback version
Response/evidence: _________________________________________________________
___________________________________________________________________________

Hypothetical worked case
A fictional package changes its default handling of missing values. The script still
runs, but the analysis denominator differs; a successful installation is not sufficient
validation of the update.

Decision rule and limitations
Accept an upgrade only after material differences are explained and downstream outputs
are reconciled. Preserve the previous environment specification for reproducibility.

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

Official method or reporting reference checked 6 November 2026
https://docs.python.org/3/library/unittest.html

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.