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 ADaM: 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: show that a lone value may stand where a list is accepted, and a lone condition or label string may stand where its full form is accepted: the short spellings run exactly as their long forms.
Input: one spec.yaml over a demographics file (one record per
subject: sex and age) and a weight file (several dated weight records
per subject).
Variables:
SEX: the subject's recorded sex.AGE: the subject's age in years; blank when not collected.AGE65FL:Yfor subjects aged 65 or older; blank otherwise. A lone condition needs no explicit yes or no text: it answersYwhen true and stays blank when false or unknown.SUBJLBL: a readable label joining the subject identifier and sex, written as one plain string with placeholders.WTMAX: the largest collected weight across the subject's weight records; the grouping key is written as a single key.LASTWT: the weight from the subject's latest dated record; the latest record wins because a single ordering value sorts earliest-first, and the match key is written as a single key.
Note: each short spelling expands to its full form before the
run: a lone key becomes a one-key list, a lone check becomes a
one-check list, a lone condition answers Y when true and stays
blank otherwise, a lone label string keeps its placeholders, and a
lone ordering value sorts earliest-first.
Inputs
Under review2 source filesExpected output
Under review4 expected rowsexpected/adsl.csv
Edit4 rows| STUDYID | USUBJID | SEX | AGE | AGE65FL | SUBJLBL | WTMAX | LASTWT |
|---|---|---|---|---|---|---|---|
| YAMAA-01 | M | 34 | — | Subject YAMAA-01-001 (M) | 71 | 71 | |
| YAMAA-01 | F | 67 | Y | Subject YAMAA-01-002 (F) | 68 | 67.5 | |
| YAMAA-01 | M | — | — | Subject YAMAA-01-003 (M) | 80 | 80 | |
| YAMAA-01 | F | 72 | Y | Subject YAMAA-01-004 (F) | 56 | 56 |
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 | SEX | Sex | character | Copy value from DM.SEX. | Predecessor | ||
| ADSL | AGE | Age | numeric | Copy value from DM.AGE. | Predecessor | ||
| ADSL | AGE65FL | Age 65 or Older Flag | character | "Y" when AGE >= 65; blank otherwise. | Derived | ||
| ADSL | SUBJLBL | Subject Label | character | Fill the template "Subject {USUBJID} ({SEX})". | Derived | ||
| ADSL | WTMAX | Maximum Collected Weight | numeric | Aggregate MAX(WT.WT) over records matching on USUBJID. | Derived | ||
| ADSL | LASTWT | Latest Collected Weight | numeric | Take WT from the last WT record matching on USUBJID, ordered by WT.WTDTC, and a row with no match is an error. | 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