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 end date (AENDT) for each
adverse event (AE), rejecting any completion that lands on a day
the month never has.
Input: adverse event records carrying collected end text
(AEENDTC) and reported term (AETERM).
Variables:
AENDTwould be the analysis end date completed fromAEENDTC: a year alone becomes 31 December, a year and month becomes the 31st of that month, and a complete date is kept as collected. A year and month whose month has fewer than 31 days would complete to a day that month never has, which is not a calendar date, so the run fails and no artifact is accepted.
How to fix
Decide which day an end date collected without one should take. To keep the latest date the collected text allows, name the last day of the month rather than a number:
date_impute:
source: AE.AEENDTC
month: 12
day: last
A year and month such as 2023-04 then completes to 2023-04-30 instead of
the impossible 2023-04-31, 2023-07 still completes to 2023-07-31, and a
February takes the 28th or 29th according to the year. A fixed day from 1
through 28 is valid in every month too, but it is a different imputation
policy, not a repair of this one.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- impute
- condition
- invalid_calendar_date
- requirement
- REQ-0608
expected/error.yaml
phase: impute
condition: invalid_calendar_date
spec_paths:
- columns.AENDT.derivation.date_impute
requirement: REQ-0608
context:
value: "2023-04"
completed: "2023-04-31"
keys:
- STUDYID: YAMAA-01
USUBJID: YAMAA-01-101
AESEQ: 2
Inputs
Under review1 source fileinput/ae.csv
Edit2 rows| STUDYID | USUBJID | AESEQ | AETERM | AEENDTC |
|---|---|---|---|---|
| YAMAA-01 | 1 | Nausea | 2023-07 | |
| YAMAA-01 | 2 | Fatigue | 2023-04 |
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 | AENDT | Analysis End Date | numeric | ISO 8601 | Impute incomplete date from AE.AEENDTC, defaulting month=12, day=31; 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