Why you should check the result file format in a demonstration

5 min read

For safety managers and purchasing staff introducing a breathalyzer or alcohol management system, the work often does not end with checking test results on screen. After testing, they fill in daily checklists or gather results from each location to prepare internal reports, and, if needed, compare them with existing access records. Here, the information shown on the device screen and the information in the result files exported from the device are not used in the same way.

A result file is data that takes information left after testing, such as test time, reading, and test processing status, out of the device as a table or other electronic document. Even if the product description says it has a result storage feature, whether that file fits your current tallies and reporting procedures must be checked separately. Looking at the file format in a demonstration is not a procedure for confirming whether a storage feature exists. It is a process for finding, before purchase, the parts that people would have to re-enter or interpret after purchase.

Information on screen differs from information in the file

Even if dates and readings are neatly arranged on the demonstration screen, the exported file may differ in how dates and times are recorded, whether the unit is kept with the reading, and how unfinished tests are shown. Viewing on screen is a function for looking at individual results at the site, while a file is data for gathering many results or putting them into other documents, so the criteria to check differ.

It is also hard to assume that the same file extension means the same follow-up work. Even for table-format files, the way you build tallies changes depending on whether date and time go in one cell, whether reading and unit are separated, and whether errors or retries are left blank. So rather than judging from a description that "it saves to a file," it is better to get an actual export and open it in the program you will use in operation.

First decide what information the report needs

Review the file format after first deciding what needs to be judged in the final report or checklist. If the work is only checking one location's results for the day, test time and reading may come first. If the work gathers data from several locations, information that tells which device a result came from may be needed, and if incomplete tests must also be looked at separately, how processing status is shown becomes important.

There is no need to put real employees' names or real readings into demonstration data. You can ask the supplier for hypothetical data covering the cases the site needs to tell apart, such as normal completion, incomplete test, and retry. Deciding on the necessary fields in advance lets you compare specifically what information is missing from the documents you currently use, instead of vaguely asking for a particular format.

Information to look for in the file What to see in the demonstration Why it needs checking
Test time Whether the time of the test can be told apart from the time the file was created Reduces mixing of recording bases in daily tallies
Reading and unit Whether the meaning and unit of the number can be confirmed in the file To avoid comparing readings on different bases as they are
Test processing status How completed, incomplete, and retry cases are marked Prevents blanks from being read as normal results
Device and subject linkage Whether there is device identification and the minimum identifying information the work needs Splits data by location and reduces distribution of unnecessary information

This table is not a list of fields every product must provide, but criteria for each site to judge. For example, at a place that uses only one device, device identification may be a lower priority. Conversely, at a place that gathers results from several locations, without this information the manual work of splitting data can increase.

Look all the way through the tallying process with a hypothetical case

As a hypothetical example, suppose a workplace receives morning test results as a table file and puts them into the day's checklist. The demonstration file contains several readings, but one row has a blank value with no indication of why. The fact confirmed here is that the meaning of a row without a value is hard to determine from the file alone, and this cannot be assumed to be a device error or a storage omission.

This observation leads to the problem that it is hard to decide whether to treat the blank row as not tested, a retry, or some other reason. A possible action is to request a hypothetical sample file containing normal completion, incomplete test, and retry cases, and try transferring it once to the actual checklist. The completion criterion here is not that the file opens, but a state in which the person in charge can tell what each row means, enter it into the checklist, and compare it with the time, value, and status in the original file.

Korean names, several records with the same time, and identifiers with letters at the start can also be items to test in the program you use. If the program converts identifiers to numbers or treats rows with the same time as one, distinctions in the original file can be lost. Placing your existing report template and the sample file side by side and marking the differences lets you define the processing you need more clearly than the broad question of "can it integrate?"

For unsupported fields, decide how they will be handled too

The lack of needed information in a sample file does not immediately rule out choosing the product. You can judge separately whether that information already exists in other records, whether people can enter it additionally, and whether that manual work is manageable if it repeats every day. Conversely, if the information is essential to the report's judgment and hard to supplement from other records, that field becomes a high-priority requirement in the purchasing conditions.

A screen saved as an image and a table file containing values are also hard to treat as the same feature. An image can be used for people to check content, but it may need to be re-entered when tallying many entries or transferring them to existing documents. Deciding who will put the data into which document before deciding what data to receive reduces both excessive feature demands and unexpected manual work.

Record the conditions agreed in the demonstration as purchasing criteria

After the demonstration, it is best to keep the sample file itself together with the program you opened it in and the conditions you confirmed while tallying. This lets you decide what to compare against if the file layout or display method looks different after delivery. You also need to check separately whether only the demonstrator can export files or whether actual operators can do the same work.

If you expect to re-export files or correct results, you can also set which data will be used as the final report material. Separating information that site reports absolutely need, information that can be supplemented manually, and information that is hard to handle with the current procedure helps you decide whether a standalone device is enough or a broader system configuration is needed. Only after putting the result file format into the actual workflow can you make quote requests and purchase specifications concrete enough to fit site conditions.

References

#result file format
#product demonstration
#data export
Considering our products?
We'll help you decide.