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.
Description of the control
Document the response times to be expected from the PST under both best- and worst-case conditions.
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
Provide a realistic range of response times (e.g. opening a patient record, saving a clinical note) under both optimal and degraded conditions, setting clear, measurable expectations instead of a vague promise of “speed”.
Why this control is important
A PST’s response times have a direct clinical impact: a health professional waiting on a patient record during a consultation or an urgent intervention loses precious time. Documenting worst cases lets the acquirer assess whether the PST stays usable even under load or network degradation.
How to implement it
- Define the critical operations to measure (login, opening a record, saving, searching).
- Measure response time under nominal load (best case) and under high load/latency (representative worst case, e.g. a remote region as characterized in PF02).
- Publish these times in the technical documentation submitted to the Certification Office and, ideally, in the deployment guide provided to facilities.
How to verify it is in place
- Request the measurement results for each identified critical operation.
- Verify the “worst-case conditions” tested match plausible scenarios for the health and social services network, not just an artificially favourable case.
- Confirm these times are continuously monitored once in production.
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: PF06 · Packet handling and loss tolerance · Back to the TGV controls guide
Frequently asked questions
- Which operations must be measured for PF05?
- The operations that matter to clinical work: login, opening a patient record, saving a note and searching. For each one, response time is measured under nominal load, the best case, and under high load or latency, a representative worst case such as a remote region as characterized in control PF02.
- Why document worst-case conditions and not just the best case?
- Because response times have a direct clinical impact: a professional waiting on a patient record during a consultation or an urgent intervention loses precious time. Documenting worst cases lets the acquirer assess whether the PST stays usable under load or network degradation, rather than relying on a vague promise of speed.
- How does the certifier make sure the published times are credible?
- The certifier requests the measurement results for each identified critical operation and verifies that the worst-case conditions tested match plausible scenarios for the health and social services network, not an artificially favourable case. They also confirm that these times are continuously monitored once the PST is in production and that they appear in the technical documentation submitted to the Certification Office.
Related pages
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.
TGV guide · Performance
TGV PF06: packet handling and loss tolerance
TGV control PF06 asks the vendor to document the packet-loss rate the PST can tolerate, how it handles reordering, and packet time-to-live on real networks.
Let's talk about your compliance program.
Last updated: 2026-09-17