Reject Missed Visits Chosen Before Any Visit Is Recorded

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: list each subject's planned visits, with the visit number in VISITNUM, the visit name in VISIT, and whether the visit took place in SVOCCUR: one record per visit that took place, and one per planned visit that has none.

Input: each subject's planned visits, and the visits that took place, each carrying the visit number (VISITNUM) and name (VISIT).

Variables:

SVOCCUR would be Y for a visit that took place and N for a planned visit with no visit that took place.

Note: a planned visit is listed as missed only when no record of that visit has been built before it. The missed visits are built first, before any visit that took place has a record, so every planned visit would look missed. The run is rejected before any data is read and no artifact is accepted.

How to fix

Build the records of the visits that took place first, then the missed visits, so a planned visit is compared with the visits already recorded:

rows:
  - id: attended
    dataset: VISITS
    derivations: ...
  - id: missed
    dataset: PLAN
    filter: "RECORDED.VISIT IS NULL"
    derivations: ...

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: phase_boundary
rule: LOOKUP-7

expected/error.yaml

phase: validation
condition: phase_boundary
spec_paths:
  - rows.missed.filter
rule: LOOKUP-7
context:
  identifier: RECORDED.VISIT
  available_phase: completed_prior_row_template
  required_phase: row_construction

YAML specification

1 spec file

spec.yaml

Edit46 lines

1yamaa: "1.0"2type: spec3model: SDTM4domain: SV5keys: [USUBJID, VISITNUM]6input:7  PLAN: {path: input/plan.csv, types: {VISITNUM: int}}8  VISITS: {path: input/visits.csv, types: {VISITNUM: int}}910output:11  path: sv.csv12  columns: [USUBJID, VISITNUM, VISIT, SVOCCUR]1314intermediates:15  # The subject's record of the visit, among the records built so far.16  - id: RECORDED17    dataset: SELF18    key: [USUBJID, VISITNUM]1920columns:21  - {name: USUBJID, type: str, label: Unique Subject Identifier}22  - {name: VISITNUM, type: int, label: Visit Number}23  - {name: VISIT, type: str, label: Visit Name}24  - {name: SVOCCUR, type: str, label: Occurrence}2526rows:27  # Each planned visit that has no record yet. These are the first records28  # built, so no visit has a record yet when they are selected, and the29  # specification is rejected before any data is read.30  - id: missed31    dataset: PLAN32    filter: "RECORDED.VISIT IS NULL"33    derivations:34      USUBJID: PLAN.USUBJID35      VISITNUM: PLAN.VISITNUM36      VISIT: PLAN.VISIT37      SVOCCUR: "'N'"3839  # Each visit that took place.40  - id: attended41    dataset: VISITS42    derivations:43      USUBJID: VISITS.USUBJID44      VISITNUM: VISITS.VISITNUM45      VISIT: VISITS.VISIT46      SVOCCUR: "'Y'"

Inputs

Under review2 source files

input/plan.csv

Edit4 rows

input/plan.csv
USUBJID	VISITNUM	VISIT
	1	SCREENING
	2	WEEK 2
	1	SCREENING
	2	WEEK 2

input/visits.csv

Edit3 rows

input/visits.csv
USUBJID	VISITNUM	VISIT
	1	SCREENING
	2	WEEK 2
	1	SCREENING

Unexpected Output

Under reviewNo artifact is produced

No fixture files in this directory.

Shaded columns are derived— = missing value

Human review and assessment

Variable Name	Variable Label	Type	Origin	Conversion Definition	Variable Type	Variable Order
USUBJID	Unique Subject Identifier	Char	Derived	Set per constructed row; see the Row construction sheet.	SDTM	1
VISITNUM	Visit Number	Num	Derived	Set per constructed row; see the Row construction sheet.	SDTM	2
VISIT	Visit Name	Char	Derived	Set per constructed row; see the Row construction sheet.	SDTM	3
SVOCCUR	Occurrence	Char	Derived	Set per constructed row; see the Row construction sheet.	SDTM	4

Template	Include when	USUBJID	VISITNUM	VISIT	SVOCCUR
missed	RECORDED.VISIT IS NULL	Copy PLAN.USUBJID	Copy PLAN.VISITNUM	Copy PLAN.VISIT	Constant "N"
attended		Copy VISITS.USUBJID	Copy VISITS.VISITNUM	Copy VISITS.VISIT	Constant "Y"

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/plan.csv

input/visits.csv

Your review

Mapping spec