Reject Per-Record RDI

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: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
Inputs: Do they trigger the failure for the reason the summary gives?
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

EditUnder reviewWhat this benchmark means

README.md

Goal: derive cumulative dose (DOSECUM) and relative dose intensity (RDI) by subject and treatment.

Input: a subject-treatment inventory carrying the dose unit (EXDOSU), with component exposure records carrying the treatment (EXTRT), the administered dose (EXDOSE), and the planned dose (EXPLDOS) on each administration record.

Variables:

EXTRT names the treatment component, and EXDOSU is the unit that component is measured in.
DOSECUM is the total administered dose across the component's exposure records.
RDI is meant to be that total as a percentage of the planned dose. The planned dose is recorded on each administration record rather than once for the treatment, so dividing the total by it leaves open which record supplies the denominator, and that choice would decide the answer. The run is rejected before any data is read, and no artifact is accepted.

How to fix

First decide what the denominator means. If each exposure row carries its own planned administration, total both actual and planned dose:

derivation:
  aggregate:
    expr: >-
      100 * SUM(EX.EXDOSE) / NULLIF(SUM(EX.EXPLDOS), 0)

If the denominator is one treatment-level plan, store it once in the subject treatment source, bind it to a numeric column, and compute RDI from that column and DOSECUM. Do not select one exposure row arbitrarily.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: aggregate_identifier_not_grouped
requirement: REQ-0503

expected/error.yaml

phase: validation
condition: aggregate_identifier_not_grouped
spec_paths:
  - columns.RDI.derivation.aggregate.expr
requirement: REQ-0503
context:
  dataset: EX
  identifier: EX.EXPLDOS

YAML specification

1 spec file

spec.yaml

Edit50 lines

1schema_version: "1.0"2domain: ADEX3keys: [STUDYID, USUBJID, EXTRT]4input:5  TRT: input/subject_treatment.csv6  EX: {path: input/ex.csv, types: {EXDOSE: float, EXPLDOS: float}}7base: TRT89output:10  path: adex.csv11  columns: [STUDYID, USUBJID, EXTRT, EXDOSU, DOSECUM, RDI]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: TRT.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: TRT.USUBJID2324  - name: EXTRT25    type: str26    label: Name of Treatment27    derivation: TRT.EXTRT2829  - name: EXDOSU30    type: str31    label: Dose Units32    derivation: TRT.EXDOSU3334  - name: DOSECUM35    type: float36    label: Cumulative Dose37    derivation:38      aggregate:39        expr: "SUM(EX.EXDOSE)"4041  # EX.EXPLDOS stands outside any reduction. The plan is recorded on every42  # administration record, so nothing says which record's plan divides the43  # total, and the specification is rejected before any data is read.44  - name: RDI45    type: float46    label: Relative Dose Intensity47    derivation:48      aggregate:49        key: [STUDYID, USUBJID, EXTRT]50        expr: "100 * SUM(EX.EXDOSE) / EX.EXPLDOS"

Inputs

Under review2 source files

input/ex.csv

Edit5 rows

input/ex.csv
STUDYID	EXTRT	EXSEQ	EXDOSE	EXPLDOS
YAMAA-01	Pembrolizumab	1	200	200
YAMAA-01	Pembrolizumab	2	150	200
YAMAA-01	Pembrolizumab	3	150	150
YAMAA-01	Pemetrexed	4	500	500
YAMAA-01	Pembrolizumab	1	200	200

input/subject_treatment.csv

Edit3 rows

input/subject_treatment.csv
STUDYID	EXTRT	EXDOSU
YAMAA-01	Pembrolizumab	mg
YAMAA-01	Pemetrexed	mg/m2
YAMAA-01	Pembrolizumab	mg

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Dataset Name	Variable Name	Variable Label	Type	Computational Method	Origin
ADEX	STUDYID	Study Identifier	character	Copy value from TRT.STUDYID.	Predecessor
ADEX	USUBJID	Unique Subject Identifier	character	Copy value from TRT.USUBJID.	Predecessor
ADEX	EXTRT	Name of Treatment	character	Copy value from TRT.EXTRT.	Predecessor
ADEX	EXDOSU	Dose Units	character	Copy value from TRT.EXDOSU.	Predecessor
ADEX	DOSECUM	Cumulative Dose	numeric	Aggregate SUM(EX.EXDOSE) over records matching on the shared output keys.	Derived
ADEX	RDI	Relative Dose Intensity	numeric	Aggregate 100 * SUM(EX.EXDOSE) / EX.EXPLDOS over records matching on STUDYID, USUBJID and EXTRT.	Derived

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

How to fix

input/ex.csv

input/subject_treatment.csv

Comments

Mapping spec