Previous Topic

Next Topic

Book Contents

Book Index

Overview of the CRF Submit system architecture

The following diagram shows the components that convert InForm study data into PDF files.

Components

Component

Description

CRF Submit client computer

The computer on which you use Internet Explorer to access the CRF Submit server to create and monitor work orders.

CRF Submit server

  • Generates XML and includes the CRF Submit web server.
  • You can use a centralized location for the storage and retrieval of the XML information that is to be converted into HTML and subsequently into PDF files.

CRF Submit database

An Oracle database that:

  • Tracks CRF Submit processes including:
    • Time a work order is submitted.
    • Time a work order is started and finished.
    • Names of the CRF Submit computers.
    • Error messages.
    • The status of work orders.
  • Stores the queue of Document Generator jobs until they are completed. Work orders and completed jobs remain in the database until an administrator purges them.
  • Stores the XML that is received from the CRF Submit Adapter server and later turned into PDFs.

Document Generator server

Performs final conversion to PDF files.

Network file server

Repository to hold the final PDF output.

CRF Submit Adapter server

Processes requests from the CRF Submit web server and retrieves clinical data from the InForm database and converts it into XML format.

Study database

Maintains and controls study data as it is entered into the InForm application. Contains the source data for the PDF, XML, and HTML files generated by the CRF Submit application.

Note: The CRF Submit application does not modify the InForm data.

Copyright © 2005, 2016 Oracle and/or its affiliates. All rights reserved.