Reject Formula Flag

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: derive AVAL, ANRHI, and HIFL for each subject and parameter, flagging collected laboratory results that lie above their reference range.

Input: collected laboratory records carrying the study and subject identifiers with LBTESTCD, the test code; LBSTRESN, the numeric result; and LBSTNRHI, the upper limit of its reference range.

Variables:

AVAL would be the collected result, taken from LBSTRESN.
ANRHI would be the upper limit of the reference range, taken from LBSTNRHI.
HIFL would be 1 for a result above that limit and 0 otherwise.

Note: the flag is written as the comparison AVAL > ANRHI inside a formula. A formula produces a number, while a comparison answers yes or no; turning that answer into 1 or 0, or into text, would each be a different result from the same comparison, so the run is rejected before any data is read and no artifact is accepted. HIFL is this benchmark's own invention, documented here; AVAL and ANRHI follow ADaMIG-1.3.

How to fix

Ask the comparison where the flag is decided, so the conversion from a yes-or-no answer to 1 or 0 is explicit:

- name: HIFL
  type: int
  derivation:
    case:
      - when: "AVAL > ANRHI"
        then: 1
      - otherwise: 0

A missing result or limit answers neither yes nor no, so it falls to otherwise and gets 0; to leave such a flag empty instead, replace the otherwise with when: "AVAL <= ANRHI" returning 0.

Expected failure

Editthe run is rejected; no artifact is accepted

expected/error.yaml

phase: validation
condition: prohibited_construct
rule: FORMULA-27

expected/error.yaml

phase: validation
condition: prohibited_construct
spec_paths:
  - columns.HIFL.derivation
rule: FORMULA-27
context:
  expr: "AVAL > ANRHI"
  construct: comparison

YAML specification

1 spec file

spec.yaml

Edit45 lines

1yamaa: "1.0"2type: spec3model: ADaM4domain: ADLB5keys: [STUDYID, USUBJID, PARAMCD]6input:7  LB: input/lb.csv89output:10  path: adlb.csv11  columns: [STUDYID, USUBJID, PARAMCD, AVAL, ANRHI, HIFL]1213columns:14  - name: STUDYID15    type: str16    label: Study Identifier17    derivation: LB.STUDYID1819  - name: USUBJID20    type: str21    label: Unique Subject Identifier22    derivation: LB.USUBJID2324  - name: PARAMCD25    type: str26    label: Parameter Code27    derivation: LB.LBTESTCD2829  - name: AVAL30    type: float31    label: Analysis Value32    derivation: LB.LBSTRESN3334  - name: ANRHI35    type: float36    label: Analysis Normal Range Upper Limit37    derivation: LB.LBSTNRHI3839  # A formula admits no comparison: a yes-or-no question belongs in a case,40  # which states how the answer becomes 1 or 0. The specification is41  # rejected before any data is read.42  - name: HIFL43    type: int44    label: High Result Flag45    derivation: "AVAL > ANRHI"

Inputs

Under review1 source file

input/lb.csv

Edit2 rows

input/lb.csv
STUDYID	USUBJID	LBTESTCD	LBSTRESN	LBSTNRHI
YAMAA-01		ALT	42	35
YAMAA-01		ALT	20	35

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	Computational Method	Origin
ADLB	STUDYID	Study Identifier	character	Copy value from LB.STUDYID.	Predecessor
ADLB	USUBJID	Unique Subject Identifier	character	Copy value from LB.USUBJID.	Predecessor
ADLB	PARAMCD	Parameter Code	character	Copy value from LB.LBTESTCD.	Predecessor
ADLB	AVAL	Analysis Value	numeric	Copy value from LB.LBSTRESN.	Predecessor
ADLB	ANRHI	Analysis Normal Range Upper Limit	numeric	Copy value from LB.LBSTNRHI.	Predecessor
ADLB	HIFL	High Result Flag	numeric	Compute AVAL > ANRHI.	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/lb.csv

Your review

Mapping spec