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: reviewedEditUnder review
What this benchmark means
README.md

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

Goal: complete the analysis end date (AENDT) for each adverse event (AE), rejecting any completion that lands on a day the month never has.

Input: adverse event records carrying collected end text (AEENDTC) and reported term (AETERM).

Variables:

  • AENDT would be the analysis end date completed from AEENDTC: a year alone becomes 31 December, a year and month becomes the 31st of that month, and a complete date is kept as collected. A year and month whose month has fewer than 31 days would complete to a day that month never has, which is not a calendar date, so the run fails and no artifact is accepted.

How to fix

Decide which day an end date collected without one should take. To keep the latest date the collected text allows, name the last day of the month rather than a number:

impute:
  type: date
  source: AE.AEENDTC
  month: 12
  day: last

A year and month such as 2023-04 then completes to 2023-04-30 instead of the impossible 2023-04-31, 2023-07 still completes to 2023-07-31, and a February takes the 28th or 29th according to the year. A fixed day from 1 through 28 is valid in every month too, but it is a different imputation policy, not a repair of this one.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
impute
condition
invalid_calendar_date
rule
TIME-10
expected/error.yaml
phase: impute
condition: invalid_calendar_date
spec_paths:
  - columns.AENDT.derivation.impute
rule: TIME-10
context:
  value: "2023-04"
  completed: "2023-04-31"
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      AESEQ: 2

Inputs

Under review
1 source file

input/ae.csv

Edit
2 rows
input/ae.csv
STUDYIDUSUBJIDAESEQAETERMAEENDTC
YAMAA-011Nausea2023-07
YAMAA-012Fatigue2023-04

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
ADAESTUDYIDStudy IdentifiercharacterCopy value from AE.STUDYID.Predecessor
ADAEUSUBJIDUnique Subject IdentifiercharacterCopy value from AE.USUBJID.Predecessor
ADAEAESEQSequence NumbernumericCopy value from AE.AESEQ.Predecessor
ADAEAENDTAnalysis End DatenumericISO 8601Impute incomplete date from AE.AEENDTC, defaulting month=12, day=31; invalid text is an error.Derived
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