A breath analyzer is a device that displays a result based on the alcohol contained in a person's breath. Here, mouth alcohol refers to a state in which alcohol remaining in the mouth can affect the initial breath sample, unlike exhaled breath that comes from the blood through the lungs. A mouth alcohol detection feature can mean a function designed so that the device separately identifies this possible effect.
After seeing this feature name in device marketing materials, safety managers and quality or engineering staff can easily interpret a particular reading as having been "judged to be mouth alcohol." But whether a model has the feature and whether the device indicated that state in this particular test are different facts. Feature support must be confirmed in product documents, while the actual judgment and numerical result must be confirmed in the test screen, the device records, and the exported result files.
Confirm feature support against the model and version
The general name "mouth alcohol detection" alone cannot define the scope of a feature. Even among products from the same manufacturer, the indications and recorded fields provided may differ by model, firmware version, and the PC software in use. So rather than sales copy that only names the product, it is more accurate to first check the official feature name and the products it applies to in the user manual or the feature description the manufacturer provides for that model.
What to check goes beyond whether the detection feature exists. You need to look separately at whether the device shows a possible detection on screen, whether it stops the test procedure, whether it also provides a numerical result, and whether a separate status is visible in exported files too. Do not fill in behavior that is not in the published documents by guessing from examples of other models.
A numerical result and a status indication do not mean the same thing
The numerical result of a breath test is the value the device calculated and displayed for that sample. A mouth alcohol-related indication, on the other hand, may be information that reports a status concerning the sample or the test process under conditions defined by the device. Whether a status indication automatically deletes or invalidates the numerical result, or conversely whether a displayed number rules out the possibility of mouth alcohol, can only be determined by looking at that product's documents and the actual records together.
OIML R 126-1:2021 is an international recommendation covering the metrological and technical requirements for evidential quantitative breath analyzers. However, the existence of this recommendation alone does not let you conclude that a particular product provides a mouth alcohol detection feature, or that a particular message leads to a certain handling of results. International recommendations, manufacturer feature descriptions, and individual test records are materials at different levels.
| Category | Materials to check | Fact to confirm |
|---|---|---|
| Feature support | That model's user manual and version information | Whether a mouth alcohol detection feature is stated for that model |
| Judgment in this test | Test screen, test records in the device | Whether the device showed a separate status message or code at the time |
| Handling of the numerical result | Result screen and exported test file | Whether the reading was kept and whether it was saved with status information |
| Display in external systems | Version of the integration software and its screens and files | Whether the device's status information is transmitted and displayed |
The reason for the separation in the table is that it is hard to judge every fact from a single screen. For example, if an external system shows only a number, you cannot immediately tell whether the device did not indicate a status or indicated one that was not passed on during integration. You need to compare the original device records with what the external system shows, using the same test time as the reference.
Record the actual judgment in its original wording
Besides the number, test records may contain information needed to interpret the result, such as on-screen wording, status codes, the test time, and device identification. If a person rewrites the device's wording broadly as "mouth alcohol confirmed" or "test invalid," the original meaning is lost. The safe order is to keep the wording the device used exactly as it is, and then interpret what that wording means separately according to that model's documents.
Take a hypothetical case. Suppose a workplace saw both a numerical result and a separate warning message on the test screen, and only the number was saved on the management screen. The observed fact is that the device screen had two pieces of information and the management screen had only one. You cannot conclude from this that the warning was caused by a particular food, mouthwash, or drinking.
A possible action is to preserve the original wording on the device screen and the test time, and then compare them with the definition of that wording and the result handling described in that model's manual. You can then compare the device records for the same time with the fields transmitted to the management screen to find where information was lost. The completion criterion is not writing down a guess about the cause, but setting out in a reproducible way what status, numerical result, and information passed to the external system the device showed in that test.
Do not turn a detection indication into a diagnosis of a person's state
A mouth alcohol detection feature should be understood as one that deals with a status related to test quality. The fact that the device reported a certain status is not grounds for explaining what a person used or whether they actually drank. In particular, if an external system creates a "mouth effect probability score" or its own judgment wording that is not in the device records and displays it like an official result, the device's result and the operating system's interpretation become mixed.
The same distinction is needed in translation and screen design. "Detection available" may describe a feature designed to identify certain conditions, but it does not mean the cause is always distinguished in every situation. If you add buttons, icons, or status wording not found in the manufacturer's documents to resemble other products, users may mistake them for an actual device judgment.
Summarize the review with three questions
In a technical review document, first state whether "this model and version support the feature." Next, state separately whether "in this test, the device actually displayed or stored a status related to that feature." Finally, confirm "how the numerical result and status information were each kept in the device and in the integrated system." This keeps the feature description from being mixed with the judgment in an individual case.
This distinction is the minimum record structure for neither overstating the reliability of a particular reading nor arbitrarily excluding it. The feature name explains the scope of support, while the actual screens and records explain what happened in that test. Not treating the two as the same thing is the starting point for reading a mouth alcohol detection feature and actual result values accurately.
