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 the systolic blood pressure (SYSBP) forward so
the prior systolic pressure (PRIORBP) holds the closest earlier
taken pressure for the same subject.
Input: collected vital signs records, each holding a systolic
blood pressure (SYSBP); the value is missing when the
measurement was not taken.
Variables:
PRIORBPwould hold the closest earlier taken pressure for the same subject, in sequence-number order, and be missing when no earlier pressure was taken.
Note: the carried value arrives as the fixed number 120
instead of a variable to search, so the run is rejected before any
data is read and no artifact is accepted.
How to fix
Decide which earlier measurement the study carries, then name the variable that holds it. When the closest earlier taken pressure is the rule, search the pressure variable itself:
- name: PRIORBP
type: int
derivation:
previous_non_missing:
source: SYSBP
window:
group_by: [STUDYID, USUBJID]
order_by: [VSSEQ]
When every gap should instead read a fixed fallback, state that as a separate rule over the carried result rather than inside the search.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_field_type
- requirement
- REQ-0287
expected/error.yaml
phase: validation
condition: invalid_field_type
spec_paths:
- columns.PRIORBP.derivation.previous_non_missing.source
requirement: REQ-0287
context:
expected: variable
actual: mapping
Inputs
Under review1 source fileinput/vs.csv
Edit3 rows| STUDYID | USUBJID | VSSEQ | SYSBP |
|---|---|---|---|
| PILOT7 | 1 | 128 | |
| PILOT7 | 2 | — | |
| PILOT7 | 3 | 132 |
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 |
|---|---|---|---|---|---|---|---|
| ADVS | STUDYID | Study Identifier | character | Copy value from VS.STUDYID. | Predecessor | ||
| ADVS | USUBJID | Unique Subject Identifier | character | Copy value from VS.USUBJID. | Predecessor | ||
| ADVS | VSSEQ | Sequence Number | numeric | Copy value from VS.VSSEQ. | Predecessor | ||
| ADVS | SYSBP | Systolic Blood Pressure | numeric | Copy value from VS.SYSBP. | Predecessor | ||
| ADVS | PRIORBP | Prior Systolic Blood Pressure | numeric | Most recent non-missing {'literal': 120} from an earlier row within each group of STUDYID, USUBJID, ordered by VSSEQ. | 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