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: build one subject-level record per subject carrying TOTDOSE, the subject's total administered dose.

Input: demographics with one record per subject, and exposure records with the dose and start date of each administration.

Variables:

  • TOTDOSE would be the total of the subject's administered doses.

Note: the request orders the exposure records by start date before totalling them. A total always adds the records in the order they are stored, so the stated order has nothing to act on, and the run is rejected before any data is read.

How to fix

Remove the order: the total adds the doses in their stored order.

- name: TOTDOSE
  type: float
  derivation:
    aggregate:
      key: [STUDYID, USUBJID]
      expr: "SUM(EX.EXDOSE)"

If the order was meant to choose one record, such as the last dose, select that record with a lookup that orders the records and keeps the last one. If it was meant to list the doses in date order, join them into one text with STR_JOIN, which reads the order.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
unpaired_fields
rule
LOOKUP-10
expected/error.yaml
phase: validation
condition: unpaired_fields
spec_paths:
  - columns.TOTDOSE.derivation.aggregate
rule: LOOKUP-10
context:
  declared:
    - order_by
  missing:
    - STR_JOIN(x)

Inputs

Under review
2 source files

input/dm.csv

Edit
2 rows
input/dm.csv
STUDYIDUSUBJID
YAMAA-01
YAMAA-01

input/ex.csv

Edit
3 rows
input/ex.csv
STUDYIDUSUBJIDEXSEQEXDOSEEXSTDTC
YAMAA-0111002025-01-02
YAMAA-0121002025-01-01
YAMAA-011502025-01-01

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
ADSLSTUDYIDStudy IdentifiercharacterCopy value from DM.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLTOTDOSETotal Dose AdministerednumericAggregate SUM(EX.EXDOSE) over records matching on STUDYID and USUBJID.Derived
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