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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: give each subject a baseline body mass index in BMIBL, computed
by the project's own routine from the subject's first height measurement and
screening weight.
Input: demographics records, one per subject; height measurements
carrying the study day (VSDY) and the height (HEIGHTCM); and weight
records carrying the visit (VISIT), the order recorded (WTSEQ) and the
weight (WEIGHTKG), where a subject may have been weighed more than once at
screening.
Variables:
BMIBLwould be the body mass index of the subject's first height measurement with the screening weight, and blank when either is missing.
Note: the routine takes one weight for each height measurement, but a subject weighed twice at screening has two screening weights, and nothing states which one to use. The run is rejected before any data is read and no artifact is accepted.
How to fix
Decide which screening weight is the baseline, and state it on the screening weights, for example the last one recorded:
- id: SCREENWT
dataset: WEIGHT
key: [USUBJID]
filter: "WEIGHT.VISIT = 'SCREENING'"
order_by: [WEIGHT.WTSEQ]
keep: last
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_derive_step
- rule
- LOOKUP-22
expected/error.yaml
phase: validation
condition: invalid_derive_step
spec_paths:
- intermediates.FIRSTBMI.derivations.BMI.function.args.weight_kg
rule: LOOKUP-22
context:
function: bmi
argument: weight_kg
intermediate: SCREENWT
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 | BMIBL | Baseline Body Mass Index (kg/m2) | numeric | Take BMI from the first HEIGHT record matching on USUBJID, ordered by HEIGHT.VSDY, where BMI is derived as call project function bmi with weight_kg = SCREENWT.WEIGHTKG and height_cm = HEIGHT.HEIGHTCM, and no match yields blank. | 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 |
yamaa