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: carry each subject's age (AGE) and first dose date (TRTSDT)
onto the subject-level analysis dataset.
Input: collected demographics with the age, and the saved exposure
summary with the first dose date. spec_exsum.yaml produces that summary,
and it takes each subject's age from the subject-level dataset in turn.
Variables:
AGEwould be the age in years as collected.TRTSDTwould be the first dose date as the exposure summary states it.
Note: the subject-level dataset takes its first dose date from the exposure summary, and the exposure summary takes its age from the subject-level dataset. Each would have to be built before the other, so no order can build them, and the run is rejected before any data is read; no artifact is accepted.
How to fix
Decide which dataset owns each value, and take it from its own source rather than from the other dataset. Here the exposure summary can read the age from the collected demographics instead of the subject-level dataset:
input:
EX: {path: input/ex_first.csv, types: {TRTSDT: date}}
DM: {path: input/dm.csv, key: [STUDYID, USUBJID]}
with the age read as DM.AGE, so that only the subject-level dataset reads
the exposure summary.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- producer_workflow_cycle
- rule
- SPEC-9
expected/error.yaml
phase: validation
condition: producer_workflow_cycle
spec_paths:
- input.ADSL.schema
rule: SPEC-9
context:
dataset: ADSL
Inputs
Under review3 source filesUnexpected 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 |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Copy value from DM.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | AGE | Age | numeric | Copy value from DM.AGE. | Predecessor |
| 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 |