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: combine blood pressure measured at clinic visits with blood pressure read at home, with the study day in VSDY, where the blood pressure was measured in VSCAT, the systolic blood pressure in VSSTRESN, and each subject's records numbered in order of study day in VSSEQ.

Input: clinic measurements, one per visit, and home readings, one per day. Both carry the study day (VSDY) and the systolic blood pressure (SYSBP).

Variables:

  • VSCAT would be CLINIC for a clinic measurement and HOME for a home reading.
  • VSSTRESN would be the systolic blood pressure of the measurement or the reading.
  • VSSEQ would number each subject's records from 1, the earliest study day first, whether a record is a clinic measurement or a home reading.

Note: the numbering takes each record's day from the clinic measurement it was built from. A record built from a home reading has no clinic measurement, so that day is not a value of the record. The run is rejected before any data is read, and no artifact is accepted.

How to fix

Number the records by a day that every record carries. VSDY already holds it, taken from the clinic measurement or the home reading that built the record, so order by that column:

VSSEQ:
  row_number:
    window:
      group_by: [USUBJID]
      order_by: [VSDY]

When the order needs a value that only one source holds, such as the time of a clinic visit, first bring it onto every record as its own column, filled from each record's own source, and order by that column.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
unknown_field
rule
WINDOW-11
expected/error.yaml
phase: validation
condition: unknown_field
spec_paths:
  - columns.VSSEQ.derivation.row_number.window.order_by[0]
rule: WINDOW-11
context:
  identifier: CLINIC.VSDY
  drivers: [CLINIC, HOME]
  operation: row_number

Inputs

Under review
2 source files

input/clinic.csv

Edit
3 rows
input/clinic.csv
USUBJIDVSDYSYSBP
1132
15128
1145

input/home.csv

Edit
2 rows
input/home.csv
USUBJIDVSDYSYSBP
8130
9124

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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
USUBJIDUnique Subject IdentifierCharDerivedSet per constructed row; see the Row construction sheet.SDTM1
VSCATCategory for Vital SignsCharDerivedSet per constructed row; see the Row construction sheet.SDTM2
VSDYStudy Day of Vital SignsNumDerivedSet per constructed row; see the Row construction sheet.SDTM3
VSSTRESNNumeric Result/Finding in Standard UnitsNumDerivedSet per constructed row; see the Row construction sheet.SDTM4
VSSEQSequence NumberNumDerivedRow number within each group of USUBJID, ordered by CLINIC.VSDY.SDTM5
TemplateInclude whenUSUBJIDVSCATVSDYVSSTRESN
clinicCopy CLINIC.USUBJIDConstant "CLINIC"Copy CLINIC.VSDYCopy CLINIC.SYSBP
homeCopy HOME.USUBJIDConstant "HOME"Copy HOME.VSDYCopy HOME.SYSBP
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