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 start date (ASTDT) of each adverse event (AE) from its collected onset text (AESTDTC).

Input: collected event records carrying the reported term (AETERM) and the collected onset text (AESTDTC).

Variables:

  • ASTDT would be the analysis start date completed from the onset text: a complete collected date unchanged, a year-and-month completed to its first day, a year-only start completed to January 1. Text that cannot be read as a date or the beginning of one has no stated completion, so the run stops when it reaches it and no artifact is accepted.

Note: a date that was never collected and text that cannot be read as a date are different defects: an onset never collected gives no analysis date, while unreadable text has no stated outcome here.

How to fix

Correct UNKNOWN upstream when a date can be recovered. If invalid date text is intentionally treated as no analysis date, declare that outcome locally:

derivation:
  impute:
    type: date
    source: AE.AESTDTC
    month: 1
    day: 1
    invalid: null

The invalid outcome applies to text that is not a calendar date or date beginning; it is distinct from text that was never collected, which gives no analysis date without any declaration. Onset text in a declared non-ISO spelling, such as 15JUN2023, is read with date_text before impute completes it.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
impute
condition
invalid_date_text
rule
TIME-13
expected/error.yaml
phase: impute
condition: invalid_date_text
spec_paths:
  - columns.ASTDT.derivation.impute
rule: TIME-13
context:
  source: AE.AESTDTC
  value: UNKNOWN
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-101
      AESEQ: 4

Inputs

Under review
1 source file

input/ae.csv

Edit
4 rows
input/ae.csv
STUDYIDUSUBJIDAESEQAETERMAESTDTC
YAMAA-011Headache2023-06-15
YAMAA-012Nausea2023-06
YAMAA-013Fatigue2023
YAMAA-014DizzinessUNKNOWN

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
ADAEASTDTAnalysis Start DatenumericISO 8601Impute incomplete date from AE.AESTDTC, defaulting month=1, day=1; 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