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 the demographics dataset, one record per subject, and submit it with its data-definition document.

Input: the study's subjects, one row each.

Variables:

  • USUBJID identifies each subject across the study.

Note: a dataset names the implementation guide it follows by the guide's name alone, so one data definition cites each guide once. The study cites two versions of the general tabulation guide, so the submission stops before any file is written; the dataset itself still builds.

How to fix

Cite the one version of the guide the study follows:

sdtm:
  standards:
    - {name: SDTMIG, version: "3.4", status: Final}

Datasets prepared under an earlier version are brought to that version before the study submits them together.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
duplicate_identifier
rule
DEFINE-6
expected/error.yaml
phase: validation
condition: duplicate_identifier
spec_paths:
  - sdtm.standards[1].name
rule: DEFINE-6
context:
  identifier: SDTMIG

Inputs

Under review
1 source file

input/subjects.csv

Edit
2 rows
input/subjects.csv
STUDYIDUSUBJID
DEV01
DEV01

Unexpected Output

Under review
2 rows presented to the failing check - not an accepted artifact

expected/dm.csv

Edit
2 rows
expected/dm.csv
DOMAINSTUDYIDUSUBJID
DMDEV01
DMDEV01
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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
DOMAINDomain AbbreviationChar2AssignedReqSet constant value "DM".SDTM1
STUDYIDStudy IdentifierChar5ProtocolReqCopy value from SUBJECTS.STUDYID.SDTM2
USUBJIDUnique Subject IdentifierChar9AssignedReqCopy value from SUBJECTS.USUBJID.SDTM3
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