A four-phase, modular methodology for independent analytical verification and Independent Result Reconstruction (IRR) across biomedical, clinical, and healthcare analytics domains. Every engagement is pre-specified, version-tracked, and independently reproducible and analytically verifiable under defined conditions.
Four-phase pipeline
How every engagement proceeds
The same four phases apply across all three domains. Domain-specific verification procedures are applied within each phase.
Phase 01
Data Provenance & Transformation Review
Evaluates the lineage and transformation pathway from source data to reported outputs. Covers normalization procedures, batch correction documentation, gating strategy definitions, endpoint derivation files, censoring rule implementations, SAP alignment, ETL logic, look-back window specifications, and crosswalk file versioning.
→ provenance-trace.pdf · transformation-log.json
Phase 02
Statistical & Methodological Assessment
Evaluates alignment between the declared analytical methodology and the structure of the underlying data. Each analytical component is assigned to an IRR class within the RIQA taxonomy. An IRR Methodology Declaration is issued specifying the verification standard to be applied in Phase 03.
Results are reconstructed from source data and documented analytical procedures. For exact and near-deterministic methods, numerical reconstruction is performed. A sensitivity analysis is separately performed to evaluate conclusion stability under reasonable alternate assumptions.
→ irr-findings.csv · sensitivity-analysis.json
Phase 04
Structured QA Reporting
Generates structured QA reports including findings registers, integrity scoring summaries, and machine-readable provenance artifacts. SHA-256 hashes of all input files are recorded in the audit trail. Every finding traces to a specific catalog entry.
Correct methodological implementation verified; seed and version documentation required.
Architectural verification
ML pipelines, CMS-HCC models, federated systems
Logic consistency, population construction, and specification-to-implementation alignment.
Anchor standards
Standards alignment
RIQA's provenance requirements are anchored to established community standards. RIQA goes beyond checklist compliance to provide independent quantitative reconstruction.
MIQE 2.0 — Minimum Information for qPCR Experiments
Bustin et al. 2025, Clin Chem 71:634. RIQA-qPCR Livak v1.1 provenance catalog is structured along MIQE 2.0 sections with severity assignments consistent with the essential/desirable distinction.
MIFlowCyt — Minimum Information about a Flow Cytometry Experiment
Lee et al. 2008, Cytometry A 73A:926. RIQA-Flow Herzenberg v1.1 provenance layer is anchored to MIFlowCyt, covering panel, gating tree, compensation, FMO controls, and viability declarations.
ICH E9(R1) — Estimands and Sensitivity Analysis
The RIQA sensitivity analysis framework for clinical trials aligns with ICH E9(R1) estimand principles, evaluating conclusion stability under alternate analytical assumptions.
RIQA QA outputs include machine-readable JSON artifacts structured for downstream integration, consistent with FAIR data principles for research provenance infrastructure.
Research-use and scope of findings
RIQA provides analytical assurance for research and quality-review purposes. RIQA does not function as a regulatory authority, certifying body, or legal compliance organization. Findings are reproducibility and methodological consistency statements derived from submitted data and declared methodology — not determinations of scientific truth, biological validity, or regulatory compliance.
Download the RIQA White Paper
Full framework documentation · RIQA-WP-001 · 2026 · Open Access CC BY-NC 4.0