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

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

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

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.

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.

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.

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.

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

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

An audio visit may be an acceptable alternative if insufficient bandwidth is available to support a video visit.

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)

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).

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

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

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).

Area of Practice.

IP Address.

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 allow other care team members to join in a secure messaging visit. This can include reading or creating messages.

IP Address.

IP Address.