Reject a Date and Time Written With a Space

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: derive the first treatment date/time (TRTSDTM) from collected exposure start text.

Input: exposure records carrying a collected start: a year and month, a date and time, or a date and time written with a space instead of T.

Variables:

TRTSDTM: the collected exposure start date/time, with any part of the time that was not collected taking its first value. A start collected to the year and month only gives no date/time, because no day is supplied. A start written with a space before its time is not ISO 8601 date or date/time text, so the run stops rather than guessing which part is the time.

How to fix

Correct the export upstream so the start uses ISO 8601 text, with T between the date and the time, such as 2025-01-15T09:30. If the study decides that such starts carry no usable date/time, state that decision explicitly:

impute:
  type: datetime
  source: EX.EXSTDTC
  time: first
  invalid: null

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: impute
condition: invalid_date_text
rule: TIME-13

expected/error.yaml

phase: impute
condition: invalid_date_text
spec_paths:
  - columns.TRTSDTM.derivation.impute
rule: TIME-13
context:
  source: EX.EXSTDTC
  value: "2025-01-15 09:30"
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      EXSEQ: 2

YAML specification

1 spec file

spec.yaml

Edit41 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID, EXSEQ]6input:7  EX: input/ex.csv89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, EXSEQ, TRTSDTM]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: EX.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: EX.USUBJID2324  - name: EXSEQ25    type: int26    label: Sequence Number27    derivation: EX.EXSEQ2829  # A collected date/time is kept and a complete date gets the first second30  # of its day; a start cut off before its day, such as 2025-01, gives no31  # date/time. No invalid handler is declared, so a start that is not ISO32  # 8601 date or date/time text, such as one written with a space before33  # its time, stops the run.34  - name: TRTSDTM35    type: datetime36    label: Datetime of First Exposure to Treatment37    derivation:38      impute:39        type: datetime40        source: EX.EXSTDTC41        time: first

Inputs

Under review1 source file

input/ex.csv

Edit3 rows

input/ex.csv
STUDYID	EXSEQ	EXSTDTC
YAMAA-01	1	2025-01
YAMAA-01	2	2025-01-15 09:30
YAMAA-01	1	2025-02-03T08:15

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 EX.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character		Copy value from EX.USUBJID.	Predecessor
ADSL	EXSEQ	Sequence Number	numeric		Copy value from EX.EXSEQ.	Predecessor
ADSL	TRTSDTM	Datetime of First Exposure to Treatment	numeric	ISO 8601	Impute incomplete datetime from EX.EXSTDTC, giving each time part the source lacks its earliest value; a source without a complete date gives blank; invalid text is an error.	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/ex.csv

Your review

Mapping spec