Reject Trivial Filter

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: carry the planned arm (ARM) and the actual arm (ACTARM) for each subject.

Input: EDC output in long form, one row per collected item.

Variables:

ARM would be the planned arm as collected; Unassigned when none was collected.
ACTARM would be the actual arm, a copy of the planned arm, but the copy also states which collected rows to choose among. The planned arm is one value by then rather than a set of rows, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Decide whether the actual arm repeats a value the record already carries or reads the collected rows itself. Repeating the planned arm names it and nothing else:

- name: ACTARM
  type: str
  label: Description of Actual Arm
  derivation:
    source: ARM

When the actual arm is collected in its own right, read the rows that hold it, exactly as the planned arm does:

- name: ACTARM
  type: str
  label: Description of Actual Arm
  derivation:
    first_available:
      sources:
        - filter: ODM.ItemOID = 'IT.DM.ACTARM'
          variable: ODM.Value
      missing: Unassigned

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: prohibited_construct
requirement: REQ-0148

expected/error.yaml

phase: validation
condition: prohibited_construct
spec_paths:
  - columns.ACTARM.derivation.source.filter
requirement: REQ-0148
context:
  identifier: ARM

YAML specification

1 spec file

spec.yaml

Edit46 lines

1schema_version: "1.0"2domain: DM3keys: [STUDYID, USUBJID]45input:6  ODM: input/odm.csv78output:9  path: dm.csv10  columns: [DOMAIN, STUDYID, USUBJID, ARM, ACTARM]1112columns:13  - name: DOMAIN14    type: str15    label: Domain Abbreviation16    derivation: {literal: DM}1718  - name: STUDYID19    type: str20    label: Study Identifier21    derivation: ODM.StudyOID2223  - name: USUBJID24    type: str25    label: Unique Subject Identifier26    derivation: ODM.SubjectKey2728  - name: ARM29    type: str30    label: Description of Planned Arm31    derivation:32      first_available:33        sources:34          - filter: ODM.ItemOID = 'IT.DM.ARM'35            variable: ODM.Value36        missing: Unassigned3738  # ARM is an output column holding one value per subject, so the filter39  # has no records to choose among.40  - name: ACTARM41    type: str42    label: Description of Actual Arm43    derivation:44      source:45        filter: ODM.ItemOID = 'IT.DM.ARM'46        variable: ARM

Inputs

Under review1 source file

input/odm.csv

Edit4 rows

input/odm.csv
StudyOID	MetaDataVersionOID	SubjectKey	StudyEventOID	StudyEventRepeatKey	ItemGroupOID	ItemGroupRepeatKey	ItemOID	Value
STUDY01	MDV.1	001	SCREENING	1	IG.DM	1	IT.DM.SEX	Male
STUDY01	MDV.1	001	SCREENING	1	IG.DM	1	IT.DM.AGE	34
STUDY01	MDV.1	002	SCREENING	1	IG.DM	1	IT.DM.SEX	Female
STUDY01	MDV.1	002	SCREENING	1	IG.DM	1	IT.DM.AGE	28

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Variable Name	Variable Label	Type	Origin	Conversion Definition	Variable Type	Variable Order
DOMAIN	Domain Abbreviation	Char	Assigned	Set constant value "DM".	SDTM	1
STUDYID	Study Identifier	Char	Collected	Copy value from ODM.StudyOID.	SDTM	2
USUBJID	Unique Subject Identifier	Char	Collected	Copy value from ODM.SubjectKey.	SDTM	3
ARM	Description of Planned Arm	Char	Derived	First non-missing of ODM.Value where ODM.ItemOID = 'IT.DM.ARM'; all missing → "Unassigned".	SDTM	4
ACTARM	Description of Actual Arm	Char	Derived	Copy value from ARM where ODM.ItemOID = 'IT.DM.ARM'.	SDTM	5

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

Comments

Mapping spec