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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: flag each subject's baseline result (ABLFL) as the latest
result dated before the day treatment starts.
Input: one spec.yaml over vital-sign results carrying subject,
sequence number (VSSEQ), assessment date (ADT), result (AVAL),
and the subject's treatment start date (TRTSDT), all carried through
unchanged.
Variables:
ABLFLisYon the latest result dated strictly before treatment start and blank on every other result. A result taken on the day treatment starts is never the baseline, so a subject whose earliest result falls on that day has no baseline.
Inputs
Under review1 source fileinput/vs.csv
Edit5 rows| USUBJID | VSSEQ | ADT | AVAL | TRTSDT |
|---|---|---|---|---|
| 1 | 2025-03-01 | 120 | 2025-03-03 | |
| 2 | 2025-03-03 | 118 | 2025-03-03 | |
| 3 | 2025-03-10 | 121 | 2025-03-03 | |
| 1 | 2025-03-05 | 96 | 2025-03-05 | |
| 2 | 2025-03-12 | 99 | 2025-03-05 |
Expected output
Under review5 expected rowsexpected/advs.csv
Edit5 rows| USUBJID | VSSEQ | ADT | AVAL | TRTSDT | ABLFL |
|---|---|---|---|---|---|
| 1 | 2025-03-01 | 120 | 2025-03-03 | Y | |
| 2 | 2025-03-03 | 118 | 2025-03-03 | — | |
| 3 | 2025-03-10 | 121 | 2025-03-03 | — | |
| 1 | 2025-03-05 | 96 | 2025-03-05 | — | |
| 2 | 2025-03-12 | 99 | 2025-03-05 | — |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADVS | USUBJID | Unique Subject Identifier | character | Copy value from VS.USUBJID. | Predecessor | ||
| ADVS | VSSEQ | Sequence Number | numeric | Copy value from VS.VSSEQ. | Predecessor | ||
| ADVS | ADT | Analysis Date | numeric | ISO 8601 | Copy value from VS.ADT. | Predecessor | |
| ADVS | AVAL | Analysis Value | numeric | Copy value from VS.AVAL. | Predecessor | ||
| ADVS | TRTSDT | Date of First Exposure to Treatment | numeric | ISO 8601 | Copy value from VS.TRTSDT. | Predecessor | |
| ADVS | ABLFL | Baseline Record Flag | character | "Y" for the last record with ADT 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 |
yamaa