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 first treatment received in TRT01A, one
record per subject.
Input: demographics records plus exposure records carrying the
administration sequence number (EXSEQ), the treatment name
(EXTRT), and the administration start date (EXSTDTC).
Variables:
TRT01Awould contain the treatment name from the earliest exposure record.
Note: the chosen record is named EX, which already names the
exposure records, so a read of EX.EXTRT cannot say whether it
means the treatment of the chosen record or of every exposure
record. The two readings differ whenever a subject has more than one
administration. The name itself is rejected before any data is
read, so no artifact is accepted.
How to fix
Give the record lookup a name that is distinct from every dataset and from the output domain, then read through that name:
intermediates:
- id: FIRSTEX
dataset: EX
key: [STUDYID, USUBJID]
order_by: [EX.EXSTDTC, EX.EXSEQ]
keep: first
# ...
derivation: FIRSTEX.EXTRT
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- duplicate_identifier
- rule
- LOOKUP-3
expected/error.yaml
phase: validation
condition: duplicate_identifier
spec_paths:
- intermediates.EX.id
- input.EX
rule: LOOKUP-3
context:
identifier: 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 | 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 first EX record matching on STUDYID and USUBJID, ordered by EX.EXSTDTC then EX.EXSEQ, 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 |