This report displays loss run totals for files that use transaction splits by Policy and by Party. It includes data from new, in-progress, and closed files for all dates and scopes, where Party RoleAn attribute assigned to your user profile that determines the pages and functionality to which you have access in RL6. is not equal to "Claimant".

This report displays loss run information when transactions are split by Claim Policy Items. It includes data from new, in-progress, and closed files for all dates.

This report displays all transactions that were split by Party Involved. It includes data from new, in-progress, and closed files for all dates and scopes, where Party Role is not equal to "Claimant".

This report displays all transactions in a file that were split by Party and Policy. It includes data from new, in-progress, and closed files for all dates and scopes, where Party Role is not equal to "Claimant".

This report displays all transactions in a claims file whether or not transaction splits were used. It includes data from new, in-progress, and closed files for all dates and scopes, where Party Role is not equal to "Claimant".

This report displays all transactions in a file that were split by Claim Policy Items. It includes data from new, in-progress, and closed files for all dates and scopes.

This report displays the total number of claims files by incident type. Each column represents a different General IncidentSee Event Type. It includes data from new, in-progress, and closed files for all dates and scopes that have a General Incident Type entered and whose Status of Claim field is equal to "Actual".

This report displays claims approaching statute of limitations for this fiscal quarter. It includes data from new and in-progress files of all scopes from the current fiscal quarter.

This report shows claims by status (i.e. actual or potential) for this fiscal year. It includes data from new, in-progress, and closed files of all scopes from the current fiscal year.

This report displays claims by co-defendent parties for this fiscal year. It includes data from new, in-progress, and closed files of all scopes, where Party Role is equal to "Defendant" or "Co Defendant" and Type of Claim is equal to "Professional Liability Claim / Medical Malpractice" or "General Liability Claim".

This report displays losses in a simplified table. It includes data from new, in-progress, and closed files for all dates and scopes.

This report displays total cost amount for the Legal fees transaction type. It includes data from new, in-progress, and closed files for all dates and scopes, in which Transaction Type contains "legal".

This report displays loss run information when transactions are split by Party Involved. It includes data from new, in-progress, and closed files for all dates and scopes, in which Party Role is not equal to "Claimant".

This report uses a formula that takes the expenses paid total as the numerator and divides it by the expense reserve total as the denominator. The result represents a percentage of what was spent versus reserved to give you an accuracy rating on your reserving practices. Some organizations are aiming to have this within 80%-120%.

This report includes data from new, in-progress, and closed files of from the current calendar year, where the Calc Expense Reserve Accuracy value is greater than "0".

This report uses a formula that takes the indemnity paid total as the numerator and divides it by the indemnity reserve total as the denominator. The result displayed in the bar chart represents a percentage of what was spent versus reserved to give you an accuracy rating on your reserving practices. Some organizations are aiming to have this within 80%-120%.

This report includes data from new, in-progress, and closed files from this calendar year, where the Calc Indemnity Reserve Accuracy value is greater than "0".

Claim Lag is calculated by the difference between the incident date and the Claim Date. The Bubble chart will display claim lag as the height of the bubble and will compare it against the Claim Severity, which is represented by the size of the bubble. Those two variables are compared against Trend Month so that it can be seen whether the lag influenced the payouts and if that has changed over time.

This report includes data from new, in-progress, and closed files from this calendar year.

This report displays how many peer review files there are of each review type. It can help users distinguish the different types of peer reviews created and being used in the system. This report includes data from files of all dates and scopes that are new , in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This is a volume report that groups files by their area of quality concern. It can help users identify the various reasons why peer reviews are being conducted in an organization.

This report includes data from files of all dates and scopes that are new , in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This is a volume report that displays how many peer review files there are by committee. It can help users discern committees that are particularly underrepresented, or overrepresented, in the peer review process, as a launching point to further analysis.

This report includes data from files of all dates and scopes that are new , in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This report displays how many peer review files there are by referral source (i.e., front-line, nursing, physician, etc). Upon drilling down into the details of the report, a user can follow-up with the person or area that brought the issue that prompted the review to attention.

This report includes data from files of all dates and scopes that are new , in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This report is a listing of files, grouped by provider. It lists key file details for each provider, and can be used for credentialing purposes to get a picture of physician performance based on a provider's history of reviews.

