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 moment
treatment started in RFSTDTM and the calendar date of death in
DTHDT and counting whole days between them in SURVDD.
Input: collected demographics carrying the treatment-start
moment (RFSTDTC) and the death date (DTHDT).
Variables:
RFSTDTMwould be the moment treatment started, time of day included, taken fromRFSTDTC.SURVDDwould be the whole-day count fromRFSTDTMtoDTHDT.
Note: a day count has no meaning between a moment and a date: the hours on either side could give two different answers, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Decide which calendar days the study counts, then state them as dates. When
only moments are collected, take each moment's calendar date first and
count from it (start: RFSTD), so the count has whole days to count:
- name: RFSTD
type: date
derivation:
to_date:
source: RFSTDTM
When the hours matter, the study needs a finer unit than days, which this vocabulary does not offer; record that gap instead of rounding it away.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- incompatible_input_type
- requirement
- REQ-0606
expected/error.yaml
phase: validation
condition: incompatible_input_type
spec_paths:
- columns.SURVDD.derivation.date_diff.start
requirement: REQ-0606
context:
source: RFSTDTM
expected: date
actual: datetime
Inputs
Under review1 source fileinput/dm.csv
Edit2 rows| STUDYID | USUBJID | RFSTDTC | DTHDT |
|---|---|---|---|
| YAMAA-01 | 2023-01-02T09:00:00 | 2023-05-14 | |
| YAMAA-01 | 2023-02-10T09:00:00 | 2023-06-01 |
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 | RFSTDTM | Reference Start Moment | numeric | ISO 8601 | Copy value from DM.RFSTDTC. | Predecessor | |
| ADSL | DTHDT | Date of Death | numeric | ISO 8601 | Copy value from DM.DTHDT. | Predecessor | |
| ADSL | SURVDD | Survival Duration in Days | numeric | Whole days from RFSTDTM to DTHDT, counting the end date but not the start. | 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