TGV guide · Performance
TGV PF02: latency tolerance
TGV control PF02 asks the vendor to document the maximum latency the PST can tolerate without losing communication or data, a critical point for remote regions.
Description of the control
Document the maximum latency the PST can tolerate without loss of communication or data, or any other undesirable effect.
This control belongs to the Performance group of the Trousse globale de vérification (TGV), the certification toolkit of Quebec’s health and social services network. The description restates the criterion from the TGV grid; the rest of the page is Sentrix’s interpretation.
What this control corresponds to
This means specifying the network latency threshold beyond which the application starts to misbehave (disconnections, synchronization errors, corrupted transactions) — particularly critical for remote regions of Quebec where internet connectivity is often slower and less reliable.
Why this control is important
Many facilities in the health and social services network are located in remote regions with limited connectivity (see the provincial requirement on “remote regions (Wi-Fi)”). A PST that does not specify its latency tolerance risks being deployed where it will fail silently, with a direct impact on the availability of clinical data at the moment a professional needs it.
How to implement it
- Test the application under increasing simulated latency (e.g. 50 ms, 150 ms, 300 ms, 500 ms) and note the degradation threshold.
- Document the expected behaviour beyond the threshold (error message, degraded mode, queuing) rather than a silent failure.
- Provide this tolerance in measurable units (ms) in the technical documentation submitted to the Certification Office.
How to verify it is in place
- Request the latency test report and the documented threshold.
- Verify the described degradation behaviour is actually implemented — not just theoretical — via a demo or a directed test.
- Confirm consistency between this threshold and the other performance controls (bandwidth PF03, response times PF05).
Need help with this control?
If you need help implementing or verifying this control, our team supports PST vendors preparing their TGV certification file, control by control. See the TGV certification support service and the TGV framework page, or contact us.
Next in the guide
Next control: PF03 · Minimum bandwidth · Back to the TGV controls guide
Frequently asked questions
- What does “latency tolerance” mean for a PST?
- It is the network latency threshold beyond which the application starts to misbehave: disconnections, synchronization errors or corrupted transactions. The vendor documents the maximum latency the PST can tolerate without losing communication or data, along with the expected behaviour beyond it, so that facilities know where the application can be deployed safely.
- How do you measure the maximum tolerated latency?
- Test the application under increasing simulated latency, for example 50, 150, 300 and 500 milliseconds, and note the degradation threshold. Document the expected behaviour beyond the threshold, such as an error message, a degraded mode or queuing, rather than a silent failure, and provide this tolerance in milliseconds in the technical documentation submitted to the Certification Office.
- Why does this control focus on remote regions?
- Many facilities in the health and social services network are located in remote regions with limited connectivity, and a provincial requirement covers remote regions with Wi-Fi. A PST that does not specify its latency tolerance risks being deployed where it will fail silently, with a direct impact on the availability of clinical data at the moment a professional needs it.
Related pages
TGV guide · Performance
TGV PF01: minimum technical specifications
TGV control PF01 asks the vendor to document the workstation, network and server prerequisites of the PST for the expected user count, backed by a load test.
TGV guide · Performance
TGV PF03: minimum bandwidth
TGV control PF03 asks the vendor to document, in Mbps or Kbps, the minimum network throughput per workstation or per site that keeps the PST running normally.
Let's talk about your compliance program.
Last updated: 2026-09-17