This lesson provides an overview of Viedoc Clinic. It describes the user interface and summarizes the main settings that can be configured in Viedoc Clinic.
Viedoc Clinic is the interface for the end user, and is primarily used by site and study staff (Investigators, Study Coordinators, Monitors, Data Managers and so on) and keeps track of all the activities performed by the site.
The access to Viedoc Clinic is by invitation only and provided by either the Study Manager or Site Manager. If invited, you will find the invitation in your email inbox (from no-reply@viedoc.net). In some cases the email can be caught by your email spam filter and in that case you will find it in the email spam folder. For detailed instructions on account activation, see Managing your Viedoc account.
The following main actions can be performed in Viedoc Clinic:
Customer computer requirements are defined as capabilities required by the customer computer to use all features of Viedoc with the intended graphical presentation and within guaranteed response times of Viedoc.
Viedoc supports the following browsers:
For non-compliant browsers you will receive a message on the login page that your browser is not supported.
For Viedoc Designer:
Viedoc does not support the use of private mode browsing in Safari.
The following are required for Viedoc to run in the compatible web browsers:
No data is permanently stored on the customer computer. All data stored in session cookies or local web storage is deleted when the browser session is terminated. The only exception to this is the optional persistent cookie used in the main portal of Viedoc 4 to remember if a user chooses to issue a 2FA trust for the browser for 30 days, and thus avoid further second-factor authentication during this period.
Viedoc 3 has no automatic checks enforcing the above requirements. Viedoc 4 checks for, and enforces, browser type and version, and support for JavaScript, local web storage, and session cookies.
The following screen resolutions are required:
Viedoc requires an internet connection of at least 384 kbit/s.
Viedoc requires an outbound firewall policy allowing encrypted HTTP to be established and communicated to a remote server on port 443 (HTTPS) using Transport Layer Security (TLS) version 1.2 or higher.
There are several layers of security built into the platform. Below are some examples:
| Important! All information related to managing your Viedoc account can be found in the following user guide: Viedoc User Account Management |
From the settings button (wheel) you can perform all actions related to managing your Viedoc account by selecting any of the following: Edit your profile, Change Password, Security Settings:
Selecting any of these options opens a new page, in the example below, the User Settings page. Select the Viedoc learning link to open the Viedoc User Account Management Guide:
When you are logged in to Viedoc, you can edit your profile.
To view or edit your user settings, select the settings button (wheel) in the top right corner of the landing page, and select Edit your profile. The User Settings page opens, where you can configure the following:
1. User name - this is your primary email address used for your Viedoc account. This is the user name you use to log in to Viedoc. See the information below about your primary email address.
2. First name and Last name - fill in these fields that are used for your Display name, used in Viedoc to identify your user.
3. System language - select the language of your choice from the drop-down menu.
4. Primary email address - this is the same as the User name described above. It is the email address used in Viedoc to log in, as well as for Viedoc user account-related operations (account setup, password recovery, study invitations).
By default, this is set to the email address used to initiate the Viedoc user account.
The primary email address must be unique and is mandatory. Therefore, it is not possible to delete the primary email address.
See Changing the primary email address.
5. Secondary email addresses - you can add up to 3 additional email addresses that will be used by Viedoc to send notifications on alerts and trackers as configured in Viedoc Designer. Viedoc alert emails will be sent to all the primary and verified secondary email addresses set up for your account.
See Adding a secondary email address and Verifying a secondary email address.
6. Mobile number - Select your country code and enter your mobile number.
You will be asked to Save and verify mobile number. A validation warning (8) will be displayed if the mobile number is not valid.
See Editing your mobile number and Verifying your mobile number.
Important!
|
7. Contact information - fill in the following fields: your street address, city, state, postal code and country.
To add a new (secondary) email address to your account:
| 1 | Select the Add another email address link under the current primary email address. |
| 2 | Enter the email address in the new field under Secondary email addresses. |
| 3 | Select Save changes. A notification email is sent to both the primary email address and to the newly added email address to inform you about the change. At the top of the Edit your profile page, you will see a warning message saying that the newly entered email address is not verified. |
To verify a secondary email address:
| 1 |
Select the Verify email address link next to the newly added email address. A six-digit code will be sent to your new email address and a Verify ownership pop-up is displayed asking you to provide the code in order to verify the new email address. Note! The verification link for the secondary email address is shown only after having saved the changes you may have performed on the other fields on the same page. |
| 2 | Enter the received code and select Confirm. The newly added secondary email address is now verified. |
To change the primary address to one of the existing secondary email addresses:
| 1 | Select Set as primary next to the secondary email address that is to be set as the primary email address. |
| 2 | Select Save changes. A notification email will be sent to both email addresses to inform you about the change. You will use the new primary email address the next time you log in to Viedoc. |
Note! For a secondary email address to be able to be set as primary, it has to be verified first.
To edit your mobile number:
| 1 | Select your country code and enter your mobile number. |
| 2 | Select Save and verify mobile number. A notification email will be sent to your primary email address to inform you about the change. |
To verify your mobile number:
| 1 | Make sure that the mobile number is correctly entered and select Verify mobile number. |
| 2 | A six-digit code will be sent as a text message to your mobile and a Verify mobile number pop-up is displayed. It will ask you to provide the code in order to verify the mobile number. |
| 3 | Enter the code and select Confirm. The mobile number is now verified. |
From the settings button (wheel) you can perform all actions related to study access management in Access Settings.
Select the settings button (wheel) in the top right corner of the window, and select Access settings.
The following information is provided, grouped by study:
For users with organization roles, these are listed in the top of the page, in a separate section, providing the following information:
To remove yourself from a certain role within a study:
| 1 |
Select the trash can icon on the right, corresponding to the role, site and study to be removed from: A confirmation window is displayed. |
| 2 |
Select Delete to confirm the deletion: A notification email will be sent to all the Study Managers, or to the Site Managers if any roles are delegated. |
You can remove your Viedoc account when you have no study memberships left, that is, 0 roles in 0 studies.
To delete your Viedoc account:
| 1 | Go to Access Settings. To be able to remove your account, you should have no roles left in any study and no pending invitations: |
| 2 | Select Remove account from Viedoc. You will be prompted to confirm the account removal by entering your password: |
| 3 | Enter your password and select Delete. A confirmation message is displayed and a notification email will be sent to your primary email address:
For identification purposes, Viedoc will keep: the user ID, display name, primary email address, and login history. They are kept until all the studies you have participated in are deleted. All other information related to your account will be removed from Viedoc. |
In case you have study invitations that you have not accepted or rejected yet, the Pending invitations window displays a list of all your pending study invitations:
To accept a study invitation, select Approve next to the respective study role. If this is the first role you have in the respective study, and if the study requires an activation password, you will be prompted to enter it:
Note! All the pending role invitations for a user are automatically approved when the Application Programming Interface (API) method GetToken/Token is used.
To reject a study invitation, select Reject next to the respective study role. The invitation will be removed from the Pending invitations list.
To postpone the approval or rejection of study invitations, select Close in the top right corner of the Pending invitations window and postpone providing an answer to the study invitation.
To access the pending invitations again, the Pending invitations window is shown:
From Viedoc you can log out from different locations:
Note! If you exit the system without logging out, any subject you are currently working with will be locked for other users. After 5 minutes, the subject will be automatically unlocked.
This lesson describes the Viedoc landing page, which is displayed directly after a successful log in:
The landing page provides the following summary information:
| Skill level | Icon | Description |
|---|---|---|
| Rookie |  |
≤ 20 logins |
| Semi-pro |  |
21-100 logins |
| Pro |  |
101-1000 logins |
| Legend |  |
> 1000 logins |
The study slider shows the studies you have access to - each study is represented by a study logo. If you have access to many studies, you can easily find a specific study by entering the study name in the search field. All studies containing characters of the search string appear in the search results.
A progress bar is shown below each study logo. The percentage displayed is calculated by the mean completion of each subject (rounded down). Thus, it measures the total completion of the study.
Note!
Select a study logo to select a study to work with. The study start page is loaded on the lower half of the screen, for more information, see Study start page.
If you are an Administrator and/or Designer you will also have access to Viedoc Admin and Viedoc Designer. Select the respective icon at the upper right corner of the landing page:
When you select the study logo in the landing page, the study start page loads, which contains the following icons that give access to different features, or enable you to view information about the study:
1. Study status
2. Messages
3. Data Export
4. Metrics and Viedoc Reports
5. Roles
6. Reference data
7. Medical coding
8. Viedoc Logistics
9. Viedoc eTMF
10. Demo mode
11. Launch
12. eLearning / Documentation & Training
13. Support
Notes!
The first page displayed when you select a study is, depending on the status of the mandatory documentation and training materials, as below:
| Important! All the mandatory materials must be "Read & Understood" and signed before you can launch the study. You might be able to launch the study in demo mode, depending on the study settings performed by the Study Manager. |
The Study status page is the first page that is shown when accessing a study, if you do not have any mandatory documentation and training material that needs to be signed. This page gives you an overview of the progress of the study - on study, country and/or site level (depending on which sites you have access to):
You can filter the displayed data for country or site by selecting the name of the country or site:
The following statistical information is provided, for the selected site(s):
Note! For resolved and open queries, this includes only manual and validation queries, not missing data queries. For resolved queries, the following statuses are included: Resolved, Rejected, Approved, and Closed.
Note! All the numbers reflect the data entered in the selected operation mode (demo or production), that is, if demo mode is selected, then the numbers reflect only the data entered in demo mode.
A message can either be a system message (such as notifications on password expiration), a study message (such as eCRF changes - for more information, see Approving eCRF changes, or other notifications according to the study configuration).
In the message window, a blue dot indicates a study-specific alert, a yellow dot indicates a form change requiring approval, and a red dot indicates an expiring password.
An indicator in the top bar of the application indicates whether you have unread messages.
Alert messagesAccording to the study configuration, you can receive alert notifications about important occurrences in the data. (For example, in case of a Serious Adverse Event). Alert notifications can be received in the Messages page and as an email.
Depending on the configuration/study setup, the email might have the PDF of the form that triggered that alert as an attachment.
If the option to enable password protection for the alert email attachments has been selected for your study, you should receive a password to enter to open the attachments. The password is provided by your Study Manager.
When you receive an email copy of the alert message with a password-protected attachment, when you open the file you will see the pop-up below where you can enter your password:
The Data export page enables you to review and download study data in the following formats:
Note! Data export might not be available to all users.
For more information about data export and preview, see Exporting data.
The Metrics page gives an overview of the quality of data in terms of open queries and missing data.
Note! Metrics might not be available to all users.
For a detailed description, see Metrics.
If Viedoc Reports is included in the study license and enabled, it is accessed from the Metrics feature. For more information, see Launching Viedoc Reports.
Note! The Roles page is only available for users with special permission to view roles, as per the study design.
The Roles page provides information on:
Under My roles you can see the roles that you have in the respective study:
The following information is displayed (with examples):
By selecting the green arrow button to the right, you will be directed to the Selection page. This is equivalent to selecting the Launch button.
Here you can see a list of all the roles and the respective user(s) for the site(s) you have access to:
To see user details of each role, select Show log. The log displays:
*date and time in Coordinated Universal Time (UTC) time zone
For each study, you can download user logs in PDF and Excel format with information about all users and roles for the sites you have access to.The generated file reflects the country/site selection in the language you have currently set in Viedoc.
Notes!
You can generate the log for the country/site selection in your current Viedoc language by selecting Generate a PDF file / Generate an Excel file at the bottom of the study start page:
Once the user log is generated you can:
The Log of users and roles PDF contains the following chapters:
The User administration log contains information about all users and roles for the sites you have access to, with the following sheets:
When you select the reference data icon, the list of available reference data source-scope combinations is displayed. From here you can open the reference data editor. For details see Working with reference data.
Note! Reference data might not be available to all users.
The medical coding feature allows you to code reported events like Adverse Events, Medical History and Concomitant Medications. When you select the medical coding icon, the page displays metrics regarding medical coding. There is one set of metrics for each medical coding scope available.
Note! Medical coding might not be available to all users.
For more information about medical coding, see Medical coding.
Viedoc Logistics is the interface for managing the supply of your study. A valid license is required to use Viedoc Logistics.
For more information about Viedoc Logistics, see Viedoc Logistics User Guide.
Viedoc eTMF is a digital repository for capturing, managing, sharing, and storing essential documents.
For more information about Viedoc eTMF, see Viedoc eTMF User Guide.
If enabled, a study can operate in demo mode. You can easily switch between demo mode and production mode using the DEMO MODE switch:
The DEMO MODE switch is only visible when you have access to both production and demo mode.
The demo mode is clearly indicated with demo icons. Make sure you do not enter any real data in demo mode!
See also the video tutorial Activate demo mode.
Select the Launch button to access the patient data and electronic Case Report Forms (eCRFs). The button is only visible when you have access to the study in Viedoc Clinic.
If multiple roles are assigned to you in this study, you are first prompted to select the role you would like to use to access the study.
If you have mandatory documentation pending to be read and signed, this is the first page that is displayed when you access the study.
Under this section, you have access to several eLearning programs and various documentation, depending on the roles that have been assigned to you. For details about the user documentation and certificates, see Documentation & Training.
The Viedoc Clinic User Guides are available in the following languages:
To change the language of the Viedoc User Guide, once opened, select the language from the upper right corner, as illustrated below:
Tip! The various lessons in the Viedoc eLearning can easily be compiled into a PDF and printed if you need to store them in the investigator binder.
Select the support icon to open a pop-up with contact details to the users that can help you in case you need support. Normally you will find the contact details of the Monitor here, as the Monitor typically is the first point of contact to the site.
Depending on the study settings and on the role(s) you have within a study, you might have access to various user documentation. This lesson describes the scenario when, under the eLearning section, you get access to the Documentation & Training page, with mandatory and/or optional documentation section(s), as illustrated in the following image:
The available documentation and training materials are split in two main categories:
1. Mandatory sections - contains all the materials that are mandatory for you to read, understand and sign before starting to work.
If you have mandatory documentation pending to be read and signed, then the first page that opens when you access the study is the Documentation and Training.
| Important! All the materials under Mandatory sections must be "Read & Understood" and signed before you can launch the study. You might be able to launch the study in demo mode, depending on the study settings performed by the Study Manager. |
2. Optional sections - contains additional educational and reference materials that you have access to. Simply click on the link to open each of the available documents/links.
To work within a study for which mandatory training sections were assigned, you need to read, understand and sign all the sections listed as mandatory.
To obtain the user certificate:
| 1 | Click the link to open the section. Read through and, when you're done, go back to the Documentation and Training page and click Read & Understood. A date and time stamp in Coordinated Universal Time (UTC) will be shown in the Read & Understood at column: |
| 2 | Repeat step 1 for each of the mandatory sections. When all the mandatory sections are marked as "Read & Understood", a Confirm 'Read & Understood' link becomes available: |
| 3 | Click Confirm 'Read & Understood'. A confirmation pop-up opens: |
| 4 | Enter your Viedoc account password and click Confirm. A confirmation message together with the date and time stamp (UTC) is displayed at the bottom of Mandatory sections. Also, a link to Download your User Certificate becomes available: |
| 5 |
Now you got your certification and are able to access the study. The Launch button is now available. You can also Download your User Certificate. For details, see Downloading your user certificate. The mandatory sections are still available for your further reference, you can at any time go back and open any of those by clicking the section link. |
After you have completed all your mandatory readings and have signed and confirmed, as described in the previous section, you can download your user certificate in PDF format by clicking Download your User Certificate in the bottom of Mandatory sections.
The following information is provided on the certificate:
The Selection page displays all the subjects from all the sites you have access to:
In the default view, each subject is represented by a card. Depending on your study setup, the Selection page can be displayed in several ways. See Views of the Selection page.
In the top right corner of the Selection page, you have dropdown menus to sort and filter the view. The options depend on the selected view. The selected sorting will be kept throughout your session.
In the table view of the Selection page, you can also sort by column in descending or ascending order by selecting a column header with the arrow symbol. Lit-up arrows indicate the selected sorting in orange:
Notes!
To search for a specific subject or any other information collected for a subject, you can type the text you are looking for in the search field:
The system will return the subjects with the information sought that has been entered in the Case Report Form (CRF).
Subject key and All data are two filters that can be applied to the search.
Note! For faster searches, we recommend that you select the Subject key filter.
| Important! If your search returns nothing, it could indicate a problem with your study design. Please contact your Professional Services representative to assist you. |
The Selection page displays a number of icons explained in the following table:
| Icon | Description |
|---|---|
 |
