Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

  1. Task: Would a real study need this derivation, specified this way? Does it follow CDISC standards: variable names, controlled terms, record structure? Flag any rule that is ambiguous or that a sponsor would handle differently.
  2. Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
  3. Expected output: Would independent QC programming reproduce every value from these inputs and rules?

The other tabs beside Comments are background for assessment, not under review.

Summary

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Goal: pin how a dictionary lookup tells a missing code from a collected code outside the dictionary.

Input: spec.yaml decodes coded sex from DM twice: once with a separate named result for codes outside the dictionary, once with one named result for both events. DM carries listed codes, a missing code, and a code outside the dictionary.

Note: a missing code means "not collected"; a collected code outside the dictionary means "outside the codelist" and is usually a data-quality finding. The SEXC column keeps the missing code missing and reads the outside code as Outside codelist. The SEXC_SINGLE column names the same result, Unknown, for both events.

Inputs

Under review
1 source file

input/dm.csv

Edit
4 rows
input/dm.csv
STUDYIDUSUBJIDSEX
YAMAA-01M
YAMAA-01F
YAMAA-01—
YAMAA-01U

Expected output

Under review
4 expected rows

expected/adsl.csv

Edit
4 rows
expected/adsl.csv
STUDYIDUSUBJIDSEXCSEXC_SINGLE
YAMAA-01MaleMale
YAMAA-01FemaleFemale
YAMAA-01—Unknown
YAMAA-01Outside codelistUnknown
Shaded columns are derived— = missing value

Comments and assessment materials

Comments

Signed in with GitHub; saved in repository Discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADSLSTUDYIDStudy IdentifiercharacterSet constant value "YAMAA-01".Assigned
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from DM.USUBJID.Predecessor
ADSLSEXCSex DecodedcharacterRecode DM.SEX: "M" → "Male", "F" → "Female"; missing values stay missing; unlisted values → "Outside codelist".Derived
ADSLSEXC_SINGLESex Decoded With One ResultcharacterRecode DM.SEX: "M" → "Male", "F" → "Female"; missing or unlisted values → "Unknown".Derived
VersionDateAuthorDescriptionReviewerSign-off
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

yamaa code

Runs the yamaa specification; its result must match the expected output

run.R

Edit
4 lines
library(yamaa)adsl <- yamaa_domain("spec.yaml")$outputadsl

run.py

Edit
4 lines
import yamaaadsl = yamaa.yamaa_domain("spec.yaml").outputadsl