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: derive each subject's end-of-study date (EOSDT) from the
subject's disposition record, reporting a subject with several records
instead of stopping the run.
Input: demographics records with disposition records carrying the disposition category, decoded term, and start date.
Variables:
EOSDTwould be the start date of the subject's end-of-study disposition record, and blank when the subject has none.
Note: a subject with several disposition records was to be reported, yet nothing says which of them gives the end-of-study date. Such a subject would have no single date to read, so the specification is rejected before any record is read and no artifact is accepted.
How to fix
Decide which record gives a repeated subject its date, such as the latest event, and declare that choice beside the warning:
intermediates:
- id: DS_EOS
dataset: DS
key: [STUDYID, USUBJID]
filter: "DS.DSCAT = 'DISPOSITION EVENT'"
order_by: [DS.DSSTDTC]
keep: last
verifications:
- unique: {columns: [STUDYID, USUBJID], severity: warning}
When every subject must have exactly one such record, keep the check at its default severity instead, so a repeated subject stops the run:
verifications:
- unique: [STUDYID, USUBJID]
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- value_not_permitted
- rule
- LOOKUP-17
expected/error.yaml
phase: validation
condition: value_not_permitted
spec_paths:
- intermediates.DS_EOS.verifications[0].unique.severity
rule: LOOKUP-17
context:
intermediate: DS_EOS
value: warning
permitted: [error]
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 | EOSDT | End of Study Date | character | Take DSSTDTC from the DS record matching on STUDYID and USUBJID, where DS.DSCAT = 'DISPOSITION EVENT', 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 |