Report Field Descriptions

Whether creating a bar chart, simple list or crosstab report, the fields available for reporting come from the RL6 taxonomy. This consists of two types of fields: “standard fields” are available for use on a form and in reports while “virtual fields” may only be used when creating reports. Standard fields are used to capture information from front-line staff and file managers through the submission and management forms.

Note: The entry limit for Report Designer fields is 32310 characters.

The fields available for selection for the y-axis are filtered by other report settings. When None, Min, Max, Avg or Sum is selected in the Aggregate Function field, for example, the Data Values only contain numeric fields; when Count is selected, all fields are available. See Locating Fields for details on using the field picker.

Virtual fields perform calculations between two or more standard fields so that the result may be included in a report. Virtual fields can only be created by RLDatix. The table below describes the virtual fields that are available for use in reports:

Note: Where appropriate, the field Name used in the calculation is shown. This is not the field Caption, which is displayed on the form and can be modified. In the table below, it follows this format TableName=>FieldName (e.g., IncidentSee Event=>EnteredDate). Contact your RL6 AdministratorThe person in charge of managing and maintaining RL6. if you need to know what a particular field’s caption is.

Table 2-15: Understanding Virtual Fields
Virtual Field	Module	Description
Age	Claims Feedback Risk	There are two Age fields in the taxonomy. One that is used on the form to calculate the age of the individual at the time of the incident and displays the result in the following formats: `new born`, `5 days`, `2 months 3 days`, and `25 years`. The other age field is a virtual field that converts the age at the time of the incident into a year; for example, `new born`, `5 days` and `2 months 3 days` become `0` while `25 years` becomes `25`. Since the virtual field is a purely numeric field, it can be used for aggregation in reports. Note: To ensure you select the correct age field, look in the browser’s status bar as you hover over Age in the list. You should see `#F2345` at the end of the URLThe Uniform Resource Locator (URL) is the address of an internet resource, such as a web page. It includes the protocol used to access the page, such as HTTP. A sample URL is http://www.rlsolutions.com..
Calc Communicated Day of Week	Feedback	The day of week the hospital was informed of the issue (`Feedback=>DateNotified`).
Calc Dynamic Person Age	Claims Feedback Risk	Person’s age in Years (if less than 1 year, then it will be listed in months) based on today's date (taken from the server).
Calc Entered Day of Week	Feedback Risk	The day of week a user first started filling the event details into submission form (`Incident` or `Feedback=>EnteredDate`).
Calc Entered Time - Aggregate	Claims Feedback Risk	Entered time (`ClaimFile`, `Incident` or `Feedback=>EnteredTime` or `IncidentTime`) set in a way such that you can use this to trend (aggregate).
Calc Entry Days - Communicated	Feedback	How long it took the user to start entering the issue (`Feedback=>EnteredDate`) after the patient communicated the issue (`Feedback=>DateNotified`) to the hospital.
Calc Entry Days - Entered	Risk	How long it took the staff to start entering the event into the system (`Incident=>EnteredDate`) after the event occurred (`Incident=>EventDate`).
Calc Entry Days - Submitted	Risk	How long it took the staff to actually submit the event into the system (stored in the database) after the event occurred (`Incident=>EventDate`).
Calc Entry Days - Submitted	Feedback	How long it took the user to actually click the submit button (stored in the database) after the patient communicated the issue (`Feedback=>DateNotified`) to the hospital.
Calc EventA patient or employee related occurrence which is recorded in paper or electronic format. Once recorded, an event file is reviewed by a file manager who may involve other individuals (e.g. using tasks and follow-ups features) to help investigate and resolve the event. Day of Week	Risk	The actual day of the week (i.e., Monday) the event occurred (`Incident=>EventDate`).
Calc Event Time - Aggregate	Claims Risk	Event time (`ClaimFile` or `Incident=>EventTime`) set in a way such that you can use this to trend (aggregate).
Calc File Close Days - Entered	Risk	The number of days between when the file was initially entered in the system (`Incident=>EnteredDate`) to when the file state was changed to closed (stored in the database). If the file is reopened and then closed, it takes the last closed date posted.
Calc File Close Days - Event	Risk	The number of days between when the event occurred (`Incident=>EventDate`) to when the file state was changed to closed (stored in the database). If the file is reopened and then closed, it takes the last closed date posted.
Calc File Close Days - Submitted	Risk	The number of days between when the file was submitted to the system to when the file state was changed to closed (these values are both stored in the database). If the file is reopened and then closed, it takes the last closed date posted.
Calc File Open Days - Communicated	Feedback	The number of days between today (taken from the server) and the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc File Open Days - Entered	Claims Feedback Risk	The number of days between today (taken from the server) and when the staff started entering the file into the system (stored in the database).
Calc File Open Days - Event	Risk	The number of days between today (taken from the server) and the date the event occurred (`Incident=>EventDate`).
Calc File Open Days - Issue	Feedback	The number of between today (taken from the server) and the day the issue occurred (`Feedback=>IncidentDate`).
Calc File Open Days - Submitted	Claims Feedback Risk	The number of days between the current date (taken from the server) and the date the file was officially submitted into the system (stored in the database).
Calc File Resolution Days - Communicated	Feedback	How many days it took for the file to be resolved (`Feedback=>ResolutionDate`) from the day the hospital was informed of the issue (`Feedback=>DateNotified`).
Calc File Resolution Days - Entered	Feedback	How many days it took for the file to be resolved (stored in the database when the file is closed) from the day the file was first entered into the system (`Feedback=>EnteredDate`).
Calc File Resolution Days - Issue	Feedback	How many days it took for the file to be resolved (stored in the database when the file is closed) from the day the issue occurred (`Feedback=>IncidentDate`).
Calc File Resolution Days - Submitted	Feedback	How many days it took for the file to be resolved from the day the file was officially submitted into the system (both values are stored in the database).
Calc First Follow-up - Communicated	Feedback	How many days between the first follow-up has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc File Resolution Days - Issue	Feedback	The number of days it took for the file to be resolved from the day the issue occurred
Calc File Resolution Days - Submitted	Feedback	The number of days it took for the file to be resolved from the day the file was officially submitted into the system
Calc First Follow-up - Entered	Claims Feedback Risk	The number of days between when the first follow-up has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`ClaimFile`, `Incident` or `Feedback=>EnteredDate`).
Calc First Follow-up - Event	Risk	The number of days between when the first follow-up was added to the file (`FollowUps=>EnteredDate`) since the event occurred (`Incident=>EventDate`).
Calc First Follow-up - Review (Communicated)	Feedback	How many days between the first “review” follow-up type has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc First Follow-up - Review (Entered)	Feedback Risk	The number of days between when the first “review” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`Incident=>EnteredDate`).
Calc First Follow-up - Review (Event)	Risk	The number of days between when the first “review” follow-up type has been added to the file (`FollowUps=>EnteredDate`) since the event occurred (`Incident=>EventDate`).
Calc First Follow-up - Review (Submitted)	Feedback Risk	The number of days between when the first “review” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc First Follow-up - SignOff (Communicated)	Feedback	How many days between the first “signoff” follow-up type has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc First Follow-up - SignOff (Entered)	Feedback Risk	The number of days between when the first “signoff” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`Incident` or `Feedback=>EnteredDate`).
Calc First Follow-up - SignOff (Event)	Risk	The number of days between when the first “signoff” follow-up type has been added to the file (`FollowUps=>EnteredDate`) since the event occurred (`Incident=>EventDate`).
Calc First Follow-up - SignOff (Submitted)	Feedback Risk	The number of days between when the first “signoff” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc First Follow-up - Submitted	Claims Feedback Risk	The number of days between when the first follow-up has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the system (stored in the database).
Calc First Follow-up - Work done on file (Communicated)	Feedback	How many days between the first “Work done on file” follow-up type has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc First Follow-up - Work done on file (Entered)	Claims Feedback Risk	The number of days between when the first “work done on file” follow-up type has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`ClaimFile`, `Incident` or `Feedback=>EnteredDate`).
Calc First Follow-up - Work done on file (Event)	Risk	The number of days between when the first “work done on file” follow-up type has been added to the file (`FollowUps=>EnteredDate`) since the event occurred (`Incident=>EventDate`).
Calc First Follow-up - Work done on file (Submitted)	Claims Feedback Risk	The number of days between when the first “work done on file” follow-up type has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc Issue Communicated Days	Feedback	The number of days that transpired between the date of the issue (`Feedback=>IncidentDate`) and the notification of the hospital (`Feedback=>DateNotified`).
Calc Issue Day of Week	Feedback	The day of week upon which the issue occurred (`Feedback=>IncidentDate`).
Calc Last Action - Communicated	Feedback	The number of days between the last modification to the file (stored in the database) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc Last Action - Entered	Claims Feedback Risk	The number of days it has been since a modification has been made to the file (stored in the database) since the event was entered in the system (`ClaimFile`, `Incident` or `Feedback=>EnteredDate`).
Calc Last Action - Event	Risk	The number of days it has been since a modification has been made to the file (stored in the database) since the event date (`Incident=>EventDate`).
Calc Last Action - Submitted	Claims Feedback Risk	The number of days it has been since a modification has been made to the file since the file was officially submitted to the system (both values are stored in the database).
Calc Last Follow-up - Communicated	Feedback	How many days between the last follow-up has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc Last Follow-up - Entered	Claims Feedback Risk	The number of days between when the last follow-up was been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`ClaimFile`, `Incident` or `Feedback=>EnteredDate`).
Calc Last Follow-up - Event	Risk	The number of days between when the last follow-up has been added to the file (`FollowUps=>EnteredDate`) since the day the event occurred (`Incident=>EventDate`).
Calc Last Follow-up - Review (Communicated)	Feedback	How many days between the last “review” follow-up type has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc Last Follow-up - Review (Entered)	Feedback Risk	The number of days between when the last “review” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`Incident=>EnteredDate`).
Calc Last Follow-up - Review (Event)	Risk	The number of days between when the last “review” follow-up type has been added to the file (`FollowUps=>EnteredDate`) since the day the event occurred(`Incident=>EventDate`).
Calc Last Follow-up - Review (Submitted)	Feedback Risk	The number of days between when the last “review” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc Last Follow-up - SignOff (Communicated)	Feedback	How many days between the last “signoff” follow-up type has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc Last Follow-up - SignOff (Entered)	Feedback Risk	The number of days between when the last “signoff” follow-up type has been added to the file (`FollowUps or FeedbackFollowUps=>EnteredDate`) since the day it was entered in the system (`Incident=>EnteredDate`).
Calc Last Follow-up - SignOff (Event)	Risk	The number of days between when the last “signoff” follow-up type has been added to the file (`FollowUps=>EnteredDate`) since the day the event occurred (`Incident=>EventDate`).
Calc Last Follow-up - SignOff (Submitted)	Feedback Risk	The number of days between when the last “signoff” follow-up type has been added to the file (`FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc Last Follow-up - Submitted	Claims Feedback Risk	The number of days between when the last follow-up has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc Last Follow-up - Work done on file (Communicated)	Feedback	How many days between the last “Work done on file” follow-up type has been added to the file (`FeedbackFollowups=>FollowupDate`) since the day it was communicated to the hospital (`Feedback=>DateNotified`).
Calc Last Follow-up - Work Done on file (Entered)	Claims Feedback Risk	The number of days between when the last “work done on file” follow-up type has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was entered in the system (`ClaimFile`, `Incident` or `Feedback=>EnteredDate`).
Calc Last Follow-up - Work Done on file (Event)	Risk	The number of days between when the last “work done on file” follow-up type has been added to the file (`FollowUps=>EnteredDate`) since the day the event occurred (`Incident=>EventDate`).
Calc Last Follow-up - Work Done on file (Submitted)	Claims Feedback Risk	The number of days between when the last “work done on file” follow-up type has been added to the file (`ClaimFollowups`, `FollowUps` or `FeedbackFollowups=>EnteredDate`) since the day it was officially submitted to the application (stored in the database).
Calc Static Person Age	Claims Feedback Risk	Person’s age in Years (if less than 1 year, then it will be listed in months) based on incident date (`PersonAffected=>Dob - [ClaimFile`, `Incident` or `Feedback]=>EventDate`).
Calc Submitted Date	Claims Feedback Risk	The day the user clicked the submit button to submit the file in to the system (stored in the database).
Calc Submitted Day of Week	Feedback Risk	The day of week the file was actually submitted into the system (stored in the database).
Calc Submitted Time - Aggregate	Claims Feedback Risk	Submitted time (which is stored in the database) set in a way such that you can use this to trend (aggregate).
Task assigned to	Claims Feedback Risk	This field displays the first and last name of the task owner. Use this field instead of the Task Owner Name field, which displays the user’s Primary KeyA unique number that identifies a record in a database. RL6:Claims files can have the same claim number, for example, and the primary key is used to differentiate between the two files. (PK) value instead (e.g., `569` would appear of the 569th user created in the system).