Waching daily Oct 25 2018

5 Star Akil - Personal Cinematic (Official Music Video) "2019 Soca" [HD]

For more infomation >> 5 Star Akil - Personal (Official Music Video) "2019 Soca" [HD] - Duration: 3:57.

-------------------------------------------

Oddly Satisfying Videos #703 - Duration: 10:01.

Oddly Satisfying Videos #703

For more infomation >> Oddly Satisfying Videos #703 - Duration: 10:01.

-------------------------------------------

REDCap Tutorial Video 11: Advanced Features - Duration: 12:35.

Let's look at some advanced features in REDCap.

First, let's look at the logging feature.

The logging feature is found under 'Applications' on the left-hand menu.

The logging feature records every action that happens in your REDCap project, who performed

the action, and when they performed it.

You can filter by event types to see when data has been exported, when design work has

happened to your project, when users were added or deleted, and detailed information

for specific records.

It will also include all the actual data that was entered into every field in REDCap.

The logging feature is a way to check any changes made inside of a record, and it's

an easy way to retrieve information that may have been deleted.

You can also filter by user, specific records, or a specific time range.

Next, let's go into more detail about field comments.

We talked a about field comments when we discussed REDCap data entry in tutorial number 5.

To leave a comment on a specific field, click on the quotation bubble next to it.

This allows the person who is doing data entry to make a comment on the data that they've

entered.

It records the user and the date/time, and when it's saved, the speech bubble turns yellow.

This is an easy way to indicate to anyone scrolling through the record that there is

more information about the field.

As a general rule, you don't have time to scroll through every response for every record.

However, REDCap allows the user to see all comments that have been made in the project

in the field comment log under 'Applications'.

Here you'll see a list of all project comments.

Users can also respond to comments by clicking on them, making this feature a great way for

data enterers and project managers to communicate over specific pieces of data that may require

additional clarification.

It's especially helpful if the data enterers and the project manager aren't working at

the same time or in the same location.

You can filter comments based on a record, field, user, or keyword.

Let's now look at the Data Import Tool.

This is found under 'Applications' on the left-hand menu.

The data import tool allows you to import large amounts of data into your REDCap project.

You can see that I have a notice at the top of the screen that my project is still in

development status.

It reminds me that I should not enter real data until the project is in production mode.

Once you're in production, there is more protection for your data.

If you want to import data into REDCap you'll have to do so using the CSV data import templates

found in step 1 of the instructions on the 'Data Import Tool' page.

Click on "Download your Data Import Template" with the records in rows (one record per line)

or the records in columns (one record per column) and you will get a blank template.

Here, I've selected records in rows, so each variable has its own column.

Enter one record per row.

If there's repeating instruments, you'll have to specify the instrument and instance in

the redcap_repeat_instrument and redcap_repeat_instance columns.

Each instrument and instance will an additional row.

One part of the template to pay extra attention to is the "database_heard_of" columns.

Back in REDCap, the field 'database_heard_of' is a checkbox field.

Checkbox fields work a little differently than multiple-choice questions.

In regular multiple-choice questions, each multiple-choice answer is assigned a code.

To manually enter data into Excel, enter the code (the number before the comma) to represent

that choice.

In checkbox fields, where one record may have more than one answer choice selected, Excel

codes the checkbox fields as series of yes/no questions for each checkbox answer.

Instead of phrasing it as "Do you know about databases one, two, and three," the template

asks, "Do you like database one: Academic Search Complete, 1, yes or 0, no?"

To manually enter data in Excel here, enter 1 for yes or 0 for no.

The same process applies to the next question: "Do you like database two, DynaMed?

Yes or no."

And so forth.

When importing data in REDCap, you have to use the variable names and codes, not the

text questions or answers.

For example, don't enter "What is your age?"

Instead, use the variable name 'age.

For "What made you attend PCOM?", use the variable name 'why_pcom.'

This requirement is one reason why it's easier to use the template for importing data,

since the variable names are already listed as rows or columns.

You also have to use the coded answers.

For 'program', I can't type in Osteopathic Medicine or Pharmacy and expect REDCap to

recognize it.

I have to give the code 1 or 2, or whichever number I assigned to that answer.

Additionally, fields that have been validated, such as numbers and dates, must contain the

type of data for which they're validated.

For example, I can't import text into a number field.

An easy way to see all the variable names, coding, and validation types in your project

is to use the codebook, found on the project home page under 'Quick Tasks'.

The codebook lists instruments and their official names, variable names and the field label

that goes with them, and the field types with any validation or coding that goes with it.

This is a great reference when you're trying to import data into REDCap.

Please note that if you already have some data entered in your fields, REDCap will give

you a chance to review how you're changing your data before you make the import permanent.

By default, blank values in your import file will not overwrite information that is in

REDCap.

So if I have a field in my REDCap file, for instance age, and I already have the person's

