When you gather breath alcohol test results in an app or on a PC for review, storing only the concentration value makes it hard to know what power-related message appeared on screen at the time of the test. A battery alert is not the reading itself. It is information showing the device's condition when that result was displayed and stored. DATECH's AF-40BT offers a battery alert, storage of up to 10,000 test results, and Bluetooth smartphone connectivity.
So it is best for the screens that manage results and the data you download to hold separately the concentration value, whether a battery alert was shown, whether the test result was actually displayed, and whether it was sent to the app. The product information provided gives no basis for arbitrarily correcting a reading or automatically invalidating a result because a battery alert appeared. What is needed is not changing the number, but keeping the observed information so the situation at the time can be reconstructed later.
Do not mix the reading and the battery alert in one field
Keep the reading together with the number and unit the device displayed. The AF-40BT lists display ranges for %BAC, ‰, and mg/L, so the integrated system should also keep the display unit at the time rather than storing only the number. For example, a number like 0.050 without its unit does not tell you which concentration display it is.
Show the battery alert as a separate field rather than adding it in parentheses after the reading. Attaching a readable status such as "battery alert shown" in the same row of the results list keeps the reading and the power-related message from being confused. If the device or integration feature passes on the actual warning text, that text can be kept as is as well. However, the app must not calculate and display a battery percentage that the product does not provide.
| Information to store | Example on screen or in data | Why it is kept separate |
|---|---|---|
| Test result and display unit | 0.050 %BAC | To preserve the meaning of the value the device output |
| Whether a battery alert was shown | Battery alert shown | To keep concentration values apart from power-related messages |
| Whether the result was displayed | Result displayed or no result | So an alert and a failure to obtain a test result are not treated as the same event |
| App transmission status | App transmission confirmed or transmission unconfirmed | To distinguish the device test from receipt on the smartphone |
Keep the warning readable in lists and downloads
If a warning is shown only by a small battery icon, its meaning may be lost when the list is printed or downloaded as a file. Icons can be used in the list, but a setup in which wording such as "battery alert shown" remains on the detail screen and in downloaded data is more suitable. If cases where no warning appeared are also marked "no battery alert shown," it becomes easier to review whether there was no information or whether the status value was lost in transmission.
The purpose of flagging the warning is not to conclude that the result is inaccurate. The official AF-40BT information describes the battery alert feature, but it does not set out any relationship between battery alerts and changes in particular concentration values. So attach a review flag to results with warnings, but do not lower or raise the number and record it again based on that flag.
Count battery alerts, no-result cases, and transmission gaps separately
A battery alert is an observation that the device displayed a power-related message. No result is a state in which you cannot confirm that a reading was displayed on screen, and a transmission gap is an event in which receipt of a result between the device and the app could not be confirmed. If all three are lumped together as "device fault," it becomes hard to tell whether you should look at the power condition or at the data integration.
The AF-40BT offers a dual mode for standalone and app use, and Bluetooth smartphone connectivity. A case where there was a result on the device screen during standalone use but no app record is not handled the same way as a case where the result itself could not be confirmed on the device. It is useful not to conclude a battery alert or test failure just because there is no record in the app, but to compare the device records you have with the transmission times and mark at which stage the information was lost.
In a hypothetical case, pin down the observed facts first
As a hypothetical case, suppose that after an AF-40BT test, 0.050 %BAC was stored in the app and a battery alert was shown on the device screen at the same time. The confirmed observations in this case are that the device displayed a concentration value, that there was a battery-related alert, and that the result arrived in the app. These three facts alone do not support interpreting that the battery condition raised or lowered the reading.
A possible action is to keep the battery alert status on that result row and check the response to battery alerts set out in the user manual. If the batteries are then replaced, record the time of replacement and the new test results obtained after replacement separately, in time order. The completion criterion in this case is not correcting the earlier number, but a state in which the reading, display unit, battery alert, whether the result was displayed, and app transmission status are all linked to the single result.
Replacing batteries does not change the assessment of earlier readings
The AF-40BT's power source is listed as two AAA alkaline batteries. If you replaced the batteries, recording after which result the replacement took place lets you review in time order when the power-related message appeared and the results that followed. However, the fact of replacement alone does not allow you to automatically delete earlier results, or to mark the first test after replacement as a result that confirms device performance.
When battery alerts recur, rather than just totaling the number of alerts, look at when they recurred together with the display and transmission status of each result. Data kept this way does not hide warnings, yet keeps warnings and readings from being treated as meaning the same thing. The key is to manage battery alerts not as grounds for overwriting results, but as separate information explaining the device's condition at the time of the test.