Reject Unknown Field

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 record per subject and treatment (EXTRT), carrying the total dose (DOSECUM) across the exposure records.

Input: subject-treatment records carrying treatment (EXTRT), and exposure records carrying treatment (EXTRT), sequence number (EXSEQ), and dose (EXDOSE).

Variables:

EXTRT would be the treatment name, carried over from the subject-treatment records.
DOSECUM would be the total dose across the subject's exposure records for that treatment.

Note: the list of exposure fields to be read as numbers also names a field the exposure file does not carry. Guessing which field was meant would total the wrong values, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Confirm which exposure column holds the dose. Here it is EXDOSE, which is already declared numeric, so remove the entry for EXDOSEN, which names no column of input/ex.csv:

input:
  TRT: input/subject_treatment.csv
  EX:
    path: input/ex.csv
    types:
      EXDOSE: float

Keep the EXDOSE entry: without it the dose is read as text and cannot be totalled.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: unknown_field
requirement: REQ-0532

expected/error.yaml

phase: validation
condition: unknown_field
spec_paths:
  - input.EX.types.EXDOSEN
requirement: REQ-0532
context:
  dataset: EX
  field: EXDOSEN

YAML specification

1 spec file

spec.yaml

Edit35 lines

1schema_version: "1.0"2domain: ADEX3keys: [STUDYID, USUBJID, EXTRT]4input:5  TRT: input/subject_treatment.csv6  # EXDOSEN is not a column of input/ex.csv, so the run is rejected7  # before any data is read.8  EX: {path: input/ex.csv, types: {EXDOSE: float, EXDOSEN: float}}9base: TRT1011output:12  path: adex.csv13  columns: [STUDYID, USUBJID, EXTRT, DOSECUM]1415columns:16  - name: STUDYID17    type: str18    label: Study Identifier19    derivation: TRT.STUDYID2021  - name: USUBJID22    type: str23    label: Unique Subject Identifier24    derivation: TRT.USUBJID2526  - name: EXTRT27    type: str28    label: Name of Treatment29    derivation: TRT.EXTRT3031  - name: DOSECUM32    type: float33    label: Cumulative Dose34    derivation:35      aggregate: "SUM(EX.EXDOSE)"

Inputs

Under review2 source files

input/ex.csv

Edit1 row

input/ex.csv
STUDYID	USUBJID	EXTRT	EXSEQ	EXDOSE
PILOT7		Carboplatin	1	300

input/subject_treatment.csv

Edit1 row

input/subject_treatment.csv
STUDYID	USUBJID	EXTRT
PILOT7		Carboplatin

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	DOSECUM	Cumulative Dose	numeric	Aggregate SUM(EX.EXDOSE).	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