age in REDCap, I can import the variable age with my import file and just leave it blank,

and it won't overwrite the age that is already saved in REDCap.

On the file import page, you can make an exception to this rule by choosing to have blank values

overwrite existing values.

The default is to ignore blank values so that real data cannot be overwritten by accident.

However, if you are specifically trying to overwrite values you can do it if you need

to.

To import a file, include the record information that you want to import and save it as a CSV

file.

Then go into the 'Data Import Tool' under 'Applications', choose the file, and upload

it to REDCap.

After uploading the file, REDCap will display the data review, then ask you to confirm the

import.

Under 'Instructions for Data Review', the system shows me that I'm overwriting existing

data by showing a Data Display table with the current data in red and the new data in

black, as described in the key above the table.

If I'm not okay with these changes, I can edit the CSV file and re-upload it.

If you try to import data that has an error in it, such as a variable name with more than

26 characters or a value outside of a range you've set, the field will be highlighted

with a warning in orange.

If you try to import data with a critical error, for example you try to import text

into a number field, you'll get a list of all the fields that cannot be imported due

to an error and what the error is so that you can go back and correct it.

Once you've reviewed the changed and errors and are ready to upload, select 'Import

Data' at the bottom of the screen.

Finally, let's look at the 'Data Quality' tool, which is found under 'Applications'

on the left-hand menu.

The Data Quality tool is a great way to help ensure the integrity of your data.

It comes with preprogrammed different rules that you can use to check your data.

To look for these rules, click 'Execute' next to the rule you want or 'All' by

'Execute Rules' at the top.

The rules can, locate all fields that are missing values or specific required fields;

find validation errors, display outliers, or highlight multiple choice fields with invalid

values or hidden fields that shouldn't have values.

One of the most valuable uses of the data quality tool is rule H - looking for incorrect

values in calculated fields.

The calculations in calculated fields aren't sent to the server until you hit save.

If you were to update a calculation and it doesn't update the values for your entire

project or you import incorrect data into a calculated field, then you'll have errors

that you may not know about.

You can use rule H to check your project, and it will let you know if there are any

discrepancies.

If there are issues, click 'View' next to the number of errors and you'll be able

to correct the values in all calculated fields with a single click.

You can also add personal data quality rules.

For example, if all the participants in your project are supposed to be over 18, you might

want to look for people under the age of 18.

To add your rule, give it a name and describe what the rule should involve.

If you have trouble working out your rule logic, there's a link under the new field

text box titled "How do I use special functions?"

The field will notify you about the validity of your logic for the project with a pop-up

box for an error or a 'Valid' checkmark if it's correct.

You can also choose if you want this rule to work in real time, meaning that the data

entry form will display a pop-up if the rule is broken when the data enterer clicks Submit.

If you don't want it to work in real time, you'll only see an error if you run the

rule in the Data Quality rules later.

Click add, and then you can execute the rule.

In this case, the project has one record where the participant is below the age of 18.

This video completes our REDCap tutorial.

Next, you need to take a short quiz about using REDCap.

After passing this quiz, an email will be sent to the REDCap administrators and your

PCOM REDCap account will be created.

You will then get an email with your new REDCap account information.

For more infomation >> REDCap Tutorial Video 11: Advanced Features - Duration: 12:35.

-------------------------------------------

REDCap Tutorial Video 9: Longitudinal Projects - Duration: 7:38.

Let's look at how to use longitudinal projects in REDCap.

To enable a project as longitudinal, click 'Enable' under the Main project settings.

Once a project is enabled as longitudinal, you will need to define the events that will

make up the longitudinal project.

To add a new event to the project, click on the 'Define My Events' button and give

the event a name with an optional custom event label.

The custom event label is a great place to use piping to make similar looking events,

such as weekly check-ins, easier to distinguish.

Here, I am inserting piping in the variable visit_date.

This means that each event will be automatically labeled with the date of that visit.

Then click 'Add New Event' and drag and drop events in any order you choose.

In a longitudinal project, you can have multiple arms in your study.

The arms are completely unrelated to each other, so record 1 in arm 1 will not be the

same as record 1 in arm 2 and the arms can have different setups.

This feature allows you to have multiple groups in your experiment, such as control and experimental

groups.

When you add or edit records in a longitudinal project, you'll have to select both the arm

and the record to create or change a record.

Once you've created all your events, go to the 'Designate Instruments for My Events'

tab at the top of the screen.

In this section, you'll need to indicate what forms to use for which events.

For example, I only need to collect demographics information for the first event.

The diet habit survey is only administered at the initial visit and week 2.

However, I want to collect exercise and check-in information at all weekly check-ins.

I click Begin Editing, select the instruments I want for Week 3, then click Save.

This setup means that when a participant fills out the form or a researcher does data entry,

they'll have the option to fill out specific forms for specific events, but only for those

specific events.

