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: submit the subject-level analysis dataset with its data definition, the age (AGE) copied unchanged from demographics.

Input: the demographics domain, one record per subject, whose specification spec_dm.yaml the study's tabulation section lists.

Variables:

  • AGE is the age in years, copied from the demographics domain.

Note: the age is copied unchanged and keeps its name, but its label, Age at Informed Consent, differs from the demographics label Age. One variable copied under one name would carry two descriptions across the package, so the submission is refused before any document is written; the dataset itself still builds.

How to fix

Keep the label of the variable the value was copied from:

- name: AGE
  type: int
  label: Age
  derivation: DM.AGE

When the analysis value means something else, give it a name of its own, which may then carry its own label.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
predecessor_label_mismatch
rule
SUB-20
expected/error.yaml
phase: validation
condition: predecessor_label_mismatch
spec_paths:
  - adam.specs[0].columns.AGE.label
rule: SUB-20
context:
  detail: AGE
  predecessor: DM.AGE
  label: Age at Informed Consent
  predecessor_label: Age

Inputs

Under review
2 source files

input/dm.csv

Edit
2 rows
input/dm.csv
DOMAINSTUDYIDUSUBJIDAGE
DMPAR0154
DMPAR0166

input/dm_raw.csv

Edit
2 rows
input/dm_raw.csv
STUDYIDUSUBJIDAGE
PAR0154
PAR0166

Unexpected Output

Under review
2 rows presented to the failing check - not an accepted artifact

expected/adsl.csv

Edit
2 rows
expected/adsl.csv
STUDYIDUSUBJIDAGE
PAR0154
PAR0166
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 IdentifiercharacterReqCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterReqCopy value from DM.USUBJID.Predecessor
ADSLAGEAge at Informed ConsentnumericReqCopy value from DM.AGE.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