Added new "out_of_bounds_blood_glucose" tag to Inform API

On 06/29/2021 the following "tags" were added to the Inform API:

"metrics": [
                {
                    "type": "blood_glucose",
                    "origin": "device",
                    "unit": "mg/dL",
                    "value": 15.0
                }
            ],
"tags": [
                {
                    "name": "out_of_bounds_blood_glucose",
                    "value": "low"
                },
            ],

"metrics": [
                {
                    "type": "blood_glucose",
                    "origin": "device",
                    "unit": "mg/dL",
                    "value": 750.0
                }
            ],
"tags": [
                {
                    "name": "out_of_bounds_blood_glucose",
                    "value": "high"
                },
            ],

The out_of_bounds_blood_glucose tag may be used if you want to display Hi/High or Lo/Low values instead of the actual blood glucose value for measurements that have a blood glucose value that's outside of the general operating ranges of most blood glucose meters on the market. Bear in mind, many glucose meters will show the text "High" or "Low" to the end user on the meter screen when an out of bounds reading value occurs.

Out of bounds ranges:

• When blood_glucose < 20 mg/dL or 1.1 mmol/L, then out_of_bounds_blood_glucose = "low"
• When blood_glucose > 600 mg/dL or 33.3 mmol/L, then out_of_bounds_blood_glucose = "high"

If the meter reports a glucose value to Validic, then the blood_glucose metric will contain the reported blood glucose value.

These "out of bounds" readings may be indicative of a problem with the meter, the testing supplies, or the meter's calibration. It's also possible that these readings are legitimate blood glucose values for the user. Therefore, we encourage you to research the possible causes of out of bounds readings to determine whether you want to show these glucose values to the end user or use such values in any analytics or calculations within your platform.

📘

As a reminder...

We use tags to provide contextual information to use in diagnostics, data migrations, etc. Generally speaking, it is not something you need to use unless we tell you to. The value of tags can vary across integrations, and the data is not overly structured or defined.