If you go to the 'Record Status Dashboard' under 'Data Collection', you can see that

during the initial visit, 'Demographics' and 'Diet Habits' appear, but the exercise,

check-in, and follow-up are not options because they are not used for this first event.

A form must be added to at least one event before you'll be able to collect data in a

longitudinal project.

The scheduling module is an extra feature within a longitudinal project.

This feature can be found on the 'Project Setup' page, under 'Enable optional modules

and customizations'.

Once you've enabled the scheduling module, the 'Define my Events' page will change

a little bit.

There's now a days offset column, and you can provide an offset range.

The days offset column is how many days after the initial event the events should happen.

For example, the week 1 check-in should happen 7 days after the initial appointment and the

week 2 check-in should happen 14 days after.

You can also set an offset range.

For example, the -1/+1 next to week 1 means that week 1 check-in should happen 7 days

after the initial visit, plus or minus a day to allow for scheduling.

In the 'Scheduling' module under 'Data Collection' on the left-hand menu, choose

any unscheduled record and select the start date and study arm.

REDCap will generate a schedule for that record, which states the day every event should happen

along with the acceptable offset range.

Any dates that fall on weekends will be listed in red to make it easier find and change these

dates.

Click create schedule, and the calendar, under 'Applications' on the left-hand side,

will show all visits as scheduled.

When you click an event on the calendar, a popup menu will appear showing the record,

the event it is in, the status (due date, scheduled, confirmed, cancelled, or a no show),

and an option to add time and make additional notes.

You can also jump to the relevant forms for that record in that event to begin data entry.

Finally, you can use repeating instruments in a longitudinal project.

If you need a refresher on how to set up repeating instruments, please view video 6 again.

The difference between when you'd want to use a longitudinal project and when you'd

want to use repeating instruments is how regularly will people be filling out the instruments.

For example, if you have no idea how many visits someone is going to have, it might

make more sense to have visit forms created as repeating instruments.

However, if you know that every participant is coming in for exactly ten visits, it makes

more sense to set it up as a longitudinal project.

Within a longitudinal project you can use repeating instruments, and you have two ways

that you can set up projects.

The first way to set up the project is to use repeating individual instruments.

In this example, the 'Exercise' form asks the participants what form of exercise they

have engaged in that week.

Participants can add more than one form of exercise by choosing to complete another instance.

In that case, the instrument repeats on its own within the event.

The second way to set up the project is to repeat the entire event.

This setup means that all instruments in the event will be repeated when you add a new

instance; you will always have the same number of instances for every instrument in that

event.

Repeating instruments and repeating events in a longitudinal project, which already allows

for the repetition of forms, can be complicated.

If you ever have questions about the best way to set up your project, we're happy to

meet with you.

That covers the basics that you'll find in a longitudinal project Next, let's look

at how to create reports in REDCap, how to export data from REDCap, and go over what

statistics REDCap collects.

For more infomation >> REDCap Tutorial Video 9: Longitudinal Projects - Duration: 7:38.

-------------------------------------------

REDCap Tutorial Video 7: Surveys - Duration: 11:22.

Now that we know the basics of how to set up a REDCap project, let's look at how to

use surveys in REDCap.

First, enable surveys under main project settings on the project setup page.

Then, go into the online designer to choose which forms to enable as a survey.

Forms within a project may be a mix of regular and survey forms.

Enabling a form as a survey will take you into survey settings.

The first option within survey settings is whether the survey should be active or not.

Next, give the survey a title.

This title is what participants will see when they take the survey.

By default, the title of the survey is the same as the form, but if you want to use something

different, change it in this section.

You may also create instructions that will appear after the title at the top of the survey.

These instructions can include piping.

For more information about piping, click on the "How to use piping here" link under

the text box.

More information about finding basic HTML can be found in our REDCap guide at libguides.pcom.edu/redcap.

Under Survey Design Options, you can set up the look of the survey, including adding a

logo.

Standard radio buttons and checkboxes can be used, such as those shown in the data entry

tutorial, or enhanced radios and checkboxes can be incorporated to create a larger button

that is easier to select on a mobile or touchscreen device.

You can specify the size and font of your survey text and the survey theme.

There are a variety of preprogramed themes within REDCap, including a PCOM theme, or

you can customize your own theme.

Once you've created a custom survey theme, you can copy the custom survey design to other

surveys to any other project you might work on later.

More customization options are available under 'Survey Customizations'.

Question numbering is formatted as either auto-numbered or as custom numbered.

If you're using branching logic on the survey, you'll have to use custom numbers to denote

how you want to handle hidden fields.

Questions can display on one page or across multiple pages, divided by sections.

If a survey is divided into multiple pages, the yellow divider will appear to a survey

participant as a next and previous button.

We recommend dividing a survey into pages so that surveys are easier to complete and

because data is sent to the server and saved when the next or previous buttons are clicked.

