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.
Description of the control
Document the percentage of traffic the PST can add to a service point’s inbound link, across all of that service point’s users, under its intended or normal use.
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 criterion asks you to quantify the share of a site’s (e.g. a clinic’s) total internet/network link capacity the application will consume, not just its absolute need (PF03) — an important distinction when several applications share the same link.
Why this control is important
A service point (clinic, CLSC) has a fixed-capacity network link shared across several systems (clinical record, IP telephony, other applications). If the PST consumes a disproportionate share without this being documented, it can silently degrade the site’s other critical services — a risk the local IT lead cannot anticipate without this figure.
How to implement it
- Calculate, for a typical service point (representative user count), the PST’s share of traffic relative to a common reference link in the health and social services network.
- Present this percentage for different site profiles (small service point vs. large centre).
- Document intensive-use scenarios (e.g. imaging transfer) that temporarily push this share higher.
How to verify it is in place
- Request the calculation and the assumptions used (reference link size, user count).
- Verify consistency with the data measured in PF01/PF03.
- Confirm this information is shared with regional network teams before deployment.
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: PF05 · Expected response times · Back to the TGV controls guide
Frequently asked questions
- How does PF04 differ from minimum bandwidth (PF03)?
- PF03 documents the PST’s absolute throughput need. PF04 asks for the share of a site’s total link capacity, for example a clinic’s, that the application will consume across all of its users. The distinction matters when several systems share the same link: the clinical record, IP telephony and other applications compete for a fixed capacity that the local IT lead has to allocate.
- How do you calculate the traffic share induced by the PST?
- For a typical service point with a representative user count, calculate the PST’s share of traffic relative to a common reference link in the health and social services network. Present this percentage for different site profiles, from a small service point to a large centre, and document intensive-use scenarios, such as an imaging transfer, that temporarily push this share higher.
- What evidence does the certifier request for PF04?
- The calculation and the assumptions used, namely the reference link size and the user count retained. The certifier then checks that this percentage is consistent with the data measured for PF01 and PF03, and confirms that the information is shared with regional network teams before the PST is deployed at the service point.
Related pages
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.
TGV guide · Performance
TGV PF05: expected response times
TGV control PF05 asks the vendor to document the response times to expect from the PST under best- and worst-case conditions, for measurable expectations.
Let's talk about your compliance program.
Last updated: 2026-09-17