Intro to aCRF Formatting
"How should I best format the annotations on my CRFs?" We get that a lot. The requirements may feel murky. Users often mimic CDISC’s sample aCRF (in the Define-XML v2.0 download). But even then, you might lack confidence on the specific formatting details, and wonder how to fit your content into the usable space.
This is the first in a series of posts where we answer questions from our recent webinar, Best Practices for Annotated CRFs. Below, we’ve summarized the regulatory expectations and our top insights. For some items, we say "recommend," since there’s no formal requirement. View them as best practices found in our talks with industry experts and our review of existing guidance.
Formatting Text
See the example aCRF below that illustrates these points.
Formatting Backgrounds
See the example aCRF below that illustrates these points.
More to Come
We hope these items give you a confident default for your workflow. For further reading, see our white paper. And please check back as we continue this series of posts!
Reference: Table of Conventions
This table shows the naming conventions frequently encountered in making aCRFs.
Type | Convention | Example |
---|---|---|
Dataset | XX = Domain Label | AE = Adverse Events |
Variable |
VARNAME XX.VARNAME VARNAME1/VARNAME2 |
AETERM DM.SUBJID EXSTDTC/EXENDTC |
Variable and Value |
VARNAME = “VALUE” VARNAME1/VARNAME2 = “VALUE” |
DSTERM = “RANDOMIZED” DSTERM/DSDECOD = “RANDOMIZED” |
Value Level |
SUPPXX.QVAL where QNAM = “VALUE” VARNAME1 where VARNAME2 = “VALUE” VARNAME1 where VARNAME2 = “VALUE1” AND VARNAME3 = “VALUE2” |
SUPPQS.QVAL where QNAM = “RTRINIT” VSORRES where VSTESTCD = “SYSBP” FAORRES where FATESTCD = “ONSETDTC” and FAOBJ = “TRIAL DISEASE” |
Unsubmitted data | [NOT SUBMITTED] | [NOT SUBMITTED] |
Tags:
Blog Main Page