Row Templates

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.

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.
Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
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

EditUnder reviewWhat this benchmark means

README.md

Goal: build output rows from input records and groups with the three row-template shapes: record-driven templates with input filters, a case split across several templates, and a grouped template whose own filter decides each candidate row.

Input: one spec.yaml over LB, which carries one record per lab test per visit: subject, visit number, test code, and result, with the tests interleaved in the file. A result may be missing.

Templates:

alt makes one ALT row per ALT record that has a result, writing the result as the analysis value (AVAL) and leaving DTYPE blank. Its filter reads the input record, so a record with a missing result is dropped before any row is built.
ast does the same for AST. Every ALT row comes before every AST row even though the input interleaves the tests: templates are sections of the output and concatenate in specification order.
visit_total builds one candidate TOTAL row per subject and visit, in the order each pair first appears in the input, with AVAL the sum of that visit's results, skipping missing ones. Its filter reads the finished candidate and keeps it only when the total exceeds 100, with DTYPE set to CALCULATION. A visit whose results are all missing sums to missing, which is neither above 100 nor not, so its candidate is dropped too.

Shared columns: the study identifier, subject, and visit number are the same for every template, so they are stated once at column level. The subject and visit read the input record on the record-driven templates and the group keys on the grouped template.

YAML specification

1 spec file

spec.yaml

Edit86 lines

1schema_version: "1.0"2domain: ADLB3keys: [USUBJID, VISIT, PARAMCD]4input:5  LB: {path: input/lb.csv, types: {LBSTRESN: float}}6base: LB78output:9  path: adlb.csv10  columns: [STUDYID, USUBJID, VISIT, PARAMCD, PARAM, AVAL, DTYPE]1112columns:13  # Uniform derivations shared by every row template live at column14  # level. USUBJID and VISIT are group keys of the grouped template, so15  # the qualified source reads resolve from the group; on the16  # record-driven templates they read the retained input record.17  - name: STUDYID18    type: str19    label: Study Identifier20    derivation: {literal: YAMAA-01}2122  - name: USUBJID23    type: str24    label: Unique Subject Identifier25    derivation: LB.USUBJID2627  - name: VISIT28    type: int29    label: Visit Number30    derivation: LB.VISIT3132  - name: PARAMCD33    type: str34    label: Parameter Code3536  - name: PARAM37    type: str38    label: Parameter3940  - name: AVAL41    type: float42    label: Analysis Value4344  - name: DTYPE45    type: str46    label: Derivation Type4748rows:49  # Case split, first section: every collected ALT record becomes one50  # row. The filter reads the input record before any row derivation,51  # so a record with a missing result is dropped here, never derived.52  - id: alt53    filter: "LB.LBTESTCD = 'ALT' AND LB.LBSTRESN IS NOT NULL"54    derivations:55      PARAMCD: {literal: ALT}56      PARAM: {literal: Alanine Aminotransferase}57      AVAL: LB.LBSTRESN58      DTYPE: {literal: null}5960  # Case split, second section: the AST records follow all ALT rows in61  # the output, even though the input interleaves the two tests. Row62  # templates concatenate in specification order.63  - id: ast64    filter: "LB.LBTESTCD = 'AST' AND LB.LBSTRESN IS NOT NULL"65    derivations:66      PARAMCD: {literal: AST}67      PARAM: {literal: Aspartate Aminotransferase}68      AVAL: LB.LBSTRESN69      DTYPE: {literal: null}7071  # Grouped template: one candidate row per subject-visit in first72  # appearance order, totaling every test of the visit (SUM skips missing73  # results). The filter reads the completed candidate's unqualified74  # columns after the group reduction: a total failing the comparison is75  # FALSE and suppressed, while a visit whose results are all missing76  # reduces to missing, which is UNKNOWN and suppressed.77  - id: visit_total78    group_by: [LB.USUBJID, LB.VISIT]79    filter: "AVAL > 100"80    derivations:81      PARAMCD: {literal: TOTAL}82      PARAM: {literal: Total of Components}83      AVAL:84        aggregate:85          expr: "SUM(LB.LBSTRESN)"86      DTYPE: {literal: CALCULATION}

Inputs

Under review1 source file

input/lb.csv

Edit9 rows

input/lb.csv
VISIT	LBTESTCD	LBSTRESN
1	ALT	40
1	AST	30
2	ALT	50
2	AST	45
1	ALT	60
1	AST	55
2	ALT	—
2	AST	—
1	ALT	30

Expected output

Under review8 expected rows

expected/adlb.csv

Edit8 rows

expected/adlb.csv
STUDYID	VISIT	PARAMCD	PARAM	AVAL	DTYPE
YAMAA-01	1	ALT	Alanine Aminotransferase	40	—
YAMAA-01	2	ALT	Alanine Aminotransferase	50	—
YAMAA-01	1	ALT	Alanine Aminotransferase	60	—
YAMAA-01	1	ALT	Alanine Aminotransferase	30	—
YAMAA-01	1	AST	Aspartate Aminotransferase	30	—
YAMAA-01	2	AST	Aspartate Aminotransferase	45	—
YAMAA-01	1	AST	Aspartate Aminotransferase	55	—
YAMAA-01	1	TOTAL	Total of Components	115	CALCULATION

Shaded columns are derived— = missing value

Comments and assessment materials

Dataset Name	Variable Name	Variable Label	Type	Computational Method	Origin
ADLB	STUDYID	Study Identifier	character	Set constant value "YAMAA-01".	Assigned
ADLB	USUBJID	Unique Subject Identifier	character	Copy value from LB.USUBJID.	Predecessor
ADLB	VISIT	Visit Number	numeric	Copy value from LB.VISIT.	Predecessor
ADLB	PARAMCD	Parameter Code	character	Set per constructed row; see the Row construction sheet.	Derived
ADLB	PARAM	Parameter	character	Set per constructed row; see the Row construction sheet.	Derived
ADLB	AVAL	Analysis Value	numeric	Set per constructed row; see the Row construction sheet.	Derived
ADLB	DTYPE	Derivation Type	character	Set per constructed row; see the Row construction sheet.	Derived

Template	Include when	PARAMCD	PARAM	AVAL	DTYPE
alt	LB.LBTESTCD = 'ALT' AND LB.LBSTRESN IS NOT NULL	Constant "ALT"	Constant "Alanine Aminotransferase"	Copy LB.LBSTRESN	Constant "None"
ast	LB.LBTESTCD = 'AST' AND LB.LBSTRESN IS NOT NULL	Constant "AST"	Constant "Aspartate Aminotransferase"	Copy LB.LBSTRESN	Constant "None"
visit_total	AVAL > 100	Constant "TOTAL"	Constant "Total of Components"	Aggregate SUM(LB.LBSTRESN) over records matching on the shared output keys	Constant "CALCULATION"

Version	Date	Author	Description
1.3	2026-09-29	yamaa docs build	Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.2	2026-09-29	yamaa docs build	Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.1	2026-09-29	yamaa docs build	Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0		yamaa docs build	Initial generation from spec.yaml

run.R

Edit4 lines

1library(yamaa)23adlb <- yamaa_domain("spec.yaml")$output4adlb

run.py

Edit4 lines

1import yamaa23adlb = yamaa.yamaa_domain("spec.yaml").output4adlb

input/lb.csv

expected/adlb.csv

Comments

Mapping spec

yamaa code

run.R

run.py