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.
Description of the control
Document the minimum bandwidth that guarantees normal operation of the PST.
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
Specify, in Mbps (or Kbps), the minimum network throughput required per workstation or per site for the application to function normally — distinct from latency (PF02), which measures delay rather than throughput.
Why this control is important
A facility planning its network links — often shared across several clinical applications — needs this figure to correctly size its telecom infrastructure and avoid bandwidth contention that would degrade several systems at once.
How to implement it
- Measure the application’s actual bandwidth consumption under typical usage load (per active user and per site).
- Document a minimum floor and, ideally, a recommendation for optimal operation.
- Distinguish, where applicable, the bandwidth required for heavy data flows (images, documents) from light transactional flows.
How to verify it is in place
- Ask for the measurement methodology used (tool, test conditions).
- Verify the documented figure is consistent with the data volume the application is expected to carry (e.g. medical imaging vs. simple forms).
- Confirm this figure was communicated to the acquirer in the deployment documentation.
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: PF04 · Traffic share induced on a service point link · Back to the TGV controls guide
Frequently asked questions
- What is the difference between PF03 and PF02?
- PF03 is about throughput: the minimum bandwidth, in Mbps or Kbps, required per workstation or per site for the application to function normally. PF02 is about delay: the maximum latency the PST can tolerate without losing communication or data. A facility needs both figures to size its network links, which are often shared across several clinical applications.
- How do you measure the PST’s minimum bandwidth?
- Measure the application’s actual consumption under a typical usage load, per active user and per site, with a tool and test conditions that you document. Then record a minimum floor and, ideally, a recommendation for optimal operation, distinguishing where applicable heavy data flows (images, documents) from light transactional flows.
- What does the Certification Office check for PF03?
- It asks for the measurement methodology used (tool, test conditions), verifies that the documented figure is consistent with the data volume the application is expected to carry, for example medical imaging rather than simple forms, and confirms that this figure was communicated to the acquirer in the deployment documentation provided to the facility.
Related pages
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.
TGV guide · Performance
TGV PF04: traffic share on a service point link
TGV control PF04 asks the vendor to document the share of a service point’s inbound link, across all of its users, that the PST can consume under normal use.
Let's talk about your compliance program.
Last updated: 2026-09-17