This report includes data from files of all scopes from the past year that are new, in-progress, or closed, and that have a Review ID entered; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This report is a listing of files with their action history, grouped by provider. Actions are items that are either assigned post-review as part of a plan to address the area of concern directly, or during the review to aid in the investigation of the file itself. Therefore, this report can give an idea of the concrete actions planned and assigned with regard to files.

This report includes data from files of all scopes from the past year that are new, in-progress, or closed, and that have an Actions ID entered; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This report is similar to Actions by provider, but lists only open actions. It can help to identify providers that are not completing their actions, and to ensure assigned work is eventually completed.

This report includes data from files of all scopes from the past year that are new, in-progress, or closed, and that have an Actions ID entered; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This report is a count of files grouped reviewer. It can help to identify over-utilized, as well as under-utilized, review resources. It includes data from files of all dates and scopes that are new, in-progress, or closed, and whose File Access Level is "Reviewer"; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This is a volume report that groups files by provider specialty. It identifies the volume of peer reviews being undertaken by specialty (which is often correlated to committee). Therefore, it can reveal which specialty areas are most active in the peer review process and which are least, findings that can launch further analysis.

This report includes data from files of all dates and scopes that are new, in-progress, or closed, and whose File Access Level is "Provider"; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This is a volume report that groups files by review specialty. It is similar to the Files by Provider Specialty report, because reviews are usually conducted within specialty, but can also help to identify outliers to this rule, findings that can launch further analysis.

This report includes data from files of all dates and scopes that are new, in-progress, or closed, and whose File Access Level is "Reviewer"; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This is a volume report which groups providers by the specialties of peer review recipients. This report gives you an idea of how many providers have been reviewed from each specialty.

This report includes data from files of all dates and scopes that are new, in-progress, or closed, and whose File Access Level is "Provider"; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This is a volume report of reviewers, not files, grouped by the specialties of peer reviewers. Similar to Providers by Specialty, it displays how many reviewers there are for each specialty. Reviewers who are listed on multiple files are only counted once.

This report includes data from files of all dates and scopes that are new, in-progress, or closed, and whose File Access Level is "Reviewer"; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This volume report groups reviews by provider name. It can be used to see the number of specific reviews each provider has.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

Similar to Reviews by Provider, this volume report counts reviews instead of files. It groups them by reviewer, and can be used to see the number of specific reviews each reviewer conducted.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

This volume report counts all reviews, grouped by care rating field, and can be used as a launching point for further analysis in identifying current or potential issues of care.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

Similar to Reviews by Care Rating, this volume report includes all reviews, grouped by behavior rating, and can also be used as a launching point for further analysis in identifying current or potential issues in behavior.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

This volume report groups reviews by documentation issues, and can be used as a launching point for further analysis in identifying documentation concerns.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

This volume report groups reviews by care issues, and can be used as a launching point for further analysis of what care issues are predominant in the peer review process.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

This volume report groups reviews by contributing factors, and can be used as a launching point for further analysis of the contributing factors leading up to a peer review.

This report includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

This volume report groups reviews by exemplary findings. It includes data from files of all dates and scopes that are new, in-progress, or closed; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed". It also excludes any file with a Status Description of "Cancelled".

This volume report gives a glimpse into what kind of actions are being assigned to providers as a result of the peer review files that are being created, based on the configurable list of actions.

This report includes data from files of all dates and scopes that are new, in-progress, or closed and have a deadline; it excludes closed files whose Peer Review Status is equal to "Duplicate", "Insufficient Info", "Invalid", and "No longer needed".

This report relies upon the end user scope - it is meant to target the incomplete files of all those who report to the end user. This report is useful in keeping tabs on files that have yet to be submitted. It includes all incomplete files of all scopes; the default date range of the report includes files from the past three months.

This report targets a popular concern for hospitals, which are falls on their premises. This report helps to isolate and specify fall sources - for example, equipment, infrastructure, etc.

This report includes files of all scopes whose event dates are within the past month, and whose file states are equal to new, in-progress, or closed.

This volume report groups falls into their reported severity, and helps users to ascertain the distribution of falls across the severity spectrum - from no-harm to catastrophic, etc.

This report includes files of all scopes whose event dates are from the past three months, Injury Incurred value is equal to "Yes", General Event Type is equal to "Fall", and file state is new, in-progress, or closed.

