# Configuring Result Filters - Advanced

* #### [**What if my HL7 message has no OBX section?**](#selecting-a-no-test-code-1-for-microbiology-lab-type)
* [**What if I want to exclude some locations when matching with my critical result ?** ](#selecting-locations-to-exclude-for-locations)
* [**What if I want to link my result filter to a specific routing rule ?** ](#linking-my-result-filter-to-a-specific-routing-rule)
* [**What if I want to display additional fields of the test result on my dashboard?** ](#displaying-additional-field-for-critical-test-result-on-critical-test-result-dashboard)

#### Selecting a 'No Test Code (-1)' for Microbiology lab type

If a lab result appears in the NTE segment of the HL7 message and does not have a corresponding OBX segment, select the "-1" test code. This option serves as a catch-all for cases where a microbiology result lacks a specific test code. 

<figure><img src="/files/ChefTKBWA1SOJCOTMaTu" alt="" width="563"><figcaption></figcaption></figure>

#### **Selecting 'Locations to exclude' for Locations**

If a certain lab result comes from various locations , we allow our users to select 'All locations' to ensure that no result is missed. However , we understand there might still be a few exclusions hence we allow users to select locations to exclude if they have selected 'All Locations' , 'All Clinics' , 'All Wards'.&#x20;

<figure><img src="/files/QKcCmMU3hakmBMmh45f5" alt="" width="563"><figcaption></figcaption></figure>

#### **Linking my result filter to a specific routing rule** &#x20;

After we determine the criticality of a result, we will iterate through all routing rules and choose the one which is the closest match to the specialty and the location of the patient. E.g if the patient is from a from A\&E, we will select the routing rule shown below :&#x20;

<figure><img src="/files/50wnFkKd6ySuE5rnZhDO" alt="" width="563"><figcaption><p>An example of a routing rule </p></figcaption></figure>

However, if you would like to route your critical result filter via a specific routing rule, you can select the checkbox below.&#x20;

<figure><img src="/files/VuksbtowxDZOmuolgN9F" alt="" width="563"><figcaption><p>Link the relevant routing rule </p></figcaption></figure>

{% hint style="success" %}
You can continue [here](/features/routing-rules.md) if you would like a critical result to skip manual intervention. This would be useful for R1U results which do not require any action from the Contact Centre.&#x20;
{% endhint %}

#### **Displaying additional field for critical test result on** [**Critical Test Result**](broken://pages/TM1KWfSMwbdm0UgZ5mtf) **Dashboard**&#x20;

* **Display additional observation** allows you to display any additional OBX fields within the HL7 message.&#x20;
* **Display comments** allow you to display comments from the NTE segment (the first NTE segment following OBX segment) within the HL7 message.

<figure><img src="/files/oASTXPk4bSpQIZAmMjGn" alt="" width="563"><figcaption></figcaption></figure>

<figure><img src="/files/NaOKCjD7alR4lpMzvJ56" alt=""><figcaption><p>An example of the Critical Results Dashboard Result detail if 'Display comments' has been selected</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://guide.rooster.gov.sg/features/result-filters/configuring-result-filters-advanced.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.