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 each subject's disposition event (EOSSTT) and the days from the last dose to it (EOSPDY) onto the subject-level analysis dataset.

Input: collected demographics with the study day of the last dose (TRTEDY), one record per subject, and collected disposition events with their category and study day (DSSTDY).

Variables:

  • TRTEDY would be the study day of the last dose as collected.
  • EOSSTT would be the subject's disposition event.
  • EOSPDY would be the study day of that event minus the study day of the last dose.

Note: the disposition events are checked to be one per subject before any record is built, but each event also carries a value computed from the record being built, its last dose day. A check made once cannot cover events whose values change record by record, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Keep the uniqueness check on the event itself, and compute the days from the last dose in the subject-level column instead:

- name: EOSPDY
  type: int
  label: Days From Last Dose to End of Study
  derivation: "DISP.DSSTDY - TRTEDY"

with DAYSPOST removed from the event's derivations.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
correlated_derivation_with_unique_verification
rule
LOOKUP-17
expected/error.yaml
phase: validation
condition: correlated_derivation_with_unique_verification
spec_paths:
  - intermediates.DISP.verifications[0].unique
rule: LOOKUP-17
context:
  intermediate: DISP

Inputs

Under review
2 source files

input/dm.csv

Edit
2 rows
input/dm.csv
STUDYIDUSUBJIDTRTEDY
YAMAA-0184
YAMAA-0130

input/ds.csv

Edit
4 rows
input/ds.csv
STUDYIDUSUBJIDDSSEQDSCATDSDECODDSSTDY
YAMAA-011PROTOCOL MILESTONERANDOMIZED1
YAMAA-012DISPOSITION EVENTCOMPLETED90
YAMAA-011PROTOCOL MILESTONERANDOMIZED1
YAMAA-012DISPOSITION EVENTADVERSE EVENT35

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
ADSLTRTEDYLast Dose Study DaynumericCopy value from DM.TRTEDY.Predecessor
ADSLEOSSTTEnd of Study StatuscharacterTake DSDECOD from the DS record matching on STUDYID and USUBJID, where DS.DSCAT = 'DISPOSITION EVENT', and no match yields blank.Derived
ADSLEOSPDYDays From Last Dose to End of StudynumericTake DAYSPOST from the DS record matching on STUDYID and USUBJID, where DS.DSCAT = 'DISPOSITION EVENT', where DAYSPOST is derived as compute DSSTDY - DM.TRTEDY, and no match yields blank.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