4.2.9: Separate clinical and administrative messages

Arya EHR ( Secure Messaging )

Product Version Jan 12/2013 Primary Vendor Name Arya Health Modality Secure Messaging Video Date of Attestation Verification Standard Version 2.0 Notes 2

The secure messaging modality of this solution has been withdrawn on the basis that it does not meet all mandatory requirements. The video modality of this solution continues to maintain verified status.

Withdrawn On Status Under Review Address

Canada

Do you accept self referrals No Address

2918 Huckleberry Drive
Squamish BC V8B 1B3
Canada

Year Business Started 4.00 Full Legal Name Arya Health Withdrawn Date Recommended Requirements 2.1.10: Meets Web Content Accessibility Guidelines (WCAG) 2.0 Level AA requirements or higher 2.1.12: Support identification of virtual visits eligible for claims submission 2.1.14: Support distribution of patient surveys 2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers 2.1.18: Enable verification of clinician identity using multi-factor authentication 2.1.9: Manage patient agreements for virtual visit services 3.2.11: Enable clinicians to export a secure calendar entry and URL for a scheduled video visit 3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event 3.2.13: Provide an audio-only option 3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active video visit 3.2.15: Provide additional data for operational statistics and information 3.2.16: Enable a videoconferencing endpoint to be added to a video visit using a dialing alias 3.2.17: Provide equipment and connectivity testing 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.11: Allow clinicians to flag patient messages as urgent or requiring attention 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages 5.2.1: Therapeutic Area of Care 5.2.2: Name of Regulatory College 5.2.3: Professional Registration Number 5.2.4: Clinical Provider Location (Event Host) 5.2.5: Participant Location (participants) 5.2.6: Participant Location (patient) 5.2.7: Participant Identification (patient) 5.2.8: Event Outcome

Arya EHR

Product Version Jan 12/2013 Primary Vendor Name Arya Health Modality Video Date of Attestation Verification Standard Version 2.0 Withdrawn Off Status Under Review Address

Canada

Do you accept self referrals No Address

2918 Huckleberry Drive
Squamish BC V8B 1B3
Canada

Year Business Started 2017.00 Full Legal Name Arya Health Recommended Requirements 2.1.10: Meets Web Content Accessibility Guidelines (WCAG) 2.0 Level AA requirements or higher 2.1.12: Support identification of virtual visits eligible for claims submission 2.1.14: Support distribution of patient surveys 2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers 2.1.18: Enable verification of clinician identity using multi-factor authentication 2.1.9: Manage patient agreements for virtual visit services 3.2.11: Enable clinicians to export a secure calendar entry and URL for a scheduled video visit 3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event 3.2.13: Provide an audio-only option 3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active video visit 3.2.15: Provide additional data for operational statistics and information 3.2.16: Enable a videoconferencing endpoint to be added to a video visit using a dialing alias 3.2.17: Provide equipment and connectivity testing 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.11: Allow clinicians to flag patient messages as urgent or requiring attention 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages 5.2.1: Therapeutic Area of Care 5.2.2: Name of Regulatory College 5.2.3: Professional Registration Number 5.2.4: Clinical Provider Location (Event Host) 5.2.5: Participant Location (participants) 5.2.6: Participant Location (patient) 5.2.7: Participant Identification (patient) 5.2.8: Event Outcome

Tia Health / Insig Health / VirtualClinic+

Product Version 7.2.45 Primary Vendor Name Insig Corporation Modality Secure Messaging Video Date of Attestation Verification Standard Version 2.0 Withdrawn Off Status Verified Address

Canada

Do you accept self referrals No Address

358 Dufferin Street,
Suite 301,
Toronto ON M6K 1Z8
Canada

