Reject Mixed Zones

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 adverse event (AE) term into AETERM and its start moment into ASTDTM.

Input: collected adverse event records carrying term (AETERM) and start text (AESTDTC).

Variables:

ASTDTM would contain the start moment copied from AESTDTC, a site-clock reading with no clock offset. A start that carries an offset, such as +02:00, is not the same kind of value, so the run stops while converting values and no artifact is accepted.

How to fix

Decide whether the study collects an offset at all. If the site clock is what was recorded, correct the collected value so every start reads the same way:

YAMAA-01,YAMAA-01-101,2,HEADACHE,2025-03-04T09:00:00

If the offset is real data, collect it as a field of its own and keep AESTDTC to the site clock. ASTDTM then holds the moment and a second text column holds the offset, where a later analysis can read it.

To inspect the collected characters without failing, carry them in an intermediate text column that is not ASTDTM:

- name: AESTDTC_RAW
  type: str
  label: Collected Start Text
  derivation: AE.AESTDTC

The text keeps the collected characters but does not order chronologically across offsets, and it is not an analysis variable: ASTDTM stays a moment.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: convert
condition: conversion_failed
rule: VALUE-15

expected/error.yaml

phase: convert
condition: conversion_failed
spec_paths:
  - columns.ASTDTM
rule: VALUE-15
context:
  from: str
  to: datetime
  value: "2025-03-04T09:00:00+02:00"
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      AESEQ: 2

YAML specification

1 spec file

spec.yaml

Edit40 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADAE5keys: [STUDYID, USUBJID, AESEQ]6input:7  AE: input/ae.csv89output:10  path: adae.csv11  columns: [STUDYID, USUBJID, AESEQ, AETERM, ASTDTM]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: AE.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: AE.USUBJID2324  - name: AESEQ25    type: int26    label: Sequence Number27    derivation: AE.AESEQ2829  - name: AETERM30    type: str31    label: Reported Term for the Adverse Event32    derivation: AE.AETERM3334  # A datetime is a site-clock reading with no zone or offset. Start text35  # carrying either (Z, +02:00) is not a datetime, and nothing replaces a36  # failed conversion, so that text stops the run.37  - name: ASTDTM38    type: datetime39    label: Analysis Start Date/Time40    derivation: AE.AESTDTC

Inputs

Under review1 source file

input/ae.csv

Edit2 rows

input/ae.csv
STUDYID	USUBJID	AESEQ	AETERM	AESTDTC
YAMAA-01		1	NAUSEA	2025-03-04T09:00:00
YAMAA-01		2	HEADACHE	2025-03-04T09:00:00+02:00

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
ADAE	STUDYID	Study Identifier	character		Copy value from AE.STUDYID.	Predecessor
ADAE	USUBJID	Unique Subject Identifier	character		Copy value from AE.USUBJID.	Predecessor
ADAE	AESEQ	Sequence Number	numeric		Copy value from AE.AESEQ.	Predecessor
ADAE	AETERM	Reported Term for the Adverse Event	character		Copy value from AE.AETERM.	Predecessor
ADAE	ASTDTM	Analysis Start Date/Time	numeric	ISO 8601	Copy value from AE.AESTDTC.	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/ae.csv

Your review

Mapping spec