This way, if a participant drops out before completing the survey, a partial response

is still recorded.

If surveys are on multiple pages, page numbers are displayed at the top of each page and

the 'previous' button can be removed to keep participants from changing completed

answers.

Required fields have the option to include a "must provide value" red text next to the

field.

If you include required fields, the survey participant will not be able to continue the

survey until those fields are complete.

If there are doubts about whether survey participants would be willing to supply an answer to a

question, do not make it required.

You can also choose whether you want survey respondents who have completed the survey

to be able to view the combined results of all respondents.

For example, they would then be able to see that 75% of participants choose choice A.

REDCap also has the option of text-to-speech functionality, which will read the question

and answer choices to the survey participant.

However, this option must be enabled by the survey creator.

You can also choose whether text-to-speech is on by default or whether participants must

click "Enable speech" at the top-right of the survey.

When enabled, participants can click the speaker icon next to any survey text to hear it read

out loud.

Under Survey Access, you can set a response limit, time limit, and expiration date if

desired.

You can also choose if participants have an option to save and return later.

Under Survey Termination Options, there are three different options on how to end a survey.

One option is to have text pop up to thank participants for taking the survey.

HTML and piping can be used in the text pop up to personalize the thank you.

If the project has multiple surveys, you have the option to auto-continue to the next survey

as soon as the participant clicks submit.

You can also redirect the participant to a specific URL upon survey completion.

This feature is useful to direct participants to a project homepage, a page that contains

further information about the project, or a page that collects information for incentives

when completing an anonymous survey.

In this last case, the best practice is to create two REDCap projects: One for the main

survey and one that collects contact information for where to send an incentive.

The first survey should automatically redirect to the incentive survey.

These two surveys cannot be linked, which keeps the original survey anonymous.

The final Survey Termination options are whether to automatically archive a PDF copy of each

response in the project's File Repository and whether to email a completion confirmation

to the participant.

When settings are complete, click the "Save Changes" button at the bottom of the page.

More customizations for surveys are located in the Online Designer.

The first customization is the survey queue, which is a to-do list of all surveys in a

project.

Select which surveys are included and when they'll be displayed to participants.

The survey queue ensures that included surveys are only displayed after specific logic is

met.

Here, I'm not activating the 'Demographics+' survey because I want all participants to

take it first.

However, depending on how participants answer my first survey, I might want to send them

a follow up survey entitled 'Barriers to Diabetes Adherence'.

This survey should only be send to participants who completed the preliminary demographics

survey 'Demographics+' and indicated that they were positively diagnosed with diabetes.

You can choose whether to have the secondary surveys start automatically and look as if

it's a continuation of the same survey, or choose to have the secondary survey appear

on the Survey Queue after the initial survey is completed.

The default setting is for the secondary survey to automatically start.

If you choose to use the survey queue, go to the survey settings and turn off 'auto-continue'.

Other survey options are Survey Login and Survey Notifications.

Survey Login requires users to log into surveys with information already saved in previous

surveys.

For example, once a user has completed a demographics survey, you can require them to enter their

date of birth and last name for any future surveys to confirm their identity.

Survey Notifications allows you or other survey administrators to receive an email every time

a participant completes a survey.

Another survey option is automated invitations.

With automated invitations, you can set conditions about who the follow up survey is sent to,

just as you could with the survey queue.

You can also choose when to send the survey after the conditions are met in the initial

survey: immediately, a specific date, or after a certain amount of time has passed.

This option is a great way to setup a pre- and post-study or if you have a form such

as a diary that participants need to fill out every day or every week.

You can enable reminders and choose whether you want the survey invitation to be active.

Finally, you can have repeating instruments within a survey, such as this 'Personal

Doctors' survey example.

In the survey settings, you have an additional option under survey termination options to

allow respondents to take the survey again.

You can customize the text of the button with the "Set custom text for the button" box.

You can also choose whether you want participants to choose to take the survey again before

or after it's submitted.

Let's see what this looks like for participants.

In Record Status Dashboard, I can go into any record for my 'Personal Doctors' survey

and have the option to open the survey as if I am a participant.

After a participant completes the form, they have the option to submit and take the survey

again.

This creates a blank version of the survey, ready for the participant to fill it out again.

That is the basics of how you set up surveys in REDCap.

In our next tutorial, we'll cover how to manage survey participants.

For more infomation >> REDCap Tutorial Video 7: Surveys - Duration: 11:22.

-------------------------------------------

REDCap Tutorial Video 8: Managing Survey Responses - Duration: 5:37.

Now that you know how to use surveys in REDCap, let's cover how to manage participants.

Start by going to the Manage Survey Participants link under Data Collection . This section

is where you'll do most of the setup for managing participants.

The public survey URL can be sent to everyone in your project.

Through this link, every participant's response will create a new record in the project.

For this reason, the public survey link will connect to the first form in the project,

which must be a survey.

