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 vital-sign result (AVAL) for each subject, parameter and timepoint, with descriptions of the values for the data-definition document.

Input: standardized vital signs, one record per subject, test and timepoint, with the numeric result.

Variables:

  • PARAMCD is the vital-sign test code.
  • ATPT is the timepoint, lying or standing.
  • AVAL would be the numeric result.

Note: each record may be described by at most one of a variable's value descriptions. One description here is chosen by parameter and another by timepoint, which nothing rules out until the data arrive: the standing systolic pressure matches both, so the run stops once the results are complete and no artifact is accepted.

How to fix

Decide which description the standing systolic pressure should carry, and make the conditions exclusive, for example by naming the parameter in the standing description as well:

value_level:
  - id: SYSBP
    where: {PARAMCD: [SYSBP], ATPT: [AFTER 5 MIN LYING]}
  - id: STANDING
    where: {PARAMCD: [SYSBP, DIABP], ATPT: [AFTER 3 MIN STANDING]}

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
verification
condition
value_level_multiple_matches
rule
SUB-13
expected/error.yaml
phase: verification
condition: value_level_multiple_matches
spec_paths:
  - columns.AVAL.submission.value_level
rule: SUB-13
context:
  column: AVAL
  failure_count: 1
  entries:
    - [SYSBP, STANDING]
  keys:
    - USUBJID: CATH-001
      PARAMCD: SYSBP
      ATPT: AFTER 3 MIN STANDING

Inputs

Under review
1 source file

input/vs.csv

Edit
4 rows
input/vs.csv
USUBJIDVSTESTCDVSTPTVSSTRESN
SYSBPAFTER 5 MIN LYING118
SYSBPAFTER 3 MIN STANDING104
DIABPAFTER 5 MIN LYING76
DIABPAFTER 3 MIN STANDING70

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
ADVSUSUBJIDUnique Subject IdentifiercharacterCopy value from VS.USUBJID.Predecessor
ADVSPARAMCDParameter CodecharacterCopy value from VS.VSTESTCD.Predecessor
ADVSATPTAnalysis TimepointcharacterCopy value from VS.VSTPT.Predecessor
ADVSAVALAnalysis ValuenumericCopy value from VS.VSSTRESN.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