Guru's Verification engine ensures consistency, confidence, and trust in the knowledge your organization shares. Learn more.

Setting Lab Test Clinical Ranges in GoRev

After you’ve created your test the next step is going to be setting your clinical ranges to determine positive/negative, detected/not detected with the result. GoRev has a 3 tier system for determining the verbiage on your result files and we will discuss this later in the guide but to start with you will need to enter your reference ranges for a specific analyte or test in the edit test window.

Setting up Gender Phases

To properly set up clinical ranges on a test like FSH or other tests that may be impacted by gender-specific conditions, the gender phases must be added into the system

We will go to the Lab Module, Configuration, and in the dropdown select ‘Gender Phases’.


This will open the ‘Edit Gender Phases’ window. Here we can add, edit and delete Gender Phases in the system. Click the Add New button and the New Gender Phase window opens. Simply select the Gender, enter the Phase Name and then click the Save button. If you want to edit a Phase, simply click on the row and it will open the edit Phase window.


Note: Gender Phases must be created if your test requires different result based on this parameter.

Clinical Ranges Overview

To open the Edit Test window, from the main menu select lab modules configuration and in the drop-down list select edit test.


This open the Edit Test window, then select the test that you would like to enter the clinical ranges for. Once the row is highlighted, in the bottom section of the window, click the clinical ranges tab, it will be the first tab. To add a new clinical range click the new button located on the right side of the bottom section and this will open the clinical range window.

The edit clinical range window is broken into 4 distinct sections. We’ll look at each section and the text options in each of those.


Clinical range prioritization

  • Effective date — The date at which point the clinical range becomes effective if you set the date to a future date and try to run a test sample today this clinical range will not be available for result interpretation on the test.

  • Units of measure — This allows you to specify the unit of measure specific to just this clinical range that is different from the global unit of measure set at the edit test level.

  • Lower limit — this field will impact how a result is displayed for example if you specify the lower limit of say 4.0 and the result comes back at 2.5 this will be displayed as less <4.0 on the result file.

  • Upper limit — this field will impact how a result is displayed for example if you specify an upper limit of 25.0 and the result comes back as 35.0, it will be displayed as > 25.0 on the result file.

Patient status requirements

  • Patient gender— this field allows you to restrict this critical range to specific patient sex.

  • Patient Gender Phases – this field allows you to restrict this critical range to specific patient Gender Phases.

  • Start/End Age (years, days) — these settings restrict the clinical range to the specified patient age range specifying years and days. For example, Restricting these ranges for a one-month-old would be 0 years and 0 days For the start age and 0 years and 30 days for the end age. For a test that has no upper boundary, we suggest setting the end age to 150 years.

  • Fasting hours — in this field you will specify the number of hours a patient is required to fast before the test is performed. During ordering users will specify the number of actual fasted hours if they enter a time that is less than the required range on the test the result will appear with no reference range found due to the fasting errors criteria having not been met.

Sample Collection Requirements

  • Decrease indent Collection start time and end time — these fields work similar to the age start and end time except it is applied to the actual time a specimen was collected. This is useful for a test like glucose or the time of specimen collection can impact the result ranges specified this time in military time for example midnight to 10 AM would be 00:00:00 to 10:00:00

  • Specimen type — This multi-select dropdown allows you to limit the clinical ranges by the specimen types selected in the list.

Observation Ranges

Go Rev supports a six-tier low and six-tier high set observation ranges. The first column of text boxes will include your quantitative values (numeric values). It is worth noting that the low values are inclusive meaning that they are greater than or equal to the amount entered in the textbox. An example would be if the low value that was entered was 5.00 and the result that came back from the analyzer, if 5.00, the result would fall within this range as it is equal to the lower level. The high ranges are non-inclusive and they will display the number that is the upper limit of the level. An example of this would be if your upper level is 35.01 and the test returned a value of 35.00 it would fall under the upper range.

Each range textbox has a description text box for the qualitative values you want to be shown on the result pdf. Each also has a comment textbox for each entered range. These text boxes allow you to customize with your preferred Range verbiage. The description allows you to specify more details to be visible on the result such as actions that must be taken now due to critical results.

As mentioned earlier GoRev has a three-tier system for determining verbiage that is displayed on the patient result file, the edit clinical ranges are the first tier in this system. The second tier is in the resulting design itself which is managed by your GoRev technician. We try to use this as a last case resort for determining verbiage on the patient result file as it requires a GoRev tech to make these adjustments. The third tier we are going to talk about now is back in the edit test window, override statutes.

Let's look at an example of this in use.

The Clinical Ranges are set with a Low 2 of 8.0000, and a Low of 11.50000. The normal range is 11.50000 to 13.50000. Hight is > 13.50000 to 20.0000 and anything over 20.00001 Is High 2. You will also notice that any results that are in the Low 2 range are reported as Critical Low and include a Comment with instructions to be followed. The same concept is used for High 2 results.

To better explain how the values that are set work:

  • Low values are inclusive of the floor, meaning it is less than or equal to (>=) the Low value.

  • High values are exclusive of the ceiling, meaning it is greater than (<) the High Value.


In this example, we see the Low is set to 5.000 and the High of 35.00100, anything between those values is considered Detected. Any result values below (0.00 to 4.99999) or above 35.00100 is considered Not Detected.


Override Statuses

The Override statuses can work in concert with the clinical ranges and are important when the clinical ranges are Inclusive Ranges. The left column has the possible values that a test result could fall within.

  • Allow checkbox - this is checked when the result modifications are wanted, they only go into effect when the Considered Normal dropdown is set other than the default.

  • Custom Description – This value is the overriding description to be displayed on the result.

  • Considered Normal – this dropdown is used to determine if the test returned value is what would be typically expected.

In the Edit Test window, we will set the Inclusive Ranges to the On position. Then set the Override status for the High, Low and Out of Range Custom Description to Not Detected and the Considered Normal dropdown to “Yes”. The In Range status description is ‘’Detected’ and the dropdown is set to "No".


Note: The Custom Description text can be whatever verbiage you require to be displayed on the patient result report.

GoRev Support Team

If you have any questions, concerns, or problems regarding this GoRev Tutorial, please contact the GoRev Support Team by submitting an IT Support Ticket, by phone at 1-(317)-794-3900, and/or by email at

Note: If possible, always submit an IT Support Ticket detailing any problem that you are experiencing within GoRev. This will give GoRev Support Agents access to additional information that will help expedite the resolution of your issue. If you are unsure how to submit an IT Support Ticket in GoRev, please see theIT Support Ticket Creation for assistance.

You must have Author or Collection Owner permission to create Guru Cards. Contact your team's Guru admins to use this template.