X

Note: All elements have a general tab, but the fields contained within vary by element type. In this graphic, a Field element has been selected.

Used to link follow-up attachments with the followup toolbar; this ensures that the attachment is included should the follow-up be emailed to another user. The value entered here should match the id field of the Attachment element in the follow-up popup grid.

For RL6:PeerReview or RL6:RootCause users, this option allows you to choose cross-references that can be used for the selected entity under which the cross-reference component was added.

For RL6:PeerReview:

• The Event Timeline component uses the entity 700006 (PRW Events) and the available cross reference options are: 1) Timeline Events and Patients - to link patients to timeline events 2) Timeline Events and Persons Involved - to link providers from the Persons Involved tab to timeline events.
• The Review Tab component uses the entity 700008 (PRW Reviews) and allows one option: Reviews and Persons Involved to link persons involved (i.e. providers and reviewers) to reviews

For RL6:RootCause, when configuring action plans using the entity 600006 (RCA Action Plan), you can choose one option: Investigation Items and Action Plans to link investigation items with action plans.

The name of the element type as it will appear on the form. This value appears above the element and does not support HTML tags.

The location of the caption with respect to the top of the grid.

Show an embedded child pop up grid. This feature should only be used by RLDatix.

Determines the width of the element within the cluster. The unit is the percentage of the cluster. Entering 50, for example, will make this element half the width of the cluster. When the field is blank, the element defaults to 100 percent.

This field is read only. It is reserved for future use.

Sets the value of this field when the form is opened. Depending on the element ID, a list may appear when you click the ellipsis.

This indicates whether the field should be hidden or visible on the form. If the field is automatically populated you may wish to hide the field from the user. For example, the file number field is on every form but is hidden because it is automatically calculated. The options are HIDDEN or LABEL (which is the default setting when the field is left blank).

For a field element, use the field picker to search for and select the field to add to the cluster.

Choose an option: True or False

A required field for the listed element types that determines the table from which fields may be selected for the grid. A grid may only contain fields from the table selected here. For attachments, you should always select table to which the attachment is related, such as Patient Outcomes. Click the ellipsis icon to choose the table caption.

Determines the filter used in a Popup grid

Used when the Popup Grid needs to show the embedded child Popup Grid. It specifies the condition to show which child grid shows when the parent Popup Grid row is selected. This feature should only be used by RLDatix developers.

Determines whether or not the attachment element’s caption is visible on the form.

Removes the Add link that appears below the popup grid.

Provides a unique ID for the attachment/grid if you wish to display, hide or require an attachment based on a selection made from another field.

The number of pixels by which the pick tree is indented.

Increases the width of the left panel and hides the attachment list. Enter a percentage value to determine the increase in width.

Associate a lookup with the section to display the magnifying glass icon next to the section title. Clicking the icon opens the associated lookup dialog. Lookups can be added to sections, clusters or fields.

Note: Lookups are not available in forms used in the Mobile application.

Used to dynamically select which lookup to use for the field. If the General Event Type is ADR, for example, the is patient lookup should be used; otherwise, the staff lookup is used.

Note: When a lookup visibility expression is configured for a responsive form, a default lookup needs to be selected.

Used to link the follow-up description with the followup toolbar to ensure that the selected form letter is inserted into the correct field. The value entered here should match the id field of the Description field in the follow-up popup grid.

The PropertyName field, which is a hidden field in the IncidentAttachments table, can be automatically populated with the value entered here.

The number of columns in which the options selected from the pick tree are displayed.

Determines whether or not the attachment added to grid record can be viewed from the table (TRUE). If you use this feature, you must specify each column’s width as a percentage of the table (Columns Tab ). This feature should only be used with the follow-ups grid.

Select either true or false to determine if the popup, inline grid, vertical tab, event timeline, Html link grid or person involved tab label is displayed on the form. Leaving this field blank defaults to true.

For RL6:PeerReview and RL6:RootCause users, choose one of the following options:

• One - allows one link to the cross reference. If no option is selected, this is the default selection.
• Many - allows multiple links to the cross reference

Note: To support associating multiple reviewers or providers with a single view, the calculated Reviewer ID and ProviderIn RL6:PeerReview, this term refers to any user who is being reviewed in a Peer Review investigation. ID fields in the PR Reviews table return comma separated values. If you enable the "Reviews and Persons Involved" cross reference to contain many links, you should use the "contains" operator when building functionality elsewhere in the application for the Reviewer ID or Provider ID (e.g., Reviewer ID "contains" [USER:ID]).

The name of the selected field as it will appear on the form. If left unchanged the name will display the form caption as defined in the field’s properties (Adding or Editing Fields).

Captions can be left, center or right aligned.

