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 a subject-level record carrying the exposure start
(TRTSDT) and end (TRTEDT) dates and counting whole months between
them in TRTDURM.
Input: collected demographics (DM) records carrying an exposure
start date (TRTSDT) and an exposure end date (TRTEDT), one record
for each subject.
Variables:
TRTSDTwould be the exposure start date, taken from DM as collected.TRTEDTwould be the exposure end date, taken from DM as collected.TRTDURMwould be the whole-month count fromTRTSDTtoTRTEDT, but it also asks to count both endpoints, which is defined only for a count of days.
Note: counting both endpoints beside a month count has no meaning: inclusive bounds answer "how many days, endpoints included", which has no whole-month reading. The request is rejected before any data is read, so no output is produced.
How to fix
Decide whether the study counts days or whole months, then state only that. A month count stands on its own with no endpoint adjustment:
- name: TRTDURM
type: int
derivation:
date_diff:
start: TRTSDT
end: TRTEDT
unit: month
When the study counts days with both endpoints included, keep unit: day
beside bounds: inclusive instead.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- value_not_permitted
- requirement
- REQ-0613
expected/error.yaml
phase: validation
condition: value_not_permitted
spec_paths:
- columns.TRTDURM.derivation.date_diff.bounds
requirement: REQ-0613
context:
value: inclusive
permitted: [exclusive]
Inputs
Under review1 source fileinput/dm.csv
Edit1 row| STUDYID | USUBJID | TRTSDT | TRTEDT |
|---|---|---|---|
| YAMAA-01 | 2025-01-06 | 2025-03-10 |
Unexpected 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 | TRTSDT | Date/Time of First Exposure to Treatment | numeric | ISO 8601 | Copy value from DM.TRTSDT. | Predecessor | |
| ADSL | TRTEDT | Date/Time of Last Exposure to Treatment | numeric | ISO 8601 | Copy value from DM.TRTEDT. | Predecessor | |
| ADSL | TRTDURM | Total Duration of Treatment (Months) | numeric | Whole months from TRTSDT to TRTEDT, counting both endpoints. | 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