Reject a Site-Scoped Subject Identity

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: carry the investigator (INVID) responsible for each subject's site.

Input: collected demographics carrying the study site (SITEID) and its investigator (INVID).

Variables:

INVID would be the investigator of the subject's site, read from INVID.

Note: the record identity includes the site (SITEID), but the result does not carry it, so a reader of the result could not check which site a row answers for. The run is rejected before any data is read and no artifact is accepted.

How to fix

Every column that forms the record identity must appear in the output. If the site is part of the identity, carry it:

output:
  columns: [STUDYID, USUBJID, SITEID, INVID]

If study and subject already form the intended identity, drop the site from the identity instead:

keys: [STUDYID, USUBJID]

Choose the option that matches the output's actual row identity.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: internal_column_in_keys
requirement: REQ-0220

expected/error.yaml

phase: validation
condition: internal_column_in_keys
spec_paths:
  - keys[2]
requirement: REQ-0220
context:
  column: SITEID

YAML specification

1 spec file

spec.yaml

Edit33 lines

1schema_version: "1.0"2domain: ADSL3# SITEID is part of the record identity but not an output column, so a4# reader of the output could not check the identity: the specification is5# rejected before any data is read.6keys: [STUDYID, USUBJID, SITEID]7input:8  DM: input/dm.csv910output:11  path: adsl.csv12  columns: [STUDYID, USUBJID, INVID]1314columns:15  - name: STUDYID16    type: str17    label: Study Identifier18    derivation: DM.STUDYID1920  - name: USUBJID21    type: str22    label: Unique Subject Identifier23    derivation: DM.USUBJID2425  - name: SITEID26    type: str27    label: Study Site Identifier28    derivation: DM.SITEID2930  - name: INVID31    type: str32    label: Investigator Identifier33    derivation: DM.INVID

Inputs

Under review1 source file

input/dm.csv

Edit2 rows

input/dm.csv
STUDYID	USUBJID	SITEID	INVID
YAMAA-01		701	INV-701
YAMAA-01		702	INV-702

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	INVID	Investigator Identifier	character	Copy value from DM.INVID.	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