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: build the laboratory domain with one record per subject for glucose and one for creatinine, each with its result in standard units (LBSTRESN) and the metadata a data definition describes it by.

Input: laboratory results delivered by the vendor, one record per subject, with glucose in mmol/L (GLUC) and creatinine in mg/dL (CREATMG).

Variables:

  • DOMAIN is LB on every record.
  • LBTESTCD would be GLUC or CREAT.
  • LBSTRESN would be the glucose as delivered, and the creatinine converted to micromoles per litre (multiplied by 88.42).

Note: the result of each test is described as delivered by the vendor. The creatinine result is converted here before it is submitted, so it did not arrive as it stands, and its description contradicts how the value is made; the run is rejected before any data is read and no artifact is accepted.

How to fix

Describe the converted creatinine result as derived by the sponsor, and keep the delivered glucose result as collected:

- id: CREAT
  where: {LBTESTCD: [CREAT]}
  origins:
    - type: Derived
      source: Sponsor
  method: Creatinine in mg/dL multiplied by 88.42

Expected failure

Edit
the run is rejected; no artifact is accepted
expected/error.yaml
phase
validation
condition
refuted_value_origin
rule
SUB-13
expected/error.yaml
phase: validation
condition: refuted_value_origin
spec_paths:
  - columns.LBSTRESN.submission.value_level.CREAT
rule: SUB-13
context:
  column: LBSTRESN
  entry: CREAT
  origin_type: Collected

Inputs

Under review
1 source file

input/lab.csv

Edit
2 rows
input/lab.csv
STUDYIDUSUBJIDGLUCCREATMG
YAMAA-015.40.9
YAMAA-016.11.2

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

Variable NameVariable LabelTypeLengthControlled Terms or FormatOriginCoreConversion DefinitionVariable TypeVariable OrderComments for Define
DOMAINDomain AbbreviationChar2AssignedReqSet constant value "LB".SDTM1
STUDYIDStudy IdentifierChar8ProtocolReqCopy value from LAB.STUDYID.SDTM2
USUBJIDUnique Subject IdentifierChar12AssignedReqCopy value from LAB.USUBJID.SDTM3
LBTESTCDLab Test or Examination Short NameChar5AssignedReqSet per constructed row; see the Row construction sheet.SDTM4
LBSTRESNNumeric Result/Finding in Standard UnitsNum8DerivedExpResult in standard unitsSDTM5
TemplateInclude whenLBTESTCDLBSTRESN
glucoseConstant "GLUC"Copy LAB.GLUC
creatinineConstant "CREAT"Compute LAB.CREATMG * 88.42
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