You can also link to the survey with a survey access code, which gives a simplified URL

and an access code that the participant can use to access the survey.

Survey access codes are easier when gathering responses on a mobile device.

While REDCap does have an option to insert a QR code, we recommend that you do not use

a QR code as it requires participants to download a special app.

Open the public survey with the "Open public survey" link to see what the survey looks

like and to test it out.

On the left side of the screen next to the text, you can see that the text-to-speech

feature is enabled and that this survey is similar to a standard data entry form.

The big difference is that no one on this survey page can access the rest of the project.

For example, if you're collecting information from someone in a clinic setting and you want

them to fill in their own information, it makes more sense to give them a survey to

complete instead of a data entry form.

From the survey all they can answer is what they see; if you pull up the data entry form

they'll have the same access to the rest of that data entry project as you do.

The second main tab of the Manage Survey Participants section is the participant list, which creates

a unique link for each participant in the project.

Because each person has a unique link, REDCap will know that this person is the same person

across multiple surveys and matches them into one record.

It will show you if a specific participant has responded, partially responded, and if

an invitation has been sent to them.

It also allows you to open up each participant's specific link and survey access code.

If you have not enabled the participant identifier option, this is an anonymous way of collecting

information by allowing you to see who has responded but not match a specific response

to a specific record.

If you enable the participant identifier, you can go directly to the responses of those

who answer after the option is enabled.

To add someone to the participant list, click the "Add participants" button at the top

and type in their email address and, if you're using the identifier, their unique identifier

after a comma.

To send invitations to people on the participant list, click "Compose Survey Invitations"

next to the "Add participants" button and choose whether the email should be sent

immediately or at a specific time in the future.

You can also set up survey reminders so that if participants haven't responded by a certain

time they get an email.

First, choose how often to send it: every Monday/Tuesday, every other day, or at a specific

date and time.

Then, choose how many reminders to send.

Finally, create the email, which can include HTML and piping.

If you want to see what the email will look like, you can preview it on the Preview tab

and send a test email to yourself.

Select which participants you want to email by selecting categories of participants in

the Actions menu or individual names, then clicking Send Invitations at the bottom.

To see previously sent or future surveys, view the third tab, Survey Invitation Log.

This log shows all future and past invitations and provides a filter to display invitation

reminders, as well.

If you do not initially have participants' email addresses but want to send them multiple

surveys linked to the same record, you can collect their email addresses through a survey.

To enable this, go to the Project Setup page.

Under "Enable optional modules and customizations," select "designate an email field for sending

survey invitations".

Then, choose any field in the project that has been validated as an email address.

Whenever a participant fills out that email field, it will automatically be linked with

their record and can be used to send further survey invitations.

This tutorial covered the basics of managing participants.

The next tutorial will cover setting up and using longitudinal projects.

For more infomation >> REDCap Tutorial Video 8: Managing Survey Responses - Duration: 5:37.

-------------------------------------------

REDCap Tutorial Video 10: Reports and Exports - Duration: 8:12.

Now that you've seen how to build a REDCap project and get data into REDCap, let's look

at how to export data.

To get data out of REDCap, go to the 'Data Exports, Reports, and Stats' page on the

left-hand sidebar under 'Applications'.

First, let's build a report to review what a subset of data looks like.

To do this, go to the "Create New Report" tab at the top of the page and name the report.

Select who is able to access your report: all users in your project or only specific

users.

For example, you may want to set up your project so that only administrators can access the

report.

After setting up the report, decide what items to include in it.

There are four ways to add a variable to a report: 1) choose an entire instrument, 2)

use the quick add feature by checking the boxes of fields to include in the report,

3) select items from the dropdown menu, or 4) type in the name of the variable.

To place fields in a different order, drag and drop them until they're in the preferred

order.

Next, add filters.

For example, if I only want Pharmacy students to show up in my report, I can specify it

in this section.

Live filters allow you to use multiple-choice questions to look at subsets of this filtered

group.

I can use live filters to switch back and forth between Pharmacy students diagnosed

with diabetes versus those who have not been.

You can also choose by which fields to sort the report.

The default setting sorts everything by the record ID, but I can change the sorting setting,

add more options, and choose if results are in ascending or descending order.

Here, I'll sort by last name by ascending order.

Select "Save Report" at the bottom of the screen, then select "View report"

to see the data you've chosen on a new page.

The report includes only information for Pharmacy students, listed by last name in ascending

order.

I can use the live filter to look at only certain subsections of the data, such as the

Pharmacy students who have not been diagnosed with diabetes.

With either a report or the entire data set, REDCap provides some basic statistics and

charts I can use to visualize data through the "Stats & Charts" buttons on the 'My

Reports & Exports' page.

Under 'Display Options', I have the option to look at the data for the entire report

or for a specific record.

For text fields, the field section provides the sample size (n) and tells me if any data

is missing.