Select top to place the caption above the field. When no selection is made, the caption appears to the left of the field. When the Caption Position is set to top, the Caption Width setting is ignored.

Determines how much space (in pixels) appears between the start of the caption and its associated field. When left blank, the caption takes up approximately 40% of the space allotted for the caption and field. If a value is entered that is smaller than the space required to show the label, the field appears right after the caption or if the caption contains more than one word, it will wrap to the second line:

This field is not used. If you wish to refresh this field based on a selection made from another list, you must provide the section in which the field resides with an ID and then enter that value into the trigger field’s Extra Sections field (Refreshing Sections in a Form).

Select either true or false to determine if the field label is displayed on the form. Leaving this field blank defaults to true.

Note: All element types use the Logic tab. See Logic Tab for a description of the Mandatory, Availability, Visibility and Readonly fields. The additional fields displayed for Pick Tree Inline Grid and Popup Grid elements are shown here.

Similar to row visibility expression in a standard pop-up grid, this field determines when cards are shown to users. Choose one of the following options:

• True - all cards will be show to all users who have access to the section/tab where the vertical tab is used.
• Note: When no option is selected (i.e. blank), this is selected by default.
• False - no cards will be shown to any users who have access to the section/tab where the vertical tab is used.
• Calculated - cards will display for users when the content of the card or the user variables (e.g., in file access level) meets the condition.

Similar to Row Deletability expression in a standard pop-up grid, this field determines when cards can be deleted by user. Choose one of the following options:

• True - cards can always be deleted. This is the same if no option is selected (i.e. blank).
• False - cards can never be deleted.
• Calculated - cards can only be deleted when the content of the card or the user variables (e.g., in file access level) meets the condition.
  

Similar to Row ReadOnly expression in a standard pop-grid, this field determines when cards are read-only. Choose one of the following options:

• True - cards are always read-only
• False - cards are never read-only. This is the same if no option is selected (i.e. blank).
• Calculated - cards are read-only when the content of the card or the user variables (e.g., in file access level) meets the condition.

Allows you to display a subset of options (i.e. based on the cross reference that is being used - see Available Cross References) for linking cross references. For example, in RL6: PeerReview, if you are linking persons involved to a timeline event, you may want to create a calculated expression to display only providers. Choose an option:

• True/False - displays all cross reference values.
• Calculated - allows you to create an expression in the Expression Editor which determines the subset options to be displayed in the form (e.g. in file access level equals "provider").

Note: When calculating filters for Cross Reference, you must use fields from the Cross Reference table.

The default is True. Check the Row Deletability box and choose:

• True – to allow rows in the grid be deleted.
• False – to turn off the ability to delete rows.
• Calculated – to use the Expression Editor to define when the rows can be deleted (Expression Editor Overview).

The default is True. Check the Row Visibility box and choose:

• True – to make all rows in the grid visible.
• False – to hide all row in the grid.
• Calculated – to use the Expression Editor to define when the rows are visible (Expression Editor Overview).

This option is used for the purpose of summarizing data from other parts (clusters, fields, pop-ups) which have been previously defined elsewhere in the form. An example of how this is used appears in the Investigation Overview tab of the standard RCA and PeerReview management forms. As data is entered in other parts of the form, matching elements are updated in the Investigation Overview tab to provide a read-only summary of the file. Check the Inline Summary View box and choose:

• True - elements are displayed as read-only and are updated as data is entered from the original instance.
• False - if you want to allow user input for the element, choose False or leave this field blank.
• Note: It is not recommended to have multiple instances of an element that allows user input or modification. However, if you do, the most recent data entered in an element will override all instances of that element.
• Calculated

The default is False. Check the Row Readonly box and choose:

• True – to make all fields in the grid readonly.
• False – to enable all rows in the grid.
• Calculated – to use the Expression Editor to define when the row are editable (Expression Editor Overview).

Check the Root Cause box and choose:

• True – to use the root cause pick tree.
• False – to disable root cause pick tree.
• Calculated – to use the Expression Editor to define when the root cause pick tree is available (see Expression Editor Overview).

Note: The tab is only seen for Field elements.

Choose the field(s) that should be reset to empty when a value is selected from this field. If multiple fields are entered, be sure that no spaces exist between the field IDs, which are separated by commas. This field must also be set to do a Post Back (Refreshing Sections in a Form) to clear the other elements.

This value is only used for MList fields (a field where multiple values may be selected, such as Contributing Factors). The default behavior is that the user must click the Add/Modify link to open a dialogbox that is used to make selections. If this value is set to true, the list items will appear as a series of check boxes that have been embedded into the form. For optimal display, this option should only be used for small pick lists. This field is used in combination with the Repeat Columns and Repeat Direction fields, described below.

