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
README.mdGoal: attach the reference-range upper limit (LBSTNRHI) to
each collected result, carrying its test code and sex.
Input: collected results carrying test code (LBTESTCD), sex
(SEX), and numeric result (LBSTRESN), plus a reference-limit
table carrying the upper limit (NRHI) by test code and sex.
Variables:
LBSTNRHIwould contain the upper limit value from the reference-limit table for the test code and sex of the result.
Note: the lookup names three limit-table columns, and each listed
column matches the same-named current-row value. The collected results
carry no unit, so the UNIT column would match against nothing. The
unknown current-row value is rejected before any data is read; no artifact
is accepted.
How to fix
If the limit table holds one unit per test code, match on test code and sex alone, since the collected results carry no unit:
intermediates:
- id: REFRANGE
dataset: LBRANGE
key: [LBTESTCD, SEX]
When a current-row name differs from the table's, map the table column to
it, as in key: {LBTESTCD: PARAMCD, SEX: SEX}.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- unknown_field
- requirement
- REQ-0117
expected/error.yaml
phase: validation
condition: unknown_field
spec_paths:
- intermediates[0].key
requirement: REQ-0117
context:
identifier: UNIT
intermediate: REFRANGE
Inputs
Under review2 source filesUnexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| STUDYID | Study Identifier | Char | Collected | Copy value from LB_RAW.STUDYID. | SDTM | 1 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from LB_RAW.USUBJID. | SDTM | 2 | ||||
| LBSEQ | Sequence Number | Num | Collected | Copy value from LB_RAW.LBSEQ. | SDTM | 3 | ||||
| LBTESTCD | Lab Test or Examination Short Name | Char | Collected | Copy value from LB_RAW.LBTESTCD. | SDTM | 4 | ||||
| SEX | Sex | Char | Collected | Copy value from LB_RAW.SEX. | SDTM | 5 | ||||
| LBSTNRHI | Reference Range Upper Limit-Std Units | Num | Derived | Take NRHI from the LBRANGE record matching on LBTESTCD, SEX and UNIT, and a row with no match is an error. | SDTM | 6 |
| 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