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: submit the demographics domain with its data definition, the sex
(SEX) traced to the case report form it was collected on.
Input: collected demographics, one record per subject.
Variables:
DOMAINisDMon every record.SEXis the sex as the investigator collected it.
Note: the sex was collected by the investigator, so the data definition must point a reviewer to the page of the annotated case report form that collected it. The study declares no annotated case report form, so the submission is refused before any document is written; the dataset itself still builds.
How to fix
Declare the study's annotated case report form in the section, and point the collected value at its page:
sdtm:
documents:
- id: ACRF
kind: annotated_crf
link: acrf.pdf
title: Annotated Case Report Form
origins:
- type: Collected
source: Investigator
documents:
- document: ACRF
pages: {type: PhysicalRef, refs: "3"}
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- origin_document_missing
- rule
- DEFINE-14
expected/error.yaml
phase: validation
condition: origin_document_missing
spec_paths:
- sdtm.specs[0].columns.SEX.submission.origins[0]
rule: DEFINE-14
Inputs
Under review1 source fileinput/dm_raw.csv
Edit2 rows| STUDYID | USUBJID | SEX |
|---|---|---|
| PAR01 | F | |
| PAR01 | M |
Unexpected Output
Under review2 rows presented to the failing check - not an accepted artifactexpected/dm.csv
Edit2 rows| DOMAIN | STUDYID | USUBJID | SEX |
|---|---|---|---|
| DM | PAR01 | F | |
| DM | PAR01 | 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 | 5 | Protocol | Req | Copy value from RAW.STUDYID. | SDTM | 2 | ||
| USUBJID | Unique Subject Identifier | Char | 9 | Assigned | Req | Copy value from RAW.USUBJID. | SDTM | 3 | ||
| SEX | Sex | Char | 1 | Collected | Req | Copy value from RAW.SEX. | 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 |