Reject a Codelist That Lists a Value Twice

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: build the demographics domain with each subject's sex (SEX), restricted to the values of the study's sex codelist.

Input: collected demographics, one record per subject, and the study's codelists in the project file.

Variables:

DOMAIN is DM on every record.
SEX would be the sex as collected, one of the codelist's values.

Note: the sex codelist lists F twice. A codelist is a set of distinct values, each with one place in the list, so a repeated value makes it unclear which entry a reader should take, and the run is rejected before any data is read; no artifact is accepted.

How to fix

List each value once:

- id: SEX
  name: Sex
  items:
    - value: F
    - value: M

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: codelist_duplicate_value
rule: CT-4

expected/error.yaml

phase: validation
condition: codelist_duplicate_value
spec_paths:
  - codelists[0].codelists[0].items[2].value
rule: CT-4
context:
  codelist: SEX
  value: F

YAML specification

1 spec file

spec.yaml

Edit67 lines

1yamaa: "1.0"2type: spec3model: SDTM4domain: DM5keys: [STUDYID, USUBJID]6input:7  RAW: input/dm_raw.csv89output:10  path: dm.csv11  columns: [DOMAIN, STUDYID, USUBJID, SEX]1213columns:14  - name: DOMAIN15    type: str16    label: Domain Abbreviation17    derivation: "'DM'"18    submission:19      core: Req20      role: Identifier21      length: 222      origins:23        - type: Assigned24          source: Sponsor2526  - name: STUDYID27    type: str28    label: Study Identifier29    derivation: RAW.STUDYID30    submission:31      core: Req32      role: Identifier33      length: 834      origins:35        - type: Protocol36          source: Sponsor3738  - name: USUBJID39    type: str40    label: Unique Subject Identifier41    derivation: RAW.USUBJID42    submission:43      core: Req44      role: Identifier45      length: 1246      origins:47        - type: Assigned48          source: Sponsor4950  - name: SEX51    type: str52    label: Sex53    derivation: RAW.SEX54    submission:55      core: Req56      role: Record Qualifier57      length: 158      codelist: SEX59      origins:60        - type: Collected61          source: Investigator6263submission:64  label: Demographics65  class: SPECIAL PURPOSE66  structure: One record per subject67  repeating: false

Inputs

Under review1 source file

input/dm_raw.csv

Edit2 rows

input/dm_raw.csv
STUDYID	USUBJID	SEX
YAMAA-01		F
YAMAA-01		M

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Variable Name	Variable Label	Type	Length	Controlled Terms or Format	Origin	Core	Conversion Definition	Variable Type	Variable Order
DOMAIN	Domain Abbreviation	Char	2		Assigned	Req	Set constant value "DM".	SDTM	1
STUDYID	Study Identifier	Char	8		Protocol	Req	Copy value from RAW.STUDYID.	SDTM	2
USUBJID	Unique Subject Identifier	Char	12		Assigned	Req	Copy value from RAW.USUBJID.	SDTM	3
SEX	Sex	Char	1	Sex	Collected	Req	Copy value from RAW.SEX.	SDTM	4

Codelist ID	Name	Value	Extensible
SEX	Sex	F	No
SEX	Sex	M	No
SEX	Sex	F	No

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/dm_raw.csv

Your review

Mapping spec