Clinical Views are created for each CRF form in a Project when a Draft is published. The views contain up-to-date subject data for the form with standard values and units.
Note: Data that is presented in Clinical Views only includes data for subjects that are in sites within the user's site group assignments.
The purpose of the Clinical Views feature is to make database views available for each form in the Project and for all lab-related data points in a simple tabular format. This tabular format will assist in report generation against the entered subject data and allow for creation of reports with subject data that is up–to-date at all times. Clinical data for these views can be accessed using third-party software serving this purpose.
A new table will be created for all forms with one row for each record in the existing Records table, including columns for each data point in the record and standard header information.
For each form, the following two database views will be created from this new table every time a new draft version is published:
Regular View
This view performs datatype transformation and verifies whether each data value is conformant. If it locates non-conformant data, it returns NULL.
Note: A PROD Clinical View containing data only from a production environment can be generated in parallel with a Regular Clinical View. The structure of this view is based on those published CRF versions which have been pushed to a PROD environment. Likewise, a production Lab View can be generated in parallel with regular lab view, one per subject.
Raw View
This view includes data point values with no data type transformation.
For each project:
Lab View
This view includes data on all lab fields (fields containing Analytes) within the project.
For Lab form data, a separate new table will contain all data points which are related to analytes (lab data points). A Lab Project level view will be created from this table when a new draft version is published in addition to the Regular and Raw views.
Each view will include a Cartesian join to the Users table that will apply restrictions when accessing clinical views. Users will not be able to see data which their Role does not permit them to see.
The following restrictions will apply to users with:
Form restrictions - views for the form will not display any data
Field restrictions - data for a field/column in both views will display as NULL or blank
Data Status restriction - views will not show data to the user until a certain status is reached
Subject Status restriction - views will not show subjects with a certain status, if the user cannot see subjects with that status
Study Site Access restriction - views will not show data for a particular site
Site Group Access restriction - views will not show data from a site group or any child sites
Primary Subject Name Restrictions - views will not show primary subject name
Secondary Subject Name Restrictions - views will not show secondary subject name.
Copyright © 2014 Medidata Solutions, Inc. All rights reserved.