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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: submit DM in a SAS transport file.
Input: one row per subject carrying the site, age and sex.
Variables:
SITEID,AGEandSEXare as collected.
Note: a submitted variable label has at most 40 characters, so the submission stops before any file is written; no label is shortened.
How to fix
Use the label the implementation guide publishes, Sex, and keep any longer
explanation in a comment, which the data-definition document carries in full:
- name: SEX
type: str
label: Sex
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- transport_label_invalid
- rule
- XPT-5
expected/error.yaml
phase: validation
condition: transport_label_invalid
spec_paths:
- sdtm.specs[0].columns.SEX.label
rule: XPT-5
context:
dataset: DM
column: SEX
label: Sex of the Subject as Collected on the Form
cause: length
Inputs
Under review1 source fileinput/dm_raw.csv
Edit2 rows| STUDYID | USUBJID | SUBJID | SITEID | AGE | SEX |
|---|---|---|---|---|---|
| CATH | 0001 | UCSD | 34 | F | |
| CATH | 0002 | UCSD | 67 | M |
Unexpected Output
Under review2 rows presented to the failing check - not an accepted artifactexpected/dm.csv
Edit2 rows| DOMAIN | STUDYID | USUBJID | SUBJID | SITEID | AGE | SEX |
|---|---|---|---|---|---|---|
| DM | CATH | 0001 | UCSD | 34 | F | |
| DM | CATH | 0002 | UCSD | 67 | M |
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 | 2 | Assigned | Req | Set constant value "DM". | SDTM | 1 | ||
| STUDYID | Study Identifier | Char | 20 | Protocol | Req | Copy value from DM_RAW.STUDYID. | SDTM | 2 | ||
| USUBJID | Unique Subject Identifier | Char | 30 | Assigned | Req | Copy value from DM_RAW.USUBJID. | SDTM | 3 | ||
| SUBJID | Subject Identifier for the Study | Char | 10 | Collected | Req | Copy value from DM_RAW.SUBJID. | SDTM | 4 | ||
| SITEID | Study Site Identifier | Char | 10 | Collected | Req | Copy value from DM_RAW.SITEID. | SDTM | 5 | ||
| AGE | Age | Num | 3 | Collected | Exp | Copy value from DM_RAW.AGE. | SDTM | 6 | ||
| SEX | Sex of the Subject as Collected on the Form | Char | 1 | Collected | Req | Copy value from DM_RAW.SEX. | SDTM | 7 |
| 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 |
yamaa