Review ask

As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs and outputs. 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: show the order a specification runs in: rows are built first, then columns are added on top of the finished rows, and rows discarded along the way never reach the final checks.

Input: one spec.yaml over one lab-results file. Each record carries a subject (USUBJID), a visit (VISIT), a test code (ALT or AST), and a result that arrives as text.

Behavior:

  • A record with no result never becomes a row: it is dropped before any row is built. Each surviving record becomes one component row carrying its test code, the test's full name (PARAM), and its result (AVAL).
  • One summary row per subject-visit carries that visit's lowest result. The visit whose results are all missing is discarded after its summary is computed, so the final completeness check on AVAL passes: it never sees the discarded row.
  • Text results become numbers while the rows are built, so the two columns added afterwards read numbers, never text: DOUBLE holds twice the result, and FLAG marks results above 50 with H.
  • Every row carries the study identifier YAMAA-01 in STUDYID.

Note: building rows may change the row count while adding columns may not: each finished row gets exactly one DOUBLE and one FLAG.

Inputs

Under review
1 source file

input/lb.csv

Edit
8 rows
input/lb.csv
USUBJIDVISITLBTESTCDLBSTRESN
1ALT32
1AST45
2ALT28
2AST—
3ALT—
3AST—
1ALT60
1AST70

Expected output

Under review
8 expected rows

expected/adlb.csv

Edit
8 rows
expected/adlb.csv
STUDYIDUSUBJIDVISITPARAMCDPARAMAVALDOUBLEFLAG
YAMAA-011ALTAlanine Aminotransferase3264N
YAMAA-011ASTAspartate Aminotransferase4590N
YAMAA-012ALTAlanine Aminotransferase2856N
YAMAA-011ALTAlanine Aminotransferase60120H
YAMAA-011ASTAspartate Aminotransferase70140H
YAMAA-011LOWLowest Result of Visit3264N
YAMAA-012LOWLowest Result of Visit2856N
YAMAA-011LOWLowest Result of Visit60120H
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 IdentifiercharacterSet constant value "YAMAA-01".Assigned
ADLBUSUBJIDUnique Subject IdentifiercharacterCopy value from LB.USUBJID.Predecessor
ADLBVISITVisit NumbernumericCopy value from LB.VISIT.Predecessor
ADLBPARAMCDParameter CodecharacterSet per constructed row; see the Row construction sheet.Derived
ADLBPARAMParametercharacterSet per constructed row; see the Row construction sheet.Derived
ADLBAVALAnalysis ValuenumericSet per constructed row; see the Row construction sheet.Derived
ADLBDOUBLETwice the Analysis ValuenumericCompute 2 * AVAL.Derived
ADLBFLAGHigh Value FlagcharacterIf AVAL > 50 then "H"; otherwise "N".Derived
TemplateInclude whenPARAMCDPARAMAVAL
componentsLB.LBSTRESN IS NOT NULLCopy LB.LBTESTCDIf LB.LBTESTCD = 'ALT' then "Alanine Aminotransferase"; otherwise "Aspartate Aminotransferase"Copy LB.LBSTRESN
visit_lowAVAL IS NOT NULLConstant "LOW"Constant "Lowest Result of Visit"Aggregate MIN(LB.LBSTRESN) over records matching on the shared output keys
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

yamaa code

Public calls generated from benchmark.yaml; results must match the expected output

R

Edit
3 lines
library(yamaa)yamaa_spec("spec.yaml")$run()$output

Python

Edit
3 lines
import yamaayamaa.spec("spec.yaml").run().output