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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: one row per adverse event (AE) with its analysis start date (ASTDT) and the study day of that start (ASTDY).

Input: collected adverse events with the onset date (AESTDTC) and the subject's first treatment date (TRTSDT).

Variables:

  • ASTDT is the onset date as collected.
  • TRTSDT is the date of the first exposure to treatment.
  • ASTDY would be the study day of the onset: the first treatment date is day 1 and the day before it is day -1. A study day is a count of days, and the column meant to hold it holds calendar dates, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Store the study day as an integer, the type every study day has:

- name: ASTDY
  type: int
  label: Analysis Start Relative Day
  derivation:
    study_day:
      source: ASTDT
      reference: TRTSDT

A specification that needs the calendar date of the onset already has it in ASTDT.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
conversion_failed
rule
VALUE-24
expected/error.yaml
phase: validation
condition: conversion_failed
spec_paths:
  - columns.ASTDY
rule: VALUE-24
context:
  from: int
  to: date

Inputs

Under review
1 source file

input/ae.csv

Edit
2 rows
input/ae.csv
STUDYIDUSUBJIDAESEQAETERMAESTDTCTRTSDT
PILOT71Headache2025-03-102025-03-01
PILOT72Nausea2025-02-272025-03-01

Unexpected Output

Under review
No artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Your review

2 questions and your comments · View benchmark discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADAESTUDYIDStudy IdentifiercharacterCopy value from AE.STUDYID.Predecessor
ADAEUSUBJIDUnique Subject IdentifiercharacterCopy value from AE.USUBJID.Predecessor
ADAEAESEQSequence NumbernumericCopy value from AE.AESEQ.Predecessor
ADAEASTDTAnalysis Start DatenumericISO 8601Copy value from AE.AESTDTC.Predecessor
ADAETRTSDTDate of First Exposure to TreatmentnumericISO 8601Copy value from AE.TRTSDT.Predecessor
ADAEASTDYAnalysis Start Relative DaynumericISO 8601CDISC study day of ASTDT against TRTSDT as day 1; there is no day zero.Derived
VersionDateAuthorDescriptionReviewerSign-off
1.72026-10-20yamaa docs buildRead 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.62026-10-17yamaa docs buildDescribe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.52026-10-17yamaa docs buildName 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.42026-10-15yamaa docs buildState datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml