RMS Report Validation

rms report Validation

rms report Validation

Table of Contents

TOC \o "1-3" \h \z \u Table of Contents PAGEREF _Toc75760748 \h 1

RMS Report Feature PAGEREF _Toc75760749 \h 2

RMS Report Validation PAGEREF _Toc75760750 \h 2

Rule Examples PAGEREF _Toc75760751 \h 4

RMS Report Feature

The Report Validation feature in RMS Entry is a set of data entry control rules which are applied to incident reports. These rules are determined by the agency and then configured by EIS. This automated quality control check may help the agency ensure consistent, accurate data entry. Currently, this feature is only available in RMS Entry of Incident Reports and JMS Booking and Release records. This document addresses the RMS use of the feature.

RMS Report Validation

Report Validation rules should not be confused with State Reporting Validation rules which are imbedded in the program. EIS RMS Entry application automatically runs each qualifying report against a specific set of State Reporting rules and returns the appropriate response on the report complete page. The Report Validation feature will not interfere with this process and is meant to augment the agency’s ability to perform quality checks on data entry.

Report Validation is displayed on the report complete page. The grid displays the following:

Module: In RMS, this will always be CASE

Item: Tree item pertaining to the rule

Rule: Description of the rule being enforced

Results: Displays the results of the validation check against the specific rule

Status: Displays the status of Passed or Error letting the user know if further correction/entry is required

ERROR: Based upon configuration an Error may either be a hard stop, must be fixed for the Report Complete checkbox to be accessible OR a warning which will allow a user to complete a report with the error warning. Errors display red in color.

PASSED: When a rule has found to comply and the status is passed there are two configuration options available. The first is to display the status in green in the Report Validation grid. The other option is to hide the status, if not displayed then the user may assume a passed status. This is agency definable and will be configured by EIS as requested.

Rule Examples

Many different types of rules can be enforced within the Report Validation feature. The below is a list of samples. It is not all inclusive.

If the Name Involvement indicates an arrest, then there must be an arrest page.

If an arrest screen has been completed, then at least one charge must be added.

If a specific UDF (additional information) box has been checked then a form must be completed. Such as a UDF checkbox labeled Use of Force is checked therefore the Use of Force form under the FORMS button must be completed and published to the media repository.

If a specific report type is chosen, such as a sex crime or burglary, then the checkbox screen must be completed.

If a specific report type is used, such as sex crime or rape, display warning to make non-disclosure if applicable.

Again, these are just a few examples of rules that may be applied and each rule may either be a firm error or a warning. Most often local mandatory reporting drives the rules to be enforced at the agency level. Contact EIS support or your project manager if you have questions about specific rules.

Source: RMS Report Validation.docx