Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

  1. Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
  2. Inputs: Do they trigger the failure for the reason the summary gives?
  3. Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?

The other tabs beside Comments are background for assessment, not under review.

Summary

Lifecycle: reviewedEditUnder review
What this benchmark means
README.md

Goal: build STRAT1R from the values recorded at randomization and STRAT1 from the matching values collected independently at entry, and require the two combined values to agree.

Input: demographics entries, disease-history entries, and the strata recorded at randomization, linked by the study and subject identifiers shared across the three files.

Variables:

  • METSTATR: metastatic disease status recorded at randomization, copied from input METSTAT in the randomization file.
  • ECOG0R: baseline performance status on the Eastern Cooperative Oncology Group (ECOG) scale recorded at randomization, copied from input ECOG0 in the randomization file.
  • REGIONUSR: region recorded at randomization, copied from input REGIONUS in the randomization file.
  • METSTAT: metastatic disease status from the disease-history entries, copied from input METSTAT there.
  • ECOG0: baseline ECOG performance status from the demographics entries, copied from input ECOG0 there.
  • REGIONUS: region from the demographics entries, copied from input REGIONUS there.
  • STRAT1R: combined randomization strata, joining METSTATR, ECOG0R, and REGIONUSR with |.
  • STRAT1: combined independently collected strata, joining METSTAT, ECOG0, and REGIONUS with | in the same order.

The two combined values must agree for every subject; a single disagreement rejects the run, and no artifact is accepted.

Note: the expected file records the completed rows as presented to the check; the disagreement still rejects the run.

How to fix

Query the disagreement and correct whichever source is wrong. If both values are valid but serve different purposes, document which one governs the analysis and replace the equality check with that reconciliation policy. Do not silently prefer the randomization value or the independently collected value.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
verification
condition
assert_failed
requirement
REQ-0384
expected/error.yaml
phase: verification
condition: assert_failed
spec_paths:
  - verifications[1].assert
requirement: REQ-0384
context:
  verification_id: randomized-strata-agree
  failure_count: 1
  keys:
    - STUDYID: PILOT7
      USUBJID: P7-103

Inputs

Under review
3 source files

input/dm.csv

Edit
3 rows
input/dm.csv
STUDYIDUSUBJIDECOG0REGIONUS
PILOT7YUS
PILOT7NNON-US
PILOT7YUS

input/mh.csv

Edit
3 rows
input/mh.csv
STUDYIDUSUBJIDMETSTAT
PILOT7M0
PILOT7M1 NED
PILOT7M0

input/re.csv

Edit
3 rows
input/re.csv
STUDYIDUSUBJIDMETSTATECOG0REGIONUS
PILOT7M0YUS
PILOT7M1 NEDNNON-US
PILOT7M1 NEDYUS

Unexpected Output

Under review
3 rows presented to the failing check - not an accepted artifact

expected/adsl.csv

Edit
3 rows
expected/adsl.csv
STUDYIDUSUBJIDMETSTATRECOG0RREGIONUSRMETSTATECOG0REGIONUSSTRAT1RSTRAT1
PILOT7M0YUSM0YUSM0|Y|USM0|Y|US
PILOT7M1 NEDNNON-USM1 NEDNNON-USM1 NED|N|NON-USM1 NED|N|NON-US
PILOT7M1 NEDYUSM0YUSM1 NED|Y|USM0|Y|US
Shaded columns are derived— = missing value

Comments and assessment materials

Comments

Signed in with GitHub; saved in repository Discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADSLSTUDYIDStudy IdentifiercharacterCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLMETSTATRRandomization Metastatic Disease StatuscharacterCopy value from RE.METSTAT.Predecessor
ADSLECOG0RRandomization Baseline ECOG Performance StatuscharacterCopy value from RE.ECOG0.Predecessor
ADSLREGIONUSRRandomization United States RegioncharacterCopy value from RE.REGIONUS.Predecessor
ADSLMETSTATMetastatic Disease StatuscharacterCopy value from MH.METSTAT.Predecessor
ADSLECOG0Baseline ECOG Performance StatuscharacterCopy value from DM.ECOG0.Predecessor
ADSLREGIONUSUnited States RegioncharacterCopy value from DM.REGIONUS.Predecessor
ADSLSTRAT1RRandomization Stratification Factor 1characterFill the template "{METSTATR}|{ECOG0R}|{REGIONUSR}".Derived
ADSLSTRAT1Analysis Stratification Factor 1characterFill the template "{METSTAT}|{ECOG0}|{REGIONUS}".Derived
VersionDateAuthorDescriptionReviewerSign-off
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml