yamaa As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.
- Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
- Inputs: Do they trigger the failure for the reason the summary gives?
- Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?
The other tabs beside Comments are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdGoal: rank each subject's adverse events (AEs) by reported
severity, carrying through AESEV and numbering the events in
SEVRANK.
Input: collected adverse event records carrying the reported
severity (AESEV).
Variables:
SEVRANKwould be the number of the event among the subject's events ordered by severity, worst first, with equally severe events sharing one number so they compare as equal. An event with no reported severity would come after every rated one.
Note: the tie-numbering choice arrives as a structured value instead of one of the two named methods. No reader may guess which method a structure means, so the run is rejected before any data is read and no artifact is accepted.
How to fix
Decide how ties consume numbers, then name the method. When equally severe events share the lowest position they occupy and the next severity continues after the gap, write it plainly:
- name: SEVRANK
type: int
derivation:
rank:
method: competition
window:
group_by: [STUDYID, USUBJID]
order_by:
- {variable: AESEV, direction: desc}
When no numbers may be skipped, name the dense method instead. Do not encode the choice in a structure the vocabulary does not define.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_field_type
- requirement
- REQ-0287
expected/error.yaml
phase: validation
condition: invalid_field_type
spec_paths:
- columns.SEVRANK.derivation.rank.method
requirement: REQ-0287
context:
expected: str
actual: mapping
Inputs
Under review1 source fileinput/ae.csv
Edit2 rows| STUDYID | USUBJID | AESEQ | AESEV |
|---|---|---|---|
| PILOT7 | 1 | MODERATE | |
| PILOT7 | 2 | SEVERE |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADAE | STUDYID | Study Identifier | character | Copy value from AE.STUDYID. | Predecessor | ||
| ADAE | USUBJID | Unique Subject Identifier | character | Copy value from AE.USUBJID. | Predecessor | ||
| ADAE | AESEQ | Sequence Number | numeric | Copy value from AE.AESEQ. | Predecessor | ||
| ADAE | AESEV | Severity | character | Copy value from AE.AESEV. | Predecessor | ||
| ADAE | SEVRANK | Severity Rank | numeric | Rank rows from 1 within each group of STUDYID, USUBJID, ordered by AESEV descending; ties share a number and the next distinct value follows without a gap. | Derived |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |
Comments
Signed in with GitHub; saved in repository Discussions