Both are acceptable as far as this request is concerned. As the requested information will be used as the foundation for future requests, please expedite this request to that those future requests can be submitted ASAP. The requested documents will be made available to the general public, and this request is not being made for commercial purposes.
In the event that there are fees, I would be grateful if you would inform me of the total charges in advance of fulfilling my request. I would prefer the request filled electronically, by e-mail attachment if available or CD-ROM if not. I look forward to receiving your response to this request within 5 business days, as the statute requires. That would allow the calculated field to be hidden without creating popup warnings about values in hidden fields during data entry.
Can I base my datediff calculation off of today? You may substitute a date or datetime field in your datediff expression with "today" or "now". Note2: It is strongly recommended that you do not use "today" or "now" in calc fields. This is because every time you access and save the form, the calculation will run and update the field value.
Most users calculate time from another field e. Can I create a calculation that uses a variable that is not a number. When a calculation is being evaluated, if the value of any field in the calculation is anything besides a number, that value is replaced with an empty string or "NaN", depending on whether the calculation is being evaluated during data entry, using JavaScript, or during import, form saving, data quality checks, or other server-side processing, using PHP.
Not only will the calculation work on these replacement values rather than the actual values, but it can lead to different results at different times. The calculation could evaluate to different values during data entry than it does during server-side processing, leading to seeing a different value when viewing the record in REDCap compared to viewing the record when exported.
Words like case, class, continue, new, return, submit, and enum are used in javascript. An error will be returned if branching logic is applied to a field with a variable name in which one or more of these words is present. From REDCap v4. In v4. So if the user tries to create a variable name that uses one of those words, REDCap will require him or her to change it.
The words "catch" and "throw" may also cause errors with some versions of Internet explorer. The branching logic format is somewhat different from the normal format because the unique event name must be specified in the logic for the target event.
Why does REDCap slow down or freeze and display a message about a javascript problem when I try to use branching logic syntax or Drag-N-Drop Logic builder in a longitudinal project with over fields? You are encountering a limitation that stems from having a lot of fields especially multiple choice fields in your project.
If a good number of your fields involve multiple choices then the number of choices that the Drag-N-Drop Logic Builder has to load into the pop-up is large. So having a lot of fields with several choices each can slow down the system. The performance is further affected because REDCap uses javascript powered by the user's browser to do the drag-n-drop and also to process the conversion of the advanced syntax to the drag-n-drop method if you decide to switch methods within the pop-up.
The slower your computer and the slower your browser Internet Explorer is the worst, especially versions 6 and 7 , than the slower the drag-n-drop method will be. Chrome is much faster at handling Javascript than other browsers and is recommended. The only other option is to use the data dictionary for building your branching logic. Yes, branching logic may utilize fields either on the current data entry form OR on other forms. Is branching logic for checkboxes different?
Yes, special formatting is needed for the branching logic syntax in 'checkbox' field types. For checkboxes, simply add the coded numerical value inside parentheses after the variable name:.
See the examples below, in which the 'race' field has two options coded as '2' Asian and '4' Caucasian :. Can you program branching logic using dates? My branching logic is not working when I preview my form. Simply previewing a form within the Online Designer will display all questions. In order to test the functionality of your branching logic and calculated fields , you must enter new records and enter test data directly into your forms. Branching logic will only hide questions, not entire data collection instruments.
If you have a list of data collection instruments DCIs in a project traditional or event longitudinal , you will see every form even if you hide all the fields with branching logic on that form. You'll have to click through the forms or "save and go to next form". A work around may be to add a descriptive text reverse branching logic to show when all fields are hidden that the form is not applicable to that specific record or just leave the form blank.
How do I hide a calculation with branching logic without causing a notification from the web form? If a calculated field is hidden by branching logic but will evaluate to a number, it causes the web form to notify the data enterer about a hidden field with data in it.
The statement should be written so if the calculated field is hidden, it will evaluate to false and provide the empty response, meaning there will be no data in the field. This will prevent the notification. What is branching logic? Branching Logic may be employed when fields in the database need to be hidden during certain circumstances.
For instance, it may be best to hide fields related to pregnancy if the subject in the database is male. If you wish to make a field visible ONLY when the values of other fields meet certain conditions and keep it invisible otherwise , you may provide these conditions in the Branching Logic section in the Online Designer shown by the double green arrow icon , or the Branching Logic column in the Data Dictionary.
For basic branching, you can simply drag and drop field names as needed in the Branching Logic dialog box in the Online Designer. If your branching logic is more complex, or if you are working in the Data Dictionary, you will create equations using the syntax described below.
In the equation you must use the project variable names surrounded by [ ] brackets. You may nest within many parenthetical levels for more complex logic. Please note that for items that are coded numerically, such as dropdowns and radio buttons, you will need to provide the coded numerical value in the equation rather than the displayed text label. See the examples below. If that field with that value should not appear due to upstream branching you will receive an error message.
Action Tags are special terms that begin with the ' ' sign that can be placed inside a field's Field Annotation.
Each action tag has a corresponding action that is performed for the field when displayed on data entry forms and survey pages. Such actions may include hiding or disabling a given field either on a survey, data entry form, or both. There is a comprehensive list of all available action tags that you may use within the Online Designer "Edit Field" pop up box.
You can use as many as you want for a single field, but if you do use more than one tag for a field, make sure to put a space or line break between them. Because the action tags are used as part of the Field Annotation, they are not displayed anywhere on the page.
For example, if you put HIDDEN-SURVEY in a field's Field Annotation text box, then the field will always stay hidden when viewed on a survey page, but the field will be visible when viewing the same instrument as a data entry form, which might be helpful if you want to hide specific fields from your survey participants so that they do not see them.
There are many different use cases for each action tag. The most effective way to use this is to pipe in a key piece of information such as the medication name here. The custom name will then show up next to the completion status for the individual instances on the record home page. If this is a longitudinal project and you are repeating the entire event, you cannot use custom naming for the repeating event. You can only compare the first instance of repeating forms with double data entry.
From the Data Comparison Tool:. Data can be compared and even merged if using Double Data Entry , but it will only allow comparison and merging of Instance 1 of a repeating instrument or repeating event.
Thus all other repeating data will be ignored on this page. Also, all non-repeating data can still be compared and merged.
However, several people have found when they import into repeating forms the import is incomplete. It is highly recommended you manually check that the data imported correctly and completely after importing data into repeating forms. Yes, you can. First, you need to enable the form as repeating in the project in general on the Project Setup page. Then make sure the form is enabled as a survey and go into the Survey Settings.
This will allow your participants to repeat the survey. You will be able to choose if you want them to see the option to repeat the survey before or after they click submit, and you will be able to customize what the text on the repeat button says. There are limitations to using repeating forms in surveys. You cannot schedule surveys that are in repeated instruments or repeated events to go out on a regular basis.
You need to compose the survey invitation for each instance manually using either the compose invitations in the participant list or the option to send a survey invitation in the survey instance itself. Additional, survey queues in repeating events only work on the first instance of the event.
Repeating forms is the ability to use the same form multiple times in a project or an event, without having to define how many times you want to use it.
You can use it a different number of times for each record in the project and add new instances of the form as you need them for each record. For example, if you are collecting a list of medications, you could create a form that asks for one of the medications, and then add a new instance for each additional medication:. In longitudinal projects, you have the option of repeating individual forms inside an event or repeating the event as a whole. If you choose to repeat just a form in an event, you will have multiple instances of just the form s you want to repeat.
If you choose to repeat the entire event, all the forms in the event will be offered again, and you will have the same number of instances of each of the forms in the event, in that record. You cannot repeat an instrument inside a repeated event. However, you cannot filter by individual instances. All data that is not in a repeating form will be on one line, and then each instance of a repeating field will receive its own line, similar to how the data exports in a longitudinal study:.
The formatting will be the same if the project is longitudinal; it will just include the event information as well. The completion status of a repeating instrument will have three small circles instead of just one. If the completion status of all the instruments is the same, the circles will be colored red incomplete , yellow unverified , or green complete , just like with regular forms.
You can add information from repeating forms in reports. You will just add the field s you need the same way as you would any field in the project. When you view the report, the information from the instances will be on their own line, similar to how information displays for different events in a longitudinal project:.
You can pipe information from other forms into a repeating form, and you can pipe information from one field to another within an instance. You cannot pipe information out of a specific instance to someplace else in the project; there is no syntax to refer to a specific instance when you are piping.
The same applies for branching logic and calculations—you can use items from outside the repeating form, and you can use information within an instance, but you cannot use information inside a single instance for piping or calculations outside of the specific instance. The ASI will only fire once conditions are met for the first instance, and reminders will only be sent for that instance.
You cannot automatically invite or remind a participant to repeat a survey. Be aware that adding repeating instruments can affect branching logic, calculations, piping, and survey set up. Existing records must be deleted by opening each one individually and deleting them. To do so, you must first have permission to delete records. Go to the User Rights page. This link is in the Applications section of the project menu. Open your account, and scroll to the bottom of the screen.
Select that option and save your account. Then, open any record or survey response. You can use the 'delete record' button to completely erase all data across all instruments for the given record. This separate permission is in the Data Entry Rights section of your account, in the upper right of the screen. To enter or view individual records, you can navigate to the " Data Collection " section on the left menu bar.
Depending on your project type, you will see "Add or View Survey Responses", a listing of your form names, or a "Data Entry" icon. You can also use the " Data Exports, Reports and Stats " module under "Applications" to view your data.
Create New Reports to search and view your project data in aggregate. When designing a project with multiple arms, its best practice to designate the first form with the record ID unique identifier field to each arm. This will allow for the unique identifier field to display within each arm so you have the ability to rename the record ID.
Can I edit survey responses? Yes, survey responses CAN be edited so long as you have been given user privileges to do so via the User Rights page. Once you have been given user privileges to edit survey responses, you will see an Edit Response button at the top of the data entry form when viewing the response the response will be initially read-only. After clicking that button, the response will become editable as normal.
Is there a way to delete data in a given record for just single instrument or event not the entire record? First, follow the instructions in the section above about deleting an individual record to ensure you have the correct permissions on your user account. You will find the delete options underneath the 'save' buttons at the bottom of the page.
There are options to erase all this record's data on the current instrument OR on the current event longitudinal projects ONLY. Technically, no. Data is not anonymous when collected using the Participant List; but it can be "coded" and "unidentifiable" to the project admins. Through the REDCap interface, there is no link between the modules and no connection between the email address entered and the responses collected unless you enter unique values into the "Participant Identifier optional " field.
The Participant Identifier field links the email address to the survey responses. To ensure confidentiality of the data, REDCap tracks responses by attributing it to an email address. Access to the association between the individual who took the survey and the survey responses is restricted in the database and can only be accessed by authorized privileged users system engineers, database admins. REDCap holds the key to the code.
For the Participant List, the identifying emails can be forever stripped from the data with no way for anyone to go back and find out the identity of the individual from whom the data the was obtained.
No re-identification is possible if you do the following:. Use the Public Survey Link to collect anonymous survey data. Only participants that answer the first survey will be able to respond to the follow-up surveys. If you wish to collect additional surveys for the non-responders, you will need to create additional REDCap projects with the follow-up surveys or you may have to open the survey using the link provided and save the survey without data issue will be required fields.
As you know, each exported record will contain a subject's response to all of the survey questions. Also note: Projects containing data entry forms and surveys cannot be considered anonymous. The emailed invitations send only 1 uniquesurvey link per email address; therefore, only the first person in the distribution group who clicks on the email link will be able to complete the survey. You'll be able to email only non-responders if you want to send a reminder. With the general distribution email, you won't be able to track responses and participants will have the potential to complete the survey more than once.
How do I manage multiple surveys Participant Contact Lists? For for projects with multiple surveys, there will be one participant list per survey.
The Public Survey Link and Participant List have been separated onto different pages within Manage Survey Participants because they each represent a different method for inviting survey participants. Note: To be able to add participants directly to the Participant Contact List, the first data collection instrument DCI must be enabled a survey.
All participants of all surveys must be added to the first survey of the project. How do I send out my survey? The most common methods to send out a survey are the Public Link and the Participant List.
These methods are on the "Manage Survey Participants" page, which is accessed through the project menu's Data Collection section. Public Link: This is a single survey link for your project which all participants will click on. This link can be copy and pasted into the body of an email message in your own email client.
It can also be posted to web pages. This is the most common method for large, anonymous surveys where you do not need to follow-up with survey respondents. It is also possible to identify an individual's survey answers by providing an Identifier for each participant. This is the most common method when you need to know who has responded so far and who hasn't. Designate an Email Field: You can capture email addresses for sending invitations to your survey participants by designating a field in your project.
If a field is designated for that purpose, then any records in your project that have an email address captured for that particular field will have that email address show up as the participant's email address in the Participant List unless an email address has already been entered for that participant in the Participant List directly.
Using the designated email address field can be especially valuable when your first data collection instrument is not enabled as a survey while one or more other instruments have been enabled as surveys.
Since email addresses can only be entered into the Participant List directly for the first data collection instrument, the designated email field provides another opportunity to capture the email address of survey participants. NOTE: If the participant's email address has already been captured directly in the Participant List, then that email address will supersede the value of the email field here when survey invitations are sent to the participant. Compose Survey Invite: This option is available on the Participant List and on survey data entry pages for individual records.
This allows you to create and send the actual survey invitations. On the Survey Invitation Log page, there is a checkbox for displaying the reminders. Check that box and then click the button to apply the filters. Then you can use the red x to delete the reminders.
Once a survey invitation is in the Survey Invitation Log, the only way to get rid of them through the UI is to click on the red X next to each one. The easiest way to simply stop future surveys from going out is to add a new field call "Do not send further survey" in a "Control Center" form, and add that to the ASI condition and click "Ensure logic is still true before sending invitation? This effectively depends on "Ensure logic is still true before sending invitation?
Whether changes in ASI and the checkbox will affect invitation already in the queue I don't know. Hence, please check before you use it in anger. If you make changes to piping, logic You may have to delete scheduled invites and reschedule. And don't forget the reminders! They are not displayed by default. As long as this was done before they clicked on the link, they would not see the survey questions to answer. Yes, but it will only affect future invites. If you need to update the email field for already scheduled invites, you must delete the invites and reschedule.
If I create a timestamp field, including hours, minutes, and days, can I create an automated survey invitation that will detect how many days it has been since the timestamp? It's possible, but if you do this be aware that the server-side PHP datediff function always treats the 'today' keyword as being the first second of the day.
If your timestamp value is at six pm , then an ASI checking the datediff on the same day as that timestamp will actually return a result of 0. On the next day it will return 0. On succeeding days it will return 1. If a survey has already been completed, will the scheduler still send out survey invitations? There are a variety of reasons why survey invitations might be in the schedule to be sent even though a survey is already completed.
The survey invite might have been both manually scheduled and automatically scheduled. The survey invite might have been scheduled but then the URL for the survey sent to the participant directly. Regardless, the scheduler will not send out a survey invitation for an already completed survey. Do automated survey invitations preclude manual survey invitations? Automated survey invitations do not preclude manual survey invitations or vice versa.
An automated survey invitation will not be scheduled if an automated survey invitation has previously been scheduled, but if an automated survey invitation's logic is checked and found to be true, a survey invitation will be scheduled regardless of whether or not a survey invitation has been previously scheduled manually. Likewise, if an automated survey invitation has been scheduled, one can still schedule a survey invitation manually.
How can I schedule a survey invitation to go out at a specific time? You can use a form of scheduling that allows you to specify next day, next Monday, etc. However that form of scheduling will not allow you to specify a lapse of a certain number of days. What mathematical operations can be used in the logic for Automated Survey Invitations? Suppose you want to send a followup survey seven days after a surgery. You could define the condition of an automated survey invitation rule to detect that six days have passed since the surgery date and then schedule the survey invitation to be sent on the next day at noon.
By checking for the sixth day instead of the seventh day, you gain the ability to set the specific time to send the invitation and you gain the opportunity to stop the sending of the invitation, if it turns out that you don't really want to send it.
You could, instead, check that one day has passed and then set the invitation to be sent six days later, but you would lose the ability to set the specific time that the invitation is sent. When are automated survey invitations sent out? Automated Survey Invitations are survey invitations that are automatically scheduled for immediate or future sending when certain conditions are true.
NOTE: In previous versions, conditions that used the "today" variable would require extra effort to make sure they were checked every day, but REDCap now detects and checks those conditions daily. The conditions are checked every twelve hours. The specific times they are checked during the day varies from one instance of REDCap to the next and changes over time. If the invitation is scheduled to be sent in the future, and a piped variable is later changed before the scheduled invitation is sent, that change will NOT be included in the already scheduled invitation.
First, change the ASI so that no more reminders get scheduled. Then, one by one, delete the reminders from the Survey Invitation Log. Do participants with partially completed surveys receive the automated survey invitation reminders? Yes, participants will continue to receive automated survey reminders if they have not completed the survey or they have a partially completed survey response.
What are Automated Survey Invitations? For any survey in your REDCap project, you may define your conditions for Automated Survey Invitations that will be sent out for a specified survey. This is done on the Online Designer page. Automated survey invitations may be understood as a way to have invitations sent to your survey participants, but rather than sending or scheduling them manually via the Participant List, the invitations can be scheduled to be sent automatically i.
Yes, his can be done two different ways as seen below. This only works for the first page if it is a multi-page survey. This is because there is not a real opportunity to modify the survey links sent to participants via the Participants List because REDCap automatically sends them out as-is.
If you wish to pre-fill such information, it is highly recommended to use method 2 below. See the example below. The form's "method" must be "post" and its "action" must be the survey link URL. Each question you wish to pre-fill will be represented as a field in the form, in which the field's "name" attribute is the REDCap variable name and its value is the question value you wish to pre-fill on the survey page.
The form field may be an input, text area, or select field. The example below shows them all as hidden input fields, which could presumably have been loaded dynamically, and thus do not need to display their value. In this example, the only thing that would be seen on the webpage is the "Pre-fill Survey" button. This module allows two project users or roles to be set as Data Entry Person 1 and Data Entry Person 2 using User Rights page , and allows them to create records with the same name and enter data for the same record without seeing one another's data.
It is sometimes recommended to use the Data Access Groups over the actual DDE module to implement a form of double data entry. The advantages of using DAGs include allowing an unlimited number of users to be in a group and enter data, to utilize the Data Import Tool, and to access all Applications pages. So if it is necessary for a third party "reviewer" to merge the two records into a third record, then in that case the DDE module would be advantageous over using DAGs.
When exporting records or viewing a report from a double data entry DDE project, the exported record set will, by default, include three records for every merged record the first user's entry, the second user's entry, and the merged record.
To limit the exported viewed records to only the final merged version of each record, follow these steps:. Is it possible copy the Data Resolution Workflow queries into a new project when copying a project? Are the Field Comments logged?
The Data Export tool includes instructions for linking the exported syntax and data files. Note that SPSS has several variable naming conventions:. Then take the following actions. The method used for calculating the percentile values is the same algorithm utilized by both R its default method - type 7 and Microsoft Excel.
How can I ensure that the leading zeros of numbers entered into text fields are retained when the data is exported? Excel will discard the leading zeros if you open your export file in Excel. The leading zeros will be retained if you open the file in Notepad. Rather than opening the file directly in Excel you should open the data into Excel and specify that the column with the leading zeros is a text column. The use of OpenOffice. CALC will ask you for a character set every time you open a.
Choose "unicode utf-8 " from the options listed. How do I export my entire data set? Then follow the prompts. Can I restrict access to a custom report? You can customize access based on individual users and data access groups. The data import template, available on the Data Import Tool page, will contain the appropriate form status variable name for your project forms.
Form status is imported as dropdown field type coded as. Data cannot be directly imported into calculated fields. If you are importing data to a field you have set up to calculate a value, follow these steps:. REDCap can auto-number records during the data import process. You will also need to provide a placeholder value as the record ID in the import file. Each individual record will need a unique placeholder value for the import to be successful.
Once data is downloaded from REDCap to a device ex: computer, laptop, mobile device , the user is responsible for that data. The following example will illustrate the distinction that was made above. Let's say that users 1 and 2 have identical data entry roles. In this situation the Create and Edit Record rights would be assigned to both users. This can be done by assigning User1 into the access group1 and User2 to the access group2. Who can unlock a record?
Can I restrict a user from viewing certain fields? This will prevent the user from viewing the entire form. You cannot selectively prevent a user from viewing certain fields within a form. How can I give someone access to my project? Assign permissions and save changes. No, you can not lock an event. You can lock a record's form and you can lock all forms across all events the entire record. The REDCap password for users in the table-based authentication mode must be at least 9 characters in length and must consist of at least one lower-case letter, one upper-case letter, and one number.
The log files will stay intact when a user is removed from the project or suspended. Even if the user is completed removed from the entire REDCap installation which requires a REDCap Administrator , the log file will still reflect the actions performed by that user.
What functions can be used in Data Quality custom rules? The Data Quality module can perform many advanced functions for custom rules that users create. What mathematical operations can be used in the logic for Data Quality rules? The Data Quality module allows you to find discrepancies in your project data. You can create your own custom rules that REDCap will execute to determine if a specific data value is discrepant or not.
Your custom rules can include mathematical operations and also advanced functions listed below to provide you with a great amount of power for validating your project data. You can also activate the real time execution of your custom rules to continually ensure the data integrity of your project.
Advanced functions can be used in the logic. A complete list of ALL available functions is listed below. NOTE: These functions are very similar - and in some cases identical - to functions that can be used for calculated fields and branching logic.
You may use IF statements i. Yes, for example, you can indicate "age" as: rounddown datediff "today",[dob],"y". This is the same as in calc fields. This will change the meaning of the data already entered and you will have to re-enter responses for those records to ensure accuracy. REDCap will flag this as:. The best thing to do when making field choice changes for radiobuttons, checkboxes or dropdowns is to leave the current response choices as is and start with the next available code.
If you re-code like this, after the changes are committed any options selected for "1, red" will change to "1, blue"; "2, yellow" to "2, green"; "3, blue" to "3, orange". In general you can assume that only the data that is tied to the deleted events is affected and that there will be no adverse impact on the data that has been entered for the remaining events.
However there could be an impact on this data if you are using branching logic or calculations across events. What happens to the data in an ongoing longitudinal project if I delete some of the events? The data which was tied to the deleted events will not be erased. Does the project go offline until the changes are approved?
Can new surveys and records still be added to the project? The project does not go offline during the change request process. All the functionality remains the same so you can continue adding and updating records as needed while the changes are pending. For radiobutton, checkbox and dropdown fields, can I delete response options?
Deleting radiobutton or dropdown choices does not change the data saved to the database, but it deletes the ability to select that option. To make changes after you have moved your project to Production, first download the current Data Dictionary so that you can revert to the current version, if necessary, if something goes wrong with making changes.
After making your changes, you can review them by clicking on "view a detailed summary of all drafted changes" hyperlink at the top of the page. REDCap will flag any changes that may negatively impact your data with the following critical warnings in red:.
If anything is questionable or flagged as critical, you may receive an email from the Administrator with this information to confirm that you really want to make the change. Certain changes to the structure of the database, such as deleting events in a longitudinal project can only be done by the REDCap Administrator. What are the risks of modifying a database that is already in Production? Altering a database that is in Production can cause data loss and challenges to your data analysis.
It is acceptable to add choices to a dropdown, radio, or checkbox field; however adding an option or even an entire field may present other analytical challenges. For example, if a response option is added, it is added to all instruments for all records. One must either consider their results in light of the instrument contents at the time of data capture or one must be careful to avoid making conclusions which would be affected by the change to the instrument.
Versioning your instruments and tracking changes over time is recommended. Use the Project Revision History to confirm changes and revisions. For radiobutton, checkbox and dropdown fields, can I add response options without impacting my data? Adding new choices has no data impact to data entered.
New choices will be added and display on all records. NOTE: Adding new response choices to a question does make it a slightly different question and, for that reason alone, could impact the integrity and analysis of your data. It is a new "version" of the question. REDCap has the capability to make voice calls and send SMS text messages to survey respondents by using a third-party web service named Twilio www.
In this way, you could invite a participant to take a survey by sending them an SMS message or by calling them on their phone. There are many different options available for how you can invite participants and how they can take your surveys, either as a voice call survey or as an SMS conversation. For those not using Twilio, there are many providers that let you convert an email into an SMS.
You have to register your email address with them for billing, then you construct your messages using a particular pattern, e. To: provider. This mechanism would work fine from within REDCap - even for automated invitations - although the built-in text containing the survey link may not be particularly nice in an SMS. The first step in accessing the API for any project is to check if you have the appropriate user rights in the project in order to use the API.
Secondly, you will need to request an API token. Please note: you will need to request a different API token for each project. You can run the method in your browser to see what type of response you'll get. You can copy and paste your chosen language code into your preferred scripting tool and run it there. We recommend the R program for demo purposes: it's free, light weight and will run on both Windows and Mac environments.
The Data Entry Trigger is an advanced feature. For example, if you wish to log the activity of records being modified over time by a remote system outside REDCap, you can use this to do so. Another use case might be if you're using the API data export to keep another system's data in sync with data in a REDCap project, in which the Data Entry Trigger would allow you to keep them exactly in sync by notifying your triggered script to pull any new data from at the moment it is saved in REDCap this might be more optimal and accurate than running a cron job to pull the data every so often from REDCap.
NOTE: If the names of your records i. SSN, MRN, name , for security reasons, it is highly recommended that you use an encrypted connection i. Autonomous utilization Research groups have complete autonomy and control to add new users.
Fully customizable You are in total control of shaping your database or survey. Many advanced features Such as branching logic, file uploading, and calculated fields. A quick and easy software installation process So that you can get REDCap running and fully functional in a matter of minutes.
0コメント