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: give each questionnaire its treatment period (APERIOD), next to
where it was completed (SOURCE), its sequence number (QSSEQ) and its date
(QSDT).
Input: questionnaires completed at clinic visits, questionnaires completed on an electronic patient-reported outcome (ePRO) device, which store their fields in a different order, and a table giving each subject's treatment periods, each from a first to a last day.
Variables:
SOURCEwould beCLINICfor a questionnaire completed at a visit andEPROfor one completed on the device.APERIODwould be the number of the subject's period whose first and last days, both inclusive, hold the questionnaire's own date, and blank when no period does.
Note: a device questionnaire is placed by a value of the device row itself: a field of the device record the row was built from, or a column built for that row. The date is taken from a clinic record instead, which a device row does not have, so the run is rejected before any data is read; no artifact is accepted.
How to fix
Decide which date places a device questionnaire; usually it is the date the device recorded. Read that date from the device record the row is built from, as the clinic template reads its own record:
between: {value: EPRO.QSDT, lower: APERSDT, upper: APEREDT}
Or name the column QSDT, which each template already fills from its own
record: a bare name reads that column of the row.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- unknown_field
- rule
- LOOKUP-9
expected/error.yaml
phase: validation
condition: unknown_field
spec_paths:
- rows.epro.derivations.APERIOD.source.between.value
rule: LOOKUP-9
context:
identifier: CLINIC.QSDT
variable: PERIODS.APERIOD
Inputs
Under review3 source filesinput/clinic.csv
Edit3 rows| STUDYID | USUBJID | QSSEQ | VISIT | QSDT |
|---|---|---|---|---|
| YAMAA-01 | 1 | PERIOD 1 DAY 1 | 2025-01-01 | |
| YAMAA-01 | 2 | PERIOD 2 DAY 1 | 2025-02-01 | |
| YAMAA-01 | 1 | PERIOD 1 DAY 1 | 2025-03-01 |
input/epro.csv
Edit3 rows| STUDYID | USUBJID | QSDT | QSSEQ |
|---|---|---|---|
| YAMAA-01 | 2025-01-31 | 3 | |
| YAMAA-01 | 2025-03-05 | 4 | |
| YAMAA-01 | — | 5 |
input/periods.csv
Edit3 rows| STUDYID | USUBJID | APERIOD | APERSDT | APEREDT |
|---|---|---|---|---|
| YAMAA-01 | 1 | 2025-01-01 | 2025-01-31 | |
| YAMAA-01 | 2 | 2025-02-01 | 2025-02-28 | |
| YAMAA-01 | 1 | 2025-03-01 | — |
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 |
|---|---|---|---|---|---|---|---|
| ADQS | STUDYID | Study Identifier | character | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADQS | USUBJID | Unique Subject Identifier | character | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADQS | SOURCE | Questionnaire Source | character | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADQS | QSSEQ | Sequence Number | numeric | Set per constructed row; see the Row construction sheet. | Derived | ||
| ADQS | QSDT | Date of Questionnaire | numeric | ISO 8601 | Set per constructed row; see the Row construction sheet. | Derived | |
| ADQS | APERIOD | Period | numeric | Set per constructed row; see the Row construction sheet. | Derived |
| Template | Include when | STUDYID | USUBJID | SOURCE | QSSEQ | QSDT | APERIOD |
|---|---|---|---|---|---|---|---|
| clinic | Copy CLINIC.STUDYID | Copy CLINIC.USUBJID | Constant "CLINIC" | Copy CLINIC.QSSEQ | Copy CLINIC.QSDT | Copy PERIODS.APERIOD | |
| epro | Copy EPRO.STUDYID | Copy EPRO.USUBJID | Constant "EPRO" | Copy EPRO.QSSEQ | Copy EPRO.QSDT | Copy PERIODS.APERIOD |
| 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 |