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: build analysis records for laboratory tests carrying
SEX, AVAL, and ANRHI, with the upper limit chosen for each
test and sex.
Input: collected laboratory results carrying the collected
result (LBSTRESN), test code (LBTESTCD), and sex (SEX),
plus a reference table of upper limits by test code and sex.
Variables:
SEXwould hold the sex the limit is chosen by, copied from the collected record.AVALwould hold the collected result, copied fromLBSTRESN.ANRHIwould hold the upper limit of normal for that test and sex, taken from the reference table for the matching test code andSEX; missing when no row matches or the sex is missing.
Note: the name the study reads for the reference table,
input/lbref.csv, is a symbolic link: a stand-in that points at
another file. Where it points can be changed without changing the
study, so the limits that were reviewed and the limits that are
read need not be the same. The run is rejected before any data is
read and no artifact is accepted.
How to fix
Read the limits under the name that holds them:
input:
LBREF:
path: input/reference/lbref.csv
Storing the file itself where the study reads it works equally well. Either way one name reaches one file, and reviewing the study is reviewing what it reads.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- resource_path_symlink
- requirement
- REQ-0783
expected/error.yaml
phase: validation
condition: resource_path_symlink
spec_paths:
- input.LBREF.path
requirement: REQ-0783
context:
dataset: LBREF
path: input/lbref.csv
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