Reject a Diary Selection Checked Against Another Dataset's Date

Review ask

As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. Agreeing with both approves this benchmark; disagreeing with either needs a comment. Propose a fix with the Edit button on any source file, or add it to your comments.

We suggest spending no more than 5 minutes on a review. The other tabs beside Your review are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: keep the diary entries of randomized subjects, with the entry date in QSDTC and the diary score in QSSTRESN.

Input: diary entries carrying the entry date (DIARYDT) and score (SCORE), a randomization list carrying each subject's randomization date (RANDDT) and arm (ARM), and demographics carrying each subject's reference start date (RFSTDTC).

Variables:

QSDTC would be the diary entry date.
QSSTRESN would be the diary score.

Note: an entry is kept when the subject was randomized on or before a date, and that date is taken from the demographics records. The diary entries, not the demographics records, build the rows, so an entry has no demographics record of its own to compare with. The run is rejected before any data is read and no artifact is accepted.

How to fix

Compare the randomization date with a date of the diary entry itself, here the entry date:

intermediates:
  - id: RANDOMIZED
    dataset: RAND
    key: [USUBJID]
    filter: "RAND.RANDDT <= DIARY.DIARYDT"

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: unknown_field
rule: LOOKUP-7

expected/error.yaml

phase: validation
condition: unknown_field
spec_paths:
  - intermediates.RANDOMIZED.filter
rule: LOOKUP-7
context:
  identifier: DM.RFSTDTC
  intermediate: RANDOMIZED

YAML specification

1 spec file

spec.yaml

Edit46 lines

1yamaa: "1.0"2type: spec3model: SDTM4domain: QS5keys: [USUBJID, QSDTC]6input:7  DIARY: {path: input/diary.csv, types: {DIARYDT: date, SCORE: int}}8  RAND: {path: input/rand.csv, types: {RANDDT: date}}9  DM: {path: input/dm.csv, types: {RFSTDTC: date}}1011output:12  path: qs.csv13  columns: [USUBJID, QSDTC, QSSTRESN]1415intermediates:16  # The subject's randomization, when it happened on or before the17  # subject's reference start date. That date belongs to demographics,18  # which does not build the rows, so the specification is rejected before19  # any data is read.20  - id: RANDOMIZED21    dataset: RAND22    key: [USUBJID]23    filter: "RAND.RANDDT <= DM.RFSTDTC"2425columns:26  - name: USUBJID27    type: str28    label: Unique Subject Identifier2930  - name: QSDTC31    type: date32    label: Date/Time of Finding3334  - name: QSSTRESN35    type: int36    label: Numeric Finding in Standard Units3738rows:39  # One record per diary entry of a randomized subject.40  - id: diary41    dataset: DIARY42    filter: "RANDOMIZED.ARM IS NOT NULL"43    derivations:44      USUBJID: DIARY.USUBJID45      QSDTC: DIARY.DIARYDT46      QSSTRESN: DIARY.SCORE

Inputs

Under review3 source files

input/diary.csv

Edit3 rows

input/diary.csv
USUBJID	DIARYDT	SCORE
	2024-04-02	3
	2024-04-09	2
	2024-04-03	4

input/dm.csv

Edit2 rows

input/dm.csv
USUBJID	RFSTDTC
	2024-04-01
	2024-04-05

input/rand.csv

Edit2 rows

input/rand.csv
USUBJID	RANDDT	ARM
	2024-04-01	Drug A
	2024-04-05	Placebo

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Variable Name	Variable Label	Type	Controlled Terms or Format	Origin	Conversion Definition	Variable Type	Variable Order
USUBJID	Unique Subject Identifier	Char		Derived	Set per constructed row; see the Row construction sheet.	SDTM	1
QSDTC	Date/Time of Finding	Char	ISO 8601	Derived	Set per constructed row; see the Row construction sheet.	SDTM	2
QSSTRESN	Numeric Finding in Standard Units	Num		Derived	Set per constructed row; see the Row construction sheet.	SDTM	3

Template	Include when	USUBJID	QSDTC	QSSTRESN
diary	RANDOMIZED.ARM IS NOT NULL	Copy DIARY.USUBJID	Copy DIARY.DIARYDT	Copy DIARY.SCORE

Version	Date	Author	Description
1.7	2026-10-20	yamaa docs build	Read a specification in the 1.0 surface as its 0.5 counterpart; state that missing values stay missing where a mapping declares no missing handler, and leave out a declared missing answer that restates a handler's default
1.6	2026-10-17	yamaa docs build	Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.5	2026-10-17	yamaa docs build	Name collected precision in words instead of letter codes; state imputation fallbacks, minimum source precision, bounds ignored outside the collected period, and invalid text with no handler as an error; describe date and datetime shifts, imputation flag codes, and partial text giving no date part
1.4	2026-10-15	yamaa docs build	State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
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/diary.csv

input/dm.csv

input/rand.csv

Your review

Mapping spec