For number fields, it gives the minimum, maximum, standard deviation, sum, and percentile breakdowns,

as well as a graph that shows the distribution.

For multiple-choice questions, the field section shows the answer distribution among the choices

and the number of selected unique fields.

I have the option to view the data as a bar or pie chart and the option to download an

image of the chart.

I can export the report from the top of the 'Stats & Charts' page or export the entire

data set from the 'My Reports & Exports' page.

There are several options of formats to use when exporting data.

REDCap works well with all major stats packages so reports can be downloaded as SPSS, SAS,

R, or STATA.

Choosing one of these options will prompt downloads of a few different files formats.

Downloading the files and running them in the order given by REDCap will format the

data and import it into the appropriate stats package.

Files can also be downloaded as XML or CSV files, which can be opened in Microsoft Excel

or other spreadsheet programs.

There are two different CSV options: raw data and labels.

Raw data will give the variable name, such as "why_pcom" instead of "Why did you choose

to attend PCOM?," and uses coded values on items like multiple choice questions.

Labels give the full question: "What is your program?" and, for multiple-choice

questions, the label for the answer choice: "Osteopathic Medicine," "Psychology," etc.

As a general rule, we recommend that you download the raw data because raw data is used for

project analysis.

When cleaning data or reimporting it into REDCap, it must be in the form of the raw

data.

There are also several de-identification options.

For users without the ability to export the full data set, some of these options will

be prechecked and can't be changed.

Under "Known Identifiers", there are options to remove all fields tagged as an identifier

or to hash the record ID field, which changes the record name to an unrecognizable value.

We recommend that the record ID field not be an identifier.

However, if an identifier for the record ID field is used, you can hash it.

Under "Free-form text", you can choose to remove any unvalidated text fields, notes,

and essay boxes, leaving only quantitative information.

Under "Date and datetime fields", you can choose to remove date/time fields.

To calculate date differences within a record while unlinking a specific appointment to

a specific person, choose the option to shift the dates in your date/time fields by between

0 and 364 days.

The amount shifted will be determined randomly, but all the values will be shifted by the

same amount.

For example, a participant with appointments on June 6 and June 13 may be shifted to October

15 and October 22, preserving the period between appointments.

You can also shift survey completion timestamps in the same fashion.

When you've made your selections, click "Export Data" at the bottom of the window and export

the prepared file.

This tutorial covered the basics of exporting data using a classic REDCap project.

The next video will cover some advanced features of REDCap.

For more infomation >> REDCap Tutorial Video 10: Reports and Exports - Duration: 8:12.

-------------------------------------------

REDCap Tutorial Video 5: Data Entry - Duration: 7:30.

Let's start by adding new records into a pre-existing project.

To add a new record, go to Add/Edit Records under Data Collection.

Either choose an existing record or click to add a new record.

This will take you to the Record Home Page.

Note that you can see all the data collection instruments you have for the project and their

statuses.

Right now, all the statuses are grey because no data has been entered.

Click on the status icon to go to the first instrument.

Type to enter the information in a text field.

The next field to complete is a pre-validated date, set up in Day-Month-Year format.

Make sure to match all data in the specified format as you enter it.

An error pop-up will appear if the format is incorrect.

In this example, the field is asking for a subject's age.

If you enter a word instead of a number, a popup will appear.

If you enter an out of range number, such as 300, a popup will appear with a suggested

range for the age: in this case, between 18 and 80.

There are three types of multiple choice questions: a basic multiple-choice option with all answers

visible on the screen, a dropdown menu option, and a checkbox option.

Checkboxes allow you to pick more than one answer choice in a multiple choice question.

You can also create multiple-choice questions with branching logic, which is called conditional

branching.

Branching logic sends respondents down different paths in a survey depending on how they respond

to specific questions.

In this example about library databases, depending on how you answer the question, you will get

a different follow up question on how much you use the specific database chose.

Note that the follow up question contains a slider field to drag and drop.

Slider fields are great in test-retest situations.

Participants are less likely to remember where they dropped the slider than they are to remember

how they answered the multiple choice question.

In the descriptive field, choose to upload documents, pictures, audio file, or even link

to video.

You can have it display inline, as this picture of a mole demonstrates, or you can make it

a link to the uploaded item.

This yes/no example question also has branching logic attached to it.

If I answer no, nothing happens.

If I answer yes, then a new field appears prompting me to upload a photo of my own mole.

Next, we have the e-signature field.

This allows for whomever is filling out the form to add their own signature that will

be stored with the record.

You can mark the form as incomplete, unverified, or complete.

REDCap gives a few different save options: save and exit form, which will go back to

the record home page; save and stay on this form; or save and go to next form.

On the next form, we have an example of matrices.

Matrices are a group of multiple-choice questions that all use the same answer choices.

These are useful if you are using a Likert scale--something where you want all the answer

choices at the top.

