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 sex and the collected result into the output and
attach the upper limit of normal (ANRHI) chosen by test and sex.
Input: laboratory records carrying test code (LBTESTCD), sex
(SEX), and collected result (LBSTRESN), plus a limit table
carrying test code, sex, and upper limit (ANRHI).
Variables:
ANRHIwould be the upper limit of normal taken from the limit table where the test matches the collected test and the sex matches the carried sex.
Note: when the carried sex is blank, the pair that chooses a limit is incomplete and no entry can be looked for, so the run is rejected with no artifact accepted. Falling back to either sex, or to a combined limit, would answer with a range the study never stated.
How to fix
Recover and correct the missing sex when possible. If the intended result is a missing reference limit whenever any lookup input is missing, declare the lookup's missing-value answer:
intermediates:
- id: LBREF_LOOKUP
dataset: LBREF
key: {LBTESTCD: PARAMCD, SEX: SEX}
no_match: null
That one answer also covers a complete test and sex that the reference table does not list: both find no entry (REQ-0129, REQ-0131).
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- join
- condition
- unmatched_key
- requirement
- REQ-0124
expected/error.yaml
phase: join
condition: unmatched_key
spec_paths:
- intermediates[0]
requirement: REQ-0124
context:
intermediate: LBREF_LOOKUP
dataset: LBREF
key:
- LBTESTCD
- SEX
intermediate_key:
LBTESTCD: ALT
SEX:
keys:
- STUDYID: PILOT7
USUBJID: P7-852
PARAMCD: ALT
Inputs
Under review2 source filesUnexpected 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 | PARAMCD | Parameter Code | character | Copy value from LB.LBTESTCD. | Predecessor | ||
| ADLB | SEX | Sex | character | Copy value from LB.SEX. | Predecessor | ||
| ADLB | AVAL | Analysis Value | numeric | Copy value from LB.LBSTRESN. | Predecessor | ||
| ADLB | ANRHI | Analysis Normal Range Upper Limit | numeric | Take ANRHI from the LBREF record whose LBTESTCD equals PARAMCD and SEX equals SEX, 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 |
Comments
Signed in with GitHub; saved in repository Discussions