Review ask

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

Lifecycle: draftEditUnder review
What this benchmark means
README.md

Public entries: Python and R. Passing coverage requires an installed inventory.

Goal: carry the pooled age group code (AGEGR1N) for each subject, coded with the study's terminology for age groups.

Input: one pre-analysis row per subject with the study and subject identifiers and the pooled age group code.

Variables:

  • AGEGR1N would be the subject's pooled age group, one of the codes the terminology lists: 1 below 65 years, 2 from 65 through 80 years and 3 above 80 years.

Note: the age group terminology also names the SAS format a reader of the submission applies to its codes. The codes are numbers, and a format whose name begins with a dollar sign is a format for text, which cannot be applied to a number, so the name is rejected before any record is read.

How to fix

Name the numeric format the age group codes are read with: drop the leading $ from the codelist's format_name.

- id: AGEGR1N
  name: Pooled Age Group 1 (N)
  data_type: integer
  format_name: AGEGRN
  items:
    - {value: 1, decode: '<65'}
    - {value: 2, decode: '65-80'}
    - {value: 3, decode: '>80'}

A study that gives its readers no format name for this list omits format_name instead.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
value_not_permitted
rule
CT-12
expected/error.yaml
phase: validation
condition: value_not_permitted
spec_paths:
  - codelists[0].codelists[0].format_name
rule: CT-12
context:
  codelist: AGEGR1N
  value: $AGEGRN
  data_type: integer

Inputs

Under review
1 source file

input/adsl_raw.csv

Edit
2 rows
input/adsl_raw.csv
STUDYIDUSUBJIDAGEGR1N
YAMAA-011
YAMAA-013

Unexpected Output

Under review
No artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Your review

2 questions and your comments · View benchmark discussions

Mapping spec

Generated from the benchmark YAML; do not edit by hand

Dataset NameVariable NameVariable LabelTypeCodelist/Controlled TermsCoreComputational MethodOrigin
ADSLSTUDYIDStudy IdentifiercharacterCopy value from ADSL_RAW.STUDYID.Predecessor
ADSLUSUBJIDUnique Subject IdentifiercharacterCopy value from ADSL_RAW.USUBJID.Predecessor
ADSLAGEGR1NPooled Age Group 1 (N)numericPooled Age Group 1 (N)Copy value from ADSL_RAW.AGEGR1N.Predecessor
Codelist IDNameValueDecodeCodelist NCI aliasValue NCI aliasExtensibleExtended valueSAS formatDictionaryVersion
AGEGR1NPooled Age Group 1 (N)1<65No$AGEGRN
AGEGR1NPooled Age Group 1 (N)265-80No$AGEGRN
AGEGR1NPooled Age Group 1 (N)3>80No$AGEGRN
VersionDateAuthorDescriptionReviewerSign-off
1.72026-10-20yamaa docs buildRead 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.62026-10-17yamaa docs buildDescribe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.52026-10-17yamaa docs buildName 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.42026-10-15yamaa docs buildState datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
1.32026-09-29yamaa docs buildShow study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.22026-09-29yamaa docs buildClassify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.12026-09-29yamaa docs buildResolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0yamaa docs buildInitial generation from spec.yaml