Reject Conflicting Ages

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: build one subject-level record carrying the collected age (AGE) and sex (SEX), one for each subject the collected demographics carry.

Input: collected demographics records carrying age (AGE) and sex (SEX), where a subject may be collected on more than one record.

Variables:

AGE would be the collected age, carried into the result unchanged.
SEX would be the collected sex, carried into the result unchanged.

Note: the subject decides how many records come out, so a subject collected twice is still one record and both collected records feed it. A value both records report the same way, or that only one of them reports, is one answer and carries without complaint. Two different ages are two answers to a question the record has one place for, so the run fails where the age is read and no artifact is accepted.

How to fix

Reconcile the two collected records and correct the governed demographics input so it holds one supported age for the subject. If both records are legitimate, declare which one answers, for example the one collected last, rather than leaving the choice to file order:

- name: AGE
  type: int
  derivation:
    source:
      variable: DM.AGE
      order_by: [DM.DMDTC]
      keep: last

The sample records carry no collection date (DMDTC here), so the source has to supply one first.

Do not reach for a row template to make the two records two rows. keys states one record per subject, so a second row for that subject would only move the same rejection to the output gate, as negative-output-duplicate shows.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: derivation
condition: multiple_values_per_key
requirement: REQ-0075

expected/error.yaml

phase: derivation
condition: multiple_values_per_key
spec_paths:
  - columns.AGE.derivation.source
requirement: REQ-0075
context:
  identifier: DM.AGE
  value_count: 2
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-102

YAML specification

1 spec file

spec.yaml

Edit33 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID]4input:5  DM: input/dm.csv67output:8  path: adsl.csv9  columns: [STUDYID, USUBJID, AGE, SEX]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: DM.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: DM.USUBJID2122  # A subject collected on two records is still one row. Its records hold23  # two different ages and nothing says which answers, so the run fails24  # here. SEX is the same on both records and carries through.25  - name: AGE26    type: int27    label: Age28    derivation: DM.AGE2930  - name: SEX31    type: str32    label: Sex33    derivation: DM.SEX

Inputs

Under review1 source file

input/dm.csv

Edit7 rows

input/dm.csv
STUDYID	AGE	SEX
YAMAA-01	64	F
YAMAA-01	58	M
YAMAA-01	59	M
YAMAA-01	72	F
YAMAA-01	72	F
YAMAA-01	45	M
YAMAA-01	—	M

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
ADSL	STUDYID	Study Identifier	character	Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character	Copy value from DM.USUBJID.	Predecessor
ADSL	AGE	Age	numeric	Copy value from DM.AGE.	Predecessor
ADSL	SEX	Sex	character	Copy value from DM.SEX.	Predecessor

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/dm.csv

Comments

Mapping spec