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: carry the treatment a subject received and the dose they
received of it onto TRT01A and TRT01DOSE.
Input: demographics records for each subject, with exposure
records carrying treatment (EXTRT), dose (EXDOSE), sequence
number (EXSEQ), and start date (EXSTDTC).
Variables:
TRT01Awould contain the treatment from the subject's chosen exposure record.TRT01DOSEwould contain the dose from that same record.
Note: the pair must come from one administration, but nothing says which one, so a subject matching more than one exposure record has no single answer, and the run is rejected with no artifact accepted.
How to fix
State the full order and which end of that order to keep. To choose the earliest administration, read the sequence as an integer so ties on the date are broken numerically:
input:
EX: {path: input/ex.csv, types: {EXSEQ: int}}
intermediates:
- id: DOSING
dataset: EX
order_by: [EX.EXSTDTC, EX.EXSEQ]
keep: first
Both TRT01A and TRT01DOSE then come from that same chosen record.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- join
- condition
- multiple_matches
- requirement
- REQ-0127
expected/error.yaml
phase: join
condition: multiple_matches
spec_paths:
- intermediates[0]
requirement: REQ-0127
context:
intermediate: DOSING
dataset: EX
key:
- STUDYID
- USUBJID
intermediate_key:
STUDYID: PILOT7
USUBJID: P7-321
match_count: 2
keys:
- STUDYID: PILOT7
USUBJID: P7-321
Inputs
Under review2 source filesUnexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
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 | TRT01A | Actual Treatment for Period 01 | character | Take EXTRT from the EX record matching on the shared output keys, and a row with no match is an error. | Derived | ||
| ADSL | TRT01DOSE | Actual Dose for Period 01 | numeric | Take EXDOSE from the EX record matching on the shared output keys, and a row with no match is an error. | Derived |
| 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