Summary
The FDA expects pharmaceutical companies to provide the SDTM Annotated CRF (acrf.pdf) as part of the electronic FDA submission package. The ClinSpark Sample CRF (sometimes called Blank CRF) provides customers with a Case Report Form that complies with the FDA’s requirements for PDF documents that can be marked up in order to create an Annotated CRF.
Compatibility
Standards
The following standards have been followed:
Industry Guidance
The following industry guidance has been followed where possible and appropriate:
https://www.pinnacle21.com/blog/formatting-annotated-case-report-forms
https://www.pinnacle21.com/blog/formatting-annotated-case-report-forms-part2
Recent Changes
Key changes. May not include minor changes.
Fonts updated to be in the 9-12 points range
Margin at least 3/4" of left and 3/8" on other sides but header/footer should not appear within 3/8”.
For landscape orientation, the margin of 3/4" at the top allows a more legible display of information
Study Events have been renamed as Visits
Dates follow the pattern ddMMMyyyy HH:mm:ss and are consistent with the web application
Added a Form based Table of Contents
Title of the document is now "crf-[study number]-[site number]-[subject identifier]” in lower case
The subject is now identified by one selected identifier across the cover page and subsequent pages. Lead-in numbers are not displayed by default
The filename is configurable and defaults to screening number
Inherit Zoom is supported across all properly bookmarked PDFs
The default Visits Table of Contents can be configured not to display
In the case of multiple AEs, bookmarks can be set to point only to the first AE
Where available, timepoints are added to the Visits bookmarks
Bookmarks are collapsed by default
Subject Over Volunteering page can be set not to display
Visits are displayed in the PDF in the order they are displayed in the user interface
Configuration Requirements
The behaviour of the Completed CRF report can be adjusted through system level configuration options available to IQVIA support staff.
Global Setting
System level configuration is through the use of a Global Setting with a key of CompletedCRFReportSettings
. The setting value is in "JSON" format.
The use of configuration is perhaps best illustrated through examples. Firstly, consider a Global Setting value that configures the Sample CRF Report to hide the ‘code lists’ section:
{ "includeScreeningNumber": true, "includeLeadInNumber": false, "filenameIncludesScreeningNumber": true, "filenameIncludesLeadInNumber": false, "filenameIncludesRandomizationNumber": false, "displayVisitToc": true, "displayFormToc": true, "includeOverVolunteeringForm": false, "onlyDisplayFirstAePerVisit": false }
Details
Available Settings
The available settings are as shown in the following table.
Setting Name | Description | Possible values | Default |
---|---|---|---|
| Controls visibility of the Screening Number in the PDF |
|
|
| Controls visibility of the Lead in Number in the PDF |
|
|
| Controls whether screening number is used in the filename |
|
|
| Controls whether lead in number is used in the filename |
|
|
| Controls whether randomization number is used in the filename |
|
|
| Controls whether a Table of Content is displayed for Visits |
|
|
| Controls whether a Table of Content is displayed for Forms |
|
|
| Controls whether OverVolunteering forms are displayed |
|
|
| Controls linking behaviour for Adverse Events |
|
|
Other Output Drivers
Visit Names and Order
This is dictated by the names and sequence of Study Events in the Study Library…
Remember that Study Events can be dragged and dropped in the UI…
User Interface
The report can be accessed via the Study | Report menu once a study has been selected…
The report includes the ability to:
Include Non-CRF data
Include non-randomised subjects
Exclude Data Audit Trails
Exclude Review (signing, non-signing) information
Filter to given subjects
Display Item Names
Limitations / Restrictions
This report is expected to pass validation using https://www.lorenz.cc/Solutions/eValidator-BASIC/. Exceptions are listed below.
ClinSpark does not support a way to set the ‘fast web view’ setting. It’s likely that this will require a new version of ClinSpark
Depending on the viewer used to open the PDF output, bookmarks may be expanded when the document is first opened. Some viewers correctly present the bookmarks as closed
ClinSpark has no direct way to set the ‘inherit zoom’ property of the PDF output, but we believe that this works under typical conditions