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: demonstrate the per-record bindings of an aggregation: convert text questionnaire responses to numbers, then sum them.

Input: questionnaire responses with text results (QSORRES) for the physical functioning scale. Each subject and visit with a record for the first item (PF01) gets one score record.

Variables:

  • PARAMCD: PFSCORE on the score record.
  • PARAM: the subscale name.
  • AVAL: the sum of the visit's physical functioning responses, each read as a number. A blank response is left out of the sum; a response that is not a number stops the run.

Note: there is no separate text-to-number step. Declaring each record's response as a decimal number is what converts it, one record at a time, before the sum runs.

Inputs

Under review
1 source file

input/qs.csv

Edit
4 rows
input/qs.csv
STUDYIDUSUBJIDVISITQSSEQQSCATQSTESTCDQSTESTQSORRES
PILOT7BASELINE1PHYSICAL FUNCTIONING SCALEPF01Trouble with strenuous activity2
PILOT7BASELINE2PHYSICAL FUNCTIONING SCALEPF02Trouble with a long walk1
PILOT7BASELINE3PHYSICAL FUNCTIONING SCALEPF03Trouble with a short walk2
PILOT7BASELINE4PHYSICAL FUNCTIONING SCALEPF04Needs to stay in bed or a chair1

Expected output

Under review
1 expected row

expected/adqs.csv

Edit
1 row
expected/adqs.csv
STUDYIDUSUBJIDVISITPARAMCDPARAMAVAL
PILOT7BASELINEPFSCOREPhysical Functioning Subscale Score6
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
ADQSSTUDYIDStudy IdentifiercharacterCopy value from QS.STUDYID.Predecessor
ADQSUSUBJIDUnique Subject IdentifiercharacterCopy value from QS.USUBJID.Predecessor
ADQSVISITVisit NamecharacterCopy value from QS.VISIT.Predecessor
ADQSPARAMCDParameter CodecharacterSet per constructed row; see the Row construction sheet.Derived
ADQSPARAMParametercharacterSet per constructed row; see the Row construction sheet.Derived
ADQSAVALAnalysis ValuenumericAggregate SUM(QSNUM) over records matching on STUDYID, USUBJID and VISIT, where QS.QSCAT = 'PHYSICAL FUNCTIONING SCALE', with QSNUM as QS.QSORRES.Derived
TemplateInclude whenPARAMCDPARAM
subscaleQS.QSCAT = 'PHYSICAL FUNCTIONING SCALE' AND QS.QSTESTCD = 'PF01'Constant "PFSCORE"Constant "Physical Functioning Subscale Score"
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