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: build one subject-level record per subject carrying TOTDOSE, the
subject's total administered dose.
Input: demographics with one record per subject, and exposure records with the dose of each administration.
Variables:
TOTDOSEwould be the total of the subject's administered doses.
Note: the request totals each different dose amount once. Two administrations of the same amount are two doses, and totalling the amount once would report less than the subject received, so the run is rejected before any data is read.
How to fix
Total every administration, so that a repeated amount counts each time it was given:
- name: TOTDOSE
type: float
derivation:
aggregate:
key: [STUDYID, USUBJID]
expr: "SUM(EX.EXDOSE)"
If a repeated record is an administration entered twice by mistake, correct
the exposure data. If the number of different dose levels is wanted instead,
count them: COUNT(EX.EXDOSE) with distinct: true.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- unpaired_fields
- rule
- LOOKUP-10
expected/error.yaml
phase: validation
condition: unpaired_fields
spec_paths:
- columns.TOTDOSE.derivation.aggregate
rule: LOOKUP-10
context:
declared:
- distinct
missing:
- STR_JOIN(x)
- COUNT(x)
Inputs
Under review2 source filesUnexpected 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 |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Copy value from DM.STUDYID. | Predecessor | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from DM.USUBJID. | Predecessor | ||
| ADSL | TOTDOSE | Total Dose Administered | numeric | Aggregate SUM(EX.EXDOSE) over records matching on STUDYID and USUBJID. | 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