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: one row per subject carrying the study identifier (STUDYID) and the
trial phase (PHASE), both taken from the study's settings.
Input: one spec.yaml over subject records, which carry the subject and
their age (AGE) but no study column, and a study settings table holding one
record: the study identifier, its title and its phase.
Variables:
STUDYIDis the study identifier from the settings record, the same on every row.PHASEis the trial phase from the settings record, the same on every row.
Note: every subject reads the settings table's one record, though the two tables share no column. A settings table with no record, or with more than one, stops the run rather than leaving the values empty or choosing a record.
Inputs
Under review2 source filesExpected output
Under review3 expected rowsexpected/adsl.csv
Edit3 rows| STUDYID | USUBJID | AGE | PHASE |
|---|---|---|---|
| YAMAA-01 | 54 | PHASE 2 | |
| YAMAA-01 | 61 | PHASE 2 | |
| YAMAA-01 | 47 | PHASE 2 |
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADSL | STUDYID | Study Identifier | character | Take STUDYID from the STUDY record matching on the shared output keys, and a row with no match is an error. | Derived | ||
| ADSL | USUBJID | Unique Subject Identifier | character | Copy value from SUBJ.USUBJID. | Predecessor | ||
| ADSL | AGE | Age | numeric | Copy value from SUBJ.AGE. | Predecessor | ||
| ADSL | PHASE | Trial Phase | character | Take PHASE from the STUDY record matching on the shared output keys, and a row with no match is an error. | 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