# How to configure pregnancy-specific reference ranges for a test?

**URL:** <https://talk.openelis-global.org/t/how-to-configure-pregnancy-specific-reference-ranges-for-a-test/2459>\
**Category:** Ask OpenELIS\
**Created:** [October 23, 2026, 10:59am UTC](https://talk.openelis-global.org/t/how-to-configure-pregnancy-specific-reference-ranges-for-a-test/2459 "2026-10-23T10:59:36Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bhupesh\_Gupta](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.openelis-global.org/bhupesh_gupta/32/1273_2.png) [@Bhupesh\_Gupta](https://talk.openelis-global.org/u/Bhupesh_Gupta)\
**Post date:** [October 23, 2026, 10:59am UTC](https://talk.openelis-global.org/t/how-to-configure-pregnancy-specific-reference-ranges-for-a-test/2459/1 "2026-10-23T10:59:36Z")

</div>

Hi all,

We’re using OpenELIS Global [3.2.3], integrated with our EMR via [FHIR / HL7 v2] electronic orders.

In Test Management, we can set different reference ranges for a test based on **sex** and **age**.

 ![image](https://canada1.discourse-cdn.com/flex030/uploads/openelisci/original/2X/4/4a9e8fad55aed29f9590e70cffa27c8bf27425d9.png)

We also need different ranges for **pregnant patients** (ideally per trimester) for tests like Hemoglobin, TSH, ALP and Creatinine, so that results are flagged correctly in antenatal care.

I have a few questions:

1. **Is there a built-in way to define reference ranges based on pregnancy status** (or any patient condition other than sex and age)? If so, where is it configured?

2. If not, **how are other implementations handling this?** For example:

3. If separate test versions is the usual approach, **how do you manage LOINC codes** , since both versions measure the same analyte? We match incoming EMR orders by LOINC, so duplicates are a concern for us.

4. **Where should pregnancy status be captured** : on the patient, on the sample/order, or somewhere else? Can it be received from an EMR order (e.g., as supporting information on the FHIR ServiceRequest)?

5. Is this **on the roadmap** , or would the team be open to a contribution in this area?

Any guidance or examples from existing deployments would be really helpful.