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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: complete the analysis start date (ASTDT) of each
adverse event (AE) from the collected start (AESTDTC), supplying
a month and a day wherever the collected text does not already
carry them.
Input: collected event records carrying the reported term
(AETERM) and the collected start (AESTDTC).
Variables:
ASTDTwould be the analysis start date completed fromAESTDTCto the earliest date the collected text still allows, with15as the supplied month and1as the supplied day. A year and month without a day would be completed, a year alone would be completed from the supplied month and day, and a fully collected date would be used as collected. The value15is not a calendar month, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Use a calendar month from 1 through 12. Because this benchmark describes earliest imputation, January is the consistent correction:
impute:
type: date
source: AE.AESTDTC
month: 1
day: 1
A year-and-month value such as 2023-06 then becomes 2023-06-01, and a
year-only value such as 2023 becomes 2023-01-01.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- month_out_of_range
- rule
- TIME-10
expected/error.yaml
phase: validation
condition: month_out_of_range
spec_paths:
- columns.ASTDT.derivation.impute.month
rule: TIME-10
context:
month: 15
Inputs
Under review1 source fileinput/ae.csv
Edit2 rows| STUDYID | USUBJID | AESEQ | AETERM | AESTDTC |
|---|---|---|---|---|
| YAMAA-01 | 1 | Nausea | 2023 | |
| YAMAA-01 | 2 | Fatigue | 2023-06-14 |
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 | Impute incomplete date from AE.AESTDTC, defaulting month=15, day=1; invalid text is an error. | 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 |
yamaa