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 first treatment received in TRT01A, one
record per subject.
Input: demographics records plus exposure records carrying the
administration sequence number (EXSEQ), the treatment name
(EXTRT), and the administration start date (EXSTDTC).
Variables:
TRT01Awould contain the treatment name from the earliest exposure record.
Note: the chosen record is named EX, which already names the
exposure records, so a read of EX.EXTRT cannot say whether it
means the treatment of the chosen record or of every exposure
record. The two readings differ whenever a subject has more than one
administration. The name itself is rejected before any data is
read, so no artifact is accepted.
How to fix
Give the record lookup a name that is distinct from every dataset and from the output domain, then read through that name:
intermediates:
- id: FIRSTEX
dataset: EX
order_by: [EX.EXSTDTC, EX.EXSEQ]
keep: first
# ...
derivation:
source: FIRSTEX.EXTRT
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- duplicate_identifier
- requirement
- REQ-0113
expected/error.yaml
phase: validation
condition: duplicate_identifier
spec_paths:
- intermediates[0].id
- input.EX
requirement: REQ-0113
context:
identifier: EX
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 first EX record matching on the shared output keys, ordered by EX.EXSTDTC then EX.EXSEQ, 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