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: build one record per subject from the subject's exposure records,
with the total dose administered in TOTDOSE and the treatment period of the
subject's first dose in APERIOD.
Input: exposure records, one per administration, carrying the study day
(EXSTDY) and the dose given (EXDOSE), and the study's treatment periods,
each running from a first (LO) to a last (HI) study day.
Variables:
TOTDOSEwould be the sum of the doses of the subject's administrations.APERIODwould be the period, both ends inclusive, that holds the study day of the subject's first dose, and blank when no period does.
Note: each subject's record summarizes all of the subject's administrations, and the period is found from an administration's study day. A subject with several administrations has several such days, so the record has no single day to place in a period, and the run is rejected before any data is read and no artifact is accepted.
How to fix
Derive the day of the first dose on the subject's record, then find the period from that value:
derivations:
FIRSTDY: {aggregate: "MIN(EX.EXSTDY)"}
between: {value: FIRSTDY, lower: LO, upper: HI}
Leave FIRSTDY out of the published columns when the artifact should not
carry it.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- ungrouped_driver_field
- rule
- ROW-5
expected/error.yaml
phase: validation
condition: ungrouped_driver_field
spec_paths:
- intermediates.PERIOD.between.value
rule: ROW-5
context:
identifier: EX.EXSTDY
intermediate: PERIOD
row: subject
dataset: EX
Inputs
Under review2 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 | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADSL | TOTDOSE | Total Dose Administered | numeric | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADSL | APERIOD | Period of First Dose | numeric | Set per constructed row; see the Row construction sheet. | Derived |
| Template | Include when | STUDYID | USUBJID | TOTDOSE | APERIOD |
|---|---|---|---|---|---|
| subject | Copy EX.STUDYID | Copy EX.USUBJID | Aggregate SUM(EX.EXDOSE) over records matching on the shared output keys | Copy APERIOD from the PERIODS record matching on STUDYID, where EX.EXSTDY falls within LO to HI, and no match yields blank |
| 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 |