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: complete the analysis start date (ASTDT) of each
adverse event (AE) from its collected onset text (AESTDTC).
Input: collected event records carrying the reported term
(AETERM) and the collected onset text (AESTDTC).
Variables:
ASTDTwould be the analysis start date completed from the onset text: a complete collected date unchanged, a year-and-month completed to its first day, a year-only start completed to January 1. Text that cannot be read as a date or the beginning of one has no stated completion, so the run stops when it reaches it and no artifact is accepted.
Note: a date that was never collected and text that cannot be read as a date are different defects, and neither has a stated outcome here.
How to fix
Correct UNKNOWN upstream when a date can be recovered. If invalid date text
is intentionally treated as no analysis date, declare that outcome locally:
derivation:
date_impute:
source: AE.AESTDTC
month: 1
day: 1
invalid: null
The invalid outcome applies to text that is not a calendar date or date
beginning; it is distinct from text that was never collected, which
missing answers.
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.ASTDT.derivation.date_impute
requirement: REQ-0588
context:
source: AE.AESTDTC
value: UNKNOWN
keys:
- STUDYID: YAMAA-01
USUBJID: YAMAA-01-101
AESEQ: 4
Inputs
Under review1 source fileinput/ae.csv
Edit4 rows| STUDYID | USUBJID | AESEQ | AETERM | AESTDTC |
|---|---|---|---|---|
| YAMAA-01 | 1 | Headache | 2023-06-15 | |
| YAMAA-01 | 2 | Nausea | 2023-06 | |
| YAMAA-01 | 3 | Fatigue | 2023 | |
| YAMAA-01 | 4 | Dizziness | UNKNOWN |
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 | ASTDT | Analysis Start Date | numeric | ISO 8601 | Impute incomplete date from AE.AESTDTC, defaulting month=1, day=1; missing or invalid input yields null. | 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