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 each vital-signs result as collected (VSORRES) for each
subject and test, with a description of each test's results for the
data-definition document.
Input: collected vital signs with the study and subject identifiers, one record per subject and test, with the test code and the result as collected.
Variables:
VSTESTCDis the vital-signs test code, one of the codes the study's test-code terminology lists:SYSBP,DIABPorPULSE.VSORRESwould be the result as collected.
Note: each test's results have their own description, which finds its
records by their test code. A record can carry only a code the terminology
lists, so a description that names any other code could never describe a
record. The pulse description names HR, a code the study's terminology
does not list, and the run is refused before any record is read.
How to fix
Decide which test the description is for. It describes the pulse rate,
which the study records under the code PULSE, so name that code:
- id: PULSE
where: {VSTESTCD: [PULSE]}
label: Pulse Rate
When the study also records heart rate as a test of its own, add HR to
the study's test-code list and give it its own description instead. HR is
a published test code, so it is an ordinary item; only a code the published
list lacks is a sponsor addition, declared with extended: true.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- value_level_where_invalid
- rule
- SUB-12
expected/error.yaml
phase: validation
condition: value_level_where_invalid
spec_paths:
- columns.VSORRES.submission.value_level.PULSE.where.VSTESTCD
rule: SUB-12
context:
column: VSORRES
entry: PULSE
reason: not_in_codelist
where_column: VSTESTCD
Inputs
Under review1 source fileinput/vs_raw.csv
Edit3 rows| STUDYID | USUBJID | VSTESTCD | VSORRES |
|---|---|---|---|
| YAMAA-01 | SYSBP | 120 | |
| YAMAA-01 | DIABP | 80 | |
| YAMAA-01 | PULSE | 72 |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| STUDYID | Study Identifier | Char | Collected | Copy value from VS_RAW.STUDYID. | SDTM | 1 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from VS_RAW.USUBJID. | SDTM | 2 | ||||
| VSTESTCD | Vital Signs Test Short Name | Char | Vital Signs Test Code | Assigned | Copy value from VS_RAW.VSTESTCD. | SDTM | 3 | |||
| VSORRES | Result or Finding in Original Units | Char | Collected | Copy value from VS_RAW.VSORRES. | SDTM | 4 |
| Codelist ID | Name | Value | Decode | Codelist NCI alias | Value NCI alias | Extensible | Extended value | SAS format | Dictionary | Version |
|---|---|---|---|---|---|---|---|---|---|---|
| VSTESTCD | Vital Signs Test Code | SYSBP | Systolic Blood Pressure | Yes | ||||||
| VSTESTCD | Vital Signs Test Code | DIABP | Diastolic Blood Pressure | Yes | ||||||
| VSTESTCD | Vital Signs Test Code | PULSE | Pulse Rate | Yes |
| 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 |