yamaa 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 meansREADME.mdGoal: build one record for every subject carrying the collected
age (AGE) and sex (SEX). Each subject may appear only once in
the result.
Input: collected demographics records carrying age (AGE) and
sex (SEX).
Variables:
AGEwould be the collected age, carried into the result unchanged.SEXwould be the sex collected in the demographics records, carried into the result unchanged.
Note: the result is built one row per collected record, so a subject entered twice reaches the result twice. That rejects the run even when the two records agree; here they also disagree on the age, and keeping either record, or merging the two, would report an age the collected data does not support. The expected file shows the completed rows as they reach the one-row-per-subject check, but the repeated subject still rejects the run and no artifact is accepted.
How to fix
Reconcile the two source records and correct the governed demographics input so it contains one supported age for the subject. If multiple source records are legitimate, build the rows from a list holding each subject once and declare an ordered record-selection rule for the demographics record; do not rely on source order to discard one. The completed output must contain exactly one row for each key.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- output
- condition
- duplicate_key
- requirement
- REQ-0240
expected/error.yaml
phase: output
condition: duplicate_key
spec_paths:
- keys
requirement: REQ-0240
context:
duplicate_count: 1
keys:
- STUDYID: PILOT7
USUBJID: P7-722
Inputs
Under review1 source fileinput/dm.csv
Edit3 rows| STUDYID | USUBJID | AGE | SEX |
|---|---|---|---|
| PILOT7 | 64 | F | |
| PILOT7 | 58 | M | |
| PILOT7 | 59 | M |
Unexpected Output
Under review3 rows presented to the failing check - not an accepted artifactexpected/adsl.csv
Edit3 rows| STUDYID | USUBJID | AGE | SEX |
|---|---|---|---|
| PILOT7 | 64 | F | |
| PILOT7 | 58 | M | |
| PILOT7 | 59 | M |
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | 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 | AGE | Age | numeric | Copy value from DM.AGE. | Predecessor | ||
| ADSL | SEX | Sex | character | Copy value from DM.SEX. | Predecessor |
| Template | Include when |
|---|---|
| record |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |
Comments
Signed in with GitHub; saved in repository Discussions