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: keep the questionnaire responses of one instrument as a dataset of
their own, named QS-PHQ9.
Input: collected questionnaire responses, one record per subject and question.
Variables:
DOMAINisQSon every record.QSSEQwould be the collected sequence number of the response.QSTESTCDwould be the short name of the question as collected.QSORRESwould be the response as collected.
Note: a dataset name holds only letters, digits and underscores, and
does not start with a digit, so that every reader and every transport format
can name it. QS-PHQ9 holds a hyphen, so the run is rejected before any data
is read and no artifact is accepted.
How to fix
Name the dataset with letters, digits and underscores only, and keep the instrument in the name without the hyphen:
domain: QSPH
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- pattern_mismatch
- rule
- SCHEMA-12
expected/error.yaml
phase: validation
condition: pattern_mismatch
spec_paths:
- domain
rule: SCHEMA-12
context:
value: QS-PHQ9
pattern: '^[A-Za-z_][A-Za-z0-9_]*$'
Inputs
Under review1 source fileinput/qs.csv
Edit3 rows| STUDYID | USUBJID | QSSEQ | QSTESTCD | QSORRES |
|---|---|---|---|---|
| YAMAA-01 | 1 | PHQ0101 | 2 | |
| YAMAA-01 | 2 | PHQ0102 | 1 | |
| YAMAA-01 | 1 | PHQ0101 | 0 |
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 |
|---|---|---|---|---|---|---|---|---|---|---|
| DOMAIN | Domain Abbreviation | Char | Assigned | Set constant value "QS". | SDTM | 1 | ||||
| STUDYID | Study Identifier | Char | Collected | Copy value from QS.STUDYID. | SDTM | 2 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from QS.USUBJID. | SDTM | 3 | ||||
| QSSEQ | Sequence Number | Num | Collected | Copy value from QS.QSSEQ. | SDTM | 4 | ||||
| QSTESTCD | Question Short Name | Char | Collected | Copy value from QS.QSTESTCD. | SDTM | 5 | ||||
| QSORRES | Finding in Original Units | Char | Collected | Copy value from QS.QSORRES. | SDTM | 6 |
| 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 |