Reject Study Datetime

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: build one record per subject carrying RFSTD, DTHDTM, and DTHDY.

Input: collected demographics rows carrying the treatment-start date (RFSTDT) and the collected moment of death (DTHDTC).

Variables:

RFSTD would hold the treatment-start date copied from the collected date.
DTHDTM would hold the moment of death, time of day included, copied from the collected moment, and would be blank when no death is recorded.
DTHDY would hold the study day of death, with the treatment-start date as day 1 and no day zero, and would be blank when no death is recorded.

A study day counts calendar dates, and a moment is not one: widening the moment into a date would choose silently between two adjacent days, so no reader may do so. The request is rejected before any data is read, and no artifact is accepted.

How to fix

Decide which calendar day the study reports, then state it as a date. When only the moment is collected, take its calendar date first and count the study day from that date:

- name: DTHDT
  type: date
  label: Date of Death
  derivation:
    to_date:
      source: DTHDTM

- name: DTHDY
  type: int
  label: Study Day of Death
  derivation:
    study_day:
      source: DTHDT
      reference: RFSTD

When the time of day carries meaning, a day count is the wrong result; keep the moment instead of forcing it into one.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: incompatible_input_type
rule: TIME-1

expected/error.yaml

phase: validation
condition: incompatible_input_type
spec_paths:
  - columns.DTHDY.derivation.study_day.source
rule: TIME-1
context:
  source: DTHDTM
  expected: date
  actual: datetime

YAML specification

1 spec file

spec.yaml

Edit42 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: {path: input/dm.csv, types: {RFSTDT: date, DTHDTC: datetime}}89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, RFSTD, DTHDTM, DTHDY]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: DM.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: DM.USUBJID2324  - name: RFSTD25    type: date26    label: Reference Start Date27    derivation: DM.RFSTDT2829  - name: DTHDTM30    type: datetime31    label: Moment of Death32    derivation: DM.DTHDTC3334  # The defect: a study day counts calendar dates, and DTHDTM is a35  # datetime, so the spec is rejected before any data is read.36  - name: DTHDY37    type: int38    label: Study Day of Death39    derivation:40      study_day:41        source: DTHDTM42        reference: RFSTD

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	RFSTDT	DTHDTC
PILOT7		2023-01-02	2023-05-14T18:30:00
PILOT7		2023-02-10	—

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	Computational Method	Origin
ADSL	STUDYID	Study Identifier	character		Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character		Copy value from DM.USUBJID.	Predecessor
ADSL	RFSTD	Reference Start Date	numeric	ISO 8601	Copy value from DM.RFSTDT.	Predecessor
ADSL	DTHDTM	Moment of Death	numeric	ISO 8601	Copy value from DM.DTHDTC.	Predecessor
ADSL	DTHDY	Study Day of Death	numeric		CDISC study day of DTHDTM against RFSTD as day 1; there is no day zero.	Derived

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