Who this is for

  • Clinical Operations leaders planning Phase II or Phase III CKD / DKD programs
  • Clinical Development leaders accountable for endpoint interpretability
  • QA / GCP / inspection-readiness stakeholders
  • Teams using central and local lab models
  • Teams planning global, chronic-care, retention-sensitive renal studies

Who this is for

This pack includes templates and controls intended to be adapted and adopted in protocol governance; study-specific thresholds must be confirmed before first participant screening.

What is inside the pack

  1. Practical 3-Pillar QbD Defense for CKD / DKD trials
  2. Red/yellow protocol audit excerpt
  3. The no silent thresholds rule
  4. Worked Objective → Trigger → Action → Evidence control-loop example
  5. Renal endpoint reconciliation example
  6. SAP Log / endpoint-defensibility example
  7. Starter list of Draft 0.5 issues that create later rework and inspection vulnerability


Renal Endpoint Integrity: Provable Data by Design

  • Explicit source-of-truth rules for eGFR, serum creatinine, and UACR
  • Central vs local lab data remain governed by a prespecified hierarchy
  • Repeat / reassessment values are classified under protocol-defined rules
  • Acute kidney event reassessment must not create silent endpoint substitution
  • Laboratory / vendor evidence must show:
    • chain-of-custody
    • transfer validation
    • reconciliation logic
    • incident / CAPA governance

Endpoint Defensibility: Operational Evidence That Supports the SAP

  • Protocol ↔ SAP ↔ DMP/CMP alignment before screening
  • Explicit handling of:
    • discontinuation
    • treatment interruption / restart
    • background therapy change
    • acute kidney events
    • protocol-driven reassessment
    • missed key eGFR visits
    • missed key UACR visits
    • temporary lab / hybrid execution gaps
  • Controlled SAP Log governance
  • Source-of-truth rules:
    • eGFR primary hierarchy
    • UACR primary hierarchy
    • supportive local data remain supportive unless explicitly endpoint-defining
  • Analysis-impacting events must leave an evidence trail, not just an email trail