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 the treatment a subject received and the dose they
received of it onto TRT01A and TRT01DOSE.
Input: demographics records for each subject, with exposure
records carrying treatment (EXTRT), dose (EXDOSE), sequence
number (EXSEQ), and start date (EXSTDTC).
Variables:
TRT01Awould contain the treatment from the subject's chosen exposure record.TRT01DOSEwould contain the dose from that same record.
Note: the pair must come from one administration, but nothing says which one, so a subject matching more than one exposure record has no single answer, and the run is rejected with no artifact accepted.
How to fix
State the full order and which end of that order to keep. To choose the earliest administration, read the sequence as an integer so ties on the date are broken numerically:
input:
EX: {path: input/ex.csv, types: {EXSEQ: int}}
intermediates:
- id: DOSING
dataset: EX
key: [STUDYID, USUBJID]
order_by: [EX.EXSTDTC, EX.EXSEQ]
keep: first
Both TRT01A and TRT01DOSE then come from that same chosen record.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- join
- condition
- multiple_matches
- rule
- LOOKUP-10
expected/error.yaml
phase: join
condition: multiple_matches
spec_paths:
- intermediates.DOSING
rule: LOOKUP-10
context:
intermediate: DOSING
dataset: EX
key:
- STUDYID
- USUBJID
intermediate_key:
STUDYID: PILOT7
USUBJID: P7-321
match_count: 2
keys:
- STUDYID: PILOT7
USUBJID: P7-321
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 | Copy value from DM.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | TRT01A | Actual Treatment for Period 01 | character | Take EXTRT from the EX record matching on STUDYID and USUBJID, and a row with no match is an error. | Derived | ||
| ADSL | TRT01DOSE | Actual Dose for Period 01 | numeric | Take EXDOSE from the EX record matching on STUDYID and USUBJID, and a row with no match 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 |