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: derive each subject's end-of-study date (EOSDT) from the subject's one end-of-study disposition record.

Input: demographics records with disposition records carrying category (DSCAT), decoded term (DSDECOD), and start date (DSSTDTC).

Variables:

  • EOSDT would be the start date of the subject's end-of-study record, the disposition event that is not a screen failure, and blank when the subject has none. The study expects at most one such record per subject; a subject with two has no single end-of-study date, so the run is rejected before any output row is built and no artifact is accepted.

How to fix

Give each subject exactly one eligible end-of-study record in the source data. When the source cannot promise that, drop the uniqueness assertion and choose the record explicitly instead, here the one with the latest start date:

intermediates:
  - id: DS_EOS
    dataset: DS
    key: [STUDYID, USUBJID]
    filter: "DS.DSCAT = 'DISPOSITION EVENT' AND DS.DSDECOD <> 'SCREEN FAILURE'"
    order_by: [DS.DSSTDTC]
    keep: last

A subject with no eligible record, one whose only disposition records are screen failures, then gets a blank EOSDT: a lookup that finds no record answers with a missing value instead of failing.

Keep the uniqueness assertion only for eligible sets that truly carry each key once.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
verification
condition
duplicate_intermediate_records
rule
LOOKUP-17
expected/error.yaml
phase: verification
condition: duplicate_intermediate_records
spec_paths:
  - intermediates.DS_EOS.verifications[0].unique
rule: LOOKUP-17
context:
  intermediate: DS_EOS
  dataset: DS
  columns: [STUDYID, USUBJID]
  duplicate_count: 1

Inputs

Under review
2 source files

input/dm.csv

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

input/ds.csv

Edit
5 rows
input/ds.csv
STUDYIDUSUBJIDDSCATDSDECODDSSTDTC
YAMAA-01DISPOSITION EVENTSCREEN FAILURE2024-01-05
YAMAA-01DISPOSITION EVENTCOMPLETED2024-01-10
YAMAA-01DISPOSITION EVENTWITHDRAWAL BY SUBJECT2024-01-15
YAMAA-01DISPOSITION EVENTCOMPLETED2024-02-11
YAMAA-01DISPOSITION EVENTSCREEN FAILURE2024-03-02

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
ADSLEOSDTEnd of Study DatecharacterTake DSSTDTC from the DS record matching on STUDYID and USUBJID, where DS.DSCAT = 'DISPOSITION EVENT' AND DS.DSDECOD <> 'SCREEN FAILURE', and a row with no match is an error.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