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: read the analysis start of each concomitant medication as ISO 8601 text (ASTDTC) and as a date (ASTDT) from the collected start (CMSTDAT).

Input: concomitant medication records, each identified by its sequence number (CMSEQ), carrying the collected start as the site wrote it.

Variables:

  • ASTDTC would be the start as ISO 8601 text, read from an ISO 8601 date or from a two-digit day, three-letter month and four-digit year such as 04MAR2001. A start written in any other spelling has no stated reading, so the run stops when it reaches one and no artifact is accepted.
  • ASTDT would be the analysis start date, a month alone completed to its first day.

Note: a start that was never collected and a start in an unlisted spelling are different defects: the first gives no analysis start, while the second has no stated reading here.

How to fix

Correct the collected start upstream when the intended date is clear: 4 March 2001 recorded as 04MAR2001 reads as March 4, 2001. Declare a spelling instead only when the sites use it and one of the closed date forms reads it. The list names each spelling the sites use, with at most one of the two slashed orders, so a study whose sites also write slashed dates month first declares:

derivation:
  date_text:
    source: CM.CMSTDAT
    forms: [iso, ddmonyyyy, mdy_slash]

No form reads 4 March 2001 itself. If text in an unlisted spelling is intentionally treated as no analysis start, declare that outcome locally with invalid: null.

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
impute
condition
invalid_date_text
rule
TIME-22
expected/error.yaml
phase: impute
condition: invalid_date_text
spec_paths:
  - columns.ASTDTC.derivation.date_text
rule: TIME-22
context:
  source: CM.CMSTDAT
  value: "4 March 2001"
  keys:
    - STUDYID: YAMAA-01
      USUBJID: YAMAA-01-301
      CMSEQ: 2

Inputs

Under review
1 source file

input/cm.csv

Edit
3 rows
input/cm.csv
STUDYIDUSUBJIDCMSEQCMSTDAT
YAMAA-0112001-03-04
YAMAA-0124 March 2001
YAMAA-01104MAR2001

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
ADCMSTUDYIDStudy IdentifiercharacterCopy value from CM.STUDYID.Predecessor
ADCMUSUBJIDUnique Subject IdentifiercharacterCopy value from CM.USUBJID.Predecessor
ADCMCMSEQSequence NumbernumericCopy value from CM.CMSEQ.Predecessor
ADCMASTDTCAnalysis Start Date TextcharacterRead CM.CMSTDAT as ISO 8601 date text from ISO 8601 date text or day-month-year text such as 04MAR2001; blank when it is blank; any other spelling is an error.Derived
ADCMASTDTAnalysis Start DatenumericISO 8601Impute incomplete date from ASTDTC, defaulting day=first; a year alone gives blank; 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