Reject Datetime Precision of a Zoned Date and Time

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: report how much of the first treatment start (TRTSTPR) was collected.

Input: exposure records carrying a collected start: a year and month, a date and time to the second, or a date and time carrying a time zone.

Variables:

TRTSTPR: month for a start collected to the year and month, and second for a start collected to the second; a start collected to the day, hour or minute gives day, hour or minute. A start carrying a time zone is not a local date and time, so the run stops rather than reporting a precision for it.

How to fix

Correct the export upstream so the start is local ISO 8601 text without a zone, such as 2025-01-15T09:30:00, after any conversion the study defines. If the study decides that such starts have no usable precision, state that decision explicitly:

precision:
  type: datetime
  source: EX.EXSTDTC
  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.TRTSTPR.derivation.precision
rule: TIME-13
context:
  source: EX.EXSTDTC
  value: "2025-01-15T09:30:00Z"
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      EXSEQ: 3

YAML specification

1 spec file

spec.yaml

Edit39 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, TRTSTPR]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  # How much of a date and time the collected start carries: year, month,30  # day, hour, minute or second. No invalid handler is declared, so a start31  # that is not ISO 8601 date or date/time text, such as one carrying a32  # time zone, stops the run.33  - name: TRTSTPR34    type: str35    label: First Exposure Date/Time Collected Precision36    derivation:37      precision:38        type: datetime39        source: EX.EXSTDTC

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-15T09:30:00
YAMAA-01	3	2025-01-15T09:30:00Z

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	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	TRTSTPR	First Exposure Date/Time Collected Precision	character	Collected datetime precision of EX.EXSTDTC: "second" through the second, "minute" through the minute, "hour" through the hour, "day" for a date alone, "month" for a year and month, "year" for a year alone, "none" for an entirely imputed datetime or text with an unknown year; 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