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: reviewedEditUnder review
What this benchmark means
README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: attempt one laboratory analysis record per collected laboratory result, carrying AVAL for the numeric analysis value.

Input: collected laboratory results with the result in standard units (LBSTRESN).

Variables:

  • AVAL would be the numeric analysis value, copying LBSTRESN. Whole and fractional numbers are stored as different kinds of value, but the declared kind says only number. Choosing either representation would invent a precision decision the declaration did not make, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Choose the type from the measurement contract. Use int only when fractions are impossible; otherwise use float:

- name: AVAL
  type: float
  label: Analysis Value
  derivation: LB.LBSTRESN

The allowed column types are str, int, float, date, and datetime.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
value_not_permitted
rule
VALUE-1
expected/error.yaml
phase: validation
condition: value_not_permitted
spec_paths:
  - columns.AVAL.type
rule: VALUE-1
context:
  value: number
  permitted: [str, int, float, date, datetime, time]

Inputs

Under review
1 source file

input/lb.csv

Edit
1 row
input/lb.csv
STUDYIDUSUBJIDLBSEQLBSTRESN
PILOT7112.5

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
ADLBLBSEQSequence NumbernumericCopy value from LB.LBSEQ.Predecessor
ADLBAVALAnalysis ValuenumberCopy value from LB.LBSTRESN.Predecessor
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