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
README.mdPublic entries: Python and R. Passing coverage requires an installed inventory.
Goal: read the analysis start of each concomitant medication as ISO 8601
text (ASTDTC) from the collected start (CMSTDAT).
Input: concomitant medication records, each identified by its sequence
number (CMSEQ), carrying the collected start as the site wrote it, here
slashed dates such as 03/04/2001.
Variables:
ASTDTCwould be the start as ISO 8601 text. A slashed date reads as month, day and year when the month comes first, and as day, month and year when the day comes first. Both orders are accepted at once here, so a slashed date has no single reading, and the run stops before any record is read.
Note: 03/04/2001 is March 4 when the month comes first and April 3
when the day comes first, so the order must be one decision for the study,
never a guess per record.
How to fix
Keep the one order the sites used, as their case report forms or data transfer agreement state it. For sites that write the month first:
derivation:
date_text:
source: CM.CMSTDAT
forms: [iso, mdy_slash]
For sites that write the day first, list dmy_slash instead. When sites
used different orders, correct the collected values to one order upstream
before reading them.
Expected failure
Editthe run is rejected; no artifact is acceptedexpected/error.yaml- phase
- validation
- condition
- invalid_field_type
- rule
- TIME-22
expected/error.yaml
phase: validation
condition: invalid_field_type
spec_paths:
- columns.ASTDTC.derivation.date_text.forms
rule: TIME-22
context:
operation: date_text
expected: mdy_slash or dmy_slash, not both
Inputs
Under review1 source fileinput/cm.csv
Edit2 rows| STUDYID | USUBJID | CMSEQ | CMSTDAT |
|---|---|---|---|
| YAMAA-01 | 1 | 03/04/2001 | |
| YAMAA-01 | 2 | 12/25/2001 |
Unexpected Output
Under reviewNo artifact is producedNo fixture files in this directory.
Human review and assessment
| Dataset Name | Variable Name | Variable Label | Type | Codelist/Controlled Terms | Core | Computational Method | Origin |
|---|---|---|---|---|---|---|---|
| ADCM | STUDYID | Study Identifier | character | Copy value from CM.STUDYID. | Predecessor | ||
| ADCM | USUBJID | Unique Subject Identifier | character | Copy value from CM.USUBJID. | Predecessor | ||
| ADCM | CMSEQ | Sequence Number | numeric | Copy value from CM.CMSEQ. | Predecessor | ||
| ADCM | ASTDTC | Analysis Start Date Text | character | Read CM.CMSTDAT as ISO 8601 date text from ISO 8601 date text, month-first slashed dates such as 03/04/2001 for March 4 or day-first slashed dates such as 03/04/2001 for April 3; blank when it is blank; any other spelling is an error. | Derived |
| Version | Date | Author | Description | Reviewer | Sign-off |
|---|---|---|---|---|---|
| 1.7 | 2026-10-20 | yamaa docs build | Read 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.6 | 2026-10-17 | yamaa docs build | Describe collected date parts written as ISO 8601 date text and times of day counted in seconds since midnight | ||
| 1.5 | 2026-10-17 | yamaa docs build | Name 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.4 | 2026-10-15 | yamaa docs build | State datetime precision codes through the hour and minute, and complete only the time parts a collected datetime lacks | ||
| 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 |
yamaa