yamaa 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
EditUnder reviewWhat this benchmark meansREADME.mdGoal: pin the lookup filter machinery: a filter that reads the current planned visit and so changes which donor record a lookup resolves to, with qualified donor fields, an ordering, and keep-last selection.
Input: PLAN carries the planned visits per subject; LB
carries lab records, one with a missing result and one outside the
planned visit list.
Lookup: the DONOR intermediate implements
last-observation-carried-forward. For each planned visit it keeps the
subject's latest lab record whose result is present and whose visit
number does not exceed the planned visit's. The filter compares each
lab record with the current planned visit's number while the lab fields
stay qualified with the lookup dataset; the eligible records sort by
visit number and the last is kept. A record with a missing result never
qualifies, so its planned visit carries the earlier value forward; a
lab record at an unplanned visit still qualifies by its visit number
and can serve a later planned visit. A planned visit earlier than every
lab record with a result finds no donor, so its result and day are
missing.
Columns: VISIT names the planned visit at visit number
VISITN; the carried-forward lab result and day land in AVAL and
LBDY.
Inputs
Under review2 source filesExpected output
Under review7 expected rowsexpected/adlb.csv
Edit7 rows| STUDYID | USUBJID | VISIT | VISITN | AVAL | LBDY |
|---|---|---|---|---|---|
| YAMAA-01 | BASELINE | 0 | 10.5 | 1 | |
| YAMAA-01 | WEEK 1 | 1 | 10.5 | 1 | |
| YAMAA-01 | WEEK 2 | 2 | 12 | 15 | |
| YAMAA-01 | WEEK 4 | 4 | 11 | 22 | |
| YAMAA-01 | BASELINE | 0 | — | — | |
| YAMAA-01 | WEEK 1 | 1 | 9 | 8 | |
| YAMAA-01 | WEEK 2 | 2 | 9.5 | 15 |
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADLB | STUDYID | Study Identifier | character | Set constant value "YAMAA-01". | Assigned | ||
| ADLB | USUBJID | Unique Subject Identifier | character | Copy value from PLAN.USUBJID. | Predecessor | ||
| ADLB | VISIT | Visit Name | character | Copy value from PLAN.VISIT. | Predecessor | ||
| ADLB | VISITN | Visit Number | numeric | Copy value from PLAN.VISITN. | Predecessor | ||
| ADLB | AVAL | Analysis Value | numeric | Take LBSTRESN from the last LB record matching on USUBJID, where LB.LBSTRESN IS NOT NULL AND LB.VISITN <= PLAN.VISITN, ordered by LB.VISITN, and no match yields blank. | Derived | ||
| ADLB | LBDY | Analysis Relative Day | numeric | Take LBDY from the last LB record matching on USUBJID, where LB.LBSTRESN IS NOT NULL AND LB.VISITN <= PLAN.VISITN, ordered by LB.VISITN, and no match yields blank. | 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 |
Comments
Signed in with GitHub; saved in repository Discussions