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.
- 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.
- Inputs: Do they look like data collected in a real trial, and do they include the situations you would expect to meet in one?
- 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
README.mdGoal: 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 review1 source fileinput/dm.csv
Edit4 rows| STUDYID | USUBJID | SEX |
|---|---|---|
| YAMAA-01 | M | |
| YAMAA-01 | F | |
| YAMAA-01 | — | |
| YAMAA-01 | U |
Expected output
Under review4 expected rowsexpected/adsl.csv
Edit4 rows| STUDYID | USUBJID | SEXC | SEXC_SINGLE |
|---|---|---|---|
| YAMAA-01 | Male | Male | |
| YAMAA-01 | Female | Female | |
| YAMAA-01 | — | Unknown | |
| YAMAA-01 | Outside codelist | Unknown |
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Set constant value "YAMAA-01". | Assigned | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | SEXC | Sex Decoded | character | Recode DM.SEX: "M" → "Male", "F" → "Female"; missing values stay missing; unlisted values → "Outside codelist". | Derived | ||
| ADSL | SEXC_SINGLE | Sex Decoded With One Result | character | Recode DM.SEX: "M" → "Male", "F" → "Female"; missing or unlisted values → "Unknown". | Derived |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.3 | 2026-09-29 | yamaa docs build | Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata | ||
| 1.2 | 2026-09-29 | yamaa docs build | Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived | ||
| 1.1 | 2026-09-29 | yamaa docs build | Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML | ||
| 1.0 | yamaa docs build | Initial generation from spec.yaml |
yamaa
Comments
Signed in with GitHub; saved in repository Discussions