Reject Datetime Precision from a Partial Date

Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
Inputs: Do they trigger the failure for the reason the summary gives?
Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?

The other tabs beside Comments are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

Goal: report whether the first treatment start (TRTSTPR) included a collected time.

Input: exposure records carrying a collected start date or date/time.

Variables:

TRTSTPR: S when the exposure start included a time and D when it was a complete date with no time. A start collected to the year and month only is neither a complete date nor a moment, so it cannot answer whether only the time is absent; the run stops rather than reporting a misleading precision.

How to fix

Recover the exposure day upstream when it was collected. If a date-imputation policy applies, complete the date separately before asking datetime_precision whether the resulting source carried a time.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: impute
condition: invalid_datetime_text
requirement: REQ-1183

expected/error.yaml

phase: impute
condition: invalid_datetime_text
spec_paths:
  - columns.TRTSTPR.derivation.datetime_precision
requirement: REQ-1183
context:
  source: EX.EXSTDTC
  value: 2025-01
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      EXSEQ: 1

YAML specification

1 spec file

spec.yaml

Edit35 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID, EXSEQ]4input:5  EX: input/ex.csv67output:8  path: adsl.csv9  columns: [STUDYID, USUBJID, EXSEQ, TRTSTPR]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: EX.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: EX.USUBJID2122  - name: EXSEQ23    type: int24    label: Sequence Number25    derivation: EX.EXSEQ2627  # S when the collected start carries a time, D when it is a complete date28  # alone. Neither handler is declared, so a missing start, or one cut off29  # before its day such as 2025-01, stops the run.30  - name: TRTSTPR31    type: str32    label: First Exposure Date/Time Collected Precision33    derivation:34      datetime_precision:35        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-15

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

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: D for a complete date, M for year and month, Y for a year alone.	Derived

Version	Date	Author	Description
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

Comments

Mapping spec