Note: If Embed Check List is set to true, postback will not occur for the form as it would for unembedded multi-pick lists.

Enter the ID values for the sections (which are specified on the General tab (General Tab) of the section properties), separated by commas, that should be refreshed when the list item is selected. In the Field Manager (Adding or Editing Fields), the Allow PostbackA request that is made from a form (entry or management) to the RL6 server to refresh its contents with relevant fields, variables, and configurations based on selections made by the user. During a postback, you may see a brief loading screen as the form retrieves relevant data from the server to refresh the page. For example, if a user selects a General Event Type of Fall, a postback may be used to ensure only the specific event types relating to Fall are displayed in the Specific Event Type drop-down list. field must be checked for the field that triggers the refresh. By default, all the fields contained within the AutoPostback field’s section are refreshed. If the field you wish to refresh resides in another section, you must specify the ID of that section in the Extra Sections field to refresh those fields as well.

When this setting is left blank, only one column is used for the embedded multipick list. When set to 2, two columns are used to display the contents. This parameter is only relevant for multipick fields that have been embedded into the form (see the Embed Check List field for details).

Note: This field is only used with multi-pick fields (MList).

Sets the listing of multipick items to be read across (by selecting Horizontal) or down (by selecting Vertical). This parameter is only relevant for multipick fields that have been embedded into the form (see the Embed Check List field for details).

Note: This field is only used with multi-pick fields (MList).

Note: This tab is only seen for Field elements, and is not available for responsive forms.

The kind of validation that you would like to perform on the field as soon as the value is entered into the field (i.e., type in a value and press tab for the validation to take place). The validation is also checked when the form is saved. For each type, you must complete the corresponding Error MessageThe test results are received via a message from the client integration engine to the RL integration engine. Each message may contain one or more test results; these test results only pertain to a single order. and Check fields:

• Required – the field must be completed. A green asterisk does not appear next field made required through this method.
• Range – the entry must be between the values specified in the Min Value and Max Value fields.
• For date ranges, enter Today in the Min Value to enforce the selection of only future dates; conversely, enter Today in the Max Value to enforce the selection of only past dates.
• Compare – the entry must be equal to (=), greater than (>), less than (<), greater than or equal to (>=), less than or equal to (<=), or not equal to (<>) the field id entered into the Compare To field.
• Text Format – checks the kind and number of characters that should appear in the field. See the Format and Regular Expression fields for details.
• Date – the date must be in a valid format, as defined in the general system parameters.
• Limit Length – the number of characters allowed are limited to the value entered in the Max Chars field. All fields have a default length that is defined in the database; use this field to decrease the total possible length (i.e., you can never allow more characters than the table allows). Optionally, you can also choose an option from the Character Count drop-down to determine whether the counter will display how many characters entered (i.e. Up) or how many characters available within the Max Chars limit (i.e. Down).

The error message to display to the user when the validation type fails.

The details of the validation type. For example, whether the field is required, is between a two numeric values or is under a certain length can be set here.

• Required – set to True of False. When left blank, it defaults to True.
• Min Value / Max Value – the number or date by which the field’s value is compared. For date fields, enter Today for the Max Value if the date cannot be in the future.
• Compare To / OperatorThe instructions used to evaluate a number, date or text string: greater than (>), equal to (=), or contains, to name a few. Operators are use to build ad hoc searches, report parameters and alert conditions. – the number, date or text value by which the field’s value is compared. Choose the operator to determine how it is compared: =, >, >=, <, <= or <> (not equal).
• Format / Regular Expression – enter RegEx in the Format field and then type the possible character combinations in the following format:
  ^([type]{length}|[other type]{other length]...)$
  
  For example: ^([0-9]{5}|[0-9]{9}|([A-Za-z][0-9]){3})$
  
  Allows for: 48076 ([0-9]{5}), 480761123 ([0-9]{9}), or M6J2S2 (([A-Za-z][0-9]){3})
• Max Chars – to total number of character, including spaces, that a field can contain. Entering 11, for example, would allows for a social security number to be entered with hyphens: 111-22-9999.
• Character Count - determines how characters are counted when users enter data into large text fields. There are two options: Up counts the number of characters entered; Down counts the characters remaining as defined by the Max Chars limit.
• Note: You can only choose Down if you use the Limit Length property and defined the Max Chars. If no Limit Length is specified, characters are counted up.

Note: The tab is only seen for Field elements.

Check this box if you wish to use a javascript function on this field.

The field(s) whose value(s) you would like to send into the JavaScript function.

Note: If using multiple field IDs, separate them with commas without any space after the commas.

The field that should be updated as a result of the function execution.

