Differences

This shows you the differences between two versions of the page.

--- cold_chain_equipment:fridgetags_integration [2025/05/20 10:27] – [20.04. Berlinger Fridge Tag and Q-Tag Integration] Adrian Boone
+++ cold_chain_equipment:fridgetags_integration [2025/05/20 10:32] (current) – [20.04. Berlinger Fridge Tag and Q-Tag Integration] Adrian Boone
@@ Line 10: / Line 10: @@
 If the Fridge Tag records regular temperature logs (e.g. the 2L), then mSupply can use that information to more accurately work out the breach start & end times for cumulative breaches. It can also use that information to work out //consecutive// breaches using the same breach detection parameters as for cumulative breaches (i.e. trigger threshold and temperature range). To differentiate between breach types, cumulative breaches are labelled with an extra "(*)".
-As of version 7.5, mSupply also supports Berlinger Q-Tags. These operate in the same way as Fridge Tags, but they record breach start and end time explicitly and they also record consecutive breaches as well as cumulative ones, so mSupply doesn't have to work anything out, apart from to consolidate breaches which span multiple days. Note though that not all Q-Tags record regular temperature logs, so the information available from them is limited to breaches only and daily max/min temperatures.
+As of version 7.5, mSupply also supports Berlinger Q-Tags. These operate in the same way as Fridge Tags, but they record breach start and end time explicitly and they also record consecutive breaches as well as cumulative ones, so mSupply has only minimal processing to  do. Note though that not all Q-Tags record regular temperature logs, so the information available from them is limited to breaches only and daily max/min temperatures.