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: build the unique subject identifier (USUBJID) from the study,
the site and the subject number, beside the sex (SEX).
Input: collected demographics with one record per subject; one subject's site was not recorded.
Variables:
USUBJIDwould be the study, the site and the subject number joined by hyphens, such asCTX-701-0001.SUBJID,SITEIDandSEXare the subject number, the site and the sex as collected.
Without its site, the second subject's identifier would be incomplete. Leaving the site out, or writing a stand-in for it, would give an identifier that could clash with another subject's or name no site at all. The run is rejected, and no artifact is accepted.
How to fix
Find the site the subject enrolled at in the source, and export the record again with it:
STUDYID,SITEID,SUBJID,SEX
CTX,701,0001,F
CTX,703,0002,M
CTX,702,0003,F
Do not invent a site for the identifier: it is only as reliable as the values it is built from.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- mapping
- condition
- missing_input
- rule
- COLUMN-10
expected/error.yaml
phase: mapping
condition: missing_input
spec_paths:
- columns.USUBJID.derivation.str_template
rule: COLUMN-10
context:
variable: DM_RAW.SITEID
Inputs
Under review1 source fileinput/dm_raw.csv
Edit3 rows| STUDYID | SITEID | SUBJID | SEX |
|---|---|---|---|
| CTX | 701 | 0001 | F |
| CTX | — | 0002 | M |
| CTX | 702 | 0003 | F |
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 "DM". | SDTM | 1 | ||||
| STUDYID | Study Identifier | Char | Collected | Copy value from DM_RAW.STUDYID. | SDTM | 2 | ||||
| USUBJID | Unique Subject Identifier | Char | Derived | Fill the template "{DM_RAW.STUDYID}-{DM_RAW.SITEID}-{DM_RAW.SUBJID}". | SDTM | 3 | ||||
| SUBJID | Subject Identifier for the Study | Char | Collected | Copy value from DM_RAW.SUBJID. | SDTM | 4 | ||||
| SITEID | Study Site Identifier | Char | Collected | Copy value from DM_RAW.SITEID. | SDTM | 5 | ||||
| SEX | Sex | Char | Collected | Copy value from DM_RAW.SEX. | 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 |