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: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
- Inputs: Do they trigger the failure for the reason the summary gives?
- Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?
The other tabs beside Comments are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdGoal: carry the numeric result (LBSTRESN) and the baseline
flag (LBBLFL) as collected, and repeat the baseline value (BAVL)
on every row for the subject.
Input: collected lab (LB) records, each with a numeric result
(LBSTRESN) and a baseline flag (LBBLFL) holding Y on the
baseline record.
Variables:
BAVL: the baseline value, taken from the subject's row flaggedYinLBBLFLand repeated on every row for that subject; missing when the subject has no flagged row.
Note: the run is rejected when a subject has more than one
record flagged Y: no single baseline value exists, so no artifact
is accepted.
How to fix
Keep exactly one baseline record per subject. Either clear the flag in the
collected data on the visit that is not the baseline, for example WEEK 1:
STUDYID,USUBJID,VISIT,LBSTRESN,LBBLFL
PILOT7,P7-901,SCREENING,5.1,Y
PILOT7,P7-901,WEEK 1,5.4,
PILOT7,P7-901,WEEK 2,5.2,
or, when both visits genuinely qualify, pick one by rule (for example the earliest) and flag only that row before deriving.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- derivation
- condition
- aggregate_multiple_records
- requirement
- REQ-0501
expected/error.yaml
phase: derivation
condition: aggregate_multiple_records
spec_paths:
- columns.BAVL.derivation.aggregate
requirement: REQ-0501
context:
reducer: ONLY
record_count: 2
Inputs
Under review1 source fileinput/lb.csv
Edit3 rows| STUDYID | USUBJID | VISIT | LBSTRESN | LBBLFL |
|---|---|---|---|---|
| PILOT7 | SCREENING | 5.1 | Y | |
| PILOT7 | WEEK 1 | 5.4 | Y | |
| PILOT7 | WEEK 2 | 5.2 | — |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADLB | STUDYID | Study Identifier | character | Copy value from LB.STUDYID. | Predecessor | ||
| ADLB | USUBJID | Unique Subject Identifier | character | Copy value from LB.USUBJID. | Predecessor | ||
| ADLB | VISIT | Visit Name | character | Copy value from LB.VISIT. | Predecessor | ||
| ADLB | LBSTRESN | Numeric Result | numeric | Copy value from LB.LBSTRESN. | Predecessor | ||
| ADLB | LBBLFL | Baseline Flag | character | Copy value from LB.LBBLFL. | Predecessor | ||
| ADLB | BAVL | Baseline Value | numeric | Aggregate ONLY(LBSTRESN) over records grouped by STUDYID, USUBJID, matching on the shared output keys, where LBBLFL = 'Y'. | 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