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: double the administered exposure dose in DOSEDBL for
each subject.
Input: a subject-treatment inventory carrying EXTRT with
matching exposure records carrying the exposure sequence number
and EXDOSE.
Variables:
DOSEDBLwould contain twice the exposure dose (EXDOSE * 2) for the subject. A subject can have several exposure records, so a formula namingEX.EXDOSEdoes not say which record it means, and choosing one without a stated rule, or totalling them, would each give a different result. A formula computes only from values the output row already carries, and a value taken from another source is bound to one of those first, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Choose the exposure record explicitly, bind its dose to an output column, and then compute from the unqualified column. For example, to use the earliest administration:
- name: DOSE
type: float
derivation:
source:
variable: EX.EXDOSE
order_by: [EX.EXSEQ]
keep: first
- name: DOSEDBL
type: float
derivation: "DOSE * 2"
Keep DOSE internal by omitting it from output.columns.
If the intended value is cumulative dose instead, use a qualified
aggregate rather than selecting one record.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- qualified_identifier
- rule
- FORMULA-9
expected/error.yaml
phase: validation
condition: qualified_identifier
spec_paths:
- columns.DOSEDBL.derivation
rule: FORMULA-9
context:
expr: "EX.EXDOSE * 2"
identifier: EX.EXDOSE
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 |
|---|---|---|---|---|---|---|---|
| ADEX | STUDYID | Study Identifier | character | Copy value from TRT.STUDYID. | Predecessor | ||
| ADEX | USUBJID | Unique Subject Identifier | character | Copy value from TRT.USUBJID. | Predecessor | ||
| ADEX | DOSEDBL | Doubled Dose | numeric | Compute EX.EXDOSE * 2. | 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 |