yamaa As a clinical trial statistician or programmer, challenge anything in this benchmark: describe a problem in Comments, or propose a fix with the Edit button on any source file.
- Task: Is this a specification error a study team could realistically make, and should the build stop on it rather than continue?
- Inputs: Do they trigger the failure for the reason the summary gives?
- Expected failure: Is this the right error, raised at the right point, and would it tell the programmer what to fix?
The other tabs beside Comments are background for assessment, not under review.
Summary
EditUnder reviewWhat this benchmark meansREADME.mdGoal: derive AGE for one record per subject from the subject's
collected answer.
Input: long-form Operational Data Model (ODM) data with one row per collected item. The export leaves out the form and form repeat fields that every ODM export carries.
Variables:
AGEwould be the subject's collected age.
Without the form level a record's place in the collection cannot be told, so the input is rejected before any record is read, naming the two fields it lacks.
How to fix
Export the ODM data with every level of its hierarchy, the form and its repeat included. When the source nests item groups without a form, the outer group is the form, which is how the engine's own ODM reader writes it:
StudyOID,MetaDataVersionOID,SubjectKey,StudyEventOID,StudyEventRepeatKey,
FormOID,FormRepeatKey,ItemGroupOID,ItemGroupRepeatKey,ItemOID,Value
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- odm_schema_field_missing
- requirement
- REQ-1275
expected/error.yaml
phase: validation
condition: odm_schema_field_missing
spec_paths:
- input.ODM.path
requirement: REQ-1275
context:
dataset: ODM
fields: [FormOID, FormRepeatKey]
Inputs
Under review1 source fileinput/odm.csv
Edit4 rows| StudyOID | MetaDataVersionOID | SubjectKey | StudyEventOID | StudyEventRepeatKey | ItemGroupOID | ItemGroupRepeatKey | ItemOID | Value |
|---|---|---|---|---|---|---|---|---|
| STUDY01 | MDV.1 | 001 | SCREENING | 1 | IG.DM | 1 | IT.DM.SEX | F |
| STUDY01 | MDV.1 | 001 | SCREENING | 1 | IG.DM | 1 | IT.DM.AGE | 34 |
| STUDY01 | MDV.1 | 002 | SCREENING | 1 | IG.DM | 1 | IT.DM.SEX | M |
| STUDY01 | MDV.1 | 002 | SCREENING | 1 | IG.DM | 1 | IT.DM.AGE | 28 |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Variable Name | Variable Label | Type | Length | Controlled Terms or Format | Origin | Core | Conversion Definition | Variable Type | Variable Order | Comments for Define |
|---|---|---|---|---|---|---|---|---|---|---|
| STUDYID | Study Identifier | Char | Collected | Copy value from ODM.StudyOID. | SDTM | 1 | ||||
| USUBJID | Unique Subject Identifier | Char | Collected | Copy value from ODM.SubjectKey. | SDTM | 2 | ||||
| AGE | Age | Num | Collected | Read collected ODM item IT.DM.AGE; no identified record yields blank. | SDTM | 3 |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 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 |
Comments
Signed in with GitHub; saved in repository Discussions