Stand-alone solutions should demonstrate seamless integration, which should include elements such as;

• Single sign-on with PoS login credentials
• Receiving patient context (identification) information from PoS systems
• Automatically sending clinical information to PoS patient records as discreet data
• Sending virtual visit notifications to the PoS
• Calendar information

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

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

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.

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