This report helps users ascertain to what degree medication contributed to a fall, specifically isolating adverse drug reactions (ADRs). It is useful for pharmacy personnel who want to know how many incidents are recorded with respect to medications.

This report includes files of all scopes whose event dates are within the past three months, and whose General Event Type is equal to "Medication/Fluid", "Adverse Drug Reaction", or Medication contributed to fall? is equal to "Yes". It includes new, in-progress, or closed files.

This report provides of list of policies which have been documented as contributing factors to adverse events. As well, the report shows the policy by ID and title, the next review date, and the reason provided.

Note: This report is used by organizations with a PolicyStat integration and have forms configured to capture contributing polices.

This reports helps monitor files for files that have "fallen off the radar". Managers interested in maintaining compliance to organization policies around timely resolution will find this report useful. This report supplements the “No Activity” alert.

This report includes files from all scopes whose Entered Date is within the past three months, and whose File State is equal to new or in-progress.

This report provides a full listing of active files, along with their key details, such as location, event date, and narrative. It includes files from all scopes whose Entered Date is within the past three months, and whose File State is equal to new or in-progress.

This report gives a glimpse into the most frequently used severity ratings that users report risks as having. It provides a complement to the actual severity that was eventually assigned to the risk. It includes files from all scopes whose Event Date is within the past three months, and whose File State is equal to "New", "In-Progress", or "Closed".

This report provides a summary of the interfacing file submitted to the National Database of Nursing Quality Indicators (NDNQI) for benchmarking, statistics, etc. It includes files of all scopes whose Event Date is within the past three months, General Event Type is equal to "Fall", and File State is equal to "New", "In-Progress" or "Closed".

This report lists a summary of first and subsequent responses for open files. Managers can use this report to examine compliance to organization workflows. It is grouped by files within departments.

This report includes files of all scopes whose Entered Date is within the past three months, and File State is equal to "New" or "In-Progress".

This volume report shows the distribution of files across different event types. It can help users to isolate specific problem areas to further address within their scope. This report includes files of all scopes whose Event Date is within the previous calendar month, and File State is equal to "New", "In-Progress", or File State is equal to "Closed".

This volume report groups falls by different organization “slices”, or organizationally-defined units. It can pinpoint which departments are more prone to falls within a particular time frame, and, for example, where to concentrate an initiative that would address how to safeguard against falls for an organization.

This report includes files of all scopes from the previous calendar month whose General Event Type is equal to "Fall", and File State is equal to "New", "In-Progress", or "Closed".

This report provides a simplified view of incomplete files for File Managers, whose details can provide a template for an Info Center view. It includes files of all scopes whose Event Date is within the previous calendar month and File State is equal to "Incomplete".

Similar to All Incomplete Files (File Managers), this report provides a simplified view of the incomplete files within a Risk Manager's purview, grouped by department. It includes files of all scopes whose Event Date is within the previous calendar month and File State is equal to "Incomplete".

This report is similar to the OSHA 300 report, but includes a heightened level of narrative/description. It includes new, in-progress, and closed files whose General Event Type equals "Employee", and whose OSHA Recordable field equals "Yes".

This report generates information concerning incidents that affect employees, using a template distributed by OSHA for OSHA audit (hard copy). It includes new, in-progress, or closed files whose General Event Type equals "Employee" and whose OSHA Recordable? field equals "Yes".

This report is a summary of the OSHA 300 report. It includes files that are new, in-progress, or closed, whose General Event Type equals "Employee", and whose OSHA Recordable? field equals "Yes".

This is a volume report which groups files based on date range categories that indicate how long the files have been open. The date ranges are represented as bars along the x-axis. For organizations that have policies or SLAs on addressing grievances in a timely manner, this report can identify the volume of files in compromising status.

This report includes files of all scopes whose Entered Date is within the last three months, and File State is equal to "New" or "In-Progress".

This is a volume report which groups files by feedback classification, where each bar represent a different feedback classification type. Hovering over and clicking on a bar enables further analysis of the files that contain the particular feedback type.

This report includes files of all scopes whose Date is within the past three months, and File State is equal to "New", "In-Progress", or "Closed".

