Reject Mixed Units

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

EditUnder reviewWhat this benchmark means

README.md

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

Goal: build a subject-level record carrying the exposure start (TRTSDT) and end (TRTEDT) dates and counting whole months between them in TRTDURM.

Input: collected demographics (DM) records carrying an exposure start date (TRTSDT) and an exposure end date (TRTEDT), one record for each subject.

Variables:

TRTSDT would be the exposure start date, taken from DM as collected.
TRTEDT would be the exposure end date, taken from DM as collected.
TRTDURM would be the whole-month count from TRTSDT to TRTEDT, but it also asks to count both endpoints, which is defined only for a count of days.

Note: counting both endpoints beside a month count has no meaning: inclusive bounds answer "how many days, endpoints included", which has no whole-month reading. The request is rejected before any data is read, so no output is produced.

How to fix

Decide whether the study counts days or whole months, then state only that. A month count stands on its own with no endpoint adjustment:

- name: TRTDURM
  type: int
  derivation:
    diff:
      type: date
      start: TRTSDT
      end: TRTEDT
      unit: month

When the study counts days with both endpoints included, keep unit: day beside closed: both instead.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: value_not_permitted
rule: TIME-5

expected/error.yaml

phase: validation
condition: value_not_permitted
spec_paths:
  - columns.TRTDURM.derivation.diff.closed
rule: TIME-5
context:
  value: both
  permitted: [right]

YAML specification

1 spec file

spec.yaml

Edit45 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADSL5keys: [STUDYID, USUBJID]6input:7  DM: {path: input/dm.csv, types: {TRTSDT: date, TRTEDT: date}}89output:10  path: adsl.csv11  columns: [STUDYID, USUBJID, TRTSDT, TRTEDT, TRTDURM]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: DM.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: DM.USUBJID2324  - name: TRTSDT25    type: date26    label: Date/Time of First Exposure to Treatment27    derivation: DM.TRTSDT2829  - name: TRTEDT30    type: date31    label: Date/Time of Last Exposure to Treatment32    derivation: DM.TRTEDT3334  # Counting both end dates is defined only for a day count, so closed: both35  # beside unit: month is rejected before any data is read.36  - name: TRTDURM37    type: int38    label: Total Duration of Treatment (Months)39    derivation:40      diff:41        type: date42        start: TRTSDT43        end: TRTEDT44        unit: month45        closed: both

Inputs

Under review1 source file

input/dm.csv

Edit1 row

input/dm.csv
STUDYID	USUBJID	TRTSDT	TRTEDT
YAMAA-01		2025-01-06	2025-03-10

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Dataset Name	Variable Name	Variable Label	Type	Codelist/Controlled Terms	Computational Method	Origin
ADSL	STUDYID	Study Identifier	character		Copy value from DM.STUDYID.	Predecessor
ADSL	USUBJID	Unique Subject Identifier	character		Copy value from DM.USUBJID.	Predecessor
ADSL	TRTSDT	Date/Time of First Exposure to Treatment	numeric	ISO 8601	Copy value from DM.TRTSDT.	Predecessor
ADSL	TRTEDT	Date/Time of Last Exposure to Treatment	numeric	ISO 8601	Copy value from DM.TRTEDT.	Predecessor
ADSL	TRTDURM	Total Duration of Treatment (Months)	numeric		Whole months from TRTSDT to TRTEDT, counting both endpoints.	Derived

Version	Date	Author	Description
1.7	2026-10-20	yamaa docs build	Read 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.6	2026-10-17	yamaa docs build	Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight
1.5	2026-10-17	yamaa docs build	Name 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.4	2026-10-15	yamaa docs build	State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks
1.3	2026-09-29	yamaa docs build	Show study codelist names, external dictionaries, and ISO 8601 formats in variable rows; list the document's codelist values and metadata
1.2	2026-09-29	yamaa docs build	Classify ADaM copies from a declared input as Predecessor and recodes as Derived, and SDTM recodes of locally derived columns as Derived
1.1	2026-09-29	yamaa docs build	Resolve lookups into the donor record they select, and give every derivation shape a plain-language rule instead of its raw YAML
1.0		yamaa docs build	Initial generation from spec.yaml

How to fix

input/dm.csv

Your review

Mapping spec