Issue - at least one open query and/or missing data |
 |
Task - there are tasks to be completed, the number indicates the number of tasks |
 |
Complete - all initiated events have been completely filled in |
 |
Signed - all data that is possible to sign has been signed |
 |
Read-only - the card is being open for edit by another user. Note that the subject card can still be accessed for review or SDV by a user without edit permissions, for example a monitor or a data manager. |
 |
In progress - the event is initiated but not completed This icon is only shown when none of the other status icons apply |
 |
Locked - the data in all forms of the event is locked |
Note! The icons showing depend on your user role permissions.
Depending on the study setup, the Selection page looks a bit different.
In the Cards view, you can see all the subjects from all the sites you have access to. Select to display the subject cards side-by-side (default) or in a table:
The subjects are sorted by added date, where the most recently added subject is displayed first. You can sort the subject cards by selecting an option in the upper right corner:
To display only the subjects for a particular site, select the site from the dropdown list. Click Include deleted subjects at the bottom of the dropdown menu to display deleted subjects:
Each card provides subject information as per the respective study design:
If all the forms were locked (typically by the Monitor), this is shown with a padlock icon on the respective subject card:
Note! The Selection page does not consider the role visibility except for task count; therefore, the subject status reflects the general status of the subject in the study, regardless of the user who has work to be performed. The subject details view reflects the subject status considering the role visibility. This could result in a subject status where a subject could have a green check mark or be locked, while in the Selection page it is not (due to some other user role having unfinished work or forms to complete on the respective subject). See Entering and Editing data for more information on the subject details view.
In the Issues view, you can see the existing issues listed in a table:
Click any row to open the form where the issue was raised:
Close the form to go back to the Issues list.
You can filter the Issues list using the dropdown lists in the upper right corner of the page:
In the Viedoc Me account view, you can monitor and follow up on the subjects' expected Viedoc Me event submissions.
For each subject, the following information is listed:
In the Events view, you can see the status of each event for each subject listed in a table.
The first column indicates if there are issues/tasks in any of the subjects' events. If there are both issues and tasks for a subject, then issues [ i ] are shown in the column.
Select any cell to go to the event in the Details page:
Click back in the browser to return to the Events view.
Select an empty cell to view the subject's latest event.
The list of subjects can be filtered using the dropdown lists in the upper right corner of the page:
Note! On the selection page, in the Events view, the event name (as set in the Study event settings in the study design) is displayed. If there is a recurring event, a counter is shown under the event name, for example: Follow up 1, Follow up 2.
To add a new subject:
| 1 |
Make sure that you have selected a site (center) from the sites dropdown list.
|
| 2 |
Complete the form and select Save changes on the top right side of the page. A new subject is now added. |
Note! Only user roles with editing permissions for the study start event form can add a new subject. If you do not have editing permissions, you cannot select Add new card and no icon is visible in the top right side of the page.
See also the video tutorial Add and select subjects.
If you receive the following message, the maximum number of subjects that is configured for your site has been reached, and you cannot add new subjects. If you need to add a new subject anyway, contact your Study Manager.
Note! As a Viedoc Clinic user, you need a special permission to view the metrics.
The metrics feature gives an overview of the quality of data in terms of open queries, missing data and overall site performance. You can filter the displayed data by country and site.
The metrics graphs depict:
Click More about [...] to open a page with detailed metrics about queries, performance or missing data. All detailed metrics pages include filtering possibilities and a bar to show the review status.
Note! The number of open queries differs between the Queries page and the Performance page. The Performance page also includes queries with the state Removed.
If you have access to Viedoc Reports, you can open it from the Metrics feature.
The Queries page includes filtering possibilities and a bar to show the review status for the entire study.
For detailed information about the query process in Viedoc, see Queries overview.
You can filter the data by selecting from the drop-down lists in the top of the page:
Based on the selected filter, the following information is provided:
Queries - a diagram that shows the graphical distribution, the total number as well as the percentage of:
The number in the center of the circle shows the total number of queries.
Note!
For detailed information about query states and pro, see Queries overview.
Query state - a pie chart shows the queries distribution based on the query state:
For detailed information about query states and process, see Queries overview.
Top 5 events - a column bar shows the top five events with the highest number of raised queries (numeric and percentage). The legend of the graph displays the event name.
Top 5 forms - a column bar shows the top five forms with the highest number of raised queries (numeric and percentage). The legend of the graph displays the form name.
Top 5 items - a column bar shows the top five items with the highest number of raised queries (numeric and percentage). The legend of the graph displays the item name.
Top 5 check OIDs - top five most triggered edit checks are displayed in a table including the actual number, percentage, Object Identifier (OID), form name as well as the query message.
The last row of the table shows the total number of queries.
Top 5 subjects (raised queries) - top five subjects that have the highest number of queries with current status raised are displayed in a table including the actual number, percentage, subject ID, study progress, site name as well as date of when the latest query was raised, name of who raised the query as well as the actual query message.
The last row of the table shows the total number of subjects.
For detailed information about query states and process, see Queries overview.
In the bottom of the Queries details page you have the options to:
The Performance page allows you to compare data from:
With data in one of the following:
Based on the comparison selection the graphs will show statistics about:
Subjects - detailed data on the subjects on the selected site(s) (in orange) and compared site(s) (in gray):
The conditions for the following subject statuses are defined in the study design (in Viedoc Designer under Study Settings > Subject status):
Tip! If there is an i symbol inside of a ring graph, you can hover over it to see a description of the status.
Queries - detailed data on queries on the selected site(s) (in orange) and compared site(s) (in gray):
For detailed information about query states and process, see Queries overview.
Missing data - detailed information on missing data (both confirmed and unconfirmed data) on the selected site(s) (in orange) and compared site(s) (in gray):
Other - miscellaneous detailed data on the selected site(s) (in orange) and compared site(s) (in gray):
In the bottom of the Performance details page you have the options to:
The Missing data page includes filtering possibilities and a bar to show the review status for the entire study.
You can filter the data by selecting from the drop-down lists in the top of the page:
Based on the selected filter the graphs will show statistics about:
Top 5 events - a column bar shows the top five events with the highest number of items with missing data (confirmed and unconfirmed), both numeric and percentage. The legend of the graph displays the event name.
Top 5 forms - a column bar shows the top five forms with the highest number of items with missing data (confirmed and unconfirmed), both numeric and percentage. The legend of the graph displays the form name.
Top 5 items - a column bar shows the top five items with missing data (confirmed and unconfirmed), both numeric and percentage. The legend of the graph displays the item name.
The top 5 subjects that have the highest level of confirmed missing data are displayed in a table including:
The last row of the table shows the total number of subjects with confirmed missing data.
The top 5 subjects that have the highest level of unconfirmed missing data are displayed in a table including:
The last row of the table shows the total number of subjects with unconfirmed missing data.
In the bottom of the Missing data details page you have the options to:
Viedoc offers support for adding centralized reference data to the study, which is automatically populated to the subject forms. When centralized reference data is added to a study, reference values don’t need to be entered individually for each subject and each form.
It is possible to configure different sets of reference data that will be populated to the form based on:
| Term | Definition |
|---|---|
| Reference data source | A source that provides reference data (for example a lab). |
| Reference data scope | A set of measurements that a reference data source carries out, and the parameters that might affect these data. The data in one reference data scope will be populated to one lab data form. One or more reference data scopes can be configured in Viedoc Designer > Global Settings, as set(s) of variables and factors (see definitions below). |
| Factor | A parameter that affects the reference data, for example a subject’s gender. Factors may affect the normal range for a test result. |
| Variable | A specific measurement to be carried out. |
| Target type | Item of a certain type of information that a reference data source can provide (such as range, unit, low/high values) for a specific measurement (defined by a variable). Any number of target types can be defined by the user. |
Reference data sources are configured in Viedoc Admin. Each reference data source is linked to one or more reference data scopes that define the following:
For each reference data source-scope combination, the reference values that should be auto-populated to the forms should be entered in the reference data editor in Viedoc Clinic. This can be done by clinic users that have permission to edit and save reference data.
To make the reference values available for auto-population to the subject forms, the reference values should be published. This can be done by clinic users that have permission to publish the reference data values.
See also the video tutorial demonstrating how to work with reference data in Enter reference data.
Note! You only have access to reference data on the landing page, and to the reference data editor, if you have a role with permission to view, edit and/or publish reference data.
On the landing page, you can view or do the following:
1. Select the Reference data icon to display all the reference data source-scope combinations that are linked to the sites you have access to.
For each reference data source-scope combination, the following information is provided:
2. Status indicator that indicates whether reference values have been entered (green) or whether the fields are still empty (grey).
3. Status indicator that indicates whether the reference values have been Published (including date, time and user who published them) or whether the reference values are Not published yet.
4. The number of sites that the reference data source is linked to. This gives an indication of how many sites are impacted in case the reference values are edited.
5. The number of forms that the reference values have been populated to. This gives an indication of how many forms are impacted in case the reference values are edited.
6. The number of users that have permission to edit the reference values.
7. Name of the user who performed the last changes to the reference values, including date and time.
8. Warning message if the latest saved version was not published.
9. Select Open reference data editor to view or edit the reference data, see The reference data editor.
When you select Open reference data editor on the reference data section of the landing page, the reference data editor opens for that specific reference data source-scope combination. Depending on the user rights that are connected to your role, you can view as read-only, edit and/or publish the reference data.
On the reference data editor, you can view or do the following:
1. Select the arrow to expand the reference data table for that specific time period. The newest time period is expanded by default and shown at the top of the list.
2. The number of the reference data set for a given time period. This number is given by default, based on the order in which the reference data sets have been created.
3. The period the reference data set is valid.
4. Select Add new to create a new reference data set for a new time period.
5. Select Duplicate to create a new reference data set for a new time period based on a previously created set.
6. Select the trash can icon to remove an existing reference data set time period.
7. Reference variable name - the variable that are defined for that reference data scope. A variable is a specific measurement to be carried out. See Variables for more information.
8. Factors - the factors that are defined in the scope. Factors are parameters that affect the reference data. See Factors for more information.
9. Values to be populated - the reference data values provided by the reference data source. The values entered here will automatically be populated to the subject forms.
10. Select Cancel to discard all the changes performed and revert to the latest published reference data.
11. Select Save to save the changes performed.
Note! Only users with clinic roles that have permission to edit reference data can edit and save the reference data.
Upon save, the reference data set becomes available for publishing.
12. Select Publish to publish the reference data. A pop-up appears asking you to enter a message. This message appears in the Messages section on the landing page.
Publishing makes the data available for auto-population into the subject forms.
Note! Only users with clinic roles that have permission to publish reference data can publish the reference data.
The column Reference variable name displays the variables that were configured for the reference data scope. By selecting the arrow to the right of the variable name, you can:
When the variable is not included, such as 3 in the image, you can:
Note! If you do not want automatic population of reference data for a certain variable, the variable should be set to Not included. This way, it is possible to manually add reference data for that variable to a form.
The column Factors displays the factors that were configured for the reference data scope. In this column, you can:
1. Select the arrow to the right of Factors, and select a factor from the drop-down list to add that factor to the table. If no arrow is displayed, all factors predefined in the reference data scope are already added (as in the image).
2. Select the arrow to the right of the factor label and select Remove to remove that factor from the table.
By default, a newly added factor is populated with N/A (not applicable) in the table. You can edit this by selecting the arrow to the right of N/A and select one of the options from the drop-down list. The drop-down list displayed varies depending on whether the factor has predefined factor options or not.
3. For a factor that has predefined options, such as Sex in the example:
+ in front of it to add a new row to the column populated with the selected option, or4. For a numeric range (no predefined options), such as Age in the example:
Note! If you would like to add the factor option N/A to a factor that also has other options, the option N/A should be the last entry for that variable in the table. The reason for this is that, while populating a form with reference data, the system is matching the factor options starting from the top of the table. If a match is found, the corresponding data are populated to the form. The option N/A is always a match. So if N/A is listed at the top of the table, the search will stop and the form will be populated with the data corresponding to N/A. If you want the system to match the other factor options first, these should be listed before N/A in the table.
When the reference data are published, they become available for auto population to the forms they are intended to be used in.
To populate a form with reference data, the Investigator/Study Nurse/site staff selects:
It is also possible that the event date is used instead of date and time of collection. In that case, the reference data populate after the source is selected.
Tip! If you do not want any reference data to be populated automatically, do not select a reference data source, but leave the drop-down list as Select a source. No automatic population of data will take place and you can fill in the fields manually.
Note! When populating numeric fields using functions and reference data, they automatically receive the number of decimals configured in the design.
Note! No reference data can be populated, if...
Note! You can only enter reference values when your role has permission to edit reference data.
To enter a new set of reference values:
| 1 | On the Viedoc landing page, select the Reference data icon. |
| 2 |
Select Open reference data editor for the reference data source-scope combination you would like to enter values into.
|
| 3 |
Select the date from which, and to which, this set of reference values is valid in the Valid to and Valid from fields. 
|
| 4 |
Select the arrow to the right of Factors and select the factors that should be included. 
|
| 5 |
For every variable, and for every factor, select the arrow to the right of N/A and select the factor options that should be included. If the factor is a numeric range, select Set a value. By default, the inclusive in between option appears. 
If you would like to change the type of the range, select the arrow again and select the type of range you would like to include. If necessary, select Add new row to add rows. Manually enter the values of the range in the blue fields. 
See also Factors for more information. |
| 6 | For every variable, and for every factor, enter the reference values that should be automatically populated to the forms. |
| 7 | Select Save to save the reference data. |
To publish reference data:
Note! You can only publish reference data when your role has permission to publish reference data.
| 1 |
Select Publish.
|
| 2 |
Enter a summary of the reference data updates in the field.
|
If the reference data scope is changed and published in Viedoc Designer after the reference values have been published in Viedoc Clinic, the following message will appear on the Reference data page.
The reference date source-scope combination needs to be updated and published again in Viedoc Clinic, for the reference values to become available for auto-population to the subject forms.
If the reference values change for already populated data, the affected forms will be marked with a red issue icon [ i ].
Note! You can only edit data when your role has permission to edit reference data.
To edit a set of reference values:
| 1 | On the Viedoc landing page, select the Reference data icon. |
| 2 | Select Open reference data editor for the reference data source-reference data scope combination you would like to enter values into. |
| 3 | Edit the variables (see Variables), factors (see Factors), or the reference values. |
| 4 | Select Save to save the reference data. |
If the reference values change during a study for already populated data, ALL affected forms will be marked with a red issue icon [ i ], and a message is displayed on the top of the form as illustrated below:
Note! To avoid all forms being marked with a red issue icon, you can follow the alternative procedure as described in the next section.
The affected forms are also listed on the Selection page, under the ISSUES view, being marked as Pending Reference data upgrade. For more details, see Selection page.
To make changes to a reference data set during a study and without causing all affected forms to get issues, you can create a copy of the existing reference data set and make the changes there.
To create a duplicate of your reference data set::
| 1 | Open the reference data editor. |
| 2 |
Select Duplicate. 
The original set is displayed at the bottom of the list and the new set at the top. |
| 3 | Make your changes in the new set. |
| 4 |
Set the dates for when you want the two sets to apply. Note! The stop date of the previous set cannot overlap the start date of the new set. It is recommended to make the new set start on the day after the old set ends. |
| 5 | Save the changes. |
| 6 | Select Publish... and write a note to the site staff, explaining what has been changed. |
| 7 |
Select Publish. |
Viedoc supports forms containing repeating item groups when using reference data values. The values of items in repeating item groups are defined in the reference data editor, according to the reference data scope specified in the study design.
Data configured in the reference data editor is displayed in the referenced form once the appropriate scope is selected.
When you add a new repeating instance to a form, their values are automatically populated based on the currently published reference data scope:
For more information on repeating item groups, see Entering/Editing data.
When publishing a new reference data scope with updated values, the corresponding form is marked as Update Pending.
Note! When editing this lesson, check if the corresponding edits are also needed in the PMS User Guide for Clinic Side Users>Issues and Tasks in a PMS Study.
The Selection page displays all subjects from all sites you have access to. Each subject is represented by a subject card.
In the upper-right corner of each subject card, orange and red icons are displayed when there are issues (such as queries) and tasks to be solved/completed for that subject. These icons help you to identify where actions are needed.
All issues and tasks should eventually disappear but when present they help you identify where action is needed.
Note! The issue list will not be visible for sites that have more than 1000 subjects.
It is possible to switch between the views showing Cards/Issues/Viedoc Me/Events by selecting the dropdown list next to Selection.
The ISSUES view displays the list of existing issues.
Select any row to open the form where the issue has been raised. If you close the form, you will return to this issue list again.
The list of issues can be filtered by using the dropdown lists on the upper-right of the page. You can filter the issues:
As soon as data has been entered, the orange task icon appears, indicating that there is data ready for review, or queries answers to be approved (see Raising/Approving/Rejecting Queries). The number of tasks is displayed. If there are more than nine tasks to be performed on a booklet or form, +9 will be displayed in the icon. Tasks should be handled continuously throughout the study to make sure data at all times is as clean and accurate as possible.
Tasks are tracked on three levels:
As soon as a task is completed, it will disappear from the views.
Note! If Role based queries is enabled for your study, the task counter includes only the queries raised by the same role, that is, the ones that the active user role can take action on.
Note that much of the information in this lesson is the same as in the lesson Clinical review, SDV, and Lock.
The requirements on data review and source data verification vary between studies. This lesson describes what is possible in Viedoc.
If applicable for your study, data review is a task to be completed. The number of tasks to be completed is displayed in the orange task icon:
The orange task icon disappears when the checkboxes for clinical review and Source Data Verification (SDV) are selected and the task is completed.
Note! If a user with edit permission is editing the subject card, you can still perform the clinical review and the SDV. And vice versa, the clinical review and the SDV will not lock the subject for users who need to edit it.
The purpose of data review is to give the Data Manager the possibility to mark forms as reviewed.
Marking a form as data reviewed can be performed in one of the following ways:
Note! If a form is edited after you have marked it as data reviewed, the review status breaks and the form must be reviewed again. The review task appears again in the orange task box icon.
Locking data in a form can be performed in one of the following ways:
Locking a form should only be performed if there are no more expected changes to that form; that is, if the data is clean.
| Important! Updates to the electronic Case Report Form (eCRF) are not applied to locked forms. If you are aware of any upcoming changes to the eCRF that potentially affect already saved and locked forms, make sure that these are unlocked before the new design version is published to the site. |
If all forms in all events for a subject have been locked, the subject card on the Selection page will be displayed with a lock icon, indicating all data is locked:
Regular clinic forms can be unlocked by clearing the Lock checkbox at the bottom of a form. Unlocking a form opens it up for editing by users with edit data permission (for example the Investigator).
Subject-submitted (Viedoc Me) forms that are filled in by the subject are locked by default.
You may have the possibility to unlock a subject-submitted form if this option is activated for your study. In this case, the Lock checkbox appears at the bottom of the subject-submitted form. The form can be locked or unlocked by selecting or clearing the checkbox respectively. Unlocking a form opens it up for editing by users with edit data permission (for example the Investigator).
You can perform data review and lock of the forms batch-wise, by using the data review console. To open the data review console, click the icon in the top right corner of the Details page.
The data review console displays an overview of all forms of a subject that require data review, SDV or lock. It shows which forms have been reviewed, SDV'ed or locked. The green and grey eye icons help you identify which forms you have visited (the most recent version of the form): the green eye icon means that you have visited the last version of the form, the grey eye icon means that you have not visited the latest version of the form.
To review and/or lock the forms:
| 1 |
Select the form(s) to be reviewed in one of the following ways:
|
|
| 2 |
In the pop-up that opens, mark with Data review and/or Lock as needed, and click Ready:
|
If any of the marked forms have not been visited by you before, you will be asked whether you want to continue with the action or not. If you choose to continue, the forms will be marked according to your selections, that is, the system will not prevent you from marking unvisited forms as reviewed or locked.
Note! If the study has the setting for item-level SDV enabled, and a form contains items that require SDV but are not visible to you, you will not be able to change the SDV status for the entire form.
The current workload can be checked on the Study status or the Metrics pages.
A query is a question about data. In Viedoc, queries can be raised:
Note! All the related queries are automatically closed, when:
In case of a validation query, when this is resolved by data edit, it is automatically closed. See Validation queries.
Resolving a query always breaks the form signature, even if there are no data changes involved.
A summary of the number of queries is displayed on the study start page, as illustrated below.
Note! This is a summary of the whole study and it does not take into consideration the role visibility conditions.
A query is raised in a form field. After a query is raised, the respective form is marked with the red issue icon i:
| Important! For all new studies started after release 4.80, the default setting Enable role-based queries is selected. For studies started before release 4.80, the default setting Enable role-based queries is cleared. For studies started before Viedoc release 4.80, all query actions will still work as usual until role-based queries is enabled. |
When the role-based queries option is enabled for your study, it restricts, at study level, the approval of the query resolution to the same user role who raised the query.
Notes!
For more information, see the eLearning lesson on Role-based queries.
Viedoc Clinic users with permission to raise queries/pre-queries, can manually add a query to any field value.
Manually raised queries can be:
Viedoc offers support for query review, that is, to review a query before it is released to the site. This is done through pre-queries.
The pre-query process can involve either two or three roles, as follows:
An unlimited number of pre-queries can be added on the same field at the same time.
The following image illustrates the main actions that can be performed on a pre-query and all the states the pre-query goes through before it is released as a query:
1. The pre-query is added by the user with permission to add pre-queries, typically the Data Manager.
As a result, a pre-query is raised, becoming visible for the Viedoc Clinic user with permission to promote pre-queries, typically the Monitor.
2. The raised pre-query can be removed, for example if it is invalid or added by mistake.
3. The raised pre-query is promoted or rejected by the Viedoc Clinic user with permission to promote pre-queries, typically the Monitor.
4. The promoted pre-query is released by the Viedoc Clinic user with permission to add queries (typically the Monitor), becoming a raised query that is visible for the Viedoc Clinic user with permission to add/update query answers (typically the Investigator), who will be responsible for resolving the query, as described in Queries.
The table below summarizes the different states of a pre-query in Viedoc Clinic, in the export output (Excel/Operational Data Model (ODM), as well as the possible actions that can be performed on a pre-query and the state this will transition to.
| In Viedoc Clinic | In export output | through... | becomes... |
|---|---|---|---|
| Awaits promotion | PrequeryRaised | Promote pre-query (by Monitor) | PrequeryPromoted (Ready for release) |
| Reject pre-query (by Monitor) | PrequeryRejected (Rejected) | ||
| Ready for release | PrequeryPromoted | Release pre-query (by Monitor) | QueryRaised (Awaits answer) |
| Reject pre-query (by Monitor) | PrequeryRejected (Rejected) | ||
| Rejected | PrequeryRejected | N/A. No action can be performed on a rejected pre-query. | N/A. Final state |
| Removed | PrequeryRemoved | N/A. No action can be performed on a removed pre-query. | N/A. Final state |
The query process involves two different roles with different permissions in handling queries:
A query is raised in Viedoc either when a query is manually added or when a pre-query is released.
An unlimited number of queries can be added on the same item at the same time.
The following image illustrates the main actions that can be performed on a query and all the states it goes through:
1. A query is raised through one of the following:
2. A raised query can be removed, for example if it is invalid or added by mistake.
3.a. The user with permission to add/update subject/event/form data and query answers, typically the Investigator, resolves the query by one of the following:
3.b. When confirming data as missing, typically by the Investigator, this becomes a resolved query that awaits approval. This type of query can only be approved at step 4 below.
4. The user with permission to add/change queries can:
See also Query states.
The following image illustrates the main actions that can be performed on a validation query and all the states it goes through:
1. A query is raised as a result of a validation performed by the system.
2. The user with permission to add/update subject/event/form data and query answers, typically the Investigator, resolves the query by one of the following:
3. The user with permission to add/change queries can:
See also Query states.
The table below summarizes the different states of a query in Viedoc Clinic, in the export output (Excel/ODM, as well as the possible actions that can be performed on a query and the state this will transition to.
Note! All the related queries are automatically closed, when:
| In Viedoc Clinic | In export output | Through... | Becomes... |
|---|---|---|---|
| Awaits answer | QueryRaised | Remove query (by Monitor) | QueryRemoved (Removed) |
| Edit query (by Monitor) | QueryRaised (Awaits answer) | ||
| Resolve query (by Investigator) | QueryResolved (Awaits approval) | ||
| Awaits approval | QueryResolved | Approve query (by Monitor) | QueryApproved (Approved) |
| Reject query (by Monitor) | QueryRejected (Rejected) | ||
| Rejected | QueryRejected | N/A. No action can be performed on a rejected query. Note! When a query is rejected, this is regarded as a final state for the original query and a new query is raised again automatically by the system. |
N/A. Final state |
| Approved | QueryApproved | N/A. No action can be performed on an approved query. | N/A. Final state |
| Closed | QueryClosed | N/A. No action can be performed on a closed query. | N/A. Final state |
| Removed | QueryRemoved | N/A. No action can be performed on a removed query. | N/A. Final state |
In order to include the query information in the exported file, you need to select Queries under the Type of data in the Data export page. When selecting to include Queries, the Query history option becomes available.
The queries can be exported to the following export output formats:
For more details and instructions on how to perform an export, see Exporting data.
For details on how queries look in the ODM export see Queries in ODM export.
For details on how queries look in the Excel/CSV exported file see Queries in Excel export.
For an overview of the entire query process see Queries overview.
To be able to raise a pre-query you must have the permission to add pre-queries, typically the Data Manager (DM).
To add a pre-query:
| 1 | Open the form that contains the field the pre-query will be raised on. |
| 2 | Click the + icon in the top-right corner of the group that contains the respective field. The Add new action pop-up is displayed:
|
| 3 |
Click Ready. The pre-query is created and needs to be promoted and released by the user with permission to promote pre-queries (typically the Monitor), in order to be visible as a query for the site staff. A Removed state is a final state for a pre-query. |
A pre-query is always marked by this icon:
Once a pre-query has been promoted and released, it becomes a query and it is marked by this icon:
To be able to promote/reject a pre-query you must have the permission to promote pre-queries, typically the Monitor.
If there are any pre-queries that await promotion, these are marked as tasks. For details about tasks, see Issues and tasks.
To promote a pre-query:
| 1 |
Browse to the task and open the respective pre-query that is marked with state Awaits promotion. A pop-up is displayed where you can either Promote or Reject the pre-query: 
|
| 2 |
|
A pre-query can be released after it has been promoted, that is, a pre-query in Ready for release state.
A pre-query waiting to be released is marked as a task. For details about tasks, see Issues and tasks.
After releasing a pre-query, this will become a raised query visible to the site staff. This is why, releasing a pre-query can be performed by a user with permission to add queries.
To release a pre-query:
| 1 | Browse to the task and open the pre-query that is Ready for release. A pop-up is displayed where you can either Release or Reject the pre-query: |
| 2 |
Note! When role-based queries is enabled for your study, when a pre-query is released, (typically by the Monitor):
For more information on pre-queries, see Queries overview. |
For an overview of the entire query process see Queries overview.
A query can be added/edited/removed/approved by the user with permission to add/change queries.
Note! When the role-based queries option is enabled for your study, all of the above actions are restricted to the same role as the role who raised the query. For more information, see Role-based queries.
To raise a query:
| 1 | Open the form that contains the field the query will be raised on. |
| 2 | Click the + icon in the top-right corner of the group that contains the respective field. The Add new action pop-up is displayed.
|
| 3 |
Click Ready. The query was raised and it is now visible for the site and ready to be resolved, with state Awaits answer: 
|
After the query has been raised it can be:
The text of a raised query can be edited as long as the query was not resolved (Awaits answer).
To edit a query:
| 1 |
Open the query (from the respective form) and click Edit: 
Note! The avatar icon and the user role who raised the query is only visible if role-based queries is enabled for the study. For more information, see Role-based queries. |
| 2 |
Edit the text and click Save query: The query text is now updated. |
A query can be removed, for example if invalid or added by mistake, as long as the query was not resolved (Awaits answer).
To remove a query:
| 1 |
Open the query (from the respective form) and click Remove: 
Note! The avatar icon and the user role who raised the query is only visible if role-based queries is enabled for the study. For more information, see Role-based queries. |
| 2 |
Click Save query to confirm: 
The query state is Removed. This is a final state for a query. |
After the query was resolved by the site (typically the Investigator), it is marked as a task, it is in Awaits approval state and can be either approved or rejected.
Note! An exception is a query raised as a result of confirming data as missing by the site user. This type of query can only be approved.
To approve a query:
| 1 | Open the query. The query pop-up opens displaying the list of the query history: |
| 2 |
Select Approve and click Save query: The query is now Approved. This is a final state for a query: 
|
To reject a query:
| 1 |
Open the query. The query pop-up opens displaying the list of the query history: 
Note! The avatar icon and the user role who raised the query is only visible if role-based queries is enabled for the study. For more information, see Role-based queries. |
| 2 |
Select Reject, optionally rephrase the query and click Save query: 
The old query is closed with state Rejected and a new query is raised that Awaits answer: 
|
The Data Export page can be accessed by selecting the Data Export icon in the study start page:
The Data Export page enables you to preview and download study data:Layout option
You can filter the data that you want to preview/export, as described in the following sections.
If you have access to multiple sites, you can filter the data for a specific country or site.
To filter data for a specific country, select the name of the country. The selected country appears in blue letters besides the Data Export header, while the site(s) for the selected country are listed below:
For a specific country, you can choose to export the data for:
To undo the selection of the site, select All sites.
To undo the selection of a country, select the cross x icon beside the name of that country.
While filtering for country or site, the number of subjects depicted in between brackets in the Subjects to include field is updated accordingly.
You can choose to include all subjects in the data preview or export, or include a selection of subjects.
To select which subjects to include:
| 1 | Select Include single subject(s). |
| 2 |
Select the Repeat this step for each subject you want to include in the data preview/export. |
To undo the selection of certain subjects, select the - icon, or select the cross x icon next to the subject ID:
You can choose to include all the data or only for certain events. You can also filter the data added or edited during a certain time period.
Note! The available events are the ones existing in the latest design version applied on the first of the selected sites to be included in the export. If there are multiple design versions running for different of the selected sites, you have to select one site at a time in order to get the available events for the respective site.
You can choose to:
To select which events to include:
| 1 | Select Single event(s). |
| 2 |
Select the |
To undo the selection of certain events, select the - icon, or select the cross x icon next to the event:
To include data from a specific time period:
| 1 | Select the Time period checkbox: |
| 2 | Select one of the following options from the first drop-down list:
|
| 3 | Select whether to define the time period until a certain date, from a certain date, or between two dates. |
| 4 | Select the date(s). |
Tip! Filtering for data that were added or edited since a specific date is especially useful if you want to see all new and changed data since for example your last monitoring visit.
To undo the selection of a certain time period, select the cross x icon next to it:
You can choose which forms and items to be included in the export output:
Note! Only data belonging to forms and items that exist in the latest effective design applied to the first of the selected sites will be included in the export. Also note that the forms and fields available to choose from are determined by the visibility settings for your user role.
To include data from specific form(s):
| 1 | Select Include single forms and items. |
| 2 | Select the forms and items to be included, in one of the following ways:
|
To undo the selection of a certain form, select the cross x icon next to it:
You can filter the data to be included in the export by the review status, as follows:
You can select to include additional information, depending on the export output format, as described in the following sections.
For PMS studies, there is an option to include booklet status and booklet status history in the export.
When selecting to include Booklet status, the Booklet status history option becomes available.
Depending on if the booklet status is included in the export or not, the export contains the following information:
Booklets in submitted status are not included in exports triggered by users on the sponsor side. The booklets are included to those users when they are received.
Note! Clinic actions to submit/recall back and forth are not available on the sponsor side. Only the latest submit of the booklet that was received by the sponsor is included.
If the Booklet Status is selected and the following options: Require Responsible Investigator for booklet submission, and Require Contract for booklet submission, are enabled for the study, two columns are added to the export.
If Booklet history is selected at export, the historically selected Contract and Responsible Investigator are included in the respective booklet status. The most recent contract information shall be shown, regardless of the booklet status.
Note! If the contract linked to a booklet is edited, the contract information is updated in the existing row for that booklet in the export performed after the information was updated.
The booklet status can be exported to the following export output formats:
When selecting to include Booklet status in the Excel export, a separate Booklet status sheet is created that lists all the forms with the following information:
| Column name | Description |
|---|---|
| Site sequence number | A counter that identifies the site globally within the study |
| Site name | The site name, as set in Viedoc Admin |
| Site code | The site code, as set in Viedoc Admin |
| Subject sequence number | A counter that identifies the subject within the site |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Booklet sequence number | A counter that identifies the booklet within the sequence of booklets for the same subject |
| Booklet Id | The booklet ID, as set in the study design (in Viedoc Designer) |
| Booklet name | The booklet name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic |
| Booklet status | One of Not initiated, Initiated, Submitted, Received, Returned, or Frozen |
| Booklet activity | Initiated, Submitted, Recalled, Received, Frozen, Unfrozen, or Returned |
| Date & time (UTC) | The date and time of the status change |
| User name (ID) | The name (ID) of the user who changed the booklet status |
| Contract number | The number of the selected contract for the specific booklet. Note! This column is present in the export only if the option to link the booklet to a contract is enabled for the study. |
| Responsible Investigator | User name (internal userID ) of the user selected as Responsible Investigator for the specific booklet. Note! This column is present in the export only if the option to link the booklet to a contract is enabled for the study. |
When selecting to include Queries, the Query history option becomes available.
The Queries can be exported to the following export output formats:
See also:
The review status can be exported to the following export output formats:
See also:
The event dates can be exported to the following export output formats:
When selecting to include Event dates in the Excel export, a separate Event dates sheet is created that lists all the events with the following information:
| Column name | Description |
|---|---|
| Site sequence number | A counter that identifies the site globally within the study |
| Site name | The site name, as set in Viedoc Admin |
| Site code | The site code, as set in Viedoc Admin |
| Subject sequence number | A counter that identifies the subject within the site |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Event Id | The event ID, as set in the study design (in Viedoc Designer) |
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic |
| Event repeat key | For recurring events, the counter that identifies different occurrences of the same event (identified by the Event ID). Available for output versions Viedoc 4.39 and onward. |
| Event status | The current status of the event. It can be one of the following:
|
| Event date | The event date, as set in Viedoc Clinic when the event is initiated |
| Planned date | The event planned date, as set in Viedoc Clinic when the event is planned |
| Proposed date | The proposed date for the event, if set in the study design |
| Window start date | The event time window start date, if set in the study design. |
| Window end date | The event time window end date, if set in the study design |
| Initiated by | The name and ID of the user who initiated the event |
| Initiated date (UTC) | The date and time (UTC) when the event was initiated |
| Last edited by | The name and ID of the user who last edited the event |
| Last edited date (UTC) | The date and time (UTC) when the event was last edited |
| Design version | The design version/revision that is active for the event |
When selecting the Uploaded files option, the uploaded file together with the thumbnail (if it exists) are part of the Excel, CSV and PDF export output:
The folder structure obtained when you unzip the file is as follows:
|
- SponsorCode_YYYYMMDD_HHmmss (date and time in UTC format) - FileData - StudySite (SiteCode) - SubjectKey - StudyEventOID - EventRepeatKey - ActivityOID - ActivityRepeatKey - FormOID - FormRepeatKey (if any) - ItemGroupOID - ItemGroupRepeatKey (if any) - ItemDefOID - FileName.extension (original filename) - FileName_tn.extension (thumbnail filename) |
The export output (Excel, PDF, CSV, ODM) as well as the Data preview provides the following information about uploaded files:
The following information on the uploaded file is available in the full history:
The pending forms can be exported to the following export output formats:
Forms are considered pending when they are uninitiated in initiated events. This applies to all types of events, including subject-initiated events. For repeating forms, if the first instance of the form is uninitiated, the form is considered pending. Resetting a form results in that form being pending.
When selecting to include Pending forms in the Excel export, a separate Pending forms sheet is created that lists all the forms with the following information:
| Column name | Description |
|---|---|
| Site sequence number | A counter that identifies the site globally within the study |
| Site name | The site name, as set in Viedoc Admin |
| Site code | The site code, as set in Viedoc Admin |
| Subject sequence number | A counter that identifies the subject within the site |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Event sequence number | A counter that identifies the event within the sequence of events for the same subject |
| Event Id | The event ID, as set in the study design (in Viedoc Designer) |
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic |
| Event repeat key | For recurring events, the counter that identifies different occurrences of the same event (identified by the Event ID). Available for output versions Viedoc 4.39 and onward. |
| Activity Id | The activity ID, as set in the study design (in Viedoc Designer) |
| Activity name | The activity name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic |
| Form Id | The form ID, as set in the study design (in Viedoc Designer) |
| Form name | The form name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic |
| Event date | The event date, as set in Viedoc Clinic when the event is initiated |
| Pending since |
The date and time since when the form has been pending This is not always the date when the event was initiated. For a form that has been hidden due to a visibility condition, the pending since date is the date when the form is made available. |
The medical coding can be exported to the following export output formats:
The edit status can be exported to the following export output formats:
The subject status can be exported to the following export output formats:
The sheet Calculated subject status contains the following columns:
Select the export output format of the data under Output format > Output to:
You can export the data to one of the following formats:
1. Microsoft Excel - Office Open XML
2. CSV
3. PDF - PDF/A
4. ODM
Viedoc uses Microsoft Excel Open XML format which is compatible with Excel version 2007 and later.
For details about the Excel export options and the format/structure of the output file, see Excel export.
The output of the CSV export is similar to the Excel export output. The CSV export output consists of a zip archive containing one CSV file that corresponds to each sheet from the Excel export. For details about the Excel export options and the format/structure of the output file, see Excel export.
For the CSV export and the one row per activity selected layout, there is also the option to Include corresponding SAS script. For details, see Exporting for SAS.
For the CSV export, for study designs which include repeating item groups, when the one row per activity and group data by form options are selected, there is also the option to export Repeating item groups as a separate form. This option is selected by default. For details, see Excel export.
Notes! The export to CSV fails if the same OID was used in Viedoc Designer in different design versions with different casing (for example, an OID defined as AE in design version 1 and AE in design version 2).
Labels are truncated to 200 characters when CSV data is imported to SAS using the CSV2SAS macro.
The Excel/CSV export does not include items set to “Hide Always" in visibility conditions when a singleform is selected for export.
For details about the PDF export and the format/structure of the output file, see PDF export output.
The Clinical Data Interchange Standards Consortium (CDISC) Operational Data Model (ODM) is a vendor neutral, platform independent format for interchange and archive of clinical trials data. The format includes the clinical data along with its associated metadata, administrative data, reference data and audit information. All of the information that needs to be shared among different software systems during the setup, operation, analysis, submission or for long-term retention as part of an archive is included in the model.
This is used for exporting the data to an ODM file, with or without Viedoc extensions. To include the Viedoc extensions in the exported file, select the Include extensions checkbox. Viedoc extensions are Viedoc-specific settings that cannot be described as part of the CDISC standards. If the exported file is to be imported to Viedoc at a future time, the checkbox should be selected.
Select SAS compliant XML to automatically populate the SAS field name and the SAS dataset name.
The ODM export file is built up as follows:
The reference data editor opens and displays the variables and the target types to be populated, as defined in the reference data scope. If you would like to exclude some of the variables, select the arrow to the right of the variable name and select Not available. See also 
Study tag contains the information on the study settings, study design, workflow.AdminData contains data about the user and site settings.ClinicalData tag contains the data that was filled in in Viedoc Clinic.Association tag contains information about the performed actions such as SDV, raising and approving queries, medical coding, lock, CRA and DM reviews.The ODM export also supports repeating item groups in both the standard CDISC ODM and SAS-compliant formats. Repeating item group data is exported with ItemGroupRepeatKey attributes, which identifies each instance of a repeating item group.
This ensures ODM exports are compliant with the CDISC ODM standard for repeating item groups.
See also:
It is possible to select the Viedoc version that the exported file should be compatible with. This option enables you to export files that have the same format as files exported from previous Viedoc versions.
Note! This functionality is optional and set in the study settings in Viedoc Admin. It might not be activated for your study.
If activated for your study, you can select the Viedoc version that you wish the exported file to be compatible with under Output format and export, from the Output version drop-down menu. If you wish to create an export file according to the latest Viedoc version, select Latest Viedoc version:
The Viedoc version used for data export is listed in the Latest exports area on the right side of the export page.
The exported file contains information about which Viedoc version was used to create it. You can find information about the Viedoc version in the following places:
The Viedoc versions available in the Output version dropdown menu are only those versions in which changes to the data structure were introduced.
As of Viedoc release 4.79, the following output versions are available:
| Output version | Changes in data structure |
|---|---|
| Latest Viedoc version | When choosing Latest Viedoc version, the exported data will automatically follow the structure of the latest Viedoc release in which changes to the data structure were introduced. |
| Viedoc 4.79 | Introduction of a number of changes to the ODM data export. See the table below for details. |
| Viedoc 4.77 | For studies where item-level SDV is enabled, when exporting review status, the SDV sheet in the CSV and Excel data exports will include only the items that require SDV and are visible to the user. On the Review status sheet, items that do not require SDV are indicated with N/A. |
| Viedoc 4.68 |
Introduction of pdf archive export system check which splits the archive into one pdf file per subject and stores resultant PDF in a zip file. |
| Viedoc 4.67 | Introduction of two new columns for approving medical coding: "approved by" and "approved on date". |
| Viedoc 4.51 | Introduction of three new form repeat keys and the table of contents in the PDF export, see the table below for details |
| Viedoc 4.39 | Introduction of repeating forms and recurring events, see the table below for details. |
| Viedoc 4.38 | Original output format (Viedoc versions 4.38 or older). |
In Viedoc 4.79, the following changes to the export output were introduced:
| File type | Changes in the export output format |
|---|---|
| ODM |
Introduction of support for partial datetime, date, and time. This is now the default type when exporting designs and data in ODM format. Partial dates as per the ISO 6801 standard are written up to the most detailed value available. This makes the export compliant with CDISC ODM. |
| ODM |
When exporting a design to ODM, multi-selection code lists are handled as follows: Checkbox item definitions are split by code list items.
For example, when splitting a checkbox ItemDef with OID="CHK" and code list IDs "Yes" and "No", the split checkbox ItemDefs will have the OIDs "__CHK__Yes" and "__CHK__No", respectively. That is, the original OIDs and the code list IDs are prefixed with two underscore characters and separated by two underscore characters. In Viedoc Designer, checkbox items are exported as multiple ItemDefs - one for each selection value. In Viedoc Clinic and the Viedoc API: In the latest export version, checkboxes are exported as separate items for metadata and clinical data. In previous export versions, checkboxes are exported as one item. This has been introduced to be compliant with CDISC ODM. |
| ODM |
Bug fix: In the ODM data export, the content of the Question element for study event items and booklet forms was not complete. According to the CDISC standard, the element should include one of the TranslatedText attributes. This is now solved, and the Question element is populated with a string related to the corresponding OID. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the MeasuremetUnit.Name contained HTML code, making it non-compliant with the CDISC standard. This is now solved, and the HTML code is removed from the name. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the translated text was missing for meta.Protocol.Description.TranslatedText. This is now solved, and the body is populated with the protocol name, as visible on the design overview page. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the Length attribute was incorrect, making it non-compliant with the CDISC standard. This is now solved, and Length is populated as per the ItemDef data type. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, there was a mismatch between the item data type and the code list data type for checkboxes. This is now solved, and the checkbox data is split into different items, in the same way as for CSV and Excel exports. This is implemented in a new export version, version 4.79. |
| ODM |
Bug fix: In the ODM data export, the study OID and ClinicalData didn't respect the Production/Demo mode for sites. This is now solved, and the study OID and ClinicalData are populated based on the Production/Demo mode of the exported study. This is applied without a new export version. |
| ODM |
Bug fix: In the ODM data export, non-repeating forms included a repeat key, making the ODM data export non-compliant with the CDISC standard. This is now solved. This is implemented in a new export version, version 4.79. |
| ODM |
Bug fix: In the ODM data export, the KeySet elements had an unregistered value for the ItemOID attribute, making the ODM data export non-compliant with the CDISC standard. This is now solved, and the KeySet elements reference items within the same MetaDataVersion. This is implemented in a new export version, version 4.79. |
| ODM |
Bug fix: In the ODM data export, the attribute OrderNumber of the element StudyEventRef was not valid with respect to its type, integer. This is now solved, and StudyEventRef elements have unique and non-empty consecutive order numbers. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, there was a data type mismatch between CodeList and ItemDef, making the ODM data export non-compliant with the CDISC standard. This is now solved by always having a matching data type between ItemDef and CodeList. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the element MeasurementUnitRef had an unregistered value for the MeasurementUnitOID attribute, making the ODM data export non-compliant with the CDISC standard. This is now solved, and measurement units not referenced in any MetaDataVersion are not included in the ODM data export. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the Alias names were not correctly populated. This is now solved, and any code list item aliases with empty names are removed at import and export - and the Alias names are populated with the context values. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the SAS field name and the SAS dataset name were not populated. This is now solved, and the SAS field name is populated based on the ItemDef OID, and the SAS dataset name is populated based on the FormDefOID, which means that the OIDs are SAS-compliant. There is an option for this in the data export. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, revisions linked to study events and revisions linked to forms requiring approval of the new design revision were not included. This is now solved. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, alerts had repeating order numbers. This is now solved, and the order numbers for all study settings alerts in Viedoc Designer are removed. This is applied to all export versions. |
| ODM |
Bug fix: In the ODM data export, the item group containing the reference data items was not added to the MetaDataVersion. This is now solved. This is applied to all export versions. |
In Viedoc 4.51, the following changes to the export output were introduced:
| File type | Changes in the export output format |
|---|---|
| Excel | Addition of three columns for the new form sequence numbers introduced:
|
| ODM | Three new form sequence numbers were introduced, as Viedoc extensions: v4:SubjectFormSeqNo, v4:OriginSubjectFormSeqNo and v4:SourceSubjectFormSeqNo, within the FormData, right after the FormRepeatKey. |
| A table of contents was added to the PDF archive, starting on page 2 of the file. |
In Viedoc 4.39, the following changes to the export output were introduced:
| File type | Changes in the export output format |
| Excel | Addition of a column for Form sequence number (FormSeq) that contains the FormRepeatKey. |
| ODM | The FormRepeatKey now contains the activity ID as well, in the following format: FormRepeatKey$ActivityId. The ExportVersion attribute has been added to the ODM. |
| The summary formats are used to display the event and form names. |
When exporting data from Viedoc, the system determines the available events, forms, and data points based on the study design version applied to the first selected site. Understanding how this works is important when a study includes sites with different study designs or multiple design versions.
What happens when study designs differ?
If a study contains multiple study designs or different versions across sites, the exported data is structured based on the design of the first selected site. This means:
What does "first selected site" mean?
The first selected site is the first site in the study that is chosen for export. The exact determination depends on:
Example: If a study has sites in Germany, Sweden, United States, and Japan, and Germany is the first selected site, the export will be based on the latest design version applied to the first site in Germany.
Selecting multiple sites with different study designs
If multiple sites are selected and they have different design versions, users must:
Best practices to ensure accurate exports:
Note! User visibility settings affect data exports. If an item is missing, check that your user role has the necessary permissions, and that the item exists in the latest design version applied to the first selected site.
Example scenario: How study design affects data export
Scenario: A study has Site A using Design Version 1.0, and Site B using Design Version 2.0. When exporting data:
The Preview data button is only available when you have selected Excel or CSV as output format for the export.
The preview is not available when you have selected 1 row per item.
On the data tab, you can preview the data in table format:
1. If you have selected Group data by form, you can select the form for which you want to display data.
2. Use the Filter text box to filter the preview data by any text in any field. The preview is filtered on all words in this field.
3. Toggle between spacious view and compact view.
4. Select a column header to sort the data in ascending order. Select again to sort in descending order. Selecting a third time removes the column sort order. To rearrange the order of the columns in the table, simply select a column header and drag the column sideways.
5. Select to open the column menu. For more information, see Column menu.
6. Select to access the column filter. For more information, see Column filter.
7. Select any hyperlink data point in the table to view the underlying form in read-only mode.
8. Select Cross-check to display a second data table. This lets you cross-check data between the two tables. Form selection and the filtering and sorting of data in the second table are independent of the settings in the first table.
The column menu contains:
|
 |
|
 |
|
 |
For more information, see the following sub-sections.
Pin Left/Right makes a column remain visible in the leftmost or rightmost position when you scroll sideways. Select No Pin to unpin the column.
Autosize adjusts the column width to the width of the text in the column.
Reset Columns resets the pinning, sizing, and order of columns to the initial state.
Use the column filters to narrow down the selection of preview data.
1. Depending on the type of item in the column, you can specify one of these types of filters:
Form items that are radio buttons, drop-down menus, checkboxes, dates, or date/time items are treated as text.
Note! The text filters are case-insensitive.
2. Once you have specified a filter, you can specify another one for the same column, either as an AND filter or an OR filter.
3. Predefined filter options based on the data available in the column.
Select the columns to be displayed in the preview table.
Use the Search field to search for columns.
By default, system data is excluded from the table. To include system data, select the column(s) to include from the System data category. Note that some system data columns are only available when you have selected 1 row per activity. For more information, see Excel export.
When you right-click in a cell in the data table, this context menu is displayed:
Copy: Copies the cell value to your clipboard.
Copy with Headers: Copies the cell value and its column header to your clipboard.
Excel Export: Exports the preview data on the data tab. The resulting Excel file will have the same sorting and filtering of data and order of columns as the preview.
Select the data set you wish to plot in a chart, and select Draw:
If you have selected Group data by form, you can only choose data sets from the form you have selected on the data table tab.
Select any data point to view its details.
Note! The pie chart has access to the same data as the data tab. That means that if you applied filters on the data tab, only the filtered data will be available in the pie chart.
Select which data you would like to plot on the X-axis and Y-axis, which series should be created, and select Draw:
If you have selected Group data by form, you can only choose data sets from the form you have selected on the data table tab.
Select any column to view details of the data.
Note! The column chart has access to the same data as the data tab. That means that if you applied filters on the data tab, only the filtered data will be available in the column chart.
Select which data you would like to plot on the X-axis and Y-axis, which series should be created, and select Draw:
If you have selected Group data by form, you can only choose data sets from the form you have selected on the data table tab.
Note! The line chart has access to the same data as the data tab. That means that if you applied filters on the data tab, only the filtered data will be available in the line chart.
When you have made settings for an export, you can save them as a template. Then you, and optionally others, can use the template to easily make new exports with the same settings.
To save your settings as a template:
| 1 |
Select Save settings as a new export template. 
|
| 2 |
In the pop-up that is displayed, enter a name for the template and select whether it should be private or shared. If you select Shared, you are prompted to also select the roles that will be able to use the template. The roles available in the drop-down list are the ones with export permissions for the latest effective design of the study in question. 
|
| 3 |
Select Save. Now the Export templates list is displayed, with your newly created template at the top of the list: 
|
To apply a data export template:
| 1 |
Select View all templates in the Export templates area of the Data export page. 
|
| 2 |
Select the apply icon for the template that you want to apply. 
|
| 3 | Select Export data to perform an export with the settings in the template. |
Tip! Alternatively, you can use the quick access apply, available in the Export templates area:
To edit a data export template:
| 1 |
Select View all templates in the Export templates area of the Data export page.
|
| 2 |
The Export templates list is displayed. Select the edit icon for the template that you want to edit. 
|
| 3 |
In the pop-up that is displayed, you can edit the name of the export template and the settings for Private/Shared. Note! You can only edit a template that you created yourself. |
To delete a data export template:
| 1 |
Select View all templates in the Export templates area of the Data export page.
|
| 2 |
The Export templates list is displayed. Select the trash can icon for the template that you want to delete. 
|
| 3 |
In the pop-up that is displayed, select Delete. 
Note: You can only delete a data export template that you created yourself. |
To perform a data export:
| 1 | Filter the data to be exported. See Filtering the data to be exported. |
| 2 | Select the Output format. |
| 3 | Optionally, select the Output version. |
| 4 | Optionally, preview the data to be exported. |
| 5 |
Select Export data. The status of the export is displayed in the Latest exports area, on the top of the list. When the export is completed, you can download the exported file: The exported file is downloaded locally. The filename is generated as follows: SponsorCode_CountryCode_SiteCode_Date_Time, where:
Note! If any of the characters that are invalid for a filename in Windows are used within any of the SponsorCode or SiteCode, these characters will be automatically replaced with - within the exported filename. |
You can see a log of the requested exports in the Latest exports area, where you can download the exported files or delete the logs.
Note! The list of the latest exports is user-specific, that is, you can only see the exports made by yourself.
The latest five exports are shown in the list. To get the complete list of the initiated exports, select the View all exports link at the bottom of the list.
Each log entry provides the following information:
1. The date and time when the export was initiated.
2. The export status:
3. Viedoc output version - see Output versions.
4. The number of exported subjects.
5. The format of the output file.
6. The selected layout, if applicable.
7. File size
Note! If data has been masked after an export was made, it is not possible to download that export because it could include the data that was later masked.
The following are some frequently asked questions and answers about exporting data in Viedoc:
Q: How do I export the audit trail (history)?
A: Any PDF data export will include the audit trail (history) by default. You can also get an Excel or CSV version by changing the layout to one row per item and including the history. See the Include history section in the Excel Export lesson for more information.
Q: Is there a size limit to exports?
A: No, there are no size limits to exports.
Q: Can I schedule exports automatically?
A: Yes, you can configure customized automatic exports using Viedoc's web API. Please see the Exporting data via Viedoc's web API for more information.
Q: How is missing data handled?
A: Viedoc's approach to missing data is to leave it blank. The system does not use "N/A" or "missing." Both unconfirmed and confirmed missing data are included when exporting queries and query history.
Q: Why does the export seem stuck at a certain percent?
A. Sometimes exports (especially PDF exports of large studies) can take a take a longer time to complete and appear "stuck". If you log out, the export will continue in the background. Please do not make multiple requests for the same export. If the export fails with an error message, please contact Viedoc for assistance.
Viedoc uses Microsoft Excel Open Extensible Markup Language (XML) format which is compatible with Excel version 2007 and later.
When selecting Microsoft Excel as Output format in the Data export page, you have different options for grouping data and for the layout, as described in the following sections.
For general information about data export in Viedoc, see Exporting data.
Note! Since the maximum number of rows supported for Excel is 1048576, in case data in a sheet exceeds this number, data will be split into multiple sheets.
The Excel export contains the following sheets:
Note! If the Output IDs (OID) and Output labels have been defined in the study design, these are shown in the Excel/CSV/SAS export. If the Output IDs (OID) and Output labels are left undefined (blank) in the study design, then the configured Item ID and label is used. For more information about the item settings in the study design, see Outputs and Validation.
The table below lists which sheets are included in the Excel file, depending on the selected Grouping and Layout:
| Group data by form | Do not group data | |
|---|---|---|
| one row per subject |
|
|
| one row per activity |
|
|
| one row per item |
|
|
The headers are always represented by the first two rows in a sheet, as illustrated in the following image:
1. Human-readable format
2. Machine-readable format
An item that was changed within a new/revised study design version will have a "__n" suffix added, where n is incremented for each study design version where the respective item was changed:
Under Type of data, you can filter the data to be exported. If you filter data for Signed data, Not signed data, SDV performed or NA, or SDV pending, certain cells in the data sheets in the exported Excel file may appear empty. The data rows that contain empty cells due to the filtering are marked by an “X” in the last column of the data sheets that is named Empty cells on row may be due to export filter.
For example, let's say that we have an Add Patient event, and the Date of Birth is one of the data entered during this event. For a particular subject, this data was entered, signed by the Investigator, and afterwards modified, but not signed after the change. We perform an export that includes only the signed data, as illustrated in the image below:
The value of the Date of birth field that was recently changed and not signed is not included in the export (the cell appears empty). The data row containing the empty cell is marked by a "X" the Empty cells on row may be due to export filter, as shown below:
You can select whether the data should be grouped by form or not, from the Data grouping dropdown list.
Note! The data grouping is available only for the Excel/Comma-Separated Values (CSV) output.
When grouping the data by form, a separate sheet is created for each form. The sheet name is the Form ID, as set in the study design (in Viedoc Designer).
In each form sheet, the first columns (to the left) are the same for all the forms and provide information about the site, subject, event, activity and design version:
| Column | Description |
|---|---|
| Site Sequence number | Counter that identifies the site globally within the study. |
| Site name | The site name, as set in Viedoc Admin. |
| Site code | The site code, as set in Viedoc Admin. |
| Subject sequence number | Counter that identifies the subject within the site. |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Event sequence number | Counter that identifies the event within the sequence of events for the same subject. |
| Event Id | The event ID, as set in the study design (in Viedoc Designer). |
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Event date | The event date, as set in Viedoc Clinic when the event is initiated. |
| Activity Id | The activity ID, as set in the study design (in Viedoc Designer). |
| Activity name | The activity name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form sequence number |
Counter that identifies the instance of the respective form within the respective activity. This is mostly used for repeating forms. For non-repeating forms, this is "1". If a form is reset and then saved again the new form has sequence number "2", and so on. Form sequence number increases one step every time reset/initiate occurs. |
| Subject form sequence number | Counter that uniquely identifies the instance of a specific form on a subject level, that is, it starts with 1 and it is incremented each time a new instance of the form is created for that subject. |
| Origin Subject form sequence number | For a copied form instance, it identifies the form instance from which data was copied for the first time. For the first instance of the form (that is, not copied) it gets the value of the SubjectFormSeqNo. |
| Source Subject form sequence number | For a copied form instance, a counter that identifies the source of a copied form instance (the form instance the data was copied from). It gets the value of the SubjectFormSeqNo from which the form instance was copied. For the first instance of the form (not copied) it is empty (null). |
| Design version | The design version used at the time of data edit for the respective form. |
| Item Group sequence number | For study designs with repeating item groups: Counter that uniquely identifies the instance of a specific form item group on a subject level, that is, it starts with 1 and it is incremented each time a new instance of the form item group is created for that subject. |
The example in the image below shows an export with the default settings for the Layout, that is, 1 row per activity.
The following columns are specific to each form, one column for each item in the respective form. Each column has the <Item name>, as set in the study design (in Viedoc Designer) as column header.
For study designs which include repeating item groups, when the group data by form and one row per activity layout options are selected, there is also the option to export repeating item groups as a separate form/file for the Excel/CSV export. This layout option is selected by default:
CSV export for repeating item groups uses the same format as the Excel export, so that each repeating item group is generated as a separate CSV file.When multiple CSV files are generated, they are bundled into a ZIP archive.
For the CSV export, the repeating item group structure is supported in the option to Include corresponding SAS script. For more information about exporting data from Viedoc that is formatted for SAS, see Exporting for SAS.
If you choose not to group the data, then all data from all forms will be exported in the same sheet (Data) of the output file.
The example in the image below shows an export with the default settings for the Layout, that is, 1 row per activity.
In the Data sheet, the first columns (to the left, marked in green) are the common for all the forms and provide information about the site, subject, event and activity.
The following columns (to the right, marked in orange) contain form-specific information for all the forms within the event. For each of the forms, the following columns are added:
In the Layout section, you can select whether the data should be organized in the output file as:
The output in this case will look as shown in the below image. The example shows an export performed with all the default settings except for the Layout which is set to 1 row per subject.
There is one sheet for each form, as the default setting is to Group data by form.
There is one row per subject, that is, one row for each SubjectID (that uniquely identifies the subject).
The first columns provide information on the site and subject:
| Column | Description |
|---|---|
| Site name | The site name, as set in Viedoc Admin. |
| Site code | The site code, as set in Viedoc Admin. |
| Subject sequence number | Counter that identifies the subject within the site. |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
The following columns are the item-specific values, one set as described below for each item in the exported data. The order of the items is by event, as set in the study workflow.
Note! The columns Event sequence number, Event Id, Activity Id, Form sequence number, Subject form sequence number, Origin Subject form sequence number, and Source Subject form sequence number are not included when you have selected 1 row per subject.
The output in this case will look as shown in the below image. The example shows an export performed with all the default settings except for the Layout which is set to 1 row per activity.
There is one sheet for each form, as the default setting is to Group data by form.
The data is grouped so that, for each subject (1), there is one row for each activity (2).
All checkbox responses for an activity are exported within a single row, with each code list option occupying distinct columns. The items that have a code list assigned are output to an additional row with the ID suffixed with "CD", for the code.
For each code list option, two columns are included: one for the label and one for the code value. Column headers use the item's OID and Export Label, each suffixed with a 1-based index (for example, CHECKBOXOID_LABEL1, CHECKBOXOID_LABEL1CD). Only the selected code list values are populated in the corresponding columns. Unselected options are left empty.
The output in this case will look as shown in the below image. The example shows an export performed with all the default settings except for the Layout which is set to 1 row per item.
There is one sheet for each form, as the default setting is to Group data by form.
The data is grouped so that there is one row for each item (3) within an activity (2) for a subject (1).
The data is sorted by: site, subject, event date, event repeat key, form repeat key, form ID, item group ID, item ID.
If the Include history option is selected (see following section), the data is ordered from the oldest to the current item data (that is, by the Edit sequence number).
When selecting 1 row per item, the option to Include history becomes available. If selected, the edit history information (audit trail) will be included in the exported output (that is, the information shown in Viedoc Clinic on form level when selecting Show history).
The following information (columns) is added for each entry in the output file:
The items belonging to a reset or deleted form/event/subject are included as well in the export, together with a full history that gives the reason for resetting or deleting the form/event/subject.
Checkbox items are output as one row per code list item. The items that have a code list assigned are output to an additional row with the ID suffixed with "CD", for the code.
All code list items are included in the output, regardless of whether they were selected or not.
The Item Id column contains the item's Object Identifier (OID) with a 1-based index appended, as illustrated in the following image:
The Item Export Label column similarly includes the Export Label with the same 1-based index.
Two columns are generated per code list item: one for the code label and one for the code value. If a code list value is selected, its corresponding value appears in these columns. Otherwise, they may remain empty.
If the option to Include history is selected, then the code list items are ordered by the time of data entry (that is, by the Edit sequence number).
When reference ranges are used for a laboratory form, the laboratory name and the laboratory code are included and the following two columns are added:
SCOPE_XXX and SCOPE_XXXCD (where XXX is the numeric value)
Form link items can be organized in the Output format as:
Selecting 1 row per activity generates the output as shown in the image below. The exported file contains two columns per linked form instance, the Data column and the Identifier column, (the header is labelled Identifier).
In the example below:
There are also two header rows in the output:
| Header rows, one row per activity | |
|---|---|
| Row 1: Data column | Item Label, Counter of the selected link starting at one |
| Row 1: Identifier column | Item Label, Counter of the selected link starting at one, Identifier |
| Row 2: Data column | Item ID, Counter of the selected link starting at one |
| Row 2: Identifier column | Item ID, Counter of the selected link starting at one, ID |
Selecting 1 row per item generates the output as shown in the image below. The exported file contains two additional columns with the headers Item value and Item code, and one row per linked form instance.
Note! In the export preview the form identifier column is excluded by default. The order the form link item was added (time of data entry) is followed in the export.
Selecting 1 row per subject generates the output as shown in the image below. The exported file adds two columns per linked form instance to the exported file, the Data column and the Identifier column:
There are also two header rows in the output:
| Header rows, one row per subject | |
|---|---|
| Row 1: Data column | Event Label (event counter), Activity label (activity counter), Item label (counter of the selected link.) |
| Row 1: Identifier column | Event Label (event counter), Activity label (activity counter), Item label (counter of the selected link), Identifier |
| Row 2: Data column | Event ID (event counter), Activity ID (activity counter), Item ID (counter of the selected link.) |
| Row 2: Identifier column | Event ID (event counter), Activity ID (activity counter), Item ID, (counter of the selected link), ID |
Recurring events are identified in the export output by the StudyEventRepeatKey.
The image illustrates the form Vital Signs in the Excel export output. The form is used in three events (Visit 1, Visit 2 and Visit 3), of which Visit 3 is a recurring event. The four instances of Visit 3 are identified by the StudyEventRepeatKey that is listed in the Event sequence number (EventSeq) column:
Note! Support for recurring events has been added in Viedoc release 4.39. That means that if you would like to export recurring events, you should select Viedoc version 4.39 or later in the Output version dropdown menu under Output format.
Repeating forms are identified in the export output by the FormRepeatKey.
The image illustrates the repeating form Lab in the export to Excel. The instances of the form are identified by the FormRepeatKey that is listed in the Form sequence number (FormSeq) column:
Note! Support for repeating forms has been added in Viedoc release 4.39. That means that if you would like to export repeating forms, you should select Viedoc version 4.39 or later in the Output version dropdown menu under Output format.
Repeating item groups are identified in the export output by the ItemGroupSeq . The instances of the repeating item group are identified by the ItemGroupSeq number that is listed in the Item group sequence number column:
The following form sequence numbers are used to make it easier to track different form instances at subject level, which are useful especially for the form instances initiated by copying the data from previous event.
FormRepeatKey: Counter that identifies the specific instance of a repeating form within a specific activity. This is available in the export output for Viedoc output version 4.39 and onwards.SubjectFormSeqNo: Counter that uniquely identifies the instance of a specific form on a subject level, that is, it starts with 1 and it is incremented each time a new instance of the form is created for that subject. This is available in the export output for Viedoc output version 4.51 and onwards.OriginSubjectFormSeqNo: For a copied form instance, it identifies the form instance from which data was copied for the first time. For the first instance of the form (that is, not copied) it gets the value of the SubjectFormSeqNo. This is available in the export output for Viedoc output version 4.51 and onwards.SourceSubjectFormSeqNo: For a copied form instance, a counter that identifies the source of a copied form instance (the form instance the data was copied from). It gets the value of the SubjectFormSeqNo from which the form instance was copied. For the first instance of the form (that is, not copied) it is empty, that is, null. This is available in the export output for Viedoc output version 4.51 and onwards.The example below illustrates how the values for these sequence numbers are assigned. The demo form used is set as repeatable and copyable and is included in Visit 1, Visit 2 and Visit 3.
We perform the following actions in Viedoc Clinic:
| 1 | Initiate Visit 1 and fill in three instances of the Demo form, these instances will get the sequence numbers as illustrated below: |
| 2 | Initiate Visit 2. Demo form will be available to be initiated by copying data from one of the previously filled-in form instances within Visit 1, so all the three instances will be shown as ghost forms: |
| 3 | Create an instance of Demo form within Visit 2 by copying the data from the third instance of the form filled in within Visit 1. This will result in the new form instance getting the sequence numbers as illustrated below: |
| 4 | Initiate Visit 3. Demo form will be available to be initiated by copying data from one of the previously filled-in form instances within Visit 1 and Visit 2, as below: |
| 5 | Create an instance of Demo form within Visit 3 by copying the data from the form filled in within Visit 2. This will result in the new form instance getting the sequence numbers as illustrated below: |
These sequence numbers are available to be used within expressions only to get the value of the sequence number for a specific form instance, that is, by using {SubjectFormSeqNo}, {OriginFormSeqNo}, {SourceFormSeqNo}.
In the above example, the form Summary format was configured by using these sequence numbers as below:
Form Repeat Key {FormRepeatKey}, SubjectFormSeqNo {SubjectFormSeqNo}, OriginFormSeqNo {OriginFormSeqNo}, SourceFormSeqNo {SourceFormSeqNo}
Notes!
In the excel export output, these form sequence numbers allows to track, for the form instances that were initiated by copying data from previous events, where the data originates from, as below:
Analyzing the values of the form sequence numbers, only the form instances that were initiated by copying the data from previous visits have values populated in the Source Subject form sequence number column, that is, the last two rows in the example. The data was copied from the form instance having the same Subject form sequence number value, highlighted in green in the above image. The form instance that the data was copied for the first time is identified by the value of the Origin Subject form sequence number, that is, "3" in our example.
When choosing PDF as output format, you have the following options:
Notes!
One .zip file is downloaded for each PDF export performed.
This section describes the structure of the exported PDF file.
The file is structured as follows:
1. A study summary on the first page.
2. A site summary page.
3. One separate sub-section for each subject in the respective site.
4. For each subject, one sub-section for each event.
5. For each event, one sub-section for each activity.
6. For each activity, one sub-section for each form. The latest version of the form PDFs are included here. See also Audit trail and Form History section in Entering/editing data.
The meaning of the signature in Viedoc is included on the last page.
Note! If the number of forms for a site exceeds 1000, the system splits the archive into one PDF file per subject and stores them in a zip file.
The first page provides a short summary, as illustrated in the image and explained below:
1. The study logo image, if any, as set in Viedoc Admin, under Study Settings.
2. Study name, as set in Viedoc Admin, under Study Settings.
3. Study description, as set in Viedoc Designer.
4. The dates for:
5. The number of sites:
6. The number of subjects:
The site summary page provides a summary of the site, as illustrated in the image and explained below:
1. The study name, as set in Viedoc Admin.
2. The site name, as set in Viedoc Admin.
3. The site code, as set in Viedoc Admin.
4. The country for the respective site, as set in Viedoc Admin.
5. The site time zone, as set in Viedoc Admin.
6. Date of First Patient Added (FPA) to the site, in the site timezone.
7. Date of Last Patient Added (LPA) to the site, in the site timezone.
8. Number of subjects from the site included in the export / total number of subjects in the site (this number will exclude deleted subjects if Exclude deleted subjects/events/forms is checked).
Following the site summary page, comes a Contents list of the subjects included in the export for the respective site, with the Subject ID and corresponding pages. After that, comes one sub-section for each subject, described in the next topic.
The subject summary page provides the following information:
1. The study name and site name, as set in Viedoc Admin.
2. Subject ID in the format set in Viedoc Designer.
3. The date and time the subject was added.
4. The number of Forms filled in / the total number of forms for that subject.
5. A table of Contents with a list of all the events that contain data for the respective subject, the event status and the page numbers where the data related to the respective event can be found.
The event summary page provides the following information:
1. The study name and site name, as set in Viedoc Admin.
2. Subject ID in the format set in Viedoc Designer and the event name together with the date when it was initiated.
3. A table of Contents with a list of all the forms within the respective event for Scheduled and Unscheduled events, providing the following information:
For Common Events, each entry will have its own Event summary page.
For each form, the form PDF is included, in the same format as for the form history pdf file. For details, see Form history PDF in Entering/editing data.
The forms in the PDF are sorted by these characteristics:
The following example illustrates the sort order.
Suppose the study design looks like this:
For the event E01, all forms belong to the same activity. This means that the order of the forms in the PDF will always be like this:
For the event E02, there are three activities. This means that if any form from A02 gets saved first, then any form from A01 gets saved second, and then any form from A03 gets saved third, the order of the forms will be:
In other words, the order of forms for event E02 for this specific example will be like this:
To include the query information in the exported file, you need to select Queries under Type of data in the Data Export page.
The Queries can be exported to the following export output formats:
This lesson describes how and where to find the query related information in the ODM export.
AssociationIn the ODM export output file, the queries are stored under the Association tag.
As the query history is always included in the ODM export, there is an Association entry for each query state (for example if there is one query that has been through 3 different states namely raised, resolved and approved, there will be 3 different Association entries).
Note! All association elements are sorted by the AuditRecord datetime stamp.
Each Association links an item (identified by the KeySet, see the description below) to a set of properties related to a specific query wrapped under the Annotation tag (see detailed description below).
The image illustrates an example of an ODM export output, with the information within the Study tag at the top of the image and a query information under the Association tag at the bottom of the image:
For each Association entry, the following information is provided:
StudyOID and the MetaDataVersionOID indicate where the respective information is defined.KeySet is generally used to identify the start and end of the annotated "link". For queries, both key sets are identical, as they identify the same item, namely the item the respective query corresponds to. It contains the following:
StudyOIDSubjectKeyStudyEventOIDStudyEventRepeatKeyFormOIDFormRepeatKeyItemGroupOID - applicable only for queries on item level.ItemOID - applicable only for queries on item level.AnnotationThe Annotation tag wraps the specific information of the respective query, as described below. Since there is only one Annotation within an Association, the SeqNum is always "1".
CommentThe Comment value depends on the query state and is set as follows:
If the query state is QueryRaised or PrequeryRaised, the query text is specified here.
If the query state is QueryRejected or QueryResolved, the resolution text is specified here, as in our example "I am confirming the data".
No comment element is present for other cases than the ones mentioned above.
"CL_ANNOTATION_TYPE"CodeListOID="CL_ANNOTATION_TYPE" indicates the annotation type, for example "ManualQuery":
All the possible annotation types can be found under the Study tag, under the respective StudyOID and MetaDataVersionOID, respectively:
"ManualQuery""ValidationQuery""UpgradePending""MissingData""SDV""CRAReview""DMReview""MedicalCoding""Lock"Of all the above, only the following refer to queries:
"ManualQuery""ValidationQuery""UpgradePending""MissingData""MissingData" annotation type is used both for unconfirmed missing data and missing data, there is no distinction between those in the ODM export."CL_QRY_STATE"CodeListOID="CL_QRY_STATE" indicates the query state, for example "QueryRaised.
All the possible query states can be found under the Study tag, under the respective StudyOID and MetaDataVersionOID, respectively:
"PrequeryRaised""PrequeryPromoted""PrequeryRejected""QueryRaised""QueryResolved""QueryRejected""QueryApproved""QueryClosed""QueryRemoved""PrequeryRemoved"For more details about the query and pre-query states, see Queries overview.
"CL_QRY_ITEM_SEQ_NO"CodeListOID="CL_QRY_ITEM_SEQ_NO" indicates the sequence number of the respective query for the linked item. This is used to identify the query, meaning that all the Annotation entries corresponding to different states of the same query, will have the same value of CodeListOID="CL_QRY_ITEM_SEQ_NO" and same KeySet.
v4:AuditRecordv4:AuditRecord contains the audit record for the respective annotation.
Since the same query can go through many query states, there can be many Annotations with the same value of CodeListOID="CL_QRY_ITEM_SEQ_NO"and same KeySet. In order to get the latest entry for the same query, you can sort as follows:
CodeListOID="CL_QRY_STATE", as listed above.The Queries can be exported to the following export output formats:
To include the query information in the exported file, you need to select Queries under Type of data in the Data export page. When selecting to include Queries, the Query history option becomes available.
Depending on if the Query history is included in the export or not, the information in the export output file is grouped as follows:
In the Excel export output, considering as an example the default settings under Output format:
...the query information is grouped in a separate sheet of the excel file, called Queries.
The columns provide information on the item that the query was raised on, followed by the query specific information, as illustrated in the image (the image shows the query-specific information only) and listed in the following table:
| Column name | Description |
|---|---|
| Query study sequence number |
Counter that identifies the query globally within the whole study. This field is empty for the Unconfirmed missing data. |
| Columns that identify the item | |
| Site sequence number | Counter that identifies the site globally within the study. |
| Site name | The site name, as set in Viedoc Admin. |
| Site code | The site code, as set in Viedoc Admin. |
| Subject sequence number | Counter that identifies the subject within the site. |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Event sequence number | Counter that identifies the event within the sequence of events for the same subject. |
| Event Id | The event ID, as set in the study design (in Viedoc Designer). |
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Event date | The event date, as set in Viedoc Clinic when the event is initiated. |
| Activity Id | The activity ID, as set in the study design (in Viedoc Designer). |
| Activity name | The activity name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form Id | The form ID, as set in the study design (in Viedoc Designer). |
| Form name | The form name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form sequence number | Counter that identifies the instance of the respective form within the respective activity. This is used for the repeating forms. For non-repeating forms, this is always "1". |
| Item Id | The item ID, as set in the study design (in Viedoc Designer). |
| Item Name | The item name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Query specific information | |
| Query item sequence number | Counter that identifies the query within a sequence of queries for the same item. |
| Raised on |
Specifies if the query was raised on an item or on the event date:
|
| Query type |
Specifies the query type, depending on how it was raised:
|
| Range check OID | Only for automatically raised item queries (i.e. Query type = Validation and Raised on = Item). The unique Object Identifier (OID) of the edit check that generated the query, as set in Viedoc Designer. |
| Query text | The text of the query. |
| Query state |
Can be one of the following (see also Query overview):
Note! The queries that were automatically closed due to form reset/delete (with status Query Closed) are not included in the export. |
| Query resolution | The resolution text entered when resolving (answering) the query. Not applicable for those changes performed by the system (i.e. User name = System (0)) |
| User name | The name of the user who performed the changes, followed by the user ID in parentheses. Note! For those changes performed by the system (such as validation queries, that are automatically raised by the system) the User name = System (0). |
| Date & time (UTC) | The date and time when the change was performed. |
| User role |
The role of the user who performed the action on the query |
| Query raised by role | The role of the user who raised the query |
This lesson describes how the medical coding information is structured within an Operational Data Model (ODM) file exported from Viedoc.
For general details about data export, see Exporting data.
There is one CL_DICT_TYPE codelist that contains one entry for each dictionary type present in the exported data:
There is one codelist for each dictionary instance present in the exported data, which contains one <ExternalCodeList> element pointing to a specific dictionary version, that specifies:
DictionaryVersionref
There is one codelist with dictionary properties for each dictionary present in the exported data. Each such codelist contains items for each property the dictionary defines:
There is one codelist for each dictionary coding scope present in the exported data, specifying:
AssociationFor each medical coding item, there is one <Association> entry.
Each Association links an item (identified by the KeySet, see the description below) to a set of properties related to a specific Annotation (see detailed description below).
KeySetThe KeySet is generally used to identify the start and end of the annotated "link". In this case, both key sets are the same, as they identify the same entity, namely the one the respective action (defined under the Annotation) corresponds to.
The KeySet specifies the following attributes:
StudyOIDSubjectKeyStudyEventOIDStudyEventRepeatKeyFormOID - not applicable for event scopeFormRepeatKey - not applicable for event scopeItemGroupOID - applicable for item group and item scopeItemOID - applicable only for item scopeAnnotationThe Annotation consists of a set of <Flag> elements, and an audit record if the export was set to include the Viedoc extensions.
Flags
1. One flag element for the annotation type, with a <FlagValue> that is always MedicalCoding in this case.
2. One flag element for the dictionary type, with a <FlagValue> set to one of the CL_DICT_TYPE items.
3. One flag for the medical coding scope, with a <FlagValue> set to one of the CL_CODING_SCOPE items.
4. One flag element for the code sequence number, with a set to one of the CL_CODE_SEQ_NO items.
5. One flag element for each dictionary property set, with a <FlagValue> set to the dictionary property codelist (for example CL_MEDDRA_PROP) and a <FlagValue> set to the property value.
AuditRecordThe <v4:AuditRecord> is a Viedoc extension and is included in the output file only if the option to Include extensions was selected at export time.
It contains information on the user ID and the date/time stamp.
In the example image below the user ID = 304:
This lesson describes how the medical coding information is structured within an Excel file exported from Viedoc.
To include the medical coding information in the exported file, you need to select Medical coding under Type of data in the Data Export page:
For general details about data export, see Exporting data.
For medical coding, in the Excel export output file, there is one sheet for each dictionary. Only values that have been coded will be present in the export:
The columns provide information on the item that was coded, followed by the medical coding specific information, as listed in the following table:
| Column name | Description | ||
|---|---|---|---|
| Columns that identify the item | |||
| Site sequence number | A counter that identifies the site globally within the study | ||
| Site name | The site name, as set in Viedoc Admin | ||
| Site code | The site code, as set in Viedoc Admin | ||
| Subject sequence number | A counter that identifies the subject within the site | ||
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. | ||
| Event sequence number | A counter that identifies the event within the sequence of events for the same subject | ||
| Event Id | The event ID, as set in the study design (in Viedoc Designer) | ||
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic | ||
| Event date | The event date, as set in Viedoc Clinic when the event is initiated | ||
| Activity Id | The activity ID, as set in the study design (in Viedoc Designer) | ||
| Activity name | The activity name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic | ||
| Form Id | The form ID, as set in the study design (in Viedoc Designer) | ||
| Form name | The form name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic | ||
| Form sequence number |
Counter that identifies the instance of the respective form within the respective activity. This is mostly used for repeating forms. For non-repeating forms, this is 1. If a form is reset and then saved again the new form has sequence number 2, and so on. Form sequence number increases one step every time reset/initiate occurs. |
||
| Subject form sequence number | Counter that uniquely identifies the instance of a specific form on a subject level, that is, it starts with 1 and it is incremented each time a new instance of the form is created for that subject. | ||
| Origin Subject form sequence number | For a copied form instance, it identifies the form instance from which data was copied for the first time. For the first instance of the form (that is, not copied) it gets the value of the SubjectFormSeqNo. |
||
| Source Subject form sequence number |
For a copied form instance, a counter that identifies the source of a copied form instance (the form instance the data was copied from). It gets the value of the |
||
| Item Id | The item ID, as set in the study design (in Viedoc Designer) | ||
| Item Name | The item name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic | ||
| Medical coding-specific information | |||
| Term | The coded term | ||
| Dictionary instance | The description of the dictionary instance, as set in Viedoc Admin when uploading the dictionary | ||
| Version | The dictionary version. | ||
| Coding scope description | The coding scope description, as defined in Viedoc Designer | ||
| Coding scope level | The coding scope level, as defined in Viedoc Designer, can be one of the following:
|
||
| Code sequence number | A counter that identifies the code for those values with more than one code | ||
| Dictionary-specific information | |||
|
WHODrug: Note! To align with WHODrug terminology changes planned for 2026, labels in exports containing medical coding have been updated. These updates are available from Viedoc version 4.91.
|
MedDRA:
|
ATC without DDD:
|
IDF:
|
| Interpretation | The medical coder's interpretation of the applied coding value | ||
| Coding operation | Shows the coding operation for each item, for example whether it was coded manually or automatically. | ||
| Coded by user | The name of the user who performed the coding, followed by the user ID in parentheses | ||
| Coded on date (UTC) | The date and time (UTC) when the coding was performed | ||
| Approved by user | The name and ID of the user who approved the items | ||
| Approved on date (UTC) | The date and time (UTC) when the item was approved | ||
This section illustrates an example of how the data coded using the World Health Organization Drug Dictionary (WHO DD) dictionary looks in the Excel export output.
There are two different use cases, depending on the which level of granularity is selected when applying the code in Viedoc Clinic:
1. Drug (default)
2. Subst
The image below illustrates how the coded data looks in the export output, if the Drug is selected when applying the code in Viedoc Clinic.
When Drug is selected, the Substance code and Substance name are shown in the export as well, in the last columns, as illustrated in the image.
The image below illustrates how the coded data looks in the export output, if substance (Subst) is selected when applying the code in Viedoc Clinic.
After Subst is selected and the code is applied, for the respective coded item, the value of the substance is shown in in both Subst and Drug fields, Viedoc Clinic, as well as in the exported output.
This lesson describes how the review status information is structured within an Operational Data Model (ODM) file exported from Viedoc.
For general details about data export, see Exporting data.
To include the review status in the export, you need to select the Review status under Type of data in the Data Export page:
Note! When selecting one row per item as Layout, the review status is not included in the export.
Note! Source Data Verification (SDV) status is only exported on study event and item level. SDV on form level is excluded from the export.
The following annotation types are relevant for the review status and are listed in the CL_ANNOTATION_TYPE codelist:
There is a CL_REVIEW_STATE codelist that indicates the review state, which is always Checked for the annotation types mentioned above. If the respective review was not performed in Viedoc, there is simply no entry for it in the ODM file.
AssociationFor each review action, there is one <Association> element.
Each Association links an item (identified by the KeySet, see the description below) to a set of properties related to a specific Annotation (see detailed description below).
KeySetThe KeySet is generally used to identify the start and end of the annotated "link". In this case, both key sets are the same, as they identify the same entity, namely the one the respective action (defined under the Annotation) corresponds to.
StudyOIDSubjectKeyStudyEventOIDStudyEventRepeatKeyFormOIDFormRepeatKeyItemGroupOIDItemOIDAnnotationThe Annotation consists of a set of <Flag> elements, and an audit record if the export was set to include the Viedoc extensions.
Flags
1. One flag element for the review type, with a <FlagValue> set to one of the CL_ANNOTATION_TYPE items.
2. One flag element for the review state, with a <FlagValue> set to one of the CL_REVIEW_STATE items.
AuditRecordThe <v4:AuditRecord> is a Viedoc extension and is included in the output file only if the option to Include extensions was selected at export time.
It contains information on the user ID and the date/time stamp.
In the example image below, the user ID = 294:
Notes!
User OID="USR.0". This is applicable, for example, for the Lock action.User OID="SYSTEM". This is applicable, for example, when the form is locked due to randomization.This lesson describes how the review status information is structured within an Excel file exported from Viedoc.
For general details about data export, see Exporting data.
Note! When selecting one row per item as Layout, the review status is not included in the export.
In the Excel export output file, there is one separate sheet for the Review status:
The first columns provide information for identifying the form that was reviewed, followed by the review information, as listed in the following table:
| Column name | Description |
|---|---|
| Columns that identify the form | |
| Site sequence number | Counter that identifies the site globally within the study. |
| Site name | The site name, as set in Viedoc Admin. |
| Site code | The site code, as set in Viedoc Admin. |
| Subject sequence number | Counter that identifies the subject within the site. |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Event sequence number | Counter that identifies the event within the sequence of events for the same subject. |
| Event Id | The event ID, as set in the study design (in Viedoc Designer). |
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Event date | The event date, as set in Viedoc Clinic when the event is initiated. |
| Activity Id | The activity ID, as set in the study design (in Viedoc Designer). |
| Activity name | The activity name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form Id | The form ID, as set in the study design (in Viedoc Designer). |
| Form name | The form name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form sequence number |
Counter that identifies the instance of the respective form within the respective activity. This is mostly used for repeating forms. For non-repeating forms, this is 1. If a form is reset and then saved again the new form has sequence number 2, and so on. Form sequence number increases one step every time reset/initiate occurs. |
| Review status information | |
| Reviewed item |
Can be one of the following:
|
| Clinical review by | User name and user ID of the user that performed the clinical review. |
| Clinical review date (UTC) | The date and time in Coordinated Universal Time (UTC) when the clinical review was performed |
| Data review by | User name and user ID of the user that performed the data review (marked by the DM review flag). |
| Data review date (UTC) | The date and time (UTC) when the data review was performed. |
| SDV by | User name and user ID of the user that performed the Source Data Verification (SDV) (marked by the SDV review flag). For studies where SDV is performed on item level, this column will contain N/A for items that do not require SDV. |
| SDV date (UTC) | The date and time (UTC) when the SDV was performed. For studies where SDV is performed on item level, this column will contain N/A for items that do not require SDV. |
| Signed by | User name and user ID of the user that signed the form. |
| Signed date (UTC) | The date and time (UTC) when the form was signed by investigator. |
| Lock by | User name and user ID of the user that locked the form. |
| Lock date (UTC) | The date and time (UTC) when the form was locked. |
If, on the Data Export page, it was selected to include the SDV information, there is one separate sheet for the SDV information in the Excel export output file:
Note! For studies where SDV is performed on item level, this sheet will include only the items that require SDV and are visible to the user.
The first columns provide information for identifying the item that was SDV-ed, followed by the review information, as listed in the following table:
| Column name | Description |
|---|---|
| Columns that identify the item | |
| Site sequence number | Counter that identifies the site globally within the study. |
| Site name | The site name, as set in Viedoc Admin. |
| Site code | The site code, as set in Viedoc Admin. |
| Subject sequence number | Counter that identifies the subject within the site. |
| Subject Id | The Subject ID, in the format configured in Viedoc Designer. The Subject ID is the subject identifier displayed in Viedoc Clinic on the subject card, subject details page, and so on. |
| Event sequence number | Counter that identifies the event within the sequence of events for the same subject. |
| Event Id | The event ID, as set in the study design (in Viedoc Designer). |
| Event name | The event name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Event date | The event date, as set in Viedoc Clinic when the event is initiated. |
| Activity Id | The activity ID, as set in the study design (in Viedoc Designer). |
| Activity name | The activity name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form Id | The form ID, as set in the study design (in Viedoc Designer). |
| Form name | The form name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| Form sequence number |
Counter that identifies the instance of the respective form within the respective activity. This is mostly used for repeating forms. For non-repeating forms, this is 1. If a form is reset and then saved again the new form has sequence number 2, and so on. Form sequence number increases one step every time reset/initiate occurs. |
| Item ID | The item ID, as set in the study design (in Viedoc Designer) |
| Item name | The item name, as set in the study design (in Viedoc Designer) and displayed in Viedoc Clinic. |
| SDV information | |
| Reviewed item |
Can be one of the following:
|
| SDV by | User name and user ID of the user that performed the SDV. |
| SDV date (UTC) | The date and time (UTC) when the SDV was performed. |
In Viedoc, it is possible to export data in .csv format and analyzed in Statistical Analysis System (SAS).
| Important! Only SAS in Unicode mode is supported. |
Note!
To export data from Viedoc that is formatted for SAS, you have to create the following selections on the Data Export page, under Output format:
Notes!
The export output is a zip file, containing:
Note! If the Output IDs (OID) and Output labels have been defined in the study design, these are shown in the Excel/CSV/SAS export. If the Output IDs (OID) and Output labels are left undefined (blank) in the study design, then the configured Item ID and label is used. For more information about the item settings in the study design, see Outputs and Validation.
To import to SAS the data exported from Viedoc:
| 1 | Export the data from Viedoc including the SAS script (the settings are described above). |
| 2 | Open SAS. |
| 3 |
Run the _RunMe.sas file (see description above). The data types from the Items file and the CodeLists formats will be converted to the SAS formats. |
This video shows how to log in/log out to/from Viedoc and how to reset your password.
If you have difficulties in viewing the video, click here.
This video provides a quick overview of the landing page as well as of the study start page.
If you have difficulties in viewing this video, click here.
This video demonstrates how to switch between demo and production mode within a study.
If you have difficulties in viewing this video, click here.
This video demonstrates how to enter reference data in Viedoc Clinic.
If you have difficulties in viewing the video, click here.
Our Working Smarter webinar series is designed to help Viedoc users get the most out of the platform, from practical tips and feature deep dives to best practices and expert insights. Each session addresses topics for our users including highlighting new features, sharing useful tips, best practices, or deeper insights into specific areas of Viedoc.
Whether you're new to the system or an experienced user, these webinars are here to help you work smarter.
The full list of webinars in Viedoc’s Working Smarter Series, including recordings and Q&A, is provided below.
October 2024
https://help.viedoc.net/l/a29eab/en/
November 2024
https://help.viedoc.net/l/04c262/en/
January 2025
https://help.viedoc.net/l/893419/en/
February 2025
https://help.viedoc.net/l/bb2d9a/en/
March 2025
https://help.viedoc.net/l/027d45/en/
April 2025
https://help.viedoc.net/l/f94362/en/
June 2025
https://help.viedoc.net/l/227838/en/
September 2025
https://help.viedoc.net/l/b01136/en/
November 2025
https://help.viedoc.net/l/f914f3/en/