yamaa As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs. Agreeing with both approves this benchmark; disagreeing with either needs a comment. Propose a fix with the Edit button on any source file, or add it to your comments.
We suggest spending no more than 5 minutes on a review. The other tabs beside Your review are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: carry the disposition event that follows each subject's last dose
(EOSSTT) onto the subject-level analysis dataset.
Input: collected demographics with the study day of the last dose
(TRTEDY), one record per subject, and collected disposition events with
their study day (DSSTDY).
Variables:
TRTEDYwould be the study day of the last dose as collected.EOSSTTwould be the disposition event recorded after the last dose; missing when no event follows it.
Note: the events are checked to be one per subject before any record is built, but which events count is decided by comparing each with the record being built, its last dose day. A check made once cannot cover events chosen record by record, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Choose the events by their own fields when they must be checked once, for example by the disposition category or term, and leave the comparison with the last dose day to a filter without the check:
- id: POSTTRT
dataset: DS
key: [STUDYID, USUBJID]
filter: "DS.DSSTDY > DM.TRTEDY"
order_by: [DS.DSSTDY]
keep: first
Here the first event after the last dose is kept for each subject, so no uniqueness check is needed.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- correlated_filter_with_unique_verification
- rule
- LOOKUP-17
expected/error.yaml
phase: validation
condition: correlated_filter_with_unique_verification
spec_paths:
- intermediates.POSTTRT.verifications[0].unique
rule: LOOKUP-17
context:
intermediate: POSTTRT
Inputs
Under review2 source filesUnexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| 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 | TRTEDY | Last Dose Study Day | numeric | Copy value from DM.TRTEDY. | Predecessor | ||
| ADSL | EOSSTT | End of Study Status | character | Take DSDECOD from the DS record matching on STUDYID and USUBJID, where DS.DSSTDY > DM.TRTEDY, and no match yields blank. | Derived |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.7 | 2026-10-20 | yamaa docs build | Read a specification in the 1.0 surface as its 0.5 counterpart; state that missing values stay missing where a mapping declares no missing handler, and leave out a declared missing answer that restates a handler's default | ||
| 1.6 | 2026-10-17 | yamaa docs build | Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight | ||
| 1.5 | 2026-10-17 | yamaa docs build | Name collected precision in words instead of letter codes; state imputation fallbacks, minimum source precision, bounds ignored outside the collected period, and invalid text with no handler as an error; describe date and datetime shifts, imputation flag codes, and partial text giving no date part | ||
| 1.4 | 2026-10-15 | yamaa docs build | State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks | ||
| 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 |