Vendor Details

Cerner HealtheLife and Video Visits

By
Cerner Corporation
Modality
Secure Messaging
Video
Status
Verified
Attested Date
2021-October-28
Product Version
3.18.0
Verification standard version
2.0
Notes

This solution has withdrawn from the Virtual Visits Verification Program and will be de-listed from the Verified Solutions List effective August 12, 2025.

Solution Provider Details

Other Operating names

Oracle Cerner


Oracle Health

Full Address
3601 Highway #7 East, Suite 400, Markham, ON, L3R 0M3, CA
Year Business Started
2013

Accessibility Information

Published Accessibility Report
Accessibility report not available

Third Party Information

Recommended Requirements

Vendors need to meet all mandatory requirements in the standard to become Verified. Recommended requirements are additional requirements that health service providers may find beneficial for their clinical practices. Below is a list of recommended requirements that this solution meets. Recommended requirements are based solely on vendor’s information provided to Ontario Health and not verified or validated by Ontario Health.

Cerner HealtheLife and Video Visits

Solutions should have web and user interfaces that provide accessibility to Ontarians with disabilities; and comply with the Accessibility for Ontarians with Disabilities Act (AODA).

Area of Practice.

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

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.

IP Address.

An audio visit may be an acceptable alternative if insufficient bandwidth is available to support 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 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).

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

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)

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)

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.

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

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

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

Last Updated: June 23, 2025