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: number each subject's adverse events in AOCCSEQ, earliest first.

Input: adverse event records carrying the analysis start date (ASTDT) and the event's sequence number (AESEQ).

Variables:

  • ASTDT would be the event's analysis start date.
  • AOCCSEQ would number each subject's events from 1 in order of their start date, the event's sequence number breaking same-day ties.

Note: the events are numbered separately for each study and subject, and the list that says so names the subject twice. A repeated entry states the same grouping again and may hide a variable that was meant instead, so the run is rejected before any data is read and no artifact is accepted.

How to fix

Name each grouping variable once. When the repeated entry was meant to be a different variable, name that variable instead:

- name: AOCCSEQ
  type: int
  derivation:
    row_number:
      window:
        group_by: [STUDYID, USUBJID]
        order_by: [ASTDT, AESEQ]

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
invalid_field_type
rule
WINDOW-3
expected/error.yaml
phase: validation
condition: invalid_field_type
spec_paths:
  - columns.AOCCSEQ.derivation.row_number.window.group_by[2]
rule: WINDOW-3
context:
  identifier: USUBJID

Inputs

Under review
1 source file

input/adae_raw.csv

Edit
3 rows
input/adae_raw.csv
STUDYIDUSUBJIDAESEQASTDT
YAMAA-0112024-03-02
YAMAA-0122024-02-20
YAMAA-0112024-03-09

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
ADAESTUDYIDStudy IdentifiercharacterCopy value from ADAE_RAW.STUDYID.Predecessor
ADAEUSUBJIDUnique Subject IdentifiercharacterCopy value from ADAE_RAW.USUBJID.Predecessor
ADAEAESEQSequence NumbernumericCopy value from ADAE_RAW.AESEQ.Predecessor
ADAEASTDTAnalysis Start DatenumericISO 8601Copy value from ADAE_RAW.ASTDT.Predecessor
ADAEAOCCSEQSubject Occurrence Sequence NumbernumericRow number within each group of STUDYID, USUBJID, USUBJID, ordered by ASTDT then AESEQ.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