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 reported adverse event term (AETERM) and its sequence number (AESEQ) onto the adverse events domain from a SAS transport file.

Input: reported adverse events in input/ae_raw.xpt, a version 5 SAS transport file with one record per reported event. The sequence number is stored as a number and the reported term as text.

Variables:

  • DOMAIN is AE on every record.
  • AESEQ would number each subject's events in whole numbers.
  • AETERM would be the term as reported. The rejected file produces no output value.

Note: a SAS file stores every field either as text or as a number, and a field stored as text is never read as a number. The reported term is declared a whole number, so the file is rejected while it is read, naming the term's field, before any record is derived; no artifact is accepted.

How to fix

The reported term is verbatim text, so read it as the text it is stored as by declaring no type for it; only the sequence number needs narrowing to a whole number:

input:
  AE_RAW:
    path: input/ae_raw.xpt
    types: {AESEQ: int}
    encoding: windows-1252

When a field stored as text does hold digits meant as a number, ask the sender to store it as a number, or read it as text and convert it in the column that needs the number.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
ingest
condition
source_sas_invalid
rule
SAS-7
expected/error.yaml
phase: ingest
condition: source_sas_invalid
spec_paths:
  - input.AE_RAW.types.AETERM
rule: SAS-7
context:
  dataset: AE_RAW
  path: input/ae_raw.xpt
  cause: field_type
  field: AETERM

Inputs

Under review
1 source file

No preview available; inspect the fixture files in the benchmark source.

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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
DOMAINDomain AbbreviationCharAssignedSet constant value "AE".SDTM1
STUDYIDStudy IdentifierCharCollectedCopy value from AE_RAW.STUDYID.SDTM2
USUBJIDUnique Subject IdentifierCharCollectedCopy value from AE_RAW.USUBJID.SDTM3
AESEQSequence NumberNumCollectedCopy value from AE_RAW.AESEQ.SDTM4
AETERMReported Term for the Adverse EventCharCollectedCopy value from AE_RAW.AETERM.SDTM5
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