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 DTHDT and LSTVSDY through and take the later of the two
in LSTALVDT as the date the subject was last known alive.
Input: collected demographics carrying the date of death (DTHDTC)
and the last-visit study day (LSTVSDY), including one subject with no
recorded death date and one with no recorded last-visit day.
Variables:
DTHDTwould be the date of death, carried over fromDTHDTC, and missing when no death date was collected.LSTVSDYwould be the study day of the last visit, counted from the first dose, and missing when no last visit was recorded.LSTALVDTwould be the later ofDTHDTandLSTVSDYas the date last known alive.
Note: a calendar date and a day number share no common order, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Put both candidates on the same scale before comparing them. For example, carry the actual last-visit date in the source and compare two date columns:
- name: LSTVSDT
type: date
derivation:
source: DM.LSTVSDTC
- name: LSTALVDT
type: date
derivation:
greatest:
sources: [DTHDT, LSTVSDT]
If only LSTVSDY is available, derive its calendar date from the study-day
reference under a separately stated rule before using greatest.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- incomparable_sources
- requirement
- REQ-0324
expected/error.yaml
phase: validation
condition: incomparable_sources
spec_paths:
- columns.LSTALVDT.derivation.greatest
requirement: REQ-0324
context:
sources: [DTHDT, LSTVSDY]
types: [date, int]
Inputs
Under review1 source fileinput/dm.csv
Edit3 rows| STUDYID | USUBJID | DTHDTC | LSTVSDY |
|---|---|---|---|
| YAMAA-01 | 2023-05-14 | 118 | |
| YAMAA-01 | — | 142 | |
| YAMAA-01 | 2024-01-30 | — |
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 | DTHDT | Date of Death | numeric | ISO 8601 | Copy value from DM.DTHDTC. | Predecessor | |
| ADSL | LSTVSDY | Last Visit Study Day | numeric | Copy value from DM.LSTVSDY. | Predecessor | ||
| ADSL | LSTALVDT | Date Last Known Alive | numeric | ISO 8601 | Greatest of DTHDT and LSTVSDY. | 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