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: one analysis record for each collected event, carrying
the start-date completeness flag ASTDTF.
Input: collected event records carrying the reported term
(AETERM) and the collected start (AESTDTC).
Variables:
ASTDTFwould contain how much of the start dateAESTDTCcarries:Dfor a full date,Mfor a year and month,Yfor a year alone, and blank when the start was never collected. Text that is neither a date nor the beginning of one has no completeness to report, so the run stops when it tries to read precision from it and no artifact is accepted.
How to fix
Correct the source text when a date can be recovered. If invalid date text is intentionally represented by a missing precision flag, declare that separately from the existing missing-source behavior:
date_precision:
source: AE.AESTDTC
missing: null
invalid: null
The invalid outcome covers UNK; missing covers a source value that
was not collected.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- impute
- condition
- invalid_date_text
- requirement
- REQ-0588
expected/error.yaml
phase: impute
condition: invalid_date_text
spec_paths:
- columns.ASTDTF.derivation.date_precision
requirement: REQ-0588
context:
source: AE.AESTDTC
value: UNK
keys:
- STUDYID: PILOT7
USUBJID: P7-341
AESEQ: 2
Inputs
Under review1 source fileinput/ae.csv
Edit2 rows| STUDYID | USUBJID | AESEQ | AETERM | AESTDTC |
|---|---|---|---|---|
| PILOT7 | 1 | Nausea | 2023-06 | |
| PILOT7 | 2 | Fatigue | UNK |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Comments and assessment materials
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADAE | STUDYID | Study Identifier | character | Copy value from AE.STUDYID. | Predecessor | ||
| ADAE | USUBJID | Unique Subject Identifier | character | Copy value from AE.USUBJID. | Predecessor | ||
| ADAE | AESEQ | Sequence Number | numeric | Copy value from AE.AESEQ. | Predecessor | ||
| ADAE | ASTDTF | Analysis Start Date Imputation Flag | character | Collected date precision of AE.AESTDTC: D for a complete date, M for year and month, Y for a year alone; a missing source → blank. | Derived |
| 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