Review ask

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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Public 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:

  • BMIBL would 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

Edit
the run is rejected; no artifact is accepted
expected/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 review
3 source files

input/dm.csv

Edit
2 rows
input/dm.csv
STUDYIDUSUBJID
YAMAA-01
YAMAA-01

input/height.csv

Edit
3 rows
input/height.csv
USUBJIDVSDYHEIGHTCM
-7175
1175
-5162

input/weight.csv

Edit
3 rows
input/weight.csv
USUBJIDVISITWTSEQWEIGHTKG
SCREENING170
SCREENING271
SCREENING158

Unexpected Output

Under review
No artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Your review

2 questions and your comments · View benchmark discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADSLSTUDYIDStudy IdentifiercharacterCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLBMIBLBaseline Body Mass Index (kg/m2)numericTake 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
VersionDateAuthorDescriptionReviewerSign-off
1.72026-10-20yamaa docs buildRead 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.62026-10-17yamaa docs buildDescribe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.52026-10-17yamaa docs buildName 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.42026-10-15yamaa docs buildState datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml