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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: translate the collected overall response into its
analysis category (AVALC).
Input: response records carrying the collected overall
response (OVRLRESP).
Variables:
AVALCwould contain the analysis category matching the collected overall response:CRmeansCOMPLETE RESPONSE,PRmeansPARTIAL RESPONSE,SDmeansSTABLE DISEASE, andPDmeansPROGRESSIVE DISEASE. Every response must be present and listed; the collected valueNEis not, so the run is rejected with no artifact accepted.
How to fix
If NE is a valid collected response, add its governed analysis meaning to
the dictionary:
mapping:
source: RS.OVRLRESP
dict:
CR: COMPLETE RESPONSE
PR: PARTIAL RESPONSE
SD: STABLE DISEASE
PD: PROGRESSIVE DISEASE
NE: NOT EVALUABLE
If an unknown response should instead produce a missing result, state that
missing-value answer explicitly with unmapped: null. Prefer
completing the dictionary when the value is valid.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- mapping
- condition
- unmapped_value
- rule
- COLUMN-10
expected/error.yaml
phase: mapping
condition: unmapped_value
spec_paths:
- columns.AVALC.derivation.mapping
rule: COLUMN-10
context:
source: RS.OVRLRESP
value: NE
keys:
- STUDYID: PILOT7
USUBJID: P7-702
RSSEQ: 1
Inputs
Under review1 source fileinput/rs.csv
Edit1 row| STUDYID | USUBJID | RSSEQ | OVRLRESP |
|---|---|---|---|
| PILOT7 | 1 | NE |
Unexpected 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 |
|---|---|---|---|---|---|---|---|
| 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 | AVALC | Analysis Value (C) | character | Recode RS.OVRLRESP: "CR" → "COMPLETE RESPONSE", "PR" → "PARTIAL RESPONSE", "SD" → "STABLE DISEASE", "PD" → "PROGRESSIVE DISEASE"; missing values stay missing; unlisted values are errors. | 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