Analysis pipeline recovery plan =============================== StatMedAnalysis | Original downloadable worksheet | 6 November 2026 Resume interrupted computation without mixing incomplete and valid outputs. How to use this worksheet Map pipeline stages and identify which outputs can be reused safely. Define completion markers that are written only after validation. Simulate interruption using synthetic inputs, then test restart behavior. Keep partial files separate from published outputs and record the input version for each checkpoint. 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. Pipeline stage and dependencies Response/evidence: _________________________________________________________ ___________________________________________________________________________ 2. Validated completion condition Response/evidence: _________________________________________________________ ___________________________________________________________________________ 3. Checkpoint contents and input identity Response/evidence: _________________________________________________________ ___________________________________________________________________________ 4. Partial-output naming rule Response/evidence: _________________________________________________________ ___________________________________________________________________________ 5. Interruption test point Response/evidence: _________________________________________________________ ___________________________________________________________________________ 6. Restart command and observed behavior Response/evidence: _________________________________________________________ ___________________________________________________________________________ 7. Duplicate or skipped work check Response/evidence: _________________________________________________________ ___________________________________________________________________________ 8. Recovery decision and owner Response/evidence: _________________________________________________________ ___________________________________________________________________________ Hypothetical worked case A fictional job writes half a summary file before stopping. A restart that merely checks whether the filename exists would accept an incomplete output; completion needs a validated marker or atomic replacement. Decision rule and limitations Resume only from checkpoints whose inputs and completion state are verified. File existence alone is not evidence that a stage finished correctly. 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/os.html#os.replace 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.