yamaa As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. Agreeing with both approves this benchmark; disagreeing with either needs a comment. Propose a fix with the Edit button on any source file, or add it to your comments.
We suggest spending no more than 5 minutes on a review. The other tabs beside Your review are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: 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 sex the limits are chosen by, copied from the collected record.AVALwould be the collected result, copied fromLBSTRESN.ANRHIwould be the upper limit of normal for that test and sex, found by matching the collected test code andSEXagainst the reference table; missing when the table has no limit for that pair or the sex is missing.
Note: the limits are named as the folder input/lbref rather
than a table file. A folder holds whatever is added to it, so the
limits a run would read depend on what happens to be filed there,
and two runs of one study could disagree. The run is rejected
before any data is read and no artifact is accepted.
How to fix
Decide which reviewed table the study was approved against. When limits arrive as several files, combine them into one reviewed table first, then name that table instead of the folder that holds it:
input:
LBREF: input/lbref/limits.csv
A study reads the table it was approved against, not a folder that grows.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- resource_path_not_regular_file
- rule
- FILE-7
expected/error.yaml
phase: validation
condition: resource_path_not_regular_file
spec_paths:
- input.LBREF.path
rule: FILE-7
context:
dataset: LBREF
path: input/lbref
Inputs
Under review2 source filesUnexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| 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.7 | 2026-10-20 | yamaa docs build | Read a specification in the 1.0 surface as its 0.5 counterpart; state that missing values stay missing where a mapping declares no missing handler, and leave out a declared missing answer that restates a handler's default | ||
| 1.6 | 2026-10-17 | yamaa docs build | Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight | ||
| 1.5 | 2026-10-17 | yamaa docs build | Name collected precision in words instead of letter codes; state imputation fallbacks, minimum source precision, bounds ignored outside the collected period, and invalid text with no handler as an error; describe date and datetime shifts, imputation flag codes, and partial text giving no date part | ||
| 1.4 | 2026-10-15 | yamaa docs build | State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks | ||
| 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 |