Overview
Advanced is the second category in the Form Builder palette. It contains 9 item-level fields that go beyond the plain text/choice/date inputs in Basic Elements: a binary field (Yes/No), formatted-value fields (Currency, Phone), file/media capture fields (File Upload, Signature), scale-based response widgets (Slider, VAS), a graphical-response field (Image Map), and a rich-text response field (Tiny Editor).
This page covers every Advanced Element. For the fields that are common to all elements regardless of category (Field label, Code, Description, Required, Read-only, PHI data, Help text, Help text display, Hidden), see Component Settings (Common) on the Build a Complete CRF page — they are not repeated here.
For elements outside this category, see Basic Elements, Group Elements, and Clinical Elements.
Yes/No
When to use: Use Yes/No for simple binary questions, such as "Did the subject experience an adverse event?" or "Is the subject currently using medication?". Prefer Yes/No over a 2-option Single Choice for this kind of question — it is functionally the same underlying choice field, but the element name communicates intent more clearly to anyone reviewing the CRF later. It is commonly used as the trigger condition for a Display rule that reveals a follow-up field only when the answer is Yes.
Basic settings
| Setting | Description |
|---|---|
| Answer style | Render the two options as radio buttons, or as button-style boxes. |
| Layout | Arrange the two options horizontally or vertically. |
| Option labels | The default "Yes"/"No" labels can be relabeled to match protocol wording (for example "Present"/"Absent") while keeping the same two-option structure. |
There is no separate Advanced Configuration for this element — the option count is fixed at two, and there are no further settings beyond Basic Configuration and the common field settings.
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Currency
When to use: Use Currency for monetary values that need currency-aware formatting — reimbursement amounts, device cost, or drug price tracking. Prefer Currency over a plain Number field whenever the value must display a currency symbol/code and follow currency-specific rounding rules.
Basic settings
| Setting | Description |
|---|---|
| Default currency | The ISO currency the field is denominated in (for example USD, EUR, VND). |
| Currency display | Show the currency next to the entered value as its full Name or its Code. |
| Rounded to | Number of decimal places the entered value is rounded to. |
There is no separate Advanced Configuration for this element beyond Basic Configuration and the common field settings.
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Phone
When to use: Use Phone for telephone number entry that needs country-aware formatting, such as an emergency contact number or a site contact number.
Basic settings
| Setting | Description |
|---|---|
| Include country code | When enabled, the entered number requires/accepts a country calling code. |
| Allowed countries | Restrict entry to phone numbers from a defined list of countries; leave unrestricted to accept any country. |
There is no separate Advanced Configuration for this element beyond Basic Configuration and the common field settings.
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
File Upload
When to use: Use File Upload when a participant or site staff member needs to attach a supporting document or image, such as a lab report, a scanned consent form, or a photograph.
Basic settings
| Setting | Description |
|---|---|
| Allowed file types | Restrict uploads to specific file extensions/formats (for example PDF, JPG, PNG). |
| File upload limit | Maximum number of files that can be attached to this field. |
| Max file size | Maximum size allowed per uploaded file. |
There is no separate Advanced Configuration for this element beyond Basic Configuration and the common field settings. Uploaded files are stored against the specific subject and visit record — mark the field as PHI data (common setting) if uploaded files may contain identifiable information.
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Signature
When to use: Use Signature to capture an electronic signature from a subject or authorized site staff — for example, consent confirmation or investigator sign-off. It is typically placed at the end of a section or CRF as a sign-off step and is subject to e-signature regulatory requirements. See e-Signature setup for the study-level signature feature toggle and related business rules — this field only captures the signature itself; whether signing is available at all is controlled separately at the application level.
Basic settings
| Setting | Description |
|---|---|
| Sub label | Optional instruction text shown under the signature pad (for example "Sign above to confirm consent"). |
There is no separate Advanced Configuration for this element beyond Basic Configuration and the common field settings. The captured signature is stored as a file attachment, the same way File Upload stores its files.
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Slider
When to use: Use Slider for ordered numeric-scale responses where the respondent drags a control along a track, such as a stepped satisfaction score. Use Slider when the scale has meaningful discrete steps. If the protocol specifically calls for a continuous "VAS" instrument (no discrete steps), use VAS instead — see that section for why the two are not interchangeable.
Basic settings
| Setting | Description |
|---|---|
| Min / Max | The lowest and highest value on the slider track. |
| Step | The increment the slider snaps to as it is dragged. |
Advanced settings
| Setting | Description |
|---|---|
| Alignment | Position of the slider control within the field. |
| Left / Middle / Right label | Optional text anchors shown at the ends and midpoint of the track (for example "No pain" / "Worst pain"). |
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
VAS (Visual Analogue Scale)
When to use: Use VAS for continuous scale assessment with no discrete steps — most commonly a validated pain/severity Visual Analog Scale (for example 0–100) referenced explicitly by the protocol. VAS is clinically distinct from Slider: it is the specific validated instrument type used for pain/severity scales, not a generic numeric-track widget. If the source instrument specifically calls for "VAS," using Slider instead is a content-fidelity error, not just a cosmetic difference.
Basic settings
| Setting | Description |
|---|---|
| From / To | The lower and upper bound of the continuous scale (for example 0 to 100). |
Advanced settings
| Setting | Description |
|---|---|
| Alignment | Position of the scale control within the field. |
| Left / Middle / Right label | Optional text anchors shown at the ends and midpoint of the scale. |
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Image Map
When to use: Use Image Map when a respondent must indicate a location on a graphical image rather than answer with text — most commonly a body diagram for marking the location of pain, a lesion, or a symptom.
Basic settings
| Setting | Description |
|---|---|
| Image | The image the respondent clicks on to answer. |
| Selectable regions (hotspots) | Defined zones on the image the respondent can select as their answer. |
Advanced settings
| Setting | Description |
|---|---|
| Response type | Currently supports single-selection response — the respondent selects one region as their answer. |
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Tiny Editor
When to use: Use Tiny Editor when a response needs basic rich-text formatting instead of plain text — for example, a narrative answer where the respondent needs to emphasize part of the text, or a field intended to carry lightly formatted reference content within the CRF. It is rarely the right choice for an ordinary CRF question; for most free-text answers, use Short Text or Long Text instead (see Basic Elements).
The field renders a rich-text editor with a reduced ("simple") toolbar, both when a site user is answering the field during data entry and when the form designer previews the field while configuring it.
Basic settings
| Setting | Description |
|---|---|
| Placeholder | Ghost text shown inside the editor before the respondent enters any content. |
Formatting available to the respondent: Bold, Italic, Underline, Superscript, Subscript, Text color, and Clear formatting. Unlike the Embedding group element, Tiny Editor does not expose block-level formatting (headings, lists, tables, links, images) — its toolbar is intentionally reduced to inline text formatting only.
There is no separate Advanced Configuration table — beyond the common field settings and the placeholder text above, no further configuration options are available for this element.
Advanced Elements are added and configured by Study Administrator and System Administrator roles while building or editing a CRF version in Form Builder.
Screenshot will be added later.
Related Guide
- Basic Elements
- Group Elements
- Clinical Elements
- Build a Complete CRF — full editor workflow and the Component Settings common to every element