This report captures the distribution of feedback types by “organizational slices”, or the units by which an organization is divided. It gives a summary of the feedback classification types that are prevalent in an organization's operating units - in this case, Site and Care Service Area.

This report includes files of all scopes whose Date is within the past three months, and File State is equal to "New", "In-Progress", or "Closed".

This report lists open files and key details about each file's follow-up tasks, giving managers a sense of how users are interacting with the currently open file.

This report includes files of all scopes whose Date is within the past three months, and File State is equal to "New" or "In-Progress".

This report lists closed files along with key details about each file's past follow-up tasks. This report may help users obtain insights into the resolutions for closed files according to the feedback type documented on file, enabling them to identify patterns relating follow-up tasks and resolutions. It includes files of all scopes whose Entered Date is within the last three months and File State is equal to "Closed".

This report shows both a volume report of feedback classification types, and a distribution of person affected types via the stacked bars. "Person Affected" refers to the person involved in the feedback rather than the person giving the feedback (though they may be the same); though the terminology may be organization-specific, examples of persons affected are inpatients, outpatients, volunteers, etc.

This report includes files of all scopes whose Entered Date is within the last three months, and File State is equal to "New", "In-Progress", or "Closed".

This report displays the distribution of feedback throughout the calendar year, enabling users to easily identify spikes and declines in feedback volume per month. It includes files of all scopes whose Date is within the current calendar year, and File State is equal to "New", "In-Progress", or "Closed".

This report lists all feedback files in which a staff member has been recorded as being involved. The report is grouped by the involved staff member name, offering a means to isolate and identify retraining and performance improvement programs.

This report includes files from the current calendar year that are new, in-progress, or closed, whose Person Involved field is filled out, and whose What is this issue about? field equals "Person".

This report shows the volume that is distributed among feedback categories (i.e., Accessibility, Safety, Dietary, Financial, etc) but since it doesn't distinguish between feedback types (i.e., Complaint, Compliment, etc). It is important to note that the displayed qualifiers may be for both positive and other types of feedback.

This report includes files from the current calendar year whose File State equals "New", "In-Progress", or "Closed".

This report, grouped by file ID, outlines key points in the event a user is investigating, i.e., admission, transfer, procedure, etc. It enables users to pull out the timeline in a concise fashion into a printable report.

This report includes files of all scopes within this calendar year whose File State is equal to "New", "In-Progress", or "Closed".

This report, grouped by file, is a summary of the Investigation and Analysis fields for each investigation item. It includes files of all scopes from the current calendar year whose File State is equal to "New", "In-Progress", or "Closed".

This report groups root causes according to what they're related to - it summarizes the Causes and Plan of Action tab in RCA management form. Every field on this tab will be represented in this report.

This report includes files of all scopes from the current calendar year whose File State is equal to "New", "In-Progress", or "Closed".

This report, grouped by department and assignee, displays Root Cause action items. It may enable a department to determine whose action it is to address a root cause.

This report includes open files of all scopes and dates that are open.

This volume report shows the proportion of times a category (e.g., communication, environmental, etc.) is selected for an investigation item that has been marked as a Root Cause for the current fiscal quarter. It includes data from new, in-progress, and closed files.

This report includes data from files that are new, in-progress, or closed, and contain a Root cause entered within the current fiscal quarter.

A volume report that shows which Care/Service Areas have events that result in RCA investigations for the current calendar year. The Care/Service Area is sent from the adverse event file when the RCA is created or is manually entered. It includes data from files of all scopes from the current calendar year that are new, in-progress, and closed.

A volume report that counts the number of actions and groups them by Action Type for the current calendar quarter. This provides an idea of the kind of actions that are most frequently assigned as part of the action plans designed to prevent adverse event from happening in the future. It includes data from new, in-progress, and closed files.

This report lists the number of times a participant was absent from a huddle during the current calendar year.

This report lists all the Equipment/Supply Issues that were documented in huddles from the last 30 days.

This report lists all the scheduled huddles that were missed during the current calendar year.

This report lists all the Operational Issues that were documented in huddles from the last 30 days.

This report lists all the patients that were added to the watchlist in a huddle from the last 7 days.

This report lists all users that have been recognized during a huddle from the last month.

This report lists all the Equipment/Supply Issues that were documented in huddles from the last 30 days.

This report lists all the incomplete tasks from all huddles.