Reject an older submission format for sponsor-defined records

Review ask

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 means

README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: carry examination sequence (ZESEQ) and name (ZETERM) in a sponsor-defined domain and request its submission metadata.

Input: an electronic case report form export lists each subject's examination records with a sequence number and the recorded examination name.

Variables:

ZESEQ identifies the examination record within the subject.
ZETERM carries the examination name as recorded.

Note: the dataset builds, but Define-XML 2.0 cannot represent its declared sponsor-defined status. The submission is refused before its metadata or transport file is published.

How to fix

Use a submission format that preserves the sponsor-defined status, without claiming that this custom dataset follows an implementation-guide definition:

sdtm:
  define_version: '2.1.11'

Keep submission.non_standard: true on the custom dataset. The section's transport request and the collected name's annotated-form reference remain.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: value_not_permitted
rule: DEFINE-25

expected/error.yaml

phase: validation
condition: value_not_permitted
rule: DEFINE-25
spec_paths: [datasets.ZE.submission.non_standard]
context:
  detail: 'schema_violation: Define-XML 2.0 representation'
  value: 2.0 has no IsNonStandard declaration

YAML specification

1 spec file

spec.yaml

Edit75 lines

1yamaa: "1.0"2type: spec3model: SDTM4domain: ZE5keys: [STUDYID, USUBJID, ZESEQ]6input:7  EYE_RAW: {path: input/examinations.csv, types: {SEQ: int}}89output:10  path: ze.csv11  columns: [DOMAIN, STUDYID, USUBJID, ZESEQ, ZETERM]1213columns:14  - name: DOMAIN15    type: str16    label: Domain Abbreviation17    derivation: "'ZE'"18    submission:19      core: Req20      role: Identifier21      length: 222      origins: [{type: Assigned, source: Sponsor}]2324  - name: STUDYID25    type: str26    label: Study Identifier27    derivation: "'NS01'"28    submission:29      core: Req30      role: Identifier31      length: 432      origins: [{type: Protocol, source: Sponsor}]3334  - name: USUBJID35    type: str36    label: Unique Subject Identifier37    derivation: EYE_RAW.USUBJID38    submission:39      core: Req40      role: Identifier41      length: 742      origins: [{type: Assigned, source: Sponsor}]4344  - name: ZESEQ45    type: int46    label: Sequence Number47    derivation: EYE_RAW.SEQ48    submission:49      core: Req50      role: Identifier51      length: 852      origins: [{type: Assigned, source: Sponsor}]5354  - name: ZETERM55    type: str56    label: Examination Name57    derivation: EYE_RAW.TERM58    submission:59      core: Req60      role: Topic61      length: 1062      origins:63      - type: Collected64        source: Investigator65        documents:66        - document: acrf67          pages: {type: PhysicalRef, refs: '1'}6869submission:70  label: Eye Examinations71  domain: ZE72  class: FINDINGS73  structure: One record per examination per subject74  repeating: true75  non_standard: true

Inputs

Under review1 source file

input/examinations.csv

Edit2 rows

input/examinations.csv
USUBJID	SEQ	TERM
	1	Slit lamp
	1	Fundoscopy

Unexpected Output

Under review2 rows presented to the failing check - not an accepted artifact

expected/ze.csv

Edit2 rows

expected/ze.csv
DOMAIN	STUDYID	USUBJID	ZESEQ	ZETERM
ZE	NS01		1	Slit lamp
ZE	NS01		1	Fundoscopy

Shaded columns are derived— = missing value

Human review and assessment

Variable Name	Variable Label	Type	Length	Origin	Core	Conversion Definition	Variable Type	Variable Order
DOMAIN	Domain Abbreviation	Char	2	Assigned	Req	Set constant value "ZE".	SDTM	1
STUDYID	Study Identifier	Char	4	Protocol	Req	Set constant value "NS01".	SDTM	2
USUBJID	Unique Subject Identifier	Char	7	Assigned	Req	Copy value from EYE_RAW.USUBJID.	SDTM	3
ZESEQ	Sequence Number	Num	8	Assigned	Req	Copy value from EYE_RAW.SEQ.	SDTM	4
ZETERM	Examination Name	Char	10	Collected	Req	Copy value from EYE_RAW.TERM.	SDTM	5

Version	Date	Author	Description
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

How to fix

input/examinations.csv

expected/ze.csv

Your review

Mapping spec