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 recorded sex (SEX) for each subject from
collected demographics, accepting only the study codes M and F.
Input: collected demographics with study and subject
identifiers and recorded sex (SEX).
Variables:
SEXis the subject's recorded sex, copied from collectedSEX, and blank when none was recorded. Only the exact codesMandFare recognized, so a lowercasem, anX, or aUis not accepted.
A code the study does not recognize rejects the run at the final check, after the values are derived, so no artifact is accepted.
How to fix
Correct the offending records at collection: m, X, and U are
not codes the study defines, so query the sites for the subjects'
sex. Widen the accepted codes only when the study genuinely admits
another value, such as U for unknown:
verifications:
- allowed_values:
values: [M, F, U]
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- verification
- condition
- allowed_values_failed
- rule
- CHECK-6
expected/error.yaml
phase: verification
condition: allowed_values_failed
spec_paths:
- columns.SEX.verifications[0].allowed_values
rule: CHECK-6
context:
column: SEX
failure_count: 3
keys:
- STUDYID: YAMAA-01
USUBJID: YAMAA-01-104
- STUDYID: YAMAA-01
USUBJID: YAMAA-01-105
- STUDYID: YAMAA-01
USUBJID: YAMAA-01-106
Inputs
Under review1 source fileinput/dm.csv
Edit6 rows| STUDYID | USUBJID | SEX |
|---|---|---|
| YAMAA-01 | M | |
| YAMAA-01 | F | |
| YAMAA-01 | — | |
| YAMAA-01 | m | |
| YAMAA-01 | X | |
| YAMAA-01 | U |
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 |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Copy value from DM.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | SEX | Sex | character | M, F | Copy value from DM.SEX. | Predecessor |
| Variable | Permitted values |
|---|---|
| SEX | M, F |
| 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 |