Fill in two numbers fields, and now you can see the calculated field that is adding up

the answer for "How many hours a week do you spend on schoolwork?"

Although this displays on the screen, it won't be saved until you hit the save button.

So let's mark the form as complete and then save and go to next form.

This next form is a little bit different from the other two.

It has the ability to repeat, which allows you to enter information more than once without

overwriting the existing data.

For example, enter in information and there is a new option under save, "Save

and add new instance."

This creates a second copy of the form-- it says instance 2 at the top--where I can enter

in new information, for a second doctor's visit.

I'm going to mark unverified so I can come back to it, and the system has memorized my

save option, "Save and add a new instance", and I can enter a third answer.

Let's save and exit the form.

On the record home page, the first two instruments are marked green for complete, and the Personal

Doctors instrument shows multiple statuses.

The blue shows that the statuses are mixed.

Under repeating instruments, all three instances of Personal Doctors show different statuses--red

for incomplete and yellow for unverified.

Data history and field comments are additional fields in data entry forms.

To review data history, find the field you're interested in within a data entry form and

select the little H with a circle next to it.

This page contains all the information that has been entered into the field, who entered

it, when they entered it, and exactly what they put.

Data history is a great way to backtrack if you make a mistake in your data entry process.

Field comments are the speech bubbles below the H. In this area, someone can enter specific

information about the field making it a great way to communicate, especially if the people

doing data entry and the project manager rarely work at the same time.

For example, this person's first name is Mickey, but I'm unsure if it's a typo for Minnie.

I can save my question as a field comment and another person can review the log page

to see and address the comment.

Finally, the record status dashboard has a list of all the records in the project.

You can see the status of each form for each record--incomplete, unverified, or complete--and

if any of these had information in Personal Doctors, you can see the mixed statuses.

To add a new instance, click on the add button.

Otherwise, go to the form for that record by clicking on the dot associated with it.

For more infomation >> REDCap Tutorial Video 5: Data Entry - Duration: 7:30.

-------------------------------------------

Español: Video #2 b Tim Canova Sobre Austeridad y Privatizacion en Estados Unidos - Duration: 5:38.

For more infomation >> Español: Video #2 b Tim Canova Sobre Austeridad y Privatizacion en Estados Unidos - Duration: 5:38.

-------------------------------------------

REDCap Tutorial Video 6: Online Designer Advanced Features - Duration: 13:03.

Now that we've explored the basic features of the online designer, let's explore some

of the more advanced features.

Let's start with branching logic.

Branching logic is a feature that changes what question or page a participant sees next

based on how they answer the current question.

For example, if a participant answers "yes" to the question "Are you taking any prescription

medication?", branching logic then asks a follow up question asking which medication

they take.

This follow up question is only seen if the participant answers "yes".

You can add or modify branching logic by clicking on the split green arrows.

There are two ways to set up your branching logic.

If you're comfortable with the syntax, you can type it out using the advanced branching

logic syntax box.

If you have questions, there's also a "How to use Branching Logic" link next to the

Advanced Branching Logic Syntax option that takes you to the branching logic section of

the FAQ.

The other way to set up branching logic is to use the drag-and-drop logic builder.

You can also use this builder to start making advanced syntax that you can modify later

on.

To use the drag-and-drop builder, find the answer choices you want to apply in the Field

Choices list.

In REDCap, branching logic always goes in the child question, the question that you

want to hide unless certain criteria are met.

For the question "How often do you use Academic Search Complete", you should only see it

if participants answer choose the variable "Academic Search Complete" for the question

"What library databases have you heard of?"

Scroll through the choices until this option is found and drag and drop it into the right-hand

box.

I can drag over as many different fields and answer choices as I like and choose whether

they have 'and' logic, where all the items have to be true, or 'or' logic, where

any of the items can be true.

If I need a mix of 'and' and 'or' logic, I can go to Advanced Syntax and add

parentheses, change some of the 'and's to 'or's, or make any other edits.

REDCap will also let you check your logic with a specific record.

When I go to "Test logic with a record" and select a record, it will tell me if the

logic validates 'true', which shows the field, or 'false', which doesn't.

If you choose to use your own advanced logic by manually typing it, it will tell you whether

the logic is valid or if you have an error.

Next, let's look at piping.

'Piping' allows the user to insert previously collected data into text on a survey or data

collection form, which allows greater control over the question wording.

