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: reviewedEditUnder review
What this benchmark means
README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: carry the recorded sex (SEX) for each subject from collected demographics, accepting only M, F, and U.

Input: collected demographics with study and subject identifiers and recorded sex (SEX).

Variables:

  • SEX is the subject's recorded sex, copied from collected SEX. A missing value remains missing and passes the final check; any other value must be M, F, or U.

A non-missing code outside the accepted set is rejected after the dataset is completed, so no artifact is accepted.

How to fix

Confirm the code against the study's sex coding convention. Correct X at the governed source when it is a data-entry error. If X is an intentional study code, document that policy and add it to the anchored accepted set on the SEX column:

verifications:
  - matches:
      pattern: '^[MFUX]$'

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
verification
condition
matches_failed
rule
CHECK-9
expected/error.yaml
phase: verification
condition: matches_failed
spec_paths:
  - columns.SEX.verifications[0].matches
rule: CHECK-9
context:
  column: SEX
  failure_count: 1
  keys:
    - STUDYID: PILOT7
      USUBJID: P7-952

Inputs

Under review
1 source file

input/dm.csv

Edit
2 rows
input/dm.csv
STUDYIDUSUBJIDSEX
PILOT7M
PILOT7X

Unexpected Output

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

expected/adsl.csv

Edit
2 rows
expected/adsl.csv
STUDYIDUSUBJIDSEX
PILOT7M
PILOT7X
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
ADSLSEXSexcharacterCopy value from DM.SEX.Predecessor
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