Enhancements to Oracle CRF Submit archives and reports

The shared servers now use the Chrome Engine to generate PDFs

This move leverages Chrome Engines' ability to optimize PDF generation when converting clinical trial data into PDFs. The result? A noticeable performance improvement when using Oracle CRF Submit.

Also, using the Chrome Engine to generate PDFs results in better PDF rendering, which reduces the number of pages in your requests' output.

Note:

Moving to this technology does not result in any layout changes in the PDFs.

We've made it easier to locate RTSM data in the PDF output of an Archive

The PDF output for Submission, Archival (site and sponsor), and Custom Archive requests now include a new heading, Subject Randomization History. This was previously called Subject History.

The PDF output includes this section when you set the Advanced Setting, Include RTSM Data, to Yes.

For more information about this setting, see Available archive types and reports in the Reporting Guide.

In-product filters are now available for the Site Confirmation report

The Site Confirmation report now includes in-product filters. Before introducing these filters, site, and sponsor users were required to generate the report for all data, only then being able to filter data directly in the output file, which can be cumbersome for studies with many sites.

A new set of filters is available under the Settings side panel in the user interface, allowing users to apply filters before generating the report.

The new available filters are:

Request Name
Request Type
Published Date
Site Name
Confirmed By
Confirmation Date
Confirmation Status

You can find additional information in the Reporting Guide after the Release Assessment Environment (RAE) upgrade.