Reject Date-Text Comparison

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 REVIEWFL to mark adverse events (AEs) starting on or after 2025-01-01.

Input: collected adverse events carrying AESTDTC (event start date).

Variables:

REVIEWFL would be Y when the event start date is on or after 2025-01-01, and N otherwise, including when no start date was collected.

Note: the cutoff is written as text rather than as a calendar date, and a date cannot be compared with text, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Declare the constant as a date so both operands carry the same temporal type:

derivation:
  flag:
    condition: "ASTDT >= DATE '2025-01-01'"
    false_value: "N"
    missing: "N"

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: incompatible_input_type
requirement: REQ-0190

expected/error.yaml

phase: validation
condition: incompatible_input_type
spec_paths:
  - columns.REVIEWFL.derivation.flag.condition
requirement: REQ-0190
context:
  left_type: date
  right_type: str

YAML specification

1 spec file

spec.yaml

Edit41 lines

1schema_version: "1.0"2domain: ADAE3keys: [STUDYID, USUBJID, AESEQ]4input:5  AE:6    path: input/ae.csv7    types: {AESEQ: int, AESTDTC: date}89output: {path: adae.csv, columns: [STUDYID, USUBJID, AESEQ, REVIEWFL]}1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: AE.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: AE.USUBJID2122  - name: AESEQ23    type: int24    label: Sequence Number25    derivation: AE.AESEQ2627  - name: ASTDT28    type: date29    label: Analysis Start Date30    derivation: AE.AESTDTC3132  # Intentionally invalid: '2025-01-01' is text, not a date, and a date33  # cannot be compared with text.34  - name: REVIEWFL35    type: str36    label: Protocol Review Flag37    derivation:38      flag:39        condition: "ASTDT >= '2025-01-01'"40        false_value: "N"41        missing: "N"

Inputs

Under review1 source file

input/ae.csv

Edit1 row

input/ae.csv
STUDYID	USUBJID	AESEQ	AESTDTC
PILOT7		1	2025-01-15

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
ADAE	STUDYID	Study Identifier	character	Copy value from AE.STUDYID.	Predecessor
ADAE	USUBJID	Unique Subject Identifier	character	Copy value from AE.USUBJID.	Predecessor
ADAE	AESEQ	Sequence Number	numeric	Copy value from AE.AESEQ.	Predecessor
ADAE	REVIEWFL	Protocol Review Flag	character	"Y" when ASTDT >= '2025-01-01'; "N" otherwise; "N" when the condition is unknown.	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/ae.csv

Comments

Mapping spec