Reject an Analysis Date Submitted as Text

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: carry each subject's date of first dose (TRTSDT) onto the subject-level analysis dataset, with the metadata a data definition describes it by.

Input: collected demographics with the date of first exposure (RFXSTDT), one record per subject.

Variables:

TRTSDT would be the date of first exposure to treatment.

Note: the date is described for submission as an ISO 8601 date. An analysis dataset submits a date as the number of days since 1 January 1960, displayed as DATE9., so the declared type is one the analysis model does not submit a date as, and the run is rejected before any data is read; no artifact is accepted.

How to fix

Leave the submission type out: an analysis date is submitted as an integer with the DATE9. display, which the model supplies:

submission:
  core: Cond
  mandatory: false
  origins:
    - type: Predecessor
      description: DM.RFXSTDT

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: submission_data_type_not_admitted
rule: SUB-6

expected/error.yaml

phase: validation
condition: submission_data_type_not_admitted
spec_paths:
  - columns.TRTSDT.submission
rule: SUB-6
context:
  column: TRTSDT
  declared_type: date
  data_type: date
  model: ADaM

YAML specification

1 spec file

spec.yaml

Edit56 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: {path: input/dm.csv, types: {RFXSTDT: date}}89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, TRTSDT]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: DM.STUDYID18    submission:19      core: Req20      mandatory: true21      length: 822      origins:23        - type: Predecessor24          description: DM.STUDYID2526  - name: USUBJID27    type: str28    label: Unique Subject Identifier29    derivation: DM.USUBJID30    submission:31      core: Req32      mandatory: true33      length: 1234      origins:35        - type: Predecessor36          description: DM.USUBJID3738  # The first dose date, described for the data definition as an ISO 860139  # date rather than the number the analysis model submits.40  - name: TRTSDT41    type: date42    label: Date of First Exposure to Treatment43    derivation: DM.RFXSTDT44    submission:45      core: Cond46      mandatory: false47      data_type: date48      origins:49        - type: Predecessor50          description: DM.RFXSTDT5152submission:53  label: Subject-Level Analysis Dataset54  class: SUBJECT LEVEL ANALYSIS DATASET55  structure: One record per subject56  repeating: false

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	RFXSTDT
YAMAA-01		2026-05-04
YAMAA-01		2026-05-11

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Dataset Name	Variable Name	Variable Label	Type	Codelist/Controlled Terms	Core	Computational Method	Origin
ADSL	STUDYID	Study Identifier	character		Req	Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character		Req	Copy value from DM.USUBJID.	Predecessor
ADSL	TRTSDT	Date of First Exposure to Treatment	numeric	ISO 8601	Cond	Copy value from DM.RFXSTDT.	Predecessor

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

Your review

Mapping spec