Reject Duplicate SITEID

Review ask

As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.

Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
Inputs: Do they trigger the failure for the reason the summary gives?
Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?

The other tabs beside Comments are background for assessment, not under review.

Summary

EditUnder reviewWhat this benchmark means

README.md

Goal: build the analysis dataset with one record per subject carrying SITEID.

Input: collected demographics records with SITEID giving the enrolling site.

Variables:

SITEID would hold the site the subject enrolled at, copied from the collected site.

Note: the completed dataset is checked for one record per site, but a site that enrolled more than one subject repeats its SITEID, which then cannot identify a subject record. The run is rejected and no artifact is accepted.

How to fix

Decide whether a record represents a subject or a site before editing anything. Assert uniqueness on the columns that truly identify a record. Either check the subject identifiers:

verifications:
  - unique:
      columns: [STUDYID, USUBJID]

or, when one record per site is the intent, aggregate the subjects to site records before asserting.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: verification
condition: unique_failed
requirement: REQ-0381

expected/error.yaml

phase: verification
condition: unique_failed
spec_paths:
  - verifications[0].unique
requirement: REQ-0381
context:
  columns: [SITEID]
  failure_count: 1
  keys:
    - STUDYID: PILOT7
      USUBJID: P7-941
    - STUDYID: PILOT7
      USUBJID: P7-942

YAML specification

1 spec file

spec.yaml

Edit31 lines

1schema_version: "1.0"2domain: ADSL3keys: [STUDYID, USUBJID]4input:5  DM: input/dm.csv67output:8  path: adsl.csv9  columns: [STUDYID, USUBJID, SITEID]1011columns:12  - name: STUDYID13    type: str14    label: Study Identifier15    derivation: DM.STUDYID1617  - name: USUBJID18    type: str19    label: Unique Subject Identifier20    derivation: DM.USUBJID2122  - name: SITEID23    type: str24    label: Site Identifier25    derivation: DM.SITEID2627# Each SITEID must appear on one row only. A site that enrolled more than28# one subject repeats its SITEID, so this fails on the completed dataset.29verifications:30  - unique:31      columns: [SITEID]

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	SITEID
PILOT7		101
PILOT7		101

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Comments and assessment materials

Dataset Name	Variable Name	Variable Label	Type	Computational Method	Origin
ADSL	STUDYID	Study Identifier	character	Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character	Copy value from DM.USUBJID.	Predecessor
ADSL	SITEID	Site Identifier	character	Copy value from DM.SITEID.	Predecessor

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

Comments

Mapping spec