Solutions should allow clinicians to send and receive patient agreements and other educational materials relating to virtual services.

Les solutions doivent avoir des interfaces Web et des interfaces utilisateurs accessibles aux Ontariens handicapés et conformes à la Loi sur l’accessibilité pour les personnes handicapées de l’Ontario (LAPHO).

Les solutions autonomes doivent faire preuve d’une intégration transparente, qui doit comprendre certains éléments, notamment :

• Signature unique avec les identifiants de connexion au point de contact

• Réception d’informations sur le contexte du patient (identification) en provenance des systèmes du PS

• Envoi automatique d’informations cliniques aux dossiers des patients du PS sous forme de données discrètes

• Envoi de notifications de visites virtuelles au PS

• Information sur le calendrier

Solutions should not automatically trigger claims submission for all completed virtual visits.

Solutions can assist clinicians to identify virtual visits that are eligible for claims (e.g., offering a “billable” vs “nonbillable” flag).

Automated OHIP verification can assist clinicians from a claims and medico-legal perspective. It can also make patient registration processes more efficient.

Solutions should verify that the 10-digit OHIP number format is valid.

Solutions can also:

• Verify that number is associated with the patient by matching with registration details
• Verify that the patient’s OHIP number is valid through MOHLTC Health Card Validation (HCV)

Virtual visit solutions will allow providers to send surveys to patients in order to: 

• Administer certain types of clinical questionnaires prior to an encounter (e.g., relating to mental health, child development, post-operative care)
• Support quality improvement efforts and patient experience reporting (e.g., at the end of a virtual care encounter)

Clinicians should authenticate using more than one piece of evidence to access the solution (2FA).

Examples:

• FOB + PIN
• Password + Security question
• Password + Authentication app
• Authenticator + SMS/Phone call

Solutions should enable a scheduled video visit to be integrated into the external calendaring systems of other clinicians (e.g., HIS, EMR, Outlook).

Solutions should allow different audio and video sources to be used during an event. For example, the clinician could use a standard webcam and a hand-held exam camera in the same event.

This data could include:

• Negotiated media codecs
• Role of each participant (host, guest) in the event.
• Performance data such as packet loss, jitter.

A common issue that would require investigation is degraded video and audio during a video visit.

H.323 ID, E.164 or SIP URI.

Solutions will allow patients and caregivers to perform equipment (i.e., audio and/or video) and connectivity tests (i.e., Wi-Fi) and send reports to clinics prior to virtual visits.

Solutions will enable patients to import a scheduled event into their calendaring systems (e.g., Google calendar, iCal, Outlook, etc.). Solutions will enable patients to forward a scheduled event to caregivers to participate in the event.

Enables health care organizations and clinicians to launch a secure video visit.

Clinician experience and efficiency can be improved by creating separate inboxes (groups) for administrative versus clinical messages.

Solutions should allow other care team members to join in a secure messaging visit. This can include reading or creating messages.

Physicians participating in the provincial pilot identified the ability to flag patient messages for review as important for triaging and care team collaboration purposes.

Physicians participating in the provincial pilot identified this feature as important in order to confirm that medical advice has been received before a visit can be completed.

Area of Practice.

IP Address.

IP Address.

IP Address.

Participant's name, date of birth, gender, and unique identifier i.e., Health card number