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: attempt one record per subject and laboratory test
carrying the collected result in AVAL and the upper limit of
normal for that test and the subject's sex in ANRHI.
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 be the collected sex, taken fromSEXin the collected records, and also chooses the limit.AVALwould be the collected numeric result, taken fromLBSTRESN.ANRHIwould be the upper limit of normal from the reference table for the record's test code and sex; missing when the table has no limit for that pair or the sex is missing.
Note: the reference table is named by a web address,
https://reference.example.org/limits/lbref.csv, whose contents
depend on when it is fetched and on who fetches it, so two runs of
one study could read different limits while recording the same
request. A run opens only stored files, never a web address, so
the run is rejected before any data is read and no artifact is
accepted.
How to fix
Fetch the governed limits once, record which version was received, and store that copy with the study:
input:
LBREF:
path: input/lbref.csv
Retrieval belongs to the step that assembles study data, where the received version can be recorded and reviewed. It is not part of building the analysis dataset.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- resource_path_uri_scheme
- requirement
- REQ-0775
expected/error.yaml
phase: validation
condition: resource_path_uri_scheme
spec_paths:
- input.LBREF.path
requirement: REQ-0775
context:
dataset: LBREF
path: https://reference.example.org/limits/lbref.csv
Inputs
Under review1 source fileinput/lb.csv
Edit2 rows| STUDYID | USUBJID | LBTESTCD | SEX | LBSTRESN |
|---|---|---|---|---|
| PILOT7 | ALT | F | 42 | |
| PILOT7 | ALT | M | 58 |
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 | 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 |
yamaa
Comments
Signed in with GitHub; saved in repository Discussions