PF03 - Minimum bandwidth
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.
Description of the control
Document the minimum bandwidth that guarantees normal operation of the PST.
Position in the TGV control list
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’s 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 is here to help.
Book meeting with us →Certifying a product for Quebec's health network?
Sentrix helps you prepare your TGV certification file, control by control, from gap analysis to attestation.