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 each collected tumor assessment into an analysis
record holding the assessment date (ADT) and the recorded
response (AVALC), rejecting a partial response (PR) recorded
directly after a complete response (CR).
Input: collected tumor assessments with the assessment date
(RSDTC) and the assessed response (RSSTRESC), identified by
study, subject, and sequence number.
Variables:
ADTis the assessment date, taken directly fromRSDTC.AVALCis the response recorded at that assessment, taken directly fromRSSTRESC:CR,PR, stable disease (SD),NON-CR/NON-PD, progressive disease (PD), or not evaluable (NE).
Note: assessments are compared in date order within a subject.
A complete response leaves no measurable disease to respond partly,
so an assessment recording PR directly after CR for the same
subject is a fault in the collected data: the whole run is rejected
and no artifact is accepted, and the expected output records the
completed rows presented to that check. A partial response that
later becomes complete is ordinary and passes.
How to fix
Review the response sequence and correct the assessment that is inconsistent with the study definition. If the protocol genuinely permits a partial response after a complete response, revise the clinical rule and its check together; do not remove the check merely to accept an unexplained sequence.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- verification
- condition
- assert_failed
- rule
- CHECK-12
expected/error.yaml
phase: verification
condition: assert_failed
spec_paths:
- verifications[1].assert
rule: CHECK-12
context:
verification_id: response-does-not-fall-back-after-a-complete-response
failure_count: 1
keys:
- STUDYID: PILOT7
USUBJID: P7-962
RSSEQ: 2
Inputs
Under review1 source fileinput/rs.csv
Edit6 rows| STUDYID | USUBJID | RSSEQ | RSDTC | RSSTRESC |
|---|---|---|---|---|
| PILOT7 | 1 | 2025-02-17 | CR | |
| PILOT7 | 2 | 2025-04-07 | CR | |
| PILOT7 | 1 | 2025-02-24 | CR | |
| PILOT7 | 2 | 2025-04-14 | PR | |
| PILOT7 | 1 | 2025-03-03 | PR | |
| PILOT7 | 2 | 2025-05-05 | CR |
Unexpected Output
Under review6 rows presented to the failing check - not an accepted artifactexpected/adrs.csv
Edit6 rows| STUDYID | USUBJID | RSSEQ | PARAMCD | ADT | AVALC |
|---|---|---|---|---|---|
| PILOT7 | 1 | OVR | 2025-02-17 | CR | |
| PILOT7 | 2 | OVR | 2025-04-07 | CR | |
| PILOT7 | 1 | OVR | 2025-02-24 | CR | |
| PILOT7 | 2 | OVR | 2025-04-14 | PR | |
| PILOT7 | 1 | OVR | 2025-03-03 | PR | |
| PILOT7 | 2 | OVR | 2025-05-05 | CR |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADRS | STUDYID | Study Identifier | character | Copy value from RS.STUDYID. | Predecessor | ||
| ADRS | USUBJID | Unique Subject Identifier | character | Copy value from RS.USUBJID. | Predecessor | ||
| ADRS | RSSEQ | Sequence Number | numeric | Copy value from RS.RSSEQ. | Predecessor | ||
| ADRS | PARAMCD | Parameter Code | character | Set constant value "OVR". | Assigned | ||
| ADRS | ADT | Analysis Date | numeric | ISO 8601 | Copy value from RS.RSDTC. | Predecessor | |
| ADRS | AVALC | Analysis Value (C) | character | CR, PR, SD, NON-CR/NON-PD, PD, NE | Copy value from RS.RSSTRESC. | Predecessor |
| Variable | Permitted values |
|---|---|
| AVALC | CR, PR, SD, NON-CR/NON-PD, PD, NE |
| 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 |