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: Would a real study need this derivation, specified this way? Does it follow CDISC ADaM: variable names, controlled terms, record structure? Flag any rule that is ambiguous or that a sponsor would handle differently.
  2. Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
  3. Expected output: Would independent QC programming reproduce every value from these inputs and rules?

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

Summary

Lifecycle: finalizedEditUnder review
What this benchmark means
README.md

Goal: show how each source reference resolves: a qualified name reads its named dataset, and a bare name reads the output columns.

Input: one spec.yaml declaring two datasets. VS carries the vital-signs records that drive the output rows: subject (USUBJID), sequence (VSSEQ), test (VSTESTCD), result (VSSTRESN), and units (VSSTRESU). In this example, each subject's sequence starts at 1. DM carries one row per subject with sex, age, and race.

Bindings:

  • VS.USUBJID, VS.VSSEQ, VS.VSTESTCD, VS.VSSTRESN, and VS.VSSTRESU read the current vital-signs record straight through; the sequence restarts at 1 for each subject and survives into ADVS as ASEQ, a key beside the subject;
  • DM.SEX, DM.AGE, and DM.RACE reach the demographics dataset through the shared subject key, and a missing race stays blank;
  • AGEGR1 groups the already-derived AGE into <65 and >=65; the bare name binds to the output column, never to a source dataset.

Note: a qualified reference always names the dataset it reads, so DM and VS may carry same-named variables without colliding; a bare name always addresses the output columns, so one column can build on an earlier column.

Inputs

Under review
2 source files

input/dm.csv

Edit
3 rows
input/dm.csv
USUBJIDSEXAGERACE
M42WHITE
F67—
M55ASIAN

input/vs.csv

Edit
5 rows
input/vs.csv
USUBJIDVSTESTCDVSSEQVSSTRESNVSSTRESU
SYSBP1120mmHg
DIABP280mmHg
SYSBP1138mmHg
SYSBP1110mmHg
DIABP270mmHg

Expected output

Under review
5 expected rows

expected/advs.csv

Edit
5 rows
expected/advs.csv
USUBJIDASEQVSTESTCDSEXAGEAGEGR1RACEVSSTRESNVSSTRESU
1SYSBPM42<65WHITE120mmHg
2DIABPM42<65WHITE80mmHg
1SYSBPF67>=65—138mmHg
1SYSBPM55<65ASIAN110mmHg
2DIABPM55<65ASIAN70mmHg
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
ADVSUSUBJIDUnique Subject IdentifiercharacterCopy value from VS.USUBJID.Predecessor
ADVSASEQAnalysis Sequence NumbernumericCopy value from VS.VSSEQ.Predecessor
ADVSVSTESTCDVital Signs Test Short NamecharacterCopy value from VS.VSTESTCD.Predecessor
ADVSSEXSexcharacterCopy value from DM.SEX.Predecessor
ADVSAGEAgenumericCopy value from DM.AGE.Predecessor
ADVSAGEGR1Pooled Age Group 1characterBand AGE at 65 into "<65" and ">=65", intervals closed on the left.Derived
ADVSRACERacecharacterCopy value from DM.RACE.Predecessor
ADVSVSSTRESNNumeric Result in Standard UnitsnumericCopy value from VS.VSSTRESN.Predecessor
ADVSVSSTRESUStandard UnitscharacterCopy value from VS.VSSTRESU.Predecessor
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

yamaa code

Runs the yamaa specification; its result must match the expected output

run.R

Edit
4 lines
library(yamaa)advs <- yamaa_domain("spec.yaml")$outputadvs

run.py

Edit
4 lines
import yamaaadvs = yamaa.yamaa_domain("spec.yaml").outputadvs