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: carry the vital-sign result (AVAL) for each subject and
parameter, with a description of the blood-pressure values for the
data-definition document.
Input: standardized vital signs, one record per subject and test, with the numeric result.
Variables:
PARAMCDis the vital-sign test code.AVALwould be the numeric result.
Note: each record may be described by at most one of a variable's value descriptions. Here one description covers both blood pressures and another covers diastolic pressure, so every diastolic record would have two descriptions, and the run is refused before any data is read.
How to fix
Decide which description a diastolic pressure should carry, and list each parameter in exactly one entry:
value_level:
- id: SYSBP
where: {PARAMCD: [SYSBP]}
label: Systolic Blood Pressure (mmHg)
- id: DIABP
where: {PARAMCD: [DIABP]}
label: Diastolic Blood Pressure (mmHg)
When the two blood pressures truly share their description, keep the single entry listing both and drop the diastolic one.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- value_level_overlap
- rule
- SUB-12
expected/error.yaml
phase: validation
condition: value_level_overlap
spec_paths:
- columns.AVAL.submission.value_level.BP.where
- columns.AVAL.submission.value_level.DIABP.where
rule: SUB-12
context:
column: AVAL
entries: [BP, DIABP]
Inputs
Under review1 source fileinput/vs.csv
Edit4 rows| USUBJID | VSTESTCD | VSSTRESN |
|---|---|---|
| SYSBP | 120 | |
| DIABP | 80 | |
| SYSBP | 135 | |
| DIABP | 85 |
Unexpected 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 |
|---|---|---|---|---|---|---|---|
| ADVS | USUBJID | Unique Subject Identifier | character | Copy value from VS.USUBJID. | Predecessor | ||
| ADVS | PARAMCD | Parameter Code | character | Copy value from VS.VSTESTCD. | Predecessor | ||
| ADVS | AVAL | Analysis Value | numeric | Copy value from VS.VSSTRESN. | Predecessor |
| 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 |