Year Business Started 2016.00 Full Legal Name Insig Corporation Other Operating Names https://insig.ca https://insighealth.com https://virtualclinics.ca Recommended Requirements 2.1.10: Meets Web Content Accessibility Guidelines (WCAG) 2.0 Level AA requirements or higher 2.1.11: Provide seamless integration with Point of Service systems 2.1.12: Support identification of virtual visits eligible for claims submission 2.1.13: Provide automated verification of patient's Ontario Health Insurance Plan (OHIP) number 2.1.14: Support distribution of patient surveys 2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers 2.1.16: Enable verification of provider identity using a provincial identity management service 2.1.17: Will support Canadian English and Canadian French languages 2.1.18: Enable verification of clinician identity using multi-factor authentication 2.1.9: Manage patient agreements for virtual visit services 3.2.10: Enable a virtual waiting room 3.2.11: Enable clinicians to export a secure calendar entry and URL for a scheduled video visit 3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event 3.2.13: Provide an audio-only option 3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active video visit 3.2.15: Provide additional data for operational statistics and information 3.2.16: Enable a videoconferencing endpoint to be added to a video visit using a dialing alias 3.2.17: Provide equipment and connectivity testing 3.2.18: Enable patient to save a virtual visit calendar entry and URL to their virtual calendar application 3.3.1: Enable clinicians to import and launch a video visit from a secured iCalendar data source 3.3.2: Enable clinicians to support an interoperable video visit with sites using codec-based videoconferencing systems and peripheral devices 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.11: Allow clinicians to flag patient messages as urgent or requiring attention 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages 5.2.1: Therapeutic Area of Care 5.2.2: Name of Regulatory College 5.2.3: Professional Registration Number 5.2.4: Clinical Provider Location (Event Host) 5.2.5: Participant Location (participants) 5.2.6: Participant Location (patient) 5.2.7: Participant Identification (patient) 5.2.8: Event Outcome 5.3.1: Create Date 5.3.2: Last Modified Date 5.3.3: Event Actor Available Not Available

Backline

Product Version 6.8.1 Primary Vendor Name DrFirst Healthcare Innovations Ltd Modality Secure Messaging Date of Attestation Verification Standard Version 2.0 Notes 2

This solution has withdrawn from the Virtual Visits Verification Program and will be de-listed from the Verified Solutions List effective December 31st, 2023.

Withdrawn On Status Verified Do you accept self referrals No Address

1055 West Hastings Street
Suite 2250
Vancouver BC V6E 2E9
Canada

Year Business Started 2015.00 Full Legal Name DrFirst Healthcare Innovations Ltd Withdrawn Date Recommended Requirements 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.11: Allow clinicians to flag patient messages as urgent or requiring attention 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages Available Not Available

Lumeca Connect

Product Version iOS 3.9.0; Android 3.1.0 (165) Primary Vendor Name Lumeca Health Inc. Modality Secure Messaging Video Video Secondary Vendor Name Vonage Verification requirements delivered by video secondary product

3.2.1-3.2.6, 3.2.11, 3.3.2

Date of Attestation Verification Standard Version 2.0 Date of Verification Withdrawn Off Status Validated Do you accept self referrals No Address

10 Research Dr,
Suite 200
Regina SK S4S 7J7
Canada

Year Business Started 2012.00 Full Legal Name Lumeca Health Inc Recommended Requirements 2.1.10: Meets Web Content Accessibility Guidelines (WCAG) 2.0 Level AA requirements or higher 2.1.11: Provide seamless integration with Point of Service systems 2.1.12: Support identification of virtual visits eligible for claims submission 2.1.14: Support distribution of patient surveys 2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers 2.1.16: Enable verification of provider identity using a provincial identity management service 2.1.17: Will support Canadian English and Canadian French languages 2.1.18: Enable verification of clinician identity using multi-factor authentication 2.1.9: Manage patient agreements for virtual visit services 3.2.10: Enable a virtual waiting room 3.2.11: Enable clinicians to export a secure calendar entry and URL for a scheduled video visit 3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event 3.2.13: Provide an audio-only option 3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active video visit 3.2.15: Provide additional data for operational statistics and information 3.2.16: Enable a videoconferencing endpoint to be added to a video visit using a dialing alias 3.2.17: Provide equipment and connectivity testing 3.2.18: Enable patient to save a virtual visit calendar entry and URL to their virtual calendar application 3.3.1: Enable clinicians to import and launch a video visit from a secured iCalendar data source 3.3.2: Enable clinicians to support an interoperable video visit with sites using codec-based videoconferencing systems and peripheral devices 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.9: Separate clinical and administrative messages 5.2.1: Therapeutic Area of Care 5.2.3: Professional Registration Number 5.2.4: Clinical Provider Location (Event Host) 5.2.5: Participant Location (participants) 5.2.6: Participant Location (patient) 5.2.7: Participant Identification (patient) 5.2.8: Event Outcome 5.3.1: Create Date 5.3.2: Last Modified Date 5.3.3: Event Actor

Expanse

Product Version 2.1, 2.2 Primary Vendor Name Meditech Information Technology Inc. Modality Secure Messaging Video Video Secondary Vendor Name Vonage Video Secondary Solution Name Expanse Verification requirements delivered by video secondary product

2.1.1 - 2.1.7, 2.3.4 - 2.3.5, 2.3.12, 2.3.14 - 2.3.15, 3.2.1 - 3.2.11

Date of Attestation Verification Standard Version 1.1.1 Date of Verification Withdrawn Off Status Validated Do you accept self referrals No Address

Meditech Circle
Westwood, MA 02090
United States

