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: carry the numeric result (LBSTRESN) and the baseline flag (LBBLFL) as collected, and repeat the baseline value (BAVL) on every row for the subject.

Input: collected lab (LB) records, each with a numeric result (LBSTRESN) and a baseline flag (LBBLFL) holding Y on the baseline record.

Variables:

  • BAVL: the baseline value, taken from the subject's row flagged Y in LBBLFL and repeated on every row for that subject; missing when the subject has no flagged row.

Note: the run is rejected when a subject has more than one record flagged Y: no single baseline value exists, so no artifact is accepted.

How to fix

Keep exactly one baseline record per subject. Either clear the flag in the collected data on the visit that is not the baseline, for example WEEK 1:

STUDYID,USUBJID,VISIT,LBSTRESN,LBBLFL
PILOT7,P7-901,SCREENING,5.1,Y
PILOT7,P7-901,WEEK 1,5.4,
PILOT7,P7-901,WEEK 2,5.2,

or, when both visits genuinely qualify, pick one by rule (for example the earliest) and flag only that row before deriving.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
derivation
condition
aggregate_multiple_records
rule
FORMULA-20
expected/error.yaml
phase: derivation
condition: aggregate_multiple_records
spec_paths:
  - columns.BAVL.derivation.aggregate
rule: FORMULA-20
context:
  reducer: ONLY
  record_count: 2

Inputs

Under review
1 source file

input/lb.csv

Edit
3 rows
input/lb.csv
STUDYIDUSUBJIDVISITLBSTRESNLBBLFL
PILOT7SCREENING5.1Y
PILOT7WEEK 15.4Y
PILOT7WEEK 25.2—

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
ADLBSTUDYIDStudy IdentifiercharacterCopy value from LB.STUDYID.Predecessor
ADLBUSUBJIDUnique Subject IdentifiercharacterCopy value from LB.USUBJID.Predecessor
ADLBVISITVisit NamecharacterCopy value from LB.VISIT.Predecessor
ADLBLBSTRESNNumeric ResultnumericCopy value from LB.LBSTRESN.Predecessor
ADLBLBBLFLBaseline FlagcharacterCopy value from LB.LBBLFL.Predecessor
ADLBBAVLBaseline ValuenumericAggregate ONLY(LBSTRESN) over records grouped by STUDYID, USUBJID, matching on the shared output keys, where LBBLFL = 'Y'.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