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 record for each collected event, carrying
the start-date completeness flag ASTDTF.
Input: collected event records carrying the reported term
(AETERM) and the collected start (AESTDTC).
Variables:
ASTDTFwould contain how much of the start dateAESTDTCcarries:dayfor a full date,monthfor a year and month,yearfor a year alone, and blank when the start was never collected. Text that is neither a date nor the beginning of one has no completeness to report, so the run stops when it tries to read precision from it and no artifact is accepted.
How to fix
Correct the source text when a date can be recovered. If invalid date text is intentionally represented by a missing precision flag, declare that outcome explicitly:
precision:
type: date
source: AE.AESTDTC
invalid: null
The invalid outcome covers UNK; a source value that was not collected
already gives a missing flag.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- impute
- condition
- invalid_date_text
- rule
- TIME-13
expected/error.yaml
phase: impute
condition: invalid_date_text
spec_paths:
- columns.ASTDTF.derivation.precision
rule: TIME-13
context:
source: AE.AESTDTC
value: UNK
keys:
- STUDYID: PILOT7
USUBJID: P7-341
AESEQ: 2
Inputs
Under review1 source fileinput/ae.csv
Edit2 rows| STUDYID | USUBJID | AESEQ | AETERM | AESTDTC |
|---|---|---|---|---|
| PILOT7 | 1 | Nausea | 2023-06 | |
| PILOT7 | 2 | Fatigue | UNK |
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 | ASTDTF | Analysis Start Date Imputation Flag | character | Collected date precision of AE.AESTDTC: "day" for a complete date, "month" for a year and month, "year" for a year alone, "none" for an entirely imputed date or text with an unknown year; 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 |