Note: If using multiple field IDs, separate them with commas without any space after the comma

When the JavaScript function should be executed (e.g., onfocus, onblur)

The name of the JavaScript function that should be executed. The following options are available:

• Age Calculation - This option calculates age based on two input fields and outputs the age as a text value. For example, in RL6:Risk, 500016,59 can be entered in the Input field Id where 500016 is the PK_ID for Person Affected Date of Birth, and 59 is the PK_ID of Event Date. In the Output field, 500017 (Person Affected Age field) can be entered to determine the field that displays the calculated age. For this example, this would need to be set up both on the Person Affected Date of Birth field and the Event Date field. Optionally, you can also use the Extra Outputs fields (Age in Days, Age in Months, Age in Years) to recalculate the age into different units (days, months, or years) to be mapped to selected age fields. Note: For both fields (e.g. Date of Birth and Event Date), the Input/Output Field IDs must be entered and Age Calculation option selected. You cannot add your own functions.
• Copy Fields - This function copies values from Input Field IDs to Output Field IDs.
• Note: You can copy more than one "pair" of input/output fields.
• Copy Current User Name - This option copies the current user's full name as a text value from the Input field Id to the Output field Id.

Note: This tab is only seen for Popup Grid and Inline Grid elements.

In order to create a new grid, you must define at least one column before saving the form or editing another element.

Click the Add link when you have finished configuring the field.

Ignore this field. Use the Width field instead.

Click the Del link to remove the column from the grid.

Use the field picker to select the field to use for one of the columns in the grid.

The title that appears in the grey row at the top of the grid. This should be descriptive enough that users understand what should be (or was) entered for this cell of the grid.

Ignore this field. Use the Width field instead.

Ignore this field. Use the Width field instead.

This field allows you to choose the column by which data is primarily sorted. For example, if you have added a date column, you can choose Date from the Primary Sort drop-down and then choose Ascending (i.e. oldest to newest, least to greatest, A to Z) or Descending (i.e. newest to oldest, greatest to least, Z to A) from the Sort Direction drop-down menu.

This field allows you to choose the column that determines the secondary sort. For example, if the primary sort used the Date column, you can choose Time from the Secondary Sort drop-down and then choose Ascending (i.e. oldest to newest) or Descending (i.e. newest to oldest). Records with the same date are then sorted by Time.

A percentage used to control the size of each column. Leaving this field empty will ensure that all columns of the grid are the same size. If you do specify a percentage, ensure that the columns total to 100% (e.g., four columns could be set as 25%, 25%, 35% and 15%).

The date field in the Event Timeline component which sorts events based on date and sequence of events.

The time field in the Event Timeline component which sorts events based on date and sequence of events.

For the Event Timeline component, choose Sequence from the Timeline entity table. This is a hidden field and is used to controlled by the system to order the events.

The title for the event in the Event Timeline component.

This determines the sort order of the timeline events. Choose one of the following options:

• Most Recent - displays events in descending order. The label Most Recent is displayed at the top showing most recent events to oldest at the bottom). This is the default sort order.
• Oldest - displays events in ascending order. The Start of Timeline label is displayed at the top showing oldest to most recent at the bottom).

Determines whether or not the Caption for the field elements will be displayed in the Card List. Choose one of the following:

• True - to display the caption and the content entered in the field
• False - to display the content entered in the field without the caption.

Allows you to determine the percentage of space allotted for the field caption in the row. For example, if you enter 50, half of the space in the row will be allotted for the field caption while the other half will be allotted to field content.

Note: This is only used if Show Field Caption is set to True and is optional.

This determines which fields from the table are to be displayed in the card list. To add a field, go to the blank row at the bottom of the list.

Note: You must have a minimum of one element and a maximum of three (3) elements defined in the Card Fields Tab.

Enter a label for the element to be displayed in the Card List.

Note: This is only used if Show Field Caption is set to True.

Enter the maximum number of rows allowed for the field. Note: For a card, the minimum number or rows is 1 and maximum number of rows is 4.

Users can specify up to a 3-level sort based on the three fields displayed on the tab. If no sorting is specified, then the sequence is displayed in the order that the cards are added. Only positive integers can be entered.

If a Sort Order has been defined, choose Ascending or Descending to determine if the elements will be sorted in ascending or descending direction.

A unique identifier for a custom CSS used to restyle components within the form.

Note: The standard form has a CSS that controls the form design. This field is optional.

This field determines visibility for the Add button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Delete button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Send button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Acknowledge button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Notify button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Accept button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Submit button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.

This field determines visibility for the Mark as Final button. Choose one of the following options:

• True - to show the button at all times.
• False - to hide the button.
• Calculated - to show the button only under specific circumstances.