Year Business Started 1969.00 Full Legal Name Medical Information Technology, Inc. Other Operating Names MEDITECH Recommended Requirements 4.2.9: Separate clinical and administrative messages

Cerner HealtheLife and Video Visits

Product Version 3.18.0 Primary Vendor Name Cerner Corporation Modality Secure Messaging Video Date of Attestation Verification Standard Version 2.0 Date of Verification Withdrawn Off Status Validated Do you accept self referrals No Address

3601 Highway #7 East
Suite 400
Markham ON L3R 0M3
Canada

Year Business Started 2013.00 Full Legal Name Cerner Canada ULC Other Operating Names Oracle Cerner Oracle Health Recommended Requirements 2.1.10: Meets Web Content Accessibility Guidelines (WCAG) 2.0 Level AA requirements or higher 2.1.11: Provide seamless integration with Point of Service systems 2.1.12: Support identification of virtual visits eligible for claims submission 2.1.13: Provide automated verification of patient's Ontario Health Insurance Plan (OHIP) number 2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers 2.1.16: Enable verification of provider identity using a provincial identity management service 2.1.17: Will support Canadian English and Canadian French languages 2.1.18: Enable verification of clinician identity using multi-factor authentication 3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event 3.2.13: Provide an audio-only option 3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active video visit 3.2.17: Provide equipment and connectivity testing 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.11: Allow clinicians to flag patient messages as urgent or requiring attention 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages 5.2.1: Therapeutic Area of Care 5.2.3: Professional Registration Number 5.2.4: Clinical Provider Location (Event Host) 5.2.7: Participant Identification (patient) 5.2.8: Event Outcome

Brightsquid Secure-Mail

Product Version 5.1.48 Primary Vendor Name Brightsquid Secure Communication Corporation Modality Secure Messaging Date of Attestation Verification Standard Version 2.0 Withdrawn Off Status Under Review Do you accept self referrals No Address

3553 31st Street NW
Suite #282
Calgary AB
Canada

Year Business Started 2012.00 Full Legal Name Brightsquid Secure Communication Corporation Recommended Requirements 2.1.14: Support distribution of patient surveys 2.1.18: Enable verification of clinician identity using multi-factor authentication 4.2.10: Enable multiple authorized clinicians to participate in a secure messaging visit 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages

Maple

Product Version Version 4.11.24 | 1678744015 | v87 and higher Primary Vendor Name Maple Corporation Modality Secure Messaging Video Video Secondary Vendor Name Twilio Inc. Video Secondary Solution Name Twilio Inc. Date of Attestation Verification Standard Version 2.0 Date of Verification Withdrawn Off Status Validated Do you accept self referrals No Address

355 Adelaide Street West
Suite 100
Toronto ON M5V 1S2
Canada

Year Business Started 2015.00 Full Legal Name Maple Corporation Other Operating Names Maple Recommended Requirements 2.1.11: Provide seamless integration with Point of Service systems 2.1.12: Support identification of virtual visits eligible for claims submission 2.1.14: Support distribution of patient surveys 2.1.15: Provide ability for virtual visit information to be shared with patients and their caregivers 2.1.16: Enable verification of provider identity using a provincial identity management service 2.1.17: Will support Canadian English and Canadian French languages 2.1.18: Enable verification of clinician identity using multi-factor authentication 2.1.9: Manage patient agreements for virtual visit services 3.2.10: Enable a virtual waiting room 3.2.11: Enable clinicians to export a secure calendar entry and URL for a scheduled video visit 3.2.12: Provide a visual indicator of poor call quality to all participants in an ongoing video virtual visit event 3.2.13: Provide an audio-only option 3.2.14: Provide the ability to switch audio and/or video inputs (USB peripherals) during an active video visit 3.2.15: Provide additional data for operational statistics and information 3.2.16: Enable a videoconferencing endpoint to be added to a video visit using a dialing alias 3.2.17: Provide equipment and connectivity testing 3.2.18: Enable patient to save a virtual visit calendar entry and URL to their virtual calendar application 3.3.1: Enable clinicians to import and launch a video visit from a secured iCalendar data source 3.3.2: Enable clinicians to support an interoperable video visit with sites using codec-based videoconferencing systems and peripheral devices 4.2.12: Provide a read receipt for messages that can be filtered 4.2.9: Separate clinical and administrative messages 5.2.1: Therapeutic Area of Care 5.2.2: Name of Regulatory College 5.2.3: Professional Registration Number 5.2.4: Clinical Provider Location (Event Host) 5.2.5: Participant Location (participants) 5.2.6: Participant Location (patient) 5.2.8: Event Outcome