yamaa As a clinical trial statistician or programmer, answer two short questions in Your review: the task and the inputs and outputs. 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: flag each subject's baseline result (ABLFL) as the latest
result with a value on or before treatment start.
Input: one spec.yaml over laboratory records carrying subject,
sequence number (LBSEQ), collection date (ADT), result (AVAL),
which may be missing, and the subject's treatment start date
(TRTSDT), all carried through unchanged.
Variables:
ABLFLisYon the latest record on or before treatment start that has a result, and blank on every other record. A record whose result is missing is passed over even when it is the latest before treatment starts, so a subject whose only record before then has no result has no baseline.
Inputs
Under review1 source fileinput/lb.csv
Edit5 rows| USUBJID | LBSEQ | ADT | AVAL | TRTSDT |
|---|---|---|---|---|
| 1 | 2025-03-01 | 4.1 | 2025-03-04 | |
| 2 | 2025-03-03 | — | 2025-03-04 | |
| 3 | 2025-03-11 | 4.6 | 2025-03-04 | |
| 1 | 2025-03-02 | — | 2025-03-05 | |
| 2 | 2025-03-09 | 5.2 | 2025-03-05 |
Expected output
Under review5 expected rowsexpected/adlb.csv
Edit5 rows| USUBJID | LBSEQ | ADT | AVAL | TRTSDT | ABLFL |
|---|---|---|---|---|---|
| 1 | 2025-03-01 | 4.1 | 2025-03-04 | Y | |
| 2 | 2025-03-03 | — | 2025-03-04 | — | |
| 3 | 2025-03-11 | 4.6 | 2025-03-04 | — | |
| 1 | 2025-03-02 | — | 2025-03-05 | — | |
| 2 | 2025-03-09 | 5.2 | 2025-03-05 | — |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADLB | USUBJID | Unique Subject Identifier | character | Copy value from LB.USUBJID. | Predecessor | ||
| ADLB | LBSEQ | Sequence Number | numeric | Copy value from LB.LBSEQ. | Predecessor | ||
| ADLB | ADT | Analysis Date | numeric | ISO 8601 | Copy value from LB.ADT. | Predecessor | |
| ADLB | AVAL | Analysis Value | numeric | Copy value from LB.AVAL. | Predecessor | ||
| ADLB | TRTSDT | Date of First Exposure to Treatment | numeric | ISO 8601 | Copy value from LB.TRTSDT. | Predecessor | |
| ADLB | ABLFL | Baseline Record Flag | character | "Y" for the last record with ADT on or before TRTSDT and a non-missing AVAL within each group of USUBJID, ordered by ADT; blank otherwise. | 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 |