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: record each subject's date of death (DTHDT) and
last-visit study day (LSTVSDY) from collected demographics, and
keep the earlier of the two in FSTALVDT as the first known alive
date.
Input: collected demographics carrying a death date-time
(DTHDTC) and the last-visit study day (LSTVSDY).
Variables:
DTHDTwould be the date of death taken fromDTHDTC, missing when no death was recorded.LSTVSDYwould be the study day of the last visit, counting days, not dates.FSTALVDTwould be the first known alive date: the earlier of the death date and the last-visit date, or the one present when the other is missing. A calendar date and a day count have no common order, so there is no earlier of the two: the run is rejected before any data is read and no artifact is accepted.
How to fix
Decide which date the study reports, then state it in dates. Take
the last contact from the date the visit was collected on, read into
a date column (LSTCONDT here), not from its study day, so both
sides are dates:
- name: FSTALVDT
type: date
derivation:
least:
sources: [DTHDT, LSTCONDT]
When only the day count exists, keep the count as a count instead of forcing it into a date column.
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.FSTALVDT.derivation.least
requirement: REQ-0324
context:
sources: [DTHDT, LSTVSDY]
types: [date, int]
Inputs
Under review1 source fileinput/dm.csv
Edit6 rows| STUDYID | USUBJID | DTHDTC | LSTVSDY |
|---|---|---|---|
| YAMAA-01 | 2025-03-14 | 74 | |
| YAMAA-01 | — | 92 | |
| YAMAA-01 | 2025-01-02 | — | |
| YAMAA-01 | — | 1 | |
| YAMAA-01 | 2025-06-30 | 181 | |
| YAMAA-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 | 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 | FSTALVDT | First Known Alive Date | numeric | ISO 8601 | Least 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