Piping can also be used to customize survey invitations (for example, by automatically

inserting the respondent's name in the email) or survey completion text (for example, by

inserting the respondent's name into a generic survey completion thank you).

Here, I want to pipe the answer for the variable "library-day" into the field label of the

variable "library_busy".

To do that, include the variable name, such as "library-day", that I want to use and

put it in brackets.

Now when I do data entry, whatever answer was selected in the question "What time

of the day do you most often go to the PCOM library?" will appear as part of the question

"How busy is the PCOM library at that time of day?"

Now let's review matrix fields.

A matrix allows a collection of multiple choice questions to use the same set of answer choices.

You add a matrix by clicking "Add matrix of fields," or you can edit matrices by clicking

on the edit button.

When setting up a matrix, you're still using multiple field labels and variable names.

Instead of entering each variable in a different field and using different popup boxes each

time, you're entering them all at once.

Similarly, you only have to enter one set of answer choices for all the different variables

and you don't have to put a label on each of the answer choices.

Sometimes these choices are left blank when participants will know what they mean, or

if a validated instrument didn't put a label over every answer choice.

For instance, there is no need to label the choice between "No interest" and "Somewhat

interested."

You can have participants give a single answer per row with radio buttons or allow multiple

answers per row with checkboxes.

If you're using radio buttons, you can also allow ranking.

Ranking means that only one answer choice can be selected per column.

Finally, you have to give your matrix a group name so that the background program in REDCap

knows all of these go together.

The following question is an example of a calculated field.

In calculated fields, you can perform calculations on hard numbers, 3+4, or you can pipe in variables

from other places in the project and have REDCap do calculations for you based on those

variables.

Here I'm doing a calculation based on how many hours a week the participant spends in

class and on homework.

I put the variable names for those two fields in brackets, just like I did with piping,

test it on different records, and see what the calculation looks like.

If I make modifications, REDCap will let me know if I have a valid calculation or a syntax

error, which requires a change.

As I start to type, REDCap will suggest fields based on what I'm entering.

This auto-suggestion provides current variable names so that you don't have to remember

them all.

If you have any questions on how to format the equation, the "How do I format the equation?"

link will take you to the calculations section of the REDCap FAQ.

For the most part, the equations are similar to what you might use in Excel, but there

are some places, such as sums or datediffs, that can be a different.

Next, I want to show you a couple of the action tags you can use in REDCap.

Action tags are customizations for data entry forms.

You put them in the field annotation box, which can also be used to include metadata

about a field.

To browse available action tags, click on the "Learn about action tags" button.

There are a number of action tags already available in REDCap, and REDCap administrators

are constantly developing new action tags.

Some of the most common ones are the Hidden tags.

These allow you to hide a field or hide it only on the data entry form, the survey form,

or when you're using the app.

Some commons tags can hide the today or now button, capture the latitude or longitude

of the data enterer, mask a password, put in a placeholder value, make something read

only, or capture the username of the person who entered it.

In this field, we want to capture the date and time of when the page was loaded, so I'm

using the @NOW button.

Whenever someone enters data on this page, the action will automatically capture the

initial date and time of access.

Another popular action tag is @DEFAULT.

@DEFAULT allows values to prefill a field that can be changed by the data enterer.

For example, if you're collecting medications at multiple visits, you could use the @DEFAULT

tab so that the medications automatically fill in entries from the previous visit, and

the data enterer only updates information as needed.

Here, I'm using this option to pipe in the person's name.

The setup is always the same: @DEFAULT= and the value you're using in quotation marks.

Here, it's @DEFAULT="Name: [first_name][last_name]".

To see what your completed instrument looks like, use the preview instrument feature.

This feature allows you to see what your instrument will look like for your participants, but

it won't let you do calculations or branching logic.

Note that previewing the instrument is not the same as testing it: do both to ensure

that your instrument looks and works as intended.

A good portion of your project setup is done in the online designer, but you can also use

the data dictionary.

To view it, go to the Data Dictionary tab and click on "Download the Current Data

Dictionary" to see how REDCap looks at your database.

Variable names are in the first column while the second column shows what form each variable

is on.

Section headers are next to a variable name.

Other columns provide the field type, the field label, and allow entry of branching

logic.

The data dictionary is often a faster way to set up a large project.

It's quicker to type out information rather than pop in and out of the add and edit field

boxes.

However, it's still a good idea to do the first few items in the online designer so

that you've got a better sense of what variables are supposed to look like in the data dictionary.

The data dictionary is better to use if you have several similar fields.

For example, if you need fields for ten different medications in one form, it's faster to do

one field in the online designer and the rest of the fields by copying-pasting and changing

the number at the end of the field name in the data dictionary.

Similarly, if you have a calculation or a piece of branching logic that applies to many

fields, it's faster to find the branching logic in the data dictionary and copy and

paste it into applicable fields.

Finally, I'll show you how to set up repeating instruments.

First, go to the project setup page and enable repeatable instruments in your project.

Choose which instrument to repeat and add a custom label for the repeating instruments,

if needed.

For example, I want the label for each instance of "Personal Doctor" to be the visit date,

so I insert the piping for the date into the label.

Now when I go into a record with repeating instruments, I can see that it automatically

inserts the visit date data as the instance name.

These tips cover the basics of how projects are created in REDCap.

Next, we're going to take a look at how to set up surveys within a project.