TGV Interoperability group, 58 criteria from I01 to I58

What the group covers

The Interoperability group of the verification criteria grid of the Trousse globale de vérification (TGV), version of April 24, 2026, checks 2 aspects of the technology product or service (PST, its French acronym): its technical integration (external authentication, platform, FHIR, provincial user identification management services, or GIU) and the validated entry of identification data for the service user (usager). It holds 58 of the grid's 382 criteria, from I01 to I58, in 6 categories whose numbers are not always continuous. From I08 on, almost every criterion targets the case where there is a “connection with common-interest information assets containing health or social services information” (arrimage avec les actifs informationnels d'intérêt commun). Only I23, I32 and I45 do not repeat this condition, which is also absent from I01 to I07. Such a link is one of the cases where certification is mandatory, according to the Gouvernement du Québec. The official grid exists only in French, so the criteria and instructions on this page are translated.

The categories one by one

The I01 instruction points to the normative framework for user identifier management (cadre normatif pour la gestion de l'identifiant de l'usager, GIU), which the references column cites as CN-GIU for almost every criterion from I08 to I54.

Interoperability (I01 to I08)

The PST must support external authentication over LDAP and LDAPS (I01) and rely on a recent operating system, components and database management system still supported by their manufacturers, backed by screenshots or version documents (I02). When needed, it can call the cryptographic library of the Windows workstation, or of the Citrix/TS session, to sign, hash and encrypt, with a live demonstration given as an example of proof (I03). I04 and I05 require calling the provincial GIU common services when a record is created, then using their interaction mechanisms to keep identification data up to date and resolve the NIU (unique identification number). I06 covers FHIR transactions and messages, and HL7v3 when needed, and I07 connectors for several technologies. I08 already deals with data: the legal last name of the service user, 50 characters, matching the Quebec health insurance card or the government-issued ID (CN-GIU p. 50-53).

Service user identification (I09 to I19, I35, I41 to I48)

These 20 criteria cover the legal first name (I09), sex per HL7 table 0001 (I10), date of birth (I11, AAAAMMJJ, that is YYYYMMDD, never in the future or more than 120 years back), date of death (I12), the names and first names of the parents (I13 to I16) and spouse (I41, I42), and other usual names (I43, I44). For names, official spelling is mandatory, and so are accents unless the facility's information systems cannot handle French characters, and an abbreviation, only when space runs out, cuts from the right and ends with a hash sign, as in “Laviolette-Latulipp#”. The Quebec health insurance number (NAM, I17, template XXXX99999999) is validated with the RAMQ algorithm (REQ-19-4); its expiry date is mandatory when it is present (I18), and a reason for its absence is mandatory when it is empty, newborns included (I35). The NIU (I19, 10 digits) is obtained only from the user registry (registre des usagers, RU). For uninsured service users, I45 and I46 ask for the type and number of the government-issued identity document (pièce étatique). For every service user, I47 and I48 also allow optional entry of country of birth (ISO 3166-1 alpha 2) and language (ISO 639-2).

Service user's place of residence (I20 to I32, I49 to I52)

These 17 criteria split the address into elements. In the official example “12B, rue des Érables Est, appartement 5A”, the civic number is 12 (I20), the suffix B (I21), the street name rue des Érables Est (I22, 40 characters), the subdivision type apartment (I26) and the subdivision 5 (I27). I23 and I24 handle addresses outside Quebec and outside Canada, I25 the post office box, I28 and I29 the municipality from the Institut de la statistique du Québec (ISQ) list, and I31 and I32 the province and the country (ISO 3166-1 alpha-2). The postal code (I30, template X9X9X9) is mandatory in an admission or registration context and automatically fills in the municipality code, the province and the country. I49 to I52 add the address territory (Quebec by default), the address type (main or permanent, temporary, mailing) and its start and end dates.

Communication with the service user (I33, I34, I53, I54)

These 4 criteria are optional and none is matchable to the RU. They cover the contact type per HL7 table 0201, “PRN” (main) by default (I33), the phone number in 10 digits with no letters or special characters (I34), the email address in 75 characters (I53), and the equipment type per HL7 table 0202, “PH” (telephone) by default (I54).

Data of the facility entering the service user's identification (I36 to I40)

I36 and I37, both optional, cover the facility and installation codes recognized by Santé Québec (template 9999-9999, source M02). The local record number (I38) is mandatory: assigned automatically by the IPL, it is stable and contains no data that could lead to identifying the service user. I39 asks for the OID code or the name of the source application holding the record. I40 describes the IPMÉ identification record number, one letter followed by 10 digits, which identifies a single individual, is never reused and never serves as a record number.

Data access (I55 to I58)

The reference for these 4 criteria reads “Respect de la GIU pour une ouverture de dossier patient” (compliance with GIU when opening a patient record). Their wording repeats I51 to I54 word for word: address start and end dates, email address and equipment type, all optional. The instructions for I57 and I58 only give examples: adressecourriel@domaine.com, then computer, phone or tablet.

Evidence to prepare

This list is Sentrix's interpretation, drawn from the group's criteria and instructions.

• The LDAP and LDAPS configuration and a screenshot of a successful login (I01).
• An inventory of versions (operating system, database, components) and each manufacturer's support status (I02).
• A live demonstration script for signing, hashing and encryption (I03).
• GIU integration documentation and call traces at record creation and update (I04, I05).
• FHIR documentation, HL7v3 if applicable, and the list of connectors with screenshots (I06, I07).
• A data dictionary that maps each PST field to its criterion, from I08 to I58: format, length, template, mandatory status and permitted values (HL7, ISO and ISQ tables, government ID types, reasons for a missing NAM).
• A demonstration of entry validations: RAMQ algorithm, presence in an admission or registration context, dates, auto-fill from the postal code, field locking when the NIU matches the RU.
• Screenshots by user profile showing that the NIU is never displayed (I19).
• The generation rule for local record and IPMÉ record numbers: uniqueness, stability, no reuse (I38, I40).
• If the PST has no connection with common-interest information assets, an architecture and data flow diagram that shows it.

Points to watch

• Read each wording: from I08 to I58, only I23, I32 and I45 lack the connection condition, and I55 to I58 repeat I51 to I54 word for word but remain separate criteria.
• “Mandatory” and “matchable to the RU” are 2 different notions. I15, I16 (father's name and first name) and I17 (NAM) are marked mandatory, but optional for RU matching. With no NAM in the record, the reason for its absence (I35) becomes mandatory.
• Never enter a temporary NAM, recognizable by the “M” in the second-to-last position, as in BERC920401M2.
• The NIU can be neither displayed nor written on a medium meant to be posted, and it must not be relayed to the IPMÉ or the IF by a third party that obtained it from the RU.
• Entry order matters: the address origin (provenance de l'adresse) is entered before the postal code, the province and the country. Sex and date of birth must not be filled in automatically when the NAM is entered manually (REQ-19-53).

Need help with this group?

Sentrix helps PST vendors prepare this group, while certification itself rests with the Bureau de certification de Santé Québec. To discuss it, book a meeting or see the TGV certification support service.

Next in the guide

Back to the full TGV controls guide · TGV framework page