yamaa 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 meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: one analysis row for each adverse event carrying the
analysis start (ASTDT) and a second analysis start (ASTDT2).
Input: collected adverse event records carrying the reported
start (AESTDTC).
Variables:
ASTDTwould contain the analysis start date taken from the reported start.ASTDT2would be the calendar date taken from the analysis start, but taking a calendar date needs a date-time value or date text while the analysis start is already a date, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Use the date directly (derivation: ASTDT). When the source is a datetime,
extract its calendar date explicitly:
- name: ASTDT2
type: date
derivation:
to_date: {source: ASTDTM}
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- incompatible_input_type
- rule
- TIME-2
expected/error.yaml
phase: validation
condition: incompatible_input_type
spec_paths:
- columns.ASTDT2.derivation.to_date.source
rule: TIME-2
context:
source: ASTDT
expected: datetime, ISO date text, or ISO 8601 datetime text
actual: date
Inputs
Under review1 source fileinput/ae.csv
Edit1 row| STUDYID | USUBJID | AESEQ | AESTDTC |
|---|---|---|---|
| YAMAA-01 | 1 | 2025-01-15 |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | 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 | ASTDT | Analysis Start Date | numeric | ISO 8601 | Copy value from AE.AESTDTC. | Predecessor | |
| ADAE | ASTDT2 | Analysis Start Date from Datetime | numeric | ISO 8601 | Take the date part of ASTDT, blank for a year or a year and month alone. | Derived |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |