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: write each administration's collected duration as ISO 8601
duration text (EXDUR).
Input: collected exposure records, one per administration (EXSEQ),
with the duration in whole minutes as the case report form collected it.
Variables:
EXDURwould hold the duration as ISO 8601 duration text, so 90 minutes givesPT1H30M. Only a number of minutes is written as a duration, and the collected minutes are still text that nothing has read as a number, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Declare the collected minutes a whole number where the input is read, so each value is checked as a number as the records are read:
input:
EX_RAW: {path: input/ex_raw.csv, types: {EXSEQ: int, EXDURMIN: int}}
Declare float instead when the form collects fractions of a minute; the
fraction is written as seconds, so 1.5 minutes gives PT1M30S.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- incompatible_input_type
- rule
- TIME-21
expected/error.yaml
phase: validation
condition: incompatible_input_type
spec_paths:
- columns.EXDUR.derivation.duration_text.source
rule: TIME-21
context:
source: EX_RAW.EXDURMIN
expected: numeric
actual: str
Inputs
Under review1 source fileinput/ex_raw.csv
Edit2 rows| STUDYID | USUBJID | EXSEQ | EXDURMIN |
|---|---|---|---|
| YAMAA-01 | 1 | 120 | |
| YAMAA-01 | 1 | 90 |
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 EX_RAW.STUDYID. | SDTM | 1 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from EX_RAW.USUBJID. | SDTM | 2 | ||||
| EXSEQ | Sequence Number | Num | Collected | Copy value from EX_RAW.EXSEQ. | SDTM | 3 | ||||
| EXDUR | Duration of Treatment | Char | Derived | Write EX_RAW.EXDURMIN, a number of minutes, as ISO 8601 duration text with days as the largest unit. | SDTM | 4 |
| 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 |